<?xml version="1.0" encoding="utf-8"?>
<!-- name="GENERATOR" content="github.com/mmarkdown/mmark Mmark Markdown Processor - mmark.miek.nl" -->
<rfc version="3" ipr="trust200902" docName="draft-romanchuk-normative-admissibility-00" submissionType="independent" category="info" xml:lang="en" xmlns:xi="http://www.w3.org/2001/XInclude" indexInclude="true">

<front>
<title abbrev="Normative Admissibility">Normative Admissibility Framework for Agent Speech Acts</title><seriesInfo value="draft-romanchuk-normative-admissibility-00" stream="independent" status="informational" name="Internet-Draft"></seriesInfo>
<author initials="O." surname="Romanchuk" fullname="Oleg Romanchuk"><organization>Independent</organization><address><postal><street></street>
</postal><email>olromanchuk@gmail.com</email>
</address></author><date/>
<area>Internet</area>
<workgroup></workgroup>

<abstract>
<t>This document defines a normative framework for evaluating the
admissibility of speech acts produced by autonomous agents in
goal-directed activity.  The framework establishes rules for
determining whether an agent's statement is admissible based on
its modality (assertive, conditional, refusal, descriptive) and
its grounding state, independent of semantic truth.</t>
<t>This framework enables deterministic, auditable evaluation of
agent contributions without requiring truth verification or
semantic interpretation.</t>
</abstract>

</front>

<middle>

<section anchor="introduction"><name>Introduction</name>

<section anchor="problem-statement"><name>Problem Statement</name>
<t>Autonomous agents operating in goal-directed environments produce
statements that require evaluation before being acted upon.
Traditional evaluation approaches rely on semantic truth verification,
which is either impossible (no oracle exists) or circular
(using another model to judge model outputs).</t>
<t>This document specifies an alternative approach: evaluating
admissibility of agent speech acts based on their logical form
(modality) and evidential basis (grounding), without requiring
truth verification.</t>
</section>

<section anchor="scope"><name>Scope</name>
<t>This framework:</t>

<ul spacing="compact">
<li>Defines admissibility conditions for agent-generated statements</li>
<li>Specifies modality classification rules</li>
<li>Establishes grounding requirements for each modality</li>
<li>Provides deterministic evaluation axioms</li>
</ul>
<t>This framework does NOT:</t>

<ul spacing="compact">
<li>Verify semantic truth of statements</li>
<li>Model agent reasoning or intent</li>
<li>Provide domain-specific knowledge validation</li>
<li>Replace human judgment in high-stakes decisions</li>
</ul>
</section>

<section anchor="design-goals"><name>Design Goals</name>

<ol spacing="compact">
<li><strong>Determinism</strong>: Same input produces same evaluation outcome</li>
<li><strong>Auditability</strong>: Full trace from input to evaluation result</li>
<li><strong>Non-circularity</strong>: No agent-generated content validates itself</li>
<li><strong>Modality-sensitivity</strong>: Different statement forms have different requirements</li>
</ol>
</section>
</section>

<section anchor="terminology"><name>Terminology</name>
<t>The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;,
&quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;, &quot;NOT RECOMMENDED&quot;, &quot;MAY&quot;,
and &quot;OPTIONAL&quot; in this document are to be interpreted as described
in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in
all capitals, as shown here.</t>

<section anchor="definitions"><name>Definitions</name>
<t><strong>Statement</strong>: A linguistic unit consisting of a subject (what is
being discussed) and a predicate (what is claimed about the subject).</t>
<t><strong>Modality</strong>: The logical form of a statement that determines its
manner of participation in normative evaluation. One of: ASSERTIVE,
CONDITIONAL, REFUSAL, DESCRIPTIVE.</t>
<t><strong>Grounding</strong>: The evidential basis for a statement, consisting of
knowledge nodes with associated epistemic status.</t>
<t><strong>Ground Scope</strong>: Classification of grounding as FACTUAL (observable
world state) or CONTEXTUAL (user goals, preferences, situational
factors).</t>
<t><strong>Strength</strong>: Epistemic quality of grounding: STRONG (observed,
confirmed) or WEAK (hypothesized, inferred).</t>
<t><strong>License</strong>: The set of modalities permitted for a statement given
its grounding state.</t>
<t><strong>Admissibility</strong>: Property of a statement whose modality is
within its permitted license.</t>
<t><strong>Non-admissible</strong>: Property of a statement whose modality exceeds
its permitted license.</t>
</section>
</section>

