Sibyla Development Plan v6.0 — cut to the day-to-day loop

GOTT Sibyla — project evolution

Plan of record is docs/V6.md; backlog is docs/project-todo-v6.md. This page yields to both. Every number below comes from the data island in this file's source, counted by the rules in Methodology.

The finding — where July and August went

One chart carries the whole argument for v6. Each bar is a day's commits on GOTT.Sibyla, split by what the commit did: feature and schema code, or governance — records, reviews, rejections, amendments and approvals.

Code — features, schema, tests Governance — records, reviews, rejects, approvals

In July, 87% of commits were code (71 of 82). From 3 August, that inverts: 74% governance (106 of 143). The three biggest days in the project's history — 5, 6 and 7 August, 118 commits between them — produced no user-visible feature. The 10 August bar is v6 itself: the plan, the revocation, the archive and the V6-O1 decision. Governance too — but the kind that ends governance.

The August code bars are honest but need a footnote: they are the P1-1a and P1-1b migrations and their tests, not application features. Measured on application code rather than schema DDL, the last change is fix: authorize strict WhatsApp LID senders on 24 July — 17 days before this page was last regenerated.

Data table — commits per day

What v6 changes

Five decisions taken on 2026-08-10. Their combined effect on the size of Phase 1:

The last row is the one that mattered most. v5.0 placed all ERP integration in Phase 2, which meant the stated core loop — document arrives, is catalogued, reaches the ERP — could not complete in Phase 1 by construction.

Roadmap — S0 through S7

Estimates, not commitments. They exist so that a phase running at triple its estimate is visible as a signal rather than absorbed silently. All of them assume the light review method (V6-O1); if the current gate structure stays, multiply by roughly three.

Phase S2 and S4 — if everything else slips and these two land, the project has a product

Backlog — 68 live items

Detail is capped at the current phase plus the next. S0–S2 are itemised; S3–S7 are sketched and get itemised when the phase before them closes. v5.0 itemised fourteen phases and delivered one.

Gates, reviews and decisions are not backlog items and never move the numerator. A phase closes on its exit criterion being demonstrated to a person, not on its boxes being ticked.

Open — if it is not here, it is decided

Next steps, in order

Deferred to Phase 2 — with the trigger that brings each back

Nothing here is called worthless. Each carries the condition that would justify reinstating it, so it can be revisited on evidence rather than re-argued from scratch.

History

The condensed chronicle. Full narratives live in git history and the dated records, now moved to docs/archive/ — this table points, it does not re-narrate.

Methodology — the counting rules behind every number

This page renders its numbers from the embedded data island with JavaScript. The data is readable in the EVO-DATA block in the page source. Regenerate the commit series with git log --format='%ad|%s' --date=short and the classifier in the Methodology table.