Skip to content
YewForge Digital / Engineering

System page · Observability

Observatory

A local analytical view for resource telemetry and bounded runtime state. It complements the native System Pulse rather than replacing it.

Partially implementedLast reviewed: 15 July 2026Evidence classes: IMPLEMENTED · VALIDATED · DESIGNED

Objective and architecture

Observatory collects and presents local CPU, RAM, GPU, VRAM and thermal telemetry alongside selected factory and runtime state. Its analytical path uses a local metrics stack and a browser-facing view. Native System Pulse remains the primary in-application surface for concise state awareness.

Observatory relationship

Both paths are local and read-only; neither is an authority mechanism.

Implementation, validation and limits

A project-local analytical stack was installed, benchmarked and stopped cleanly after use. It retained authentication and restricted navigation to a local loopback endpoint. Exporter and collection failure/recovery behaviour were tested. The browser path remains operational as a local analytical option.

KEJ-EV-004IMPLEMENTED · VALIDATED
Claim
A local analytical Observatory path was installed and benchmarked.
Method
Targeted observability tests, runtime suite checks and measured local benchmark work.
Result
Local collection and analytical presentation were validated within their bounded setup.
Limitation
The embedded native shell was deliberately deferred after process-cleanup validation failed; it is not an active integrated surface.
Source period
2026 implementation and benchmark records.

Failure, recovery and privacy

Freshness and unavailable-source states are important: absent telemetry should be labelled unavailable rather than represented as fixture data. The analytical stack is local-only and temporary; it is not an external cloud service or a permanent boot integration.

Future work may add event annotation and stronger links to the Living Activity Timeline. It must retain graceful renderer failure behaviour and the established local privacy boundary.

Related systems and provenance

Living Activity Timeline supplies time-based context. Forge Workshop can surface read-only operational state. Evidence and External Memory preserves validation and failure records.

Sources: canonical Observatory benchmark, native-shell result and Command Centre live-wiring records. Local addresses, ports and configuration details are excluded.

Related revision

See KR-002: Native Observatory Cleanup Gate for the lifecycle correction record.