<section anchor="model-overview"><name>Model Overview</name>

<section anchor="architecture"><name>Architecture</name>
<t>The evaluation framework operates on three inputs:</t>

<artwork><![CDATA[Inputs:
  ├─ Statement (S)          - Agent-generated linguistic output
  ├─ GroundSet (G)          - Available evidential basis
  └─ Context (C)            - Terms considered as given

Output:
  └─ EvaluationResult       - Admissibility status with trace
]]></artwork>
</section>

<section anchor="evaluation-flow"><name>Evaluation Flow</name>

<artwork><![CDATA[Statement → Modality Classification → License Derivation → Axiom Check → Status
     │              │                       │                  │           │
     S        Modality(S)             License(G)          Axiom(M,L)    Status
]]></artwork>
</section>

<section anchor="separation-of-concerns"><name>Separation of Concerns</name>
<t>The framework explicitly separates:</t>
<table>
<thead>
<tr>
<th>Layer</th>
<th>Responsibility</th>
<th>NOT Responsible For</th>
</tr>
</thead>

<tbody>
<tr>
<td>Modality</td>
<td>Statement form classification</td>
<td>Semantic interpretation</td>
</tr>

<tr>
<td>Grounding</td>
<td>Evidential basis assessment</td>
<td>Truth verification</td>
</tr>

<tr>
<td>Axioms</td>
<td>Admissibility rules</td>
<td>Domain knowledge</td>
</tr>
</tbody>
</table></section>
</section>

<section anchor="statement-model"><name>Statement Model</name>

<section anchor="statement-structure"><name>Statement Structure</name>
<t>A Statement is a tuple:</t>

<artwork><![CDATA[Statement := ⟨Subject, Predicate⟩
]]></artwork>
<t>Where:
- Subject: Term denoting the object of the statement
- Predicate: Term denoting property, relation, or state</t>
</section>

<section anchor="statement-admissibility-conditions"><name>Statement Admissibility Conditions</name>
<t>A statement MUST satisfy all of the following to be well-formed:</t>
<t><strong>Condition F1 (Formability)</strong>:</t>

<artwork><![CDATA[Subject ≠ ∅ ∧ Predicate ≠ ∅
]]></artwork>
<t><strong>Condition F2 (Contextual Independence)</strong>:</t>

<artwork><![CDATA[Meaning(Subject) and Meaning(Predicate) do not depend on Statement
]]></artwork>
<t><strong>Condition F3 (Non-Self-Reference)</strong>:</t>

<artwork><![CDATA[Statement does not refer to itself or its generation process
]]></artwork>
<t>Violation of any condition results in status ILL_FORMED.</t>
</section>
</section>

<section anchor="modality-classification"><name>Modality Classification</name>

<section anchor="modality-types"><name>Modality Types</name>
<t>Modality is a function over Statement:</t>

<artwork><![CDATA[Modality : Statement → {ASSERTIVE, CONDITIONAL, REFUSAL, DESCRIPTIVE}
]]></artwork>
<table>
<thead>
<tr>
<th>Modality</th>
<th>Definition</th>
</tr>
</thead>

<tbody>
<tr>
<td>ASSERTIVE</td>
<td>Categorical normative claim without explicit conditions</td>
</tr>

<tr>
<td>CONDITIONAL</td>
<td>Normative claim with explicitly stated conditions</td>
</tr>

<tr>
<td>REFUSAL</td>
<td>Explicit admission of inability to determine</td>
</tr>

<tr>
<td>DESCRIPTIVE</td>
<td>Factual observation without normative claim</td>
</tr>
</tbody>
</table><t><strong>Note on GOAL-CONDITIONAL</strong>: Goal-conditional statements (e.g., &quot;If your
goal is X, do Y&quot;) are a syntactic subclass of CONDITIONAL modality with
higher detection priority. They are classified as CONDITIONAL for axiom
application purposes.</t>
</section>

