0x0LearnReferenceLibraries0x0.jmp0x1b.com

Full Parity Production Roadmap

This is the single active roadmap for making 0x0 a production replacement for

the current local source set:

The result at the end of this roadmap must be full parity. A feature is not

complete because a document exists, a constructor exists, a test fixture returns

the expected shape, or a checker knows how to inspect a static file. A feature is

complete only when the 0x0 implementation is the normal production path and the

same user-visible behavior, release artifacts, operations, tests, public docs,

and support matrices are present.

Non-Negotiable Closure Rule

No milestone may close with contract-only, demo-only, draft-only, fixture-only,

constructor-only, checker-owned, or shim-owned behavior.

Every closed milestone must prove:

status text.

release, not silently missing from parity claims.

Current Blocking Facts

cannot close until the old library source is restored, recovered from version

control, or replaced with an auditable source snapshot.

163 Index rows and 252 Kukulkan rows, with 0 rows marked production-ready.

behavior, artifacts, and evidence directly.

Standing Rules

review in the same change set. Run make adr-rfc-check and

make documentation-impact-check.

final release points or when specifically requested.

integrity evidence.

artifacts, never by roadmap milestone text.

Milestone 0: Source Of Truth And Parity Ledger

Status: blocked-source-missing after source ledger generation.

Goal: establish an auditable source baseline for lang, libs, index, and

kukulkan, then convert every required behavior into a row-level parity ledger.

Submilestones:

and /home/n0um3n4/repositories/kukulkan with commit SHA, dirty-state

summary, file inventory, command inventory, release artifact inventory, public

website inventory, and operational evidence inventory.

deleted intentionally, recover the last authoritative source from version

control, backups, registry publication artifacts, or release archives.

static websites, deployment, and release operations. Every row must name the

old source, expected 0x0 source, production command, tests, docs, release

artifact, and owner gate.

constructor-only, checker-owned, fixture-only, shim-owned, or obsolete.

tests, docs, release artifacts, and ADR/RFC evidence.

ledger reference.

Acceptance:

checked into the parity evidence area.

language wording.

Current evidence:

Milestone 1: Governance, Evidence, And Anti-Placeholder Gates

Status: evidence-gated.

Goal: make it impossible for fake production behavior to pass release gates.

Submilestones:

target path, execution command, positive tests, negative tests, release

artifact, public documentation, ADR, RFC, and static-site publication evidence.

fixed-response routes, checker-owned behavior, Python release shims, and

roadmap-derived evidence.

helper-only or checker-only logic.

artifact that produced each shipped command.

CLI, compiler, runtime, standard-library, or behavior change.

release checks without running broad session-breaking commands by default.

Acceptance:

implementation cannot be marked production-ready.

Current evidence:

Milestone 2: lang Language And Runtime Parity

Status: done.

Closure basis: current 0x0 language and runtime parity is closed for behavior

that runs, works, and has bounded tests. Remaining library, app, public-site,

and final-release parity blockers stay tracked by Milestones 5 through 9.

Goal: close every behavior 0x0 still misses from jmp0x1b/lang as real source,

runtime, compiler, docs, and release behavior.

Submilestones:

generic tau forms such as tau Option[a], ↯ effects, imports, packages,

actor declarations, protocol/session syntax, typestate assertions, and

*.html.0x0 templates.

polymorphism, effect handlers, protocol/session checking, typestate-style

assurance, imported-module signatures, and stable diagnostics.

and release artifact paths. The same supported source corpus must lower

through every production backend or fail with documented diagnostics.

WASM execution, model checks, sandboxing, mission IO, industrial IO, and

space-assurance commands.

runtime parity with production schedulers, failure behavior, replay logs,

supervision trees, node identity, transport, and negative security tests.

references, compiler/runtime references, diagnostics, source examples, and

website publication.

Acceptance:

of roadmap text.

0x0 source.

Current evidence:

Milestone 3: ABI, Runtime Layout, And Dynamic Value Parity

Status: pending.

