Registers
| Status: |
Draft |
| Source file: |
06 Evidence Register; 02 Secondary Research/Source Log; program opportunity validation working set |
| Sensitivity review: |
Completed |
| Purpose: |
Provide a reader-friendly entry point to the project registers published through the controlled MkDocs layer. |
Registers support traceability. They help readers see where evidence, source references and product-pathway classifications are recorded without publishing private contact details, raw interview notes or commercially sensitive material.
What To Read Here
| Register |
Use it for |
| Source Register |
Reader-facing source list for Source IDs cited across published research pages. |
| Claim And Data Extracts |
Pilot source-level claim and data extract page using sub-IDs such as S001-001, with links back to where each item is used. |
| Product Pathway Register |
Current classification of industrial hemp product pathways, confidence levels and evidence thresholds. |
Register Rules
| Rule |
Why it matters |
| Keep source traceability |
Significant claims should be traceable to a source, evidence record or explicit uncertainty statement. |
| Use claim/data sub-IDs where helpful |
Priority source claims and data points can be given stable sub-IDs such as S001-001 so reviewers can see what was taken from each source and where it was used. |
| Separate product pathways |
Seed, food, oil, fibre, hurd, bedding, building-material and excluded cannabinoid pathways have different markets, risks and evidence needs. |
| Protect sensitive material |
Raw notes, personal contact details and commercially sensitive information must remain outside the publishing layer. |
| Preserve uncertainty |
Registers should show confidence, evidence strength and follow-up needs rather than implying conclusions are settled. |
The working registers outside docs/ remain the authoritative internal records. Published registers are reviewed derivatives for navigation, transparency and reader reference.