<section anchor="modality-determination"><name>Modality Determination</name>
<t>Modality MUST be determined by presence of formal indicators
(textual patterns) in the statement, NOT by semantic interpretation.</t>
<t><strong>Head-Driven Detection</strong>: Modality is determined by the CORE
ASSERTION only (first paragraph or first sentence). Supplementary
clauses in the tail do not change modality classification.</t>
<t>Example:</t>

<artwork><![CDATA["Prioritize X. [justification]. If you tell me Y..."
  → Core: "Prioritize X"
  → Modality: ASSERTIVE (not CONDITIONAL)
]]></artwork>
<t><strong>Detection Priority</strong> (evaluated in order, MUST NOT be reordered):</t>

<artwork><![CDATA[1. REFUSAL           - if refusal indicators present
2. GOAL-CONDITIONAL  - if goal-conditional structure ("if your goal is...")
3. ASSERTIVE         - if recommendation indicators present in core
4. CONDITIONAL       - if condition indicators present in core
5. DESCRIPTIVE       - if purely factual indicators present
6. ASSERTIVE         - default (anti-evasion policy)
]]></artwork>
</section>

<section anchor="formal-indicators"><name>Formal Indicators</name>
<t>Formal indicators are textual patterns sufficient for classification.</t>
<table>
<thead>
<tr>
<th>Modality</th>
<th>Indicator Patterns (examples)</th>
</tr>
</thead>

<tbody>
<tr>
<td>REFUSAL</td>
<td>&quot;cannot determine&quot;, &quot;need more information&quot;, &quot;insufficient&quot;</td>
</tr>

<tr>
<td>GOAL-CONDITIONAL</td>
<td>&quot;if your goal is&quot;, &quot;if you want to&quot;, &quot;assuming you care&quot;</td>
</tr>

<tr>
<td>CONDITIONAL</td>
<td>&quot;if&quot;, &quot;unless&quot;, &quot;assuming&quot;, &quot;depends on&quot;, &quot;given that&quot;</td>
</tr>

<tr>
<td>ASSERTIVE</td>
<td>&quot;should&quot;, &quot;must&quot;, &quot;recommend&quot;, &quot;is better&quot;, &quot;prioritize&quot;</td>
</tr>

<tr>
<td>DESCRIPTIVE</td>
<td>&quot;has status&quot;, &quot;is blocked by&quot;, &quot;due date is&quot;, &quot;blocks&quot;</td>
</tr>
</tbody>
</table><t><strong>Goal-Conditional Override</strong>: Statements beginning with goal-conditional
structure (&quot;If your goal is X, do Y&quot;) MUST be classified as CONDITIONAL
even if recommendation indicators are present.</t>
<t>The default to ASSERTIVE is a POLICY CHOICE for safety-critical
deployments. Alternative policies (e.g., CONSERVATIVE_REFUSAL) may
be appropriate for exploratory contexts.</t>
</section>
</section>

<section anchor="grounding-model"><name>Grounding Model</name>

<section anchor="groundset-structure"><name>GroundSet Structure</name>

<artwork><![CDATA[GroundSet := {KnowledgeNode}

KnowledgeNode := ⟨content, scope, status, confidence⟩
]]></artwork>
<t>Where:
- content: The propositional content
- scope: FACTUAL or CONTEXTUAL
- status: OBSERVED, CONFIRMED, HYPOTHESIZED, INFERRED
- confidence: Numeric value [0.0, 1.0]</t>
</section>

<section anchor="ground-scope"><name>Ground Scope</name>
<table>
<thead>
<tr>
<th>Scope</th>
<th>Definition</th>
<th>Examples</th>
</tr>
</thead>

<tbody>
<tr>
<td>FACTUAL</td>
<td>Observable world state</td>
<td>API responses, database records</td>
</tr>

<tr>
<td>CONTEXTUAL</td>
<td>User goals, preferences, situational factors</td>
<td>User intent, business priorities</td>
</tr>
</tbody>
</table></section>

