Skip to content
Agent OS
AOS-PROD-006 Normative foundation

Stock Experiences and Product Surface Roadmap

Stock Experiences and Product Surface Roadmap: scope, decisions, requirements, evidence, risks, and traceability for the Agent OS programme.

Edit on GitHub →

Stock Experiences and Product Surface Roadmap

This specification defines a user-facing capability in terms of entities, actions, history, consent, recovery, accessibility, and provider contracts.

Table of Contents

Purpose and Scope

Area: Product System.

This specification defines a user-facing capability in terms of entities, actions, history, consent, recovery, accessibility, and provider contracts.

This document owns the semantics implied by Stock Experiences and Product Surface Roadmap. 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

  1. Represent nine chronological execution phases separately from ten thematic documentation volumes.
  2. Schedule evidence gates and dependency edges, not only activity dates.
  3. Keep tracker state derived from repository CSV plus API reconciliation; no critical decision exists only in Linear or GitHub.

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. Represent nine chronological execution phases separately from ten thematic documentation volumes.
  • R02. Schedule evidence gates and dependency edges, not only activity dates.
  • R03. Keep tracker state derived from repository CSV plus API reconciliation; no critical decision exists only in Linear or GitHub.
  • 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

  • Acyclic task graph.
  • Milestone and dependency reconciliation.
  • Monthly evidence, risk, spend and decision review.
  • 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

Task Obligation Priority Gate/Milestone Verification
AOS-PROD-110 Deliver Tier 0/1 stock experience alpha P1 M8 daily-use dogfood, accessibility, crash/recovery, provider uninstall/update and cross-target conformance
AOS-OPEN-052 Validate open-phone display, touch, and audio experience P0 M6 EXP-022 common workflows, rotation/mode, touch/audio routing, driver crash and accessibility
AOS-CELL-030 Deliver native cellular data and SMS prototype P0 M6 EXP-042 registration/data/DNS/large transfer/SMS send-receive/duplicate/loss/reset/roaming policy cases
AOS-CELL-070 Integrate cellular data/SMS into open-phone product experience P0 M6 normal/loss/reset/SIM change/duplicate SMS/denied action/restore and accessibility workflows
AOS-ODM-011 Freeze product-hardware architecture envelope P1 M9 product/camera/cellular/power/security/regulatory/supply review and sensitivity scenarios

Risks and Open Questions

  • False precision in long-range dates hides unknown hardware work.
  • Large epics can mask stalled evidence.
  • Parallel tracks can duplicate interfaces without conformance ownership.
  • 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

Planning Reference Anchors

Tier One

AOS-PROD-110 — Deliver Tier 0/1 stock experience alpha; AOS-PROD-110 — Deliver Tier 0/1 stock experience alpha

Tier Three

AOS-ODM-011 — Freeze product-hardware architecture envelope

Tier Two

AOS-OPEN-052 — Validate open-phone display, touch, and audio experience; AOS-CELL-030 — Deliver native cellular data and SMS prototype; AOS-CELL-070 — Integrate cellular data/SMS into open-phone product experience

Tier Zero

AOS-PROD-110 — Deliver Tier 0/1 stock experience alpha; AOS-PROD-110 — Deliver Tier 0/1 stock experience alpha