# ADR 0006: Local Dashboard and Global Lastheard Are Separate

## Status
Proposed

## Context
Each server has its own live dashboard. The global lastheard service is centrally hosted and non-real-time.

## Decision
Local dashboard consumes local live feed; global lastheard consumes curated summaries via exporter/collector.

## Rationale
Local live visibility must survive central outages. Global aggregation should not add packet-process load or require the core to do database/export work.

## Consequences
A separate exporter process may be needed for global feeds. The broker handles fanout.

## Compatibility
Existing global lastheard behaviour should be migrated to consume summaries rather than packet-plane events.

## Testing Requirements
Tests should confirm local reporting works without global exporter connectivity and that exporter failure does not affect packet handling.