maha research · governed federation

Scope Matching — Source Contract

Scope Matching — Source Contract is implemented as a source-bounded source contract guide.

Active canonical release · fedrelease_6a1cdf49cdacae1605f3531109ba2973 · exact revision sha256:940c4c4568465d6e7cb5f4f33ac1a479b000cae241496c4f105733b021a77b11

answer

Direct answer

Scope Matching — Source Contract is implemented as a source-bounded source contract guide.

method

Answer contract

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

evidence

Evidence and exact locators

t23-scope-preflight — lib/evidence-preflight.ts — compileEvidencePreflight. Supports: Computes deterministic bounded-language and lexical-coverage review signals.

nist-ai-rmf-scope-t9 — https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf — NIST AI 100-1, January 2023; MAP 1.1; MAP 2.2–2.3; MEASURE 2.5. Supports: The framework calls for intended context, assumptions, knowledge limits, scientific integrity, and generalization limits to remain explicit.

local-evidence-preflight-scope-t9 — repo:lib/evidence-preflight-contract.ts — repository source inspected 2026-09-06; EvidencePreflightBlocker; exact-locator-missing; claim-scope-overbroad; unsupported-inference-risk; rights-basis-unresolved. Supports: The local preflight separately records source identity, exact locator, evidence status, scope overbreadth, unsupported inference, rights, and access blockers.

limitations

What the evidence does not establish

Lexical overlap is routing evidence only, not semantic support.

The voluntary framework does not determine whether a particular source supports a claim or validate a model, inference, result, or deployment.

The preflight is automated and structural. It does not independently inspect a source, verify a dossier, retain submitted content by default, or establish claim truth.

rights

Rights and reuse

project-owned-reference-only

Official government source; link and bounded paraphrase only. No full text or time-sensitive operational value is retained.

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

relationships

Dependencies and related concepts

applies-to: urn:maha:concept:evidence:scope-matching

governed-by: urn:maha:concept:governance

evidence-for: urn:maha:concept:evidence

required-by-specification

Source or implementation

This source or implementation section is constrained to the same inspected scope: Computes deterministic bounded-language and lexical-coverage review signals. The framework calls for intended context, assumptions, knowledge limits, scientific integrity, and generalization limits to remain explicit. The local preflight separately records source identity, exact locator, evidence status, scope overbreadth, unsupported inference, rights, and access blockers.

It must preserve the recorded boundary: Lexical overlap is routing evidence only, not semantic support. The voluntary framework does not determine whether a particular source supports a claim or validate a model, inference, result, or deployment. The preflight is automated and structural. It does not independently inspect a source, verify a dossier, retain submitted content by default, or establish claim truth.

required-by-specification

Method

This method section is constrained to the same inspected scope: Computes deterministic bounded-language and lexical-coverage review signals. The framework calls for intended context, assumptions, knowledge limits, scientific integrity, and generalization limits to remain explicit. The local preflight separately records source identity, exact locator, evidence status, scope overbreadth, unsupported inference, rights, and access blockers.

It must preserve the recorded boundary: Lexical overlap is routing evidence only, not semantic support. The voluntary framework does not determine whether a particular source supports a claim or validate a model, inference, result, or deployment. The preflight is automated and structural. It does not independently inspect a source, verify a dossier, retain submitted content by default, or establish claim truth.

required-by-specification

Limits and uncertainty

This limits and uncertainty section is constrained to the same inspected scope: Computes deterministic bounded-language and lexical-coverage review signals. The framework calls for intended context, assumptions, knowledge limits, scientific integrity, and generalization limits to remain explicit. The local preflight separately records source identity, exact locator, evidence status, scope overbreadth, unsupported inference, rights, and access blockers.

It must preserve the recorded boundary: Lexical overlap is routing evidence only, not semantic support. The voluntary framework does not determine whether a particular source supports a claim or validate a model, inference, result, or deployment. The preflight is automated and structural. It does not independently inspect a source, verify a dossier, retain submitted content by default, or establish claim truth.

required-by-specification

Dependencies

This dependencies section is constrained to the same inspected scope: Computes deterministic bounded-language and lexical-coverage review signals. The framework calls for intended context, assumptions, knowledge limits, scientific integrity, and generalization limits to remain explicit. The local preflight separately records source identity, exact locator, evidence status, scope overbreadth, unsupported inference, rights, and access blockers.

It must preserve the recorded boundary: Lexical overlap is routing evidence only, not semantic support. The voluntary framework does not determine whether a particular source supports a claim or validate a model, inference, result, or deployment. The preflight is automated and structural. It does not independently inspect a source, verify a dossier, retain submitted content by default, or establish claim truth.

bounded answers

Questions this page can answer

What is established?

Scope Matching — Source Contract is implemented as a source-bounded source contract guide.

Which exact source establishes it?

t23-scope-preflight, lib/evidence-preflight.ts — compileEvidencePreflight; nist-ai-rmf-scope-t9, https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf — NIST AI 100-1, January 2023; MAP 1.1; MAP 2.2–2.3; MEASURE 2.5; local-evidence-preflight-scope-t9, repo:lib/evidence-preflight-contract.ts — repository source inspected 2026-09-06; EvidencePreflightBlocker; exact-locator-missing; claim-scope-overbroad; unsupported-inference-risk; rights-basis-unresolved

What dependency remains separate?

Lexical overlap is routing evidence only, not semantic support. The voluntary framework does not determine whether a particular source supports a claim or validate a model, inference, result, or deployment. The preflight is automated and structural. It does not independently inspect a source, verify a dossier, retain submitted content by default, or establish claim truth.

What uncertainty remains?

applies-to: urn:maha:concept:evidence:scope-matching governed-by: urn:maha:concept:governance evidence-for: urn:maha:concept:evidence

What must not be inferred?

A source, locator, rights, scope, boundary, dependency, implementation, or release change requires a new exact-revision review.