Target layout inside forge-intelligence

The handbook site is a derived static surface. Apply this pack to the forge-intelligence product repository, then rebuild the separate handbook shell.

Recommended native layout

forge-intelligence/
├── knowledge/
│   └── math/
│       ├── registry.yaml
│       ├── dependencies.json
│       ├── symbol_registry.yaml
│       ├── source_registry.yaml
│       ├── snapshots/
│       └── objects/
│           ├── reference/
│           │   ├── math/
│           │   ├── geometry/
│           │   └── physics/
│           ├── learner_seed/
│           ├── curriculum/
│           ├── discovery_staging/
│           ├── promoted_discovery/
│           └── rejected/
├── packs/
│   ├── math/knowledge-ingest/
│   ├── math/problem-formalize/
│   ├── math/concept-mine/
│   ├── math/concept-promote/
│   ├── math/curriculum-evolve/
│   ├── geometry/solve-verify/
│   └── physics/model-test/
├── lmeta/
│   ├── library/math/
│   └── units/math/
├── lcdl/contracts/
│   ├── intelligence_math_knowledge_ingest_v1/
│   ├── intelligence_math_candidate_validate_v1/
│   ├── intelligence_math_concept_promote_v1/
│   └── intelligence_physics_model_assess_v1/
├── schemas/mathgenesis/
├── registries/
│   ├── math_object_index.json
│   ├── math_partition_policy.yaml
│   └── math_snapshot_registry.yaml
├── wiki/
│   ├── semantic/math-*.md
│   └── execution/math-*.md
├── docs/mathgenesis/
└── sessions/<session_id>/

Existing-surface integration

Pack catalog

Add problem classes to packs/catalog.yaml. Keep each break-in action closed and each LLM input bounded.

Capability identity

Maintain the Forge Intelligence identity rule:

1 capability ↔ 1 LMeta unit ↔ 1 FI-local LCDL contract ↔ declared artifacts

Artifact bus

Wrap batches and individual outputs in the existing artifact envelope. Machine artifacts remain canonical; generated Markdown is a derived projection.

Maturity

Start new capabilities at I0_scaffold/A0_assisted. Move to I1_runtime only after schema-valid contracts, runtime tests, allowlist entry, and golden fixtures exist. Mathematical truth or physical validity requires additional semantic evidence and must not be inferred from envelope execution.

Handbook

Add narrative pages under docs/mathgenesis/ and paired semantic/execution wiki pages. Rebuild forge-intelligence-website; do not hand-edit generated HTML.

Compatibility rollout

A low-risk first step is:

1. Keep the current knowledge-module.schema.json unchanged.
2. Store native MathGenesis objects inside the compatibility wrapper’s formulas array.
3. Add schemas/mathgenesis/ and validate native objects separately.
4. Add the native registry after a first audited batch.
5. Migrate module consumers to direct native-object retrieval.

This preserves existing consumers while avoiding permanent dependence on the shallow compatibility representation.