# SCGA-BS-003 → BS-005 — Preserved Examination Lineage

## Status

**Evidence record only. This directory does not modify Harmonic runtime behavior, primitive semantics, request contracts, or execution policy.**

This record preserves the adjudicative lineage of three prospective examinations of a narrow Harmonic execution-boundary proposition. Predecessor findings remain findings; BS-005 does not rewrite BS-003 or BS-004.

## Claim boundary ultimately supported

Under the BS-005 frozen examination, historical validity did not silently retain consequential standing after the examined material change in present state.

This is a **bounded implementation finding**, not a claim that Harmonic detects every material change in reality and not a claim about downstream real-world execution enforcement.

## Lineage

| Examination | Positive control | Negative / target | Falsifier | Final reading |
|---|---|---|---|---|
| SCGA-BS-003 | **FAIL** — `REFUSED`; native packet omitted the required obligation witness | **TARGET_SURVIVES_THIS_TEST** — `REFUSED` | **NOT TRIGGERED** | Full discrimination **NOT ESTABLISHED**. Positive control was constitutionally incomplete. Preserved; no rerun/repair/remap. |
| SCGA-BS-004 | **FAIL under frozen criterion** — expected `PERMITTED`, observed `CONSTRAINED / admissible=true / action=constrain` | **TARGET_SURVIVES_THIS_TEST** — `REFUSED / admissible=false` | **NOT TRIGGERED** | Full counterfactual discrimination **NOT ESTABLISHED** because the frozen PC criterion required `PERMITTED`. Source review later established that ordinary `PERMITTED` is not reachable for the same native high-consequence class while the high-consequence warning survives. Preserved; no retrospective remap. |
| SCGA-BS-005 | **PASS** — `CONSTRAINED / admissible=true / action=constrain` | **TARGET_SURVIVES_THIS_TEST** — `REFUSED / admissible=false / action=refuse` | **NOT TRIGGERED** | **SUPPORTED SURVIVAL CONDITION SATISFIED** for the frozen proposition. |

## BS-003 preserved identifiers

- Positive-control event: `712709de-1e4c-4283-9405-25ba7c79f6a6`
- Negative event: `d7a6b368-77bf-43fc-a1db-2aab848eee92`
- Frozen package root SHA-256: `bb8c8ff51bc08fb96ccfeddbf9178cff417f96cac839979d66749acaa8b376ab`
- Frozen ZIP SHA-256: `e600ba54002a69d2ee07a05cedad8b95495af10646766f265c852bb610d3c0eb`
- Preserved execution-evidence ZIP SHA-256: `a466a47276a9018debd2c77b75a75a56954b1b9afc9044c58c35a37a7b5d4033`

The BS-003 positive control reached current Understanding, Reality Contact, and Authority Continuity but failed closed at Obligation Continuity (`NOT_PROVIDED / admissible=false`). The negative also refused, including `UNDERSTANDING_INADMISSIBLE`. Because the positive control failed, the examination did not establish full discrimination.

## BS-004 preserved reading

BS-004 prospectively closed the missing-obligation issue. Its positive control reached:

- `UNDERSTANDING_CURRENT / admissible=true`
- `CONTACT_CONFIRMED / admissible=true`
- `AUTHORITY_CONTINUOUS / admissible=true`
- `OBLIGATIONS_SATISFIED / admissible=true`
- `BOUNDARY_ELEVATED / admissible=true`
- runtime `CONDITIONALLY_ADMISSIBLE / admissible=true / action=constrain`

The top-level result was therefore `CONSTRAINED`, not the frozen expected `PERMITTED`; the positive control remained a frozen FAIL. The negative was `REFUSED / admissible=false`, but the examination could not be upgraded to full discrimination after the fact.

Subsequent source inspection established that the surviving `high_consequence_level` warning is native to the examined high-consequence class and drives the constrained-but-admissible disposition. That source finding explains the mismatch; it does **not** rewrite BS-004.

## BS-005 supported result

BS-005 was constituted prospectively against the established native high-consequence contract rather than retroactively remapping BS-004.

Observed result:

- Positive control: `CONSTRAINED / admissible=true / action=constrain` — **PASS** under the frozen BS-005 criterion.
- Negative after one controlled material state transition: `REFUSED / admissible=false / action=refuse` — **TARGET SURVIVES THIS TEST**.
- Precommitted falsifier: **NOT TRIGGERED**.
- `high_consequence_level` warning remained common to both specimens.
- Reality Contact was `CONTACT_CONFIRMED` in both specimens.
- The material state transition / invalidated prior-state standing was the controlling discriminator in the negative specimen.
- No BS-006 was required for this proposition.

## BS-005 production persistence fingerprints

The preserved production database identifies the two BS-005 specimens directly as `SCGA-BS-005-PC-001` and `SCGA-BS-005-NEG-001`. Both were evaluated by runtime `4.1.0` with Governance Pack `1.10.0-v4.1-governance-visibility-upgrade`. The PC was evaluated at `2026-09-04T20:18:53.882Z` and persisted as `CONSTRAINED / admissible=true / action=constrain`; the NEG was evaluated at `2026-09-04T20:19:18.470Z` and persisted as `REFUSED / admissible=false / action=refuse`.

The exact recovered packet, request, trace, input-packet, runtime-input-snapshot, present-state-binding, primitive, response-binding, source-runtime-artifact, determination, dependency-root, transaction-digest, and infrastructure-persistence fingerprints are published in [`BS005_PRODUCTION_PERSISTENCE.json`](./BS005_PRODUCTION_PERSISTENCE.json). The infrastructure record also preserves successful HTTP `201` writes for each determination, receipt, and evaluation event at execution time.

This is publication of preserved production persistence, not reconstruction of a raw bundle. Receipt hashes are not asserted in this publication because they were not recovered in this extraction.

## What this establishes

The BS-005 evidence supports the narrow proposition that, in the examined native governed disposition path, a historically valid state did not silently retain consequential standing after the controlled material state transition invalidated the prior-state standing required for the same consequence.

## What this does not establish

This record does **not** establish:

- downstream executor compliance or real-world consequence prevention;
- omniscient detection of material conditions outside Harmonic's represented/observable state;
- universal correctness across every domain, packet, consequence class, or possible ΔN;
- architectural equivalence to another governance system;
- that BS-003 or BS-004 passed;
- that later source or test-coherence changes caused or retroactively validate the BS-005 production result.

## Preservation rule

The lineage is append-only in meaning:

1. A failed or indeterminate predecessor remains where it landed.
2. A successor must be constituted prospectively.
3. A successor result does not confer standing backward onto its predecessor.
4. Claim language must remain bounded to the evidence actually earned.

## Artifact availability

This repository snapshot records the adjudicative findings, the known BS-003 artifact identities, and the recovered BS-005 production-persistence fingerprints. It does **not** manufacture or reconstruct missing frozen BS-004/BS-005 raw execution bundles. If additional exact preserved artifacts are published later, they should be added as immutable evidence objects with their original digests and linked from this record without changing the findings above.