Six commitments Sadie will not trade.
Every product is a stack of decisions. Here are the ones that matter enough to state plainly — so the shape of the thing is legible from the outside, not just the inside.
- 01One deployment, one person
Intimacy over tenancy.
A personal wiki is, by its nature, intimate. The sources you feed it, the voice it models, the drafts it holds — none of that belongs in a schema designed for teams. Sadie is single-tenant by construction. No org layer. No row-level security. One deployment serves exactly one person.
- 02Behavioral inference over self-description
Watching is higher fidelity than asking.
Self-description is a lossy codec. Users flatten themselves in forms. Sadie learns who you are by reading what you read, observing what you save, examining how you rewrite. The model of you is editable — but never declarative.
- 03Editorial over infinite
Three, not three hundred.
Today is three briefs per session. Each one earns its place by being live now, being relevant to you specifically, and being conversation you could actually plausibly enter. An infinite feed is a failure mode, not a feature.
- 04Compound over novel
What you keep is what compounds.
The wiki is the compounding artifact. Drafts get filed, entries get cross-referenced, sources get cited. Nothing stays novelty. Every surface runs on the same underlying model of you, and every addition tightens everything downstream.
- 05Read-only on posting
Sadie listens. You speak.
X is a data source. Sadie watches feeds so you know what to say. It does not — and will never — post. The act of saying it, in your words, under your name, remains entirely with you. The saying is the point.
- 06Warm over chrome
The interface should feel handcrafted.
Clay: warm cream backgrounds, Fraunces serif for editorial moments, IBM Plex Sans for the utilitarian work, pressed shadows, pill controls. Sadie should feel like a well-made notebook, not a SaaS dashboard. When in doubt, warm.
These commitments are meant to constrain what Sadie can become. If something tempts a trade — a growth loop that violates read-only, a team feature that splits the schema, a notification surface that becomes a feed — the answer is no, not yet-not-ever.