# Kibi

> Prompt the intent. Kibi makes the agent remember it—and prove the implementation.

Kibi keeps product intent, requirements, and their proof in the repository beside the code, so coding agents carry them across sessions and branches. Start with the guide; the reference is the exact CLI, MCP, and schema contract.

## Guide: Start

- [What is Kibi?](https://looted.github.io/kibi/guide/welcome.html): Kibi is an agent-native requirements compiler. It turns product intent into an enforceable model your coding agent carries with it — and proves.
- [Quick start](https://looted.github.io/kibi/guide/quick-start.html): Install Kibi, initialize it in your repository, and let your coding agent bootstrap the project model in one guided step.
- [Installation](https://looted.github.io/kibi/guide/install.html): Install the Kibi packages with your package manager and set up the SWI-Prolog prerequisite.
- [Connect your coding agent](https://looted.github.io/kibi/guide/connect-an-agent.html): Give your coding agent the same Kibi operations you can run yourself, through an MCP server or the kibi CLI.

## Guide: Understand

- [How Kibi works](https://looted.github.io/kibi/guide/how-it-works.html): The loop from human intent to proven implementation — compilation, deterministic checks, and fresh end-to-end evidence.
- [Read the health report](https://looted.github.io/kibi/guide/reading-the-report.html): How to open the requirement-health report and what proven, a proof gap, stale evidence, and a contradiction mean.
- [The proof ladder](https://looted.github.io/kibi/guide/proof-ladder.html): From a stated requirement to fresh end-to-end evidence: the stages a requirement climbs to count as proven.
- [Modeling requirements](https://looted.github.io/kibi/guide/modeling.html): A practical cheat sheet for turning product intent into requirements, scenarios, tests, facts, and code links.

## Guide: Ship

- [Publish requirement health](https://looted.github.io/kibi/guide/github-integration.html): Publish the requirement-health report and badge on GitHub Pages so proof status is visible on every pull request.
- [Troubleshooting](https://looted.github.io/kibi/guide/troubleshooting.html): Recovery procedures for setup problems and broken Kibi state.

## Reference: Commands

- [CLI reference](https://looted.github.io/kibi/reference/cli.html): Every kibi CLI command, flag, and dedicated JSON operation route, command by command.
- [MCP tools](https://looted.github.io/kibi/reference/mcp.html): The canonical MCP tool catalog, onboarding contract, and schemas exposed by the Kibi MCP server.
- [Error reference](https://looted.github.io/kibi/reference/errors.html): Every MCP error code, its meaning, and the recovery path.

## Reference: Model

- [Entity schema](https://looted.github.io/kibi/reference/entity-schema.html): The eight entity types, their fields, and every typed relationship the knowledge graph supports.
- [Inference rules](https://looted.github.io/kibi/reference/inference-rules.html): The deterministic validation, contradiction, and coherence rules Kibi enforces.
- [Symbol traceability taxonomy](https://looted.github.io/kibi/reference/symbol-taxonomy.html): How code symbols are classified and linked to requirements, and what counts as sufficient traceability.
- [Architecture](https://looted.github.io/kibi/reference/architecture.html): Storage layout, branch isolation, and the data flow between the CLI, MCP server, and Prolog engine.

## Reference: Proof

- [Proving requirements](https://looted.github.io/kibi/reference/proving.html): Proof contracts, the kibi prove workflow, and the kibi.proof-run.v1 producer artifact contract.

## Reference: Extend

- [Plugin development](https://looted.github.io/kibi/reference/plugins.html): Extend Kibi with capability plugins: the SDK, manifests, and plugin lifecycle.
- [Agent onboarding](https://looted.github.io/kibi/reference/agent-onboarding.html): The copy-paste discovery snippet that lets any coding agent find and use Kibi's interfaces.