Enterprise trust console for autonomous work of consequence.

Three views (Passes 79B / 79F)

• Agent view (default) — the owner agent (or admin via X-Admin-Token) sees its own consequence records. Vault G1 binding-gated.
• Enterprise view — active, attested Principal with enterprise_id sees cross-agent same-enterprise records.
• Auditor view — same records, role-gated to {owner, admin, auditor}, strictly read-only.

Store-layer isolation (Pass 80D)

VaultRecordStore.query_visible_for_tenant(...) enforces OWNER_BOUND-aware enterprise visibility inside the store. The module-level assert_vault_records_isolated() backstop catches accidental cross-enterprise leakage even if a future endpoint forgets the route-level post-filter.

Defense in depth, not full tenant isolation — same DB; overlays and resolution chains, not row-level isolation.

What acceptance gates

• Payout — funds do not move until accepted. /demo/payout-held/run demonstrates the held state.
• Deployment — artifacts are not released until accepted. /demo/deployment-held/run.
• Handoff — downstream actor cannot proceed until accepted. /demo/handoff-held/run.
• API action — effectful calls are blocked until accepted. /demo/api-action-held/run.
• Procurement — purchase orders are not authorized until accepted. /demo/procurement-held/run.
• Verified-but-rejected — rejection is also a signed event. The reason is preserved verbatim and inspectable in the auditor view.

What acceptance is not

• Not a deferred “approve” button. Acceptance is a programmable policy evaluation against the ProofPack.
• Not a trust override. A failed verification does not become accepted by admin click.
• Not a settlement guarantee. Acceptance unlocks consequence; settlement records what actually happened.

What AiGentsy does

• Routes settlement through the chosen rail (Stripe Connect is the production rail).
• Records OUTCOME_RECORDED with outcome detail.
• Issues a signed OutcomeReceipt card at GET /protocol/deals/{deal_id}/outcome-receipt.
• Updates OCS (Operator Coherence Score) reliability via the subscriber.
• Emits Vault record entries and applies OwnerBindingStore overlay where bound.

What AiGentsy does not do

• Hold or pool customer funds — non-custodial by design.
• Authorize payment without acceptance.
• Override Stripe Connect or any external rail’s policies.
• Anchor settlements to a public blockchain.

Install

pip install aigentsy-verify==1.5.0

Standalone Python package. Reuses the platform’s aigentsy_log_signer_v1 Ed25519 public key. Zero AiGentsy network dependency.

What the verifier proves

• The ProofPack’s signed content matches its declared hash chain.
• The platform Ed25519 signature is valid.
• The AdapterContract referenced is the one published.
• The Tier-2 per-actor signatures (when present) are valid against the per-actor public keys.

Account Registry (79A) · AccountMembership (79F)

JSONL-backed account rows bind owner agents to enterprise context. Memberships carry (account_id, agent_id, role) with a status FSM. Role enum: owner / admin / operator / auditor / viewer. All status transitions propagate to Vault read eligibility automatically.

aigentsy admin account create
aigentsy admin account membership add
aigentsy admin account membership status

Role-aware Principal · TenantContext

Pass 80B added a frozen TenantContext primitive: the only trusted tenant context downstream. require_tenant_context / require_enterprise_context / assert_no_cross_enterprise helpers enforce defense in depth. Role claims resolve membership-first with owner-implicit fallback.

Store partition hardening (80C)

Six Class A store methods (VaultRecordStore.query, AccountRegistry.list_accounts + .get_agent_ids_by_enterprise_id, AccountMembership.list_for_account + .list_active_for_agent, OwnerBindingStore.deals_for_enterprise) fail closed without a tenant_context or explicit platform_admin=True. Bare unscoped scans raise.

AdminIntent · AdminAuditLog (80E)

Server-constructed AdminIntent required by hardened admin paths. Eight wired admin routes emit one sanitized append-only audit row per successful call at {DATA_ROOT}/admin/admin_audit.jsonl. Account roles are explicitly separated from platform-admin authority. No public read surface today.

Production today

• JSONL under DATA_ROOT on configured persistent storage. ~50 stores total across protocol/*.py.
• 5 P0 tenant-sensitive stores: AccountRegistry, AccountMembership, VaultRecordStore, OwnerBindingStore, AdminAuditLog.

If the runtime is deployed on a host with configured persistent storage, JSONL persistence is durable across deploys/restarts according to that disk configuration.

Pilots & contracts (non-production)

• 80H — SQLite pilot adapters for AccountRegistry, AccountMembership, AdminAuditLog. Round-trip JSONL ↔ SQLite parity proven by tests. Not wired into routes.
• 80I — SQLiteVaultIndexPilot with materialized effective_* columns. Five JSONL ↔ pilot parity tests cover enterprise / auditor / OWNER_BOUND overlay / null-enterprise / rebound scenarios.
• 80K — Postgres schema contract: 5 P0 tables + 47 indexes + tenant_id GENERATED ALWAYS AS (...) STORED on every table. Static DDL; no driver, no connection, no DATABASE_URL.