{"assumptions":[],"conflicts":[],"created_at":"2026-08-26T16:56:39Z","decision_principles":["Source presence, simulation, loopback evidence, and catalog eligibility never grant production or physical authority.","A consequential gate retains a named human owner and cannot be approved by the OPDG checker.","Every public statement must preserve the evidence level, exact source commit, and excluded claims."],"decisions":[{"assumption_refs":[],"coupled_with":[],"decided_at":"2026-08-26T16:56:39Z","decision":"Treat Auralink as a governed horizontal Physical AI software platform and explicitly exclude real-hardware interoperability, HIL, certification, production activation, and customer deployment.","depends_on":[],"evidence_refs":["ev-status","ev-product-boundary"],"governance_state":"clear","id":"d-strategy-gate","is_gate":true,"owner":"Mohammed Cherifi","question":"What claim may the owned Auralink programme make before physical evidence and activation exist?","rationale":"The authoritative status and product-boundary records support a narrow software-reference claim and explicitly reject the broader physical-product interpretation.","reversal_or_containment":"Withdraw or narrow the public software claim without enabling any physical or production path.","reversibility":"reversible","review_triggers":["The governed product boundary, status authority, intended use, excluded use, or public product claim changes."],"stage":"strategy","status":"decided","surface":"opportunity","title":"Bound the Auralink product promise"},{"assumption_refs":[],"coupled_with":[],"decided_at":"2026-08-26T16:56:39Z","decision":"Retain EV Charging, Smart City, Robotics, and Industrial as source-only release-candidate reference packs exercised through declared simulation or loopback boundaries.","depends_on":["d-strategy-gate"],"evidence_refs":["ev-reference-releases"],"governance_state":"clear","id":"d-discovery-gate","is_gate":true,"owner":"Mohammed Cherifi","question":"Which implemented vertical paths may be evaluated together without implying physical deployment?","rationale":"The reference-release catalog names those four packs, their supported source claims, and their explicit hardware, deployment, certification, and customer exclusions.","reversal_or_containment":"Remove a reference pack or narrow its supported claim without promoting images, devices, sites, or customers.","reversibility":"reversible","review_triggers":["A reference pack, supported claim, excluded claim, execution environment, hardware scope, or distribution channel changes."],"stage":"discovery","status":"decided","surface":"workflow","title":"Select the owned source-reference scope"},{"assumption_refs":[],"coupled_with":[],"decided_at":"2026-08-26T16:56:39Z","decision":"Recognize the catalog-selected software-reference boundary while withholding hardware readiness, hosted release, production trust, rollout, restore acceptance, and customer claims.","depends_on":["d-discovery-gate"],"evidence_refs":["ev-status","ev-reference-releases"],"governance_state":"clear","id":"d-source-boundary","is_gate":false,"owner":"Mohammed Cherifi","question":"What does the current owned evidence establish, and what remains outside it?","rationale":"The current status record distinguishes implementation and source/simulation evidence from every activation and physical-evidence gate.","reversal_or_containment":"Keep every production and physical effect path disabled and retain the source-only labels.","reversibility":"costly","review_triggers":["A source commit, governed catalog, exact-head aggregate, release channel, image promotion, trust input, restore result, or deployment assertion changes."],"stage":"productization","status":"decided","surface":"boundary","title":"Separate software evidence from physical authority"},{"assumption_refs":[],"coupled_with":[],"decided_at":"2026-08-26T16:56:39Z","decision":"No. Keep real hardware and deployment activation at NO-GO until the four named external evidence gates and the separate activation inputs are satisfied for an exact release.","depends_on":["d-source-boundary"],"evidence_refs":["ev-open-evidence-gates"],"governance_state":"blocked","id":"d-productization-gate","is_gate":true,"owner":"Mohammed Cherifi","question":"May the current owned source candidate progress to a production physical-system launch decision?","rationale":"The authoritative findings ledger records open production-device integration, source-bound HIL, independent protocol or interoperability evidence, and independent safety or regulatory approval. Current source and loopback evidence cannot substitute for them.","reversal_or_containment":"Do not create a launch-stage Release Case or authorize physical, hosted-production, rollout, customer, or certification commitments.","reversibility":"one_way","review_triggers":["Representative production devices are selected and integrated with reviewed mappings and trust controls.","Source-SHA-bound HIL campaigns retain passing raw evidence for every selected device and failure mode.","Applicable protocol and interoperability profiles receive independent evidence for the selected versions and peers.","Applicable safety and regulatory approvals are bound to the selected hardware, sites, jurisdictions, and exact release.","Every separately declared production activation input is supplied and independently reviewed."],"stage":"productization","status":"decided","surface":"evidence","title":"Hold the production-activation gate"}],"evidence":[{"classification":"public","collected_at":"2026-08-24T12:08:47Z","digest":"97daf70fea581aa0af88ae8e181d62b54abc882dae0145fcf6882da0dc3c72b5","id":"ev-status","level":"E0","limitations":"A status record is declared governance evidence, not current-head aggregate test, HIL, production, certification, or customer evidence.","scope":"The declared repository-wide software-reference and source-only release-candidate boundary at the cited commit","source":"Auralink STATUS.md at commit c36b8872cc500e817a51e8e7501172fd66c1ec6b","statement":"At the cited source commit, Auralink's authoritative status classifies the governed boundary as software-reference complete and real hardware as NO-GO.","status":"current"},{"classification":"public","collected_at":"2026-08-24T12:08:47Z","digest":"011337153d81128fc35448584aff991403d357e8c801f4eaf6243a172a250e8a","id":"ev-product-boundary","level":"E0","limitations":"Catalog selection establishes governance scope only; it does not establish correctness, device compatibility, deployment, or approval.","scope":"Catalog-selected Auralink Physical AI product boundary and declared external work","source":"Auralink catalog/product-boundary.yaml at commit c36b8872cc500e817a51e8e7501172fd66c1ec6b","statement":"The machine-readable product boundary selects the horizontal platform and four source-candidate verticals while excluding hardware, HIL, certification, and activation claims.","status":"current"},{"classification":"public","collected_at":"2026-08-24T12:08:47Z","digest":"54b823c7d1776766831581d27cf46cd29c4f7c4e8020eb6b2fa6d166c80981ac","id":"ev-reference-releases","level":"E1","limitations":"The catalog describes governed source and loopback boundaries; it is not current-head aggregate, HIL, independent, production, or customer evidence.","scope":"Four catalog-selected source-reference packs and their declared supported and excluded claims","source":"Auralink catalog/reference-releases.yaml at commit c36b8872cc500e817a51e8e7501172fd66c1ec6b","statement":"The reference-release catalog declares source-only EV Charging, Smart City, Robotics, and Industrial packs with simulation or developer-loopback hardware scope and explicit excluded claims.","status":"current"},{"classification":"public","collected_at":"2026-08-24T12:08:47Z","digest":"d84c3cb18f56f0199ddb62ef88afbeaf2d7de4a8ab09475d06e3b64f2a74e5d4","id":"ev-open-evidence-gates","level":"E0","limitations":"The ledger records missing evidence and exit criteria; it neither performs the external work nor predicts that approval will be granted.","scope":"SAFETY-REALHW-001, HIL-VALIDATION-001, PROTOCOL-CERTIFICATION-001, and SAFETY-CERTIFICATION-001","source":"Auralink docs/audit/findings.yaml at commit c36b8872cc500e817a51e8e7501172fd66c1ec6b","statement":"The governed findings ledger keeps four external physical-product gates open: production-device integration, source-bound HIL, independent protocol or interoperability evidence, and independent safety or regulatory approval.","status":"current"}],"method_id":"HC-OPDG-001","method_version":"0.1.0","product":{"accountable_product_leader":"Mohammed Cherifi","classification":"public","current_stage":"productization","excluded_uses":["Authorization of real-hardware actuation, production rollout, or customer deployment","Safety, regulatory, protocol, interoperability, cybersecurity, privacy, or conformity certification","A claim that source presence, simulation, loopback evidence, or a structurally coherent graph proves operational readiness","A customer case study, independent adoption claim, benchmark, or performance guarantee"],"id":"auralink-source-release-boundary","intended_use":"Govern whether Auralink may progress from its catalog-selected source-only release-candidate boundary toward production physical-system activation.","name":"Auralink Physical AI source-release boundary","summary":"A Hyperion-owned pre-production reference decision system that keeps Auralink's software-reference result separate from hardware, deployment, certification, and customer claims."},"release_cases":[],"revision":1,"schema_version":"launchpad.physical-ai-product-graph/v1","updated_at":"2026-08-26T16:56:39Z"}