Done Work Item
Docker Compose topology — local dev and production compose files with volume and network strategy
Create docker-compose.yml for local development and docker-compose.production.yml for production deployment. Include: operator-cockpit service (using BF-214 image), volume mounts for SQLite database persistence and log output, network isolation, health check wiring per service. Local compose should mount source for hot-reload in dev. Production compose should use built image with explicit restart policy. Add .env.example documenting all required environment variables. Both compose files must start the system cleanly from a fresh checkout. Prerequisite for BF-218 (SSL) and BF-220 (deploy pipeline).
Execution Context
- ID
- wi-BF-216
- Branch
- bf/BF-216-docker-compose-topology
- Validation
- ./scripts/validate-local.ps1
- PR
- https://github.com/SingletonTheory/build-factory-bootstrap/pull/271
Lifecycle Metadata
- Lane
- Done
- Work type
- operations
- Source
- done
- Status
- done
- State
- done
- Done criteria
- 8
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-216.prompt.md
Create docker-compose.yml for local development and docker-compose.production.yml for production deployment. Include: operator-cockpit service (using BF-214 image), volume mounts for SQLite database persistence and log output, network isolation, health check wiring per service. Local compose should mount source for hot-reload in dev. Production compose should use built image with explicit restart policy. Add .env.example documenting all required environment variables. Both compose files must start the system cleanly from a fresh checkout. Prerequisite for BF-218 (SSL) and BF-220 (deploy pipeline).
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-216/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-216/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-216/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-216/actions/record-history