Roadmap

ContextStack tracks delivery through five horizons. Horizons report sequencing and current status; they do not replace the North Star's definition of done.

Delivery horizons

H0 — Reliability baseline · closed green 2026-06-19

The exit gate required a ≥70% verified pass rate. The measured result was 93% with a +5% verifier lift. The kernel → node → gateway → csworker path and seven targeted seams were demonstrated. This is real factory-substrate evidence, not evidence that the organizational product is complete.

H1 — Operator surface and overnight lanes · active

H1 exercises shadow cohorts at sustained volume and closes the security controls needed before unattended work can scale. Those controls are not all landed.

The current command center is still a CLI and trace view. H1 being active does not mean the finished Bot roster, workrooms, approval inbox, or intelligence view exists. The organizational product surface belongs to later horizons.

H2 — Mission layer · pending

The first narrow, productized responsibility reaches A1 graduation and uses the production executor path. The goal is one earned mission layer, not a generic UI claiming every kind of work.

H3 — Hardening and first dark lane · pending

Concurrency expands, governed learning activates, and the first revertible action class earns A2 with automatic compensation. Structured collaboration begins only where responsibility genuinely diverges.

H4 — Dark factory and organization steady state · pending

Level 5 operating criteria become an active gate: goal-only operation, closed-loop improvement, adjudication hardening, and long-horizon stability. The organizational surface and expansion by durable responsibility mature here.

H4 is the final delivery horizon. It is not, by itself, proof that the North Star has been reached.

The thirteen-box finish line

ContextStack reaches its North Star only when all thirteen conditions close under versioned verification specifications, minimum evidence windows, and independent completeness review:

1. Delegation is the interface. People assign outcomes instead of authoring workflows.
2. The organization is durable. Bot identity and responsibility survive processes, models, machines, and time.
3. One executor, no second loop. Bot work uses the governed Kernel, Node, UAH2, and Gateway path.
4. The majority runs dark. Routine work completes without contemporaneous human intervention under measured policy.
5. Model independence. Removing one provider changes cost or latency, never identity or canonical state.
6. Economics are measured and improving. Cost per accepted outcome trends down at equal-or-better verified quality.
7. The existing estate is absorbed. Standing automations become Bot-owned missions, collectors, or retired capabilities with no orphan work.
8. Learning compounds without silent drift. Promotions are measured, reviewed, versioned, and reversible.
9. Authority is never ambient. Every irreversible action resolves explicit or evidence-earned, revocable authority for that action class.
10. Collaboration is inspectable. Commitments, handoffs, and evidence bundles retain one accountable owner and reconstructable history.
11. The operator surface is an organization. Command center, Bot roster, Bot workspaces, shared workrooms, approval inbox, and intelligence view render canonical Kernel truth.
12. The stack builds itself. Most ContextStack changes land through its own guarded, evidence-backed lanes.
13. Ownership is total. Definitions, state, memory, evidence, and ledger can be exported and restored without a rented identity dependency.

None of these conditions is claimed closed by this public page. Missing, stale, or incomplete evidence fails closed and can reopen a previously accepted result.

Availability

ContextStack is in active development. There is no generally available product, pricing plan, or beta today. Use the updates form on the home page to hear when that changes.