⭐ The told page has two body modes, and the second was hiding
A told page is usually prose — the memoir, the walk, the
history. But this one is a listing, and the live version is
not written at all. It is a stack of Google Maps cards.
The cafés guide — 7 bookmarks, 5 of them pointing at places:
Title: "Cafe Tamara · Peter Celli St, Fort Nagar, Fort Kochi, Kochi,
Kerala 682001"
Description: "★★★★★ · Western restaurant"
Caption: — none —
⭐ 768 characters of machine text on that page, and zero characters
of human caption. Five cafés distinguished only by what Google thinks
of them, on a site whose entire value is a local opinion.
On the food guide the caption survives but is the small print — the headline
is a 120-character postal address, the description is Google's star rating and
Google's category, and the one sentence a person wrote sits underneath in
grey. Either way the machine text out-weighs the human text.
⭐ And the meals guide shows the second problem:
Caption: "Veg place. 70 INR for meals. Follow it up with
a lassi from Rawal Lassi just opposite"
That is a price, in a caption, with no date on it. So the
bookmark card is not only burying the human voice — it is burying an
unstamped fact, which is exactly what the checked-on stamp exists to
prevent. A place row therefore needs a slot for a price, and that slot
inherits the list's stamp.
That is the sponsorLabel error at page scale — the most useful line
is styled as the least important — and the fix is the same: promote
the sentence, drop the metadata. The address becomes a Map link. The
stars and "Juice shop" go entirely; they are Google's opinion, not ours.
Fourth time: ask what component the writer did not have
- The 89 coloured callouts were a table nobody had.
- The 47 cat-looking boxes were a newsletter signup.
- The six italic questions were subheads.
- ⭐ These Bookmark cards are a place row — and Ghost's
Bookmark card is built for linking to articles, so pointing it at a
venue dragged the whole address in with it.
Same shape every time: Ghost had no component for the job, so the
writer used the nearest one and its furniture came along.
Three decisions this page forced
1. One stamp for the whole list, not one per place. Twelve
strips on a twelve-place guide would be absurd, and each place's hours are not
separately checked — the walk was checked, on a day. So the list is the unit,
and the stamp sits under it with the correction link.
2. A row must work with no verdict. On the cafés guide
there is nothing to promote — so a row is a name, a kind and a Map link, and
that is honest. ⛔ A component that only works when a verdict exists would be
a component that mostly does not work. Verdicts are editorial work, not
something the layout can conjure.
3. A row needs a slot for a price. Shown above on the
meals row. It sits under the list's stamp, so the number is dated — which the
live caption version is not.
⚠️ A note on evidence. The food-guide caption
quoted here is real — food-in-fort-kochi.mdx line 27 — but that
file is status: "draft", so it is absent from the published
export. Two of us searched different artefacts and got different answers. The
cafés guide above is published, and is the stronger case anyway.
⚠️ Rendered in Figtree, the real face — inlined as base64 below, it downloads inside an artifact the same as anywhere else.