Blame
|
1 | # Release Notes |
||||||
| 2 | ||||||||
| 3 | Release notes explain the behavior, compatibility, migration requirements, known limitations, and availability of an approved AeThex release. They supplement the public release record; they are not a second independently maintained changelog. |
|||||||
| 4 | ||||||||
| 5 | | Field | Value | |
|||||||
| 6 | |---|---| |
|||||||
| 7 | | Documentation status | Active | |
|||||||
| 8 | | Applies to | Corporation, Foundation, and Labs | |
|||||||
| 9 | | Public release directory | [aethex.us/releases](https://aethex.us/releases) | |
|||||||
| 10 | | Last source review | 2026-07-29 | |
|||||||
| 11 | ||||||||
| 12 | ## Where releases live |
|||||||
| 13 | ||||||||
| 14 | - [aethex.us/releases](https://aethex.us/releases) is the canonical public directory across the three Trinity arms. |
|||||||
| 15 | - Product `/changelog` pages are filtered views of the same approved release records. |
|||||||
| 16 | - Product documentation on this site explains released behavior. |
|||||||
| 17 | - [[Changelog]] records changes to the AeThex platform and documentation history currently preserved here. |
|||||||
| 18 | - Repository commits and deployment records remain engineering history. |
|||||||
| 19 | ||||||||
| 20 | ## Required release-note content |
|||||||
| 21 | ||||||||
| 22 | A substantial product release should document: |
|||||||
| 23 | ||||||||
| 24 | 1. What changed and who it affects. |
|||||||
| 25 | 2. Production availability and release channel. |
|||||||
| 26 | 3. Affected products, components, and domains. |
|||||||
| 27 | 4. Authentication, permission, data, or privacy changes. |
|||||||
| 28 | 5. Compatibility and migration requirements. |
|||||||
| 29 | 6. Known limitations. |
|||||||
| 30 | 7. Rollback, correction, deprecation, or supersession state. |
|||||||
| 31 | 8. Links to the permanent release record and relevant product documentation. |
|||||||
| 32 | ||||||||
| 33 | ## Historical material |
|||||||
| 34 | ||||||||
| 35 | Older release claims are retained only when they can be tied to current source, deployment evidence, or an approved historical record. Reachability, placeholder content, roadmap text, and unverified implementation notes are not sufficient evidence of a public release. |
|||||||
| 36 | ||||||||
| 37 | ## Related documentation |
|||||||
| 38 | ||||||||
| 39 | - [[Releases]] |
|||||||
| 40 | - [[Release System]] |
|||||||
| 41 | - [[Changelog]] |
|||||||
| 42 | - [[Domain Registry]] |
|||||||
| 43 | - [[API Versioning]] |
|||||||