Kesita documentation
The repository contains implemented services and incomplete capabilities. Each page states its own scope.
These pages describe Kesita’s implementation and clearly marked target work. Each handwritten page carries a status badge and a scope note:
| Badge | Meaning |
|---|---|
| Implemented | The described capability has code and executable evidence in this repository. This does not certify cloud deployment or production acceptance. |
| Partial | Some described behavior exists; the page names the implemented subset and the gaps. |
| Target | Proposed 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.
| Section | Start here |
|---|---|
| Guides | Run, configure, test and release Kesita |
| Architecture | Actual process boundaries and explicitly marked targets |
| AIX | Implemented assistant behavior and remaining capabilities |
| Database | Current schema, constraints and producer limitations |
| API | Checked-in contracts and transport scope |
| Hermit | Isolated 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.