PBS Decisions
This directory contains PBS decision records.
Purpose
A decision record is the bridge between agenda discussion and normative spec text.
Use this directory to capture:
- what was decided,
- why that direction was chosen,
- which constraints now apply,
- what remains intentionally out of scope,
- which specs must be updated.
Architecture and decisions must be resolved before implementation.
Expected Format
A decision record should usually include:
- Title
- Status
- Date or Cycle
- Context
- Decision
- Invariants
- Explicit Non-Decisions
- Spec Impact
- Validation Notes or Examples
Writing Rules
- Write in stable, reviewable language.
- State the adopted decision first and clearly.
- Capture architectural constraints and invariants explicitly.
- Record what is still not decided so later implementation does not guess.
- Point to the exact specs that need integration.
Implementation Rule
If implementation work exposes a missing decision, do not infer it. Stop, surface the ambiguity, and return it to agenda or decision review.