YYLO Ledger

YYLO Ledger keeps task bodies, statuses, responses, tags, relationships, and commit evidence stored directly in Git, so the record remains versioned and inspectable.

Dependency awareness

Blockers and relationships are modeled explicitly, so teams can find ready work and topologically order tasks before dispatch.

Agent-friendly output

Results can be produced as JSON, NDJSON, XML, or tables, making the data easy to consume for scripts, agents, and human operators.

Retained history

Mutation history is preserved, and completed work is moved into immutable cold archive packs for a durable engineering memory.

• Coding teams: Keep task intent, status, and blockers in Git so every agent and developer sees the same source of truth.
• AI agent operators: Track dispatched work and commit evidence across multiple automated runs without losing state.
• Engineering leaders: Surface blockers and ready work to plan and topologically order the next round of tasks.
• Compliance and audit: Preserve mutation history and archive completed work in immutable cold packs for later review.
• Handoffs: Provide a durable task-memory record that survives when conversations or team members change.

What is YYLO Ledger?

YYLO Ledger is a local, dependency-aware source of truth for task intent, status, blockers, responses, history, archives, and commit evidence. It stores this task truth natively in Git, so the record is durable, versioned, and inspectable by both people and coding agents.

How do I install YYLO Ledger?

Install the synchronized open-source release with the command pip install yylo-ledger==0.2.1rc1. Version and links are synchronized directly from the repository source truth, so you always get the current release.

How do I start using it?

Start with one bounded outcome, for example yy ledger create "Verify the release" --status todo. Keeping the first change small makes it easier to validate and review before scaling up to more tasks.

How does it store task data?

It stores task bodies, statuses, responses, tags, relationships, and commit evidence directly in Git. Dependencies are modeled between tasks so they can be topologically ordered before dispatch to agents.

Why is it dependency-aware?

Blockers are modeled explicitly, which lets teams find ready work and order tasks correctly before dispatch. This reduces coordination overhead and keeps the workflow deterministic for coding agents.

What formats does it support for output?

It can produce output as JSON, NDJSON, XML, or tables. These formats are designed to be easily consumed by scripts, coding agents, and human operators.

How does it preserve history?

Mutation history is preserved in the Git-native record, and completed work is moved into immutable cold archive packs, building a long-term engineering memory.

• Install the synchronized release with pip install yylo-ledger==0.2.1rc1 to get the current open-source version.
• Start with a bounded outcome by running yy ledger create "Verify the release" --status todo as the first task.
• Record task bodies, statuses, blockers, responses, tags, and relationships directly in Git for a durable truth.
• Let Ledger surface blockers and ready work, then topologically order tasks before dispatch to agents.
• Review retained history and archive completed work into immutable cold packs for a long-term engineering memory.