Separate spaces
One operator can create multiple spaces for distinct products or clients. Public content resolution is scoped to a single space slug.
implementedStatic product walkthrough
This page documents the implemented path from writing a document to a searchable reader. It does not depend on a seeded customer space, fake activity, or future capabilities presented as current product behavior.
End-to-end path
Evidence ledger
The product is unreleased and not validated with external users. Implemented means the code path exists, not that production reliability or market fit is proven.
One operator can create multiple spaces for distinct products or clients. Public content resolution is scoped to a single space slug.
implementedA rich Tiptap editor parses and serializes Markdown. Autosave writes the Markdown body to R2 and updates its searchable representation in PostgreSQL.
implementedThe operator changes publication state from the document toolbar. Public routes select published documents and reject private spaces.
implementedPublished spaces include path-based navigation, breadcrumbs, rendered Markdown, and ranked full-text search over published text.
implementedPassword-protected and token-gated unlisted links are central to the intended client workflow. Their authorization and lifecycle are not complete.
plannedA native MCP server and publishing API should let an agent send Markdown and receive a reader link. That end-to-end operation has not shipped.
plannedSee how navigation, publication, and conventional search work.
Understand exactly what R2 and PostgreSQL each store.
Direct answers about pricing, AI, GitHub, access, and release state.