Pykit work
What pykit is made of and what is left to do. The board says what is next; the
epic says how; its ADRs say why. Closed means implemented; the Releases and
Backlog sections below are derived from the epic, feature and release pages by
task docs:generate; never edit inside their fence.
Releases
| Release | Status | Features |
|---|---|---|
| Release 11 — Dependency updates, Sonar debt and key-path artifacts | shipped (2026-11-21) | 4 Closed |
| Release 10 — Typed application state and faster XLSX transfer | shipped (2026-11-19) | 2 Closed |
| Release 9 — pykit simplification | shipped (2026-11-18) | 19 Closed |
| Release 8 — kiln adoption and local-first extraction | shipped (2026-11-14) | 12 Closed |
| Release 7 — authentication and PyPI distribution | shipped (2026-10-30) | 16 Closed |
| Release 6 — kit upgrades for kiln | shipped (2026-10-25) | 7 Closed |
| Release 5 — rn-forge-devops meets kiln's CI contract | shipped (2026-10-18) | 2 Closed |
| Release 4 — kiln readiness | shipped (2026-10-16) | 4 Closed |
| Release 3 — HTTP contract extensions | shipped (2026-10-12) | 8 Closed |
| Release 2 — workspace automation | shipped (2026-10-03) | 4 Closed |
| Release 1 — the first coordinated tags | shipped (2026-09-28) | 9 Closed |
Backlog
Features with no Iteration, by State and epic.
Deferred
| Epic | Features | Entry criteria |
|---|---|---|
| E7 — Azure adapters | F7.1, F7.2, F7.3, F7.4, F7.5, F7.6, F7.7, F7.8 | the owner schedules the package and settles its namespace |
| E11 — Framework codegen | — | the owner schedules it with a concrete framework template to generate |
| E15 — Package boundaries | F15.4, F15.5, F15.6, F15.7 | Per feature; see the epic. |
| E17 — Local-first web-app extraction | F17.6 | Per feature; see the epic. |
E8 — Django scope and auth was retired on 2026-09-28. Its auth review is E13; its package-boundary question is part of E15.
Ideas not yet agreed as work are parked in the ideas list.
Conventions
docs/specs/_structure.md, which the site does not publish, holds the full
rules; this is the short form.
- Taxonomy. Epic
E<n>→ featureF<n>.<m>→ storyS<n>.<m>.<k>(an ADO User Story). IDs are permanent once a commit names them or work starts; aNew, uncommitted item that moves takes its new parent's next ID. This maps 1:1 to Azure DevOps's Agile process; seespecs/_structure.md, Tracker mapping. - State.
New,Active,Closed, orRemoved(retired in place, with a reason). A feature taggeddeferredis not scheduled and carries entry criteria; stories carry their own state. A feature'sIterationfield is the single source of truth for release assignment — the release page's Scope table is generated from it. - A decision is its own story, so work can depend on the decision without depending on its implementation.
- Open questions live on the feature or epic they block. An answered question becomes an ADR or a rejected option.
- Acceptance is checked inside pykit (ADR-0008); another repository's work never gates a feature or release.
- Ideas start in the ideas list, without an ID. Promoting
one creates a
Newepic or feature and deletes the entry. - Do not start or elaborate a
deferred-tagged epic or an idea unless the owner asks.
The decision log records the durable constraints.