0x0 Migration Policy

This policy governs public migration from jmp0x1b/lang and jmp0x1b/libs to

0x0.

Current Language Path

0x0 is the current path for new language work. jmp0x1b/lang is historical

context and migration input.

Truth Rule

An old feature may be documented as current 0x0 behavior only when this

repository has matching source, tests, docs, and safe gates.

If matching evidence does not exist, document the feature as:

• deferred;
• app-specific;
• fake-adapter-only;
• partial;
• obsolete;
• unsupported.

Syntax Migration

.jmp0x1b syntax must be translated to implemented .0x0 syntax. Do not copy

old syntax into public 0x0 examples unless the current parser accepts it.

Package Migration

Old library names are migration inputs. The public registry must assign each old

name one of:

• preserved compatibility id;
• 0x0-native alias;
• deprecated package with tombstone;
• hidden/deferred package.

No silent renames are allowed.

Embedded Migration

Embedded and hardware docs are deferred. They may be linked as archive context

but must not appear in current 0x0 feature sections.

Domain Migration

Planned public behavior:

• 0x0.jmp0x1b.com: current docs;
• lang.jmp0x1b.com: archive and successor notice;
• libs.jmp0x1b.com: 0x0 library registry;
• jmp0x1b.com: top-level path to 0x0.

Remote changes require dry run, manifest, rollback, and smoke evidence.