How we build Bladbase

The scan plan (2026-09-20) asked for a photographed handwritten page to become a Markdown page, keeping the formatting a person wrote on paper — # headings, - lists, [ ] tasks, bold, tables ruled by hand — with the ph…

Phase 16 asked three questions that each had a cheap answer and a right one.

Two kinds of page were losing their most useful information because they had nowhere to put it.

Connecting an agent to a workspace was a settings page, a paste into a config file whose shape differs per agent, and a token that reaches the wrong workspace without anyone noticing — the endpoint is one URL for ever…

An approver reading an ADR had two answers: accept, or reject with a note. Neither says "yes, but change the rollback section." That answer went into an ordinary comment, which an agent would never see unless a person…

An editor who opened a page got the editor at once. The server load signed a collab ticket for anyone with page.edit, the client joined the WebSocket room on mount, and the Tiptap bundle loaded — whether the person ha…

A workspace accumulates finished work. Every completed plan, accepted ADR and approved brief stays where it was, and after a few months the page tree is mostly things nobody needs to open. The tree drew no status at a…

The comment record has carried an anchor field since Phase 4, documented as a "ProseMirror/Yjs-relative range anchor; null = page-level thread". Nothing ever wrote it. The web use case and the MCP add_comment tool bot…

The MCP service limits each token to 120 requests a minute, and /developers says so. Until now the counter was a Map in the process, so on Cloud Run the real limit was 120 × the number of instances serving that token…

An MCP token today binds to a human. apiTokenSchema carries a userId, and every request resolves getMember(db, token.workspaceId, token.userId) (apps/mcp/src/index.ts), so an unattended system acts with a real person'…

Bladbase is Firebase-native by design (Strategy §8): Firestore for metadata, Cloud Storage for document content, RTDB for presence, Firebase Auth for identity, Cloud Tasks for async work, Typesense for search. That ch…

PLAN Phase 6 required an explicit choice: reject, or apply API writes as Yjs updates through the collab service. A live room's in-memory Y.Doc is the authority while editors are connected; writing beneath it silently…

The product needs a dense, quiet, keyboard-first UI (Outline/Docmost class) with heavy customization of editor chrome, page tree, and command palette. Most polished component libraries are React-only; the SvelteKit ch…

Strategy §13 calls for authenticated Yjs rooms over WebSockets. Cloud Run supports WebSockets but has properties that could disqualify it: instances are ephemeral, requests have a max timeout (configurable to 60 min),…