Commit Graph
2 Commits
Author SHA1 Message Date
thePR0M3TH3ANandClaude Opus 4.8 5443c4eb66 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
2026-08-12 08:37:38 -04:00
thePR0M3TH3ANandClaude Fable 5 34eac32224 BitBlocks umbrella site — the parent identity for the stack
A monochrome, architectural landing tying BitLogin/BitGate/BitFeed/BitUnlock/
Tessera into one message. Parent brand distinct from every product
(Alphabet-to-Google): the five product colours are the only chroma; monumental
condensed Ubuntu Sans display, mono annotation layer, theme-aware. Sections:
tenant->owner thesis, the five blocks, how they compose (Tessera as the worked
example), foundation principles, builders CTA. Static, no build, CSP-locked.

Co-Authored-By: Claude Fable 5 <[email protected]>
2026-08-11 17:21:20 -04:00