developer · AVC

Executable boundaries are the source of truth.

Schemas define allowed states, transitions and compatibility.

Adapter contract

One shared surface serves two users without merging their authority.

The human interacts with a view while the assistant receives bounded state and invokes named tools.

Human view

May
Present state, collect decisions and expose consequences.
May not
Imply that a displayed control already executed a tool.

Assistant context

May
Receive the minimum structured state needed to reason.
May not
Read hidden client state or infer credentials from presentation.

Tool contract

May
Validate inputs and perform one declared server action.
May not
Expand scope beyond its schema or bypass authorization.

Evidence contract

May
Record request, approval, action and outcome references.
May not
Treat UI optimism as execution proof.
Serialized truth

Contracts define allowed state, identity and compatibility.

Schemas for capabilities, jobs, events, evidence, risk, money and Product Cells provide shared machine-enforced vocabulary.

Boundary behavior

Inputs, outputs and failure semantics belong in the interface.

A contract is incomplete when consumers must guess whether an operation is idempotent, reversible, asynchronous or approval-gated.

Shared conversational surfaces

Human view state, assistant context and tool execution remain distinct.

Any future MCP or ChatGPT adapter must make shared state inspectable to both users without turning UI state into hidden authority.