Pixel 9 Evidence and Reverse-Engineering Dossier
Pixel 9 Evidence and Reverse-Engineering Dossier: scope, decisions, requirements, evidence, risks, and traceability for the Agent OS programme.
Pixel 9 Evidence and Reverse-Engineering Dossier
This specification treats hardware support as an evidence programme with explicit documentation rights, recovery paths, quality gates, and replacement strategies.
Table of Contents
- Purpose and Scope
- Normative Position
- Operating Model
- Requirements
- Failure and Degradation
- Evidence and Acceptance
- Implementation Obligations
- Risks and Open Questions
- Related Documents
- Planning Reference Anchors
Purpose and Scope
Area: Hardware Programme.
This specification treats hardware support as an evidence programme with explicit documentation rights, recovery paths, quality gates, and replacement strategies.
This document owns the semantics implied by Pixel 9 Evidence and Reverse-Engineering Dossier. It does not assert that every described subsystem already exists. It defines the target model, constraints, evidence needed to trust an implementation, and the boundary with adjacent documents.
Normative Position
- Pixel 9 is an evidence and quality-ceiling track, not the platform architecture.
- Allowed Android/Linux uses are stock baselines, lawful observation, recovery, extraction, and temporary isolated bridges with end dates.
- Every legacy cell declares inputs, outputs, taint, license, security boundary, replacement owner, and final acceptable gate.
Operating Model
The operating model is contract-first and evidence-driven. A component declares its authority, resources, lifecycle, error model, cancellation and timeout behavior, observability, version, and compatibility promise. Backends are replaceable only when the same conformance suite passes and no forbidden platform type leaks into portable layers.
Implementation proceeds through a reference model or mock, deterministic QEMU evidence where relevant, documentation-first physical hardware, and quality-hardware evidence. Pixel 9 adapters remain quarantined according to ADR-0004.
Requirements
- R01. Pixel 9 is an evidence and quality-ceiling track, not the platform architecture.
- R02. Allowed Android/Linux uses are stock baselines, lawful observation, recovery, extraction, and temporary isolated bridges with end dates.
- R03. Every legacy cell declares inputs, outputs, taint, license, security boundary, replacement owner, and final acceptable gate.
- R04. Specify normal, partial, denied, timeout, cancellation, restart, upgrade, and permanent-failure behavior.
- R05. Expose structured diagnostics without leaking secrets or vendor-specific implementation details.
- R06. Link material unknowns to a claim and, when testable, an experiment with an owner and gate.
- R07. Update affected documentation and task data when evidence changes the model.
Failure and Degradation
Degradation must be explicit rather than accidental. The system reports capability absence, reduced quality, unavailable provider, stale data, or unsafe condition through typed states. It must not silently fall back to broader authority, unrestricted legacy execution, unverified firmware, lossy data migration, or irreversible agent action.
Recovery defines what state is retained, reconstructed, re-enrolled, compensated, or intentionally discarded. Unsupported hardware or providers are rejected at binding time where possible.
Evidence and Acceptance
- Dependency scan proving no Android/Linux types above adapters.
- SKU-specific acquisition and recovery dossier.
- Native replacement or explicit track termination at each gate.
- Evidence records target identity, hardware revision, firmware, source commit, toolchain, configuration, seed, timestamps, artifacts, expected result, actual result, and reviewer.
- Acceptance requires the referenced tasks to meet their own criteria; prose completion is not implementation completion.
Implementation Obligations
Risks and Open Questions
- A temporary bridge can become permanent through schedule pressure.
- Factory images and firmware may restrict redistribution or reverse engineering.
- Pixel SKUs, unlockability, firmware, and vendor interfaces vary.
- Open-question rule: an unanswered high-impact question becomes a claim/experiment record and cannot be hidden in meeting notes.
- Stop rule: work stops or changes track when legal rights, recovery, debug access, safety, or the required evidence path is unavailable.
Related Documents
- Product vision
- Portable system architecture
- Portable device-service contracts
- Hardware portfolio
- Decision gates
- Claim register
Planning Reference Anchors
Experiments
AOS-CAM-090 — Build a lawful Pixel-class camera quality oracle corpus; AOS-P9-090 — Establish Pixel 9 stock baseline, SKU, unlock, and recovery evidence; AOS-P9-090 — Establish Pixel 9 stock baseline, SKU, unlock, and recovery evidence; AOS-P9-091 — Produce Pixel 9 boot-chain and early-diagnostics dossier; AOS-P9-092 — Test Pixel 9 USB, storage, display, and touch feasibility; AOS-P9-092 — Test Pixel 9 USB, storage, display, and touch feasibility; AOS-P9-093 — Test Pixel 9 GPU, IOMMU, firmware, and power feasibility; AOS-P9-093 — Test Pixel 9 GPU, IOMMU, firmware, and power feasibility
Role
AOS-P9-090 — Establish Pixel 9 stock baseline, SKU, unlock, and recovery evidence; AOS-P9-090 — Establish Pixel 9 stock baseline, SKU, unlock, and recovery evidence
Stop
AOS-P9-092 — Test Pixel 9 USB, storage, display, and touch feasibility; AOS-P9-092 — Test Pixel 9 USB, storage, display, and touch feasibility; AOS-P9-096 — Issue the Pixel 9 continue, limit, partner, or stop decision