maha strategies · governed federation

Reproducibility Fixtures — Worked Example

Reproducibility Fixtures — Worked Example describes the bounded Maha behavior established by the cited implementation and carries the implementation's explicit non-claims.

Active canonical release · fedrelease_bdcfe7563f233bc8e6ebede37b420faa · exact revision sha256:43ad0c99fe4572413267248cfdd5a8f7f02cf7c29c0b0746fc661eefd486c039

answer

Direct answer

Reproducibility Fixtures — Worked Example describes the bounded Maha behavior established by the cited implementation and carries the implementation's explicit non-claims.

method

Answer contract

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

evidence

Evidence and exact locators

t19-reproducibility-fixtures — lib/evidence-workflow-examples.ts — EVIDENCE_WORKFLOW_EXAMPLES. Supports: Provides committed synthetic inputs, expected outputs, refusals, checks, and explicit synthetic boundaries.

limitations

What the evidence does not establish

A fixture exercises a code path and is not independent scientific reproduction.

rights

Rights and reuse

project-owned-reference-only

relationships

Dependencies and related concepts

applies-to: urn:maha:concept:computation:reproducibility-fixtures

governed-by: urn:maha:concept:governance

evidence-for: urn:maha:concept:computation

required-by-specification

Inputs and prerequisites

This inputs and prerequisites section is constrained to the same inspected scope: Provides committed synthetic inputs, expected outputs, refusals, checks, and explicit synthetic boundaries.

It must preserve the recorded boundary: A fixture exercises a code path and is not independent scientific reproduction.

required-by-specification

Ordered behavior

This ordered behavior section is constrained to the same inspected scope: Provides committed synthetic inputs, expected outputs, refusals, checks, and explicit synthetic boundaries.

It must preserve the recorded boundary: A fixture exercises a code path and is not independent scientific reproduction.

required-by-specification

Verification or refusal states

This verification or refusal states section is constrained to the same inspected scope: Provides committed synthetic inputs, expected outputs, refusals, checks, and explicit synthetic boundaries.

It must preserve the recorded boundary: A fixture exercises a code path and is not independent scientific reproduction.

required-by-specification

What this does not establish

This what this does not establish section is constrained to the same inspected scope: Provides committed synthetic inputs, expected outputs, refusals, checks, and explicit synthetic boundaries.

It must preserve the recorded boundary: A fixture exercises a code path and is not independent scientific reproduction.

required-by-specification

Related definition and applications

This related definition and applications section is constrained to the same inspected scope: Provides committed synthetic inputs, expected outputs, refusals, checks, and explicit synthetic boundaries.

It must preserve the recorded boundary: A fixture exercises a code path and is not independent scientific reproduction.

bounded answers

Questions this page can answer

What exact behavior is implemented?

Reproducibility Fixtures — Worked Example describes the bounded Maha behavior established by the cited implementation and carries the implementation's explicit non-claims.

Which inputs and identities are required?

t19-reproducibility-fixtures, lib/evidence-workflow-examples.ts — EVIDENCE_WORKFLOW_EXAMPLES

Which exact symbol bears the explanation?

A fixture exercises a code path and is not independent scientific reproduction.

Which refusal or verification boundary applies?

applies-to: urn:maha:concept:computation:reproducibility-fixtures governed-by: urn:maha:concept:governance evidence-for: urn:maha:concept:computation

What external outcome does this implementation not establish?

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