Claim Extraction — Machine Record

Direct answer

Claim Extraction — Machine Record is implemented as a source-bounded machine record guide.

Answer contract

Apply the machine record lens only to the exact inspected source scope; do not infer authority from adjacent topics.

Evidence and exact locators

t23-claim-extraction — lib/claim-evidence.ts — assertClaimEvidence. Supports: Validates claim provenance and empirical-evidence axes independently under a typed contract.

local-claim-evidence-contract — repo:lib/claim-evidence.ts — repository source inspected 2026-09-06; assertClaimEvidence; provenance and empirical evidence axes. Supports: The contract represents where a claim came from separately from what empirical evidence, if any, supports it.

local-source-alignment-contract-t7 — repo:lib/frontier-source-alignment.ts — repository source inspected 2026-09-06; source identity, version, locator, claim scope, and boundary axes. Supports: The alignment contract keeps source identity, version relationship, locator completeness, claim scope, and inference boundary as distinct review axes.

What the evidence does not establish

The contract records supplied assertions; it does not establish truth, source support, completeness, or semantic entailment.

A typed evidence label does not make a claim true, sufficient, current, causal, reproducible, or within a source’s actual scope.

The contract detects recorded defects and omissions; it cannot replace inspection or infer support from metadata or topical similarity.

Rights and reuse

project-owned-reference-only

Maha-controlled repository source; symbols, headings, and file identity only. No credential, customer value, runtime payload, private input, or receipt body is retained.

Dependencies and related concepts

applies-to: urn:maha:concept:evidence:claim-extraction

governed-by: urn:maha:concept:governance

evidence-for: urn:maha:concept:evidence

Source or implementation

This source or implementation section is constrained to the same inspected scope: Validates claim provenance and empirical-evidence axes independently under a typed contract. The contract represents where a claim came from separately from what empirical evidence, if any, supports it. The alignment contract keeps source identity, version relationship, locator completeness, claim scope, and inference boundary as distinct review axes.

It must preserve the recorded boundary: The contract records supplied assertions; it does not establish truth, source support, completeness, or semantic entailment. A typed evidence label does not make a claim true, sufficient, current, causal, reproducible, or within a source’s actual scope. The contract detects recorded defects and omissions; it cannot replace inspection or infer support from metadata or topical similarity.

Method

This method section is constrained to the same inspected scope: Validates claim provenance and empirical-evidence axes independently under a typed contract. The contract represents where a claim came from separately from what empirical evidence, if any, supports it. The alignment contract keeps source identity, version relationship, locator completeness, claim scope, and inference boundary as distinct review axes.

It must preserve the recorded boundary: The contract records supplied assertions; it does not establish truth, source support, completeness, or semantic entailment. A typed evidence label does not make a claim true, sufficient, current, causal, reproducible, or within a source’s actual scope. The contract detects recorded defects and omissions; it cannot replace inspection or infer support from metadata or topical similarity.

Limits and uncertainty

This limits and uncertainty section is constrained to the same inspected scope: Validates claim provenance and empirical-evidence axes independently under a typed contract. The contract represents where a claim came from separately from what empirical evidence, if any, supports it. The alignment contract keeps source identity, version relationship, locator completeness, claim scope, and inference boundary as distinct review axes.

It must preserve the recorded boundary: The contract records supplied assertions; it does not establish truth, source support, completeness, or semantic entailment. A typed evidence label does not make a claim true, sufficient, current, causal, reproducible, or within a source’s actual scope. The contract detects recorded defects and omissions; it cannot replace inspection or infer support from metadata or topical similarity.

Dependencies

This dependencies section is constrained to the same inspected scope: Validates claim provenance and empirical-evidence axes independently under a typed contract. The contract represents where a claim came from separately from what empirical evidence, if any, supports it. The alignment contract keeps source identity, version relationship, locator completeness, claim scope, and inference boundary as distinct review axes.

It must preserve the recorded boundary: The contract records supplied assertions; it does not establish truth, source support, completeness, or semantic entailment. A typed evidence label does not make a claim true, sufficient, current, causal, reproducible, or within a source’s actual scope. The contract detects recorded defects and omissions; it cannot replace inspection or infer support from metadata or topical similarity.

Questions this page can answer