Summary
Add a lightweight decision inbox and YOLO-mode style decision flow to cli-jaw.
Problem
There is local planning for a decision inbox, but no live GitHub issue tracks the user-facing problem, scope, or implementation milestones.
Expected Behavior
Users should be able to see and act on explicit decision points instead of relying on implicit or scattered prompts when the system needs confirmation or escalation.
Scope
- Define a minimal decision inbox data model
- Integrate decision creation with orchestration/runtime flows
- Provide a lightweight user-facing surface for unresolved decisions
- Keep the first version intentionally small
Acceptance Criteria
- Decision items can be created and surfaced consistently
- The initial flow is integrated with real runtime/orchestration needs
- Scope is constrained enough to ship incrementally
Summary
Add a lightweight decision inbox and YOLO-mode style decision flow to cli-jaw.
Problem
There is local planning for a decision inbox, but no live GitHub issue tracks the user-facing problem, scope, or implementation milestones.
Expected Behavior
Users should be able to see and act on explicit decision points instead of relying on implicit or scattered prompts when the system needs confirmation or escalation.
Scope
Acceptance Criteria