What has been built, and what proved it.

Select an increment to read its scope, what verified it on each surface, its boundaries and its receipts.

• Gate 10 CLI provider rejection error surface

  Recorded: 2 September 2026, Australia/Brisbane

• Gate 10 XCUITest automation attachment

  Date: 2 September 2026, Australia/Brisbane.

• Gate 13 aggregate provider-order assertion

  Date: 2 September 2026 (Australia/Brisbane)

• Gate 15 — build-tab usage and Apple upload workflow

  Date: 5 September 2026, Australia/Brisbane.

• Gate 15 Codex timeline delta flood

  Date: 4 September 2026, Australia/Brisbane

• Gate 15 — clear assistant selection and message delivery

  Date: 5 September 2026, Australia/Brisbane.

• Gate 15 — iPad device-owner authentication loop

  Date: 5 September 2026, Australia/Brisbane.

• Gate 15 — newest-first activity and persistent token monitor

  Date: 5 September 2026, Australia/Brisbane.

• Gate 15 native provider-request approval boundary

  Date: 4 September 2026, Australia/Brisbane

• Gate 15 — native review and reconnect repair

  Recorded: 5 September 2026, Australia/Brisbane. Gate 15 remains `ACTIVE`.

• Gate 15 — exact session navigation and runtime-owned click gates

  Date: 5 September 2026, Australia/Brisbane. Gate 15 remains ACTIVE.

• Gate 15 — native session continuation and visible runtime state

  Recorded: 5 September 2026, Australia/Brisbane. Gate 15 remains `ACTIVE`.

• Gate 15 — native terminal paste integrity

  Recorded: 5 September 2026, Australia/Brisbane. Gate 15 remains `ACTIVE`.

• Gate 2 failure capsule — explicit termination state

  Date: 1 September 2026, Australia/Brisbane

• Gate 2 failure capsule — locked Mac data protection

  Date: 1 September 2026, Australia/Brisbane

• Gate 2 failure capsule — PTY ANSI assertion race

  Date: 1 September 2026, Australia/Brisbane

• Gate 2 failure capsule — streaming redaction boundary

  Date: 1 September 2026, Australia/Brisbane

• Gate 2 failure capsule — capability accessibility locator

  Date: 1 September 2026, Australia/Brisbane

• Gate 2 failure capsule — runtime fixture propagation

  Date: 1 September 2026, Australia/Brisbane

• Gate 2 failure capsule — UI runtime product name

  Date: 1 September 2026, Australia/Brisbane

• Gate 2 failure capsule — running runtime rebuild race

  Date: 1 September 2026, Australia/Brisbane

• Gate 2 failure capsule — UI runtime framework search path

  Date: 1 September 2026, Australia/Brisbane

• Gate 2 failure capsule — UI-test sandbox inheritance

  Date: 1 September 2026, Australia/Brisbane

• Gate 2 failure capsule — signed runtime test environment

  Date: 1 September 2026, Australia/Brisbane

• Gate 2 failure capsule — live terminal accessibility

  Date: 1 September 2026, Australia/Brisbane

• Gate 3 failure capsule — locked data protection

  Classification: environment defect

• Gate 4 locked-session data-protection capsule

  Date: 1 September 2026, Australia/Brisbane

• Gate 5 locked-session native viewer replay

  Date: 1 September 2026, Australia/Brisbane

• Gate 6 Android foreground proof repair

  Classification: test defect. Status: repaired and replayed.

• Gate 6 native accessibility and suite replay

  Classification: test defects. Status: repaired and replayed.

• Gate 6 web driver repairs

  Classification: test defects. Status: repaired and replayed.

• Gate 7 aggregate device-toolchain timeout

  Classification: product latency-boundary defect, repaired and regression-covered.

• Gate 7 native mission accessibility identifier

  Classification: product accessibility defect, repaired and regression-covered.

• Gate 7 parallel mission mutation race

  Classification: product defect, repaired and regression-covered.

• Gate 9 clean-clone resource-timeout repair

  Status: repaired and clean-clone-verified.

• Gate 9 current-head runtime race repairs

  Status: repaired and hosted-verified.

