A design kit, reviewed by Fable 5.1

agent

+0:38

[redacted: pack files]

I've read the settled decisions and all twenty-two stills. Here is the review.

The stills, in order

The first still, the Bench in light tone, is the kit's thesis page, and most of it lands. One dark plane runs down the left, meets the paper along a single slanted edge with a red sliver, and nothing else on the page competes with that edge. The designation sits huge at top left in Space Grotesk, the eval result lands on a red plate beside it, and the run list on the right is a column of numbers that reads at a glance. The marks on this page have jobs: the forked-from Y before the base model, the overlaid-runs ring before the loss axis, the hanging minus on the negative readings. Two things do not hold. The rule says seven-segment digits are for live readings only, yet this is a finished run, the footer says nothing is live, and every reading on the page is seven-segment. And a short red tick sits at the same position in all fourteen rows of the run list. Nothing names it. It behaves exactly like the score-to-beat mark the owner rejected in round one.

The dark tone of the same page shows what the plane flip costs. The paper goes dark and the plane goes cream, so the identity block, the largest area on the page, becomes the brightest thing on screen. That keeps the rule that the plane is the page's opposite, and the red plate on cream is handsome. But a training dashboard is the kind of page someone watches at night, and this dark mode puts a bright slab across a third of it. The run list inverts cleanly, and the selected row becomes a light plate on dark, which still reads as the one chosen thing. The loss chart's line changes colour as it crosses the cut, white on the plane and black on paper, which is the first sign that data, unlike text, has no rule about crossing.

At ultrawide width the cut becomes spectacular and the content does not grow into it. The eight readings spread into a two-row grid and leave a void beneath them that runs the width of the chart. The epoch tabs stretch to several times their natural width with the value hugging the left end, so each tab is mostly empty plate. The loss chart stretches the same twenty-eight points into long flat segments. The run list stays pinned to the right at its narrow width, which is right, but it leaves the middle of the screen as the least useful part. The page proves the cut scales. It does not yet show what a wider Bench is for.

The phone still is the honest test of "flat and small", and the shapes pass. The straight dark band at the top carries the designation, the slanted red plate below it still reads as a plate with both cut ends showing, and the run list at the bottom keeps its numeral column and its dark selected row. The chart sits wholly on paper, so nothing crosses a cut. The epoch strip changes lockup, tag above value instead of beside, which is acceptable but undocumented. The header does not pass. The chips for sample data and standby share the key's slanted shape with the replay action, and on a phone they wrap into a second row of what look like six buttons, of which one is a button. The line "This page updates by itself" sits orphaned under them.

The landing sheet shows the whole sequence at roughly 130 ms per frame and it mostly matches the words. The sweep reveals left to right, the small plate appears near the title, grows out of it into the big commit plate with the result in red seven-segment, holds for about nine tenths of a second with the page stepped back, then leaves and the result sits on its red plate. The three beats are there. What the frames also show is a pink wash and red construction rules over the unrevealed areas from the very first frame. That is a visible thing before the sweep arrives, which the round-six rule forbids, and it is the kind of page-plumbing display the owner rejected elsewhere. Either the pink is the intended unscanned tint and the kit should say so, or it is a bug.

The run-list sheet shows hover, lock-on and the commit on a click. The row lifts to a lighter plate, a preview card appears under the list, the click inverts the row, and the same plate grows out and holds before the page becomes run seven. The grammar is consistent with landing, which is the point of "one sequence". Two things weaken the sheet. The preview card reads plus or minus zero because the hovered run ties the selected one, so the preview shows nothing new, which rule sixteen says it should not do at all. And the commit on a list click is the same full takeover as landing, nearly a second with the page dimmed, for an action a user will repeat many times in a session.

The Claviger tracker in light tone is where the surface ladder earns its place. A sunken band holds the stage cards, raised cards sit on it, the current stage sits on the plane, and the page has depth without a single shadow. The stage markers read instantly: quiet numerals for done, a dark plate for current, an outline for upcoming. The waiting rings, the warning edges on medium issues, the depends-on mark under stage six and the count lockup all have jobs a reader can name. The cut does not. The dark header band ends against a raised card, so the one big gesture is a sliver of red and plane visible through a gap of a few dozen pixels. The activity rail labels stack so that stage three sits above stage two. The small filled diamond before "1 to decide" is near enough to the milestone diamond on the rail to risk two meanings for one shape. And the bottom-right column is a header with nothing under it.

The dark tracker inverts the same page and reads as well, with the same brightness caveat as the Bench. The header band becomes a cream slab with the layered-sheet ornament more visible on it, and the current stage card becomes light on dark. The to-decide highlight becomes a black panel inside a dark raised card, which is the one place the ladder's steps get close enough to blur.

