os-control-intake

Work Intake (os-control-intake)

Critical intake gateway for discovery, interview clarification, and four-pillar specification authoring before implementation.

Contents

• Critical Constraints
• Quick start
• Workflow
• Verification
• References

Critical Constraints

1. Confirm Approver Identity First: Real work lives in context/control_plane.db where only the human operator's signing key approves; simulation runs in simulation_control_plane.db with agent test identity (test-human@local).
2. Read Guidance & DB First: Read transition_templates.yaml, transition-guidance, and SQLite DB first; say exactly which parts were read, never more.
3. Artifact Location & Running Ledger: Task artifacts live in docs/plans/work-tasks/<task-id>/, never plans root. Maintain a running ledger of every human directive from first message.
4. Question Budget & Chat Answers: Answer from context first; ask only ONE question per turn. Never re-ask what is recorded and never dispute the human's account. Persist chat answers via coordinate-transition --interactive (actor=human); never write interview answers as interviewer.
5. Pasteable Commands Only: Every command the human must run is complete and ready to paste, with no back-references, no vague references, and never "see above".
6. Stop on Blocked Gate: On blocked gate, STOP and state cause and cost; no workaround commands (recovery approvals, direct DB edits). Never record a review skip on the human's behalf.

Quick start

Check advisory guidance for the active task state:

python3 scripts/control_plane/coordinator.py transition-guidance --task-id <task-id>

Workflow

1. Read Guidance & State: Read transition_templates.yaml and SQLite DB enforcement before asking or acting.
2. Interview & Spec Synthesis: Interview for missing requirements. Compile the 4 pillars of TASK_SPEC.md (The Job, The Why, Semantic Guardrails, Objective DoD).
3. Plan Drafting: Draft plan via native host facilities. For STANDARD work, evaluate execution topology (select-loop-strategy) and conditionally invoke graph-planner to compile graph-manifest.json before review.
4. Stage Transitions: Transition through INTAKE -> INTERVIEW -> DRAFT_PLAN -> PLAN_REVIEW using coordinate-transition.
5. Advance to Approval: In PLAN_REVIEW, once the plan is accepted, agent runs coordinate-transition --to AWAITING_APPROVAL.