Tue 7 Jul 2026

◆ v110.0 — Two new surfaces, no duplication Honest read of v110 transmission: ~75% was already-shipped work (schema, relations, addNextLeaf, addCounterProof, MachineJsonLink, HighSignalBadge, Advanced accordion, unlisted default, /for-agents). Re-implementing = duplicate files + regressions. Refused. Genuine new work delivered: — VERIFIED CLAIMS SECTION (5.1) — • New VerifiedClaimsSection component on every moment page. • Shows INCOMING attests_to edges — the missing half of the graph. • RelatedMoments walks outgoing edges (what this moment points at). VerifiedClaimsSection walks incoming (what points at this moment). • Renders counter-proofs and attestations differently (red vs green edge). • The surface journalists, scientists, artists actually need: 'here is my claim, and here are the sovereign witnesses to it.' — ACTIVE BRANCHES (5.2) — • New ActiveBranches component embedded at the top of /discover. • Filters recent public moments by leaf_count >= 2 OR relations >= 2. • Ranks by (leaves*2 + rels) — leaves count double, deeper signal. • Shows only moments the network is actively co-writing. — STORY POSITIONAL POLISH (1.3) — • ContinueStoryButton lifted to the primary action slot on MomentPage. • Now sits immediately below the Bitcoin proof, before Story Evolution / branch map. • Continuation is the primal act — it should feel like the obvious next step, not buried. Refused (with reason): • RelationsSection.jsx — duplicates existing RelatedMoments.jsx. Same feature, different name = fragmentation. • HighSignalBadge rewrite — v104 version already implements the exact requested logic. • MachineJsonLink re-wiring — already live on every public moment. • Default privacy to 'unlisted' — already the default in v104. • /for-agents rebuild — already excellent, no changes needed. The honest signal in this cycle: half of what looks like new asks are shipped-but-not-remembered. The discipline this build practiced was saying no to duplication.

Not submitted.