Handbook
Prompt 16 — Forge Intelligence repository assembler
Produce a repository write plan. Do not write files and do not claim that a commit occurred.
Updated
Inputs
ASSEMBLY_MODE: {{ASSEMBLY_MODE}} # native_mathgenesis or compatibility_module
VALIDATED_BATCH: {{VALIDATED_BATCH_JSON}}
PROMOTION_DECISIONS: {{PROMOTION_DECISIONS_JSON}}
TARGET_REPOSITORY_INDEX: {{TARGET_REPOSITORY_INDEX_JSON}}
PACK_ID: {{PACK_ID}}
WRITE_POLICY: {{WRITE_POLICY_JSON}}
Task
Produce a repository write plan. Do not write files and do not claim that a commit occurred.
Native MathGenesis mode
Route objects to proposed paths such as:
knowledge/math/objects/<partition>/<domain>/<object_id>.json;knowledge/math/registry.yaml;knowledge/math/dependencies.json;packs/<problem-class>/policy.yaml;packs/<problem-class>/flows/*.lmeta;packs/<problem-class>/fixtures/*.json;wiki/semantic/<intelligence>.md;wiki/execution/<intelligence>.md.
Compatibility mode
Wrap validated objects in a schema-valid existing knowledge-module document. Keep the native object unchanged inside the wrapper and identify the native schema version. Use:
jurisdiction: formal-universalfor pure mathematics;jurisdiction: geometry/<axiomatic-context>for geometry when context matters;jurisdiction: physical-model/<regime>for physics.
Required checks
- Never include an object whose promotion or validation status is incompatible with the destination partition.
- Never expose historian-only aliases, solutions, or target labels in learner-visible paths.
- Resolve ID collisions through a proposed new ID or semantic version; never overwrite changed meaning silently.
- Preserve source snapshots, checksums, artifact provenance, dependency IDs, assumptions, and validation receipts.
- Update registries atomically in the write plan.
- Identify generated human-wiki pages as derived; machine objects remain canonical.
- Include expected validator commands and rollback steps.
- For every file, provide
path,operation,content,content_type,depends_on, andvalidation_commands. - Mark any uncertain path or unavailable target content as a blocker rather than guessing.
Output
Return JSON matching schemas/repository-write-plan.schema.json.