Research & Evidence · Source Governance
Source Hierarchy Designer
Decide which sources govern a project, which merely inform it, and what happens when they disagree.
ORIGINAL BY ZAIN HASEEB · 1.0.0 · DEVELOPED FROM STRAITEGY HUB AUDIENCE AND OPERATING FRAMEWORKS WITH AI-ASSISTED DRAFTING.
Copy-ready prompt
Design a source hierarchy for this project so an AI or team member does not silently choose whichever document is easiest to find.
PROJECT: {{PROJECT}}
AVAILABLE SOURCES: {{SOURCES}}
KNOWN OWNERS: {{OWNERS}}
FRESHNESS OR VERSION INFORMATION: {{DATES_AND_VERSIONS}}
KNOWN CONFLICTS: {{CONFLICTS}}
PUBLIC, PRIVATE, OR LICENSED BOUNDARIES: {{RIGHTS}}
Classify each source as governing, authoritative for one domain, supporting evidence, historical context, example only, or superseded. For every source, record owner, scope, effective date, rights boundary, and what it cannot decide.
Create explicit conflict rules: newer versus approved, policy versus example, public versus private, and owner judgment versus automated inference. Do not resolve a material conflict without authority. End with a compact source register, a citation rule, a freshness review cadence, and a preflight checklist that a future agent must run before changing the project.