A projection is a read-only view of ROOK's on-device record. It can arrange the same recorded history for a desktop dashboard or a phone screen, but it does not own a second copy of project state.
[Visual 3.2 — One append-only record stands on the left. Three arrows fan outward to read-only views on the right: a task list, a decision-card view and a status view. Every arrow points away from the record, and no arrow connects one view to another. A small return arrow for an operator's answer goes past the views and ends at the origin record. A caption reads: "many views, one authority".]
Views follow the record
Different surfaces need different arrangements. A desktop can show a broad dashboard while a phone shows the decision that needs an answer. Both remain windows onto the work machine's warehouse. The useful distinction is between presentation and authority: a projection presents recorded state; the warehouse owns it.
That boundary also keeps an operator's answer attached to the original history. The answer is not stored as private phone state and copied back later. Writes go online to the origin work machine. When disconnected, the surface is read-only rather than pretending it can safely create an independent queue.
Limits
A shared source does not guarantee a correct view. A surface can select the wrong field, present an old state or give recorded data the wrong meaning. The record prevents a projection from becoming the authority; it does not prove that every projection is complete or well explained.
The same limit applies to message contracts. Generated decoders can make wire-schema mismatches fail loud at decoded boundaries, but they do not prove semantic, behavioral or presentation agreement. Projections are therefore replaceable views, not evidence that every screen must look or behave the same.
Next
With the record established, continue to autonomy.