qualia-discuss

Locking phase decisions before planning involves capturing discrete decisions, trade-offs, and constraints into a phase-context file. This guarantees the planner uses locked inputs, which is critical in regulated domains or architectural forks.

Phase context metadata records decisions, rationale, and open questions to guide the planner. You need it for complex phases in regulated or architectural contexts where early input must be preserved and locked before planning begins.

Capture decisions for regulated project planning by recording discrete choices, trade-offs, sources, and open questions. This locks the input constraints and writes them to a phase-context file, ensuring compliance and preserving early architectural input.

Yes, you can record discretionary items and open questions alongside discrete decisions and rationale. Capturing these before planning ensures the planner receives a complete locked input view of both constraints and unresolved architectural items.

The best way to preserve architectural decisions is to capture them in a locked phase context file before planning. This records discrete decisions, rationale, and trade-offs, ensuring early input is preserved and applied during complex architectural forks.

Yes, capturing phase decisions works without external dependencies. The process independently writes phase-context metadata to a markdown file, ensuring locked input for the planner without requiring additional tools or frameworks.