Entry Gate
Resolve cross-functional language and rules only when the ambiguity spans owners or lifecycle boundaries. Require an identified fact source and scope; do not invent product decisions or technical design.
Route Map
| Request condition | Read | Result |
|---|---|---|
| Shared terms, invariants, or context boundaries conflict | modeling guide | Named glossary/context/rule facts |
| A feature-local behavior or acceptance is unresolved | usage | Route to product-spec |
| Need examples and nearest boundaries | usage | Owner decision |
Invariants
- Keep facts, assumptions, unresolved questions, and implementation choices distinct.
- Preserve the source authority and evidence level for each conclusion.
- Do not write a competing product/UI/design contract, source change, review, or Git result.
Output Map
Return the named fact source, terms/rules/context boundaries, source basis, unresolved ambiguities, affected owners, and next semantic handoff.
Reference Map
- Read modeling guide for context, lifecycle, rule, and validation procedures.
- Read usage for mode selection and boundaries.
- Maintainers only: read eval cases; do not load it during ordinary runtime.