Control plane / agentic engineering · v0.1.0-rc.24

Coordinate the work. Preserve the evidence.

YYLO (why-lo) runs bounded coding-agent work across providers, preserves worktree and session provenance, and coordinates validation, review, and integration.

Supplementary visual overview

YYLO at a glance.

Product behavior and commands are defined by the verified HTML documentation; this artwork provides a high-level visual summary.

Open full-size image Visual overview of the YYLO coding-agent control plane, task records, and evaluation layer

Install / first run

Start with one bounded outcome.

Install the synchronized release, then begin with a change small enough to validate and review.

Install
npm install -g @yylo/cli@0.1.0-rc.24
First run
yylo init --task "Ship the smallest verified change" --subagent pi

Available today / mechanisms

Control is visible, not implied.

01

Bounded delegation

Route work to configured agents and models with explicit iteration and workflow limits.

02

Isolated execution

Keep task changes in admitted worktrees bound to an exact repository target.

03

Provenance

Retain provider, model, session, logs, commits, and structured execution evidence.

04

Guarded integration

Validate candidates and coordinate policy-bound review and merge outcomes.

Product direction / clearly separated

How this layer strengthens the System of Work.

YYLO is progressively connecting task and lifecycle evidence into a durable Engineering Change record. Deployment, production-outcome learning, and automatic workflow selection remain direction rather than current-release claims.

Next step

Operate the control plane.

Read the YYLO documentation