Available, demonstrated or still pending.
Evidence as of 23 October 2026. Source review, a passing build, an installed release and a successful native experiment establish different things.
This is a dated snapshot. Check your installed build and private workspace receipts for present connectivity. These docs do not show live service status or imply that all current source is deployed.
| Capability | State at this snapshot | Boundary |
|---|---|---|
| Private owner boards/tasks/sessions | Deployed owner preview | Protected workspace release 2456 / UI13 remains the delivery baseline. |
| Standalone downloadable client | Released v0.1.0-preview.1 | Unsigned private release from 21 October; original local dashboard and explicit inventory. It is older than the enrolled central client. |
| Enrolled metadata discovery | Installed and observed on scoped Windows/Linux clients | Current activity, coverage and receipt age must be checked; no global native control implied. |
| Private Claude history | Bounded transfer observed; requested full coverage open | Partial capture exists. Later codecs/transfer/export source is not accepted complete activation. |
| Owned native questions | Finite Codex/Claude browser-answer proofs | Version-pinned original transport only; broad lifecycle/permission adoption unproved. |
| CEO native MCP read/report | Real finite experiments on 22 and 23 October | Scoped read/note, ended and revoked. No timer, code fix, child delegation or direct Desktop push inferred. |
| General request-to-native dispatch | Source building blocks; broader acceptance pending | Installed version, grant, native proof and destination routing remain separate gates. |
| Automatic handoffs and new-session rotation | Requested; manual workflow recorded | No automatic compaction policy or successor launch claimed. |
| Cross-device vault/restore | Limited early experiments | No complete user-ready backup/removal/restore product acceptance. |
Recent changes
23 October · Better continuity, another bounded native reply
The workflow now calls for an explicit continue-or-successor decision and a durable handoff rather than unbounded reuse of a growing conversation. Product automation remains pending. A finite CEO turn replied and posted a recommendation; a further bounded board-assessment turn completed and its authentic reply was delivered to the requested Desktop chat through the owner bridge.
22 October · First actual native CEO MCP report
The ordinary MCP route completed a native board snapshot and attributed report. Native cleanup and temporary actor revocation were verified. This supersedes the earlier “first native report blocked” status; stronger custom custody was not a prerequisite for this bounded proof.
22 October · Published workspace UI
The protected owner workspace release passed its documented UI and preservation checks. Later prepare pipelines and source candidates remain separate from that deployed release.
21 October · Private installable preview and central workspace
Credential-free Windows/Linux release packages, authenticated download/checksum verification and bounded install checks were completed. The separately enrolled private workspace and scoped metadata discovery followed with their own profiles and access.
How to interpret status
- Requested: an accepted product outcome or workflow direction.
- Source implemented: code exists; release/runtime acceptance may be pending.
- Experiment demonstrated: a finite result on the stated provider/device/version.
- Installed / deployed: a specific build was placed in service; only its verified capabilities apply.
- Unresolved: missing evidence, compatibility, permission or product behavior remains.
Earlier evidence and stable links
The archived evidence page preserves the older 22 October snapshot and historical experiment deep links. Its blocked CEO statements describe that earlier time; use this page for the later finite native result. Historical findings are not silently rewritten as new acceptance.
The requested documentation destination is docs.delegate.haviar.xyz. The earlier docs.delegrator.haviar.xyz site has a different hostname. Initial coexistence is the migration choice; no redirect or hostname equivalence is implied before deployment verification.