Skip to content

UAR 1.4.0-rc.4 Linux amd64

Pre-release
Pre-release

Choose a tag to compare

@GQAdonis GQAdonis released this 14 Nov 09:30
· 31 commits to main since this release
v1.4.0-rc.4
eaf82c9

UAR 1.4.0-rc.4 qualification record

Release candidate scope is the Linux amd64 UAR API container. Installed checks exercise UAR through its public interfaces using deterministic fixtures and independent protocol peers. Browser, application UI, Astro site build, and standalone framework certification are excluded. The full offline archive remains in the security audit.

The selected lane is Linux amd64, server-full,postgres-backend, behind a trusted host or gateway. Embedded SurrealKV on SurrealDB 4.0 is the default. PostgreSQL 18.6 in the pinned Forge Compose profile is Preview and subject to the published capability restrictions. Support and recovery contract · Persistence capability contract.

Source commit eaf82c935887ef5fe1c77379f36246a19b6075a8. Source tree 13ffd54be582070d925e9f8372caef99f56655b1. The last source pin landed through PR #501 after the Liter Astro 7.4.7 frozen install. PR #501.

Exact image ghcr.io/prometheus-ags/universal-agent-runtime@sha256:0b6d94d6a776d7de8abd00085856c68dddd12e12251750f1aab8e1f1dc79780e.

Check Evidence and scope
F01 Exact baseline Passed on exact committed tree. Three existing Rust baseline feature profiles compiled. Focused JWT/JWKS, embedded storage reopen and Wasm-trust behavior passed. A fresh HTTPS clone fetched and matched all 16 recursive pins.
F02 Installed lifecycle Passed installed RC4 readiness, governed MCP, active cancellation and interrupted-stream scenarios. The separate same-image known-outcome shutdown and restart control stopped cleanly. Earlier Gate091 also verified known-tool-outcome clean exit.
F03 Restart and retained state Passed on RC4 with owned data retained across a clean stop and restart on the same volume. Earlier Gate103 covered retained knowledge-base fact and conversation history.
F04 Upgrade and rollback Earlier embedded SurrealKV qualification passed five scenarios for the pinned 3.3.0 baseline to 4.0, using a separate destination, preserving the source and exercising rollback after interruption or a recorded write disposition. It covers the documented pair and recovery procedure. Upgrade and rollback runbook.
F05 Restricted PG18 Earlier Gates106–107 used the Gate096 Linux image and pinned PG18.6. They observed seven capability refusals, backup/restore of owned data, foreign-owner refusal before and after restore, and clean shutdown. The restore fixture reseeded configuration and excluded credential-bearing settings.
F06 Streaming and tools Passed RC4 installed cancellation, interruption, admission and MCP checks. Earlier RC3 Gate171 exercised the existing source integration targets and Gate174 verified the installed RC3 digest.
F07 Routing and vision Earlier Gate083 passed three inherited-fallback, constrained-routing and refusal scenarios, including intact image order and the final output cap. Deterministic peer evidence covers delivery and dispatch. Genuine-provider vision and broader routing remain unverified.
F08 Embeddings Earlier Gates108–113 exercised deterministic counters, selected input/output refusals, held-request model swap, and re-embedding of a retained document after explicit old-space refusal.
F09 Documents Passed RC4 installed DOCX, XLSX, EML, ZIP and PNG OCR extraction, indexing and retrieval, including malformed-file refusal.
F10 Independent MCP Passed on RC4 with the independent official rmcp 3.8.0 peer, Streamable HTTP, and negotiated MCP revision 2025-11-25. The uncertain-effect shutdown refused as expected. Known-outcome shutdown is covered by the separate control.
F11 Independent A2A Passed RC4 independent A2A flow and cancellation with official @a2a-js/sdk 1.0.1, covering Agent Card, JSON-RPC, streaming and refusal. Earlier Gate092 is retained for the earlier artifact. Other transports and extensions are excluded.
F12 Full-harness restart contract Passed RC4 old-epoch refusal after restart. Full-harness execution is process-ephemeral, with no supported restart recovery or steer. Native interfaces have their separately documented recovery guarantees.
F13 Recovery and effects Passed current RC4 admission, restart and refusal to treat unresolved MCP effects as safely shut down. Earlier Gates154–157 cover selected accounting and completion scenarios. The #466 recovery table governs each interface. Browser history reload is excluded.
F14 Release supply chain Recursive OSV and the final security audit passed on the exact tree and digest, with zero open Dependabot alerts. Full offline source archive passed the locked network-denied build. Passed verification of signed archives and checksums, image signature, SLSA provenance and CycloneDX attestations against the approved Sigstore identity. The modified checksum file failed signature verification as expected.
F15 Wasm Passed direct Wasm trust checks on exact RC4 source and installed offline toolchain inspection. Governed Wasm and AOT execution are excluded.

The earlier gates retain their original artifact, verifier, and fixture identities. ARM64, Windows, mobile, standalone/native runtime, arbitrary throughput or latency guarantees, real-provider quality, production deployment, and GA promotion are outside this record. The PG17 Kubernetes and Helm defaults are outside the restricted Forge PG18 profile. No ARM64 wal-g qualification is claimed.

Use the published release manifest, Sigstore bundles and checksum set to verify the exact payload before use. The downloadable Linux binary was extracted from the tested container. Installed qualification applies to the container. RC4 signed release evidence.