THE ROADMAP — HELD AS BINDINGS, LIKE EVERYTHING ELSE

Shipped is graded. The rest is bound, and open.

Most roadmaps are promises with no test attached. This one is written in the product's own grammar: what is marked graded has been graded against the house's daily use; what is not is a commitment we have written down — with its gate — and will be graded on.

TWO TRACKS, INTERLEAVED

The apparatus, and the doors into it.

The Foundation track — the apparatus

Packaging the proven substrate into the shipping product, standing up the two surfaces, the tenancy foundation, the attestation layer — and the multiplayer workspace on top. Engineering, not research.

packaging → two surfaces → tenancy → attestation → multiplayer

The Product track — the surfaces

The credibility-to-depth ladder, cheapest-proven-work first: the dossier, then the binding ledger and coordination, then the clash check and blueprints, and only when tenancy, attestation, and consent are real — the org platform and the graph.

credibility first, the whole way up

The starting position matters: the substrate is already proven. The house runs on it — every wave of Vulcora's R&D is bound before the work, graded when it lands, and kept. What gates the build is packaging and foundation engineering, not whether the discipline works. The house runs on it →

GRADED — SHIPPED AND DOGFOODED, DAILY

What already holds.

  1. GRADED_SATISFIEDthe binding lifecycle — declared → claimed → satisfying → graded, retractable from every live state with a reason it must state, and every transition writing a versioned row
  2. GRADED_SATISFIEDthe three-valued verdict — satisfied · violated · indeterminate, append-only, with a concluding verdict refused unless it carries evidence and the abstain deliberately left free
  3. GRADED_SATISFIEDthe goal tree and its gates — work attaches only at a ripe leaf; four gate kinds, each recomputable from this ledger's own rows, and a gate that cannot tell refuses rather than passes
  4. GRADED_SATISFIEDthe maker's MCP surface — the full ritual worked from inside your own tools
  5. GRADED_SATISFIEDthe gate and the guard — a commit naming no bound intent refused in the repository; the range re-walked on our side from a boundary commit, against keys the organization enrolled rather than any file the repository holds
  6. GRADED_SATISFIEDthe observatory, single-operator — the orrery over one org's goal tree, the three ledger lenses, the coordination plane, and the two machine reads, all live over one seam
  7. GRADED_SATISFIEDthe workspace runtime — allocation under a lease, the seat as a real terminal rather than a transcript, and a machine the plane cannot address saying so at both ends

SATISFYING — CLAIMED, IN FLIGHT

What is being satisfied now.

  1. SATISFYINGpackaging — the proven substrate into the shipping product, hardened surface by surface. Measured, and de-risked
  2. SATISFYINGthe accountability dossier — intake → dossier → portal, repeatable before it counts as done
  3. SATISFYINGbind-first workspace start — plan and bind in the workspace, make in your own tools

DECLARED — BOUND, GATED, NOT YET CLAIMED

What is written down, and what gates it.

  1. DECLAREDworkspace tenancy — org · team · workspace · membership over ONE ledger with row-level scoping, never a physical split. The long pole, and we know it: sizable, mechanical, well-understood — the critical path runs through this pass
  2. DECLAREDthe attestation layer — the manifest fingerprint is deterministic today; the exchange around it (challenge/response, per-action tokens, trust tiers) is the remaining build
  3. DECLAREDthe multiplayer flagship — many humans + agents in one shared org world, clash-checked at bind-time, both surfaces at org scale. Gated on surfaces + tenancy + attestation together
  4. DECLAREDthe clash check, all of it — syntactic overlap as much as semantic contradiction. Neither runs today: the shipped ledger has no clash state and nothing computes one. This line said "phase-1 syntactic clash, near-complete" under a graded chip until 2026-08-15, and that was false. Gated on the concurrent multi-maker workspace, where two live binds can meet at all — and no coverage number will be quoted before one has been measured
  5. DECLAREDfalsifiability translation — a natural-language promise turned into a test spec by the sealed engine. Today the maker writes the test, and an intent bound without one records that nobody stated a test
  6. DECLAREDForgeBlame and the nav-spine — gated on an intent recording the paths it moved; today it records a commitment and a test, and there is no edge from a line of code to the commitment it answered
  7. DECLAREDthe conductor and the verifier suite — an automated compile / drift / test pass grading a commitment before it lands. Nothing of this exists; what does exist is the gate that refuses an unnamed commit and the guard that proves the gate ran
  8. DECLAREDblueprints as a library — a named, typed, ordered procedure that can be walked and graded as a unit. The practice is real in the house; nothing in the shipped ledger holds a blueprint, so this is a build, not a productization
  9. DECLAREDorg instances + the cross-org graph — hard-gated on full tenancy, attestation, consent, and the data firewall; no schedule ships it early
  10. DECLAREDthe OS runtime's upper rungs — containers, micro-VMs, per-customer federation, the governance rituals at org scale; the confession channel is the most distinctive piece, and honestly the least built
  11. DECLAREDthe editor you open — gated on being genuinely better than editing next to Solora; an earned move, never a forced one

THE LOAD-BEARING ORDER

The gates are the roadmap.

Held in this order, or not at all

  • Packaging before anything. Nothing ships until the proven substrate stands on its own inside the product.
  • One ledger, never split. A workspace is a projection over one record, never a separate store — the whole cross-cutting value lives on one index.
  • Surfaces + tenancy + attestation before multiplayer. The flagship is the synthesis, not a shortcut.
  • Credibility first. The house has run on the substrate from day one; the dogfood is the credibility.
  • Consent before the graph. The cross-org graph ships on consented data with measured isolation, or it does not ship.
  • Evidence, never a guarantee. Every phase carries honesty and privacy underneath — and no coverage number is published before it is measured, because an unmeasured bound is a guess wearing a percentage sign.

Measured, not asserted: planning experiments against the live substrate say the remaining work is engineering, not research — the long pole is tenancy. The whole is buildable; the critical path runs through the tenancy pass.

What is marked graded has been graded. What is not, is a commitment we have written down — and will be graded on.

The world, lit in order.

What holds today is graded against the house's daily use; the rest is bound, gated, and named — a roadmap written in the product's own grammar. Solora is the world the work runs in, over one accountable ledger — bound before the work, graded when it lands, kept in the light.

PUBLIC ACCESS · SOON  The apparatus is live inside the house today; this is how it works.