RJ Clothing · Continuity Register · T008 — prepared for Ró

Forty-four worries.
A handful of stitches that hold the cloth.

Joe may hard-exit Shanghai on ~26 July — staying employed, working remotely (no exact date given). The flat register reads like 44 separate fires. It isn't. Collapse it and you find 8 parent problems, and 7 keystones that each fan out to several at once. Ró has now reviewed all 8 parents himself — open any to read his full analysis. The whole map reduces to two scarce resources — Joe's final month on the ground, and the absence of a trusted non-001 body — and almost every red resolves to spending one or both. Open the Coherence view to see the dependency web. Pull one stitch; watch a row of panels fall into place.

0line items
0parent problems
0keystones
Red Amber Green
Fully resolves Partly mitigates Not yet / unproven
Click a gold keystone to light its fan · click any problem for its source row
Already safe — ignore Continues remotely on existing process. No keystone needed, no action.
Every problem node traces to one RAW v1 register row (quoted on click). Severity = v1 register reconciled with Ró's Round-2 honest re-rank, then OVERRIDDEN by his finalized P1–P8 analyses (open any parent → "Read the founder's full analysis"). Brass ✦ = reviewed by Ró — now ALL 8 parents. ☾ = rare-event item (frequency-discounted). ⚠ = a dated time-bomb / retained RED tail. S6 (the high-end hire) was surfaced from Ró's own words, not the original map. The Coherence view renders the cross-parent dependency web, the keystone→parents fan, and the physical-now checklist for Joe's final month. Open questions on a node = a Ró-only judgment call, surfaced not assumed. Source: /tmp/t008/v1-register-NEW.csv · model: T008-grouping-model.json · analyses: T008-P1…P8-analysis.json · coherence: T008-coherence.json