← All whitepapers

Platform architecture

The federated data platform

By Richard White ·

Free, no form.

Abstract

The architecture update adds a platform view and an authorized request-to-action path, with an invoice example connecting domain ownership, context, retrieval, approval and execution.

A practical architecture for domain delivery, shared services and consistent enterprise control. Domains publish supported products; shared infrastructure and a common control plane make their operation coherent.

The paper connects analytical and operational paths, sets out the three platform planes, explains where a semantic layer helps and where it does not, gives selection criteria, shows the control plane in action, and treats copy-or-query as a cost and control decision. It closes with golden paths, a capability map, AI services, agent access and a readiness sequence.

It assumes the stack you already have. In a smaller firm the platform can be one managed cloud stack and a small team; the sequence holds, and each step is smaller.

Architecture update · 29 October 2026

From domain data to an authorized AI action.

Domains own their products and meaning. Shared services support identity, policy, delivery and operation across analytical, operational and knowledge paths. Each serving interface enforces the decisions that apply to its resources.

Source systems feed domain analytical, operational and knowledge products, then governed interfaces and consumers. Shared control services span all paths; shared semantics connect domain models.
Richard White’s architecture, adapted into an RJL reference design. Domain ownership can use shared infrastructure.

A question and a command have different authority.

An employee asks why an invoice is held. The application verifies identity and context, then retrieves permitted evidence. A request to change the invoice follows a separate approval and command path. The model’s response cannot grant permission.

Verify identity and bind context; authorize and retrieve; explain or propose; approve and recheck; execute with idempotency; record and operate. A read-only answer ends after explanation with its own evidence record.
Illustrative request path. Stop the affected operation when mandatory context, authority or current state cannot be established.

This is a reference design for client architecture work. It does not describe every capability of the current Studio demos.

In the paper

Three passages, as published

Architecture is not authorization

Name the policy authority and each serving enforcement point.

Count all operating cost

Zero-copy isn’t zero-cost, and it isn’t automatically safer.

The platform promise

A team can create a supported product without rebuilding identity, deployment, monitoring and baseline policy from scratch.

Keep reading

Read next

Stay informed

Subscribe to whitepapers and updates

Hear from Richard White when new whitepapers, practical guides and Studio updates are available. Subscribing is optional; every whitepaper remains free to download.

We use your email for these updates. Reply to any update or email rwhite@rjlsol.com to unsubscribe. See our privacy notice.

Next step

Discuss this paper against your own program.

A free sixty-minute working session with Richard on your top gaps. You leave with a one-page summary within three business days, and three next questions.