From proven controls to a production service.

The core guardrail, ZK, MCP, Skills, and x402 transport layers now exist. The current work is to simplify the public surface, stabilize operations, and prove the service boundary before any production activation.

Delivery track
  1. Shipped

    Deterministic guardrails

    Typed ActionPlans and stable policy decisions across the runtime.
  2. Live on testnet

    Private-policy ZK attestation

    RISC Zero Groth16 receipts verified through Soroban.
  3. Current

    Hosted production path

    Lean infrastructure, guarded x402 activation, and external security review.

Build the boundary before expanding the surface.

NeuroChain already demonstrates the hard path end to end. The roadmap now favors a smaller public product, clear operational gates, and one invariant: payment or valid proof never becomes automatic permission to execute.

  1. Shipped Deterministic foundation

    Plan and evaluate

    • AI and automation requests become canonical, typed Stellar ActionPlans.
    • Allowlist, contract-policy, and intent-safety checks return stable decisions and exit codes.
    • CLI, REPL, .nc scripts, and the API share the same runtime behavior.
    • Preview, confirmation, signing, and submission remain explicit later operations.
  2. Live on testnet Private-policy evidence

    Prove and verify

    • A RISC Zero guest evaluates a typed ActionPlan against a private owner policy.
    • The Groth16 receipt binds the evaluator, plan, policy commitment, decision, and audit nullifier.
    • Soroban verifies evidence read-only, while an owner-authorized path can consume the nullifier and reject replay.
    • A valid proof confirms evidence. It never signs or submits the underlying action.
  3. Current Production path

    Stabilize, activate, and audit

    • Consolidate the public site and hosted runtime into a lean, recoverable operating footprint.
    • Activate the guarded x402 facilitator only after operator, pricing, receiver, and settlement controls are fixed.
    • Complete independent security review, monitoring, recovery, and production key-management design.
    • Consider mainnet only after pilots, audit evidence, and an explicit deployment decision.

What stays fixed.

The implementation can evolve. These product boundaries do not.

Bounded authority

Every request becomes a typed plan before policy or chain interaction.

Inspectable evidence

Private-policy decisions remain independently verifiable without revealing the policy.

See the boundary in motion.

Launch the CLI Explore the code