Skip to content

Prove a complete delivery on an owner-selected application #4

Closed

Description

@gustavonline

Result — 10 October 2026

Delivered and installed: AIOS 0.27.0, through PR #49. The real application pilot passed as an assisted native Factory delivery.

The owner selected AIOS-plugin. The accepted final result gives Context the same Primary/Docs rows as Skills and Memory, adds space in the dashboard/Settings, and makes the chat bubble open the GitHub repository directly. The earlier feedback-form proposal was superseded by that explicit owner choice. No mail service, telemetry or personal-context export was added.

Bound evidence

Boundary Observed result
Source Base 152fcdafb9ad5f3ec59a2e60b61f09bbe61f1fea; final independently reviewed candidate 4595f9c3ab1d9b373534d4adab632c0969f4f445. Merge 3977b4de6da004bdbca47e383862390c2e4cd1fe has the same tree 89a9564db368ca9bbd049972caae81f7dda44c7c.
Implementation Native T3 worktree-bound Claude Opus 5.5, High, fast mode off; one writer. Native version/profile/workspace observations are retained privately.
Review Separate native Codex GPT-6 Astra High review. A real P2 found GitHub failure/retry could hide a stale Context warning and Load latest. The same writer isolated the error; independent review passed the exact repaired tree.
Checks Node 22 locked install/build, 83 sidebar tests, bundled smoke, package/release validation and required Python checks. Final PR, main and tag/release CI pass.
Visual/native behavior Sample screenshots in PR49; light/dark, narrow panel and short Settings viewport checked. Installed Codex shows 0.27.0; the button opens the real repository URL. Settings preserves existing destinations; unchanged Save is disabled; Cancel returns to the dashboard.
Recovery Failure/retry regression cases preserve existing warnings and recovery controls. Reinstall/reopen recovered a stale desktop plugin instance; owner instruction/navigation files retained identical hashes. The immutable previous v0.26.2 release is preserved. A live downgrade was not rehearsed.
Adoption Z13 source is clean at delivered main. Mac native package follows the published source again; owner data and the separate local development workspace were preserved.

Acceptance

  • Pin scope, base, acceptance and delegated admission/delivery authority.
  • Use a bound worktree and appropriate native methods/model; verify meaningful regressions.
  • Obtain independent review, repair substantive findings and refresh affected evidence.
  • Complete actual PR/CI/merge/tag/release without bypassing protections.
  • Verify the installed application behavior in the selected Codex client.
  • Exercise proportionate failure/recovery and retain the previous version.
  • Report interventions, rework, elapsed time and usage limits honestly.

Operational limits and follow-up

The lead, writer and reviewer used native T3 on the qualified host; the coordinator handled bounded approval requests, Node 22 checks, browser inspection and release/adoption. Reviewer requests were individually inspected (31 + 2 in the earlier rounds; 4 + 2 in final review/repair), not blanket-approved. The writer sandbox could not execute the host Node toolchain. Shared AIOS authoring-plugin discovery was unavailable; the repository explicitly permits the reported source-method fallback. These gaps remain in #7 and do not establish unattended throughput.

Implementation began 18:18 UTC; final independent review finished 19:58 UTC; release was published 20:10 UTC. These elapsed times include owner-directed UI revisions, coordinator work and approval waits; they are not active inference time. Native aggregate tokens, subscription cost and quota savings were not established and remain unknown. Host/phone observations are in #2.

The owner's subsequent request to complete the AIOS repository's Foundation assessment, repair its current Factory references and consolidate the duplicated Project Foundation skill is separate follow-up work. It does not change the delivered UI pilot's evidence. Kastanje, Defence and scheduled backlog intake remain outside this pilot.

Metadata

Metadata

Assignees

No one assigned

    Labels

    adlcApplication and defensive work methodsqualificationObserved proof of a capability

    Type

    No type

    Projects

    • Status
      Triaging

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions