Projects
What I am actually building.
Six demos, all runnable in the browser: read a compressed record, watch authorship assemble,
then find out what a reader loses. No installs, no model calls, nothing to sign up for.
DemoLive
What the patient hears
A clinical record and the version a reader reconstructs from it, compared line by line: kept,
compressed, dropped, inverted. Four cases, including the same record rewritten properly for
contrast.
- Question
- What survives when a record is restated for someone else?
- What it shows
- Meaning loss per line, scored by how much of it a reader has to act on.
Health comm.CompressionInteractive
Open the demo →
DemoLive
The Handover
Read a ward handover once, then read the summary the night shift is given, then answer seven
questions about the patient. Fifty seconds of reading, and it keeps score.
- Question
- What does a summary let a clinician forget?
- What it shows
- Compression as an experience, with the dropped facts named at the end.
Meaning under compressionGame
Play it →
DemoLive
Provenance Strands
A generated clinical letter with its authorship drawn above every sentence. Scrub the timeline
and watch two hands write, edit and sign it, then find the lines a human never touched.
- Question
- Where does accountability actually sit in a generated document?
- What it shows
- The audit trail as something a reader can look at, not a single label.
ProvenanceAuthorshipInteractive
Open the demo →
DemoLive
Drift Ribbons
A record and its patient rewrite, joined by a ribbon per pair. Thickness is how far the meaning
moved, colour is which way it went. Pull the threshold and everything harmless fades away.
- Question
- How much of the action survives a rewrite that reads better?
- What it shows
- Where the clinical risk sits, and how a friendly sentence ends up saying the opposite.
Health comm.MeasurementVisual
Open the demo →
DemoLive
The Compression Waterfall
One letter, four summarisation passes. Drag the slider and it comes apart in the order detail
actually disappears, while the version beside it keeps reading fluently.
- Question
- What does the second, third and fourth compression take that the first did not?
- What it shows
- Loss compounding, and why every pass still looks reasonable at the time.
CompressionIterationInteractive
Open the demo →
DemoLive
The Failure Gallery
Twelve ways a sentence changes what it tells a reader, collected rather than argued. Filter by
category, flip a card for the mechanism and where in a document it happens.
- Question
- What kinds of failure are there, and which ones change what a reader does next?
- What it shows
- A taxonomy you can recognise before it becomes something you can measure.
TaxonomyFailure modesGallery
Open the gallery →