STILL: Four Distinct UI Worlds & Zero-Obsidian Architecture

Recreated from the ground up after replacing the generic frontend-design skill with impeccable and studying your aside-relay/DESIGN.md tokens, paired with a live architectural and UI consultation with Claude. Every variation below changes the primary object, home screen, navigation model, and where AI output lives.

1. Four structural worlds, not palette swaps

Compare Relay (bb + aside-relay continuity), Paper (chronological serif journal + margin slips), Desk (4-lane spatial cards + clipped slips), and Workbench (3-pane hairline diff + ⌘K).

2. You do not need Obsidian at all

Use single-file still.db (SQLite WAL + FTS5 + immutable revision trigger) plus a nightly read-only Git .md mirror on your VPS. Zero sync conflicts, zero plugins, zero lock-in.

3. Verbatim capture, explicit AI boundary

Saving, browsing, searching, and editing make 0 AI calls. Refine, Challenge, and Plan run server-side with tools: [] only after payload disclosure, pinned to exact revision IDs.

Four Distinct Aesthetic & Spatial Variations

Claude's sharpest UI test: "Take grayscale wireframes with no text. If you cannot tell the variants apart, they are outfits on one layout." Use the live studio below to test real dictation paste, verbatim save (0 tokens), non-destructive v1 -> v2 edits, the outbound AI disclosure gate, and brief.md export across all four worlds on Mac and iPhone.

Dimension 1. Relay 2. Paper 3. Desk 4. Workbench
Design lineage Your aside-relay + bb mobile/Mac continuity Bear, iA Writer, editorial field notebooks Things 3, Muse, Apple grouped tables Linear, Raycast, Swiss precision tools
Home screen Blank stage with centered 28px frosted composer + 4 recent tiles Today's dated manuscript page ready for prose; older entries scroll below 4 spatial lifecycle lanes (Inbox, Exploring, Challenged, Planned) 3-pane split (Index | Raw Source Diff | AI & Markdown Studio)
Navigation model 288px sidebar on Mac; two-line glass drawer button on iPhone (no tab bar) One vertical chronological scroll with lightweight stage filter pills Position on board on Mac; sliding 4-segment pill switcher on iPhone Keyboard & ⌘K command palette; compact 3-mode switch on iPhone
Where AI output lives Conversational sheets stacked below the locked raw thought bubble Right-hand scholarly margin slips (inline indented slips on iPhone) Stepped physical sub-slips clipped directly underneath the parent card Dedicated right-hand inspector locked side-by-side next to raw diff
Raw vs AI signal Depth & surface contrast over the bb dithered horizon Typeface contrast: human serif prose vs monospace/sans margin notes Spatial hierarchy: white parent card vs recessed stepped attachment slip Column boundary + live word-diff (v1 -> v2) + stale revision pin
Claude's cross-device recommendation

You do not have to force one layout onto both screens

Capture in transit on iPhone and adversarial thinking at a desk on Mac are two different jobs. Because all four variations share the exact same API and SQLite schema, STILL can ship Relay (or Paper) as the default iPhone PWA capture shell while opening Workbench (or Desk) on wide Mac viewports, or let you toggle between them.

How STILL Works Under the Hood

STILL is a small single-owner web service on your personal VPS (personal-vps.example), built with the same self-hosted discipline as aside-relay. Nothing runs in the background, no AI model ever touches your database directly, and no tool inside STILL can execute code or reach company systems.

1. End-to-End Topology & Hard Trust Boundaries

