# Auralink owned OPDG reference

## Product boundary

This is a Hyperion-owned, pre-production reference decision system for Auralink at source commit
`c36b8872cc500e817a51e8e7501172fd66c1ec6b`. It tests whether the Operated Product Decision Graph
can prevent a governed software-reference result from being misread as authority to deploy a
physical product.

The authoritative Auralink records at that commit classify the selected boundary as a horizontal
Physical AI software platform with four source-only release-candidate verticals: EV Charging, Smart
City, Robotics, and Industrial. They separately classify real hardware as NO-GO and deployment
activation as not executed.

## Intended and excluded use

The graph is intended to govern one question: may the current source candidate progress toward a
production physical-system launch decision?

It cannot authorize real-hardware actuation, hosted production, rollout, customer deployment,
certification, conformity, safety, legal, regulatory, technical, or commercial approval. It is not
a customer case, independent adoption claim, benchmark, performance result, or representation that
all current-head Auralink tests passed.

## Decision inventory

The derivative contains four human-owned decisions:

1. bound the public product promise to the software-reference result;
2. select the four source-only reference packs without transferring their exclusions;
3. separate source and loopback evidence from physical and production authority; and
4. hold the productization gate until the external physical-product evidence and activation inputs
   exist for an exact release.

## Evidence class

The graph cites four committed public records by their exact SHA-256 digests: `STATUS.md`,
`catalog/product-boundary.yaml`, `catalog/reference-releases.yaml`, and
`docs/audit/findings.yaml`. The status, boundary, and open-gate records are classified E0 because
they are declared governance records. The reference-release catalog is classified E1 because it
describes governed simulation and developer-loopback evidence. No E2, field, HIL, independent,
production, deployment, certification, or customer evidence is asserted.

## Assumptions

No assumption is used to bridge the missing evidence. In particular, the graph does not assume that
a supported source path will work on selected production hardware or that an independent authority
will approve it.

## Specialist authorities

The Auralink findings ledger retains the relevant specialist gates: representative device
integration, source-SHA-bound HIL, independent protocol or interoperability evidence, and
independent safety or regulatory approval. OPDG keeps Mohammed Cherifi as the integrated product
decision owner without transferring those specialist authorities to him, the checker, or an AI
system.

## Release Case binding

No launch-stage Release Case is created. That absence is deliberate: the product remains at the
productization boundary, and its gate is blocked before a configuration-bound launch decision can
be considered.

## Checker findings

The deterministic checker returned `BLOCKED` with exit code `5`. It identified authored blocked
governance at the productization gate. It also warned that the gate cites current evidence only up
to E1 while the method's productization scope expectation is E2. The append-only private trial and
separately initialized public-derivative ledgers both retained valid revision-one chains.

## Decision changes

The trial produced three useful effects:

- **decision narrowed:** “software-reference complete” remains a source/simulation claim and cannot
  be promoted into “physical-product ready”;
- **new evidence requested:** the release path now names the four exact external evidence gates and
  the separately declared activation inputs that must reopen the decision; and
- **owner and escalation clarified:** Mohammed Cherifi owns the integrated product gate, while the
  named hardware, HIL, protocol/interoperability, and safety/regulatory authorities retain their
  independent decision rights.

This meets the method's owned-trial usefulness threshold without manufacturing a positive launch
verdict.

## Method defects

No material schema, checker, ledger, export, or decision-contract defect was observed. A blocked
verdict for a legitimately blocked product is correct method behavior. The E1-versus-E2 warning is
also correct and makes the evidence gap more precise.

## Unchanged decisions

Real hardware remains NO-GO. No image is promoted, no hosted release or deployment is executed, no
customer or field commitment is made, no Release Case is created, and no certification or
independent assessment is inferred.

## Public-export exclusions

The evidence pack includes only the manually bounded graph, deterministic checker output, exit
code, this case record, and their governance records. It excludes Auralink working-tree changes,
private ledger state, source code, internal rationale, credentials, security-sensitive material,
customer data, personal data beyond the named accountable owner, and unpublished operational
evidence.

## Owner review

Mohammed Cherifi explicitly authorized completion of the OPDG release gates and directed the
programme to take the best decision on his behalf on 26 August 2026. The exact factual review and
rights records bind this payload to that owner authorization. This is an owner decision, not legal
advice or an independent technical, safety, regulatory, or conformity review. The later rendered
website inspection remains a separate publication/deployment decision.