← Gallery NOW Project Execution Orchestration
Single alignment point for humans, local AI, cloud AI, and handoff discipline.
Business model: Orchestration root (non-execution)
Operational protocol — not a product SKU
Problem
Multiple projects, machines, and AI surfaces drift without a single registry of slugs, handoffs, and execution pointers.
Constraints
- CONTROL TOWER does not replace project execution directories (
~/Projects/, ~/ShipYard/).
- Machine identity only via
~/.machine_env — never synced to Drive.
- Hidden slugs (e.g. deferred case work) live in
HIDDEN_SLUGS.md, not the public index.
Systems Analysis
CONTROL TOWER coordinates:
- 06_PROJECT_INDEX — canonical slug list consumed by ShipYard CLI and Web mirror.
- 05_HANDOFFS/projects// — INTAKE, STATE, DOMAIN, EXECUTION_POINTER per project.
- 09_SYNCHRONIZATION — dry-run first, then apply to Drive.
Deployment
- Local workspace:
~/CONTROL TOWER/
- CLI:
shipyard list, shipyard refurbish <slug>, shipyard sync <slug>
- Public narrative: consolidated under PORTFOLIO →
shaneturon.ca