Skip to content

ASB v2.0.0-rc.3 — Preview

Pre-release
Pre-release

Choose a tag to compare

@thinksyncs thinksyncs released this 04 Nov 10:51
Immutable release. Only release title and notes can be modified.
v2.0.0-rc.3
c7a3004

This prerelease includes the Human and application previews developed since rc.2. It preserves the supported Direct-Agent v1 compatibility boundary. The stable/latest release remains v1.1.1.

Changes

  • Local Human approval with four distinct decisions. Only approval permits a change; an undecided Human judgment remains separate from an unknown execution result.
  • Experimental Human Coordination, Task–Action lifecycle, single-host SQLite recovery and durable relay state. The opt-in Cloudflare notification adapter does not turn delivery acknowledgement into Human approval.
  • GGUF and Safetensors/LoRA bundle verification under the documented runtime restrictions. External model APIs without verifiable evidence are rejected.
  • Stricter required-attestation evidence handling, Agent RPC proof binding and runtime lifecycle checks.
  • Go 1.26.10 and dependency updates, including JOSE 4.1.6, chi 5.5.0 and protobuf 1.36.12.

Preview downloads

Download Platform / purpose
asb-human-v2.0.0-rc.3-linux-amd64.zip Local Human approval, Linux x86-64
asb-human-v2.0.0-rc.3-darwin-arm64.zip Local Human approval, macOS Apple Silicon
asb-human-v2.0.0-rc.3-windows-amd64.zip Local Human approval, Windows x86-64
asb_2.0.0.rc.3-1_all.deb Debian metapackage
asb-tools_2.0.0.rc.3-1_amd64.deb Debian tools
asb-human_2.0.0.rc.3-1_amd64.deb Debian Human application
asb-s3_2.0.0.rc.3-1_amd64.deb Debian S3 application

Human ZIPs are the original CI artifact archives, with usage instructions, a binary checksum, a source/build inventory and license notices. Debian packages include their inventories and notices. Use the top-level SHA256SUMS to verify downloaded release files; release-evidence.json records their exact source and CI provenance. The signed Git tag records the SHA-256 of that checksum manifest.

GitHub normalizes special characters in asset filenames. It replaces ~ with . in these four Debian download names, including when their names are updated through the API. The package bytes and internal version 2.0.0~rc.3-1 are unchanged. Both checksum manifests and the CI evidence retain the original filenames. After downloading the assets into a new directory, restore these four names before checking the manifest:

gh release download v2.0.0-rc.3 --repo ToppyMicroServices/agents-secure-binding --dir asb-v2.0.0-rc.3
cd asb-v2.0.0-rc.3
mv asb-human_2.0.0.rc.3-1_amd64.deb 'asb-human_2.0.0~rc.3-1_amd64.deb'
mv asb-s3_2.0.0.rc.3-1_amd64.deb 'asb-s3_2.0.0~rc.3-1_amd64.deb'
mv asb-tools_2.0.0.rc.3-1_amd64.deb 'asb-tools_2.0.0~rc.3-1_amd64.deb'
mv asb_2.0.0.rc.3-1_all.deb 'asb_2.0.0~rc.3-1_all.deb'
sha256sum -c SHA256SUMS

On macOS, use shasum -a 256 -c SHA256SUMS for the last command. The manifest itself has SHA-256 10de0532295b0a6126f53c8b2b4712b588f0b8f4c081b3021223434493e26bfb, anchored in the signed v2.0.0-rc.3 tag. Filename restoration does not modify any file contents.

Validation

Two Human qualification attempts encountered macOS arm64 runner-capacity failures before the affected job started: first the Mac application tests, then the Mac artifact self-test. Scoped retries preserved successful jobs and the CI-built artifacts. The evidence records these infrastructure failures and the final qualification attempt.

Scope and limits

Human, model-runtime, least-privilege and delivery features remain Preview or experimental. The executables are not platform-code-signed or notarized. SNP, TDX and Cocos retain their independent module versions. See the compatibility policy and complete changelog.

Production APT publication, full Azure acceptance and deployment-specific provider qualification remain separate. APT lifecycle tests use ephemeral CI keys; those keys and test repository metadata are not release assets. The original Debian candidate manifest says unpublished because it records the build-stage state; the later release and CI evidence establish publication and qualification. These new S3 binaries do not inherit the historical binary's AWS qualification. No local builds or runtime tests were used for this release; builds and execution checks ran on hosted CI.