- Decision ID: ABYSS-STACK-D-NNNN
- Status: proposed
- Date: YYYY-MM-DD
- Owner surface:
path/or/surface
- Original date: YYYY-MM-DD
- Surface classes: root/topology
- Stack lanes: decision lane
- Mechanic parents: none
- Guard families: none
- Posture: proposed rationale
What problem, drift, topology pressure, validation failure, workflow need, or owner-boundary question made this decision necessary?
- Option A:
- Option B:
- Option C:
State the chosen route in present-tense language.
Why does this route preserve runtime clarity, owner boundaries, reviewability, public-safe source shape, and future repair better than the alternatives?
- Positive:
- Tradeoff:
- Follow-up:
path/to/source.md
Name the next owner, validator, or future condition that should revisit this decision.