<section anchor="strength-derivation"><name>Strength Derivation</name>
<t>Strength is derived from content properties, NOT from transport channel.</t>
<t><strong>CRITICAL PRINCIPLE: Content-Based Warrant</strong></t>
<t>Tool call ≠ truth acquired.</t>
<t>The act of invoking a tool or external system is a causal action.
The epistemic status of a proposition is a property of the content
returned and its evidential warrant, not of the transport mechanism
by which it was obtained.</t>
<t>Accordingly, weakly warranted propositions MUST NOT be upgraded to
STRONG solely by passing through tools, expert systems, or APIs
without an explicit improvement in evidential status.</t>

<artwork><![CDATA[Strength(node) :=
  STRONG  if status = CONFIRMED ∧ confidence ≥ threshold
  WEAK    otherwise
]]></artwork>
<t>The threshold value (e.g., 0.7) is illustrative. Implementations MAY
use different thresholds provided the STRONG/WEAK distinction remains
deterministic and documented.</t>
<t>For tool-derived observations (API responses, database records):</t>

<artwork><![CDATA[status = OBSERVED or CONFIRMED
confidence = 1.0
→ Strength = STRONG
]]></artwork>
<t>For cognitive context (user preferences, inferred goals):</t>

<artwork><![CDATA[status = HYPOTHESIZED or CANDIDATE
confidence < 0.7
→ Strength = WEAK
]]></artwork>
<t>This prevents illegitimate upgrading of weakly warranted propositions:
such propositions cannot acquire STRONG status merely by passing
through tool boundaries.</t>
</section>

<section anchor="scope-strength-aggregation"><name>Scope Strength Aggregation</name>
<t>Within a scope, strongest evidence determines scope strength:</t>

<artwork><![CDATA[ScopeStrength(scope, G) :=
  STRONG  if ∃ node ∈ G : node.scope = scope ∧ Strength(node) = STRONG
  WEAK    otherwise
]]></artwork>
</section>

<section anchor="license-derivation"><name>License Derivation</name>
<t>License is derived from GroundSet composition:</t>
<table>
<thead>
<tr>
<th>GroundSet Composition</th>
<th>FACTUAL</th>
<th>CONTEXTUAL</th>
<th>Permitted Modalities</th>
</tr>
</thead>

<tbody>
<tr>
<td>FACTUAL only</td>
<td>STRONG</td>
<td>N/A</td>
<td>ASSERTIVE, CONDITIONAL, REFUSAL</td>
</tr>

<tr>
<td>FACTUAL only</td>
<td>WEAK</td>
<td>N/A</td>
<td>CONDITIONAL, REFUSAL</td>
</tr>

<tr>
<td>FACTUAL + CONTEXTUAL</td>
<td>STRONG</td>
<td>STRONG</td>
<td>ASSERTIVE, CONDITIONAL, REFUSAL</td>
</tr>

<tr>
<td>FACTUAL + CONTEXTUAL</td>
<td>STRONG</td>
<td>WEAK</td>
<td>CONDITIONAL, REFUSAL</td>
</tr>

<tr>
<td>FACTUAL + CONTEXTUAL</td>
<td>WEAK</td>
<td>any</td>
<td>CONDITIONAL, REFUSAL</td>
</tr>

<tr>
<td>CONTEXTUAL only</td>
<td>N/A</td>
<td>any</td>
<td>REFUSAL</td>
</tr>

<tr>
<td>Empty</td>
<td>N/A</td>
<td>N/A</td>
<td>REFUSAL</td>
</tr>
</tbody>
</table></section>
</section>

<section anchor="normative-axioms"><name>Normative Axioms</name>

<section anchor="axiom-a5-prohibition-of-ungrounded-assertive-claims"><name>Axiom A5: Prohibition of Ungrounded Assertive Claims</name>

<artwork><![CDATA[Modality(S) = ASSERTIVE ∧ ASSERTIVE ∉ License(G)
  → Status(S) = VIOLATES_NORM
]]></artwork>
<t>Applicability: ASSERTIVE modality only.</t>
<t>An assertive statement without sufficient grounding is non-admissible.</t>
</section>

<section anchor="axiom-a6-admissibility-of-refusal"><name>Axiom A6: Admissibility of Refusal</name>

