← Back to the seven directions

This is the working document behind the seven mockups. Written 2026-09-17 16:15 Beirut, before the seven were built.

Caverio — the synthesis problem

Caverio: the synthesis problem, seven directions

Rook, 2026-09-17 16:15 Beirut. From Thomas’s 16:07 voice note (sequencing register). Status: RUNNING, seven mockup workers, one per direction. Supersedes the rung-letter presentation in REVIEWER-RESPONSE-2026-09-17.md section 6 and the v3 mockups as the direction of the card. The ladder, the case document and the M1 measurement are untouched: this is about what the user sees, not how the builder reads.

1. What Thomas said (16:07)

2. The problem, stated plainly

Per situation we hold about eleven fact streams (case/1): stage and age, cap and its path since first sight, price, liquidity, pool age, covered buys and sells with size vs usual, participant records and shared history, holder exposure, priced net flow per interval, first public call and attention counts, one reader sentence, a comparable and its path, what changed last, and what would change the read. Everything a card needs exists. The failure is not evidence; it is the encoding. Every attempt so far has collapsed the streams into a code (a score in v1, five letters in v2 and v3) and asked the user to learn the code. A trader looking at a card for three seconds will not learn a code. He reads position, motion, and people.

The test for any direction: a trader who has never seen Caverio looks at one card for three seconds and can say what is happening, whether he is early or late, and what he would watch next, without a legend. Then he opens it and finds the depth.

3. Constants across all seven (the correction Thomas asked for)

Every direction keeps, on every card: - Header as on the live card: symbol, chain, pool age, stage pill, a copy-address button, pin. - The big market cap number with the change since Caverio first saw it, and the 30 min (or since-first-seen) cap line from ticks. Price and liquidity under it. - Money in and money out: net flow per interval as bars, from life buckets (cap-scaled interval per the case), with the latest interval labelled. Unpriced or absent flow is drawn as absent, never as zero. - No letter codes. No composite score. No confidence number. No buy / sell / long / short words. Every drawn element is a fact from the case document or its stated unknown. - Palette and type from signal-room/public/caverio.css (dark mineral, serif for the read, mono for numbers). Green only for observed inflow, rose only for observed outflow or an observed exit.

The seven differ in what carries the judgment. Same facts, same nine situations, seven different answers to “what is the synthesis”.

4. The seven directions

# slug the synthesis is… what the eye reads first
1 tape the annotated tape: the cap line since first sight is the spine and every fact is placed on it in time (covered buys as marks sized by ticket, sells, the first public call, the window as a shaded span, flow bars underneath, “now” as a cursor) where am I on the curve relative to the people who were early
2 arrival the order of arrival: a typed event strip (call, first covered buy, second buyer, flow turned in, attention spike, sell, reduce) with real gaps; the shape of the sequence is the judgment (money before attention is early; attention before money is late; sells after entry is deterioration) what came first, and what has not come yet
3 map two questions on a map: “how real” (independent buyers, money in, early holders intact: count of confirmations, 0 to 3) against “how early” (share of the move already made since first sight, window left, attention lag); Strike is the map with nine labels, each card carries its own dot where this sits among the others, in two words each
4 story the story so far: three short paragraphs in plain language with the numbers inline (what happened, what it means, what would change it), the chart small at the right; the sentences already exist in the case document a desk note a human could have written
5 setup the setup sheet: the way a trader plans, filled from facts: context (cap at first sight vs now), what confirms it (what we have, what we are waiting for), what invalidates it, risk facts (liquidity as % of cap, pool age, unchecked holders), the chart and flow; explicitly not a recommendation how complete is the setup, and what is missing
6 race money versus attention: two curves on one clock (cumulative priced net flow; X posts per hour, Telegram mentions, caller calls) with covered buys as ticks; the lead and the gap between the curves are the read is money leading, or is the crowd
7 people follow the people: led by who is in and how they usually do (record, usual hold, size vs usual), whether each is still holding, whether they usually move together; their entries drawn on the cap line who is here, are they still here, do I trust them

Directions 1, 6 and 7 are chart-led. 2 and 3 are structure-led. 4 and 5 are language-led. Each has a failure mode the notes must state honestly (1: crowded on a busy tape; 2: sparse on a one-event situation; 3: the axes are our invention; 4: reads slower than a picture; 5: can look like advice; 6: attention counts are hourly buckets; 7: most Solana buyers have no wallet on file).

5. Deliverables per direction

Under projects/caverio/mockups/2026-09-17-synthesis/d<n>-<slug>/: - index.html: the board, nine cards (the shared nine in ../fixtures/fixtures.js, CAVERIO_FIXTURES.nine), three by three on desktop, one column on a 390 px phone. Clicking a card opens the situation view for that card (in-page panel or situation.html#<key>), which is the same synthesis at full depth, not a different design. - NOTES.md: ten lines. What carries the judgment. What the three-second read gives on each of the nine cards (one line each: what is happening, early or late, what to watch). What this direction cannot show with today’s data. What it would cost to keep live (which endpoints, what cadence). - shots/: board-desktop.png, board-phone.png, situation-desktop.png, situation-phone.png, each under 0.5 MB, captured with a script in the folder (Playwright or Puppeteer, whatever ../../2026-09-17-strike-v3/capture.cjs used), 0 page errors, 0 console errors, nothing wider than 390 on phone. - REPORT.md: standard header, the screenshot table, the three-second test written for the nine cards, the constants checklist from section 3.

Shared: fixtures/fixtures.js (snapshot 16:11 Beirut of /api/case, ticks thinned to 400 points, situation-flow life buckets, social-read documents; people[].wallets and ticketUsd stripped). A worker may read the live API to check a fact but renders from the fixture so the seven are comparable side by side.

6. Hard rules for the workers

7. Comparison

The link (caverio-design-rook.pages.dev) gets a comparison index: the seven boards side by side as thumbnails with the one-line “the synthesis is” from section 4, then each opens full. v3 stays on the index as the letters reference so the correction is visible. Thomas picks pieces; the next iteration is assembled from the picks, not from a vote.

8. What this does not change

The ladder config, the case builder, posture rule v1, the M1 measurement (Strike order against four baselines, freeze Sunday 2026-09-21 00:00) all stand. Posture stays a builder field; whether it appears on a card is a design pick, not a contract question.