Financial-authority specifications
Inspect the contracts that make GuardState's financial-authority model independently reviewable across identity, Mandate, Acceptance, Permit, evidence, telemetry, conflicts, and provider boundaries.
Financial Agent Events
The event specification preserves durable identity, source, occurrence time, correlation, causation, idempotency, authority class, integrity, and replay semantics so a proposal cannot be confused with execution evidence.
Agent Passport and Investment Mandate
Agent Passports describe identity and evidence state. Investment Mandates define versioned capital and authority constraints. Neither grants execution by itself, and hierarchical Mandates narrow rather than silently widen inherited authority.
Authority Envelope and Acceptance Record
The Authority Envelope derives effective reach from identity, role, Mandate, policy, risk, approvals, credentials, account, provider capability, control boundary, circuits, and Permit state. Acceptance Records preserve the deterministic gate outcomes and reason codes for each evaluated financial action.
Execution Permit v2
Execution Permit v2 binds the material authorization context for an exact financial action, including identity, Mandate, Authority Envelope, Acceptance, account, provider, instrument, bounds, policy, evidence, approvals, boundary identity, validity, nonce, key, and signature. Permits are short-lived and single-use.
Decision Evidence and Conflict Provenance
Decision Evidence records observable financial inputs and outputs without requiring hidden model reasoning. Conflict and incentive relationships retain their evidence class and do not independently establish misconduct.
Financial OTel and Evidence Pack
Financial OTel correlates standard observability context with financial-authority identities while minimizing sensitive telemetry. Evidence Pack v3 provides human-readable and machine-readable proof of the decision path, including missing or unverified evidence rather than hiding it.
Versioning discipline
Compatible additions can evolve within a stable contract; changes to authority semantics, required bindings, signature behavior, or other breaking protocol elements require an explicit version transition. Compatibility must never silently widen financial authority.