YOUR DEVICES (CLIENTS) iPhone Home Screen PWA 1. Dictate in Phona / Wispr Flow 2. Paste & tap Save (UUID key) 3. Short-term IndexedDB outbox SW caches static shell only Mac Browser Studio Browse, FTS5 search, append v2 Trigger Refine / Challenge / Plan Copy or curl frozen brief.md Cache-Control: no-store PERSONAL OVH VPS (still.personal-vps.example · EUR 4.49/mo) Caddy TLS + Auth WebAuthn Passkeys (x2) HttpOnly SameSite session SSH enroll-link recovery Fastify + Zod API Idempotent raw byte save 1-run-per-idea mutex queue Zero shell / git / fs tools still.db (SQLite WAL) ideas + idea_revisions ai_runs (pins rev_id) artifacts (frozen .md) ideas_fts (FTS5 index) Immutable trigger blocks UPDATE/DELETE on raw text Nightly Git Mirror mirror/thoughts/*.md mirror/runs/*.md mirror/artifacts/*.md + sqlite3 .backup -> age encrypted off-VPS store Read-only, zero lock-in EXPLICIT CONSENT GATE ONLY Anthropic Messages API tools: [] (hardcoded in server) Receives ONLY selected rev_id Server API key (not CLI login) MANUAL EXECUTION HANDOFF bb / Orca / Claude Code You paste or curl brief.md when you choose to build something. No auto-agent inside STILL HARD ISOLATION WALL: ZERO EMPLOYER OR EXTERNAL EXECUTION COUPLING No company Tailscale · No company Notion · No reuse of employer Claude org login · No GitHub tokens or repo mounts on STILL

Dashed amber arrow = fires only when you click Authorize in the disclosure sheet. Dashed green arrow = manual Markdown handoff initiated by you on your own machine.

2. Why SQLite Pins revision_id Instead of idea_id

ideas id: "th-01" (UUID) stage: "planned" client_key: idempotent Organizational envelope. Changing stage makes 0 model calls. idea_revisions (IMMUTABLE) rev v1: exact pasted bytes rev v2: morning edit bytes BEFORE UPDATE OR DELETE: SELECT RAISE(ABORT, 'revisions are append-only'); ai_runs mode: "challenge" pinned_rev_id -> rev v1 prompt_sha + token_audit When rev v2 is added, UI flags "stale: v2 exists" instead of lying silently. artifacts (FROZEN) kind: "brief.md" pinned_rev_id -> rev v2 frozen: true (v1) Edits mint artifact v2. Exported to git mirror and GET /a/<id>.md.

Interactive 6-Step Request, SQLite & Privacy Trace

Click each step from initial iPhone dictation paste to final brief.md handoff to see the exact browser behavior, wire payload, SQLite state, and token guarantee.

1. Browser & Device State


        

2. HTTP / Wire Traffic


        

3. SQLite WAL & Mirror State


        

4. Privacy & Cost Guarantee


        

Why Do We Need Obsidian? We Don't: Brainstorm & Claude Consult

We checked your July 2026 thinking-partner notes (obsidian-thinking-partner.md), your November 2026 vault audit, and ran a live architectural consult with Claude. Both reached the exact same conclusion: STILL has zero reason to depend on Obsidian.

Where Obsidian came from

Why Obsidian felt required in July 2026

  • In the Greg Isenberg / Internet-Vin setup, Claude Code ran as a local CLI agent that needed files on disk to read and write. A local vault folder was a precondition for the CLI, not an advantage in itself.
  • Obsidian had to wear five hats at once: phone capture box, sync client, viewer, Markdown editor, and agent scratchpad.
  • What you actually valued in that setup was strict human-vs-AI write separation (AI writes only to agent-output/), explicit /challenge and /graduate passes, and confidence markers on claims.
Why Obsidian hurts STILL

Four concrete headaches you drop immediately

  • No headless VPS sync mess: Your OVH Linux VPS cannot natively mount iCloud Drive (iCloud~md~obsidian) without fragile sync daemons and conflict files.
  • Schema enforcement beats plugin promises: In Obsidian, plugins like Bedrock want to rewrite your notes; in SQLite, an append-only trigger makes mutating raw thoughts impossible.
  • No manual MOC file-count upkeep or qmd breakage: Queries replace hand-maintained *Index.md files and fragile Node/SQLite plugin binaries.
  • Clean credential isolation: Keeps raw brain dumps completely away from personal vault folders that hold keys or sensitive records.
Storage Architecture Atomic Writes & Immutability Search & Provenance 5-Year Survival If App Dies Verdict
Option A: still.db (SQLite WAL) + Nightly Git .md Mirror Single ACID transaction; SQLite trigger rejects UPDATE/DELETE on raw revisions. Built-in FTS5 (unicode61) in same DB file; zero index drift; real foreign keys to revision_id. Nightly script exports deterministic mirror/thoughts/*.md and artifacts/*.md into a plain Git repo. Recommended (Claude + BB)
Option B: Plain .md Folder Primary + Disposable SQLite Index Requires custom temp-file-and-rename locking; filesystem cannot natively enforce append-only revisions. Provenance lives in YAML frontmatter conventions; FTS5 index can drift from files if edited externally. Files are primary on disk from second zero (rg, cat, rsync). Viable runner-up
Option C: Obsidian Vault + Sync Daemon Sync conflicts on mobile offline edits; plugins can mutate raw human notes. Requires manual MOC upkeep or brittle community plugins. Plain Markdown, mixed with .obsidian/ plugin config churn. Drop completely

Safeguard 1: Safe Live WAL Backups

Never back up a live WAL SQLite database with plain cp still.db, which can miss uncommitted WAL frames. Run sqlite3 still.db ".backup /tmp/still-snap.db" (or Litestream), encrypt with age, and push off-VPS.

Safeguard 2: Elevator / Tunnel Capture Outbox

Write pasted dictation to a tiny short-term IndexedDB outbox with a client-generated UUID before POST /api/ideas. Retries on flaky mobile data never lose text and never create duplicate rows.

Safeguard 3: Raw Bytes vs Diacritic Search

Store exact UTF-8 bytes in idea_revisions.raw_text without trimming or normalizing, while configuring FTS5 with unicode61 remove_diacritics 2 so English and German queries both hit cleanly.

Safeguard 4: Two Passkeys + SSH Enrollment Escape Hatch

On a single-user passkey app, losing one device must not lock you out. Register both iPhone and Mac authenticators on day one, and include an SSH-only CLI (still-cli mint-login) on the VPS.

Two Decisions to Lock In Before Building

Decision 1 · UI World

Which aesthetic posture should STILL build?

  • Option 1A (Paired default): Relay on iPhone for thumb-first capture + Workbench on Mac for side-by-side diff & Challenge review.
  • Option 1B (Single world everywhere): Pick one of Relay, Paper, Desk, or Workbench across both devices.
Decision 2 · Zero-Obsidian Storage

Confirm storage engine on personal-vps.example VPS

  • Option 2A (Recommended): still.db (SQLite WAL + immutable revision trigger + FTS5) + nightly read-only Git .md mirror.
  • Option 2B: Plain .md directory as primary write target + disposable SQLite FTS5 index.