Migrating From jmp0x1b/lang

Current implementation evidence: docs/public-docs-gap.html,

docs/public-docs-source-map.tsv, site/redirects.tsv, and site/migration.html.

Replacement Status

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

archive context.

Command Mapping

The full command map lands in Milestone 7. Until then:

• use 0x0 repository commands for new work;
• use safe public docs gates for site work;
• do not use old jmp0x1b commands as current 0x0 instructions.

Syntax Mapping

0x0 uses .0x0 files and the syntax documented in docs/language.html.

Old jmp0x1b/lang syntax should be translated only when the target 0x0 syntax

is implemented. Unsupported syntax must be marked unsupported or deferred.

Package Mapping

The library migration is local in the repository today. Public registry

metadata, aliases, deprecations, and old-registry unregistration land in

Milestone 6.

Unsupported And Deferred Features

Embedded and hardware-oriented features are deferred. Actors, supervision,

replay, distributed execution, and generic LiveView-style behavior also require

current 0x0 evidence before they can be documented as current generic features.

Domain Mapping

Planned public behavior:

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