Inferensys

Glossary

Normative Faithfulness Metric

A quantitative evaluation score measuring the degree to which a generated legal text or reasoning chain accurately reflects the deontic content of its source material without hallucination or omission.
AI evaluator reviewing output quality on laptop, comparison metrics visible, casual evaluation session.
EVALUATION

What is Normative Faithfulness Metric?

A quantitative evaluation score measuring the degree to which a generated legal text or reasoning chain accurately reflects the deontic content of its source material without hallucination or omission.

The Normative Faithfulness Metric is a quantitative evaluation score that measures the degree to which a generated legal text or reasoning chain accurately reflects the deontic content—obligations, permissions, and prohibitions—of its source material without hallucination or omission. It provides a rigorous benchmark for assessing the citation integrity of AI systems in high-stakes legal applications.

This metric typically operates by comparing the deontic graph extracted from a source document against the deontic graph inferred from the model's output, penalizing both the fabrication of non-existent norms and the omission of critical duties. It is essential for validating Deontic RAG architectures and ensuring that automated legal reasoning systems maintain strict alignment with authoritative texts.

MEASUREMENT DIMENSIONS

Core Properties of Normative Faithfulness Metrics

A normative faithfulness metric quantifies the alignment between a generated legal text and the deontic content of its source material. The following properties define a rigorous evaluation framework.

01

Deontic Precision

Measures the proportion of generated deontic operators (obligations, permissions, prohibitions) that are actually present in the source text.

  • Formula: True Positives / (True Positives + False Positives)
  • Key Insight: A high score indicates the model is not inventing duties that do not exist
  • Example: If a model generates 10 obligations but only 7 are grounded in the contract, precision is 0.7
  • Penalizes: Hallucinated obligations and fabricated prohibitions
02

Deontic Recall

Measures the proportion of deontic operators in the source text that are successfully captured in the generated output.

  • Formula: True Positives / (True Positives + False Negatives)
  • Key Insight: A high score indicates the model is not omitting critical duties
  • Example: If a contract contains 12 obligations but the summary only reflects 9, recall is 0.75
  • Penalizes: Omission of normative content, which creates compliance risk
03

Hohfeldian Structural Fidelity

Evaluates whether the generated text preserves the correct jural correlatives defined by Hohfeldian analysis.

  • Right/Duty pairs: Does every generated right have a corresponding duty bearer?
  • Power/Liability pairs: Are generated powers matched with the correct liability?
  • Privilege/No-right pairs: Are permissions correctly structured?
  • Example: A clause stating 'Party A may audit' (privilege) must not be transformed into 'Party B must submit to audit' (duty) unless the source explicitly establishes both correlatives
04

Contrary-to-Duty (CTD) Consistency

Assesses whether the generated text correctly handles conditional obligations that arise when primary duties are violated.

  • Primary obligation: The ideal normative state
  • CTD obligation: The fallback rule triggered by non-compliance
  • Evaluation: Does the output preserve the logical relationship between primary and secondary duties?
  • Example: 'The contractor shall deliver by June 1. If delivery is late, the contractor shall pay $500 per day.' The metric checks that the penalty obligation is correctly conditioned on the violation of the primary duty
05

Normative Conflict Resolution Accuracy

Measures the model's ability to correctly resolve conflicting norms using established legal principles.

  • Lex Superior: Does the model defer to constitutional over statutory norms?
  • Lex Specialis: Does the specific provision override the general one?
  • Lex Posterior: Does the later-enacted rule prevail?
  • Example: If a federal statute prohibits data sharing but a state regulation permits it, the metric evaluates whether the output correctly applies the supremacy principle
06

Temporal Obligation Lifecycle Tracking

Evaluates whether the generated text accurately represents the temporal states of obligations: activation, fulfillment, violation, and expiration.

  • Activation: Is the triggering condition correctly identified?
  • Fulfillment: Is the satisfaction condition accurately described?
  • Violation: Is the breach state properly flagged?
  • Expiration: Is the termination condition preserved?
  • Example: 'The NDA obligations survive for 5 years post-termination.' The metric verifies that the survival period is not truncated or extended in the generated summary
NORMATIVE FAITHFULNESS METRIC

Frequently Asked Questions

A quantitative evaluation score measuring the degree to which a generated legal text or reasoning chain accurately reflects the deontic content of its source material without hallucination or omission.

A Normative Faithfulness Metric is a quantitative evaluation score that measures the degree to which a generated legal text or reasoning chain accurately reflects the deontic content—obligations, permissions, and prohibitions—of its source material without hallucination or omission. The metric is typically calculated by comparing the set of deontic statements extracted from the generated output against a gold-standard set extracted from the source documents. Precision measures the proportion of generated deontic statements that are actually grounded in the source, while recall measures the proportion of source deontic statements that were successfully reproduced. The F1 score—the harmonic mean of precision and recall—is the most common aggregate metric, penalizing systems that either fabricate norms or omit critical obligations. Advanced implementations use deontic annotation schemas to tag obligations with attributes like bearer, counterparty, and triggering condition, enabling fine-grained faithfulness scoring at the clause level rather than the document level.

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.