openlogos launch

Transition the project from initial lifecycle to active lifecycle. Once activated, all modifications to existing documents must go through a structured change proposal.

Synopsis

openlogos launch

No arguments or options. Must be run from the project root.

What it does

1. Reads logos/logos.config.json and checks the current lifecycle value
2. Sets lifecycle to "active" in logos.config.json
3. Syncs logos-project.yaml project name
4. Regenerates AGENTS.md and CLAUDE.md with change management rules
5. Re-deploys Skills with active lifecycle context

Example output

✓ Change management activated! Lifecycle is now "active".
  From now on, modifications to existing documents require a change proposal.
  Run `openlogos change <slug>` to start a new change proposal.
  ✓ AI rules updated in logos/skills/

Before vs. after

Aspect	initial	active
Phase progression	Free — AI follows phases	Free — AI follows phases
Modifying existing documents	Allowed directly	Requires a change proposal
AGENTS.md content	”No change proposals needed"	"MUST create proposal before modifying”
AI behavior	Writes code directly	Stops and asks for proposal first
openlogos change	Works (but not enforced)	Enforced by AI instructions

When to use

Run launch after completing your first development cycle (all phases done, openlogos verify passed). The status command suggests this automatically when all phases are complete.

Typical timing:

openlogos init → Phase 1 → 2 → 3 → openlogos verify
                                          │
                                    openlogos launch   ← here
                                          │
                              openlogos change <slug>  (iterations)

Idempotency

Running launch when lifecycle is already active is a no-op:

Change management is already active (lifecycle: "active").

Errors

Error	Cause	Fix
logos/logos.config.json not found	Not in project root	cd to project root, or run openlogos init first

Related commands

• change — Create a change proposal (available after launch)
• status — Shows the lifecycle state and suggests launch when ready
• sync — Regenerate files (launch also regenerates internally)