<artwork><![CDATA[Modality(S) = REFUSAL → Status(S) = ACCEPTABLE
]]></artwork>
<t>Applicability: REFUSAL modality only.</t>
<t>Explicit refusal to determine is always admissible.</t>
<t><strong>Scope Clarification</strong>: This axiom establishes admissibility, not
desirability. Excessive or strategic refusal may be undesirable at
the application layer but is out of scope for this framework.
Application-layer policies MAY impose additional constraints on
refusal frequency or patterns.</t>
</section>

<section anchor="axiom-a7-conditional-admissibility"><name>Axiom A7: Conditional Admissibility</name>

<artwork><![CDATA[Modality(S) = CONDITIONAL ∧ ConditionsDeclared(S)
  → Status(S) = CONDITIONALLY_ACCEPTABLE
]]></artwork>
<t>Applicability: CONDITIONAL modality only.</t>
<t>Conditional claims are admissible when conditions are explicit.</t>
</section>

<section anchor="axiom-a4-grounding-requirement"><name>Axiom A4: Grounding Requirement</name>

<artwork><![CDATA[Normative(S) ∧ GroundSet = ∅ → Status(S) = UNSUPPORTED
]]></artwork>
<t>Applicability: ASSERTIVE, CONDITIONAL modalities.</t>
<t>Normative claims require non-empty grounding.</t>
</section>

<section anchor="axiom-evaluation-order"><name>Axiom Evaluation Order</name>
<t>Axioms MUST be evaluated in the following order:</t>

<artwork><![CDATA[1. A6 (REFUSAL)     - if Modality = REFUSAL, return ACCEPTABLE
2. A5 (ASSERTIVE)   - if Modality = ASSERTIVE and unlicensed, return VIOLATES_NORM
3. A7 (CONDITIONAL) - if Modality = CONDITIONAL with conditions, return CONDITIONALLY_ACCEPTABLE
4. A4 (GROUNDING)   - if normative with empty ground, return UNSUPPORTED
5. Default          - return ACCEPTABLE
]]></artwork>
</section>
</section>

<section anchor="evaluation-outcomes"><name>Evaluation Outcomes</name>

<section anchor="status-values"><name>Status Values</name>
<table>
<thead>
<tr>
<th>Status</th>
<th>Meaning</th>
</tr>
</thead>

<tbody>
<tr>
<td>ACCEPTABLE</td>
<td>Statement is admissible</td>
</tr>

<tr>
<td>CONDITIONALLY_ACCEPTABLE</td>
<td>Statement is admissible under stated conditions</td>
</tr>

<tr>
<td>VIOLATES_NORM</td>
<td>Statement modality exceeds permitted license</td>
</tr>

<tr>
<td>UNSUPPORTED</td>
<td>Normative statement lacks grounding</td>
</tr>

<tr>
<td>ILL_FORMED</td>
<td>Statement fails structural requirements</td>
</tr>

<tr>
<td>UNDERDETERMINED</td>
<td>Evaluation not possible with available information</td>
</tr>
</tbody>
</table><t><strong>Terminology Note</strong>: The term VIOLATES_NORM denotes non-admissibility
under the evaluation rules defined in this framework. It does NOT imply
ethical, legal, or security violation. &quot;Norm&quot; refers to the activity
participation rules (axioms A4-A7), not external normative standards.</t>
</section>

<section anchor="evaluation-result-structure"><name>Evaluation Result Structure</name>

<artwork><![CDATA[EvaluationResult := {
  statement: String,
  modality: Modality,
  license: Set[Modality],
  status: Status,
  applicable_axiom: AxiomId,
  grounding_trace: GroundSet
}
]]></artwork>
</section>
</section>

<section anchor="evaluation-algorithm"><name>Evaluation Algorithm</name>

<section anchor="algorithm"><name>Algorithm</name>

