Domain Evidence Discipline

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 Updated 2 repo stars

File contents

F-e-u-e-r/opus-pack commit cb8de74054

Frequently asked questions

npx get-skill add f-e-u-e-r/domain-evidence-discipline