JM Sovereign Coding Estate

Ask once. Route properly.

Describe the game, tool, language or OS behaviour. The estate selects bodies, then adds trace, Ding and source authority.

Search by name, family, capability or job. Aliases remain aliases; no body is crowned supreme.

All declared direct links, adapter requirements and forbidden collapse laws. A route declaration does not equal device proof.

Three routes that execute existing sovereign bodies together.

Game proof WIRED

GameForge → PLAYFORM → Seedform → Pattern-Tapping → Visual Graft → Interaction Runtime.

FOURFOLD integration route

Tool proof WIRED

Parser → Compiler → OneBody IR → JS Emitter → compileCading API.

Cading compile API route

Estate OS proof WIRED

RouteCore Native → OS_CODING → CodeHand RouteOS → Choice Box.

SovereignWorld route

Conformance CI GATED

Registry, router, compatibility, documentation and all three executable proofs.

integration-selftest.mjs

The technical integration can pass while this gate remains deliberately red.

The connected repository reports public visibility, conflicting with the private-estate law.

Change repository visibility in GitHub settings or separate private estate source from deliberate public releases.

Release law

Private estate source → deliberate release gate → public delivery body.