Part 5 made Ethiopia one Component that three coffees point at, so a correction lands everywhere at once. That is the right decision and this part does not undo it.
But the Ethiopia card now says exactly the same thing on all three pages, and it should not. The Guji is a washed lot from a co-operative; the Yirgacheffe is a natural; what is worth saying about Ethiopia differs depending on which coffee you arrived from.
The obvious moves are both wrong, and seeing why is the part worth having.
Two bad answers
Split Ethiopia into three Components. Now the shared facts — the altitude, the harvest window, the region — are written three times, and part 5’s whole argument is undone to solve a much smaller problem.
Add a field to coffee. Something like origin-note. Except it is the Origin card that renders it, so the card would have to reach back up into the coffee that referenced it to find its own text. The card would need to know what kind of thing was pointing at it, which is precisely the coupling a reference is supposed to remove.
Whose value is it?
The useful question is about ownership, and this value has an unusual answer.
altitude belongs to the Origin. It is true of Ethiopia regardless of who is asking.
This note belongs to the relationship between a coffee and its origin. It is not a fact about Ethiopia and it is not a fact about the Guji. It is a fact about the Guji being from Ethiopia — which is neither entity on its own, and therefore has no field on either that could honestly hold it.
Some values do not belong to a thing. They belong to an edge.
Contextual fields
So origin.note is declared contextual, and the shape follows exactly:
- The Origin holds the value, as normal. Ethiopia’s own page reads it.
- Each coffee’s binding — the reference itself, not the coffee — may supply its own value for that one field.
- Everything else about the Origin stays shared, unaffected, single-sourced.
Delivery overlays the override before the renderer ever sees the document. So OriginCard reads content.note and never knows the difference:
<p>{origin.content.note}</p>
No branch, no "did somebody override this", no second code path. The card renders an origin; which origin, and whose reading of it, is resolved before it is called.
One Component, four readings: three coffee-specific and one default on Ethiopia’s own page, where there is no binding to override anything.
Where a contextual value is actually typed — on the binding, not on the origin, and saved with the coffee that holds it.
When to reach for it
Contextual values are easy to over-use, because "different here" is a very common feeling and this makes it cheap. The test that holds up:
Would the value still be true if you deleted the thing referencing it? altitude would. This note would not — it exists only because a particular coffee points at a particular origin, and it disappears with that relationship.
If a value survives the referrer, it belongs to the referenced thing. If it dies with the reference, it is contextual.
Where this leaves us
A model that has not grown a single Contract in three parts, and has gained generated types, per-relationship copy and — next — a second language.
That is the argument, and the next part is where it lands.
