Competitive Intelligence
decisions/2026-06-26-ci-dashboard-ia.md
ADR: CI Dashboard Information Architecture
Date: 2026-06-26 Status: Accepted
Context
The CI dashboard must become an operator console and decision surface, not a pretty archive. It should help Arijit and future stakeholders answer: what happened, how reliable is it, what should be done, who owns it, and what changed since prior reports.
Decision
Build the CI dashboard as a private-tunnel-first product with six v1 views.
V1 Views
| View | Purpose |
|---|---|
| Today | Latest daily pulse, current bottom line, top action, and source-health warning. |
| Weekly | Latest weekly digest, patterns, owner actions, and battlecard update candidates. |
| Sources | Source health by competitor, source type, priority, cadence, status, and failure streak. |
| Signals | Searchable/filterable signal ledger by competitor, category, owner, score, date, and source type. |
| Actions | Track proposed, accepted, assigned, completed, and rejected recommendations. |
| Archive | Daily and weekly reports with Markdown, HTML, PDF, quality score, and delivery status. |
Access Model
V1 is private tunnel only for Arijit. Stakeholder mode is explicitly deferred until:
- Authentication exists.
- Report claims pass evidence gates.
- Export controls exist.
- Athena review status exists.
- The system avoids Algolia-confidential leakage by design.
Visual Story
Use the official Algolia design system for Algolia-specific CI artifacts and dashboard styling. The UI should feel like an operational intelligence console: dense, scannable, restrained, evidence-forward, and suitable for repeated daily use.