Status

Current working state.

An honest, up-to-date view of what is built, what is in progress, and what is not yet enabled.

Build status panel: ALL SYSTEMS OPERATIONAL — working, in-progress, and not-enabled items listed with test suite output
Current build state — verified by test suite
Working
  • ✓ Local x402 simulation for paid data procurement
  • ✓ Base-first wallet profile architecture
  • ✓ Akasha Control Room
  • ✓ Provenance and accounting
  • ✓ Governed paper trading
  • ✓ Live trading block path
  • ✓ Base Sepolia x402 adapter installed
  • ✓ Decision packet signing
  • ✓ Budget reservation engine
  • ✓ Merchant route fingerprinting
  • ✓ Payee drift detection
  • ✓ Constitution compiler
  • ✓ Postgres runtime
In progress
  • ~ Funded Base Sepolia x402 payment proof
  • ~ Test USDC receipt persistence validation
  • ~ Builder Codes attribution
  • ~ Spend Permission compiler target
  • ~ Postgres runtime hardening
  • ~ Akasha repo integration
Not enabled
  • ✗ Autonomous live trading
  • ✗ Unsupervised real-money spend
  • ✗ Raw wallet signing
  • ✗ Base mainnet payments
  • ✗ Production custody
Test coverage

Verified by the test suite.

Core flows are covered by unit, integration, and Postgres tests. Run them yourself to verify any claim on this page.

Full test run 
pnpm typecheck       # Type safety
pnpm test            # Unit tests
pnpm test:integration # Integration tests
pnpm test:postgres   # Postgres-backed tests
Confidence signals

Why the MVP is credible.

Typed end-to-end

No untyped paths from SDK call to persistence. TypeScript strict mode throughout.

Deterministic runtime

The evaluation engine produces the same output for the same input. Policy is not probabilistic.

Dual storage backends

The same flows run in snapshot mode for local demos and Postgres mode for durable validation.

No agent signing surface

The SDK exposes zero signing methods. The live trading block path is tested, not assumed.

Honest about gaps

Real x402, production custody, and live trading are listed as not enabled — not as future roadmap items to hide.

Akasha integration real

The Akasha adapter connects through the same SDK surface any developer would use. No privileged internal path.

Verify it yourself.

The demo runs all five flows locally. The test suite prints pass/fail for every claim on this page.

Run the demo → Quickstart guide