Journal Field
The journal records immutable history before anything else is inferred from it.
AETHER Documentation
The quickest way to understand AETHER is through one governed case desk: support agents, retrieval sidecars, and human leads share customer issues, candidate resolutions, assignment handoff, replay, and proof in one fabric. Underneath that desk is the same replayable, explainable semantic kernel that also powers the incident blackboard and coordination pilot stories.
Start with the support resolution desk if you want the most relevant ML-facing product story first. The incident blackboard remains the broader governed-workspace reference pattern after that.
Fastest Doorway
These are the quickest links for first-time readers who want one concrete use case before the broader thesis and architecture.
The ML-facing working app pack for retrieved evidence, selected resolution, handoff, replay, and proof.
Reference PatternThe broader governed shared workspace story for agents, operators, authority, replay, and proof.
WalkthroughThe 5-10 minute runnable support-desk exemplar for design-partner and sponsor conversations.
ContextSee where the support desk and incident blackboard fit between live proof and longer-range platform vision.
ProofThe current coordination pilot that keeps the story honest and evidence-backed.
Field Grammar
The docs are meant to do more than index files. They teach the system in the order the system itself thinks, with each semantic job mapped to a recurring field abstraction.
The journal records immutable history before anything else is inferred from it.
The resolver turns raw history into semantic state at `Current` or an exact `AsOf` cut.
The runtime composes recursive and stratified truths from the resolved state.
The explainer shows why the answer is true, not just that the system emitted it.
Field Abstractions
AETHER now presents itself through structural abstractions rather than mascots. Each field below names a recurring semantic behavior in the kernel and gives it a stable visual identity.
Temporal replay, addressability, and semantic motion across `Current` and exact `AsOf` cuts.
Recursive closure, SCC iteration, and the way local relations tessellate into larger truths.
Visible boundaries between semantic states, where a different journal prefix yields a different answer.
Proof paths, parent links, and provenance lines that let the operator inspect why a tuple exists.
Semantic Fabric
AETHER is not just a runtime. It is an attempt to bring support operations, operational memory, derived understanding, and governed action into one coherent surface.
Determine what is truly ready, who is authoritative now, and which stale attempts should be fenced.
Replay exact semantic cuts with Current and
AsOf instead of relying on partial logs and
recollection.
Derive readiness, authority, and consequence from the full dependency chain, then preserve the proof.
Presentation Surface
The docs portal now includes outward-facing product pages built for sponsor review, partner conversations, and screen-share-ready storytelling.
A live front entrance for exportable presentation assets, covers, and proof snapshots.
ExecutiveA concise landing flow for sponsors, buyers, and evaluators, anchored to the current single-node pilot proof.
DeckA presentation-ready view of the commercial story with reusable visual sections.
Use CasesA sequence of increasing proof and ambition for stakeholders, partners, and outside evaluators.
App PackThe flagship ML-facing working application built honestly on top of the current pilot surfaces.
BriefA one-page outward-facing summary for partner and sponsor conversations.
Start Here
If you only have a few minutes, these are the documents that make the project legible quickly and accurately.
The clearest product-facing doorway into AETHER’s current utility.
Front DoorThe thesis, current implementation line, and repository map.
HandbookThe reading map for developers, operators, and evaluators.
EducationA gentle learning path with figures, analogies, and worked examples.
System ShapeHow the journal, resolver, compiler, runtime, explainer, and service fit together.
VisionAn outward-facing page for the product story: memory, intelligence, coordination, and proof.
Commercial StoryThe vision, buyer map, messaging architecture, and category narrative for AETHER.
Use CasesThe disciplined progression from dependency readiness to the autonomous operations control plane.
ShowcaseThe strongest current end-to-end story: replay, recursion, leases, fencing, and proof traces.
Published Surfaces
Generated automatically from the Rust workspace on every push to
main.
Human-written architecture, workflow, glossary, and operator guides anchored in the current codebase.
Open documentation hubOperator-facing walkthroughs and one-click launcher paths for the strongest demonstrations in the repository.
Open operator guideBest Showcase
If you need one demonstration that proves progress rather than merely claiming it, start with Demo 03.
Operator Path
Use the one-click Windows launcher or the direct Rust example, then keep the generated report as a presentation artifact.
Core Guides
Implementation Frontier