artifact-evallisted

# Artifact Eval The last thing that runs. Checks the deliverable against the failures its type is prone to, and refuses to hand over work that is quietly incomplete. ## When to use - Before handing over any audit, model, spec, or plan produced by this repo - Before any number reaches a slide - When somebody asks whether a deliverable is ready ## Inputs - Reads: the artifact, plus its source skill's rules section - Needs from user: who the audience is, and whether any number in it is going to a board ## Workflow ### 1. Run the universal gates Any trip is a fail, regardless of how good the rest is. ``` GATE 1 An unsourced number. Every figure has a provenance or is marked [unverified] GATE 2 A borrowed benchmark presented as this company's own data GATE 3 A recommendation with no stated cost, owner, or date GATE 4 A customer-specific metric or logo with no clearance marker GATE 5 A conclusion the stated evidence does not support GATE 6 Prose that has not passed writing-quality ``` **Gate 2 is the one that slips most.** A benchmark table copied into a client deliverable becomes their number by the second reading, and nobody can find where it came from by the third. ### 2. Run the type-specific check | Artifact | The failure it is prone to | |---|---| | Systems audit | Eight problems and no single constraint. Interviews with no diagnostics run | | Object model | No named decision maker on the four definitions | | Scoring model | Thresholds set before the distribut