Operator Frame

Global navigation, page frame, and live control-plane status.

The shell is intentionally persistent: left-side navigation, a shared header, and durable status surfaces remain stable while future workflow views swap in.

Lane

Done

Domain

bootstrap

State

done

Work Item

Typed detail boundary

Control-plane detail payloads expose explicit context, lane, approvals, execution state, and action metadata.

Snapshot 2026-03-27T08:09:58.037Z

Done Work Item

Sync CONTROL_PLANE.md and QUEUE_FLOW.md with actual repo lane inventory

CONTROL_PLANE.md and QUEUE_FLOW.md describe the canonical lifecycle (github-backlog/approved → work-items/ready → running → review → done) but omit two active folders that exist in the repo: work-items/approved (used by factory-create-work-item-from-promotion.ps1 for promotion-derived staging) and work-items/backlog (used by factory-capture-pr-review-risks.ps1 for review-risk triage items). Update both docs to accurately reflect all live lifecycle folders, their purpose, the scripts that write to them, and where they fit in the operator workflow. Do not redesign the lifecycle — only document what exists accurately.

bootstrapstate: done

Execution Context

ID
wi-BF-181
Branch
bf/BF-181-sync-control-plane-queue-flow-docs
Validation
./scripts/validate-local.ps1
PR
https://github.com/SingletonTheory/build-factory-bootstrap/pull/192

Lifecycle Metadata

Lane
Done
Work type
documentation
Source
done
Status
done
State
done
Done criteria
2

Queue Truth

Freshness: Fresh (snapshot age 0s)

Drift: none.

Reconciliation Guidance

  • No reconciliation required; item truth signals are consistent.

Prompt Context

./work-items/prompts/wi-BF-181.prompt.md

CONTROL_PLANE.md and QUEUE_FLOW.md describe the canonical lifecycle (github-backlog/approved → work-items/ready → running → review → done) but omit two active folders that exist in the repo: work-items/approved (used by factory-create-work-item-from-promotion.ps1 for promotion-derived staging) and work-items/backlog (used by factory-capture-pr-review-risks.ps1 for review-risk triage items). Update both docs to accurately reflect all live lifecycle folders, their purpose, the scripts that write to them, and where they fit in the operator workflow. Do not redesign the lifecycle — only document what exists accurately.

Available Actions

  • Start executionBlocked

    Queue execution handoff for this work item.

    Recovery guidance

    Cause
    Done items stay closed; Start execution cannot move them backward.
    Policy context
    Lane transition policy blocks Start execution when the item is already Done.
    Next step
    Create a net-new work item if more delivery is needed instead of reopening this one.
    Safe retry
    Do not retry Start execution on a done item.

    identity: start-execution

    permission: factory.work-item.execute

    policy gate lane-transition: blocked (Done items stay closed; Start execution cannot move them backward.)

    POST /api/control-plane/items/wi-BF-181/actions/start-execution

  • Request reviewBlocked

    Mark this item ready for review lane handoff.

    Recovery guidance

    Cause
    Done items stay closed; Request review cannot move them backward.
    Policy context
    Lane transition policy blocks Request review when the item is already Done.
    Next step
    Create a net-new work item if more delivery is needed instead of reopening this one.
    Safe retry
    Do not retry Request review on a done item.

    identity: request-review

    permission: factory.work-item.request-review

    policy gate lane-transition: blocked (Done items stay closed; Request review cannot move them backward.)

    POST /api/control-plane/items/wi-BF-181/actions/request-review

  • Prepare releaseEnabled

    Run release-preparation checks for the work item.

    identity: prepare-release

    permission: factory.work-item.prepare-release

    policy gate lane-eligibility: pass

    policy gate pull-request: pass

    POST /api/control-plane/items/wi-BF-181/actions/prepare-release

  • Record historyEnabled

    Capture history snapshots for audit and validation views.

    identity: record-history

    permission: factory.work-item.record-history

    policy gate context-visibility: pass

    POST /api/control-plane/items/wi-BF-181/actions/record-history