Aegis Release Notes
v2.9.4 (2026-09-01)
Generalize bounded preservation references
- Broaden Bounded Preservation beyond identity, selector, precedence, scope,
and role-binding examples to any existing semantics, responsibility,
contract, or relationship change. - Require every known explicit anchor and upstream/downstream reference to
receive an explainable disposition: preserve, rebind to the canonical owner,
retire with reason, or reject because of conflict. - Keep unresolved relationships unknown and reuse existing
*Ref,
missingRefs,unknowns, and uncovered-scope slots instead of adding a new
artifact, required field, or semantic graph. - Keep relationship-graph, referential-integrity, and authoritative-lineage
authority with the future Runtime Core. - Update systematic debugging, first-principles review, completion
verification, artifact schema, and runtime-ready boundary guidance. - Add a non-selector shared-config regression case while preserving the
original selector role regression coverage.
Bounded failed-verification evidence convergence
- Add
add-attemptfor failed verification retries inside the active slice. - Reserve
add-evidencefor terminal evidence and make same-slice evidence
updates idempotent instead of append-only. - Keep
bundlescoped to terminal evidence; excludeattemptedand
supersededrecords from the proof bundle. - Add advisory
process-artifact-pressuremetrics and a convergence-stop
signal after repeated failed attempts. - Keep checkpoint, drift, baseline-usage, and evidence markdown sections
bounded through in-place updates instead of unbounded append growth. - Add deterministic retry-convergence and workflow-quality coverage while
preserving Aegis advisory boundaries.
Verification boundary
- Targeted workspace-helper, artifact-schema, long-task, workflow-quality,
context-budget, boundary, governance, host-wiring, plugin-sync, and unit
checks passed. - Layer 1 passed 36 checks and retained the known environment-bound offline
Codex fixture platform check on this Windows environment. That check is not
treated as a fresh Codex live-closeout claim. - Claude dynamic trigger testing remains environment-bound because this
environment does not provide a usable Claude CLI; it is not claimed as
passed.