Vetrina Gallery Ten pages, ten shapes

Ten pages that a paragraph could not have delivered.

Each one is a single self-contained HTML file, built by an agent that had not seen any of the others, given the finding the page had to carry and never the layout. They are here to show what the window is for: the page is shaped like the task, which is the one thing a dashboard shipped to everybody structurally cannot be.

Real projects, invented data. Gregario, Luxifare and Officina are mine. The incidents, numbers and findings in these pages are made up for the demo. The one page with an outage on it uses a fictional company on purpose.

The pages

10

Ordered so the shape changes every time you scroll. Nothing here loads a font, an image or a script, and every page renders with no network at all.

Luxifare. Thirty-two named concepts scored the move. Four decided it, and two of those pull against each other.

Gregario. Ten thousand voice turns. The middle of the distribution is fine and the entire story is in the tail.

Luxifare. A clear net gain hiding one class of position where it got worse. The aggregate number cannot show this.

Fictional. Two clocks, one axis, and the time lost to the wrong cause drawn as a hole rather than described in a sentence.

Officina. The contract rendered as the document it is, with each rule marked in place against the code that enforces it, and one that nothing does.

Gregario. A ride's writes from signal loss to reconciliation, and the one fork where last-write-wins picked the wrong side.

Officina. Forty-one config files drawn by size and marked by reach, so the mismatch between the two is a picture rather than a sorted list.

Gregario. The same table declared twice, aligned line for line, so a difference is a visible break in alignment.

Officina. Five asides dropped into chat while an agent worked, and what became of each. Two are still unanswered. No chart on this one, deliberately.

Gregario. One question, everything needed to answer it, and nothing else. A hundred and thirteen lines. Most of what the skill says is when not to build a page, and this is what restraint looks like.

How they were made

Ten agents, no shared context, none of them able to see another's page. Each was given the finding its page had to carry and never the layout, because a brief that describes markup has taken the agent's job and the result proves nothing.

They share one stylesheet, which ships with the daemon and is linked in a single line. It owns the frame, the spacing and the type, and deliberately owns nothing in the middle of the page: there is an axis, a track, a bar and a cell, and no component that draws a whole timeline. Whether that worked is checkable rather than arguable, so it was checked. The ten came out between 113 and 579 lines with eight distinct combinations of drawing primitives, and three of them use none at all.

Measured on every page at 320, 390 and 1440 pixels wide in both themes: no page scrolls sideways, none makes a network request, none logs an error, and every number stays readable with the stylesheet removed entirely.