Registry, after the Spine
The Registry was built to answer "what screens does the app have, and how do they fit together." The Spine answers that now. What the Registry alone still does is keep track of files: which file draws which screen, its versions and designs, its states, and whether it's built.
Why it feels tedious
Peregrine's Registry as it stands. Most of what it asks for is scaffolding around one file per folder, and most of it is empty.
30units; 19 hold one screen
≈200readiness checks (up to 7 × 30 units)
0 / 30units with a loop or summary
3 / 49screens with a purpose
1 / 49screens with states
4places actions live: header, strip, footer, Revise bar
Part by part
What each part does, what covers it now, and what I'd do with it.
| Part | Covered by | Verdict | Note |
|---|---|---|---|
| Units and the unit rail Groups files into 30 folders; 19 hold one screen | Spine screens, by tier | Cut | Hidden: units stay in the data (matching reads a game's unit name) but stop being a place you work in. |
| Readiness strip Up to 7 steps per unit, 30 units | What next, one list for the whole app | Cut | Its useful checks — unfiled files, missing states, built links — reappear as What next items. |
| Flows tab 5 flows; 4 are Fault in the Record's 17 steps, none on a screen | Spine › Flows | Cut | Fault in the Record's flows move onto the spine with a rework, or go. |
| Loop tab Loop and summary per unit; set on 0 of 30 | Spine lens: one loop for the app | Cut | Nothing to migrate. |
| Ways in / out (links) 7 links between mockups | Spine › Map | Move | The Map becomes the one record of ways between screens; Place writes ways onto it. |
| Filing new mockups 4 unfiled files; 1 of 6 on every unit's strip | — | Keep | Stays here, and becomes the Registry's main job: every file lands in the table and gets its spine screen. |
| Takes: versions and designs 56 versions; 5 screens with history, 4 alternate designs | — | Keep | Unique to the Registry. Also shown on the Spine's screen panel. |
| Declared states 1 of 49 screens | — | Keep | Unique. Read from the file or declared, per row. |
| Built links 0 of 49; Find built screens | — | Keep | Unique. One column. |
| Place this mockup (AI) Reads a file, proposes screens, states, ways in | Rework on the Spine | Move | Re-aimed: its screens become takes of spine screens and its ways in land on the Map. |
| Generate a mockup (AI) For a screen with no file | — | Move | Moves to a spine screen with no mockup. |
| Fill from files / Ask for the rest Purpose, loop, summary per screen and unit | Spine screens already carry Design Studio's purposes | Cut | |
| Revise bar Registry-edit conversation | Spine › Rework | Cut | Boards keep theirs for now; it reads the same data. |
| Canon, frame contract, canon packet In the ⋯ menu | — | Move | To the Mockups ⋯ menu, where the files are. |
The Registry I'd recommend: a table of files
One row per mockup screen, no folders, no checklist. Each row says which spine screen it's a take of, how many versions and designs it has, its states, and whether it's built. New files arrive at the top. The "Spine screen" column below shows the matcher's suggestions for Peregrine's real files (10 close, 9 maybe); nothing is linked yet.
| Mockup screen · file | Spine screen | Versions | States | Built |
|---|---|---|---|---|
4 new files saved to docs/mockups since the last scan | Place… | — | — | — |
Beat the Shakedown peregrine-v3-mockups-with-training-ground.html |
Beat the Shakedown | 1 | — | not built |
Folder Slam kingpin-folder-slam.html |
Kingpin Showdown | 1 | — | not built |
Showdown kingpin-lean.html |
Kingpin Showdown | 2 · 2 designs | — | not built |
Board red-string-live.html |
The Case Board | 3 · 2 designs | — | not built |
Case Board peregrine-case-board-v4.html |
The Case Board | 1 | — | not built |
Case Board Timeline case-board-timeline.html |
The Case Board | 1 | — | not built |
Behind Glass lineup-behind-glass.html |
The Lineup (Game) | 1 | — | not built |
Round View lineup-round-view-v6.html |
The Lineup (Game) | 2 | — | not built |
Training peregrine-v3-mockups-with-training-ground.html |
The Training Ground | 1 | — | not built |
Undercover Gauntlet undercover-gauntlet.html |
Undercover Gauntlet | 1 | — | not built |
File View the-dossier-file-view.html |
Maybe Personal Dossier Unlock? | 1 | — | not built |
Prove It Live the-dossier-prove-it-live.html |
Maybe Personal Dossier Unlock? | 1 | — | not built |
Cold Case cold-case.html |
Maybe The Case Board? | 1 | — | not built |
Drawer Stamp cold-case-drawer-stamp.html |
Maybe The Case Board? | 1 | — | not built |
Prime Suspect Case View prime-suspect-case-view.html |
Maybe The Case Board? | 1 | 5 | not built |
Prime Suspect The Glass That Never Broke prime-suspect-the-glass-that-never-broke.html |
Maybe The Case Board? | 1 | — | not built |
Showing 16 of 49. Clicking a row opens the same takes, states and built link the Spine's screen panel shows.
What changes, and what it touches
Moves out of the Registry
- Flows, the loop and links go to the Spine: Flows, the lens and the Map.
- Place a mockup writes takes and Map ways instead of units and links.
- Generate a mockup moves to a spine screen with no mockup.
- Canon and the frame contract move to the Mockups ⋯ menu.
What depends on the old parts
- Unit and flow boards read units and registry flows. The Spine's section boards replace them; saved boards keep working.
- Boards from the browser land in a screen by matching a unit name. That match changes to spine screens.
- The board view's Revise bar edits the registry. It stays until boards use Rework.
- Fault in the Record's 4 flows (17 steps) need moving to the spine or dropping.
Decisions for you
1. Keep a Registry segment as the file table, or fold it into the Spine?
I recommend the table. It's the concrete layer your nav order already implies, and filing 47 files is faster in a table than one screen panel at a time. Folding it in would leave three segments: Mood Board, Mockups, Spine.
I recommend the table. It's the concrete layer your nav order already implies, and filing 47 files is faster in a table than one screen panel at a time. Folding it in would leave three segments: Mood Board, Mockups, Spine.
2. Fault in the Record's flows: move them onto the spine, or let them go?
They're the only real content in the Registry's Flows tab: 17 steps, none on a screen yet.
They're the only real content in the Registry's Flows tab: 17 steps, none on a screen yet.
3. Styling: the table gets the Spine's treatment (cards, pills, the segmented filter above) in the same pass.