Antonius de Kok / Architecture AtlasSelected architecture / DAC
DAC / Agentic transactions

Checkout needs
its own authority.

Deterministic Agent Checkout

A closed checkout architecture for protected agentic transactions.

Proposed transactionProtected checkout

Public boundary view · conceptual illustration

Explore the boundary
Architecture status

Complete, structurally closed architecture

01 / Governing boundaryDAC / Public description

From proposal
to consequence.

DAC governs the boundary at which intelligent continuation attempts to move from proposal, instruction, or generated action into protected transaction consequence.

The architecture prevents prompt injection, content steering, delegated ambiguity, or model-controlled continuation from becoming transaction authority.

Protected actions require independently established authorization bound to the exact transaction context.

01

Content & continuation

Webpage content and model-controlled continuation do not become authority for protected transaction consequence.

02

Exact transaction context

Protected action requires independently established authorization bound to the exact transaction context.

03

A bounded domain

DAC was developed for checkout and can operate as a specific checkout extension within the wider AGS architecture.

02 / Architectural contextDistinct domains. Defined boundaries.
Related architecture / AGS

Checkout within a wider authority architecture.

DAC addresses the narrower checkout domain. AGS addresses authority across agentic tools, services, workflows, and institutional environments.

03 / Status & disclosureComplete privately. Disclose selectively.

A public outline.
A controlled discussion.

Status
Complete, structurally closed architecture
Availability
Controlled acquisition discussion only

Public descriptions establish the domain, governing boundary, and significance. Enabling technical structure remains under controlled disclosure.

Implementation, deployment, adaptation, and post-transfer development belong to the acquiring party.

DAC / Controlled discussion

Begin with
the transaction boundary.

For a relevant acquisition discussion, identify the transaction domain, why DAC may matter, and the authority to consider acquisition.

Discuss DAC