Final-form material.
Vault contains settled doctrine and recorded decisions — material intended to hold under pressure.
Orientation
How to read this surface
Vault contains final-form thinking only. Drafts, experiments, and open questions do not live here. If a doctrine or decision appears in this surface, it is considered settled.
Future work is expected to reference what exists here, not reinterpret it.
Final form
This surface contains settled doctrine only.
Vault doctrines
Authoritative references
Vault Doctrine 001 — Modus Operandi
Constitutional spine
This doctrine defines how VaultRec operates under pressure. If a future action conflicts with this Modus Operandi, the action is wrong.
Final
Governs all VaultRec work, decisions, and changes.
Unchanged after ratification.
Vault Doctrine 002 — Decision Ledger Standard
How decisions are recorded and frozen
1. What qualifies as a decision
A decision is any choice that affects scope, durability, authority, exposure, or future cost. If reversing it would require explanation, it is a decision.
2. Recording standard
All decisions must be recorded with:
- Decision statement
- Rationale
- Constraints considered
- Date and authority
3. Freezing decisions
Once recorded, a decision is considered frozen. Frozen decisions are referenced, not debated.
4. Reversals
Reversal requires explicit acknowledgement of:
- What assumption failed
- What cost the reversal introduces
- What downstream work is affected
5. Forward reference
New work must reference relevant past decisions. Ignoring the ledger is treated as regression.
Final
Prevents re-litigation and drift.
Vault Doctrine 003 — Engagement & Refusal Criteria
Scope discipline and integrity
1. Accepted work
VaultRec accepts work only when scope, authority, and outcomes are explicit and the result increases system durability.
2. Refused work
Work is refused when it introduces ambiguity, requires constant attention, or exists primarily to signal effort rather than produce outcome.
3. Refusal posture
Refusal is not rejection of the counterparty. It is preservation of system integrity.
4. Enforcement
Scope boundaries are enforced by default. Exceptions require recorded rationale and authority.
Final
Defines acceptance, refusal, and boundary enforcement.