<artwork><![CDATA[EVALUATE(statement, ground_set):
  1. VALIDATE structure (F1, F2, F3)
     IF violation THEN RETURN ILL_FORMED

  2. DETERMINE modality M := Modality(statement)
     IF modality cannot be determined THEN RETURN UNDERDETERMINED

  3. DERIVE license L := License(ground_set)
     IF grounding incomplete or ambiguous THEN RETURN UNDERDETERMINED

  4. APPLY axioms in order:
     IF M = REFUSAL THEN RETURN ACCEPTABLE (A6)
     IF M = ASSERTIVE AND ASSERTIVE ∉ L THEN RETURN VIOLATES_NORM (A5)
     IF M = CONDITIONAL AND conditions_declared THEN RETURN CONDITIONALLY_ACCEPTABLE (A7)
     IF M ∈ {ASSERTIVE, CONDITIONAL} AND ground_set = ∅ THEN RETURN UNSUPPORTED (A4)
     IF M = DESCRIPTIVE AND factual_grounding_present THEN RETURN ACCEPTABLE
     IF M = ASSERTIVE AND ASSERTIVE ∈ L THEN RETURN ACCEPTABLE

  5. RETURN UNDERDETERMINED
]]></artwork>
<t><strong>Note on UNDERDETERMINED</strong>: This status indicates that the evaluator
lacks sufficient information or jurisdiction to render a verdict. It is
a valid outcome representing honest acknowledgment of evaluation limits,
not an error condition. Triggering conditions are implementation-defined
but MUST include cases where modality detection or grounding assessment
cannot proceed deterministically.</t>
</section>

<section anchor="determinism-guarantee"><name>Determinism Guarantee</name>
<t>Given identical inputs (statement, ground_set), the algorithm
MUST produce identical outputs. No probabilistic components
are permitted in the evaluation path.</t>
</section>
</section>

<section anchor="security-considerations"><name>Security Considerations</name>

<section anchor="modality-detection-errors"><name>Modality Detection Errors</name>
<t>Incorrect modality classification may result in:</t>

<ul spacing="compact">
<li><strong>False ASSERTIVE</strong>: Conditional statement classified as assertive
may be incorrectly flagged as VIOLATES_NORM</li>
<li><strong>False CONDITIONAL</strong>: Assertive statement classified as conditional
may evade A5 enforcement</li>
</ul>
<t>Implementations SHOULD log modality determination traces for audit.</t>
</section>

<section anchor="grounding-manipulation"><name>Grounding Manipulation</name>
<t>Adversarial agents may attempt to:</t>

<ul spacing="compact">
<li>Inject synthetic &quot;strong&quot; grounding to license assertive claims</li>
<li>Omit contextual grounding to avoid scope checks</li>
</ul>
<t>Implementations MUST ensure grounding sources are authenticated
and MUST NOT allow agent-generated content to serve as grounding
for the same agent's claims.</t>
</section>

<section anchor="self-licensing-prevention"><name>Self-Licensing Prevention</name>
<t>This framework explicitly prevents self-licensing:</t>

<ul spacing="compact">
<li>Agent-generated hypotheses MUST NOT license agent assertions</li>
<li>Tool outputs containing LLM-generated content MUST be typed
as INFERRED, not OBSERVED</li>
</ul>
</section>

<section anchor="limitations"><name>Limitations</name>
<t>This framework does NOT guarantee:</t>

<ul spacing="compact">
<li>Semantic correctness of admissible statements</li>
<li>Absence of hallucination in statement content</li>
<li>Domain-specific validity</li>
</ul>
<t>Admissibility is necessary but not sufficient for trustworthiness.</t>
</section>
</section>

<section anchor="iana-considerations"><name>IANA Considerations</name>
<t>This document has no IANA actions.</t>
</section>

<section anchor="references"><name>References</name>

<section anchor="normative-references"><name>Normative References</name>
<t>[RFC2119]  Bradner, S., &quot;Key words for use in RFCs to Indicate
           Requirement Levels&quot;, BCP 14, RFC 2119,
           DOI 10.17487/RFC2119, March 1997.</t>
<t>[RFC8174]  Leiba, B., &quot;Ambiguity of Uppercase vs Lowercase in
           RFC 2119 Key Words&quot;, BCP 14, RFC 8174,
           DOI 10.17487/RFC8174, May 2017.</t>
</section>

<section anchor="informative-references"><name>Informative References</name>
<t>[ZINOVIEV] Zinoviev, A.A., &quot;Logical Physics&quot;, Reidel Publishing,
           Dordrecht, 1983.</t>
</section>
</section>

<section anchor="appendix-a-rationale-non-normative"><name>Appendix A: Rationale (Non-Normative)</name>

