Python 0.3.0 source, broker, runner, typed adapters, deployment instructions and supplied tests. Preview workspace connectivity was exercised using a synthetic host-side action over a real Unix socket; no locked Docker worker or billable model call ran here.
Point-in-time 0.3.0 suite: 66 tests discovered, 57 passed and 9 Docker-gated tests skipped; no failures. These are builder observations, not independent assurance. The current 0.3.2 package adds domain/IP controls and is not assessed by this historical report. No comprehensive penetration test was performed.
IR-01 · Independence not established
Reviewer independence & scope
Prepared by the AI builder involved in implementation. No external reviewer, signed scope or conflict declaration has been supplied.
Required next evidence: Appoint a qualified external reviewer and agree version-specific scope.
IR-02 · Source inspected · host untested
Host & worker boundary
The runner requests a non-root, credential-free, read-only worker with restricted mounts and privileges. Actual host, image layers, kernel and runtime configuration were not assessed.
Required next evidence: Inspect the deployed host and pinned image; independently verify provenance and isolation configuration.
IR-03 · Local functional evidence only
Network & action gate
Unix-socket dispatch, typed requests, fixed destinations and rejection paths have supplied test coverage. Network denial across native calls, DNS and child processes has not been verified in a real container here.
Required next evidence: Capture independent host traffic and run all denied-path probes.
IR-04 · Preview connection verified · partial coverage
Workspace decisions & exact approvals
A real host broker submitted a synthetic action through the preview gateway; acknowledged completion appeared on the workspace dashboard and the disposable key was revoked. Supplied local tests cover approval and denial, but this is not a complete independently witnessed deployment journey.
Required next evidence: Repeat allow, quarantine, approval, denial, timeout and revocation from the pinned worker on the target host.
IR-05 · Configured · container measurements pending
Process gate & stop boundary
Host-owned resource limits, bounded runtime and container removal are implemented. The nine Docker-gated tests were skipped because no Docker engine is available here; skipped tests are not passes.
Required next evidence: Measure cgroups, deadline overshoot and detached-child cleanup on Linux.
IR-06 · Ledger tests passed · provider untested
Token & spend gate
Local tests exercise persistent conservative reservations, concurrency and overshoot handling. No real-provider billing reconciliation or model-specific tokenizer qualification was performed.
Required next evidence: Approve a capped provider run and verify current prices, usage bounds and budget reconciliation.
IR-07 · Local replay tests passed · recovery incomplete
Durability & uncertain effects
Consumed request IDs survive restart in supplied tests, and unacknowledged telemetry stops dispatch. This is not business-level exactly-once execution; admitted remote effects can finish after stop.
Required next evidence: Independently inject crash failures and rehearse human reconciliation and downstream idempotency.
IR-08 · Design reviewed · deployment privacy pending
Secrets, evidence & privacy
The design keeps keys outside the worker and bounds evidence. Image-layer leakage, deployed access, retention and approved-provider data leakage have not been independently assessed.
Required next evidence: Review synthetic-marker leakage, data flows and privacy controls on the actual deployment.
IR-09 · Deployment defects corrected · retest pending
Operations & supply chain
Qualification previously allowed a mutable base and fabricated a repository digest from a local image ID. Those paths were removed; the script now requires reviewed digests and matching built/pulled image identity. Two refusal regression tests passed, but the full registry/build workflow has not run here. Dependencies use version ranges rather than a fully locked reviewed inventory.
Required next evidence: Independently retest the registry workflow; pin dependencies and assign patching, backup and incident-response owners.
IR-10 · Release blocked by missing assurance evidence
Findings, retest & release decision
No signed external report, independent retest or customer production acceptance exists. A supplied test suite and this assessment cannot substitute for those records.
Required next evidence: Close findings, obtain a signed external conclusion and record customer risk-owner acceptance.