Beacon Guardrails¶
Why This Exists¶
This document defines operating guardrails for Beacon.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Guardrail Catalogue¶
| Guardrail | Requirement |
|---|---|
| Source ownership | Domains own facts. Beacon must not become a source-of-truth owner. |
| Practice scope | Beacon must operate within Funding capabilities. |
| Human approval | High-impact actions require human approval. |
| Memory control | Memory cannot override current domain state. |
| Tool control | Tools must be approved, scoped, and auditable. |
| Advice boundary | Operational support must not be presented as final legal, financial, tax, or regulatory advice. |
| Escalation | Uncertainty, conflict, or high risk must be escalated. |
Human Approval Boundary¶
Beacon must escalate: accepting funding, signing agreements, regulated financial decisions, repayment commitments, and final partner selection.