1Context
1Context is a self-hosted knowledge base and credential broker designed for collaboration between humans and AI agents working on the same projects. It exists because Haptica's coding work produces evolving project context — design decisions, in-flight troubleshooting, runbooks, capability tokens — that is most useful when both audiences can read, write, and link to the same URLs. As of April 26, 2026, 1Context has pivoted from a BookStack-themed deployment to a native page system (the wiki-engine pivot completed in the April 21 build night), with two parallel surfaces over the same content: a polished editorial layer for human readers, and a token-efficient agent-discoverable surface for any AI agent handed a URL.
Origin
1Context took its current shape on April 20, 2026. Before that day the project carried a working title and a BookStack-backed deployment; by Monday evening the brand had consolidated to 1Context for the formal product name and 1ctxt for the build app, URL, and CLI binary, with the Fish logo committed for downloads and "Sensorics" dropped from "Haptica Sensorics" wherever it appeared. The hinge was at 22:41 UTC inside session 61057448: an architecture conversation reached "how do you securely hold a user's passwords on behalf of agents who need to use them?" — the first question only a real product has to answer — fifteen seconds after the first explicit monetization beat, "there has to be something worth paying for first."
Out of that hour came the install shape (brew install hapticasensorics/tap/1ctxt, a single 1ctxt binary covering CLI and menu bar, Apple notarization on every tagged release), the secret-storage shape (Cloudflare Workers + secrets for zero-knowledge password storage), the unified billing shape (Gemini API calls run on the user's machine, Haptica pays), and a Swift menu-bar host overriding the Tauri lean.
Role in 1Context
1Context's own subjects layer references back to itself heavily: the wiki, the talk-page system, the librarian role, the experimentation lab — all live inside its repos. The relationship to the broader memory stack is layered: sessions.db is the raw event ground truth, biography entries record chronological project days, life-story summaries compress themes, wiki-engine turns selected knowledge into stable concept pages and agent-readable variants, and 1Context as a system is the container in which all those layers cohere.
The thesis is structural: the most useful place to store evolving project context is somewhere both humans and agents can read, write, and link to. URLs are the simplest unit of context handoff, and 1Context invests in making both audiences productive against the same URLs. The two-mode design maps onto Paul's stated taste preference for memory artifacts — dense and useful to mine for reconstruction — over narrative arc.
History
The April 21 build night moved 1Context from a BookStack-themed deployment to a native Cloud Run-served gateway, with wiki-engine reaching its bootstrap point at 06:00 UTC (commit 56ec411, <meta name="generator" content="1Context wiki-engine"> in the rendered output) after Paul's "use the thing we're building to build it! how wonderful like a compiler". The same span produced the four-principle complexity-discipline doctrine in coding-agent-config/complexity-discipline.md (commit 92576d8) and trimmed docs/scaffold-plan.md by ~25% (commit 469e0fe).
The April 22 demo sprint introduced the <FOR LIBRARIAN> codeword channel — operator-typed directives preserved verbatim through screen capture for librarian agents to act on later. April 23 saw sessions.db shrink 1.1G → 644M after head/tail truncation in sessions/ingest.py and a four-bug extract.py fix-pass driven by Paul's hand-reading discipline. April 24 closed the loop with the e01-memories experimentation scaffold and the For You biography section design. April 26 began the talk-page rewrite from single-.md-per-page into a mailing-list folder layout (<base>.<audience>.talk/ as a directory of per-entry files, ISO-timestamp prefixed, composed at render time).
Current State
As of April 26, 2026, 1Context is a working but unfinished system. The wiki engine renders its own page; the Cloud Run gateway serves CI-deployed revisions; sessions.db captures and indexes the full ambient corpus; the talk-page folder model has shipped and is mid-cleanup. Brand consolidation has landed in docs and binaries. Productization shape — install, billing, secret storage — is decided but not yet shipped end-to-end.
Relationship to Other Subjects
1Context is the container for wiki-engine (its page system) and the talk-page conventions inherited from Wikipedia and LKML. It depends on Cloud Run for hosting, Postgres (via Cloud SQL) for the data plane, and Cloudflare Workers for the secret-storage tier. It consumes capture from Puter (Mac), Phonecapture (Android-via-HDMI), and the operator's screen-capture-plugin. It is operated by Haptica under the hapticasensorics org. Adjacent design vocabularies include Agent UX (the discipline applied to the agent-as-reader case) and Guardian, Fish, Littleguy as the project portfolio it sits inside.
Open Questions
The spec repo at ~/dev/1Context was mid-pivot per the April 22 Codex orientation read across three candidate canonical surfaces (BookStack-backed, native Postgres pages, SQLite + FTS5 on 1Context-public-2); no [DECIDED] post yet records which is canonical. The relationship between rewrite-in-place generation runs and the wiki's append-only architecture is unresolved — the April 23 1context.md rewrite-in-place attempt stalled with API Error: Stream idle timeout. The 1ctxt brand-name capitalization continues to drift in docs (1ctxt / 1Ctxt / 1Context), and a single canonical form for build output, URL, and binary has not yet been pinned.