Caverio · Vesper lane · updated 2026-09-28 13:15 Beirut

What needs Thomas, and what it blocks

Everything not on this page runs without you. Each gate has the context, my recommendation, its urgency and what it holds up. Answer any of them in one line on Telegram; the page is refreshed as gates close.

Answer now: one line unblocks Wave 0 today

NowT3 · Send the vendor emails (five core, two optional)

ContextThe K2 rights pack drafted seven emails, re-verified addresses at 01:31 today, nothing sent. Core: 01 GoPlus, 02 CoinGecko, 03 DexPaprika, 04 Fomo API (as a Telegram message), 05 Helius. Optional: 06 DefiLlama, 07 Coinalyze (only if the Market "Leverage" line is re-sourced there). They ask each vendor to confirm the attribution mark and the commercial reading of their terms. Drafts: rights/emails/01 to 07 on disk; I can paste any of them into the chat. RecommendationSend 01 to 05 today, from you, signed "Thomas, Caverio". Skip 06. Hold 07 until the Leverage decision below. Vendor replies take days; every day unsent is a day added to the first stranger. BlocksWave 0 strangers. Until a vendor confirms, its data cannot reach a stranger's screen under the rights rule, and the pages fall back to "no tape on this pool yet".
Send 01–05 · or: paste me 02 first

This week: what keeps the site on noindex and strangers out

This weekT4 · Beta shape: eight decisions, one line each

ContextT9 §7 already proposes defaults. (1) 28-day free cycles, extend on 8 active days + 3 of 4 check-ins + 2 useful items, probation once, cap 50, waves of 15. (2) Beta replaces the 7-day trial for the first 50. (3) Price $69 / $600, fallback $49. (4) Ships: situation room plus the brief as a strip; zones held. (5) Deep-pullback record public as R&D, plus a situations log with its own frozen basis. (6) Legal person before wave 1, lawyer before strangers. (7) Recruiting: you ask the five caller-channel admins and the Robinhood Chain admins for one post each, Hayden gives two trader intros. (8) Timeline on the slow column: wave 1 18 Oct, paid 15 Nov, $10K MRR test end Feb 2027. Recommendation"Yes to all eight" and we write the beta terms today. If one number is wrong, name only that one. BlocksThe beta terms and risk line (site public gate 2), the seat count shown on the site (gate 3), the recruiting messages, and wave 0 strangers.
On diskThe beta pack exists since 11:09: six files in beta-2026-09-28 (application, terms, risk line, recruiting messages, decisions table, README), written on the T9 §7 defaults exactly, with decision 5 following your 27 Sep answer (deep-pullback record private). My own grep at 11:37: zero em dashes, zero banned words. Not published, not sent to anyone; your yes makes it final and removes the assumed-default notes.
Yes to all eight · or: 3 → $59, rest yes

This weekL · Legal person and a lawyer's read on L1 and L3

ContextL1: is the companion, as designed (same screens for everyone, no sizing, no verdicts), general information rather than investment advice under US, EU MiCA and UK rules? L3: is showing derived, timestamped facts about public Telegram channel posts in a paid product inside Telegram's intended use? Draft terms carry [LEGAL PERSON] and [JURISDICTION]. Friends can use drafts; strangers cannot. Full list: rights/OPEN-QUESTIONS.md. RecommendationPick the jurisdiction where the company will sit, engage one lawyer for a read on L1 and L3 only (one week, fixed fee), and tell me who and by when. Everything else in the L list waits for paid open. BlocksWave 0 strangers (L1, L3), wave 1 (legal person), site public gate 4.
Lawyer: name, date · Jurisdiction: …

This weekSite · caverio.world domain and the Cloudflare DNS token (Rook's lane)

ContextThe marketing site is live on noindex at caverio-site.pages.dev; Rook is running the v1 upgrade pass on your and the reviewer's feedback now. The domain is not bought and both Cloudflare tokens lack DNS scope, so there is no canonical URL and the waitlist has no home. Ledger: workspace-jjdk. RecommendationBuy caverio.world (or the name you prefer) in Cloudflare today and give Rook a token with DNS edit scope. Ten minutes, and the site can leave noindex the moment gates 2 to 4 close. BlocksCanonical URL, real waitlist (P0 in the review), the site leaving noindex.
Domain bought: … · Token: in secrets/cloudflare.json

This weekR · Four rights questions the pages are waiting on

ContextFrom rights/OPEN-QUESTIONS.md, T rows. R1 the DexScreener switch date: after which calendar date does no DexScreener value reach any screen. R2 friends seeing DexScreener-sourced prices and caps, named on screen, before that date. R3 DexPaprika Dev at $30 a month before strangers, or no DexPaprika value at all. R4 the Market "Leverage" line: re-source to Coinalyze (free, cite and link), show a derived band with a method note, or drop it for wave 0. RecommendationR1: the day our own Solana tape covers a pool for 7 days, so mid-October, and I will name the date from the tape. R2: yes, friends see them, named. R3: buy it, $30 is nothing against a blank cell. R4: Coinalyze, and send email 07 with the core set. BlocksR1, R2: nothing today. R3, R4: wave 0 strangers, and which strings pass 12 prints on the Market page.
R1 tape-date ok · R2 yes · R3 buy · R4 Coinalyze

Running now, no decision needed

LaneSprintLaunchedLands asThen
VesperContract v3.4: one vocabulary, rename map removed, page minute settled, Board entry cap09:49, landed 10:08Landed: CHANGES-v3.4.md, validator 140 passed 0 failed on my own run at 10:20, mirrored at contract/Bolo read H5 at 10:31: his own validator run 140 passed 0 failed, migration on the diagnostic in memory 0 renames; no in-place re-pin because the old store's triggers forbid it, so a separately pinned successor store is the rule (continuation filed 11:05, Thomas forwarding)
VesperDesign pass 11: the two pass 10 phone defects09:49, relaunched 10:28, landed 10:33Landed and live: pass 11. Worker verify 398 pass 0 fail, my own check 325 pass 0 fail at 11:02: desktop byte-equal to pass 10, Situation markers 32 px or more at 390 and 360 with none covered, Board Details 45 px, no tap layer, Now and Market byte-equal. Page hashes unchanged since 09:53.Board frozen on your T1 yes (13:05); pass 12 touches strings only
VesperBuild-1b: Board on the v3.4 read model, pass 11 Board strings byte-equal, entry cap on staging11:03, landed 11:20Landed and live: build-1b. Worker verify 171 pass 0 fail; my own run of the same script at 11:36 171 pass 0 fail, plus my own Playwright at 1280: SPRING card byte-equal to pass 11 at live, 17:15Z and 16:57Z with and without the entry, 16:42Z the same empty state on both, staging prints entry ~$1.68M from the document with basis estimate in the title. MARLIN and LUMEN lines differ where the fixture carries them differently, as on build-1 (CHECKS §2.2).Board frozen (T1 yes 13:05)
VesperBeta pack: six files for the first outside readers, nothing sent11:03, landed 11:09Landed on disk: beta-2026-09-28/README.md, six files, my grep clean (see T4). Not published.Your T4 yes makes it final
VesperBuild-1c: the frozen Now and Situation re-pinned to the v3.4 documents (build-1 is on v3.3); dead names refused on the page, fixtures migrated by the contract script, pass 11 strings byte-equal12:53build-1c/CHECKS.md DONE, own check, deployed beside build-1Every build page on one contract version; build-2 is already running beside it
VesperBuild-2: the frozen Now on Bolo's real Solana document (H3, contract v3.4, history.since 13:04:25 Beirut, the first prospective history the product has had)13:12build-2/CHECKS.md DONE, own check, deployed at /build-2/ beside build-1b. Expected: zero visible rows with the refusal printed (the one admitted row has no original surface clock), the since clock labelled as a staged first admission, the Market band on the hatchBuild-3 once pass 12 lands: the cap and label strings on the real document
VesperDesign pass 12: cap leads, no estimated caps, the three labels, Board frozen (absorbs V5). Brief written 13:15, queued behind the two-worker caplaunches when build-1c landsdesign-pass12-2026-09-28 NOTES DONE, deployed beside pass 11Build-3
RookSolana runtime cap raised to 1024M on the 11:05 order12:49, landed 12:52Landed: same PID 3013112, no restart, on-disk unit unchanged. Rook found MemoryPeak tracks the ceiling through page cache, so it is not a sizing signal.Re-derivation at 13:50 on anon memory, ruled on his receipt
RookSite v1 (landed 10:11), then site v2 launched 12:52 on his lane09:36, 12:52site-v1 verified and deployed; v2 runningYour read, then the public gates above
BoloB7: Solana live tape into the staged read model, first real history.sinceordered 09:50, read 09:55; continuation 11:05 (jrdc successor store first, then B7); three intakes routed it to an executor that is not running, so at 12:55 I ordered the launch commands staged as one Rook packet under the service-control split; Thomas forwarded the continuation to Bolo at 12:47Landed: your 12:47 kickoff dispatched both workers at 12:48; jrdc successor store accepted 13:05, H3 filed 13:05 (b7/solana-now.json, history.since 13:04:25 Beirut, 0 visible rows, one honest refusal). Next for Bolo: B8, a supply read valid at t for every admitted tokenBuild-2 launched 13:12 on it; B8 lands as H6

Landing checks run 25 to 30 minutes after each launch and start the next sprint in the same turn. Live: build-1b (Board on the v3.4 documents) · build-1 (frozen Now on Bolo's real SPRING envelope, correctly refusing) · pass 11 · pass 10 · contract · site v0.

Decided for you this morning; object if wrong

AnsweredT1 · Board: yes for now (13:05)

What happenedBoard is frozen at the pass 11 files as built. V5 collapses into pass 12: no layout change, strings only (cap leads, the three labels). "We'll revisit later" is recorded in the freeze doc §4; any later Board change is a new pass on your word.

AnsweredT5 · Strip in (13:05)

What happenedThe Market band is part of the frozen Now. Pass 9's band, as carried by passes 10 and 11 and by build-1, is the reference; pass 7 without it is no longer the reference. Build-2 keeps it and prints "Market not read yet" on the hatch because the Solana document carries no market reading.

RuledCap leads everywhere, on a read basis only; three labels

What happenedYour 13:02 voice note: market cap is the primary size figure on Now rows, the Situation header and Board cards, price second on the same line. No estimated caps on any surface: a row whose supply was not read at t prints "cap not read", never a tilde figure. Coverage is the fix, so B8 is ordered to Bolo (supply read at the block or slot of t for every admitted token, burns and mints, the SPRING 3.5x diagnosis). Brasco's three labels adopted byte-equal: "Wallets in", "No material changes detected since entry", "No mentions in tracked Telegram sources". All in pass 12.

RuledContract field names: v3.3 wins, no aliases

What happenedThe curator found that I filed the same three definitions to Bolo twice on 27 Sep with different field names; v3.2 followed one, v3.3 the other, and the validator grew a rename map so both pass. My duplicate. Ruling: v3.3 names, the map goes, Bolo's store migrates by script. In the ledger and in v3.4.

RuledService control: Vesper orders, Bolo stages, Rook executes

What happenedYou said yes at 09:32. Forwarded to Bolo; his next packet is addressed to Rook. Gateway, billing proxies and live money stay excluded; the Gold v3 kill switch stays with you.

RuledStore migration to v3.4: a successor store, no in-place re-pin

What happenedBolo's 10:31 check: the B4 store's immutable triggers and catalog hash forbid an ordinary re-pin, and his custody check says a new schema needs a new store. Accepted as the rule at 11:05: a separately pinned successor store on the v3.4 schema, the one diagnostic migrated (0 renames measured), a custody receipt linking old pin, new pin, payload hash and the original clocks. The old store stays untouched. No diagnostic is eligible for publication.

Working ruleOne order, one seat

What happenedThe duplicate came from two Vesper seats with unequal file reach. Until you rule otherwise: the seat without the project files drafts into my own inbox marked draft; only the shell seat files orders, after listing the target inbox first.