- Draft PR via forge (apps/worker/src/git/pr.ts) push branch + createPullRequest draft with echodo-convoy marker, expose prUrl in Mission Control (convoy-service, convoys router, detail panel) - Operator notes mid-build: convoy_operator_messages (0016), tRPC post/list, worker poll between tool rounds (queued) and before generateText (direct), detail panel thread for in_progress - Doc-writer: harness doc-writer examples (docs/examples/research-pipeline.md), SOP template (docs/templates/doc-sop.md), role-doc-writer wiring Convoy: .convoys/worker-closeout-docwriter Co-authored-by: orchestrator
676 B
676 B
| kind | slug | title | status | priority | tenant_id | updated_at |
|---|---|---|---|---|---|---|
| doc-sop | <doc-sop-slug> | <SOP title> | draft | P2 | <tenant-uuid-or-placeholder> | <ISO-8601> |
SOP:
One-line purpose of this SOP.
Objective
What this SOP standardizes and when to use it.
Prerequisites
- Inputs, tools, or access required
Steps
- Step one — action
- Step two — action
- Step three — action
Verification
- Outcome check 1
- Outcome check 2
Status
draft → doc_review → published via human-gate-2 / doc-approver (packages/shared/src/convoy-lifecycle/state-machine.ts:9)
Links
- Related:
docs/examples/research-pipeline.md