Projects / ki-techne-principal
The canonical record of the Knowledge Islands engineering discipline.
Techne Principal translates the philosophy into engineering: architecture, operating models, workflows, technology posture, and the implementation patterns the tooling repositories follow. It informs how things are built without owning any repository's executable behaviour or its portable normative contracts.
Public principal repository · source
The problem
What this is for.
AI-native engineering practice is mostly folklore. The conventions live in one person's head, work well, and evaporate when that person moves on — and an agent cannot read a habit. Techne Principal writes the practice down: what the architecture is, how work is run, what the technology posture is, and why each was chosen.
Whose problem
Whether it is yours.
Read it if you are building something in this ecosystem and want to know the patterns before you meet them as audit findings, or if you are building your own and want a worked example of engineering discipline held explicitly rather than by habit.
Capabilities
What it actually does.
- Foundations: the engineering principles everything else here is derived from.
- Architecture: how systems are structured, where boundaries fall, and what may depend on what.
- Operating model: how work is captured, planned, delivered and reviewed with agents in the loop.
- Technology: the posture on languages, runtimes and tools, with the reasoning kept beside the choice.
- The engineering material this site publishes as guidance is drawn from here.
State
How finished it is.
Public and actively developed, revised continuously rather than released. Where this site publishes engineering guidance, Techne Principal is the upstream it restates.
Using it
How to start.
A public Markdown knowledge base. Read it in the repository alongside the guidance published on this site.
Boundaries
What it deliberately does not do.
It shapes implementations without owning them. No executable behaviour is defined here and no portable contract: a repository's own code is authoritative for what it does, and KI Specifications for what it must do. It describes one practice honestly rather than prescribing a universal one.
Authority
What this repository owns.
Canonical source of the engineering discipline. It shapes implementation repositories; it does not define their executables or standards.
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.
ki-arcadia-principal— The canonical record of the Knowledge Islands philosophy and conceptual model.
See every public project, or go straight to the released command-line tools.