The lowmarch tracker is the kit's strongest proof and its most useful failure. Seven stages, built from a scratch copy, and the kit holds: the dotted rail segment for a later stage is a good invention that the kit document does not yet describe. The failure is semantic. Stage five is in progress with a heavy outlined marker, stage six is deferred, and stage seven is the open stage on the plane marked "Next". The loudest marker is on the stage where no work is happening. The settled rule says current is loudest, but "current" meant two things here and the kit has only three states. The narrow cards also show the waiting-ring lockup breaking down: a question wrapped over five lines in a column a few words wide.

The personal site in light tone keeps its locks. There is no big name, the newest write-up gets room and the feed rows beneath it are single lines, the contact sits at the bottom, and the cut runs full height between two sides of equal standing. Then the colour rule gives way. Every outbound link carries a small red arrow, around two dozen of them, so red is the most frequent colour on a page whose one commit is a red feed label. The hexes beside the section heads count items that are visible by looking down. The email is red text that is neither a commit nor a warning. The lower half of the dark plane, between the links and the contact block, is empty apart from ornament.

The dark personal site flips the plane cream, with the chevron sheets now visible on it, and otherwise repeats the light page's strengths and problems. The red arrows on dark are more prominent, not less.

The phone version of the site keeps the right order. Introduction, the lately rail and all-updates key, feed, orgs, projects, repos, contact. The feed drops its dates, which is a fair loss. The all-updates key wraps its label onto two lines, which a key should never do. The contact header sits directly against the last repo rule with no gap, where every other section has one.

Scene Convert's light tone is a dark page. The tool is the plane, the plane is the page's opposite, and the plane covers everything, so a user who chose light gets a page that is dark top to bottom. The settled decisions ask for a cut per page, and here the cut is a horizontal red rule with the same surface above and below it, which is not a cut by the kit's own anatomy. The kit also says a tool and its help are two sides of equal standing and get a full-height cut. The uploaders are headed by framed numbers used as step markers, which rule eighteen excludes by name. Red leaks into a result count, the output hexes, the download arrows and a warning count. What does work is the tool-first order, the reference under section caps, the sample-project key and the result row's lockup of name, direction and downloads.

Scene Convert's dark tone is a cream page with the same layout, and every observation above transfers. The grey uploader panels and the grey sample key on cream read correctly as panel and key.

The kit document's first part lays out foundations and does the thing design kits usually skip: it gives every surface a token, a hex in both tones, a use and a contrast ratio, and states the one big step between paper and plane. The colour-roles table is equally concrete until it reaches signal red, where the rule becomes a paragraph of exceptions that quietly licenses the cut edge and the outbound arrows. The changelog above it is addressed to "you" and refers to what "you marked". That is a record of the rounds, not a spec another project can take.

The second part gives motion real numbers: one curve, grow, hit-stop, flash and hold ranges, an explicit reduced-motion rule, and a "when" paragraph that states the whole sequence. The cut and the plate follow the same template of use, don't, anatomy, states and a do/don't pair, and the don't images show real failures like a plate cropped at the screen edge. The hanging-minus note explains behaviour at two widths. This is the best-written stretch of the kit.

The third part covers the key, the stage marker, the selected row and the small plate. The key's four states are precise. The selected-row do/don't pair, one change against four, is the clearest argument in the document. Two gaps. The stage marker lists three states while the lowmarch proof draws five. And the key's markup uses class names like elk and elu with two empty inline elements for decoration, which no new project can read or maintain.

The fourth part is the marks table, and the "where it's used" column is the kit's enforcement mechanism for earned decals. It also exposes that stopped-by-hand and the budget dial are not used anywhere, and the drawn examples that follow are clean at the sizes shown.

The fifth part adds the round-two marks, five of which are marked not used yet, then the seven-step "apply it to a new project" sequence and the starter theme file. The seven steps are the right skeleton and too short to carry a stranger through a new page. The theme file is complete but minified into three lines. The quiet-gap note admits the threshold was set to the sample data.

The sixth part is three thumbnails, as published, kit v1 and kit v2, with two large keys beneath. The strip makes the case for the surface ladder better than any paragraph, and the keys at large size are the key at its best.

The last still, the marks in use, is a grid of twenty-six marks with their meanings. It makes the ring problem visible in one place: open arcs, a heavy ring, a ring with an hourglass, a ring with two quarters, overlapping rings, linked rings, a hex ring and a dial. Eight ring-shaped marks under a rule that says no new rings, several of which will be indistinguishable at the thirteen pixels the kit specifies. The hex sample shows one red hex with no rule naming it. The marks still carry sheet ids like ornament-13 where they need names.

The settled decisions

