Nuxt Backend Interface
To close: Replace '_Filled at completion._' with a two-line verdict: Fable chosen, cut over in c107 · Move to HISTORY.md
last activity Oct 2
Every page of the dashboard fetched its data its own way, and nobody had written down how pages, parts and data should fit together.
A written rulebook for how pages get data, and every page rebuilt on it, twice, by two AI builds. One build became the product's app a few days later.
Documents
With file names, on their own page →What changed
The three changes that matter most, in plain words. Open any one to see it.
- 1
Every page was rebuilt on the new rules and checked against the old app, screen for screen.
Same pages, new wiring · came from Mark Parson
- 2
Each of the 43 pages was checked to see which numbers come from the backend and which are stand-ins.
Where every number comes fromopen →
- 3
A written rulebook now says how a page gets its data and hands it to its parts, each rule with a test.
A rulebook for data · came from Tyler Flint and Mark Parson
- A short report page explains the experiment, what was found, and the decisions it needs. In words
- A few days later, one of the two rebuilt apps became the product's app. In words
How we got here
Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.
From the record: no recorded conversation behind this one.
c99-D1 Each build is a separate app in its own branch and folder, runnable side by side, never touching the live one. — Mark Parson
c99-D2 Front end only: the backend's answers are a fixed contract. — Mark Parson
c99-D3 Build the foundation and the Team pages first, then the rest in waves. — Mark Parson
Every page was rebuilt on the new rules and checked against the old app, screen for screen.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
Each of the 43 pages was checked to see which numbers come from the backend and which are stand-ins.
From the record: no recorded conversation behind this one.
c99-D6 New shared parts stay inside each app, flagged for the layer, not extracted yet. — Mark Parson
A written rulebook now says how a page gets its data and hands it to its parts, each rule with a test.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
His composables were the grammar the rulebook wrote down
The rulebook codifies the composable patterns he built in app.qpoint.io (useList, useEntity and the metric primitives), and the report was written for his evaluation. That evaluation is not recorded yet; the switch went ahead on Mark's ruling to confirm with him afterwards.
Set the experiment's rules and called the switch
Ruled that each build is its own app, that the backend stays fixed, Team first, and what counts as data in the report; later, to promote one app now and confirm with Tyler afterwards.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 2
The full record 9 decisions · 20 key-change entries · 2,696 words · 0 captures
The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.
Open the record for c99 →