• Gate 9 hosted file-protection capability

  Status: repaired and hosted-verified.

• Gate 9 hosted-runner ripgrep repair

  Status: repaired and hosted-verified.

• Gate 9 hosted Swift test oversubscription

  Status: repaired and hosted-verified.

• Account lanes

  Status: implemented (increment 13, the account registry of the workload patch). Code: `Packages/OverwriteCore/Sources/AccountLaneModels.swift`, `AgentRuntimeManager` (lane registry, probes, descriptors, launches), `PersonalCLIProviderRegistry.laneAuthenticationState`, `PersonalCLIClient.environment(_:lane:)`, routes `GET/POST /v1/agents/lanes`, `POST /v1/…

• Agent parity: every lane gets tools, the browser, sign-ins, context and effort

  Status: programme in progress (increments 18–26). The founder's requirement of 18 September 2026: Claude, Grok, Gemini and ChatGPT (Codex) all need access to the broker's tools, control of the shared browser, the ability to fill usernames and passwords on approved sites, injected context, and an effort level the orchestrator can switch per task.

• Allocation and effort master

  **Version 2 — 22 September 2026.** The one policy the orchestrator uses to allocate work to lanes and to set effort, for every task of a project from its first draft to its store upload. It replaces six drafts the founder supplied on 19 September 2026 — three editions of *AI API token pricing and ability matrix* (draft, revised, reviewed) and three orches…

• Cache invalidation

  Status: dependency-scoped for context packs and document reads since increment 14; whole-tree for handoffs and evidence by design (specification §4).

• The complete portal programme — 20 September 2026

  What the founder asked for on 20 September, in one plan: the iPad as a complete portal into the Mac (the iPhone its compact version), pairing that needs no portal page and no Terminal, the browser inside Overwrite, store delivery through that browser, API-key lanes, and the CLIs' own instruction files. Each row is one increment with the usual loop (packag…

• Context compiler

  Status: partial. The single assembly point for plan-task context is `ContinuityManager.contextPack` (`Packages/OverwriteRuntimeKit/Sources/ContinuityManager.swift`); contracts are in `Packages/OverwriteCore/Sources/ContextContinuityModels.swift`.

• Device journeys: the runtime drives the app on its own simulator

  Status: fixture-verified and run for real against the pad app on the runtime's simulator (increment 53) and against the runner's fixture on the runtime's emulator (increment 56; see `docs/BUILD_STATUS.md`). This answers the founder's requirement that click-through on iOS and Android devices is contained within Overwrite: a native app's acceptance criteria…

• Gearlog proving run

  Status: **in progress** (started 19 September 2026). The founder's instruction: build a complete equipment-tracking product — website, iPhone and Android apps, hosted, on a cheap domain, uploaded to TestFlight and Google Play — *through Overwrite*, and repair Overwrite wherever it cannot finish the job. This note records what Overwrite did, where it fell…

• Model router and dispatch governor

  Status: partial. Code: `Packages/OverwriteCore/Sources/RoutingModels.swift` (`CapabilityRouter`, `RoutingPolicy`, `CapabilityRegistrySnapshot`, `TaskClass`), `Packages/OverwriteRuntimeKit/Sources/RoutingManager.swift`, `DispatchGovernor.swift`, `RuntimeServer+Scheduler.swift`, `RuntimeServer.performPlanTaskLaunch`.

• Operational help: Overwrite answers questions about itself

  Status: fixture-verified (increment 20; see `docs/BUILD_STATUS.md`). The founder's requirement of 18 September: the system must answer technical and operational questions about the Overwrite application, not only about the project.

• Override workload audit — existing implementation against the intelligent-scheduler specification

  Audited: 2026-09-18, local `main` at `11031c9` (unified increment 11); statuses updated after increments 12 (measurement) and 13 (account lanes) on the same day. Role: BUILD. Method: execution paths were traced from the runtime routes (`Packages/OverwriteRuntimeKit/Sources/RuntimeServer.swift`) through the actors they call, into the protected stores; noth…

• Override workload patch — completion report (as of 18 September 2026)

  Role: BUILD. Increments 12–16 on local `main` (`4ddcde1`, `b895e7f`, `bf8a59d`, `861ae3f`, `ce0f207`), each with its own verification loop and evidence file under `Evidence/Gate15/`. Nothing is pushed; nothing live was performed. This report states what exists, what was measured and what remains. The audit it follows is `override-workload-audit.md`.

• Plan drafting: from the founder's request to an accepted plan

  Status: fixture-verified (runtime and Mac; see `docs/BUILD_STATUS.md`, increment 19). This closes the gap the founder asked about on 18 September: nothing turned "build an app that tracks business equipment" into the runtime's product plan.

• Project intelligence

  Status: partial — the deterministic file and import index exists (increment 14); symbols, routes, tables, tests and a knowledge inspector do not yet (specification §3–5, §33).

• Research section

  Status: built (increment 46). Code: `Web/src/app/research/page.tsx`, `Web/src/components/research-dashboard.tsx`, `Web/src/lib/research.ts`, `Web/scripts/build-research-data.mjs`, data `Web/src/research/research-data.json`.

• Shared results bus and evidence graph

  Status: partial — findings exist since increment 16 and join the ledgers below; agents cannot record findings through the bridge yet, and findings carry file digests rather than a full evidence graph (specification §19–21).

• Routing and effort patch plan

  Written 19 September 2026 (BUILD), from the founder's question "is this the best way to manage this?" about how the account and the effort are chosen. Ground truth as built is in `model-router.md`; this document plans the patches, in order, with what each changes, how it is proven and what it must not do. Nothing here is built yet except where marked.

• Security boundaries of the workload architecture

  Status: enforced as described; tenancy is single-operator. See also `docs/SECURITY_MODEL.md` and `docs/THREAT_MODEL.md`.

• The browser inside Overwrite: the founder's sign-ins, the AI's driving

  Status: fixture-verified (runtime, driver, iPad and web; the Mac's own *Browser* mode waits on the Xcode 27 Metal toolchain — see `docs/BUILD_STATUS.md`). This answers the founder's question "how is a controllable browser open, with tabs and the ability to log into many sites, for the AI to control?" — and, since increment 79, "without any external window".

• Store delivery through the browser

  Status: fixture-verified (increment 80; see `docs/BUILD_STATUS.md`). What a store only offers in its console — the Play Console's internal-testing release, App Store Connect's app record, tester group and review submission — Overwrite drives through the project's browser inside Overwrite (`docs/architecture/shared-browser.md`), as approval-gated release a…

• Task DAG

  Status: complete for compiled plans; decomposition of a goal into requirements is founder-authored. Code: `Packages/OverwriteCore/Sources/ProductPlanModels.swift`, `PlanMissionCompiler.swift`, `OrchestrationModels.swift`, `Packages/OverwriteRuntimeKit/Sources/ProductPlanOrchestrator.swift`, `MissionOrchestrator.swift`, `RuntimeServer+Scheduler.swift`, `Ru…

• Token accounting

  Status: implemented (increment 12, Phase 1 of the workload patch). Code: `Packages/OverwriteCore/Sources/WorkloadMeasurementModels.swift`, `Packages/OverwriteRuntimeKit/Sources/WorkloadMeasurement.swift`, `DispatchGovernor.swift`, store tables `usage_observations`, `entitlement_observations`, `dispatch_decisions`, `context_manifests` (mission store schema…

• Tool broker

  Status: complete for the reviewed catalogue. Code: `Packages/OverwriteCore/Sources/ToolBrokerModels.swift`, `Packages/OverwriteRuntimeKit/Sources/ToolBroker.swift`, `ToolBridge.swift` (`owd tools-bridge`), `RuntimeServer.routeTools` / `routeToolBridge`, `ToolLedgerSummariser.swift`.

• UI shell and design tokens

  Status: tokens and every surface restyled and journey-verified (see `docs/BUILD_STATUS.md`). The design brief is the "CodeFlow" IDE mockup of 18 September 2026: the same style, with a layout that reflects what Overwrite is.