Reference implementation for the Phoenix Architecture. Work in progress. aicoding.leaflet.pub
README.md

Trail — Issue & Sprint Tracker #

A Linear/Jira-style issue tracker generated by Phoenix from three plain-language specs. Issues move across a Kanban board and roll up into time-boxed sprints.

spec/issues.md + spec/sprints.md + spec/board.md
   → phoenix bootstrap →
3 specs · 12 clauses · 72 canonical nodes · 6 Implementation Units · 6 modules

What it exercises #

  • Multi-spec project — three documents compiled into one app, with cross-spec context (the board UI calls the issues and sprints APIs).
  • Workflow rules — a five-stage status board (backlog → todo → in_progress → in_review → done) with one-step transitions, point estimates, and validation.
  • Derived views — live sprint rollups (points committed/completed, % done, over-capacity warnings, status breakdown).
  • A Kanban web UI — five color-coded columns, priority badges, a sprint selector, filters, search, and a new-issue form, all driving the REST API.

Run it #

npm install
npx tsc            # emits dist/ (the trust gate flags two IUs as opaque — see below)
PORT=4500 node dist/server.js
# board UI:  http://localhost:4500/design
# REST API:  http://localhost:4500/issues , /sprints , /sprint-rollup

Inspect the compilation #

npx phoenix inspect

Opens the dynamic provenance inspector: click any issue requirement to trace it through clause → canonical node → IU → the exact generated lines that implement it (green "traced" gutter tags come from //phx provenance markers the generator emits). The Trust tab surfaces the regeneration gate's verdict per IU.

Honesty note #

This is real, unedited generator output — four coherent modules (board, issues, sprints, sprint-rollup). The validation/workflow-rules sections fold into their entity IU rather than spawning duplicate table-owning modules, and the web UI is generated against the issues API's real contract, so the board and API agree on field names (point_estimate), types (labels as an array), and status spelling. Create / move / save all work end to end.

The trust gate still marks every IU opaque (no evaluations/evidence collected yet) and flags the merged Issues module's conceptual mass — honest signal, not a bug. The inspector surfaces all of this rather than hiding it, which is the point.