seedlisted

# X2 Seed Copy the kernel down, initialise it to the product, and anchor the method in the repo. Seeding runs right after gate 1 so the repo exists before any decision work: D-000, the behaviour spec, and the prototype import all need a home, and the standing constraints and ledger must be repo-anchored from the first turn. The pilot instantiated late and the missing scaffolding cost roughly a quarter of all measured turns (INV-03); its pasted-prompt constraints decayed under compaction into 55 violations (MET-08). Seed exists so neither happens again. ## Steps 1. **Create the repo.** A new sibling repo named for the product, decided at ideation. 2. **Instantiate the edition per its manifest.** The edition README's "Instantiation manifest" section is the definition: the file set (A), the ordered setup steps (B), and the verify-as-a-set list (C). Run all three parts and verify part C as a set, not one by one from memory. The manifest's contents are the kernel's to define; this skill runs it and does not restate it. Two points the record proved sharp: - Renaming Kernel to the product includes config values, not only code identifiers (the pilot shipped an issuer still named "kernel"). - The CI workflow moving to the repo root is not the gate. Branch protection requiring it is, and it must be verified armed, not assumed (TEST-3's one honest asterisk). The same arming step covers HUM-1: code-owner review required, with `@OWNER` in CODEOWNERS ren