Reference Map
Use the authority that matches the fact. Record its verification revision when the fact can change.
State the fact to verify. Classify its authority type as behavior, procedure, command, learning, delivery, service operation, or licensing.
This reference map covers source selection. It does not replace the selected source or define a new rule.
Authority
Section titled “Authority”Use the Beskid Standard for required language and tool behavior. Use task Docs for current procedures. Use the Book for learning sequence and rationale. Use Tracker for delivery status. Use Licensing for component terms.
| Information | Canonical source |
|---|---|
| Required behavior | OpenSpec and the public Standard. |
| Current procedure | Technical Docs. |
| Command syntax | Pinned CLI evidence and the command reference. |
| Learning rationale | The Beskid Book. |
| Delivery status | Tracker and release metadata. |
| Service operation | Service and infrastructure contracts. |
| License boundary | LICENSING.md and local license declarations. |
Use one canonical source and record its verification revision. An informative page links to the authority instead of duplicating its rule.
Report a mismatch
Section titled “Report a mismatch”If two sources conflict, do not infer a new rule. Use Report a bug to record both source URLs, both revisions, and the conflicting statements. Use an OpenSpec change only when normative reconciliation changes observable behavior.