approval-evidence-packlisted

# approval-evidence-pack - **Roadmap feature:** F035 **On-disk spec:** `specs/063-approval-evidence-pack/` (dir 063 == F035; when the dir number and the F-number disagree, the roadmap F-number wins). - **Authority category:** Product Module / `artifact-writing` (the F024 enumerated declaration -- see `docs/architecture/product-modules.md`). Four of the seven readiness stages -- Mapping Ready, Semantic Model Ready, Dashboard Ready, Publish Ready -- require a NAMED-HUMAN approval the agent is constitutionally forbidden to grant for itself (Principle V; recorded in each table's `mappings/<table>/readiness-status.yaml` `approvals[]`). When such a human is asked to sign a stage gate, the evidence they need is real but SCATTERED: the per-stage readiness doc says what the gate requires; readiness-status.yaml carries the four-status state and the open blockers; the AL1 assumption ledger (surfaced from the metric contracts) may flag an unresolved judgment call; the parked-on map may show the work is blocked on a shared bottleneck. This skill is the COMPOSER that assembles those scattered, already-committed artifacts into ONE ordered PRE-approval pack for one (table, stage). It FILLS the pack; it originates no evidence and owns no truth. Every line points back at the artifact it came from; any source that is missing or unfilled is a BLOCKER, never papered over with invented content. The pack surfaces the gate's readiness picture; it never signs it. ## Boundary against neighbo