The LIBRARY Flywheel

Knowledge that knows where it lives,
who owns it, and who can see it.

LIBRARY is the governed knowledge layer for agentic systems. Deterministic discovery, policy-gated access, and a type taxonomy that prevents knowledge drift at scale.

The Problem

Your agents can access everything. They should access exactly what they need.

RAG without governance is a search engine with admin credentials. LIBRARY turns retrieval into a governed operation — scoped, attributed, and auditable.

Ungoverned RAG

Agent embeds everything. Retrieves across boundaries. No ownership model. No access control. Sensitive documents surface in unrelated contexts.

Result: knowledge leaks, stale data, no attribution, no audit trail

LIBRARY

Every artifact has an owner, a scope, and a lifecycle stage. Cross-boundary access goes through Agent Alex. VIGIL gates the response. LEDGER records the retrieval.

Result: deterministic discovery, scoped access, full provenance

The Difference

LIBRARY doesn't restrict knowledge — it routes it. The right knowledge reaches the right agent at the right time, with the right clearance. Nothing more.

Result: agents get smarter without getting dangerous

Ownership

Three scopes. No ambiguity.

All knowledge in ACE belongs to exactly one scope. Routing rules are deterministic — no heuristics, no guessing.

Project-Local

Runbooks, playbooks, SOPs that belong to a single project. Agents read locally — no LIBRARY call needed. Fast, implicit, zero overhead.

Location: <project>/docs/ops/

Platform-Canonical

Standards, doctrine, governance rules, and taxonomy owned by LIBRARY. Cross-project queries go through Agent Alex with VIGIL clearance.

Location: core_reference/docs/standards/TOK/

Cross-Project Initiative

Knowledge shared across projects for coordinated work — incident patterns, protocol specs, shared standards. Scoped views enforced by VIGIL.

Location: core_reference/.../initiatives/

Knowledge Gateway

Agent Alex: the librarian with clearance

Every cross-boundary knowledge request flows through Agent Alex. Alex evaluates clearance, resolves the query, and returns only what the requesting agent is permitted to see.

Agent Alex knowledge gateway flow diagram showing outbound retrieval and inbound intake paths with VIGIL clearance, catalog resolution, and ALDL document lifecycle

Lifecycle

From intake to retirement. Every stage governed.

The ACE Library Document Lifecycle (ALDL) manages artifacts from submission through active use to retirement. No orphaned documents. No stale knowledge.

00 — Incoming

Raw submission. Awaiting classification and cataloging. Source and submitter recorded.

10 — Draft

Classified and typed. Under active development. Not yet discoverable by other agents.

20 — Review

Complete and awaiting review. Quality checks, accuracy verification, ownership confirmation.

30 — Approved

Reviewed and approved. Ready for promotion to active use. Embeddings generated.

40 — Active

Discoverable. Retrievable. Governed. The knowledge is live and serving agent queries.

50/60 — Archived / Retired

Superseded or no longer relevant. Retained for audit trail and historical reference. Not served to active queries.

Knowledge Promotion

Glean from projects. Graft to the platform.

Glean

Harvest mature, battle-tested knowledge from project-local docs. A runbook that survived production is worth more than a standard written in theory.

Graft

Attach gleaned knowledge to the platform-canonical layer with provenance intact. The project origin, author QUID, and promotion date are all recorded.

Compound

Promoted knowledge becomes discoverable across all projects. Agents in different contexts benefit from lessons learned elsewhere. The platform gets smarter.

Taxonomy

One type system. No drift.

LIBRARY owns the canonical type taxonomy for all knowledge artifacts in ACE. Every artifact has a type. Every type has a schema. No "miscellaneous" bucket.

Cognitive

context_pill, memory, skill, standard

Knowledge that shapes how agents think and behave.

Operational

runbook, playbook, workflow, protocol

Knowledge that drives how agents act and respond.

Incident

signature, triage, containment, recovery

Knowledge from HEAL — patterns deposited by every incident cycle.

Governance

metadata, quality, lifecycle

Knowledge about knowledge. The rules that govern the library itself.

The Flywheel

HEAL deposits patterns. LIBRARY makes them discoverable. Next incident — faster.

HEAL — Self-Healing Ops → QUIDxQUID — Agent Communication →

Governed knowledge. Deterministic discovery. Compounding intelligence.