ETHENOTETHAN / PORTAL

Architecture Observatory

Source-backed loading Overview Features Repository ↗

LIVE ARCHITECTURE MODEL

The shape of Portal

A hierarchical view of product surfaces, state orchestration, backend seams, foundations, and external systems. Select any component to trace its evidence.

DETERMINISTIC INTERPLAY GRAPH

Connection pools & on-device models

A verbose, source-extracted graph of the connection-pool resources, the queried RPC and REST endpoints, the product surfaces that invoke each namespace, the on-device language and speech engines, and the event bus, seam, and hub constructions that fan a transport's push events out to their subscribers and make a network transport and an on-device model interplay. Every node deep-links to its source; the load-bearing pools and engines are gated by a curated overlay.

Extracted by static source rules and checked against architecture/interplay/overlay.json. Edges are ownership, lifecycle, and cross-domain wiring—not runtime topology or live connection counts.

DETERMINISTIC EXECUTION EVIDENCE

Execution & tasks

Lexically observed execution domains, task creation sites, stored handles, and cancellation calls grouped by source-owned component. Each item carries its extraction rule and exact source line.

Observed by static source rules—not agent-authored and not proof of runtime scheduling or overlap.

STATIC OWNERSHIP & LIFECYCLE CLUSTERS

Connections & streams

Deterministic pockets group stored resources, task handles, and mechanically recognized lifecycle operations by component and enclosing owner type.

These pockets are static clusters, not runtime topology. Cardinality describes source fields, never live connection counts.

SOURCE-ORDERED OPERATIONS

Scenarios

Operation sequences are assembled only from deterministic lifecycle evidence within one static pocket.

HUMAN-CONTROLLED AUTHORITY

Specifications

Normative architecture remains reviewable prose. Generated observations may inform it, but cannot silently redefine it.

DETERMINISTIC DISCOVERY

Source inventory

Every Swift source file is assigned to one architectural component. The inventory is reproducible from the repository without an LLM.

ComponentLayerFilesLinesDeclarations