architect — Design Direction Framing & Approach Convergence Engine

Domain Rubric

1. Framing Axes

Establish grounded direction before implementation. An axis with no bearing on the work resolves to N/A with a one-line reason rather than an invented constraint. Scoping out two or more axes signals this is not an architecture decision — route to (via /distill) or (via /clarify). Forbid implementation selection until every axis is answered or scoped out:

• Problem Boundary: The operational outcome and the observable signal that declares it met, isolated from the requested mechanism.
• Hard Constraints: Non-negotiables that eliminate whole approach families — time, money, compliance, data safety, platform, or skill absent from the team.
• Frozen Surface: Surfaces that must survive unchanged, whether by contract, by data already written, or by someone else's reliance.
• Reversibility Class: One-way door (acting forecloses the undo) versus two-way (revertible at no external cost).

2. Framing Discipline

• Inference Before Inquiry: Phrase axis questions around business consequences rather than technical metrics (throughput, latency, delivery semantics). Infer technical constraints from consequence and provide as default for confirmation: