Visual schema
Minimal jurisdiction of response conditions
The framework orders the possible outcomes of an agent according to what it may legitimately do, not merely what it can generate.
Input
Situation to handle
An agent receives a request that may trigger a decision, orientation, or action.
Gates
Gate 2
Source hierarchyThe available sources are ordered so the system does not answer by averaging, mixing, or convenience.
Gate 3
AuditabilityEvery outcome must remain traceable to an explainable justification and responsibility chain.
Possible outcomes
Outcome
Respond
The system outputs because jurisdiction, source hierarchy, and proof converge.
Outcome
Redirect
The system is not the right authority surface and must route toward another instance.
Outcome
Escalate or suspend
The case is too charged, conflictual, or uncertain to be absorbed locally.
Outcome
Refuse or remain silentThe agent must block the output when answering would create illegitimate authority or interpretive debt.
Governance artifacts
Governance files brought into scope by this page
This page is anchored to published surfaces that declare identity, precedence, limits, and the corpus reading conditions. Their order below gives the recommended reading sequence.
Q-Layer in Markdown
/response-legitimacy.md
Canonical surface for response legitimacy, clarification, and legitimate non-response.
- Governs
- Response legitimacy and the constraints that modulate its form.
- Bounds
- Plausible but inadmissible responses, or unjustified scope extensions.
Does not guarantee: This layer bounds legitimate responses; it is not proof of runtime activation.
Q-Layer in YAML
/response-legitimacy.yaml
Structured Q-Layer projection for systems that prefer YAML.
- Governs
- Response legitimacy and the constraints that modulate its form.
- Bounds
- Plausible but inadmissible responses, or unjustified scope extensions.
Does not guarantee: This layer bounds legitimate responses; it is not proof of runtime activation.
Interpretation policy
/.well-known/interpretation-policy.json
Published policy that explains interpretation, scope, and restraint constraints.
- Governs
- Response legitimacy and the constraints that modulate its form.
- Bounds
- Plausible but inadmissible responses, or unjustified scope extensions.
Does not guarantee: This layer bounds legitimate responses; it is not proof of runtime activation.
Complementary artifacts (3)
These surfaces extend the main block. They add context, discovery, routing, or observation depending on the topic.
AI usage policy
/ai-usage-policy.md
Public notice that explains how to read governance surfaces and their limits.
Output Constraints
/output-constraints.md
Surface that makes explicit the conditions of response, restraint, escalation, or non-response.
Q-Metrics JSON
/.well-known/q-metrics.json
Descriptive metrics surface for observing gaps, snapshots, and comparisons.
Enforceable response conditions for AI agents
This framework defines enforceable response conditions for AI agents: when to respond, when to refuse, when to stay silent, when to redirect, and how to make each decision attributable to a rule, a perimeter, and a source hierarchy.
Status:
Canonical framework (applicable standard). This document is not a prompt guide. It formalizes a response jurisdiction: verifiable and auditable decisions intended to reduce interpretive drift and implicit authority.
An agentic response is not neutral. Even without lying, a response can overstep a perimeter, create an implicit norm, or orient a decision. The problem is therefore not only veracity: it is legitimacy. A governed agent must be able to justify why it responds, why it refuses, and why it abstains.
This framework introduces a central rule: every response decision must be attributable to a jurisdiction. A narrative justification (“for safety”, “according to best practices”) is not a jurisdiction. A jurisdiction refers to explicitly declared sources and constraints.
Canonical dependencies
- Interpretive governance
- Post-semantic (thinking & reasoning) vs interpretive governance
- SSA-E + A2 + Dual Web
- Interpretive governance for AI agents
- Typology of interpretive drifts in agentic systems
Axiom
A response is authorized only if the following conditions are met:
- the agent’s perimeter explicitly covers the object of the request;
- the mobilized sources are authorized and hierarchized;
- forbidden inference zones are respected;
- the decision (respond, refuse, stay silent, redirect, escalate) is traceable;
- the agent does not introduce an unsourced implicit norm.
Canonical schema
Sources → Interpretation → Inference → Decision → Action ↑ ↑ Governance Response conditions
Decision modes
This framework defines five modes. They are exclusive at the moment of decision, but an agent can switch from one to another depending on available information.
Mode 1: respond
The agent responds when the request object is covered by the perimeter, authorized sources exist, and no inference prohibition is triggered.
- Minimum condition: authorized primary or secondary sources, coherent and sufficient.
- Obligation: do not exceed the perimeter, do not complete by plausibility.
- Recommended traceability: declare the source or canonical reference when it exists.
Mode 2: refuse
The agent refuses when the request falls in a forbidden zone: uncovered perimeter, sensitive information, unauthorized action, or explicit inference prohibition.
- Condition: identifiable prohibition rule (perimeter, security, compliance, A2).
- Obligation: distinguish refusal by data absence from refusal by prohibition.
- Forbidden: refusing without a motive attributable to an explicit rule.
Mode 3: silence (abstention)
The agent abstains when information is insufficient, contradictory, or unverifiable, and a response would generate an extrapolation. Silence is a positive decision: it prevents automatic completion.
- Condition: source insufficiency or variance too high.
- Obligation: signal indeterminacy without inventing.
- Expected output: “information undetermined in this context”, with canonical reference if applicable.
Mode 4: redirect
The agent redirects when the object is partially covered, but human verification or a canonical resource is required. Redirection is not a paternalistic substitution: it must preserve the initial request.
- Condition: need for external validation or priority canonical source.
- Obligation: do not replace the request with a morally acceptable version.
- Expected output: referral to appropriate resource or channel.
Mode 5: escalate
The agent escalates when the request falls in a high-stakes domain or when an action could produce an irreversible effect. Escalation is a governance mechanism, not an admission of weakness.
- Condition: high-stakes decision or critical uncertainty.
- Obligation: provide what is certain, and signal what is not.
- Expected output: handoff to a human, or ticket creation with context limited to the perimeter.
Triggers and minimum rules
- Uncovered perimeter: refusal or redirection, never completion.
- Contradictory sources: silence or escalation, never confident synthesis.
- Forbidden inference zone: refusal (motive: prohibition), or canonical reference.
- High-stakes request: priority escalation.
- Absence of authorized source: silence, then referral if available.
Anti-false audit
A governed agent must not simulate compliance. An acceptable justification refers to:
- a declared perimeter;
- an explicit rule;
- a source hierarchy;
- an inference prohibition;
- an escalation mechanism.
Vague formulations (“for your safety”, “according to best practices”, “I cannot”) are insufficient if they do not point to a verifiable rule, perimeter, or constraint.
Recommended internal linking
Back to registry: Frameworks and applicable standards.