Speculum

What this draws

Rings are roles. The centre is the public site. The first ring contains runtime services. The second contains periodic observers and the local host they can see from inside. The third contains public policy, reusable tooling, and source substrate. The outer ring holds dependencies outside the repository projection.

Beam length is reach. Rotation speed is the reviewed period, so the thirty-second local telemetry sampler moves visibly while weekly dependency and resource audits barely turn. At Real · 1×, almost nothing moves. That is the least flattering and most literal view.

In Evidence mode a green dot means the periodic schedule has an inspected source. A hollow amber dot would mark an assumed period; this snapshot currently contains none. Nodes without a dot are request-driven, event-driven, manual, continuous, boot-triggered, or external rather than unverified.

Pinning a node filters the investigation to its declared observation and report paths. The guided trace follows one deterministic route from local telemetry to the public site. It is an explanatory traversal of declared relationships, not a claim that those components just ran.

The ledger is generated simulation output, not operational evidence. Notifications and state changes are deliberately not simulated. This page does not claim that a workflow ran, a service changed condition, or an alert was delivered.

Evidence boundary

The topology is a reviewed public snapshot dated 27 July 2026. Repository classification comes from the Atlas Infra public classification projection. Runtime relationships come from the public estate manifest and direct repository configuration. Periods come from the owning repository's current workflow, Worker configuration, timer documentation, or sampler documentation.

Private repository identities and private relationships are absent. This is not a live health surface and makes no network request. Status remains the public source for current service condition.