InquirySpec - Ontological Boundary: Warrant Gravity is the authority gradient that prevents all retrieved information from being treated as equal. - Not This: Not popularity, confidence score, or citation count. - Doctrine Dependencies: The_Anatomy_of_Action M1.5, Unified Glossary, Persistent_Context.
Working Definition
Warrant Gravity is the authority-gradient behavior of a knowledge system. It names the fact that artifacts exert different normative pull depending on source, scope, review state, governance level, consequence history, currency, and relevance to the action being considered.
A raw trace, a local note, a draft interpretation, a reviewed procedure, a ratified standard, and a consequence log may all be retrievable. They should not all pull action with the same force. A system that can find everything but cannot distinguish warrant will route work as if availability were authority.
Warrant Gravity is therefore not a confidence score. It is not popularity, citation count, semantic similarity, recency, or how often an artifact appears in search. Those signals may matter, but they do not decide what an artifact is allowed to govern. Warrant Gravity asks: what kind of artifact is this, under what boundary was it produced, what review or accountability process supports it, and what action is it permitted to constrain?
The Phenomenological Problem
The ordinary failure is the information equivalency trap.
A search interface returns a policy, a Slack message, a meeting note, a stale draft, a model answer, a ticket, and a postmortem. All of them appear in the same list. The human reader may know they are different kinds of things, but the workflow often treats the list as a flat pool of candidates. The top result becomes convenient. The recent result feels alive. The confident paragraph reads as if it knows what it is doing.
This failure does not require cynicism or conscious distortion. It is systemic gravity. Under time pressure, the artifact that is easiest to retrieve becomes the artifact easiest to act on. The system spends energy finding records but does not spend equal energy preserving their authority layer. People compensate with private judgment, memory, status, and improvisation. Machines compensate with ranking, similarity, or generated synthesis. Neither compensation is enough for governed work.
The danger is especially sharp when agents are asked to act. An agent can retrieve a raw trace and a global standard in the same context window. If the architecture does not mark their relative warrant, the agent may treat both as comparable evidence. It may let a vivid anecdote override a reviewed constraint, or let a stale standard suppress a fresh consequence signal that should trigger repair. Both errors come from the same flattening: the system remembered content but not authority.
The Engineering Anchor
The action anatomy beneath this node treats knowledge as a higher, heavier layer than raw information processing. A query for knowledge creates retrieval load, verification load, and maintenance load. The system cannot honestly pretend that knowledge is a frictionless database lookup. Higher-order artifacts have to be held by lower layers: traces, processing receipts, state metadata, comparison logs, governing constraints, and memory indices.
Persistent memory provides the substrate for this work. Persistent Context keeps artifacts re-enterable by preserving provenance, state, relationships, access boundaries, and retrieval paths. But persistence alone is not warrant. A durable artifact can still be local, stale, partial, low-authority, or out of scope.
Warrant Gravity adds the missing gradient. It lets the system ask whether a retrieved artifact is a raw sensed trace, an interpreted note, a draft model, a current operating commitment, a reviewed procedure, a ratified standard, or a consequence record that should force reconsideration. The point is not to silence low-warrant artifacts. Raw traces matter. Local notes matter. Anomalies matter. The point is to stop the system from confusing their role.
This is why the public graph must become a Stratified Semantic Authority Graph, not merely a vector store or generic knowledge graph. The graph must preserve authority metadata alongside semantic relationships. Retrieval can return candidates; governance evaluates what those candidates are allowed to do.
The link to The Anatomy of Action matters because warrant is action-relative. An artifact does not carry the same force in every situation. A local observation may be enough to open an inquiry, but not enough to impose a global rule. A standard may govern routine execution, but not excuse ignoring a fresh signal that the standard is causing harm. A consequence log may not rewrite policy by itself, but it can require the policy to be reopened.
Boundary Conditions
Warrant Gravity is not a claim that official artifacts are always right. A ratified standard can be obsolete. A reviewed procedure can be mis-scoped. A local trace can reveal a failure that the governing document has not yet absorbed. Authority strata do not remove inquiry; they make inquiry assessable.
Warrant Gravity is also not anti-search. Retrieval is necessary. Search gives the system candidate artifacts to inspect. The failure begins when the retrieval layer is asked to do the governance layer's job. Similarity can help find an artifact, but similarity cannot decide whether the artifact should govern action.
Warrant Gravity is not a moral ranking of people. It ranks artifact force inside a bounded action context. The same person can produce a low-warrant observation, a high-warrant reviewed analysis, and a superseded draft. The artifact's role, review state, scope, and relation to consequence determine its pull.
Warrant Gravity is not permanent. A record can gain warrant through review, corroboration, adoption, or successful use. It can lose warrant when superseded, contradicted, scoped down, or shown to produce harmful consequences. The gradient is maintained, not declared once.
Drill Path
- Stratified Semantic Authority Graph: how authority layers are represented so agents do not flatten traces, commitments, and standards.
- Persistent Context: how artifacts remain re-enterable with provenance, state, metadata, and repair paths.
- The Anatomy of Action: why warrant must be evaluated relative to an intended action, not as an abstract property.
Warrant Gravity is the pressure that keeps available information from pretending to be governing knowledge.