DEV Hermes Workspace
76 pages 75 clean 1 need attention
Page navigation 76

Project

Domains

1

Folders · apps/

Folders · docs/

Folders · knowledge/

Folders · ops/

Folders · packages/

Folders · scripts/

Folders · tests/

Folders · pods/

Folders · tools/

Shared

Metadata stale
Route
/knowledge/portal/domains/dashboard
Source
knowledge/portal/domains/dashboard.md
Covered files
9
Last generated
2026-04-13T16:32:49.474488+00:00

Dashboard

State: source hash changed since last sync

Dashboard

Overview

Domain page auto-seeded by wiki bootstrap for new source lane.

Covered files

  • apps/portal/dashboard/README.md
  • apps/portal/dashboard/__init__.py
  • apps/portal/dashboard/data/README.md
  • apps/portal/dashboard/dispatch_telemetry.py
  • apps/portal/dashboard/log_retention.py
  • apps/portal/dashboard/logs/active/INFO/2026-04-13.jsonl
  • apps/portal/dashboard/sampler.py
  • apps/portal/dashboard/telemetry.py
  • apps/portal/dashboard/tokscale_ingest.py

File map

README.md

  • Path: apps/portal/dashboard/README.md
  • What: apps/portal/dashboard/ contains dashboard data assembly and telemetry projection logic. This boundary currently has 7 direct file(s) and 2 direct subfolder(s).
  • Does: It implements runtime-facing product behavior and integration wiring (dominant direct file kinds: .py:6, .md:1).
  • Why: This is where user-visible behavior is delivered, so clear ownership is critical for reliable iteration.

__init__.py

  • Path: apps/portal/dashboard/__init__.py
  • What: init module for apps/portal/dashboard.
  • Does: Implements module routines used by this runtime surface.
  • Why: Keeps behavior boundaries explicit so wiki maps stay useful without reading full files.

README.md

  • Path: apps/portal/dashboard/data/README.md
  • What: apps/portal/dashboard/data/ contains dashboard fixture/reference inputs used by dashboard data assembly. This boundary currently has 1 direct file(s) and 0 direct subfolder(s).
  • Does: It implements runtime-facing product behavior and integration wiring (dominant direct file kinds: .md:1).
  • Why: This is where user-visible behavior is delivered, so clear ownership is critical for reliable iteration.

dispatch_telemetry.py

  • Path: apps/portal/dashboard/dispatch_telemetry.py
  • What: Dispatch telemetry persistence contract for Portal inference events.
  • Does: Expands/migrates the inference_events schema and ingests normalized dispatch records with explicit latency/fallback provenance fields.
  • Why: Implements TASK-246 so local/remote route, fallback behavior, and timing signals are durable for dashboards and QA evidence.

log_retention.py

  • Path: apps/portal/dashboard/log_retention.py
  • What: Structured log retention and recycling policy for Portal runtime logs.
  • Does: Applies age-based movement from active logs to recycle bins per severity tier and purges recycle data after retention cutoff.
  • Why: Enforces predictable disk hygiene and recoverability while matching project WoW retention rules (INFO/WARN/CRITICAL windows plus recycle cleanup).

2026-04-13.jsonl

  • Path: apps/portal/dashboard/logs/active/INFO/2026-04-13.jsonl
  • What: Source artifact for 2026 04 13 in apps/portal/dashboard.
  • Does: Contributes implementation or support behavior for this runtime surface.
  • Why: Maintains explicit ownership boundaries for faster agent orientation.

sampler.py

  • Path: apps/portal/dashboard/sampler.py
  • What: Runtime metrics sampler and summary builder for Portal dashboard APIs.
  • Does: Collects host/service health snapshots, stores time-series in SQLite, and assembles the dashboard payload consumed by live UI cards and charts.
  • Why: Centralizes operational telemetry so the dashboard can stay fast, deterministic, and auditable across degraded and normal runtime states.

telemetry.py

  • Path: apps/portal/dashboard/telemetry.py
  • What: Lane telemetry aggregation helpers for dashboard telemetry APIs.
  • Does: Aggregates lane cost/SLO and dispatch route parity with optional environment/role/model filters and trend windows.
  • Why: Keeps telemetry dashboards/API contracts queryable by operator dimensions without duplicating aggregation logic in routes.

tokscale_ingest.py

  • Path: apps/portal/dashboard/tokscale_ingest.py
  • What: Tokscale snapshot persistence helpers for Portal dashboard APIs.
  • Does: Stores generated Tokscale report payloads in Portal-owned SQLite and returns the latest normalized snapshot for dashboard rendering.
  • Why: Keeps Hermes usage analytics durable inside Portal so dashboards can show real Tokscale-backed details without shelling out on every page load.

Test coverage

  • (no explicit Tests headers found)