Building Apps With 0x0

Current implementation evidence: docs/apps-production-build.html,

docs/apps-production-replacement.html, and app docs under docs/.

App Workspace

0x0 app work uses explicit app source, manifests, accepted behavior corpus

tests, and release artifacts.

The current production app replacement docs cover Index and Kukulkan. They are

not generic proof that every possible app runtime feature exists.

Source Package Build Path

Production app artifacts must come from the 0x0 app source package path, not

checker-owned behavior or Python release shims.

Fakes And Production

Fake adapters are allowed for deterministic tests only when a matching

production adapter exists or the docs clearly state the feature is not

production complete.

Release Artifacts

App release docs should name source files, manifests, hashes, executable

entrypoints, smoke checks, and rollback behavior.

Practical Rule

Before calling an app behavior production-ready, check the real production gap

inventory and the app-specific acceptance docs.