YYLO Ledger documentation

Stable 0.4.0

Tasks and dependencies

Keep task intent, status, blockers and responses in Git-native records.

Use create, list, search, get, update and mark for the legacy flat task interface. Native Records also provide a typed task profile.

Dependencies must be explicit: ready finds unblocked work and order sorts dependencies. Cycles and invalid completed-task transitions fail before writes.

Use body-file and response-file transport for rich Markdown; do not hand-edit the store.

yylo-ledger create --title "Verify onboarding" --body "Run the documented quick start" --tags onboarding
yylo-ledger list --limit 5 --format table
yylo-ledger ready
yylo-ledger doctor

Boundary: Ledger records work; it does not own coding-agent execution or Git integration.

Stable 0.4.0

Native Records: wiki, workflow and artifacts

Use immutable IDs and revision-safe updates for durable engineering memory.

Wiki stores Markdown knowledge. Workflow stores validated definitions but does not execute them. Artifacts retain provenance and intentional payload modes.

General Records and typed profiles share ID-first discovery. Aliases resolve to an immutable ID; updates use revision/preimage controls.

Search is bounded by count and bytes. Summary excludes payload bytes; full output is an explicit audited choice. Sensitive records expose safe identity metadata.

yylo-ledger wiki --help
yylo-ledger workflow --help
yylo-ledger artifact --help
yylo-ledger record search --scope all --profile wiki --projection summary --limit 20 --format json

Boundary: Storage, workflow execution and evidence retention remain separate authorities.

Stable 0.4.0

Read-only Record host

Serve bounded local views without exposing a mutation API.

The host exposes record, history, wiki, workflow and artifact routes. Loopback is the default.

Non-loopback access requires an explicit private policy. External artifact redirects require approved HTTPS hosts; traversal and unsafe redirects fail closed.

yylo-ledger host --host 127.0.0.1 --port 8765 --access-policy local

Boundary: No write, workflow-execution or arbitrary remote-fetch API.

Stable 0.4.0

Preservation-first migration

Copy legacy knowledge into Records without deleting original files.

Inventory, plan, apply, status and verify use explicit receipts outside the source root. Review the plan before apply.

Plans bind source bytes, destination, runtime and record identities. Drift fails closed. Retries reuse only matching migration provenance.

yylo-ledger migration inventory --help
yylo-ledger migration plan --help
yylo-ledger migration apply --help

Boundary: Migration is not cleanup: source deletion is never performed.

Stable 0.4.0

History and cold archives

Keep current state and append-only history separate.

Markdown and segmented ledgers are canonical. SQLite is a rebuildable query cache. Default discovery reads hot work; exact ID lookups can resolve verified cold packs.

Archive-pack planning and creation are separate, revision-bound owner operations requiring clean state and external receipts. Follow up with a new related task rather than reopening a cold ID.

yylo-ledger history TASK_ID --limit 20
yylo-ledger archive-pack plan --help
yylo-ledger archive-search --limit 20 --projection metadata

Boundary: Never edit sealed packs or automate destructive archival.

Stable 0.4.0

Install independently distributed skills

Acquire reviewed skill procedures separately from the Ledger runtime.

Ledger 0.4.0 selects seven legacy-compatible YYLO procedures; the four Record skills are the standalone Ledger subset by purpose, not the installer count. Use the open Skills CLI or compatible YYLO CLI for the complete eight-skill catalog, including Benchmark.

Acquisition is explicit and uses the network; local status and ordinary Record commands remain offline. Customized copies are preserved unless replacement is explicitly authorized.

yylo-ledger skills --help
yylo-ledger skills status

Boundary: Review installer compatibility before selecting a newer skills tag. Installing Ledger is not installing skills.

Stable 0.4.0

Cross-project routing and machine output

Make destination and output projection explicit.

Project routing is opt-in and allowlisted. Invalid or stale routes never silently fall back to the source board.

Use JSON, NDJSON, XML or table output. Request bounded projections rather than dumping all payloads.

yylo-ledger project --help
yylo-ledger search --status todo --format json

Boundary: The destination wrapper and policy remain authoritative.

Stable 0.4.0

Retrieve any Record by ID

Read tasks, documents and artifacts without guessing their kind.

New identities use task_, doc_ and artifact_ storage-kind prefixes. Existing IDs remain valid. PDRs can be artifact/report Records.

Collection JSON is one object containing tasks and summary, including empty results. Exact get and collection projections have distinct shapes.

Small readable payloads are included by default. Explicit --content reads bounded local/inline bytes; external URLs are never fetched implicitly.

yylo-ledger get RECORD_ID -f json
yylo-ledger get RECORD_ID --content --max-content-bytes 65536
yylo-ledger record search --projection summary --limit 20 -f json

Boundary: Metadata is not proof that payload bytes were retrieved. Inspect omission reasons and preserve missing, ambiguous or corrupt Record diagnostics.