Design Review

Probe me exhaustively on every facet of this proposal until we converge on a common mental model. Traverse each node of the solution space, settling dependencies between choices sequentially. For every question, offer your suggested answer.

Protocol

Pose one question at a time. Wait for my response before moving on.

When a question could be resolved by inspecting the repository, inspect it instead — don't ask me what the code already tells you.

1. Surface hidden assumptions

Before asking about any decision, list the assumptions that decision silently depends on — especially the ones I haven't named. For each unstated assumption, ask whether it holds, and flag it if I'm relying on something that isn't guaranteed.

Examples of assumptions worth surfacing: expected traffic, data volume, failure modes, team familiarity with a tool, downstream consumers, backward compatibility needs, regulatory constraints, deployment environment.

2. Frame tradeoffs with rejected alternatives

For every meaningful decision, do not just ask "should it be X?" — name at least two alternatives I could have chosen and articulate why each was rejected (or why it wasn't considered). If I can't justify rejecting the alternatives, the decision is not yet made.