← ClaudeAtlas

domain-evidence-disciplinelisted

Evidence discipline for non-code deliverables — marketing copy, research reports, data analyses, business/ops documents. Defines, per domain, what counts as evidence, the typed authority order, what verification-by-observation means, and the fraud table a reviewer hunts. Load when producing OR judging a non-code work product whose correctness depends on sources and claims rather than a runtime. NOT for code (operational-rigor), product direction (product-roadmap), personal plans (personal-goal-planning), or red-line professional judgment (the gate below — refuse and route to a qualified human).
F-e-u-e-r/opus-pack · ★ 2 · AI & Automation · score 75
Install: claude install-skill F-e-u-e-r/opus-pack
# Domain Evidence Discipline This skill's evidence-control loop stays constant across domains; only the nouns change. For any non-code deliverable, name the four nouns BEFORE producing anything — in your working notes or the report, where a reviewer can see them — and hunt the same four afterward. Under this skill, a deliverable whose four nouns were never named is incomplete and unauditable. **Red-line gate — run before anything below.** Where the deliverable would substitute for individualized, materially high-stakes professional or regulated judgment — a medical/clinical decision, legal advice, a buy/sell financial call, mental-health treatment, safety-critical engineering sign-off — refuse the deliverable and route to a qualified human: an evidence checklist supplies structure, never the judgment, and its presence invites trust it cannot back. General work that merely touches money or health (a budgeting spreadsheet, fitness copy) is not red-line; the line is substituting for the professional's individualized call. Adjacent work that is not substitution (compliance research, tooling for practitioners) may be drafted under the matching instance, labeled as not the professional's individualized call — and when the user would reasonably treat it as professional work-product, it ships only with a qualified human's review; unreviewed, it stays a labeled draft. This is the execution-side sibling of skill-authoring §5's authoring gate (that rule stops the checklist being WRITT