04 / AOSWhat exists?
What awaits verification?
Site tests and AOS application evidence are tracked separately. A working diagram does not demonstrate a working service.
AOS application
Latest source record: 19 September 2026. No newer runtime evidence supplied.
Architecture & contracts
Verified at package levelDocuments, schemas and synthetic examples prepared; package validation recorded.
- Evidence
- docs/STATUS.md
- Date / version
- 2026-09-19 · Commit not supplied
- Limitation
- Not evidence of application or model execution.
Operator / Gateway
Awaiting verificationArchitecture contract exists; no newer implementation evidence supplied.
- Evidence
- docs/STATUS.md
- Date / version
- 2026-09-19 · Commit not supplied
- Limitation
- Actual target environment, model integration or training tests are unverified.
Bonsai-2 / Decider-2B
Awaiting verificationArchitecture contract exists; no newer implementation evidence supplied.
- Evidence
- docs/MODELS.md
- Date / version
- 2026-09-19 · Commit not supplied
- Limitation
- Actual target environment, model integration or training tests are unverified.
Agent Computer
Awaiting verificationArchitecture contract exists; no newer implementation evidence supplied.
- Evidence
- docs/STATUS.md
- Date / version
- 2026-09-19 · Commit not supplied
- Limitation
- Actual target environment, model integration or training tests are unverified.
Dataset / LoRA / adapter
Awaiting verificationArchitecture contract exists; no newer implementation evidence supplied.
- Evidence
- docs/EVALUATION_AND_PROMOTION.md
- Date / version
- 2026-09-19 · Commit not supplied
- Limitation
- Actual target environment, model integration or training tests are unverified.
SEPARATE RECORDThis website
TR/EN pages, interactive diagrams and three explanatory flows are implemented in this repository. Website verification records and repeatable checks are kept in the delivery documentation independently of this public site.
- Status
- Published static website
- Source / date
- README.md · docs/VALIDATION.md · 2026-09-20
- Version / boundary
- 1.0.0 · Website release; not AOS runtime acceptance.
Acceptance criteria
before a calendar.
These phases define evidence requirements, not completion promises. Future dates are not set.
01Design and contracts
Typed state, protocol, registry and data contracts; package-level validation.
Existing evidence: 19 September 2026 design package. Not evidence of a running application.
Available at package level02First deterministic task
Write → read → verify equality in an allowed workspace; intent and result records must match.
Minimal gateway and isolation must exist in the first test. A fixture test is not real-model acceptance.
Awaiting verification03Isolated computer integration
Gateway, mount permissions, restart and later XFCE/noVNC desktop smoke tests.
Evidence for observation and handover without unrestricted host access.
Awaiting verification04Model integration
Decider option tests with pinned backend/checkpoint; Bonsai structured plan and visual assessment tests.
Actual memory, latency and joint-operation measurements on the target environment.
Awaiting verification05Outcome verification and human control
Post-failure observation, recovery, repeated policy checks and queued-input cancellation.
Evidence for approval/rejection/takeover and restart scenarios.
Awaiting verification06Held-out evaluation
Compare baseline and candidate under identical conditions; report uncertainty and human assistance.
Pinned benchmark, raw results, acceptance gates and rollback rehearsal.
Awaiting verification07Data preparation and offline adaptation
Redact, review and split records with known rights; produce a compatible training experiment.
Versioned data manifest, leakage checks, adapter compatibility and explicit promotion decision.
Awaiting verificationOpen questions
Exact backend/checkpoint revisions, joint model memory use, model licensing, LoRA lineage and backend compatibility, adapter switching, image digest, retention periods and actual benchmark results await verification.