Skip to content

Kesita documentation

Partial

The repository contains implemented services and incomplete capabilities. Each page states its own scope.

Code and tests

These pages describe Kesita’s implementation and clearly marked target work. Each handwritten page carries a status badge and a scope note:

BadgeMeaning
ImplementedThe described capability has code and executable evidence in this repository. This does not certify cloud deployment or production acceptance.
PartialSome described behavior exists; the page names the implemented subset and the gaps.
TargetProposed behavior without a completed implementation. Its diagrams are design intent.

Open Code and tests below a page title for its source references. Mixed capability pages also identify status per capability. Generated API pages describe contracts and do not inherit an implementation badge.

SectionStart here
GuidesRun, configure, test and release Kesita
ArchitectureActual process boundaries and explicitly marked targets
AIXImplemented assistant behavior and remaining capabilities
DatabaseCurrent schema, constraints and producer limitations
APIChecked-in contracts and transport scope
HermitIsolated integration execution and evidence

Owner pages prevent rules drifting between copies: Storage & indexes owns erasure, Workers & recovery owns stale-worker fencing, and Model gateway owns uncertain paid-call outcomes. Other pages link to these contracts.

Target pages describe intended behavior separately from callable APIs. A capability is available only when its contract and implementation are listed in the relevant API reference.