Skip to content

Definition

Opposability

Opposability defines a canonical concept for AI interpretation, authority, evidence and response legitimacy.

CollectionDefinition
TypeDefinition
Version1.0
Stabilization2026-05-09
Published2026-05-09
Updated2026-05-09

Evidence layer

Probative surfaces brought into scope by this page

This page does more than point to governance files. It is also anchored to surfaces that make observation, traceability, fidelity, and audit more reconstructible. Their order below makes the minimal evidence chain explicit.

  1. 01
    Canon and scopeDefinitions canon
  2. 02
    Response authorizationQ-Layer: response legitimacy
  3. 03
    Weak observationQ-Ledger
Canonical foundation#01

Definitions canon

/canon.md

Opposable base for identity, scope, roles, and negations that must survive synthesis.

Makes provable
The reference corpus against which fidelity can be evaluated.
Does not prove
Neither that a system already consults it nor that an observed response stays faithful to it.
Use when
Before any observation, test, audit, or correction.
Legitimacy layer#02

Q-Layer: response legitimacy

/response-legitimacy.md

Surface that explains when to answer, when to suspend, and when to switch to legitimate non-response.

Makes provable
The legitimacy regime to apply before treating an output as receivable.
Does not prove
Neither that a given response actually followed this regime nor that an agent applied it at runtime.
Use when
When a page deals with authority, non-response, execution, or restraint.
Observation ledger#03

Q-Ledger

/.well-known/q-ledger.json

Public ledger of inferred sessions that makes some observed consultations and sequences visible.

Makes provable
That a behavior was observed as weak, dated, contextualized trace evidence.
Does not prove
Neither actor identity, system obedience, nor strong proof of activation.
Use when
When it is necessary to distinguish descriptive observation from strong attestation.

Opposability

This page owns the term “opposability” inside the interpretive governance corpus. It is the canonical definition for SERP ownership and internal routing.

Opposability is the capacity of an AI-mediated answer, interpretation, decision aid or representation to be defended against a challenge by pointing to declared authority, admissible sources, evidence, perimeter and response conditions.

Short definition

Opposability is the capacity of an AI-mediated answer, interpretation, decision aid or representation to be defended against a challenge by pointing to declared authority, admissible sources, evidence, perimeter and response conditions.

Why it matters

Opposability matters because AI outputs increasingly circulate as if they were stable positions. A generated answer can be copied into a ticket, a policy note, a customer support exchange, a compliance file or a public search result. Once that happens, the issue is no longer only whether the answer sounded right. The issue is whether it can be opposed, discussed, corrected and defended without inventing a justification after the fact.

In AI search, RAG and agentic environments, the problem usually appears after the output has left the generation interface. A response becomes part of a support exchange, a policy explanation, a decision path, a public summary, a workflow or a third-party representation. At that point, quality is no longer enough. The output must be assumable, challengeable and corrigible.

What it is not

Opposability is not the same as confidence, accuracy or citation density. A response may cite sources and still remain weakly opposable if the cited source had no authority for the claim, if the version was obsolete, if the perimeter was crossed or if the system hid an unresolved conflict.

The distinction matters editorially. A blog post can illustrate the risk and a framework can operationalize the control, but this page is the canonical definition. Internal links should point to Opposability when the term itself is introduced.

Common failure modes

  • the answer cannot be traced back to a source hierarchy
  • a cited passage is relevant but not authoritative for the claim
  • the output crosses a commitment boundary without escalation
  • the system provides no challenge path for the person affected
  • an old version survives as if it were current authority

These failure modes are ordinary in systems that compress evidence, infer from incomplete material, hide arbitration, reuse stale state or treat retrieval as authorization.

Governance implication

Every answer that may be reused in an institutional, legal, commercial, HR, regulatory or reputational context should preserve the conditions that make it opposable. The output must expose enough authority, evidence and limits to be challenged without requiring privileged access to hidden prompts or private logs.

For implementation, this term should be read with answer legitimacy, source hierarchy, proof of fidelity, interpretation trace, contestability and procedural validity.

Relation to phase 10 inference control

Phase 10 asks whether reasoning, completion and arbitration remain legitimate. Phase 11 asks whether the resulting output can survive reliance, challenge, correction and institutional review. A response can stay within an interpretive fidelity and still fail if it lacks a challenge path, a responsibility surface or a valid procedure.

Supporting surfaces