CHANGEGATE RELEASEPROOF · SYNTHETIC

One missing field. A reason to stop.

Intended sequence: omit the required validation_exits_raw field from an invented evidence packet, then restore it from the original packet in a separate attempt. Observed process results below show which attempts actually ran.

SYNTHETIC evidence only. Human release approval is pending; deployment.authorized=false. This is not live-provider recovery, clean native QC, deployment verification, approval or production release. G0 OPEN / NOT APPROVED; G1 CLOSED.
Bundle statusSYNTHETIC DEMONSTRATION COMPLETED
Receipt outcomeSYNTHETIC_DEMONSTRATION_PASSED

The page presents the retained run receipt and files observed when it was generated. It is not a new report validator or authenticated provider proof. Available files on a failed run are evidence for inspection, not proof of recovery.

Inspect the run receipt and reading guide
  1. Inputs: preserve the synthetic originals

    The expectation is separate from the packet. The intended negative packet removes only validation_exits_raw and retains the remaining provenance. Inspect the available inputs and observed attempts below.

    Inspect original inputs, hashes and producer logs
    Fixture producer — observed process result
    FieldObserved value
    StatusSUCCEEDED
    Exit code0
    SignalNone recorded
    Spawn errorNone recorded
    Recorded output directory (inert text)Unavailable
    Observed output file names (inert text)Unavailable
    Retained input byte identities
    InputRecorded path (inert text)SHA-256Bytes
    Original valid packetvalid-input/packet.json6b66febb7302ada3d3e91fb9e67b707bcdb9c5ddf69659074adf61cf2084aa405282
    Separate trusted expectationvalid-input/expected.json5e93dfe3ba96682bf480ca9dad6a0a65c461713dfac053be62bb919bd0b81067355
    Negative packetnegative-packet.json2e79d0480d96c1c45af56cf3df99fb4b85755bda6f7a1c6543b2cfc65b9eb4af5185
    Recovery packetrecovery-packet.json6b66febb7302ada3d3e91fb9e67b707bcdb9c5ddf69659074adf61cf2084aa405282
  2. Rejected attempt: required evidence is missing

    The runner recorded the required-artifact rejection: exit 2, the missing-field diagnostic and no generated review outputs.

    Inspect the rejected attempt and diagnostic
    Negative CLI attempt — observed process result
    FieldObserved value
    StatusSYNTHETIC_REQUIRED_ARTIFACT_REJECTED
    Exit code2
    SignalNone recorded
    Spawn errorNone recorded
    Recorded output directory (inert text)negative-output
    Observed output file names (inert text)[]

    Empty output directories are not retained in ZIP files. The receipt records the observed listing.

  3. Single correction: restore the omitted field

    Recovery is designed to use the preserved original valid packet, restoring only validation_exits_raw; it does not change validation rules or clear findings.

    Observed byte relationship: Runner established recovery packet byte-identical to original.

    Inspect the single correction

    Recorded correction: Restore only required packet.validation_exits_raw from the original valid packet.

  4. Recovery attempt: report generation only

    Human release PENDING; approved=false; deployment.authorized=false; action=NONE.

    Inspect recovery process results and logs
    Recovery CLI attempt — observed process result
    FieldObserved value
    StatusSYNTHETIC_REPORT_GENERATED_WITH_FINDINGS
    Exit code0
    SignalNone recorded
    Spawn errorNone recorded
    Recorded output directory (inert text)recovery-output
    Observed output file names (inert text)["review.html","review.json"]

    Retained synthetic release limits

    Report generation succeeded while the underlying QC verdict remains failed. Five synthetic High findings remain visible in the report.

    FAILED_WITH_FINDINGS · 5 synthetic High findings. These fixture findings are separate from the real development dependency audit.

    Inspect the recorded release boundary
    Boundary recorded after successful demonstration
    FieldRecorded value
    QC verdictFAILED_WITH_FINDINGS
    Artifact provenanceINCOMPLETE_NATIVE_ARTIFACT_PROVENANCE
    Synthetic High findings5
    Human release statusPENDING
    Human release approvedfalse
    Deployment authorizedfalse

Recorded CI execution identity

Inspect execution identity and provenance

This generated demonstration contains no CI execution identity. No identity is inferred from the build host.

Execution identity, when recorded, identifies only the demonstration runner. It does not establish deployment provenance or release approval. All provider-like input identities are synthetic.