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:10:03.224Z

Done Work Item

VPS/hosting provisioning runbook + initial production deploy to public domain

Execute the initial production deployment of Build Factory to a publicly accessible VPS. Steps: provision VPS (DigitalOcean Droplet / Hetzner VPS — minimum 2GB RAM, 2 vCPU, 40GB SSD), install Docker + Docker Compose on VPS, clone repo to VPS at /opt/build-factory, configure .env with production values (DATABASE_URL, DOMAIN, auth secrets), run docker compose -f docker-compose.production.yml up -d, confirm /api/health returns 200 from public internet, trigger first deploy via GitHub Actions pipeline (BF-220), confirm zero-downtime redeploy works. Write a production operations runbook documenting the complete setup and recovery procedure.

bootstrapstate: done

Execution Context

ID
wi-BF-274
Branch
bf/BF-274-vps-hosting-provisioning-initial-deploy
Validation
./scripts/validate-local.ps1
PR
https://github.com/SingletonTheory/build-factory-bootstrap/pull/323

Lifecycle Metadata

Lane
Done
Work type
operations
Source
done
Status
done
State
done
Done criteria
28

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-274.prompt.md

Execute the initial production deployment of Build Factory to a publicly accessible VPS. Steps: provision VPS (DigitalOcean Droplet / Hetzner VPS — minimum 2GB RAM, 2 vCPU, 40GB SSD), install Docker + Docker Compose on VPS, clone repo to VPS at /opt/build-factory, configure .env with production values (DATABASE_URL, DOMAIN, auth secrets), run docker compose -f docker-compose.production.yml up -d, confirm /api/health returns 200 from public internet, trigger first deploy via GitHub Actions pipeline (BF-220), confirm zero-downtime redeploy works. Write a production operations runbook documenting the complete setup and recovery procedure.

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-274/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-274/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-274/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-274/actions/record-history