Charter

Why not RAG, a shared doc, or a prompt file?

The most common question we get, answered in one place.

Explainer

AlternativeWhat it does wellCharter distinction
RAG / retrievalFinds relevant informationEstablishes which governed source is authoritative and applicable. RAG optimizes relevance. Charter establishes authority.
Enterprise searchFinds accessible informationApplies entitlement plus governing authority. Access is not authority.
A shared docOne place to lookAdds owner, version, content hash, review cycle, declared dependencies, and enforcement.
Prompt or instruction filesInstructs model behaviorMakes authority, approval, version, precedence, and entitlement explicit governance properties. Prompts instruct. Charter governs.
GuardrailsInspect inputs and outputsEstablishes governing context and governs registered execution. Guardrails inspect. Charter governs.
ObservabilityRecords what happenedPreserves the authoritative resolution behind the trace. Observation is not authority.
GRCDocuments policy and controlsConnects governed policy to the context and execution it governed.
Policy as codeMachine-evaluable decisionsGoverns the human-authored knowledge and decision context around executable policy.
Model or project memoryContinuity and convenienceMakes governing context explicit, versioned, entitled, and reproducible. Remembered is not governed.
Knowledge graphsModels entities and relationshipsResolves, delivers, entitles, versions, and evidences knowledge as part of execution.

Retrieval finds. Identity grants access. Prompts instruct. Guardrails inspect. Observability records. GRC documents. Policy engines decide. Charter establishes what governs.

Explainer

Why this is not retrieval

What happens to a policy answer when chunks come back out of order, and what deterministic retrieval does instead.

Explainer

What is SIGN™

Prose an agent has to interpret, next to the same rule expressed as SIGN™.