Pending reason: ABI runtime descriptor rows and the bounded schema gate are in

place, but cross-backend ABI invalid-layout, ownership, stale-handle,

descriptor leak, and incompatible artifact tests remain before closure.

Goal: make all runtime values used by language, library, Index, and Kukulkan

features stable enough for production artifacts and cross-backend execution.

Submilestones:

runtime values, process handles, socket handles, runtime errors, and hardware

evidence values.

behavior for every new value family.

native, VM, WASM, object, archive, and linked outputs where those outputs

support the feature.

recursive context errors, stale handles, leaked descriptors, and incompatible

artifact versions.

compatibility, and support-matrix docs.

Acceptance:

value.

conventions for production APIs.

Current evidence:

Milestone 4: Embedded, Hardware, HAL, RTOS/BSP, And Assurance Parity

Status: pending.

Pending reason: bounded Milestone 4 evidence and gates exist, but physical

board claims remain fail-closed and external certification remains external.

Goal: make the embedded and hardware-oriented 0x0 surface real source and

release behavior, with emulation accepted only where physical evidence is not

yet available.

Submilestones:

MCU and bare-metal targets.

run against emulated or virtualized targets.

boundaries, memory regions, and failure handling.

rollback, and verification fixtures.

ingestion that fails closed when real evidence is absent.

source artifacts, including traceability from requirement to test to release

artifact.

Acceptance:

faked by a static text row.

external certification status.

Current evidence:

Milestone 5: libs Full Library Parity And Registry Production

Status: blocked-source-missing.

Blockers: blocked-source-missing because /home/n0um3n4/repositories/libs

is absent, and registry-name-collision because current compatibility packages

still collide on some public aliases. Old-library full parity cannot be closed.

Current 0x0 library registry production evidence is tracked by the Milestone 5

gate while those blockers remain.

Goal: make the current 0x0 libraries fully equivalent to the recovered

/home/n0um3n4/repositories/libs source and publish them as the active

production library registry.

Submilestones:

function, data type, test, README, and registry inventories.

name, compatibility aliases, public API, examples, behavior tests, and

deprecation state.

library must compile, test, document, and publish independently.

behavior that existed in the old libraries.

solving, provenance, signatures, yanking, rollback, namespace ownership, and

package publication workflow.

package pages sourced from standalone READMEs and generated API docs.

Acceptance:

README, or registry row.

local-only fixture path.

Current evidence:

Milestone 6: Index Full Production Rewrite

Status: blocked-unresolved-gaps.

Blockers: unresolved-index-gap because apps/real-rewrite-gap.tsv still has

Index rows that are not production-ready, and index-runtime-gate-failure

because current Index runtime gates expose a local-effects timeout and CLI

corpus mismatch. Current 0x0 Index source and release evidence is tracked by

the Milestone 6 gate while those rows remain.

Goal: replace /home/n0um3n4/repositories/index with a real 0x0 production

implementation that preserves user-visible behavior, release artifacts, and

operations.

Submilestones:

document model, extractors, rendering, terminal UI, file flows, browser flows,

network flows, auth/session assist, adapters, compatibility packs, IDX

protocol, release packaging, shell integrations, and operations.

implementations under apps/index/src.

verify app behavior, not contain the behavior.

extraction, rendering, capture, network, browser, auth, and package behavior.

and package artifacts from the 0x0 build path.

corpus, including negative tests for malformed input, unsafe paths, network

failures, auth failures, and corrupt package data.

obsolete migration wording.

Acceptance:

fixture-only, fixed-response, or shim-owned.

the old Index acceptance corpus.

Current evidence:

Milestone 7: Kukulkan Full Production Rewrite

Status: blocked-unresolved-gaps.

Blocker: unresolved-kukulkan-gap because apps/real-rewrite-gap.tsv still

has Kukulkan rows that are not production-ready. Current 0x0 Kukulkan package,

API, UI, integration, deployment, and release evidence is tracked by the

Milestone 7 gate while those rows remain.

