Skip to main content
Test counts below are from a per-package vitest run on 2026-07-06 (commit 1f62e24 plus this session’s uncommitted work). Running vitest run once from the repo root instead of per-package will produce spurious failures in packages/runtime — several tests resolve fixture paths relative to process.cwd() assuming a per-package invocation; this is a pre-existing test fragility, not a functional bug (see Troubleshooting).
PackagePurposeStatusTestsEvidence
sharedDomain types, config, canonical JSON types[AVAILABLE]6packages/shared/src/domain/*.ts
cryptoSigning, hashing, key providers, canonical serialization[AVAILABLE]29AuthorizationSigner, Ed25519SignatureProvider, Dilithium3SignatureProvider
policyDeterministic, first-match-semantics rule evaluation[AVAILABLE]61PolicyRouter, PolicyValidator, CLAIMS.md 2.2/2.3
runtimeOrchestrates policy → decision → execution → trust record; the 3-check VerificationService[AVAILABLE]31packages/runtime/src/services/verification-service.ts
apiThe Express HTTP server — the only long-running process[AVAILABLE]30 + 1 skippedpackages/api/src/app.ts
receiptCryptographic receipts over a verified Trust Record[AVAILABLE]— (covered via runtime/api)ReceiptCrypto, ReceiptHasher
replayDeterministic execution reconstruction[PARTIAL]9Package + engine real; semantic verification of every trust artifact is an explicit Future Claim in CLAIMS.md, not yet true
storageAppend-only ledger abstraction; memory / Postgres / Supabase providers[AVAILABLE]8memory provider verified live this session; Supabase/Postgres providers exist in source, not independently verified in this audit
envelope-verifierVerifies a SignedExecutionAuthorization: signature, expiry, TTL, nonce[AVAILABLE]15EnvelopeVerifier, CLAIMS.md 2.9/2.10
execution-gatewayRecomputes content hash, compares to businessTransactionHash, releases to a Connector[AVAILABLE] as a library; not wired into the running server25ExecutionGateway.ts:150-165; see the Warning on Architecture Overview
execution-controlGateway-authenticated, session-scoped credential isolation for connectors[PARTIAL]11ExecutionControlService, InMemoryCredentialVault — real scaffold, not the finished “AI never holds credentials” claim (see Roadmap)
execution-systemExecutionSystem interface + the default (non-gateway) implementation the server actually uses[AVAILABLE]1packages/execution-system/src

​
SDKs and app

PackagePurposeStatusEvidence
python/Python SDK[AVAILABLE]26 tests, structured HTTP exceptions, generated + drift-guarded models
typescript/TypeScript SDK[PARTIAL]Real client/model code; all 9 test files are empty (0 lines); HttpTransport.ts:107-125 returns any HTTP status as a “successful” response — 4xx/5xx are never raised

​
Not a package: python-old/

A prior Python SDK generation (v0.1.0) was being removed from the repository as of this session (uncommitted deletion in the working tree). Not part of the current architecture.