How it comes together, end to end.

The architecture

The agentic enterprise, layer by layer.

People and agents work in redesigned processes on top of five layers. Security frames every layer, and orchestration and operation run beside them. The names match the capability map and the product layers below.

Vendor neutral. Three requirements anchor this design: identity for every agent, meaning separate from access authority, and evidence that lets an authorized reviewer reconstruct a request.

The layers

One example combination of products.

Examples, not endorsements. The architecture depends on the contracts between layers, not on these products. A substitute must keep the same contracts and controls. Richard has worked closely with several vendors named here as a customer and practitioner. No vendor reviewed or paid for this content.

Use case · synthetic reference example

A claims assistant, traced end to end.

A claims examiner asks who is connected to an assigned case, its status, and which procedure applies. This read-only architecture pattern supports the synthetic claims preparation guide: team A, group disability, region 2. Events within the assigned case are included; prior-claims history, internal notes, decisions, payments and customer contact are excluded from its narrowed release.

1. 01

   Security

   The examiner signs in through single sign-on. The assistant runs under its own agent identity, registered to the claims owner, with a defined role.

2. 02

   Security

   The request carries a short-lived token scoped to this examiner and this agent: only what both are allowed.

3. 03

   AI

   A fixed sequence resolves claim status, the related parties and the applicable procedure. Cross-case search and note tools are unavailable in the narrowed runtime.

4. 04

   DataSecurity

   Claim status comes from a certified data product through a narrow API. Tag-based masking hides fields this examiner may not see.

5. 05

   DataSecurity

   Procedure documents were classified and labeled by the DSPM tool. Retrieval returns only documents this examiner may read, for this tenant.

6. 06

   Security

   One document contains hidden instructions to email the file outside the company. The agent has no tool that can send externally; the attempt is refused and flagged.

7. 07

   AI

   The answer separates facts from interpretation, cites its sources and flags an unresolved party match for the examiner.

8. 08

   Security

   Every step is traced with the agent’s identity, the user, the tools, the data labels and each policy decision, and streamed to the SOC.

9. 09

   Security

   Days later, the agent starts requesting claims outside the examiner’s assigned book. Each call is denied; the repeated denials alert the SOC, and a playbook suspends the agent identity and opens an incident for the owner.

10. 10

    Security

    When an examiner leaves, the identity provider removes access, and the revocation test shows the assistant stops using it within the tested window.

11. 11

    Orchestration

    The trace, the refused instruction, the incident and the revocation test become release evidence. The owner decides whether to restore the agent, and on what conditions.

All records and outcomes here are synthetic. The steps illustrate architecture and incident handling, not a client deployment or an executed test. The versioned workflow record and completed release decision define the worked guide’s accepted scope and held dependencies.

Agentic delivery

Faster code still needs authority, independent checks and learning.

Coding agents can draft, test and execute changes within bounded tools and identities. The loop starts from governed intent, validates independently of the agent that made the change, releases under named authority and feeds what operation reveals back into intent.

Data Is Not Just Code