beo-reference

Canonical lookup router: references/doctrine-map.md.

Read

• The user's BEO rule, schema, transition, command authority, or safety lookup request.
• references/doctrine-map.md first to choose the narrowest source.
• references/kernel.md when authority, lifecycle, safety, closure, or invariant questions are involved.
• The narrow registry, schema, template, script contract, or reference file needed for the lookup.

Do

• Answer from canonical BEO references and registries.
• Prefer registries for machine-readable contracts.
• Prefer references for rationale and operating guidance.
• Cite exact file paths or section names.
• State clearly when an answer is advisory rather than approval-bearing.
• Use this lookup shape when practical: Answer; Canonical source; Authority status (binding or advisory); Related caveat.