Expressive Range
We knew the native kit is light; we did not know whether it can look and read like our web pages.
Our building blocks rebuilt natively and scored, and the Inventory pages running on one laptop's data, close to the web pages beside them.
Documents
With file names, on their own page →Pages
- /cycles/design/c131/doc/phase2-plan (local dev)
- /cycles/qnative/c2/doc/review-tour (local dev)
- /cycles/qnative/c2/doc/CYCLE (local dev)
- /pages/native/bake-off (local dev)
What changed
The 8 changes that matter most, in plain words. Open any one to see it.
- 1
Our building blocks exist natively, with a score for each.
Our layer in Rust, scored · came from Mark Parsonopen →
- 2
The first pages run natively and read like the web, for one machine.
Harnesses, beside the web · came from Mark Parsonopen →
- 3
A table row opens in place on what it carried, and stays open when the list moves.
Tools and the table expand row · came from Mark Parsonopen →
- 4
The whole Inventory section runs natively on one machine's data.
Repos & Workspaces, and the section complete · came from Mark Parsonopen →
- 5
The evidence for the brand ruling: our look comes from a drawn layer, not the kit's components, and costs little at rest.
How close we got: the scorecard and the budget · came from Mark Parsonopen →
- 6
The tour layer's three DOM habits (find by attribute, restyle from outside, Floating UI) all have native answers, and none needed the page to change beyond an id.
The tour, native: What's on this machine · came from Mark Parsonopen →
- 7
The guide no longer needs the dev server and a browser tab: the app is the page.
The MCP guide drives the native app · came from Mark Parsonopen →
- 8
Both review stops cleared and built the same evening, on a branch beside developer mode and merged onto its seam.
Mark's rulings on both review stops, built · came from Mark Parsonopen →
- The app wears our colours and type, from the same source as the web. Before → after
- Every component can be tried, case by case, inside the app. New in this cycle
- Most of the section now runs natively. New in this cycle
- A skill reads natively the way the harness reads it. New in this cycle
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.
qn-c2-D3 Each page is built to a spec measured on qdash at the same window size; qdash's oddities are listed and decided, not copied. — Mark Parson
Our building blocks exist natively, with a score for each.
From the record: no recorded conversation behind this one.
qn-c2-D1 The world is priya-x1's laptop cut from the Meridian seed through qdash's real ingest and handlers; requests are keyed exactly as the web asks for them, so synthetic, the fixture plane and HTTP answer the same keys. — Mark Parson
qn-c2-D3 Each page is built to a spec measured on qdash at the same window size; qdash's oddities are listed and decided, not copied. — Mark Parson
The first pages run natively and read like the web, for one machine.
From the record: no recorded conversation behind this one.
qn-c2-D3 Each page is built to a spec measured on qdash at the same window size; qdash's oddities are listed and decided, not copied. — Mark Parson
A table row opens in place on what it carried, and stays open when the list moves.
From the record: no recorded conversation behind this one.
qn-c2-D3 Each page is built to a spec measured on qdash at the same window size; qdash's oddities are listed and decided, not copied. — Mark Parson
The whole Inventory section runs natively on one machine's data.
From the record: no recorded conversation behind this one.
qn-c2-D3 Each page is built to a spec measured on qdash at the same window size; qdash's oddities are listed and decided, not copied. — Mark Parson
The evidence for the brand ruling: our look comes from a drawn layer, not the kit's components, and costs little at rest.
From the record: no recorded conversation behind this one.
qn-c2-D3 Each page is built to a spec measured on qdash at the same window size; qdash's oddities are listed and decided, not copied. — Mark Parson
The tour layer's three DOM habits (find by attribute, restyle from outside, Floating UI) all have native answers, and none needed the page to change beyond an id.
From the record: no recorded conversation behind this one.
qn-c2-D3 Each page is built to a spec measured on qdash at the same window size; qdash's oddities are listed and decided, not copied. — Mark Parson
The guide no longer needs the dev server and a browser tab: the app is the page.
From the record: no recorded conversation behind this one.
qn-c2-D3 Each page is built to a spec measured on qdash at the same window size; qdash's oddities are listed and decided, not copied. — Mark Parson
Both review stops cleared and built the same evening, on a branch beside developer mode and merged onto its seam.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Asked how close the kit can get
Called the spike a success and set the phase: the whole Inventory section in our skin, on the data the web shows, translated from fleet to personal; answered the plan's four questions; asked mid-phase for a draggable title bar, a Dev section and component docs with every scenario live; called each next page.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 29
The full record 4 decisions · 19 key-change entries · 4,434 words · 27 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 c2 →