The Æther Flow documentation system serves two related research tracks: foundational physics and the governed, human-accountable AI workflow used to organize and test that work. This overview is the reader-facing front door to those materials, not a replacement for the registered sources and current records that define their scoped claims and status.
Five public destinations organize the system. Documentation Overview explains how to read it; Anthology Articles collects approved PDF-first publications; Research Articles groups registered TeX with readable PDF manifestations; Governance & Control presents explicitly approved Markdown within operational scope and freshness limits; and Diagram Gallery presents approved visual aids with captions and provenance.
Formats do not inherit equal authority from appearing together. Registered TeX can carry scoped research-source authority, a PDF may be its human-readable derivative, approved Markdown can carry governance or operational authority within its stated lane, diagrams remain explanatory, and manifest hashes establish artifact identity rather than scientific correctness.
Begin with the internal route that explains the question, then use status, provenance, and source links when direct inspection is needed. Current-state material must carry dates or revision evidence; generated, historical, source-index-only, and retrieval-support material remains visibly distinct from current approved sources.
Five public destinations
Choose the document role before the file format.
The overview is the front door to four collection categories. Each destination states its typical formats and the boundary that remains attached to those materials.
01 · Front door
Documentation Overview
Orient by category, format, authority role, provenance, status, and reader purpose before opening individual files.
- Typical format: reader-facing HTML.
- Boundary: explanation and navigation do not replace registered sources or current control records.
Open category02 · PDF-first
Anthology Articles
Read curated synthesis, exposition, and editorial publications only when an approved catalog-backed PDF exists.
- Typical format: PDF.
- Boundary: visual polish does not determine authority; the source record and publication status do.
Open category03 · Research
Research Articles
Inspect logical research documents with TeX and PDF roles kept distinct. The current catalog contains 8 approved research records.
- Typical formats: registered TeX and corresponding readable PDF.
- Boundary: claim and research status remain scoped to the registered source record.
Open category04 · Operations
Governance & Control
Read explicitly approved policy, schema, procedure, registry guidance, publication, and workflow Markdown.
- Typical format: approved Markdown.
- Boundary: authority applies only within the stated operational scope and freshness window.
Open category05 · Visual
Diagram Gallery
Browse approved concept-grouped visuals with nearby captions, alternative text, and provenance.
- Typical formats: PNG and SVG derivatives from registered visual sources.
- Boundary: a diagram aids comprehension and does not independently prove a claim.
Open categoryStatus and freshness
Status labels answer different questions.
Publication status, source role, and currentness remain separate. A polished derivative can still be historical, and an indexed source can remain unavailable as a public download.
- Approved
- Reviewed for its stated public roleApproval does not expand the source's scientific or operational authority.
- Draft
- Not a final public claim surfaceRead as work in progress and do not infer publication or promotion.
- Historical
- Retained for traceabilityA historical record may be superseded even when its artifact identity is intact.
- Current snapshot
- Freshness-sensitive stateCheck source date, commit, import date, review date, and supersession state.
- Generated derivative
- Produced from another sourceUse for reading or comprehension while the registered source retains its role.
- Source-index-only
- Discoverable without a public fileThe index identifies a source record but does not imply a downloadable publication.
- Retrieval support
- Navigation aidSearch, memory, semantic, wiki, and cache layers help locate evidence without becoming authority.
Freshness evidence
Current-state material needs an inspectable time boundary.
When any field is unavailable, the page should say that freshness cannot be confirmed rather than infer currentness from presentation.
Scroll table horizontally when it overflows.
| Field | Why it matters |
|---|
| Source date | Places the material in its original research or operational context. |
|---|
| Source commit | Binds the public manifestation to an inspectable repository revision. |
|---|
| Website import date | Shows when the public copy was synchronized, not when its claims became correct. |
|---|
| Review date | Records the bounded review event when one is available. |
|---|
| Current or superseded | Prevents older material from being read as the live state without confirmation. |
|---|
| Freshness warning | States when currentness cannot be confirmed rather than silently assuming it. |
|---|
← Earlier columnsMore columns →
Internal-first reading paths
Start with the page that explains the question.
Downloads, raw files, manifests, and repository paths follow the explanatory route unless a specialist already knows the exact source record that requires inspection.
Scroll table horizontally when it overflows.
| Reader | Recommended route sequence | Reason |
|---|
| New reader | Documentation Overview → Anthology Articles or a project overview page | Orientation and context come before individual publications. |
|---|
| Physics specialist | Physics status pages → Research Articles → source provenance | Claim status and open burdens frame direct source inspection. |
|---|
| AI workflow reviewer | AI Research System → Governance & Control → relevant records | Workflow scope and human gates precede operational artifacts. |
|---|
| Governance reviewer | Governance & Control → Source Authority → Registries → Publication Process | Policy scope, record status, and publication boundaries stay connected. |
|---|
| External reviewer | Reviewer Packet → Research Articles → Claim Status → Governance & Control | The review path exposes nonclaims and evidence boundaries before source evaluation. |
|---|
| Website maintainer | Documentation Overview → Publication Process → Repository Map → Site Builder Guide | Reader purpose and source bundles come before repository edits. |
|---|
← Earlier columnsMore columns →
Catalog-backed publication state
Only populated approved collections appear as published.
The catalog summary is derived from the current public document records. It does not turn an empty planned category into a publication and does not expand the authority of any listed item.
- Approved records
- 8Only approved catalog records contribute to this count.
- Published collections
- 1A collection is counted only when it contains an approved item.
- Empty categories
- Not represented as publishedA planned category remains an explicit empty state until approved catalog content exists.