| Wave | Name | Done | % | |
|---|---|---|---|---|
| Wave 0 | Foundation | 109/112 | 97.3% | |
| Wave 1 | The gate | 125/128 | 97.7% | |
| Wave 2 | Data, channels, retrieval | 200/215 | 93.0% | |
| Wave 3 | Agents, knowledge, console | 19/314 | 6.1% | |
| Wave 4 | Doing, lifecycle, extensions | 0/199 | 0.0% | |
| Wave 5 | Hands, delivery, go-live | 0/182 | 0.0% |
8d27f96 Installing a template and building an agent by hand are one code path, or the guardrail has a doorede4c9c A batch is a budget, and it is sized from the slot rather than the container7b1ce50 Sealing the authority section would move the edit one screen, so the seal is on the guardrails2d54610 The library's own answer for a read-only field renders the withheld value into the DOM43fd9a5 An agent is two axes, and tying them together is how a permission model grows a hole95ef75e A grid is the easiest place in this system to leak a count, so this one cannot render a digitM0.4.2M38.2.1.2M38.2.1.3Every figure here is computed from commits merged to main, never entered by hand. A task counts as done when a commit naming its id is on main and CI passed, so this page cannot show progress that does not exist. Generated at build time from d9077de, so it always describes the code actually running.