Signature versus spectacle, keep. The landing sheet's thumbnails are three hundred pixels wide and the page is recognisable in every one of them by its cut and plate alone. The register, keep, with the note that the stills honour it as inspiration: the stamped commit and the dossier-like stage cards carry the feel without quoting anything. Shapes and motion as the giveaway, keep, because the phone stills prove it. The four rejected directions, keep, and hold the scan against the fourth one, since its construction-line frames come closest to dramatising plumbing. The bar of one strong gesture and no fine-line detail, keep, and turn it on the marks inventory, which is now where the fine-line detail lives.

Type, keep the faces and revisit the seven-segment rule. Either the rule means readings from a run, live or recorded, or the Bench needs a plain-digit variant for finished runs. The surface ladder, keep without reservation. It fixed the owner's complaint and the comparison strip proves it. Signal red's three jobs, revisit. The stills count at least ten jobs across the four surfaces. The fix is to write the cut edge in as a fourth structural job, then remove the outbound arrows, the red hexes, the red counts and the red email, so the commit is red again by contrast.

The cut, keep on the Bench and the personal site, revisit on the trackers and Scene Convert. The tracker's cut is hidden behind a card and the converter's cut has no angle and no tonal change. C the key, keep, and settle a rule for status chips so sample data and standby stop wearing the key's shape. The commit gesture, keep the gesture and revisit its scale for in-page commits. Landing earns a takeover. Picking a run from a list should grow the plate from the row without dimming the page for a second. Scan, revisit until the pre-sweep pink wash is either named or removed. Lock-on, keep. "Only where you can act" is the best rule in the kit, and the tie-score preview just needs rule sixteen applied to it. One sequence, keep, the two sheets show the same plate doing every beat. Nothing moves at idle, keep, and cut the round-seven hourglass test. The kit already uses a ring with an hourglass for queued, so an hourglass for waiting on a person would make one glyph carry two meanings. Effects follow information, keep, and run it against the hex counts on the personal site.

Decals must be earned, keep, and apply it retroactively: seven marks in the kit are not used on any page, and the kit proper should hold only what a page uses while the rest stays on the candidate sheet. The exclusions, keep, and repair two contradictions in the record. No new rings was set, then two rings were approved in round two. Square frames as step markers were excluded, then Scene Convert used them as step markers. Round one's yeses, keep the activity rail, warning edge, waiting ring, milestone, forked from, depends on, closed and layered sheets, all of which are in use. Move stopped-by-hand to candidates until a run stops. Cut the hover edge, which was meh twice and whose job the row plate now does. Round two's yeses, keep section caps, quiet gap, phase span and overlaid runs, revisit changed, which no data can show yet, and park queued, failing, archived and partial result. Round three's yeses, keep the count lockup, plates on a track, the locked slot and the group rule, cut the readout wedge as the owner's own words suggest, and tighten the cost chips.

The Bench run list, keep, it is the most resolved component in the kit. Name or remove the red tick that appears in every row. The personal site's locks, keep, and revisit the arrow density, the hex counts and the empty lower plane. Scene Convert, revisit as a whole. Tool-first and borrowed tokens are right. The tone inversion, the horizontal rule and the framed-number steps are not. Trackers, keep the direction and the full width, and revisit the stage states so that in progress, open and deferred are three documented things. The whole kit as repeatedly applicable, keep the goal and rewrite the document for a reader who was not in the rounds: a spec in front, the round history behind it, real names for marks and classes.

What's missing

Nothing in the kit is in trouble. No still shows a failed run, a stopped run, a rejected file in Scene Convert or an empty list. The kit defers status colours until a page needs a problem state. A dashboard for training runs will need one on its first bad night, and the red rule should be settled against that case before it is settled against anything else.

Nothing in the kit is live. The Bench's premise is that the page updates by itself, and every still shows a finished run with nothing running. There is no still of digits ticking, of the waiting ring on the Bench, of a new run entering the list, or of what the commit does when the newest thing changes under the user.

Several rules exist without a picture. Reduced motion has a sentence and no still of the landing with stamps applied directly. Focus has a tint value and no still, and a red tint as the only focus cue on a dark plate needs checking. Status chips have no rule. Data crossing the cut has no rule, although the loss chart does it on every Bench still. Dark tone's bright plane is a consequence of a rule, not a decision anyone made.

Two pages are implied and absent. The tracker breadcrumb points to an index of trackers, which is where the archived mark would live. The wide Bench needs a content plan, not a stretch.

And the document itself needs a reader. The changelog talks to the owner, the marks carry sheet ids, the classes are three-letter codes, the theme file is minified, and the apply-it section is seven lines. The kit has done the hard part, which is deciding. The part that makes it reusable is writing those decisions for someone who was not there.