Coordinate the work. Preserve the evidence.

Source candidate · check installed yy init --help

Choose Simple or Advanced

For a new project, the final interactive initialization question selects the workspace mode. This source behavior is not a claim about the stable release above.

• Simple (recommended to start): code, notebooks, notes and Ledger in one Git checkout. Agents share files and the Git index; coordinate overlapping edits. Task completion is local bookkeeping, not managed delivery.
• Advanced: a separate metadata controller, isolated task worktrees and managed merging. Use this when you need managed parallel development and protected-target delivery.

git init
yy init
# Guided Simple, skipping only the mode question:
yy init --interactive --mode simple
# Explicit Advanced automation:
yy init "Build an API" --mode advanced

Simple requires prior Git initialization, preserves existing project instructions, and does not install dependencies, stage, commit or create worktrees. The selected agent and project goal are saved locally. Leave the Advanced-only Git URL blank.

Existing inline automation stays Advanced. Noninteractive yy init --mode simple remains a read-only preview; use --plan-file then --apply-plan for reviewed setup. Normal initialization never converts an existing workspace; do not toggle the mode field manually.

Advanced to Simple: a fresh copy

For a settled registered metadata-only controller with a same-repository product branch, an explicit plan/apply flow creates a new Simple checkout. It preserves product history and committed Ledger data while leaving the original controller, registrations and worktrees unchanged. Simple to Advanced is unsupported, even with force.

yy init --mode simple --from-advanced /controller --directory /new-project --plan-file /external/conversion.json
yy init --mode simple --apply-plan /external/conversion.json

Stop writers and settle managed tasks first. Dirty worktrees, ignored durable data, symlinks, submodules, conflicting product-side Ledger data and existing destinations are refused. Other legacy or combined layouts are not supported.

Review inactive old instructions and settings under .juno_task/advanced-backup, restore only compatible project conventions, and configure agents, dependencies and credentials manually. No automatic remote, staging, commit, cleanup or live cutover occurs. The new Ledger is an independent snapshot. Preserve interrupted destinations for inspection; never delete a reservation to force startup.