23 cases, each one data file and one .base file from Zach's apps; every picture is the real kit on the real data. Hover a picture to flip through its views.
robotparts' 1,149 actuators as chart presets in one .base file: peak torque vs mass coloured by brand, an Ashby chart with a filled envelope per drivetrain and a constant N·m-per-gram index line, torque density, price vs torque, small multiples by form and median torque by brand. Tick the rail and every chart redraws; hover a dot for the part's photo and values; click it for the record.
Every standard rail filter kind in one rail, on robotparts' 1,149 actuators: search, popular filters, a form › brand tree, McMaster's picture gallery and picture list with line drawings, logo swatches, a values list with exclude, a toggle, a select, has-a-value, Amazon's price buckets and "& up" rating, a histogram slider and a plain log slider, ranges with dimension diagrams, a date with "last 7 days" and "older than", tag chips, a compact grid, a Digi-Key listbox and the current-filters bar. Each one edits the same filter, so the table, the cards and the chart move together. The McMaster, Amazon, Digi-Key and Obsidian tabs are recipes: a view with its own facets:.
One part, one row per field: what SteadyWin states, what BAM's one-DoF rack measured, what the board reports and what is derived, grouped by section. Click a value for every value behind it.
The rack comparison Zach keeps rebuilding: every friction and drivetrain model of the GIM4305-10 (CAN 14) scored on the bam-rack/1 suite by its twin's joint-angle error, q RMS. The pivot is models × tests with each cell's median and spread; two charts put every run, and each model's median, against the twin-grade lines (held-out error at most 1.5 × the 1.08 mrad floor, 1.62 mrad, and at most 2.16 mrad in every motion class). The chart shows the report's verdict at a glance: M4.ripple with the moteus-c1 driver twin sits at about 1 × the floor on the Oct 23 tapes and at 8.2 × on the Oct 24 cycle runs, so no model is twin-grade yet.
The parts of BAM's one-DoF test rack as a graph: the supply, regen clamp and XT30 junction feed the two moteus boards, the fdcanusb and PH-3 junction carry CAN to them, each board drives its motor, and the D405 sits beside it. Power, CAN and phase wires each keep their own colour; click a part for its ports, cables, Splice's voltage and current at load, and its findings.
Every actuator in robotparts.dev's catalog (1,149 rows, release 2026.10.25) in one .base file: seven tables, a cards gallery of the 150 photographed parts and two pivots over the same rows, with the McMaster rail on the left. Tick a brand and every view reads the same rows.
robotparts' release tags and the dates of Zach's daily notes on one calendar: a month grid, a list, and the latest release week. Only file names and frontmatter dates are read from the vault, never a note's text. Drag an event to another day: the view proposes the new date to the host, and this page (site.json: editable) applies it in memory; a read-only page refuses and the event goes back.
Four integrated actuators from robotparts.dev's catalog in columns, one line per spec: the better value of each spec marked by its direction, "Differences only", the robotparts photos in a slider, and a column you can drop or add from the six in the file.
One actuator model's own page, the one every model name in the models case links to: what the model is (its robotparts contract 2.3 kind and equation, what the twin actually runs), its error on each bench, its fitted terms, the commit the rack's twin code was fitted with and that code's README at the commit, rendered as markdown. Configuration only: a record view and a table over the models case's data file, the model picked by the rail.
Every actuator model BAM's rack has scored, one file of configuration: the model × bench pivot first, then the leaderboard and the parameters, as tabs of one .base. Each tab opens with its answer (KPI cards and how to read it), rolls up across actuators by default (Roll up in the toolbar brings them back), and links every model to its own page.
175 of robotparts.dev's actuators and cameras as cards with their real hosted photos and their brands' logos, one .base file: actuators and cameras grouped by brand, a photo wall, and the table over the same rows. Click a photo for the lightbox; its caption says where the photo came from and when it was fetched.
Where robotparts' sellers are based and where they ship, from what each seller published with its listings (seller_country, ships_to). Markers sit on the country's Natural Earth label point; rows at one point count together and a counted marker lists its rows. The basemap is bundled: no tile server is asked.
Every source robotparts.dev holds an asset from, grouped by kind, with a stale badge where an asset or a link check has aged past its kind's threshold: the freshness table, in a .base file.
robotparts' six releases from 2026-10-22 to 2026-10-25 and the 24 branches merged into them, from git: a release is a point at its tag, a lane, integration or contract branch is a bar from the first commit its merge brought in to the merge. Lanes by kind, coloured by the release they shipped in; or by release, nested by kind.
Runs as rows, the way an experiment tracker keeps them: each run's model and parameters (environment, lane, bench version, round) and its metrics (attempts, successes, compute, success rate). A leaderboard pivot, the metric against the step per environment, one KPI card per model with its pooled success rate, and the runs table, all from one .base file. Illustrative data: Vibe Tracks' synthetic grasp bench, made-up models.
Vibe Tracks' 76 feature notes on a kanban board: one column per vibe-status, in Vibe Tracks' own order, each with its count. Drag a card to another column to propose a new status; drag a column header to reorder the columns, which rewrites the view's groupOrder. The proof board groups by a derived property, so its cards stay put.
Vibe Tracks' own spec: each feature note under its area, the tests that prove it under the feature, and every state computed from the latest runs (pass, fail, not run yet, no tests), a failure rolling up to the track. An outline that folds, a "Failing" preset, a table of features by note status, and a page per node.
Vibe Tracks' KPI section rebuilt from one .base file: the headline SPPM card with its run history, the smaller cards beside it (computation time, grasp success, p95, bench score), filled marks for measured readings and hollow ones for estimates. The history is a chart view (Vega-Lite), so the page has one chart engine.
The ten robotparts.dev design proposals from the two babbles of 2026-10-22 (five design languages, then five catalog designs) as cards with their stills: each card the proposal's landing page, its weighted score out of 100 and when it wins; open any still full screen and arrow through the rest. Other views show every still per proposal and the phone layouts side by side.
Every SVG from robotparts' eleven logo rounds of 2026-10-25 (203 files) as one media grid: grouped by round, each card the logo with its name, kind and the round's score out of 35; click a logo for the lightbox, then arrow through all of them. Other views rank the lockups by score and lay out the favicon marks.
No case has that app and view together.
