Entry Gate
Own current product facts and acceptance, not implementation architecture or visual semantics. Require a named product authority or authorized artifact target; resolve only decisions needed for the requested slice.
Route Map
| Request condition | Read | Result |
|---|---|---|
| One feature needs behavior, states, and acceptance | workflow and template | Progressive Feature Spec |
| New product line/boundary reset is explicit | workflow | Foundation Spec |
| Confirmed changes update a named fact source | documentation boundaries | Bounded artifact update |
| A material product decision needs challenge | decision pressure test | Decision disposition |
| Prototype evidence is decisive | prototype evidence | Qualified product facts |
Invariants
- Do not infer behavior from UI appearance, source, or tests when product authority is absent.
- Keep product behavior separate from shared visual semantics, technical design, implementation, and runtime proof.
- Stop each slice at its Ready gate; unknowns remain named, not silently decided.
Output Map
Return the one applicable current product artifact, source basis, decisions/states, acceptance, non-goals, unresolved questions, and next owner.
Reference Map
- Read workflow for Feature/Foundation/update procedure and gates.
- Read template when creating an artifact.
- Read documentation boundaries for authority and placement.
- Read prototype evidence only when prototype evidence applies.
- Read decision pressure test only for a material decision challenge.
- Read usage for public modes and nearest owners.
- Maintainers only: read eval cases; do not load it during ordinary runtime.