site: tighten stack-wide claims to what the architecture actually guarantees

Reframe claims that a technically-literate critic could fairly challenge,
since a hosted service (BitUnlock, D1-backed) exists in the stack and relay
retention is best-effort:

- "No server of record" -> "No platform-owned source of truth" (state on
  relays, not a platform database; no single operator controls it).
- Drop the impossibility claim "no one can ... delete your history" -> relay
  retention is best-effort; keep your recovery export.
- "No platform to capture" -> "No lock-in" (fork any client, self-host any
  service).

Accurate architectural claims are unchanged (keys never leave the browser,
Tessera never sees your key, ads cannot reach ranking, etc.).

Co-Authored-By: Claude Opus 4.8 <[email protected]>
Claude-Session: https://claude.ai/code/session_01BXQCvJPA6sVSQ5j8uBd9bB

index.html

@@ -34,7 +34,7 @@
       <p class="coord">composable nostr · bitcoin infrastructure</p>
       <h1 class="display">The web made you a tenant. <span class="own">Own</span> the stack.</h1>
       <p class="lede">BitBlocks is a set of composable building blocks for apps that can't lock anyone
-        in — no server of record, no account to close, no algorithm you can't swap. Each block does
+        in — no platform that owns your state, no account to close, no algorithm you can't swap. Each block does
         one thing, signs everything, and runs on open relays.</p>
       <div class="actions">
         <a class="btn" href="#blocks">See the blocks</a>
@@ -155,11 +155,11 @@
     </div>
     <div class="prin-grid">
       <div class="prin"><div class="n">01</div><h3>Signed by substrate</h3><p>Every action is a signed event. Provenance isn't a feature bolted on — it's the storage layer, verified on your device, not taken on a server's word.</p></div>
-      <div class="prin"><div class="n">02</div><h3>No server of record</h3><p>State lives on open relays. Any client can read it; no one can close your account or delete your history out from under you.</p></div>
+      <div class="prin"><div class="n">02</div><h3>No platform-owned source of truth</h3><p>State lives on open relays, not a platform database — any client can read it and no single operator controls it. Relay retention is best-effort, so keep your recovery export.</p></div>
       <div class="prin"><div class="n">03</div><h3>Own the algorithm</h3><p>The feed, the policy, the trust graph, the price — all of it is data you write and swap. No opaque ranking, no locked-in rules.</p></div>
       <div class="prin"><div class="n">04</div><h3>Static-first</h3><p>Each block embeds in a plain static site. The code that decides anything about you runs on your side, where you can read it.</p></div>
       <div class="prin"><div class="n">05</div><h3>Bitcoin-native money</h3><p>Value moves over Lightning and settles cryptographically. Payment is proof, not a promise from a processor that can reverse it.</p></div>
-      <div class="prin"><div class="n">06</div><h3>No platform to capture</h3><p>Vendor-neutral format, vendor-neutral distribution. Fork any client; the network is the events, not the front door.</p></div>
+      <div class="prin"><div class="n">06</div><h3>No lock-in</h3><p>Vendor-neutral format and distribution: fork any client, self-host any service. The network is the events, not the front door.</p></div>
     </div>
   </div>
 </section>