Ledger Tasks Yylo

YYLO Ledger CLI Reference

Use yy ledger for all commands. Before any operation, run yy ledger --version and yy ledger --help; the installed runtime's help is authoritative. Read the current task/board state before mutation, preserve the returned mutation receipt when offered, and never edit Markdown/store files directly to bypass controller routing or lifecycle state. If the required command group is absent, stop and request a Ledger upgrade rather than guessing or invoking mutable source code. Ledger 0.3.x exposes both the compatible flat task commands and the native ID-first record|task|wiki|workflow|artifact groups. yy kanban is a labelled compatibility alias for the same controller-routed task runtime.

Supported task contract

• Preflight installed yy ledger --version and yy ledger --help; command help is authoritative for the selected runtime.
• Use the flat task surface for lifecycle task management. Use the dedicated native skills for wiki, workflow, and artifact Records rather than guessing their arguments.
• New operational PDRs, contracts, plans, reports, receipts, and evidence belong in typed Artifact Records, not product documentation, task bodies/responses, or new .juno_task/specs files.
• If a required native group is absent, fail closed and request a Ledger upgrade. Never invoke mutable source directly or write Ledger store files by hand.
• Read current task state before mutation, preserve mutation receipts where offered, and never bypass controller routing or lifecycle state with direct file edits.
• Normal discovery is hot-only unless an explicit cold-archive command is used.

Opt-in cross-project routing