Vertical roadmap, straight and readable
The goal is simple: anyone landing here should understand the maturity of the project immediately, without digging through commits or scattered notes.
-
Stable base layer
- Locked baseline model for Stellar intent planning with strong eval and golden coverage.
- Guardrails already in place: allowlist, policy checks, and intent safety exit paths.
- Typed templates v2 support practical normalization for `address`, `bytes`, `symbol`, and `u64`.
- Runtime parity across REPL, `.nc` files, CLI, and API keeps behavior predictable.
- Public web demos make the current surface reviewer-friendly and easy to understand.
-
Contract-aware Soroban depth
- Deeper Soroban integration through typed templates per contract function instead of generic intent routing alone.
- Event and return-value decoding fed back into DSL flow so the script can react to on-chain responses deterministically.
- First real multi-step workflow executed inside one `.nc` run, not just isolated single-step actions.
- Sharper testnet demo and runbook flow for external reviewers and technical pilots.
-
Toward pilot readiness
- Contract-level resource and fee guardrails.
- Consistent audit trail and error taxonomy.
- Release hardening with regression and parity gates.
- Pilot candidate flows evaluated on testnet.
What the roadmap is optimizing for
This is not roadmap theater. The throughline is deterministic execution, reviewer clarity, and practical integration depth.
Determinism first
Every phase keeps the “explicit plan before action” model intact instead of hiding behavior behind opaque automation.
Better integration depth
The next leap is not cosmetic. It is stronger contract-level structure and richer DSL-to-chain feedback loops.
Reviewer confidence
The final shape targets traceability, safer pilot execution, and a clean explanation surface for external evaluators.
Try the live surfaces while the roadmap advances
What is already visible publicly is meant to show the philosophy now, not just promise it later.