Shared state needs a home agents can use

Multi-party operations already share state. Today that state lives in each organization’s private systems plus reconciliation exports and attestation PDFs. Race conditions across orgs, “who changed this,” and assessor packs built from screenshots are the symptoms. Agents make the gap worse when lasting commit power sits inside the model.

Delegated authority for agents on a shared record.

Legate is Stratum’s envoy for AI agents: delegated access to a multi-party shared record, with humans keeping the final say and the AI never keeping lasting power to commit changes.

Stratum is the scoped shared record no single organization controls. Arbiter is the verification-first evidence layer when records must be assessor-ready. Agents prepare. Signers conclude.

This portal describes states, shapes, actor boundaries, and verification checks. It is not a full API dump. Judgment, scoring, and policy source stay private. See Disclosure Boundary.

Unit of record

The unit of record is a scoped shared record on Stratum.

Layer	Role
Stratum	Durable shared record. Ordered writes. Independent proof. No single owner
Legate	Envoy for agents: delegated access under packs and consent. Humans keep the final say
Arbiter	Optional sealing and assessor-oriented evidence when the interface exposes it
Agent host	Private generative layer. Out of this contract
External signer	Human or dedicated signer that applies the final signature after prepare

What this stack provides

Capability	Outcome
Shared record state	One answer to where the record sits and what can happen next
Delegated agent access	Short-lived credentials under packs such as legate.read / legate.write
Write authority boundary	simulate → prepare → external sign → submit_signed
Evidence integrity	Machine-native shared state; optional Arbiter fingerprint/seal at the interface
Verification checks	What a permitted party can confirm — and what verification excludes

How the system fits together

1. Stratum holds scoped shared state counterparties can rely on without trusting one org’s database.
2. Legate exposes tools under packs and write consent. Agents prepare; they do not conclude writes.
3. Operators and external signers entitle connections and apply final signatures.
4. Arbiter (when entitled) attaches assessor-oriented evidence to that shared record path.

Who connects

You are…	What you need	Start here
CTO / Head of Infrastructure	Agents on a multi-party shared record without a specialty platform team	Integration Surfaces → Access model
CISO / GRC / Compliance	Assessor-credible provenance when agents touch the record	Disclosure Boundary → Verification model
Technical champion	Connect a client after the business case	Connect → Quickstart

Reading order

To answer	Read
What can I rely on today	Integration Surfaces
Who may act and who signs	Access model
What agents should and must not do	Agent guide
What is published vs private	Disclosure Boundary
What verification proves	Verification model
How to connect a client	Connect