Continuity & CTOs
Keep the approved direction and records intact when the current operator leaves.
On this page
Save the operating policy
- 1
Expand Continuity settings
Choose Managed, Backup, or Autopilot in Operating mode.
- 2
Choose the fallback
For backup, choose a 24, 48, or 72 hour inactivity grace period. Save the approved fallback image direction.
- 3
Save continuity plan
The settings and policy revision are saved to the project. Use I’m running this shift for an explicit operator check-in.
What each mode means
| Mode | Current behavior | Intended production behavior |
|---|---|---|
| Managed | The authorized creator starts work. | The operator directs and delivers the plan. |
| Backup | Saves a grace period and fallback brief. | Approved work becomes eligible after the operator’s lease expires. |
| Autopilot | Saves the approved direction. | A worker follows the policy within its spending and cadence limits. |
| Paused | New work is blocked. | No new production until an authorized resume. |
What a CTO can eventually take over
The intended handover is an operating role. It must not grant treasury withdrawals, redirect creator fees, or transfer someone else’s social account. A site login, ticker, or elapsed timer cannot establish rightful control.
The production design requires verified project authority, a published transition rule, and a challenge window. Delivery receipts should determine whether an operator meets the schedule. Check-ins alone are not proof of work.
Provider failures, missing funding, and disconnected channels need their own blocked states. They should not automatically count as abandonment. CTO claims, voting, operator eviction, and role transfers are not enabled today.