A system you can inspect from the boundary inward.
The viewport maps the intended layers: public edge, controlled routes, operator stations, receipts, and experimental language fields. Move a pointer or use the arrow keys to inspect the stack. The map explains the architecture; linked source and evidence support the claims.
AetherMoore micro-stack
Public edge · tunnels · operator stations · sealed data
System layouts & flow
Client → edge gateway → tunnel → home runner → receipts.
- Pages + Workers edge
- cloudflared outbound only
- AetherDesk control plane
Fields & relations
Langues fields, browser ops fields, audit entities — not one SQL warehouse.
- Six tongue fields (below)
- Session / Receipt / DesktopState
- Perceive→Plan→Govern→Execute
Stations & routes
Ops floor tiles and assistant routing maps instead of raw infra sprawl.
- Backroom stations
- assistant-routing.json
- Control Bridge surfaces
Admin live probes
Edge health, scorecard, local desk/MCP when on operator machine.
- Backroom monitors
- scbe-shim health
- Context Ledger events
Langues and Related Fields
The published field registry describes each experimental tongue and its current weight profile. These fields are implementation concepts under evaluation, not evidence of a general capability or security guarantee.
Perceive · Plan · Govern · Execute
Control fields of the governed browser loop (AetherBrowse / AetherWeb).
Browse · Chat · Rooms · Vault · Ops
User-facing surfaces from Browser System Fields and Surfaces.
/static/langues-fields.json records the
published field map, and the
public repository exposes the
implementation and test history. This viewport is an architecture map, not proof by itself.