Goal: replace /home/n0um3n4/repositories/kukulkan with a real 0x0 production

implementation that preserves API, UI, deployment, release, and operations

behavior.

Submilestones:

shared packages, API boot/config, routing, responses, auth, RBAC, sessions,

database workflows, geospatial workflows, compliance workflows, service

adapters, observability, UI templates, Live runtime, browser flows, deployment,

rollback, and operations.

0x0 implementations.

shaping, auth, authorization, sessions, idempotency, database-backed

workflows, and service adapter failures.

Live runtime APIs, browser integration, accessibility checks, and load tests.

cluster paths, SQL/runtime identity provider registry, environment handling,

rollback, backup, restore, and operational probes.

tooling and runtime-backed adapters.

corpus, including negative tests for auth bypass, data corruption, retry

behavior, service failure, browser failure, and deployment rollback failure.

smoke, browser, API, and rollback evidence.

Acceptance:

fixture-only, fixed-response, Python-shim, or checker-owned.

API, UI, browser, deployment, rollback, and operations gates.

Current evidence:

Milestone 8: Websites, Registry, Deployment, And Public Operations

Status: current-static-ops.

Current state: current-static-ops with app-ops-blocked for app-specific

public operations. Static website, registry, redirect, search,

rollback, deployment report, and post-commit 0x0 redeploy evidence exists, but

Index and Kukulkan public app operations cannot be final until Milestones 6 and

7 close.

Goal: make the public websites and deployment operations match the final 0x0

production state with no stale migration or obsolete-source language.

Submilestones:

including roadmap, language, runtime, compiler, library, app, release, and

operations pages.

standalone package docs.

as the active language/runtime and does not advertise obsolete language work.

artifacts.

evidence for all public sites.

and app deployment.

Acceptance:

instructions, or unsupported production claims.

Current evidence:

Milestone 9: Integrated Production Release And Final Parity Gate

Status: active.

Current state: blocked-prerequisites. The integrated release gate is wired,

but final parity release execution is blocked by Milestone 5

blocked-source-missing and registry-name-collision, Milestone 6

unresolved-index-gap and index-runtime-gate-failure, and Milestone 7

unresolved-kukulkan-gap. Heavy release, ecosystem, and self-host gates must

not be treated as release evidence until those blockers close.

Goal: produce one integrated release where 0x0 has full parity with lang,

recovered libs, Index, and Kukulkan.

Existing final release discipline is governed by ADR-0010/RFC-0010 and remains

part of the full parity release gate.

Submilestones:

app, docs, website, deployment, and release gates.

in a session-safe order with logs and resource measurements.

registry, release bundles, hashes, SBOM/provenance, and deployment artifacts.

Kukulkan against the new 0x0 artifacts.

migration-only docs, fake adapters, fixture-only production paths, and

obsolete public references.

operational docs, and static websites from the final source state.

release documentation.

Acceptance:

websites, registry, deployment, and release operations is closed by production

evidence.

source repositories in the normal path.

registry pages, and deployed sites all describe the same production behavior.

constructor-only, checker-owned, or shim-owned production claims.

Current evidence:

Gate Inventory

This list is not a substitute for the parity ledgers. It names the current

bounded and final gates that must be kept aligned as the roadmap is implemented.


make adr-rfc-check
make documentation-impact-check
make type-system-check
make runtime-depth-closure-check
make abi-layout-check
make abi-v1-layout-check
make backend-coverage-check
make backend-parity-closure-check
make embedded-distributed-support-check
make actor-runtime-check
make distributed-cluster-check
make live-runtime-check
make embedded-hardware-check
make physical-hardware-evidence-check
make certification-evidence-check
make libs-check
make libs-standalone-check
make libs-compile-check
make package-check
make package-registry-check
make apps-real-rewrite-gap-check
make index-full-check
make kukulkan-production-check
make app-runtime-revalidation-check
make public-site-build-check
make static-site-0x0-redeploy-check
make final-release-discipline-check
make release-verify
make ecosystem-check
make selfhost-guard