Release identity
READY- Version
1.0.0- Release date
August 15, 2026- Source commit
23ffa25- Publication commit
3c76484- Baseline commit
97e45b7- Baseline status
- CERTIFIED
Follow each public release from its promoted source through the official archive and registered baseline. Download artifacts and documentation remain connected to the same canonical release record.
The current public release is tied to a tagged source state, a tracked artifact publication, and a certified post-release baseline.
1.0.0August 15, 202623ffa253c7648497e45b7ACC 1.0.0 is the repository's current stable public release. Its report records every implemented readiness gate as PASS, while the baseline connects the promoted source to the later artifact publication.
Supported installation targets are Linux and macOS. Verify the package and its adjacent checksum before extraction.
These three repository commits establish the v1.0.0 release lineage; each step records a different responsibility.
Step 1
23ffa25
The v1.0.0 tag identifies the promoted source state.
Step 2
3c76484
The package, checksum, manifest, and release report entered the tracked archive.
Step 3
97e45b7
Publication lineage and architecture evidence were registered as CERTIFIED.
The package and its three adjacent records are served directly from the tracked v1.0.0 archive.
611 KiB · tar.gz
Canonical v1.0.0 source package for verified installation.
ACC-1.0.0-23ffa25.tar.gz
SHA-256 · text
Published digest and package filename for byte-level integrity checks.
ACC-1.0.0-23ffa25.tar.gz.sha256
Manifest v1 · text
Version, source commit, build time, and exact package identity.
release.manifest
Validation evidence · text
READY decision and PASS results from every implemented release gate.
RELEASE.report
Only releases with a tracked public artifact set are listed here; development milestones and internal tags are not presented as public downloads.
Current stable
Released August 15, 2026 from 23ffa25; archived in3c76484 and registered with aCERTIFIED post-release baseline.
Keep the package, checksum, manifest, and report together, then follow the version-matched installation workflow.