Release System

AeThex separates public releases, product changelogs, documentation changes, deployments, incidents, and community announcements. These records may reference one another, but they are not interchangeable.

Field	Value
Documentation status	Active
Applies to	Corporation, Foundation, and Labs
Public release directory	aethex.us/releases
Canonical documentation	docs.aethex.support
Last verified	2026-07-29

Public hierarchy

Ecosystem releases — aethex.us/releases presents curated public changes across all three Trinity arms.
Trinity views — Corporation, Foundation, and Labs filters use the same release records.
Product changelogs — product domains show only releases that affect that product.
Release details — permanent pages describe changes, availability, affected domains, documentation, and known limitations.
Technical documentation — docs.aethex.support explains how released behavior works.
Engineering history — repositories and staff deployment records retain commits, builds, and rollback details.

Record types

Record	Purpose	Public location
Release	Curated user-visible product change	`aethex.us/releases`
Product changelog entry	Product-filtered release	Product `/changelog`
Release note	Detailed behavior, compatibility, and migration information	`docs.aethex.support`
Documentation change	Change to manuals or reference material	Documentation changelog
Deployment	Environment, build, commit, and rollback evidence	Engineering/staff history
Incident	Availability degradation and resolution	Status service
Security advisory	Coordinated vulnerability disclosure	Security advisory section
Announcement	News that may not change a product	Product or community feed

Required release fields

Stable release identifier
Title and plain-language summary
Primary Trinity owner
Collaborating Trinity arms, when applicable
Product and affected components
Primary and affected domains
Release channel and maturity
Version or dated web-release identifier
Publication and production-availability timestamps
Added, changed, fixed, security, deprecated, and removed items as applicable
Documentation and migration links
Known limitations
Deployment evidence
Author and approver
Correction, supersession, rollback, or withdrawal state

Publication flow

Code or configuration change
  → engineering/deployment record
  → draft public release
  → product-owner review
  → documentation verification
  → approved canonical release
  → aethex.us/releases
  → product changelog
  → optional Discord or email announcement

Deployments may create draft release material, but they do not automatically become public releases.

Ownership and scope

One Trinity arm is the primary owner; other arms may be contributors.
A cross-Trinity release is one record with multiple contributors, not three duplicated releases.
Shared product changes belong to the shared product.
Customer configuration belongs to that customer or community deployment history.
Infrastructure-only work remains in the engineering log unless it changes public behavior.
Documentation-only work appears in the documentation changelog.

Corrections

Published history is not silently rewritten. Corrections identify what changed and when. Withdrawn, rolled-back, superseded, and deprecated releases retain their permanent URLs and current state.