Provenance
People need to know who wrote what: before they accept it, after they accept it, and long after it has been copied into a report. Provenance keeps authorship visible for the life of the content.
When you need it
- The model drafts text that a person will send, sign or publish under their own name.
- A document mixes a person’s writing with sections the model wrote.
- The model changes values in a table, and someone will make decisions from that table.
How it works
| Moment | What people see | Component |
|---|---|---|
| The model is writing | Pigment text behind a steady model caret | Flux |
| The draft awaits review | Pigment that flows once per beat | Flux |
| A person accepts it | The pigment stops flowing, and stays pigment | Flux |
| Both write in one field | Ink runs and pigment runs, side by side | Caret |
| A long document | A scrollbar mapping every author | Rail |
| Data the model changed | New value in pigment, old value struck beneath | Shift |
Best practices
- Keep provenance in the data, not only in the styles. Store who wrote each run of text, so it survives copy, export and reload.
- Never let acceptance erase authorship. Accepted means a person approved it, not that a person wrote it.
- When people edit model text, the edited words become ink and the untouched words stay pigment.
- Say it in words for screen readers and exports: “written by the model, accepted by Asvin, 13 Oct”.