Prepare aoa-techniques v0.5.0 release#494
Merged
Merged
Conversation
8Dionysus
marked this pull request as ready for review
July 14, 2026 01:39
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
The existing Unreleased section covered only part of the actual landed delta. This release note is based on the tagged Git range, the 366-path source diff, commit bodies, owner surfaces, and generated contracts. It includes an exact ordered 37-of-37 commit inventory so the public release cannot silently omit work that bypassed CHANGELOG.md.
Impact
v0.5.0 publishes the manifest-owned validation topology, bounded memo/eval/KAG/stats ports, hardened KAG artifact admission and canonical repository index family, plus the correctness and public-hygiene fixes landed since v0.4.5. It does not claim skill runtime, proof, routing, memory, KAG-substrate, cross-owner stats, or package-registry authority.
Validation
Generated parity and remaining risk
All changed generated surfaces were rebuilt from authored sources. The release remains a tagged public corpus and GitHub Release; no package registry publication is in scope.