Target layout inside forge-intelligence

forge-intelligence/
├── knowledge/
│   └── physics/
│       ├── registry.yaml
│       ├── dependencies.json
│       ├── quantity_registry.yaml
│       ├── unit_registry.yaml
│       ├── source_registry.yaml
│       ├── model_registry.yaml
│       ├── experiment_registry.yaml
│       ├── dataset_registry.yaml
│       ├── snapshot_registry.yaml
│       └── objects/
│           ├── reference/
│           ├── learner_seed/
│           ├── curriculum/
│           ├── discovery_staging/
│           ├── promoted_discovery/
│           └── rejected/
├── packs/physics/
│   ├── knowledge-ingest/
│   ├── quantity-normalize/
│   ├── model-formalize/
│   ├── experiment-design/
│   ├── simulation-assess/
│   ├── law-discover/
│   ├── model-validate/
│   ├── curriculum-evolve/
│   ├── safety-gate/
│   └── historian-compare/
├── lmeta/
│   ├── library/physics/
│   └── units/physics/
├── lcdl/contracts/
│   ├── intelligence_physics_knowledge_ingest_v1/
│   ├── intelligence_physics_quantity_normalize_v1/
│   ├── intelligence_physics_model_formalize_v1/
│   ├── intelligence_physics_experiment_design_v1/
│   ├── intelligence_physics_simulation_assess_v1/
│   ├── intelligence_physics_candidate_validate_v1/
│   ├── intelligence_physics_safety_gate_v1/
│   └── intelligence_physics_law_promote_v1/
├── schemas/physicsgenesis/
├── registries/
│   ├── physics_object_index.json
│   ├── physics_partition_policy.yaml
│   ├── physics_snapshot_registry.yaml
│   └── physics_capability_maturity.yaml
├── wiki/
│   ├── semantic/physics-*.md
│   └── execution/physics-*.md
├── docs/physicsgenesis/
└── sessions/<session_id>/

Integration rules

• Add problem classes to packs/catalog.yaml with closed break-in actions and bounded token policy.
• Preserve the identity rule: one capability ↔ one LMeta unit ↔ one FI-local LCDL contract ↔ declared artifacts.
• Exchange only typed artifact envelopes between nodes.
• Start new capabilities at honest scaffold maturity and promote only after contracts, runtime tests, allowlist, golden fixtures, semantic validators, and review exist.
• Store machine session JSON as canonical truth; generate human reports and run the freeze gate.
• Publish narrative pages from the product repository; do not hand-edit generated handbook HTML.

Compatibility rollout

1. Keep the current generic knowledge-module schema unchanged.
2. Store native physics object references in compatibility formulas entries.
3. Validate native objects against schemas/physicsgenesis/ separately.
4. Add the native physics registry after the first audited batch.
5. Migrate consumers to partition-scoped native retrieval.