Skip to content

Evidence Versions ​

Wire versions preserve machine-readable compatibility. They are scoped to an evidence family: a larger number is not a stronger claim, and two families may use the same version.

Suite and Property families ​

FamilyVersionSelected whenCatalog
Scenario localv1Local report without source bindingInput via VerificationSchemaCatalog; local report model
Scenario source-boundv2Ordinary source-owning SuiteVerificationEvidenceSchemaCatalog
Fixture fidelityv4Declared control observations are publishedVerificationFixtureEvidenceSchemaCatalog
Contract sensitivityv6Baseline plus supported controlled mutantsVerificationSensitivityEvidenceSchemaCatalog
Property samplesv7Finite Property without relation or shrinkVerificationPropertyEvidenceSchemaCatalog
Environment isolationv8Lease/namespace isolation evidenceVerificationIsolationEvidenceSchemaCatalog
Oracle independencev10Reference-model child observationVerificationOracleIndependenceEvidenceSchemaCatalog
Metamorphic invariantv12One INVARIANT relationVerificationMetamorphicEvidenceSchemaCatalog
Idempotent repetitionv13One IDEMPOTENT_REPETITION relationVerificationIdempotencyEvidenceSchemaCatalog
Permutation invariantv14One PERMUTATION_INVARIANT relationVerificationPermutationEvidenceSchemaCatalog
Numeric conservationv15One CONSERVES_NUMERIC_TOTAL relationVerificationConservationEvidenceSchemaCatalog
Property shrinkv16Supported signed-64-bit values or integerRange shrinkVerificationShrinkEvidenceSchemaCatalog
Case process boundaryv17Each Case executes behind a process boundaryVerificationCaseProcessEvidenceSchemaCatalog

Durable families ​

VersionContentReader / catalog
v1Local durable reportDurableVerificationEvidence / DurableVerificationEvidenceSchemaCatalog
v2Source-owning durable action evidenceDurableSourceBoundEvidence / DurableSourceBoundEvidenceSchemaCatalog
v3Durable actions plus Scenario business projectionDurableSourceBoundEvidence / DurableScenarioSourceBoundEvidenceSchemaCatalog
v4Team evidence with Policy continuity, effect provenance, and declared portsDurableSourceBoundEvidence / DurableTeamSourceBoundEvidenceSchemaCatalog

Durable action and temporal input schemas use DurableVerificationSchemaCatalog and DurableTemporalSchemaCatalog. Their input versions are a separate axis from durable evidence v1–v4.

Project and Reactor families ​

FamilyVersionContentCatalog
Project aggregatev2Requirement aggregate and complete child receipt inventoryVerificationProjectEvidenceSchemaCatalog
Project childv3Ordinary source-bound childVerificationProjectEvidenceSchemaCatalog
Fixture project childv5Fixture-fidelity childVerificationFixtureProjectEvidenceSchemaCatalog
Isolation project childv9Environment-isolation childVerificationIsolationProjectEvidenceSchemaCatalog
Oracle project childv11Reference-model childVerificationOracleIndependenceEvidenceSchemaCatalog
Process project childv18Case-process-boundary childVerificationCaseProcessEvidenceSchemaCatalog
Reactor aggregatev1Literal Maven root coordinatesVerificationReactorEvidenceSchemaCatalog
Reactor aggregatev2Controlled CI-friendly root property snapshotVerificationReactorEvidenceSchemaCatalog

A project child version is not a capability level. The project reader binds every exact module, Suite, run, and receipt from the parent manifest to one child artifact.

Comparison and attestation families ​

FamilyVersionContentCatalog
DSL graph comparisonv1One DSL_GRAPH change axisVerificationComparisonEvidenceSchemaCatalog
BLOGE toolchain comparisonv1BLOGE_TOOLCHAIN with controlled child JVM/runtime cohortVerificationToolchainComparisonEvidenceSchemaCatalog
Toolchain request/responsev1Parent/child protocolVerificationToolchainProtocolSchemaCatalog
External provenance attestationv1Signed Oracle provenance claimsVerificationExternalAttestationSchemaCatalog
Release attestationv1Governed receipt plus attributed comparison receiptVerificationReleaseAttestationSchemaCatalog

Reader rules ​

  1. Select the schema and reader by family, not by version number alone.
  2. Pass the artifact directory, original project root, and externally retained receipt.
  3. Do not copy, migrate, or re-seal a source-bound artifact.
  4. Treat an unknown version, missing relation, or projection mismatch as a verification failure.
  5. Pass only reader-verified facts to VerificationClaims.assess(...).

The artifact version describes the wire contract. The resulting EvidenceTrust and ClaimCapability depend on the verified contents and cumulative prerequisites.