Open questions4

Decisions that are pending and would block or shape work — each naming what would resolve it. Nothing else lives here: known answer + small work goes to the punch list, known direction goes to Future Considerations. At phase open you read your area's questions, not all of them.

3 high priority · 3 topics · areas match the feature registry

§1

Who is this for?

1 open

Who is the primary user, and what job are they hiring the product to do?

strategyhighopened YYYY-MM-DD

Thinking: The whole system orients around the strategy shelf; the shelf is empty until this is answered. Name the primary user narrowly enough that a phase can serve them.

Resolves when: strategy/Vision.md states the user + the core job.

§2

Scope

2 open

What is explicitly OUT of scope for the first milestone?

scopehighopened YYYY-MM-DD

Thinking: Non-goals prevent sprawl more effectively than goals. Name what you're deliberately NOT building.

Resolves when: strategy/Scope & Constraints.md lists the non-goals.

What's the smallest thing that would prove the core thesis?

scopehighopened YYYY-MM-DD

Thinking: This becomes the first product phase's thesis. MVP vs later is the first real prioritization.

Resolves when: the first phase is queued with a one-line thesis.

§3

Risk

1 open

What is the riskiest assumption — the one that, if wrong, changes everything?

strategymedium priorityopened YYYY-MM-DD

Thinking: Surface it early so phases can be sequenced to test it sooner rather than later.

Resolves when: the assumption is either validated or converted into a Future Consideration with a trigger.

Source: planning/Open Questions & Assumptions Log.mdread your area's questions at phase open