Agent theater transfers risk to the customer
A fluid demonstration can hide brittle memory, weak authority boundaries and missing recovery. The buyer discovers those absences only after deployment.
Design record · Sketch 04 · Not part of the site
At 1280 the Captain's Log panel is 1754px tall and its ink stops at 842.
912px — 52% of the column — is empty, and the ratio holds at 1440, 1080 and 900. The
panel is stretched by min-height: 100% on a block that spans every grid row,
so the emptiness is not a gap in the content: it is a panel drawn taller than anything it
was ever given to hold.
Five answers below, each drawn at the rail's real width on the rail's real ground. Two are structural — stop stretching the panel, or shorten what it holds. Three put something in the corner. The last two are the same drawing at two levels of ambition.
On matching the panel to the crew graph: the log's ink already ends at 842 while the graph is 572 tall at 1280 and 628 at 1440. Cutting the panel to the image clips roughly 270px — one whole entry. It is available, but it is “show two entries”, not “trim the panel”.
Nothing here is installed. The build values in sketch 01 are the real fields of
static/build-meta.json, shown with a plausible sha; the chart in 04 and 05 is
drawn from the routes that exist today and would be generated from them, not hand-placed.
The panel as built, with the void drawn as itself. The archive link is the last ink in the column; everything below it to the footer is marine ground. On a page whose whole argument is that nothing should appear without carrying meaning, half a column of ink is the largest unexamined thing on the site.
A fluid demonstration can hide brittle memory, weak authority boundaries and missing recovery. The buyer discovers those absences only after deployment.
The corner of a sheet is where the title block goes, and a sheet is mostly empty between the
drawing and that corner without anyone reading it as a gap. The fields are
build-meta.json's own keys — commit, branch, built — which the repository
generates on every build, serves publicly, and displays nowhere.
Useful rather than decorative: you can tell which build you are looking at without
curling a JSON file. And on anything that is not a deploy the branch reads
local-dev, which is funny to exactly the reader this site is for and
invisible to everyone else.
A fluid demonstration can hide brittle memory, weak authority boundaries and missing recovery. The buyer discovers those absences only after deployment.
No addition at all: drop min-height: 100% so the panel is the height of its
contents and stays stuck at the top while the left column scrolls past it. The void does not
get filled, it stops existing.
A fluid demonstration can hide brittle memory, weak authority boundaries and missing recovery. The buyer discovers those absences only after deployment.
Against it — two costs. A dark block that travels with the reader pulls more attention than one that sits still, and the page loses the two-tone right edge that gives the homepage its structure. The void is not removed so much as moved: below the panel the right third becomes linen instead.
A site map, drawn as a survey rather than as a menu. Primary territories is
INFORMATION-ARCHITECTURE.md's own heading, so the cartography is not a conceit
laid over the structure — it is the word the structure was already described in.
Two things make it a drawing rather than a decoration. Stations are placed by what links
to what, not on a grid — ming-qiao sits offshore because it is exercised aboard
AstralMaris and defined by neither. And the contour closes only where the territory has
somewhere to go: the Observatory's coast is drawn open, because
observatory.ts already says in prose that “each plate names a line of
writing that is open, so none of them links out yet”. The chart tells the truth about
its own completeness, and it will close that coast by itself on the day an essay ships.
A fluid demonstration can hide brittle memory, weak authority boundaries and missing recovery. The buyer discovers those absences only after deployment.
Primary territories
For it — it is a site map, so it is functional by definition, and it is the only sketch here that would make the homepage's right column tell a reader something they cannot get from the navigation: the shape of the work, and how much of it is finished.
The same drawing in the narrow rail, which is where a chart of this density either survives or does not. Labels hold because they are set in absolute units inside a scaling viewBox — the same decision the stage stamp's ladder came to after its labels shrank illegibly at 390px.
Primary territories
The chart's other half of the idea, and the one that answers “linked to current important
articles” directly. Two of the three log entries already declare a
relatedArtifact in their frontmatter; nothing new has to be authored for this
to exist. Set as bearings taken from the record to the work it concerns, it makes the log
what the site says it is — a field record of the build — rather than three blurbs beside it.
It also has teeth: an entry with no related artifact shows as a bearing not taken. Two of
three, today.
Bearings from the record
Sketches 02 and 04 taken together, and not stacked. The chart is not a figure placed below
the archive link — it is printed on the panel, and the record stands on top of it.
The rail becomes the sheet.
A single opacity would either drown the entries or vanish in the void, so the drawing is
masked down the column: a whisper behind the record, full ink from about two-thirds down
where nothing else is. The emptiest part of the column is the part the chart is most
legible in, which is the whole trick — the space is not filled, it is used.
Mariner's colouring, from inside the site's palette rather than from outside it: brass
and gold are already its warm pair, so the chart reads as printed at a different time
from the record on top of it without importing a colour the site does not own. The
rhumb network, the doubled rose, the tighter shading line just inside a surveyed coast
— all standard portolan construction, and AGENTS.md names navigational
records as a source of character in the first place.
A fluid demonstration can hide brittle memory, weak authority boundaries and missing recovery. The buyer discovers those absences only after deployment.
What to judge — whether the entries still read cleanly over the rhumb lines at the top, and whether the rose earns its place or is the one piece of pure ornament on the site. The lines are chart construction rather than decoration, but they are construction for a navigation nobody performs here.
The drawing at full strength everywhere, so the mask in 06 can be judged against what it is holding back rather than against a description of it. This is what the panel looks like if the chart is treated as a surface the record sits on rather than as something behind it. It is almost certainly too much — the entry is now competing with a rhumb line through its own second sentence. It is here to set the far end of the range.
A fluid demonstration can hide brittle memory, weak authority boundaries and missing recovery. The buyer discovers those absences only after deployment.
This is the drawing that shipped. Since the sketch was taken it has
grown, moved down the column, had its coasts respaced over a taller field, and had its
islands made selectable — each one is a link to its section, which is what turns a chart
that repeats the navigation into the site map it is drawn as. The specimen below is the
component's own markup and geometry, kept in step deliberately: a record that no longer
matches what it produced is worse than no record.
Two faults were found only after installing, and both were invisible in the markup. The
group carried a translate(0, -22) inherited from this sheet, where the
drawing sat in a differently proportioned panel; and the crop began at y=320 while the
drawing begins at 325, which together put AstralMaris's north shore above the top edge.
The crop is measured from the drawing now — getBBox over the coasts,
islets and labels — rather than chosen by eye.
Where this specimen still differs from the component, and why. The
panel is the rail's real height at 1280 (1742px) and the chart its real 620, anchored
the same distance above the panel's foot — so the chart sits where it sits on the
site. Two things do not match, and both are this sheet's furniture rather than the
drawing's: the title block here renders about 40px shorter than the component's, and
the three entries above are set from copy typed into this record rather than read from
the log, so they wrap a little shorter and the archive link sits higher. Measured:
620 / 620 chart, 1742 / 1742 panel, 208 against 109 from link to first land.
The rose was the one thing on this sheet I could not defend: chart construction, but
construction for a navigation nobody performs here. The mark replaces it and settles the
argument rather than dodging it — rhumb lines radiating from a vessel's own
position are a bearing network from a fix, which is both real navigation and the
thing the site actually claims. The lines now start where the ship is.
The image is the site's own: latentwinds-schooner-mark.svg, the drawing the
masthead carries. Nothing is borrowed, nothing is licensed, and the mark appears twice
on the page at two sizes doing two different jobs — identity at the top, position at the
foot.
The coasts are engraved rather than outlined. An old plate does not
draw land as one line — it lays a band of tone inside the contour and ticks it with
hachures, so the water side and the land side of the line are never in doubt. Both are
the coast path stroked wide and clipped to its own shape, so only the inner half of
each stroke survives; the hachures are the same stroke broken into short marks. No
second path is drawn or maintained, which means a coast can be moved and its shoreline
follows.
Chronological field record
Captain’s Log
A durable station cannot collapse when its current model changes. Otherwise we have named an instance, not built an institution.
The crew works better when agents can reach one another directly through ming-qiao while the XO remains responsible for coherent execution.
A fluid demonstration can hide brittle memory, weak authority boundaries and missing recovery. The buyer discovers those absences only after deployment.
The same, keeping one fine ring around the mark. A chart rings a fix; the ring also holds the rhumb origin visible where the lines are densest, which the bare mark does not. The question is whether it reads as a position circle or as the rose refusing to leave.
Not taken — sketch 08 is the direction, decided 2026-08-16. The ring was doing the rose's job again, and the hull holds the convergence of the rhumb lines without it. This stays on the sheet as the alternative that was drawn and looked at.
A fluid demonstration can hide brittle memory, weak authority boundaries and missing recovery. The buyer discovers those absences only after deployment.
The standing rule from the stage stamp's seventh sketch: before writing any label that
speaks in a component's own voice, check it exists in docs/. If it does not,
say plainly that it is a proposal — at the point of introducing it, not when asked.
INFORMATION-ARCHITECTURE.md. AstralMaris,
The Practice, The Observatory,
Architectural Work are its six territories, less About and Contact.
A.1–A.3, E.1–E.4, P.1–P.4 are the plate numbers
the pages already carry. W2 is ming-qiao's stage in
ming-qiao.ts. Commit, branch,
built are the three keys of build-meta.json. The two bearings
are relatedArtifact values, verbatim from the entries' frontmatter.
logKinds — but using it for a link between an entry and a plate is a second
meaning, which may be one too many.
/architecture is missing, at full width, with the rail carrying only the title
block.