Evidence

What has been exercised, and at what boundary

A useful result names the source revision, environment, caller, provider, action, and observable outcome. Coverage turns those records into current capability verdicts.

0.3.0 is released

The release notes list the attached packages, checksums, signing state and package verification.

0.2.0 is released

One shared runtime now brings durable jobs and downloads, AI inference, service-held credentials, application presence and operator controls together. Download 0.2.0 or read the release verification report.

Windows: installation through recovery

Both per-user and machine installation passed on x64, including upgrade from 0.1.7, reinstall, failed-upgrade rollback, startup in a fresh session, crash recovery and removal. The MSI is unsigned. ARM64 is cross-built and has no hardware installation evidence.

Linux: a real download through the installed service

A disposable Ubuntu account installed the runtime under its systemd user manager, downloaded and verified bytes, observed the completed job and removed the installation while retaining user data. Installation and removal without a user manager also passed. ARM64 installation remains untested.

macOS: package available, identity limit explicit

The universal package is signed, notarised and stapled. Local launchd lifecycle checks passed separately. Protected service calls still lack the required caller proof; this release makes no macOS capability-readiness claim. The final signed package still needs end-user installation qualification.

Current integration evidence

Provider substitution

A coding-agent integration exercised chat through OA's mediated native provider route, including tool use, operation ownership, cancellation, lost-reply reconciliation, restart, audit attribution, and revoked-rights refusal.

Application activation and interaction

A closed image editor was activated through OA, announced readiness from its own process, bound actions to the current workflow, previewed a change, applied it separately, read it back, and refused stale context.

Durable downloads and storage

The image-editor adopter submits retained download jobs, observes them across reconnects, and can use the service-selected shared storage backend. Replacement and restart paths have focused evidence.

Operator controls

Focused checks cover permission decisions for named programs, provider and application visibility, permission to open apps, revisioned configuration, log reading and observation, credential metadata, and structured diagnostic results.

How to judge a result

ScopeThe exact operating system, architecture, language, application, process boundary, and provider.
BehaviorThe request and observable result, including refusals, interruption, replacement, and restart where relevant.
AuthorityThe component that supplied caller identity, rights, provider selection, credentials, and outcome evidence.
LimitsThe boundary of the run. Skipped, hidden, unavailable, and unexercised checks remain unverified.

Evidence routes

Generated coverage

Capability, language, and platform cells carry the reviewed current verdict and its public evidence route where available.

Open coverage

Public source

Contracts, generated clients, runtime composition, focused tests, and source adopters make the checked boundary inspectable.

Browse the organization

ComfyUI adopter

ComfyUI is a node-based image generation editor. Its adopter shows durable download, storage, logging, application presence, and workflow interaction integration points.

Inspect the adopter

Earlier public records

Dated transcripts preserve older cross-language, transfer, identity, and lifecycle observations. Their scope belongs to the recorded revision.

Browse dated results

Claims that require separate evidence