# PNVA Reproducibility Guard

Author: Gustavo de Aguiar Martins  
Project: PNVA-Core / Enygnalab / EnyOS  
Edition: Open Research / Production Evidence Edition, 2026

## Objective

This layer proves that the public PNVA evidence package is reproducible from the current repository tools.

It answers a direct engineering question:

```text
can the current commands regenerate the same essential results?
```

## Current Public Result

Report:

```text
reports/pnva-reproducibility-2026-05-05.json
```

Current classification:

```text
REPRODUCIBILITY_READY
```

Current result:

```text
command_count: 40
comparison_count: 445
failure_count: 0
command_failure_count: 0
comparison_failure_count: 0
```

## What Is Reproduced

The guard regenerates temporary reports for:

```text
canonical replay
native replay
canonical no-tick invariants
native no-tick invariants
native event emitter
canonical policy
native policy
canonical proof-chain
native proof-chain
canonical causal graph
native causal graph
schema contract validation
causal chronology guard
tension-decision calibration
decision trace index
heuristic influence map
entity no-tick matrix
suppression ledger
sovereign robustness gate
R3 migration plan
authority migration ledger
R3 authority projection
R3 cutover gate
R3 runtime event emitter
R3 runtime capture matrix
R3 runtime evidence guard
R3 runtime replay
R3 runtime policy
R3 runtime no-tick
R3 runtime proof-chain
R3 runtime instrumentation plan
R3 runtime contract validation
sovereign evolution ledger
adversarial validation
entity and heuristic maturity
evidence attestation
semantic consistency
```

Then it compares stable fields against the published reports.

## What Is Compared

Examples:

```text
classification
pass flag
event count
proof hash count
suppression count
no-tick suppression ratio
strong decision count
legacy authority warning count
proof-chain final hash
causal graph hash
adversarial detection count
maturity score
attestation evidence hash
semantic consistency count
tension-decision warning count
decision trace coverage
heuristic influence edge count
entity no-tick matrix suppression count
suppression ledger avoided execution count
sovereign robustness score and native clean signal count
R3 current readiness, target readiness, migration action count and primary debt
authority migration candidate count, native debt, mapping coverage and proof coverage
R3 authority projection event count, precheck count, commit count, no-tick suppression, proof coverage, replay, policy and no-tick classifications
R3 cutover contract readiness, approval block, remaining runtime replacement count and runtime blocker count
R3 runtime capture slot count, pending count, required runtime event count, projection-pair coverage and target entity/action counts
R3 runtime evidence guard readiness, pending slot count, required runtime event count and negative-control detections
R3 runtime instrumentation plan readiness, action contract count, template count, mandatory field count and required runtime event count
R3 runtime contract validation readiness, contract check count, failure count, mandatory field count and enforced control count
sovereign evolution score, evidence integrity, no-tick readiness, native clean path, R3 preparation, runtime pending count and runtime approval boundary
```

The guard intentionally ignores:

```text
generated_at timestamps
temporary paths
stdout formatting
non-semantic command environment details
```

## Why This Matters

Semantic consistency proves that published reports agree with each other.

Reproducibility proves that the current tools can regenerate the same stable evidence fields.

Together:

```text
consistency = the package agrees with itself
reproducibility = the package can be regenerated by method
```

## Attestation Boundary

This report is intentionally outside the evidence attestation hash seed.

Reason:

```text
reproducibility consumes the attestation
the attestation must not hash a report that depends on the attestation
```

This keeps the evidence graph acyclic.

## Command

```bash
python3 tools/pnva_reproducibility_guard.py \
  --write reports/pnva-reproducibility-2026-05-05.json
```

For CI or temporary validation:

```bash
python3 tools/pnva_reproducibility_guard.py \
  --write /tmp/pnva-reproducibility.json
python3 -m json.tool /tmp/pnva-reproducibility.json >/dev/null
```

## Sovereign Rule

PNVA evidence should be:

```text
valid
consistent
adversarially tested
semantically coherent
reproducible from source commands
```

This turns a collection of reports into a defensible open research evidence package.