PhysicsGenesis migration plan

Phase 0 — Design review

• Review schemas, partitions, status ladder, safety rules, and target layout.
• Approve native IDs and registry ownership.
• Confirm no new task is added to generic Forge LCDL unless it satisfies the cross-domain promotion rule.

Phase 1 — Compatibility ingestion

• Add native schemas under schemas/physicsgenesis/.
• Wrap the first reference objects in current knowledge modules.
• Add source, quantity, unit, and object registries.
• Validate examples and invalid fixtures in CI.

Phase 2 — Runtime packs

• Implement quantity normalization, model formalization, experiment design, simulation assessment, validation, and safety contracts.
• Add LMeta units, policies, fixtures, catalog entries, maturity rows, and allowlist entries.
• Preserve artifact-envelope and session dual-wiki behavior.

Phase 3 — Native storage

• Introduce partition-scoped native object retrieval.
• Add learner/historian credential separation and retrieval traces.
• Migrate consumers from compatibility wrappers.

Phase 4 — Physica-0

• Freeze seed, worlds, prompts, learner model, evaluators, and hidden target map.
• Run bounded generations with falsification, validation, safety, contamination, and human promotion gates.
• Keep historian comparison post-freeze and isolated.

Phase 5 — Training and open exploration

• Generate training/replay records only from policy-eligible frozen artifacts.
• Expand domains and worlds gradually.
• Move from known-concept rediscovery to bounded open law, model, experiment, and algorithm discovery in easy-to-verify domains.