Releases: wallidsaydi-creator/HOM-AIMOS
Release list
HOM-AIMOS v1.0.4 — Canonical Working Baseline
HOM-AIMOS v1.0.4 is the closed canonical software baseline: an agent-security system built on cryptographically auditable persistent memory.
This software release includes:
- one public same-user installer with Housekeeper-first Genesis and one-passphrase agent onboarding;
- certificate-envelope authenticated SAVE and RECALL;
- immutable memory, provenance, lineage, epistemic, mutation, and event ledgers;
- native retrieval with signed disclosure receipts;
- Canary controls and signed SABER-style operational evaluation;
- autonomous Housekeeper heartbeat and scheduler ownership;
- independent portable protocol and evidence verifiers.
The retired SE runtime authority remains disabled. Authorization and disclosure are enforced by the signed identity/grant boundary, database scope, provenance admission, Canary, epistemic selection, and bounded signed receipts.
Verification:
- Secret scan: passed
- Node.js 20, 24, and 26 source gates: passed
- Fresh disposable Genesis and signed live-fire proof: passed
- SAVE, RECALL, Housekeeper heartbeat, and restart parity: passed
- Dependency audit: zero known high-severity vulnerabilities
Release ceremony: https://github.com/wallidsaydi-creator/HOM-AIMOS/actions/runs/33520234578
Main source CI: https://github.com/wallidsaydi-creator/HOM-AIMOS/actions/runs/33521897905
Use SHA256SUMS to verify the source package and CycloneDX SBOM.
Publication boundary: the submitted MutMem paper is a separate timestamped research artifact and is not revised or republished by this software release.
HOM-AIMOS v1.0.0 — MutMem V2 paper snapshot
Immutable historical source snapshot cited by the MutMem V2 arXiv submission.
Tag v1.0.0 resolves permanently to commit fcda26d. The source tree is bound by RELEASE-SOURCE-MANIFEST.json and was rechecked for manifest parity, private-path exclusion, internal-disclosure exclusion, and secrets before this archival release was restored.
This release preserves the system and evidence state referenced by the paper. Current HOM-AIMOS development continues independently on main; later product releases do not move or rewrite this tag.
A 2026-09-01 rerun of this historical tag workflow stopped before live-fire because the old workflow used the runner Python environment, whose cffi 2.1.0 differed from the tag-pinned 2.0.0. No new green-ceremony claim is made for that rerun.