maha strategies · governed federation

Reproducibility Fixtures — Machine Interface

Reproducibility Fixtures — Machine Interface is limited to the behavior or authority established by the bound source and explicitly excludes the source's non-claims.

Active canonical release · fedrelease_afab9904d14554389423ec86536e22b8 · exact revision sha256:995cbb5ad2be27d3a9d224a3615b76db2e11cb5f05f0023467b773e49bc7f1a1

answer

Direct answer

Reproducibility Fixtures — Machine Interface is limited to the behavior or authority established by the bound source and explicitly excludes the source's non-claims.

method

Answer contract

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

evidence

Evidence and exact locators

t20-fixture-registry — lib/evidence-workflow-examples.ts — EVIDENCE_WORKFLOW_PUBLIC_REGISTRY and EVIDENCE_WORKFLOW_REGISTRY_DIGEST. Supports: Publishes a typed synthetic fixture registry with expected outputs, refusals, checks, and one digest over the registry.

limitations

What the evidence does not establish

Synthetic conformance is not independent reproduction and the registry is prepared rather than deployed.

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

Authority or implementation

This authority or implementation section is constrained to the same inspected scope: Publishes a typed synthetic fixture registry with expected outputs, refusals, checks, and one digest over the registry.

It must preserve the recorded boundary: Synthetic conformance is not independent reproduction and the registry is prepared rather than deployed.

required-by-specification

Mechanism or procedure

This mechanism or procedure section is constrained to the same inspected scope: Publishes a typed synthetic fixture registry with expected outputs, refusals, checks, and one digest over the registry.

It must preserve the recorded boundary: Synthetic conformance is not independent reproduction and the registry is prepared rather than deployed.

required-by-specification

Verification and uncertainty

This verification and uncertainty section is constrained to the same inspected scope: Publishes a typed synthetic fixture registry with expected outputs, refusals, checks, and one digest over the registry.

It must preserve the recorded boundary: Synthetic conformance is not independent reproduction and the registry is prepared rather than deployed.

required-by-specification

What this does not establish

This what this does not establish section is constrained to the same inspected scope: Publishes a typed synthetic fixture registry with expected outputs, refusals, checks, and one digest over the registry.

It must preserve the recorded boundary: Synthetic conformance is not independent reproduction and the registry is prepared rather than deployed.

bounded answers

Questions this page can answer

What is established?

Reproducibility Fixtures — Machine Interface is limited to the behavior or authority established by the bound source and explicitly excludes the source's non-claims.

Which exact source or symbol establishes it?

t20-fixture-registry, lib/evidence-workflow-examples.ts — EVIDENCE_WORKFLOW_PUBLIC_REGISTRY and EVIDENCE_WORKFLOW_REGISTRY_DIGEST

Which jurisdiction or implementation boundary applies?

Synthetic conformance is not independent reproduction and the registry is prepared rather than deployed.

What remains uncertain?

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

What must not be inferred?

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