Current ledger update: 2026-08-14. Overall release posture: blocked. Older
rows retain their exact run dates and remain historical evidence. This ledger
separates checked-in historical release evidence from an explicitly labeled
uncommitted worktree candidate, records only commands actually run for the stated
update, and preserves explicitly absent external (E) or accountable-owner (O)
evidence. A local
mock, deterministic harness run, reviewed upstream defect, safe default, skip,
or disabled feature is never promoted into evidence it does not provide.
Evidence tiers:
| Tier | Meaning |
|---|---|
H |
Hermetic unit, contract, property, vector, or fault-injection evidence. |
L |
Local multi-process or real local service integration. |
P |
Privileged exact host/OS/kernel/process-boundary evidence. |
E |
Real harness semantics, external peer/SDK/IdP/partner, multi-node failure-domain, model, or production-like lab evidence. |
O |
Signed accountable policy/ceremony/root decision. |
Gate statuses used here:
PARTIAL: cited H/L evidence passes, but a required tier or case is absent.FAILED: a required official suite or stop-ship invariant is non-green.BLOCKED_EXTERNAL: required P/E infrastructure or independent system is absent.BLOCKED_OWNER: required O evidence is unsigned/unresolved.IMPLEMENTATION_GAP: required executable behavior is absent; an interface is not completion.PASSED: every required tier/case is current and reviewed. No gate isPASSEDin this snapshot.
| Scope | Command or record | Observed result | Boundary |
|---|---|---|---|
| Complete authorized repository run | AGENTNET_TEST_POSTGRES_URL='postgresql:///agentnet_test_final?host=/tmp/agentnet-pgsocket-20260713-final&port=55432' AGENTNET_TEST_POSTGRES_ALLOW_MUTATION=1 PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=src .venv/bin/pytest -q -p no:cacheprovider |
983 passed, 0 failed, 0 skipped, 0 xfailed | Includes seven real-PostgreSQL cases, real Unix binding sockets, host-level Bubblewrap network denial, signed backup/restore and archive validation, and current release-manifest verification. Local H/L/P evidence only. |
| Release input, package, and clean install | .venv/bin/python scripts/verify_release.py; SOURCE_DATE_EPOCH=1580601600 PYTHONDONTWRITEBYTECODE=1 UV_CACHE_DIR=/tmp/uv-cache UV_LINK_MODE=copy uv build --offline --no-build-isolation --out-dir /tmp/agentnet-final-build-20260713; clean-wheel install/init/status/backup/restore/demos in evidence/local/2026-07-13-final/manifest.json |
Verifier PASS; locked build backend produced retained, content-validated sdist/wheel evidence; new-environment install and clean schema-v1 status passed | Local package evidence only; it is not an independent signature, SBOM/provenance publication, root ceremony, maintained KMS, or cross-platform qualification. |
npm 0.1.3 packaging patch |
SOURCE_DATE_EPOCH=1580601600 PYTHONDONTWRITEBYTECODE=1 UV_CACHE_DIR=/tmp/uv-cache UV_LINK_MODE=copy uv build --offline --no-build-isolation --out-dir /tmp/agentnet-build-0.1.3-a; repeated in an independent output directory |
Byte-identical retained wheel and sdist; current package tests and release verifier pass | Marketing, discoverability metadata, preview image, and version-only runtime edits; prior PostgreSQL/security evidence remains historical and is not promoted. |
npm 0.1.4 installer repair |
Retained build evidence plus clean public npm-tarball retest from an unrelated cwd | Python artifacts were byte-identical and bounded cwd/version checks passed, but full packed verification later reproduced 894 passed, 16 failed, 7 expected PostgreSQL skips; activation blocked |
The public package omitted six verifier inputs and allowed host-dependent Python minor selection. This row preserves the failed packed-artifact outcome; no production evidence is promoted. |
npm 0.1.5 packed-artifact correction |
Exact CPython 3.13.13; uv>=0.11.28; two independent reproducible Python builds; source release suite; clean installed npm tarball full agentnet verify from unrelated cwd |
Byte-identical wheel/sdist; source 911 passed, 7 expected PostgreSQL skips; packed 911 passed, 7 expected PostgreSQL skips; release verifier PASS |
Exact evidence-file inclusion, portable artifact-retention evidence, interpreter/toolchain selection, explicit old-uv rejection without host mutation, and full packed-tarball prepublication gate only; no identity, authorization, protocol, storage, delivery, A2A, or production-gate semantics change. |
npm 0.1.6 P1–P5 candidate |
Exact CPython 3.13.13; uv>=0.11.28; two independent reproducible Python builds; npm run check; clean installed npm tarball from unrelated cwd |
Byte-identical wheel/sdist; source package gate 999 passed, 7 expected PostgreSQL skips; packed 999 passed, 7 expected PostgreSQL skips; release verifier PASS on 2026-07-15 |
Local candidate evidence for validated-address OIDC, activation, mailbox acknowledgement, bounded artifact client/CLI, protected TaskGrant payload release, and standalone WebAuthn-UV component. No real authenticator/independent host, IdP, harness, PostgreSQL HA, scanner, A2A, owner, production, deployment, or cutover evidence is promoted. |
Published npm 0.1.6 full PostgreSQL verification |
Clean public npm install on the ordinary Hub host; dedicated mutation-authorized loopback PostgreSQL; /root/.nvm/versions/node/v22.23.0/bin/agentnet verify |
1004 passed, 2 failed on 2026-07-15: one stale fresh-schema test expected only migration 1 although current schema is 2; one federation security-revocation HTTP test intermittently returned non-enumerating 404 because its frozen service clock could precede the live policy-decision clock. Isolated federation replay passed. |
Synthetic package evaluation remains allowed, but 0.1.6 must not construct the AgentNet company network, carry real company data, or replace existing A2A. AgentNet stayed inactive and existing A2A stayed unchanged. |
npm 0.1.7 verification-hotfix candidate |
Exact 1.1-second clock-boundary reproduction; focused federation/service tests; 30 repeated security-revocation HTTP runs; UV_CACHE_DIR=/tmp/uv-cache uv run pytest -q --ignore=tests/adapters/test_installed_live_inference.py --ignore=tests/conformance/test_release_manifest.py |
Exact published 404 reproduced before the test-clock fix; 14 passed focused; 30/30 repeated target passes after the fix; code-regression corpus 1049 passed, 7 expected PostgreSQL skips on 2026-07-15. Dedicated PostgreSQL rerun remains required before publication approval. |
Test-only repair: production authorization remains fail-closed and unchanged; clean PostgreSQL tests now require the complete current migration catalog. Use test data only. No network construction, real company data, activation, or cutover. |
npm 0.1.8 confidential-OIDC correction candidate |
Pre-edit writer/critic and constitution review; focused OIDC/config/deployment/invitation/HTTP suite; actual-implementation writer/critic repair pass; broad code-regression corpus; npm run check source and clean packed-package gates |
Pre-edit reviews PASS; focused 71 passed; broad 1060 passed, 7 expected PostgreSQL skips; source package 1010 passed, 7 expected PostgreSQL skips; packed package 1010 passed, 7 expected PostgreSQL skips; release verifier PASS on 2026-07-16. Local real-PostgreSQL rerun was not executed because no PostgreSQL client/server is installed; independent Hub verification remains required after publication. |
H-only confidential-client mechanism evidence: explicit public/POST/Basic methods, runtime-only secret resolution, discovery advertisement, Google three-origin callback profile, rotation/redaction/migration, and invitation verifier binding. No live Google ceremony, real secret, independent approval deployment, owner decision, production activation, network construction, real company data, or cutover evidence is promoted. |
npm 0.1.9 guided identity-only enrollment candidate |
Focused approval/OIDC/CLI/config suites; code-regression corpus; release/package conformance; source npm run check lane; clean npm run check:packed lane; release verifier; two independent SOURCE_DATE_EPOCH=1580601600 builds |
Focused guided lane 80 passed with one expected PostgreSQL skip plus targeted hardening subsets; code-regression corpus 1079 passed, 7 expected PostgreSQL skips; release/package conformance 29 passed; source and clean packed package each 1029 passed, 7 expected PostgreSQL skips; package check, packed check, and release verifier PASS; byte-identical wheel and sdist retained under evidence/local/2026-07-16-v0.1.9/ on 2026-07-16 |
H/L candidate evidence only: versioned approval-store migration, hash-only continuation, Core-only receipt retrieval, PoP-before-retrieval, exact response-loss recovery, owner-only resumable CLI state, and zero implicit entitlements. No current mutation-authorized PostgreSQL run, live Google ceremony, release-bound real passkey, independently administered production approval boundary, blank-laptop cross-host test, signed first message/reply, owner decision, real company data, activation, or cutover evidence is promoted. |
npm 0.1.10 recursive-package repair candidate |
Pre-edit package-lifecycle and clock-edge inventory with model-diverse adversarial review; root-ignore negative tests; relay rotation clock fixture; release verifier; two independent SOURCE_DATE_EPOCH=1580601600 builds; explicit source → pack/install generation 1 → repack/install generation 2 verification from isolated state and unrelated cwd |
Relay rotation 25/25 repeated target passes; focused package and relay suites 35 passed; code-regression corpus 1079 passed, 7 expected PostgreSQL skips; both installed npm generations independently reported 1030 passed, 7 expected PostgreSQL skips; package check, two-generation packed check, release verifier, compile, and reproducible-build comparisons PASS on 2026-07-16 |
Release/test-only repair: npm package roots require neither .gitignore nor .npmignore; exact retained sdist validation models Hatchling 1.28.0's unavoidable VCS metadata without requiring that file in installed npm roots; production relay freshness remains unchanged. No current mutation-authorized PostgreSQL, live enrollment, real passkey, first signed message/reply, activation, company data, publication, or cutover evidence is promoted. |
Published npm 0.1.10 independent Hub verification |
Fresh public npm artifact identity check; package check; source → installed generation 1 → repacked generation 2 verification; release verifier; dedicated disposable PostgreSQL 18.4 corpus and migration catalog | Public identity and package check passed; generation 1 1030 passed, 7 expected PostgreSQL skips; generation 2 failed with 1028 passed, 2 failed, 7 expected PostgreSQL skips; dedicated PostgreSQL 1037 passed, 0 failed, 0 skipped; migration catalog 1–3 and schema version 3 verified on 2026-07-17 |
Required recursive package gate failed. Exact failures were conversation task idempotency across a clock boundary and a relay test policy decision recorded on wall time while the relay used an injected clock. 0.1.10 remains immutable and is not package-green; no enrollment, activation, company data, or cutover was allowed. |
npm 0.1.11 recursive-generation repair candidate |
Deterministic one-second conversation retry reproducer; exact relay and internal-invitation repeated-run reproductions; explicit-deadline negative test; coherent relay/invitation test clocks; stable approval-purpose config serialization; model-diverse critic and constitution review plus bounded claude -p clock analysis; broad and repeated regression runs; release verifier; two independent SOURCE_DATE_EPOCH=1580601600 builds; explicit source → pack/install generation 1 → repack/install generation 2 verification |
Conversation/relay/assignment focused suites 56 passed; relay target 100/100 repeats; activation serialization 100/100 repeats; internal-invitation HTTP target 100/100 repeats; code-regression corpus 1079 passed, 7 expected PostgreSQL skips; unfiltered local run 1106 passed, 2 preserved G01 failures, 7 expected PostgreSQL skips; complete npm run check PASS with source and both installed npm generations each reporting 1030 passed, 7 expected PostgreSQL skips; package check, release verifier, compile, and reproducible-build comparisons PASS on 2026-07-17 |
Minimal production change reuses the stored encrypted canonical conversation deadline only for exact omitted-deadline proposal retries; explicit caller deadline changes still conflict. Relay and invitation production freshness remain unchanged at 300 seconds; only test fixtures now use coherent clocks. Config change only sorts an unordered approval-purpose set during serialization. No current mutation-authorized PostgreSQL, live enrollment, real passkey, first signed message/reply, activation, company data, publication, or cutover evidence is promoted. |
0.1.12 cross-platform implementation, pre-version real-host gate |
GitHub Actions run 29610467753 at commit 6d7834e; pinned Node 24.18.0, uv 0.11.28, CPython 3.13.13; platform contracts; package check; npm pack/install; direct launcher execution from unrelated cwd |
Ubuntu 13 passed, 8 skipped; macOS 15 passed, 6 skipped; Windows 17 passed, 4 skipped; package check and packed install/launch passed on all three hosts on 2026-07-17 |
P-shaped exact-host evidence for package launch, canonical state, portable SQLite, macOS peer/read-only-pipe/link denial, Windows SID/DACL/reparse/named-pipe/replay/capability-theft/Job cleanup, and host-gated imports. This is not signed installer/update/uninstall/rollback, privileged hostile same-account/path replacement, semantic harness, clean-worker, production, enrollment, activation, company-data, first-message, or cutover evidence. Package metadata at this pre-version commit still read 0.1.11; final 0.1.12 evidence binds the frozen release source separately below. |
npm 0.1.12 cross-platform candidate |
Real-host gate above; DeepSeek security and GLM constitution review with repairs; local unfiltered suite; exact installed-harness probe; release verifier; two independent SOURCE_DATE_EPOCH=1580601600 builds; explicit source → pack/install generation 1 → repack/install generation 2 verification |
Unfiltered local 1122 passed, 15 expected host/PostgreSQL skips; installed deterministic harness 8 passed; source, generation 1, and generation 2 each 1043 passed, 15 expected skips; package check, release verifier, recursive package gate, and reproducible Python builds PASS on 2026-07-17 |
H/L and bounded ordinary-runner P-shaped evidence only. Cross-platform installation creates no identity or authority. No current mutation-authorized PostgreSQL, signed native installer/update/uninstall, privileged hostile-host campaign, semantic clean-worker inference, live enrollment/passkey, independent production host, first signed message/reply, activation, company data, publication, or cutover evidence is promoted. |
npm 0.1.13 canonical onboarding prompt candidate |
Canonical-template commit 2dc177c; pre-release critic and constitution review; focused npm/release conformance; release verifier; two independent SOURCE_DATE_EPOCH=1580601600 builds; complete npm run check source → pack/install generation 1 → repack/install generation 2 verification |
Reviews PASS; focused release/package conformance 30 passed; source, generation 1, and generation 2 each 1043 passed, 15 expected host/PostgreSQL skips; package check, release verifier, recursive package gate, canonical prompt markers, and byte-identical Python builds PASS on 2026-07-18 |
Documentation/skill and regression correction only: one canonical public fresh-laptop prompt is required and unresolved public metadata blocks issuance. The template itself grants no enrollment, approval, authority, messaging, activation, deployment, restart, production, or cutover permission. No mutation-authorized PostgreSQL, live blank-laptop ceremony, passkey, first signed message/reply, company data, npm publication, or production evidence is promoted. |
npm 0.1.14 fresh-laptop single-paste and cross-host entitlement candidate |
Claude Opus onboarding inspection; DeepSeek and GLM adversarial plan and final-diff reviews; constitution-watcher; deterministic CLI/policy/package regressions; Pi skill loader; release verifier; two independent SOURCE_DATE_EPOCH=1580601600 builds; complete source → installed generation 1 → repacked generation 2 package verification |
Reviews and constitution PASS with no blocker; focused release/onboarding/security 58 passed; source, generation 1, and generation 2 each 1048 passed, 15 expected host/PostgreSQL skips; package check, release verifier, recursive package gate, skill loader, prompt/CLI conformance, and byte-identical Python builds PASS on 2026-07-19 |
H/L candidate evidence only: canonical prompt moved to references/examples/; claim-code and reporting channels remain owner-gated under PD-002/PD-001; principal-ID issuance removes beneficiary-private-key transfer while preserving signed/current/same-domain server checks. No mutation-authorized PostgreSQL, deployed Core, live Google ceremony, independent real passkey host, approved claim-code relay, blank-laptop enrollment, first signed message/reply, company data, activation, publication, production, or cutover evidence is promoted. |
npm 0.1.15 ordinary-onboarding simplification candidate |
Explicit authenticated owner instruction; full Claude onboarding-policy review; Codex implementation scout; DeepSeek adversarial review; GLM constitution review; focused approval/onboarding/installed-harness tests; unfiltered local suite; release verifier; two deterministic builds; source → installed generation 1 → repacked generation 2 package verification; GitHub Actions run 29705571577 at commit 1abd4aad0c30f4cf026c050d628da44a83e65b4e |
Final reviewers PASS/converge; focused 23 passed; unfiltered 1128 passed, 15 expected host/PostgreSQL skips; source and both installed npm generations each 1049 passed, 15 expected skips; package check, release verifier, recursive package gate, byte-identical Python builds, and Ubuntu/macOS/Windows package-host jobs PASS on 2026-07-19 |
H/L candidate evidence only. Ordinary onboarding may colocate Core/PostgreSQL/approval under distinct OS identities, uses owner-controlled WebAuthn outside the enrolling harness, and reports independent_boundary_proven=false; separate approval hosting remains optional high assurance. The 128-bit five-minute five-attempt claim code, candidate PoP, no implicit authority, and three individually signed/audited C0 grants remain. The owner instruction is not independent signed O-tier evidence. No live deployment, mutation-authorized PostgreSQL, Google/passkey ceremony, fresh-laptop round trip, company data, activation, publication, production, A2A cutover, or gate promotion is claimed. |
npm 0.1.16 headless enrollment handoff repair candidate |
Headless-flow edge inventory; current OAuth/device-flow source research; Codex scout; writer/DeepSeek critic convergence; DeepSeek constitution review; control-byte/no-TTY/partial-write/resume/default-browser regressions; focused approval/OIDC/CLI suite; unfiltered local suite; release verifier; two deterministic builds; source → installed generation 1 → repacked generation 2 package verification | Reviews PASS/converge; focused 64 passed; unfiltered 1142 passed, 15 expected host/PostgreSQL skips; source and both installed npm generations each 1063 passed, 15 expected skips; package check, release verifier, recursive package gate, and byte-identical Python builds PASS on 2026-07-20 |
H/L candidate evidence only. Explicit --browser terminal reuses existing OIDC/PKCE/WebAuthn/claim-code semantics, writes validated printable-ASCII HTTPS URLs only to verified POSIX /dev/tty, and fails closed without fallback on control bytes, no TTY, unsupported platform, or partial write. Default fresh-laptop system-browser behavior, identity-only enrollment, candidate PoP, replay/expiry/idempotency, existing A2A, and zero implicit authority remain unchanged. No completed live cross-device ceremony, server binding, C0 message round trip, mutation-authorized PostgreSQL, company data, publication, production, A2A cutover, or gate promotion is claimed. |
npm 0.1.17 model-broker request-replay repair candidate |
Broker nonce edge inventory; canonical source scout; GPT-5.5 patch plan; DeepSeek security and constitution reviews; required/malformed/duplicate/concurrent/cross-capability nonce regressions; unfiltered local suite; release verifier; two deterministic builds; source → installed generation 1 → repacked generation 2 package verification | Reviews PASS/converge; focused broker suite 10 passed; unfiltered 1147 passed, 15 expected host/PostgreSQL skips; source and both installed npm generations each 1068 passed, 15 expected skips; package check, release verifier, recursive package gate, and byte-identical Python builds PASS on 2026-07-20 |
H/L candidate evidence only. The capability remains reusable within exact worker/grant/model/expiry/request/token budgets, while every inference requires a persistent per-capability one-use request nonce before transport. Duplicate and concurrent replay fails closed without a second transport call or extra budget spend. No live semantic worker, mutation-authorized PostgreSQL, real-host cross-platform 0.1.17, publication, enrollment, company data, production, A2A cutover, or gate promotion is claimed. |
npm 0.1.18 Core→Approval signed-broker replay repair candidate |
Broker edge inventory; Core/Approval wire-contract reconciliation; Codex implementation plan; DeepSeek security critic; constitution review; exact proof binding/tamper/time/canonicalization/duplicate-header/query and sequential/concurrent/reopen replay regressions; focused approval suite; unfiltered local suite; agentnet verify; release verifier; two deterministic builds; source → installed generation 1 → repacked generation 2 package verification |
Reviews PASS/converge with no blocker; focused approval suite 46 passed; unfiltered 1166 passed, 15 expected host/PostgreSQL skips; agentnet verify, source, and both installed npm generations each 1087 passed, 15 expected skips; package check, release verifier, recursive package gate, and byte-identical Python builds PASS on 2026-07-20 |
H/L candidate evidence only. Every Core→Approval create/status/retrieve request retains Bearer authentication and adds an exact method/path/body/audience/purpose/key/time/nonce HMAC proof; Approval schema v3 persistently and atomically consumes the verified nonce hash before business action, while response-loss retries use fresh broker nonces and preserve separate business idempotency. No mutation-authorized PostgreSQL v3 run, atomic live Core/Approval deployment, live enrollment/passkey, C0 round trip, company data, publication, production, A2A cutover, or gate promotion is claimed. |
Published npm 0.1.19 zero-state C0 release and blocked deployment preflight |
Exact public registry identity/integrity; clean install/launcher/package/Pi-skill checks; source → generation 1 → generation 2 verification; peer-reported remote public-artifact preflight against reportedly live Core schema v3 | Public package checks passed; the remote deployment peer reported that pre-migration require_exact_postgres_catalog failed deterministically with psycopg.ProgrammingError because PostgreSQL format('%I.%I', ...) appeared in a parameterized psycopg query, and reported stopping before mutation on 2026-07-22 |
H/L package evidence plus peer-reported negative deployment evidence only. The peer reported no migration, restart, runtime switch, enrollment, authority, message, company-data action, live C0, or A2A mutation and reported live Core/Approval still on 0.1.18, schema v3; this candidate's retained local evidence does not independently verify that remote runtime report. 0.1.19 is immutable and must not be deployed. |
Published npm 0.1.20 PostgreSQL placeholder correction and blocked read-only preflight |
Public package verification plus independent private-staging, transaction-read-only PostgreSQL 18.4 preflight against preserved live schema v3 | Public package checks passed; %I defect was corrected; preflight then exposed exact-catalog gaps for PostgreSQL 18 contype='n' rows and server-rendered CHECK/index predicates before mutation |
Negative deployment evidence only. The peer reported no migration, restart, runtime switch, enrollment, authority, message, company-data action, or A2A mutation. 0.1.20 remains immutable and undeployable. |
Published npm 0.1.21 PostgreSQL 18 exact-catalog correction and blocked startup |
Exact NOT NULL reconciliation; bounded structural CHECK/index comparison; fail-closed tamper matrix; public package verification; exact public-artifact startup on PostgreSQL 18.4 | Source/package gates passed and independent read-only catalog verification passed at 94 tables, 1,085 columns, 1,398 constraints, 53 indexes; startup then failed because the S4 constraint query aliased pg_constraint as reserved word constraint |
Negative deployment evidence. The peer stopped the failed rollout and later clean-uninstalled AgentNet under owner direction. Pi, A2A, and the PostgreSQL service remained unchanged. 0.1.21 is immutable and undeployable. |
Published npm 0.1.22 PostgreSQL 18 reserved-alias correction |
Alias-only constraint → con repair; focused query regression; full hermetic and disposable real-PostgreSQL 18.4 storage corpus; installed npm-packed candidate verification against the same PostgreSQL lane; broad source regression; Codex critic and constitution review |
Pre-fix regression failed exactly at constraint.contype; post-fix target passed; hermetic PostgreSQL lane 78 passed, 7 expected dedicated-database skips; signature-verified disposable PostgreSQL 18.4 lane 85 passed, 0 skipped; complete source suite 1377 passed, 15 expected host/PostgreSQL skips; installed npm-packed candidate 1305 passed, 8 expected non-Linux host skips; reviews PASS/converged |
H/L release evidence only. Migration SQL/checksums, catalog expectations, identity, authority, bounded C0, messaging, cleanup, and A2A semantics remained unchanged. Later ordinary-server installation debate proved that this public artifact still lacked one product-owned zero-to-running host setup boundary. |
Tagged npm 0.1.23 candidate; staging stopped |
Reviewed product-owned ordinary-server candidate; local source/release/two-generation packed/Pi-loader gates; tag-triggered GitHub staging workflow 30034647834 |
Local gates and reviews passed. GitHub staging CI stopped before registry staging because one hermetic interruption test mocked /usr/bin/useradd on a runner where that path was absent: 1 failed, 1335 passed, 15 expected skips. No package was staged or published. |
Negative CI evidence only. Runtime behavior was not implicated; immutable tag v0.1.23 remains unpublished and must not be moved or reused. |
Published npm 0.1.24 publication candidate |
Exact test-only correction: mock AgentNet's validated host-tool resolver rather than a nonexistent runner filesystem path; reviewed 0.1.23 runtime unchanged |
Corrected focused server-setup/npm lane 46 passed; source lane excluding installed-live inference and release-manifest self-check 1385 passed, 15 expected host/PostgreSQL skips; final retained-artifact, exact prepublication, recursive packed, and Pi-loader checks are bound in the immutable package evidence manifest. |
H-shaped package evidence only. No privileged real-host apply, live PostgreSQL/OIDC/passkey/TLS ceremony, external clean-host install, production durability, authority, deployment, or gate promotion is claimed. |
Published npm 0.1.25 JSON-RPC interoperability release |
Official A2A TCK commit 5996b79f9cefa6fc390980e383e358a66fb9e49e; exact /rpc plus /rpc/ strict aliases; route-bound tenant restoration with missing/spoofed token and conflict rejection; cross-alias idempotency and no-residue regressions; critic and constitution review |
Local A2A 57 passed; source lane excluding installed-live inference and release-manifest self-check 1386 passed, 15 expected host/PostgreSQL skips; focused official JSON-RPC 3 passed; full JSON-RPC MUST 50 passed, 11 failed, 174 skipped; final retained-artifact, exact prepublication, recursive packed, Pi-loader, and public-package identity checks are bound in the immutable 0.1.25 package evidence manifest. |
H/L-shaped public-package evidence only. G04 remains FAILED; TCK fixture/profile failures, worker-driven transitions, cross-SDK/public-peer/callback/streaming/artifact evidence, privileged deployment, production durability, authority, and gate promotion remain absent or separately gated. |
Published npm 0.1.26 ordinary-server convergence release |
Node/uv/AgentNet/systemctl/useradd executable plus full executed package-tree-content-bound approval digest v2; protected-home and broker validation; locked apply reread; bounded product/systemd execution; exact service-identity PostgreSQL peer canary plus parsed HBA/ident and config-load freshness; marker-v2 same-request CAS/retry/interruption plus deterministic persisted-config digest regressions; Windows Unix-import correction; rewritten installer-agent procedure; source skill and packed-source Pi loader |
Focused platform/setup/activation/package/release lane: 152 passed, 9 expected platform skips; code-regression lane excluding installed-harness and release-manifest gates: 1433 passed, 16 expected platform/dedicated-PostgreSQL skips; source and both recursive installed npm generations: 1386 passed, 16 expected skips. Release verifier, source package/syntax checks, bounded process regressions, byte-identical wheel/sdist build, recursive package gate, and source/fresh-packed Pi skill loaders passed. At commit 58a13dd, run 30155733937 passed clean Ubuntu 24.04/PostgreSQL 18 plan, expected PostgreSQL blocker, separate PostgreSQL boundary, apply/start, unchanged retry with setup_marker=already_satisfied, and cleanup; run 30155733938 passed package conformance on Ubuntu, macOS, and Windows. |
H/L-shaped public-package evidence with reproducible retained local wheel/sdist archives and one ephemeral clean-host lifecycle only; these are not persistent-host, hostile-path, or production evidence. Live OIDC/WebAuthn, production durability, authority, G04 promotion, and ship claim remain absent. |
Published npm 0.1.27 communication-only real-network proof release |
Request-v2 explicit artifact_mode=disabled; exact offline_custody; version-disjoint digest-v3/marker-v3; no scanner/artifact state; setup/runtime forbidden-residue gates; all public artifact service and HTTP surfaces fail closed; message/task/conversation/replay artifact bindings deny before custody; signed message/mailbox/ACK/obligation/downward-task local journey; complete operator prompt and setup documentation; constitution, skill-architecture, and adversarial code reviews |
Affected suite 215 passed; npm run check source and two recursively packed generations each 1412 passed, 16 expected platform/dedicated-PostgreSQL skips; release verifier, source/packed package checks, and byte-identical wheel/sdist build PASS. The unfiltered pre-refresh run preserved two installed-harness pin gate failures; they are not waived. Hub root-installed verification later exposed three portability failures before any setup/network mutation. |
H/L public-package evidence only. It proves local implementation and package integrity, not an actual AgentNet network. Network creation, fresh-laptop enrollment, cross-host message/ACK, maintained scanner/FILE/G13, production durability, and ship eligibility remain pending and must be reported separately. |
Published npm 0.1.28 root-installed verifier repair |
Python and Node privileged setup-input readers use two bounded content snapshots, accumulate short reads, retain metadata/path custody checks, and reject coarse-timestamp same-size drift; launcher tests separately prove structured user-owned and service-inaccessible rejection states; release verification rejects pending candidate evidence | Ordinary-user and UID-0 user-namespace focused lanes each 7 passed; server-setup 92 passed; npm conformance 10 passed; source and both clean recursively packed npm generations each 1418 passed, 16 expected platform/dedicated-PostgreSQL skips; those lanes exclude installed-live-inference, subprocess-lifecycle, and bake-off-evidence files, while the two installed-harness pin failures remain non-green and were not rerun or waived; package, release-verifier, launcher, recursive-package, and byte-identical wheel/sdist checks pass. Exact public-package root-installed Hub verification later passed. |
H portability/package evidence only. UID-0 is a Linux user namespace, not external privileged-host qualification. A subsequent real owner OIDC callback failed before claim because valid provider extensions were rejected. Hostile writer exclusion, completed enrollment, message/ACK, FILE/G13, production durability, and ship eligibility remain unproven. |
npm 0.1.29 OIDC callback interoperability repair candidate |
Real public 0.1.28 owner callback incident; shared decoded-pair parser; separate strict success/error projections; duplicate known/unknown, mixed, orphan, missing, extension, wrong-state/cookie, provider-error, replay, audience-drift, expiry, race, metadata-nondisclosure, and no-token-exchange regressions; owner, enrollment, and recovery transaction lifecycle coverage |
Focused callback suite 92 passed; source and both clean recursively packed npm generations each 1443 passed, 16 expected platform/dedicated-PostgreSQL skips; release verifier, agentnet verify, package checks, Codex/Claude/constitution reviews, and byte-identical wheel/sdist build PASS. The package lane excludes installed-live-inference, subprocess-lifecycle, and bake-off-evidence files; two historical installed-harness pin failures remain non-green and were not rerun or waived. |
H-shaped local package evidence only. Unique unrecognized OAuth extensions are ignored, not trusted; provider errors terminally consume only exact state/browser-bound pending transactions without exchange. Existing PKCE, nonce, issuer/audience/signature, expiry, replay, and owner binding remain. Failed callback URL is never retried. No completed live passkey/enrollment, message/ACK, FILE/G13, production, or gate-promotion evidence is claimed. |
Published npm 0.1.30 installed-verifier custody repair |
Sanitized Hub probe of exact public 0.1.29; bounded disposable package-copy execution; inherited pytest controls cleared; all caller pytest arguments rejected; recursive packed launcher verification with complete installed-tree content digest plus named-residue assertions; deterministic wheel/sdist builds |
Focused verifier lane 11 passed; source and two recursively packed generations each 1449 passed, 16 expected platform/dedicated-PostgreSQL skips; complete tree-digest and named-residue assertions pass; final Codex closure and Claude Opus 5 constitution/security reviews PASS with no required fixes |
H-shaped public-package evidence only. Fix is limited to installed-verifier custody. No completed OIDC/passkey, fresh-laptop enrollment, native message/ACK, production, or gate promotion is claimed. |
Published npm 0.1.31 first-message onboarding/recovery release |
Exact-approved-owner fixed remote activation; wrong-account/malformed/ambiguous/rate-limit negatives; purpose-separated OIDC/bootstrap Approval possession; automatic broker delivery and safe output; supported setup migration/journal rollback/response-loss recovery; status-scoped guided-join polling through fresh challenge expiry; Core-authenticated argument-bound terminal replacement with same-key reuse; enabled-unit proof; package-only persistent-lock reset; operator skill/docs/evals | Latest affected lane 344 passed; unfiltered local run 1625 passed, 16 expected platform/dedicated-PostgreSQL skips, with two installed-harness pin failures and pre-refresh manifest drift non-green/unwaived; packed focused recovery/conformance lane 72 passed, one Pi skill, zero loader diagnostics, no residue; official source and two recursive packed generations each 1549 passed, 16 expected skips with complete package-tree digest/no-residue checks green; two deterministic builds produced byte-identical wheel/sdist archives. Narrow Claude Opus 5 closure reports BLOCKERS: none, live-test decision PROCEED, and PASS for skill architecture, code security, and Constitution. First exact untagged Hub package installed byte-identically into an inert root-owned prefix, then package verifier failed closed before setup on stale internal release bindings. |
H-shaped local/package-portability evidence plus one fail-closed inert Hub installation only. Replacement internally bound package verification, live Google/WebAuthn ceremony, fresh-laptop enrollment, native signed message, recipient recipient_committed, COMPLETED_C0_ROUND_TRIP, five-power revocation, production, and gate promotion remain unproven. |
Published npm 0.1.32 coordinated first-C0 blocker repair |
Signed public-path Approval broker readiness with explicit verified host system trust, hostile TLS-env denial, wrong-host/untrusted-chain negatives, and sanitized TLS failure; authoritative setup reconciliation; Core migration 5 OIDC-begin replay and finite current-credential renewal; isolated package-owned C0 responder; current-package setup-attempt custody; recoverable terminal cleanup; five-unit systemd/reset lifecycle; timer-aware inactive-unit runtime proof; Node.js lifecycle compatibility policy | Affected lane 599 passed, 7 expected dedicated-PostgreSQL skips; source lane excluding installed-harness and release-manifest gates 1639 passed, 16 expected skips; final unfiltered run 1672 passed, 16 expected skips, 2 installed-harness G01 pin failures, with the two tests aggregating current version mismatches across all four installed harnesses and remaining non-green/unwaived; source plus two recursive packed generations each 1595 passed, 16 expected skips with complete package-tree digest/no-residue checks; release verifier and deterministic builds PASS; final TLS security and skill-architecture reviews converge, Constitution review passes, and Node-lifecycle skill audit converges. Exact three-OS/release baseline remains Node.js 24.18.0 LTS plus npm 12.0.1; the exact Node.js 22.19.0 minimum-floor lane uses compatible npm 10.9.3, while the Node.js 24.18.0/26.5.0 lanes use npm 12.0.1. The deployed Hub compatibility target is separately verified as Node.js 22.23.2 with npm 11.18.0; EOL Node.js 23/25 remain unsupported. Exact public-package Hub apply later failed safely at setup_marker_conflict before managed reconciliation or runtime/database/identity/authority mutation because the live 0.1.31 marker records a two-unit profile not admitted by 0.1.32. |
BLOCKED; H-shaped public-package evidence plus bounded negative live-Hub migration evidence. No successful deployment, live ceremony, dedicated local PostgreSQL mutation, production readiness, ship eligibility, requirement promotion, or gate promotion. |
Published npm 0.1.35 identity-preserving setup/credential recovery |
Exact digest-bound 0.1.33 five-unit predecessor; atomic journal succession; Approval SIGTERM/status 143 contract; exact failed-latch reconciliation; marker-first PostgreSQL boundary; pre-C0 same-key expired-credential reauthorization |
Focused release lane 625 passed, 7 expected dedicated-PostgreSQL skips; source and recursive packed lanes 1621 passed, 16 expected skips; byte-identical artifacts; cross-platform run 30693899336, clean setup run 30693899319, and real upgrade run 30693899330 passed. Exact public Hub apply later committed marker/schema migration and exposed the impossible actor.key_id setup check; five units remained inactive, authority false, no enrollment/C0. |
BLOCKED; H/L package and bounded non-green live-Hub evidence. No production, ship, requirement, or gate promotion. |
Corrective npm 0.1.36 strict identity-profile and setup-convergence candidate |
Duplicate-key-rejecting JSON plus strict canonical VerifiedActor parsing; exact domain/harness/credential label checks; unchanged private profile/key custody and P-256 readability; removal of impossible nonexistent actor.key_id comparison; exact released 0.1.33 five-unit marker migration only; Approval/Core/C0 systemd Type=exec live-runtime convergence |
Test-first identity regression failed on canonical writer output under 0.1.35, then passed after the minimal correction. Exact upgrade E2E run 30707067892 passed. Clean setup run 30707067865 passed first apply then exposed the Type=simple pre-exec race on same-digest retry; official systemd semantics support the minimal Type=exec correction, and the temporary diagnostic classifier was removed. Focused release lane 631 passed, 7 expected dedicated-PostgreSQL skips; source and two recursive packed generations each 1627 passed, 16 expected skips; direct agentnet verify, release verifier, complete package-tree equality, and deterministic double-build checks pass. Same-commit main-push workflows passed, but immutable-tag upgrade run 30750626969 failed in the released 0.1.31 seed's post-start sampling of systemd's transient pre-exec MainPID; cleanup passed and npm staging did not run. |
BLOCKED; immutable non-public tag and bounded negative CI evidence. No waiver, tag rewrite, authority grant, production, ship, requirement, or gate promotion. |
Published npm 0.1.37 released-seed convergence repair |
One real released 0.1.31 --apply --start; strict exit-1 plus exact service_runtime/message/schema and actual-boolean false safety-field classification; bounded non-mutating invocation of the exact released package's own Approval/Core runtime and loopback/public health validators only on the classified failure branch; separately captured stderr included in synthetic-secret scanning; exact 0.1.33-to-0.1.37 five-unit marker edge only |
Focused lane 637 passed, 7 expected dedicated-PostgreSQL skips; source and two recursive packed generations each 1633 passed, 16 expected skips; conformance 40 passed; direct agentnet verify, release verifier, complete package-tree equality, no-residue checks, deterministic byte-identical retained archives, same-commit GitHub, immutable tag, and trusted npm stage pass. Malformed/duplicate/non-finite evidence, numeric false-lookalikes, wrong exit/blocker/message/safety fields, stable wrong runtime, unexpected blocker, timeout, health mismatch, and module-provenance mismatch fail closed. |
BLOCKED; H/package evidence only. 0.1.34, 0.1.35, 0.1.36, and direct legacy marker sources remain rejected. No setup retry/restart, runtime-proof weakening, deployment, reset, database, enrollment, authority, C0, federation, production, ship, requirement, or gate promotion. |
Published npm 0.1.38 public-health convergence repair |
Exact live failure after loopback health succeeded but public route required about 49–61 seconds; public Approval/Core health and public Core readiness reuse the existing finite 90-attempt startup bound; ordinary probes retain 30 attempts; exact 0.1.37 five-unit marker edge only |
Pre-fix regression failed because all three public calls passed the default bound; corrected setup/recovery lane 223 passed; focused release lane 644 passed, 7 expected dedicated-PostgreSQL skips; source lane 1613 passed, 16 expected skips; source plus two recursive packed generations each 1640 passed, 16 expected skips; conformance 40 passed; release verifier, package checks, deterministic byte-identical archives, same-commit CI, immutable tag, trusted npm stage, registry signature/provenance, and public-byte checks pass. The remote Hub peer reported from bounded read-only fresh-install preflight that the default Python-urllib/* User-Agent received HTTP 403 on all three public routes; no 0.1.38 Hub installation occurred. That report is corroboration only, not retained reproducible proof. |
BLOCKED; H/package evidence plus bounded read-only negative Hub evidence. Exact payload, TLS, redirect, authority, and auxiliary-unit ordering checks are unchanged. No deployment, reset, database, enrollment, authority, C0, federation, production, ship, requirement, or gate promotion. |
Corrective npm 0.1.39 request-identity plus packaged local-communication candidate |
Explicit GET urllib.request.Request; User-Agent: AgentNet/0.1.39; JSON Accept; unchanged TLS/proxy/redirect/timeout/identity boundaries; local-policy-only deterministic lab revision, recipient-resolution, and custody-ACK composition; second recursive npm generation runs a real Core plus separate fresh-proof client processes over loopback from installed bytes; fresh clean-state setup only with no migration edge |
Health regression passed (2 passed); setup/recovery (224 passed) and prior focused release (645 passed, 7 expected PostgreSQL skips) remain green. New focused synthetic-lane/HTTP/obligation regressions report 7 passed. A fresh manually packed npm tarball installed into an unrelated prefix passed accepted_local, exact proof-derived request/reply attribution, offline recipient recovery after Core restart, stable request event/obligation and ACK receipt idempotency, recipient_committed, typed obligation completed, requester response custody after another restart, fresh authentication refusal after an explicitly non-approved lab credential fixture, closed listener, and removed state. Final metadata-bound recursive verification passed in both clean npm generations with 1642 passed, 16 expected skips each; generation 2 additionally passed the installed-byte multiprocess lifecycle, package-tree equality, empty-workspace, listener-release, and no-residue checks. Peer-reported 403→502 comparison remains corroboration only. |
BLOCKED; H/L-shaped synthetic local evidence only. The production policy engine still rejects deterministic lab harnesses. This is not bounded COMPLETED_C0_ROUND_TRIP, approved revocation or five-power cleanup, real enrollment, ordinary server-agent COM-002/COM-003, PostgreSQL durability, Hub installation, production, ship, requirement, or gate promotion. Exact same-commit cross-platform, clean-setup, public-0.1.38-marker rejection, packaged communication, tag, stage, public-byte, and fresh-setup evidence remain pending. |
Unpublished npm 0.1.42 narrow real C0 candidate |
Explicit owner-approved reset of only disposable AgentNet state; fresh ordinary server setup; real workforce Google OIDC and owner-controlled WebAuthn UV for exact server and laptop harness enrollment; strict remote-browser challenge evidence; fixed one-hour BootstrapGrantPlan; package-owned systemd responder credential custody; native request/reply/ACK journey; authoritative PostgreSQL postcondition query |
Narrow live path PASS: both harnesses ended identity-only before the fixed plan; plan commit returned prepared_unusable; c0-pilot progressed waiting_owner → waiting_fresh → COMPLETED_C0_ROUND_TRIP; retained parent-scoped postconditions are exactly one committed plan, its one revoked guard, its one communication_revoked attempt, 7 rows/7 distinct fact kinds for that attempt, 5/5 communication entitlements for that plan revoked, and 5 exact-revoke items for that plan. Broad run remains non-green: 1747 passed, 16 skipped, 3 failed; agentnet verify reported 1665 passed, 16 skipped, 1 failed; release verifier reported 15 manifest/source/package drift findings. |
Narrow L/E-shaped real IdP/authenticator plus disposable single-node service evidence is retained at evidence/local/2026-08-04-v0.1.42-c0-live/manifest.json; its sanitized parent-scoped postcondition query/result is hash-bound as postconditions.json SHA-256 518f030c0503f93bcc6e119581c1c4d88c16f6ec06b69addc2768a5c7be2681a. Both artifacts remain historical evidence for deployed source d8884b6c03a0dd38baab03386982aae8ad11dd58; they do not prove the post-run nonblocking credential-open correction at 52b6941. The run does not pass a gate, certify a release, prove independent approval hosting, production key custody, PostgreSQL HA/PITR, real four-harness semantics, cross-platform packaging, or owner decisions. Candidate is unpublished and release posture remains BLOCKED. |
Post-live 0.1.42 credential-open correction |
O_NONBLOCK before descriptor metadata validation; dedicated regression; retained parent-scoped C0 SQL/result evidence |
Regression failed before the correction; responder file passed 23 tests; independent corrective review ended NO_BLOCKING_FINDINGS |
H-shaped source-only evidence at evidence/local/2026-08-04-v0.1.42-post-live-corrective/manifest.json. Revision 52b6941 was not deployed for the historical live run. No package, live rerun, release, requirement, or gate promotion is claimed. |
Candidate npm 0.1.43 corrected first-C0 release path |
Strict remote-browser bootstrap evidence; byte-preserving P-256 responder credential handling; package-owned systemd credential custody; O_NONBLOCK before regular-file validation; retained historical real OIDC/WebAuthn two-harness C0 and exact-revocation evidence |
Focused affected lane 757 passed, 7 expected dedicated-PostgreSQL skips; broad source lane and both fresh recursive npm generations each 1640 passed, 16 expected skips; the retained-content generation completed the real loopback Core/separate-client local communication journey and left an empty workspace. The candidate manifest records final release-manifest/direct-verifier and byte-identical archive outcomes. Same-commit CI/stage and corrected-source remote evidence remain external actions. Historical narrow deployment passed only at source d8884b6c03a0dd38baab03386982aae8ad11dd58. |
H/L-shaped candidate source, recursive-package, installed-byte, and retained-archive evidence at evidence/local/2026-08-04-v0.1.43/manifest.json. The historical live run predates the descriptor-open correction. No requirement, release, production, or gate promotion is claimed. |
Candidate npm 0.1.44 private administration and Manager communication path |
Loopback-only owner dashboard with one-time browser handoff, per-request credential/authority revalidation, single-use exact mutation tokens, proof-bound sponsored enrollment, passive content-free updates, combined schema-v6 SQLite/PostgreSQL state preserving the published v5→v6 path; one-approval same-principal communication scopes; parent-owned short-lived Linux Manager binding, complete packaged Pi extension staging, signed canonical HTTP dispatch, PID-namespace descendant cleanup, and real two-principal signed Manager journey | Affected release lane 329 passed, 7 expected dedicated-PostgreSQL skips; broad source lane 1761 passed, 16 expected platform/dedicated-PostgreSQL skips; source and both clean recursive npm generations each completed 1788 passed, 16 expected skips, with generation 2 also completing the installed-byte multiprocess communication gate and leaving no workspace or named verification residue; real installed Pi RPC launch returned canonical get_state and exit 0; browser smoke exercised authenticated Home/People navigation and the existing/new-person enrollment toggle; Lighthouse accessibility 100 with zero accessibility failures |
H/L-shaped local source, recursive-package, installed-byte, and retained-archive evidence only. No owner decision, production IdP/WebAuthn ceremony, independently administered approval host, privileged exact-host process-boundary evidence, multi-host PostgreSQL/HA proof, cross-platform Manager support, staged remote deployment, or gate promotion is inferred. Same-commit external workflows remain required before candidate handoff. |
Candidate npm 0.1.45 exact-endpoint collaboration and lifecycle cutover |
Sole schema-v7 SQLite/PostgreSQL catalog; verified actor-, harness-, credential-, policy-, and revocation-bound endpoint lifecycle fenced to the exact framed platform/account/pid/start-time/executable process instance with an audited endpoint.lifecycle.process_reconnected transition and owner-private capability-root recovery; one exact authorized recipient plus current collaboration scope per send; no fallback/default/static scopes; all five harness adapters; immutable conversations, rooms, tasks, obligations, artifact transfer, and safe-download tools; semantic background workers admitted only for typed task assignments; opaque public invitation continuation; resumable user-level update; hermetically covered schema v6->v7 authority migration whose packaged upgrade lane is NOT green |
Focused acceptance lane 454 passed, 5 expected dedicated-PostgreSQL skips; package source corpus 2102 passed, 21 expected platform/dedicated-PostgreSQL skips; source plus two clean recursive npm generations each 2129 passed, 21 expected skips; two independent SOURCE_DATE_EPOCH=1580601600 builds byte-identical; release verifier and manifest conformance PASS; isolated installed-package routing reported target harness equals processing harness, zero sibling reactions, endpoint-owned offline custody, no offline processing, zero surviving endpoint processes/capability roots, and no workspace fallback; same-commit GitHub cross-platform package conformance (Ubuntu, macOS, Windows, Node 22/24/26) and the ordinary-server clean-install lane with a live maintained ClamAV daemon are terminal-green; the 0.1.44 to 0.1.45 packaged upgrade/rollback lane remains terminal-red and is preserved as non-green |
H/L-shaped local source, browser, installed-byte routing, lifecycle, and same-commit clean-install evidence only. In-place upgrade from 0.1.44 is NOT proven and is not a supported path for this release; operators must perform a fresh clean install and re-enrollment. Two upgrade defects found while exercising the lane were corrected at source (journal validation rejected every upgrade; rollback safety demanded empty v7 tables, blocking any deployment holding committed v6 communication authority). No dedicated PostgreSQL rerun, signed installer, privileged exact-host process boundary, semantic real-harness proof, external staging/deployment, owner decision, HA/PITR, or gate promotion is inferred. |
Candidate npm 0.1.46 timer correction and audited post-C0 credential recovery |
Retains the timer and exact 0.1.45→0.1.46 upgrade corrections already recorded for this candidate. Expired same-key recovery now preserves immutable C0 terminal provenance and an owner-private canonical credential-supersession journal. Every replacement entry binds the exact prior and new credential epoch, actor/harness/key, managed-file digests, owner-approved transaction and receipt, prior journal digest, and authoritative PostgreSQL audit-record hash. Setup and Core validate the complete journal and audit chain before service readiness; exact replay reconciles response loss, while missing, stale, noncanonical, skipped-epoch, unaudited, key/actor drift, and conflicting replay fail closed. Recovery grants no authority and restarts no service. |
Expanded focused release lane 543 passed, 5 expected dedicated-PostgreSQL skips; broad releasable-source lane 2151 passed, 21 expected platform/dedicated-PostgreSQL skips; fuller local source run 2259 passed, 21 expected skips, 3 deselected where the deselections are the two separately non-green installed-harness pin checks and the expected pre-assembly release-manifest binding check. Source plus two recursive packed generations each 2178 passed, 21 expected skips after reassembly. The earlier disposable Ubuntu timer/upgrade proof remains bound only to its recorded pre-supersession source tree and was not rerun as post-C0 recovery evidence. |
H/L-shaped evidence only. No gate or requirement is promoted. Publication, a fresh disposable-host post-C0 recovery run, mutation-authorized real-PostgreSQL recovery evidence, signed owner policy, privileged hostile-host trials, and other external tiers remain pending. |
Candidate npm 0.1.47 exact stranded-marker correction |
Adds only the exact forward-only 0.1.46→0.1.47 five-unit marker edge; preserves same-version request-digest rejection and schema-v7 identity/credential/endpoint/communication state without database migration |
Focused lane: 544 passed, 5 skipped; broad releasable-source lane: 2152 passed, 21 skipped; recursive packed-package and installed-host upgrade evidence pending |
H-only correction evidence; no gate promotion. Affected IDs: ID-009, SEC-007, OPS-003. |
Candidate npm 0.1.48 canonical post-C0 credential correction |
Completed-C0 terminal credentials now resolve through the exact domain/principal-bound harness plus credential epoch; unknown or mismatched identity state remains fail-closed. Adds only the exact forward-only 0.1.47→0.1.48 five-unit marker edge and no database migration. |
Focused lane: 547 passed, 5 skipped; broad releasable-source lane: 2155 passed, 21 skipped; recursive packed-package and installed-host upgrade evidence pending. |
H-only correction evidence; no gate promotion. Affected IDs: ID-006, ID-009, SEC-007, OPS-003. |
Candidate npm 0.1.49 completed-C0 communication recovery |
Permanent communication activation resolves the exact completed C0 pair; only the authenticated ordinary server harness may advance to its current active credential, while the C0 peer remains pinned to its enrolled credential absent separately verified succession. Terminal pre-commit retries converge without replacing committed authority. Signed message send, inbox, and acknowledgement requests bind the exact collaboration scope. Adds only the forward-only 0.1.48→0.1.49 five-unit marker edge and no database migration. |
Focused lane: 645 passed, 5 skipped; broad releasable-source lane: 2166 passed, 21 skipped; recursive packed-package and installed-host upgrade evidence pending. |
H-only correction evidence; no gate promotion. Affected IDs: ID-001, ID-002, ID-004, ID-006, AUTH-001, AUTH-002, AUTH-003, AUTH-004, AUTH-007, AUTH-009, COM-001, COM-002, COM-003, COM-006, COM-009, COM-011, AVL-003, AVL-005, AVL-006, SEC-003, SEC-005. |
Candidate npm 0.1.50 setup-usability, direct-upgrade, and communication-scope approval path |
One guided server command over the strict request/plan/apply protocol; one server-origin-only guided laptop command with authenticated discovery defaults; content-free named phases; ten-minute server and five-minute laptop bounds; resumable blocker output; exact direct allowlist from v0.1.45–v0.1.49 schema-v7 five-unit markers; installed separate-process local communication/obligation roundtrip added to packed verification; explicit one-hour Approval request ceiling limited to authorization.communication_scope.approve, with all other approvals retaining the five-minute ceiling and short-lived WebAuthn challenges |
Focused release lane: 681 passed, 5 skipped; broad releasable-source lane: 2180 passed, 21 skipped; source and two recursive packed generations: 2207 passed, 21 skipped each; two byte-identical release builds; release manifest verifier passed; installed tarball journey passed from an unrelated prefix; installed-host, fresh-machine, and same-commit CI evidence pending |
H/L-shaped local candidate evidence only. No production, owner-policy, external, privileged-host, or gate promotion. Affected IDs: ID-006, AUTH-004, AUTH-007, COM-001, COM-002, COM-003, COM-006, COM-009, AVL-003, AVL-005, AVL-006, UX-001, UX-002, SEC-003, SEC-005, OPS-003, OPS-006. |
Candidate npm 0.1.51 same-binding expired laptop credential reauthorization, measured Pi/OMP Manager activation, and guided identity-only correction |
Dedicated package-owned recovery for an expired ordinary laptop credential preserves the exact domain/principal/harness binding, OS- or hardware-bound public key, authority, scopes, memberships, capabilities, and supersession history. Fresh independent WebAuthn user verification is required; active, revoked, mismatched, non-laptop, stale, replayed, expired-transaction, and conflicting bindings fail before key use or mutation. One same-key successor epoch commits idempotently; no enrollment, generic renewal, key replacement, authority grant, or service restart occurs. Guided enrollment terminates identity-only and never implicitly begins or completes a bootstrap plan or C0 pilot. The existing single-child Manager launcher accepts Pi or OMP, stages the exact packaged Pi-compatible extension, rejects caller-selected extension/tool flags, retains exact-process binding and a private PID namespace/procfs sandbox, and exposes only canonical AgentNet tools. | Focused lane: 762 passed, 5 skipped; broad releasable-source lane: 2228 passed, 21 skipped; source plus two recursive packed generations: 2229 passed, 21 skipped each; two byte-identical release builds; release verifier, packaged exact-endpoint routing, packaged 0.1.45 user journey, separate-process communication/obligation roundtrip, and measured Linux OMP launcher smoke passed; fresh installed-host, live owner WebAuthn/Core recovery, live OMP AgentNet tool use, same-commit CI, and production-topology evidence pending. |
H/L-shaped local recovery, Manager activation, authority-boundary, and packaging evidence only; no gate promotion. Affected IDs: ARC-001, ARC-002, ARC-004, ID-001, ID-002, ID-003, ID-004, ID-005, ID-006, ID-007, ID-008, ID-009, AUTH-001, AUTH-002, AUTH-003, AUTH-004, AUTH-005, AUTH-006, AUTH-007, AUTH-008, AUTH-009, AUTH-010, COM-001, COM-002, COM-003, UX-001, UX-002, SEC-003, SEC-005, SEC-007, OPS-002, OPS-003, OPS-006, OPS-007. |
| OIDC validated-address transport repair | UV_CACHE_DIR=/tmp/uv-cache uv run pytest -q tests/identity/test_oidc_enrollment.py tests/operations/test_fail_closed_config.py tests/production/test_deployment_config.py |
53 passed, 0 failed on 2026-07-15 | H only: includes the real _PinnedHTTPSConnection socket path under a validation-to-connect DNS-answer change, exact TCP address/SNI/Host assertions, proxy/tunnel and redirect denial, response bounds, unsafe address-class rejection, invalid resolver type handling, private IPv4/IPv6 pins, configuration, and deployment wiring. No real IdP/TLS service or independent approval boundary is claimed. |
| Independent WebAuthn-UV approval component | UV_CACHE_DIR=/tmp/uv-cache uv run pytest -q tests/approval; approval-consumer lane; non-gate full regression below |
12 focused passed; 144 approval/consumer passed; included in 1049-pass broad lane on 2026-07-15 | H only: strict owner-only config/key custody, exact SQLite catalog/tamper rejection, UV-required maintained-library call contract, exact display/digest, bounded duplicate-rejecting HTTP, one-receipt response-loss retry, committed denial/expiry audits, rejection, credential revocation, loopback serving, and non-authorizing provisioning. WebAuthn verification is seam-controlled in hermetic tests; no real authenticator, independent host/device/operator, TLS proxy, rotation/recovery drill, or owner decision is claimed. |
Prior 0.1.8 candidate, unfiltered local run |
UV_CACHE_DIR=/tmp/uv-cache uv run --extra test pytest -q |
1087 passed, 2 failed, 7 expected PostgreSQL skips on 2026-07-16 |
Both failures were preserved environmental G01 gates. This was not a passing unfiltered release run and is not current 0.1.9 evidence. |
Prior 0.1.9 candidate, unfiltered local run |
UV_CACHE_DIR=/tmp/uv-cache uv run --extra test pytest -q |
1106 passed, 2 failed, 7 expected PostgreSQL skips on 2026-07-16 |
Both failures were preserved environmental G01 gates. This was not a passing unfiltered release run and is not current 0.1.10 evidence. |
Prior 0.1.10 candidate, unfiltered local run |
UV_CACHE_DIR=/tmp/uv-cache uv run --extra test pytest -q |
1107 passed, 2 failed, 7 expected PostgreSQL skips on 2026-07-16 |
Both failures were preserved environmental G01 gates. Independent public recursive verification later failed as recorded above; this is not current 0.1.11 evidence. |
Prior 0.1.11 candidate, unfiltered local run |
UV_CACHE_DIR=/tmp/uv-cache uv run --extra test pytest -q |
1106 passed, 2 failed, 7 expected PostgreSQL skips on 2026-07-17, plus one expected release-manifest drift failure before release metadata refresh |
Both substantive failures are preserved G01 gates: installed Claude, Codex, Pi, and Antigravity versions differ from immutable release pins, and the dependent deterministic lifecycle fails closed. Release-manifest drift was expected during the pre-manifest repair stage and is not presented as a passing unfiltered run. |
Prior unreleased 0.1.11 branch, code-regression corpus |
UV_CACHE_DIR=/tmp/uv-cache uv run pytest -q --ignore=tests/adapters/test_installed_live_inference.py --ignore=tests/conformance/test_release_manifest.py |
1079 passed, 7 expected PostgreSQL skips on 2026-07-17 |
Excludes only the explicit installed-version and current release-manifest gates. It is local regression evidence, not current real-PostgreSQL, real-harness, live Google/passkey, independent-deployment, first-message, or production evidence. |
| PostgreSQL/storage corpus | AGENTNET_TEST_POSTGRES_URL='postgresql:///agentnet_test_final?host=/tmp/agentnet-pgsocket-20260713-final&port=55432' AGENTNET_TEST_POSTGRES_ALLOW_MUTATION=1 PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=src .venv/bin/pytest -q -p no:cacheprovider tests/production/test_postgres_runtime.py |
44 passed, 0 skipped | Seven cases use a real local UTF-8 PostgreSQL 18.4 database for pre-release rejection, clean schema-v1 creation/checksum/DDL tamper fencing, mailbox visibility, reconnect fencing, quota admission, breaker CAS, and conflict/adjudication serialization; 37 are hermetic connection/SQLite contracts. No multi-node HA/failover/PITR or PostgreSQL restore-execution claim. |
| Four installed deterministic harnesses | PYTHONDONTWRITEBYTECODE=1 UV_CACHE_DIR=/tmp/uv-cache uv run pytest -q -p no:cacheprovider tests/adapters/test_installed_live_inference.py |
8 passed in 1.94s | Exact installed version probes and deterministic private lifecycles only; no inference or semantic conformance. |
| Native A2A local regression | .venv/bin/pytest -q tests/a2a |
Included in the broad run; all checked-in A2A tests passed | H/L SDK, mapping, security, callback, persistence, and gateway evidence only. |
| Official A2A TCK | evidence/gates/G04/2026-07-13-alpha2-http-json/manifest.json |
235 selected: 46 passed, 12 failed, 177 skipped, 0 errors | Official 1.0.0.alpha2 HTTP+JSON gate is non-green. All 12 failures and all 177 skips are exhaustively classified without waiver; original reports are retained and hash-bound in the gate directory. |
The checked-in A2A classification is
evidence/gates/G04/2026-07-13-alpha2-http-json/REVIEW.md. It explains the
security/fixture conflicts behind the 12 remaining failures and categorizes all
177 disabled-binding/feature and fixture skips without waiving any outcome.
That review does not turn G04 green.
| Gate | Required tiers | Actual executable evidence | Current status | Explicit absent evidence |
|---|---|---|---|---|
| G01 — foreground isolation | H,L,E | Manifest/no-foreground contracts: tests/adapters/test_all_harnesses.py; private installed deterministic lifecycle: tests/adapters/test_installed_live_inference.py; background dispatch: tests/adapters/test_offline_queue_integration.py |
BLOCKED_EXTERNAL |
E: semantic traffic with exact focus/input/context/turn instrumentation for Claude, Codex, Pi, and Antigravity is absent. |
| G02 — worker recovery | H,L,E | Queue crash recovery: tests/supervisor/test_background_queue.py; native process kill/restart/timeout: tests/adapters/test_subprocess_lifecycle.py; result-upload retry: tests/adapters/test_supervisor_core_composition.py |
BLOCKED_EXTERNAL |
E: real semantic worker kill/compaction/restart at every state edge for all four harnesses is absent. |
| G03 — harness isolation and model egress | H,P,E | Clean-worker admission/environment/broker negatives: tests/adapters/test_clean_worker_boundaries.py; subprocess sandbox contracts: tests/adapters/test_subprocess_lifecycle.py; broker grant/budget plus persistent per-capability one-use request-nonce replay/race rejection: tests/supervisor/test_clean_workers_and_model_broker.py; requested live gate fails closed in tests/adapters/test_installed_live_inference.py |
BLOCKED_EXTERNAL |
P/E: privileged escape/canary trials and signed clean-worker inference evidence are absent. Deterministic runs do not satisfy them. |
| G04 — native A2A | H,L,E | Mapping/security/version/grants: tests/a2a/test_mapping.py; tests/a2a/test_gateway_profile.py; tests/a2a/test_security_requirements.py; signed/persistent/callback/recovery: tests/a2a/test_signed_native_gateway.py; tests/a2a/test_persistent_service_mount.py; tests/a2a/test_native_client_and_callbacks.py; durable official evidence: evidence/gates/G04/2026-07-13-alpha2-http-json/manifest.json |
FAILED |
Official alpha2 recorded 46 passed, 12 failed, and 177 exhaustively classified but non-passing skips. E: cross-SDK, public peer, certificate, real callback receiver, cancellation/resubscription, and enabled streaming/push/artifact matrix is absent. |
| G05 — MCP/local API parity and direct IPC | H,L,P,E | Canonical dispatcher across direct/MCP/Pi IPC; Linux SO_PEERCRED; macOS LOCAL_PEERPID/getpeereid; Windows protected named pipes with server-derived client PID; exact account/PID/start/executable/parent/module binding; generation/TTL/epoch/revocation/replay checks; sealed memfd/read-only pipe/one-time Windows capability delivery; Unix bootstrap socket descriptor pinning with retryable-renewal preservation and terminal cleanup; Job cleanup: src/agentnet/bindings/mcp.py; src/agentnet/bindings/ipc.py; src/agentnet/bindings/windows_mcp_bootstrap.py; src/agentnet/supervisor/runtime.py; src/agentnet/supervisor/windows_binding_delivery.py; tests/adapters/test_subprocess_lifecycle.py; tests/platform/test_host_support.py; tests/bindings/test_local_binding_composition.py; tests/security/test_ipc_capability.py |
BLOCKED_EXTERNAL |
Ubuntu VM evidence covers immediate inode reuse, renewal recovery, post-publication startup cleanup, and terminal exhaustion, while E and stronger P remain absent: exact installed-harness semantic interoperability, privileged hostile same-account/PID-reuse/path-substitution trials, macOS O_EVTONLY host proof, and a stronger off-Linux loaded-executable measurement. No bearer or caller-supplied identity is accepted locally. |
| G06 — identity/enrollment | H,L,E,O | Enrollment/PoP/replay/races: tests/identity/test_enrollment.py; OIDC/PKCE/JWKS/origin/approval attacks and direct validated-address TLS transport: tests/identity/test_oidc_enrollment.py; standalone WebAuthn-UV config/store/ceremony/HTTP/CLI, stable receipt retry, expiry, denial audit, and credential revocation: tests/approval/test_webauthn_service.py; tests/approval/test_approval_http.py; tests/approval/test_approval_cli.py; fail-closed config/deployment: tests/operations/test_fail_closed_config.py; tests/production/test_deployment_config.py; recovery/rotation/revocation: tests/identity/test_recovery.py; tests/identity/test_credential_rotation.py; tests/identity/test_revocation.py; HTTP: tests/integration/test_enrollment_http.py. |
BLOCKED_OWNER |
The ordinary self-hosted PD-001/PD-002 defaults were recorded from explicit owner instruction on 2026-07-19, but that record is not independent signed O-tier evidence. L/E also remains absent: live workforce IdP/certificate integration, real passkey/authenticator ceremony, target-device key custody, colocated distinct-OS-identity process/receipt/trust-anchor attack trials, and signer/authenticator recovery drills. Separately administered approval-host evidence is required only for the optional high-assurance/independent_boundary_proven=true tier. PD-003/005/009 and production certification remain open. |
| G07 — local IPC/signing oracle | H,P,E | Purpose/target-bound signatures: tests/security/test_signatures_and_replay.py; composed current-epoch actor, real child process, durable nonce/process/session/root fencing; real-host peer/DACL/reparse/replay/capability-theft negatives: tests/bindings/test_local_binding_composition.py; tests/security/test_ipc_capability.py; tests/platform/test_host_support.py; registered workload proof: tests/identity/test_workload_identity.py |
BLOCKED_EXTERNAL |
Current CI supplies bounded ordinary-runner P-shaped evidence, not the required privileged hostile tier. Same-account PID-reuse/path/socket substitution, flood trials, and exact installed Pi semantic direct-binding evidence remain absent. |
| G08 — authorization and intent | H,L,O | Human-only policy/coherent revision: tests/authorization/test_policy.py; exact grants/races: tests/authorization/test_grants.py; zero-authority relationship proposal, verifier-derived exact owner consent, replay/drift/renew/revoke races, signed human/guest exception, exact completed local activation intent, authenticated renewal HTTP, server-derived bounded deadlines, typed arrival-order-independent multi-administrator task conflicts, opposite-adjudication and overlapping-release races, terminal propagation/revision fencing, exact subordinate-owner partition, permanent task/task-linked-control generic-read redaction, and recipient-owned TaskGrant authorize→local-custody→payload-release with audit-before-disclosure, current-state retries, no second grant use, result-release linkage, wrong recipient/dimension/epoch/conflict/expiry/tamper/revocation/missing-intent denials: tests/organization/test_relationships.py; tests/property/test_relationship_lifecycle.py; tests/organization/test_assignment.py; tests/organization/test_task_custody.py; tests/adapters/test_supervisor_core_composition.py; tests/messaging/test_conversation_semantics.py; tests/integration/test_product_http_api.py; tests/production/test_postgres_runtime.py; fail-closed runtime policy: tests/operations/test_runtime_policy_enforcement.py |
BLOCKED_OWNER |
Local authorization, ORG-005 mechanics, and exact payload/semantic release are implemented. Generic reads remain redacted and tool/effect authority remains false. The relationship activation intent remains local provenance, not an independent witness. O is absent: signed principal/attenuation policy; eligible relationship proposers/proposal entitlements; exception/override/appeal authorities and thresholds; and break-glass policy. |
| G09 — durability | H,L,E,O | Mailbox duplicate/offline/fact ownership: tests/delivery/test_mailbox.py; artifact release/quota recovery: tests/artifacts/test_staged_artifact.py; ordinary-agent relay crash/reconnect: tests/relay/test_server_agent_relay.py; seven real-PostgreSQL plus 37 hermetic storage cases: tests/production/test_postgres_runtime.py |
BLOCKED_EXTERNAL |
E/O synchronous HA topology, separate failure domains, standby failover, WAL archive/PITR/restore, replicated artifact backend, load/pressure, and approved RPO/RTO remain absent. |
| G10 — delivery, effects, expiry | H,L,E | Declared delivery graph properties: tests/property/test_delivery_state_machine_properties.py; actor-owned mailbox expiry/cancel/effect negatives: tests/delivery/test_mailbox.py; assignment custody derives and persists an exact whole-second effect/delivery deadline bounded by scope/relationship; payload release rechecks delivery/effect/retention boundaries and result upload requires committed release: tests/organization/test_task_custody.py; tests/adapters/test_supervisor_core_composition.py; effect reservation/terminal evidence/crash/reconciliation: tests/effects/test_effect_reservation.py |
PARTIAL |
E: real connector-specific effect reconciliation and long-running expiry/cancel/commit race evidence is absent. Payload release itself grants no effect authority. |
| G11 — revocation | H,L,E,O | Harness/sibling revocation: tests/identity/test_revocation.py; exact relationship subject exit/admin override, automatic expiry, credential/policy drift, lineage-fenced renew/revoke races, grant/task drift: tests/organization/test_relationships.py; tests/property/test_relationship_lifecycle.py; tests/organization/test_task_custody.py; relay and bilateral guest/home revoke: tests/relay/test_server_agent_relay.py; tests/federation/test_bilateral_guest.py |
BLOCKED_OWNER |
E/O: complete cross-resource matrix on real devices/partners, cross-domain signal SLO, continuity window, compromise adjudication, and PD-005/009 signatures are absent. |
| G12 — room authority | H,L,E,O | Membership/speaker/epoch/state/guest/transfer/tombstone/model gates: tests/rooms/test_room_authority.py; signed HTTP governance: tests/integration/test_product_http_api.py |
BLOCKED_OWNER |
E/O: maintained MLS lifecycle, two independently administered domains, formal model artifact, and signed PD-006/007 governance/history/retention policy are absent. |
| G13 — files and audit | H,L,E,O | Artifact quarantine/release/deletion crash recovery, exact legal hold, retention/event gates, scanner staleness/substitution, dedup non-disclosure, and guarded unlink: tests/artifacts/test_staged_artifact.py; audit chain/checkpoint: tests/audit/test_audit_chain.py; attachment/lifecycle HTTP and relay holding: tests/integration/test_product_http_api.py; tests/relay/test_server_agent_relay.py |
BLOCKED_OWNER |
E/O: maintained hostile-file scanner/corpus, replicated object host-loss restore, independent audit witness, and signed retention/deletion/legal policy are absent. |
| G14 — signed-peer abuse and semantic intent | H,L,E | Source/sink/grant bounds: tests/authorization/test_grants.py; task custody alternate-ingress checks plus exact action/resource/source/sink/classification drift denial during protected release: tests/organization/test_task_custody.py; tests/adapters/test_supervisor_core_composition.py; A2A/relay abuse containment: tests/a2a/test_signed_native_gateway.py; tests/relay/test_server_agent_relay.py; broker budgets: tests/supervisor/test_clean_workers_and_model_broker.py |
BLOCKED_EXTERNAL |
E: 1,000 adaptive hostile trials for every exact supported model/config, semantic-to-typed fuzzing, flood safety capacity, and exfiltration canaries are absent. Tool/network/budget/effect authority is not yet modeled by the release path. |
| G15 — supply chain | H,P,E,O | Threshold update verification plus atomic signed lifecycle contracts, durable anti-rollback, residual recovery, pinned executable health, owner-protected canonical state, immutable image digest, recursive package evidence, and Linux/macOS/Windows source-to-packed-launch CI: tests/security/test_update_verifier.py; tests/security/test_distribution_lifecycle.py; tests/platform/test_host_support.py; tests/production/test_deployment_config.py; tests/conformance/test_release_manifest.py |
BLOCKED_EXTERNAL |
Real-host package/local qualification does not satisfy E/O independent signing/root ceremony, published SBOM/provenance, or signed native installer/update/uninstall/rollback and recovery drills on macOS/Windows. |
| G16 — operations, failure, and adoption | L,E,O | Fail-closed component registry/config: tests/operations/test_fail_closed_config.py; deployment topology: tests/production/test_deployment_config.py; health/readiness/recovery: tests/production/test_postgres_runtime.py; signed actual SQLite backup/restore and forged-seal/path-race negatives: tests/operations/test_backup_restore.py; CLI flow: tests/integration/test_cli_product_journey.py; relay failure paths: tests/relay/test_server_agent_relay.py |
BLOCKED_OWNER |
E/O: locked authenticated PostgreSQL restore execution, off-host/KMS backup custody, full dependency outage matrix, kill-switch SLO under load, physical/admin topology, staffing/stop rules, and reviewed component adoption/replacement records are absent. |
| G17 — owner policy | O | Executable conservative floors: src/agentnet/operations/policy_defaults.py; floor/runtime tests: tests/operations/test_secure_policy_defaults.py; tests/operations/test_runtime_policy_enforcement.py; OIDC purpose coverage: tests/operations/test_fail_closed_config.py |
BLOCKED_OWNER |
O: no signed current PD-001 through PD-011 records exist. Defaults prevent unsafe enablement but are not owner consent. |
| G18 — discovery, version, and config | H,L,E | Non-enumerating discovery; negotiation/critical-extension rejection; immutable unsupported-event quarantine/replay; expand-migrate-verify-contract rollout; N/N-1 window; one-use versioned config migration/rollback; immutable first-release migration-1 checksum plus contiguous Core migrations 2–5; exact SQLite v4 catalog/checksum verification, one-transaction v4→v5 N/N-1 upgrade, Approval v1/v2/v3→v4 atomic migration, injected rollback with no partial schema, five-migration PostgreSQL catalog generation, and rejection of unilateral/prototype/tampered/future/unsupported-old state: tests/discovery/test_non_enumerating_directory.py; tests/protocol/test_version_negotiation.py; tests/operations/test_versioning_runtime.py; tests/production/test_postgres_runtime.py |
BLOCKED_EXTERNAL |
E: independently deployed mixed-version peers and production deprecation/rollback drills remain external. Prototype databases are rejected rather than treated as consent; production mixed-version upgrade evidence is absent. |
| G19 — freshness, crypto, and audit roots | H,L,E,O | Canonical signatures/freshness/replay: tests/security/test_signatures_and_replay.py; IPC restart/root fencing: tests/security/test_ipc_capability.py; key rotation/recovery: tests/identity/test_credential_rotation.py; tests/identity/test_recovery.py; audit checkpoint: tests/audit/test_audit_chain.py |
BLOCKED_OWNER |
E/O: cross-language vectors, cache-partition trials, independent KMS/audit roots, backup/key restore, witness outage/backlog, and catastrophic-root rebuild are absent. |
The release verdict remains blocked while any gate is not PASSED. In this
snapshot G04 has a concrete non-green result, and every required external or
accountable-owner tier listed above is still absent. There is no remaining
locally identified implementation-gap row in the 85-requirement ledger.
Disabling a high-risk optional feature does not waive requirements for the
ordinary self-hosted communication product that remains enabled.
Promotion requires an immutable evidence record identifying the exact source, command, selected tests, environment, versions, seeds/corpus, artifacts, operator, and independent reviewer where applicable. Skips, xfails, missing fixtures, unavailable services, mock ceremonies, deterministic no-inference runs, or reviewed upstream defects remain non-passing evidence.