Compatibility: Pactmark 0.1.x.
The intended flow
Figure 1. Read this alongside your own network diagram. Pactmark’s flow is only half the picture — the other half is where each of these stages physically executes in your infrastructure. Stated as a sequence:1
The host authenticates a principal and validates a WorkOrder
Tenant and principal come from the authenticator, never from the request body.
2
Policy and admission reserve authority and budgets before mutation or export
Reservation happens first. A crash after this point cannot leak budget.
3
The runtime appends events and stores protected resumable context separately
Run truth and operational context are different records with different lifecycles.
4
The model adapter receives only admitted context and a bound credential reference
Never a resolved secret, never another call’s credential.
5
Tool requests return to policy; the executor resolves credentials and egress at dispatch
Not at planning time. The gap between “decided” and “dispatched” is where revocation lands.
6
Effects write preparation, acknowledgement and reconciliation state around the boundary
Before, and after. The ledger is what makes uncertainty recoverable.
7
Artifacts enter content-addressed storage, then exact verifiers run
Addressing first, verification second, bound to the address.
8
Redacted evidence records selected claims and digests
With a required statement of what it does not prove.
Trust boundaries
Figure 2. Each numbered crossing is a place where untrusted data becomes trusted only after an explicit check. Your deployment diagram must add the operator’s real network, region, key, backup and identity systems on top of this.Where data physically lives
Notice the last row. Pactmark records the model security profile — provider, region, retention,
logging, training — but it cannot enforce what happens on the other side of that boundary. That is a
contract question, and the profile exists so the contract is written down and digested.
Credentials across the boundary
Figure 3. The reference is issued after authority succeeds and resolved immediately before invocation. The resolved value has no persistent home anywhere in the system.What your deployment diagram must add
Network topology
Which components can reach which, egress paths, and where TLS terminates.
Regions and residency
For the host, database, artifact store, model provider, tools, logs, backups and support systems.
Key management
Where encryption keys live, who can use them, and how rotation works.
Backup topology
What is backed up, where it goes, how long it lives, and who can restore it.
Identity systems
How your IdP maps to principals, tenants, authentication strength and decision roles.
Observability path
Where telemetry and logs go, and who can read them.
Secrets, egress and regions
The credential and network boundary in operational terms.
Threat model
The same boundaries, with adversaries and controls attached.