The company's memory.
New projects ask what could work. Inherited ones ask what is already true.
Kinbase is being built to answer the second question: a store of what the company has decided, and why, that engineers and coding agents read before they change a line. It is the Company product of the three-store Kindex system, developed in this repository under the name Kinbase. This site is the technical documentation; the pitch and the proof condition live at kinbase.tools.
Status specification ratified · proof of concept not yet run · two candidate amendments in review
Three stores, one engine
personalyour conversations and contextseparate root · never mounted by a coding session
codebasethe repository's .kin/, plain files in gitKindex · read by the session · approved by the maintainer
companydirection, architecture, standards, ownershipKinbase · read by the session · admitted by the steward
Documents
- OverviewWhat Kinbase is specified to do, who holds authority over what, and how a coding session composes the stores.
- Proof conditionsEvery arm and every threshold the proof of concept must meet, in plain words, and what the proof does not claim.
- Amendment registerCandidate amendments to the ratified specification, their status, and what ratification means.
- llms.txtThe machine-readable summary for agents.
- SpecificationThe ratified source of every claim: source request, product, architecture, threat model, verification, and the leak runbook.
- PrivacyThe site sets no cookies and runs no analytics; the notice lives on kinbase.tools.