Projects / ki-principal
The canonical record of the Knowledge Islands philosophy and conceptual model.
Knowledge Islands Principal is where the approach is developed and proved before anything is built on it. It holds the philosophy, the conceptual model, and the worked record that shows the model surviving contact with real knowledge work — and it does so without mandating any particular tooling implementation.
Public principal repository · source
The problem
What this is for.
An approach to knowledge work that lives in slide decks and habits cannot be argued with, and cannot be inherited. Knowledge Islands Principal is the opposite arrangement: one public knowledge base where the philosophy and the conceptual model are developed in the open and kept as a living record, so anything built downstream can be traced back to a stated idea rather than to an assumption nobody wrote down.
Whose problem
Whether it is yours.
Read it if you want to understand why Knowledge Islands is shaped the way it is before deciding whether any of the tooling is worth adopting, or if you are working out how to hold your own approach explicitly. It is not a manual, and it will not tell you which command to run.
Capabilities
What it actually does.
- A Philosophy pillar: the island metaphor, the conceptual model, and the realisation material that connects the two.
- A Technē pillar carrying the conceptual tool-ecosystem map the implementation repositories are arranged by.
- An Engineering Practice pillar: the canonical engineering discipline — architecture, operating models and technology posture — adopted from the retired Techne Principal.
- An Aesthetics pillar holding the symbol library, logo, diagrams and visual style this website is built from.
- The ecosystem decision GDR-KI-PRINCIPAL-006, cited across the estate, which fixes who owns what.
- A Streams area carrying the live working record, so the reasoning is visible rather than only its conclusions.
State
How finished it is.
Public and actively developed, in continuous revision rather than versioned releases. The distilled account of the philosophy and the model is published on this site; the repository holds the full working record behind it.
Using it
How to start.
A public Markdown knowledge base. Read it in the repository, or read the distilled account under Philosophy and Model on this site.
Boundaries
What it deliberately does not do.
It mandates no implementation. Nothing here constrains any repository's code, and a change made in Arcadia obliges no tool to follow — KI Specifications exists for the cases where obligation is actually wanted. It is also not a tutorial: there is no getting-started path, because there is nothing here to install.
Authority
What this repository owns.
Canonical source of the philosophy and conceptual model. It informs every other repository and mandates none of their implementations.
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.