The ecosystem
Every project, and what it is the authority for.
Knowledge Islands is not one program. It is a set of repositories with deliberately separate authority — philosophy, engineering discipline, agentic capabilities, portable standards, command-line tools, MCP adapters, and the infrastructure that delivers them. This page names all of them, says what each one owns, and sends you to the owner.
Only public repositories are listed.
Principal knowledge bases
Where the thinking is kept.
Two repositories hold the ecosystem's reasoning. Arcadia Principal owns the philosophy and the conceptual model; Techne Principal owns the engineering discipline that turns it into buildable practice. Everything else in this list is downstream of them.
ki-arcadia-principal
The canonical record of the Knowledge Islands philosophy and conceptual model.
source
ki-techne-principal
The canonical record of the Knowledge Islands engineering discipline.
source
Agentic capabilities
What an agent is actually given.
A capability is a typed, published thing an agent can be handed — a skill, an agent definition, an MCP server, a hook, an eval. These repositories define what each one contains and how it is delivered to a runtime.
ki-agentic-harness
The canonical source of reusable agentic capabilities and compatible harnesses.
source · /tooling/harnesses/
ki-plugins
A Claude plugin marketplace projecting harness skills and agents onto the Cowork surface.
source
Portable standards
The contracts implementations must keep.
Normative, portable contracts, written only once a concept is proven and implementations have supplied evidence. An Active specification then governs anything claiming conformance within its scope.
Command-line tools
The released executables.
Each released tool has a product page and a stable installer endpoint, both generated from the registry that also pins the version this site recommends. The cards below go to those pages; Tooling explains the contract they share.
ki
The Knowledge Islands command-line interface.
v0.4.0 · preview
mgit
Run commands across many Git repositories at once.
v0.13.0 · preview
git-almanac
Inspect one local Git repository's calendars, authors and reports offline.
v0.1.0 · preview
rig
A declarative description manager for a person's working setup.
v0.2.0 · preview
MCP servers
Adapters onto the systems where work already lives.
Model Context Protocol servers that give an agent bounded access to a real system — a knowledge base, a mail account, a tree of repositories. Each one defaults to read-only, validates every path or identifier it is handed, and hides its destructive tools until an operator opts in. None of them is published to a package registry yet; each is built and registered from source.
mcp-ki-kb-fs
Give an agent scoped read and write access to local knowledge-base directories.
source
mcp-ki-kb-notion-mirror
Mirror knowledge-base notes into Notion for people who do not work in the repository.
source
mcp-git-audit
Audit a whole tree of Git repositories, read-only until an operator says otherwise.
source
mcp-housekeeping-claude
Audit and safely clean the filesystem state Claude applications accumulate.
source
mcp-gsuite
Connect an agent to Google Workspace, with outbound mail confined to drafts.
source
mcp-m365
Connect an agent to Outlook and OneDrive through the Microsoft Graph API.
source
Platform and delivery
How the rest of it reaches a machine.
Infrastructure and transport. These repositories run work, package releases, and publish pages; none of them is an authority on knowledge, capability, or standards.
Why the list is shaped this way
Separate authority is the point, not an accident of history.
The split exists so that a philosophical claim cannot quietly become an engineering mandate, a CLI implementation cannot quietly define a standard, and a page on this site cannot quietly become the source of truth for something it merely describes. Each repository states its own place in the ecosystem near the top of its README, and every card above links to that repository rather than trying to replace it.
This directory is descriptive. It pins no version, hosts no artefact, and redirects no installer — those promises belong to the tooling registry and to the repositories that publish releases.