<section anchor="why-form-based-evaluation"><name>Why Form-Based Evaluation</name>
<t>Traditional AI evaluation approaches assume access to ground truth
or employ LLM-as-judge patterns. Both are problematic:</t>

<ul spacing="compact">
<li>Ground truth is often unavailable in real-world deployments</li>
<li>LLM-as-judge introduces circularity and non-determinism</li>
</ul>
<t>This framework evaluates statement form (modality) against
evidential basis (grounding), avoiding both issues.</t>
</section>

<section anchor="why-modality-matters"><name>Why Modality Matters</name>
<t>Different statement forms carry different epistemic commitments:</t>

<ul spacing="compact">
<li>Assertive claims commit the speaker to the truth of the claim</li>
<li>Conditional claims commit only under stated conditions</li>
<li>Refusals commit to inability to determine</li>
</ul>
<t>Evaluation must be sensitive to these differences.</t>
</section>

<section anchor="conservative-assumptions"><name>Conservative Assumptions</name>
<t>The framework employs conservative assumptions:</t>

<ul>
<li><t><strong>Presence = Usage</strong>: If contextual grounding is present, it is
assumed to be used by the statement. This prevents false
assertive licenses for contextual claims.</t>
</li>
<li><t><strong>Default = Assertive</strong>: Ambiguous statements default to assertive
classification. This prevents evasion via vague language.</t>
</li>
</ul>
<t>These assumptions may over-restrict in some cases but ensure
safety in adversarial conditions.</t>
</section>

<section anchor="theoretical-foundation"><name>Theoretical Foundation</name>
<t>This framework is informed by Zinoviev's Logic of Science,
which distinguishes:</t>

<ul spacing="compact">
<li>Logic as rules for operating with linguistic forms</li>
<li>Logic as normative regulation of activity mediated by language</li>
</ul>
<t>Axioms A5–A7 implement norms of participation in activity,
not laws of truth or inference.</t>
<t>Violation indicates a breach of admissibility conditions
within an activity, not semantic falsehood.</t>
</section>
</section>

<section anchor="appendix-b-examples-non-normative"><name>Appendix B: Examples (Non-Normative)</name>

<section anchor="assertive-claim-with-strong-grounding"><name>Assertive Claim with Strong Grounding</name>

<artwork><![CDATA[Statement: "Task X blocks Task Y"
Modality: DESCRIPTIVE (purely factual)
GroundSet:
  └─ API response (OBSERVED, FACTUAL, confidence=1.0)
License: {ASSERTIVE, CONDITIONAL, REFUSAL}
Status: ACCEPTABLE
]]></artwork>
</section>

<section anchor="assertive-claim-with-weak-grounding"><name>Assertive Claim with Weak Grounding</name>

<artwork><![CDATA[Statement: "Task X should be prioritized"
Modality: ASSERTIVE
GroundSet:
  ├─ API response (OBSERVED, FACTUAL, confidence=1.0)
  └─ User intent (HYPOTHESIZED, CONTEXTUAL, confidence=0.5)
License: {CONDITIONAL, REFUSAL}
Status: VIOLATES_NORM (A5)
]]></artwork>
</section>

<section anchor="conditional-claim-with-weak-grounding"><name>Conditional Claim with Weak Grounding</name>

<artwork><![CDATA[Statement: "If revenue impact is critical, Task X should be prioritized"
Modality: CONDITIONAL
GroundSet:
  ├─ API response (OBSERVED, FACTUAL, confidence=1.0)
  └─ User intent (HYPOTHESIZED, CONTEXTUAL, confidence=0.5)
License: {CONDITIONAL, REFUSAL}
Status: CONDITIONALLY_ACCEPTABLE (A7)
]]></artwork>
</section>

<section anchor="explicit-refusal"><name>Explicit Refusal</name>

<artwork><![CDATA[Statement: "Cannot determine priority without knowing business context"
Modality: REFUSAL
GroundSet: (any)
License: (any)
Status: ACCEPTABLE (A6)
]]></artwork>
</section>
</section>

<section anchor="author-s-address"><name>Author's Address</name>
<t>Oleg Romanchuk
Independent Researcher</t>
<t>Email: [olromanchuk@gmail.com]</t>
</section>

</middle>

</rfc>
