human-merge

# /human-merge **Many reports in, one decidable surface out.** Each input may be excellent. The pile is still undecidable, because the reader cannot tell which claims are corroborated, which rest on one source wearing four hats, and which two reports quietly disagree. > **The complete style layer lives in `human-output` when that skill is > installed.** Otherwise apply the portable style floor, stopping-point rule, > and checker contract in > [`references/human-contract.md`](references/human-contract.md). This file > carries only what exists *because there is more than one report*. ## The four operations These are the whole skill. Each has no single-input analogue, which is why nobody who wrote one of the inputs could have done it. 1. **Collapse correlated reports to one source.** Reports are not sources. 2. **Name what is superseded** — and whether a live decision already rests on the dead figure. 3. **Classify each conflict** before touching it. Most are not contradictions. 4. **Pool coverage.** A hole no single report had appears only at merge time. Anything else you are tempted to add is `human-output` restated. Leave it out. ## The order the work happens The sections below are reference, not a running order. Executed top to bottom they would grade confidence before counting sources, which is the error this skill exists to prevent. Run these ten steps in order. Three of the dependencies are load-bearing and named where they bite. 1. **Inventory.** List every i...