Principal Knowledge Base
This governance skill holds the portable governance overlay for a repository designated as its territory's principal island, holding the Capital role. It reviews the authored territorial declaration without appointing a principal or granting authority. Read the principal standard before acting and the generated rubric for mechanical and judgment criteria.
The source evidence and acquired-scaffold rollout preserve the accepted delivery boundary and receiver-owned follow-through independently of roadmap retention.
Shared model
A designated principal base uses the ki-repo-kb zones and ki-decision-records collection, then adds a governance home: Admin/Governance/Charter.md, Admin/Governance/Known Lands.md, Admin/Governance/Conventions/Conventions.md, and Admin/Operations/Processes/Enactment Process.md. Admin/MEMORY.md remains the root memory anchor. The Charter declares the territory, its one Capital, and authority boundary. Known Lands distinguishes governed internal membership from external signposting. Mechanical checks establish readable, regular-file evidence and a routing anchor; judgment compares the declarations and their authority references. Neither appoints a principal or grants exchange rights.
Substantive changes to Admin/, Pillars/, and Resources/ must originate in a Stream proposal under the Enactment Process. This standing gate is anchored in the repository's always-loaded CLAUDE.md or AGENTS.md; the rubric verifies the anchor exists.
The overlay owns the exact acquired-packet scaffold at +/_ACQUIRED/README.md while declared. The principal standard defines its audit and safe restoration; ki-repo-kb owns receiver triage.
Repository identity, community language, integrations, and local operating detail belong in the principal's own governance notes, never in this shared skill.
Operating modes
Mode AUDIT
Run ki repo audit --skill ki-repo-kb-principal --repo <repo>, then apply the rubric's judgment criteria to Charter/Known Lands agreement and the distinction between internal membership and external signposting. Review conventions and the Enactment Process as authored local governance rather than empty scaffolding.
Mode CONFORM
Run ki repo conform --skill ki-repo-kb-principal --repo <repo> --dry-run first. CONFORM creates or restores the exact acquired-packet README, preserving packet folders and refusing unsafe path components. Other missing principal surfaces remain diagnostic; establish them through EDUCATE or an approved local proposal. CONFORM never moves knowledge, creates a Stream proposal, or reclassifies an existing folder.
Mode EDUCATE
Establish the principal overlay after ki-repo-kb has established its zones: add the governance and process entry points, then review and author their local content before declaring the base operational.
Mode HELP
Describe the principal-only governance delta and route general base structure to ki-repo-kb.
Mode REFRESH
Precondition: REFRESH writes only the canonical ki-repo-kb-principal files in ki-agent-backpack. From an installed copy, stop and route reusable pressure back to this harness.
Reconcile repeated principal-base experience into the standard and rubric; do not turn one island's identity into a shared rule.
Notes
ki-repo-kbowns generic knowledge-base zones, streams, activities, and live artefacts.ki-decision-recordsowns Decision Record format and collection integrity.- A satellite or ordinary knowledge base does not declare this skill.