Projects / ki-specifications
The canonical source of normative, portable Knowledge Islands contracts.
KIPs, KIS documents, schemas, templates, conformance rules, reference examples, and the portable capability identity and inventory contracts. Specifications formalise concepts once they are proven and once implementations have supplied evidence; an Active KIS then governs every implementation claiming conformance within its scope.
Public standard repository · source
The problem
What this is for.
A convention that exists only inside an implementation cannot be conformed to, argued with, or versioned — the code is simultaneously the rule and the only evidence of it. This repository is where a proven concept becomes a written contract that something else can claim conformance with, and be measured against.
Whose problem
Whether it is yours.
Reach for it if you are implementing something that has to interoperate with Knowledge Islands, or proposing a change to a foundational concept rather than to a single tool. If you want to know how the tooling behaves today, the tool repositories and this site's guidance answer that faster.
Capabilities
What it actually does.
- The KIP series: numbered proposals moving Draft to Review to Accepted, then Implemented once a specification exists.
- The KIS series: the normative specification an accepted proposal produces, moving Draft to Active once there is real implementation experience behind it.
- Schemas, templates, conformance rules and reference examples published alongside a specification.
- A documented process for raising a proposal and stewarding it through review, and registries that track both series.
State
How finished it is.
The process, the registries and the governance are in place; no KIP or KIS document is registered yet. The series start afresh at KIP-000001 and KIS-0001, so today this repository is the mechanism rather than the corpus. It is MIT licensed, text and schemas alike.
Using it
How to start.
Read the canonical documents and schemas in the repository. The corpus is not yet published on this site.
Boundaries
What it deliberately does not do.
It formalises what implementations have already proved rather than designing ahead of them, which is why it is deliberately empty rather than speculatively full. The corpus is not published on this site: with nothing Active, there would be nothing to read.
Authority
What this repository owns.
Canonical source of portable normative contracts. Active specifications constrain the harness and the CLI; neither of them constrains a specification.
That boundary is deliberate. The ecosystem separates philosophy, engineering discipline, capability semantics, portable standards, and executable behaviour so that none of them can quietly absorb another. The full directory shows where this project sits relative to the rest.
Nearby
Other projects of the same kind.
See every public project, or go straight to the released command-line tools.