D4C Phase 2: Operator Daily Loop — Briefing → Replay → Evidence

[JH9384]

Goal

Extend the reuse-first D4C arc from fleet signal plumbing into the operator daily loop:

Briefing → Fleet Health → Top Signal → Replay → Recommendation/Outcome → Evidence Pack

This phase should make UAR useful as a daily operational console while continuing to avoid sprawl.

Completed initial slice

• Added backend composer:
  • uar/core/operator_daily_briefing.py
• Added backend tests:
  • tests/core/test_operator_daily_briefing.py
• Added dashboard briefing panel:
  • apps/web/src/components/mission-control/OperatorBriefingPanel.tsx
• Added Briefing tab to existing Dashboard.tsx
• Added replay handoff support:
  • ReplayExplorer initialRunId
• Added dashboard styles for briefing state and actions.

Reuse commitments

• Reuse /api/uar/mission-control as the briefing data source.
• Reuse fleet_summary.top_signal.linkage for replay/incident/recommendation context.
• Reuse existing Dashboard tabs instead of creating a separate daily console.
• Reuse Replay Explorer for run investigation.
• Reuse Evidence Pack v2 composer instead of creating a new report pipeline.

Acceptance criteria

• Briefing appears inside existing Dashboard shell.
• Briefing uses Mission Control data rather than a new store.
• Top fleet signal can open Replay tab with run filter.
• Briefing exposes incident IDs, recommendation IDs, and evidence refs.
• Evidence action routes to existing Artifacts tab.
• Add frontend tests for OperatorBriefingPanel.
• Add dashboard integration tests for Briefing → Replay tab handoff.
• Optionally expose operator_daily_briefing through a backend route if a real API consumer needs structured briefing JSON.

Anti-sprawl checklist

• No new dashboard app.
• No new briefing store.
• No new replay surface.
• No new incident workbench.
• No new evidence report pipeline.

Commits

• 170d334d21c77946a1a614877187b37cd5e12127 — add operator daily briefing composer
• cbafdf794e1c0168ca8351a6502c510bcf4bb16e — cover operator daily briefing composer
• c573b89674d75caaa24f28b34aa7dd320b95482e — add operator briefing dashboard panel
• f67e821af3f41eb8308d55daa106a6948b881bf2 — add briefing tab to dashboard
• f142b812352ca85db0cb7fb1ed35f9b501848b2d — allow replay explorer initial run filter
• 0bb3f1506030bf689fc15b6b7ca1cf3613f2069e — add operator briefing dashboard styles

[JH9384]

D4C Phase 2 Hardening — recommended tests added

Completed the recommended frontend hardening for the Operator Daily Loop.

Added OperatorBriefingPanel tests

File:

• apps/web/src/components/mission-control/OperatorBriefingPanel.test.tsx

Coverage:

• nominal briefing renders from Mission Control data
• critical top fleet signal renders in briefing
• replay button calls onOpenReplay(runId)
• incident IDs, recommendation IDs, and evidence refs are displayed
• Evidence button routes to artifacts

Commit:

• 5646533171ea0d41d64c8590ee2e2f42c8bc309c — cover operator briefing panel

Added Dashboard integration test

File:

• apps/web/src/components/Dashboard.test.tsx

Coverage:

• Dashboard starts on Briefing
• briefing replay action switches to Replay tab
• ReplayExplorer receives initialRunId and applies it as the run filter

Commit:

• 3df8b9cec22f46e8825ed2a33c4b0d2da0158ad7 — cover dashboard briefing replay handoff

Recommended local validation

Backend:

pytest tests/core/test_fleet_signals.py \
       tests/core/test_fleet_alerts.py \
       tests/core/test_fleet_linkage.py \
       tests/core/test_fleet_outcome_trust_movement.py \
       tests/core/test_fleet_evidence_section.py \
       tests/core/test_evidence_pack_v2.py \
       tests/core/test_operator_daily_briefing.py \
       tests/api/test_mission_control.py

Frontend:

cd apps/web
npm run test:run
npm run build

Remaining

No additional feature work is needed before local validation. Optional backend GET /api/uar/operator/briefing should wait until there is a real external API consumer.

[JH9384]

D4C Phase 2 Validation Support — repeatable script added

Added a focused validation script for the reuse-first fleet + operator loop.

File:

• scripts/validate_d4c_operator_loop.sh

What it runs:

1. Backend D4C regression slice:

   • fleet signals
   • fleet alerts
   • fleet linkage
   • fleet outcome/trust movement
   • fleet evidence section
   • Evidence Pack v2 composer
   • operator daily briefing
   • Mission Control fleet summary/linkage

2. Frontend D4C operator loop tests:

   • AlertBanner fleet surfacing
   • OperatorBriefingPanel
   • Dashboard Briefing → Replay handoff

3. Frontend production build:

   • npm run build

Commit:

• 87ddf81dec5f6e6a0dbd517815c48f70efbf8afd — add operator loop validation script

Run with:

bash scripts/validate_d4c_operator_loop.sh

This is validation support only; no new product surface area was added.

[JH9384]

D4C Phase 2 update: added a focused CI validation workflow.

File added: .github/workflows/d4c-operator-loop.yml

Commit: 2a9b91d0417259fd9ef90d25e6afdceae677cd53

The workflow validates the D4C operator loop by running the existing validation script on relevant pull requests, pushes to main, or manual dispatch.

It covers the backend D4C regression slice, the frontend operator-loop tests, and the frontend production build.

Local command remains:

bash scripts/validate_d4c_operator_loop.sh

No new product surface was added.

[JH9384]

D4C Phase 2 documentation update: added the operator loop validation gate doc.

File: docs/operations/D4C_OPERATOR_LOOP_VALIDATION.md

Commit: 84ac263c90f3d0b84b264cacf91c1c82a3abe344

It documents what the gate covers, how to run it locally, the CI workflow, anti-sprawl rules, and the next eligible work after the gate passes.

Recommended validation command remains:

bash scripts/validate_d4c_operator_loop.sh

Next eligible work after validation: outcome capture UI, Boring Mode, or Evidence Pack surfacing.

[JH9384]

D4C Phase 2 progress: Evidence Pack surfacing is now implemented in the existing Artifacts tab.

Completed:

• Added apps/web/src/utils/evidencePackPreview.ts
• Added apps/web/src/utils/evidencePackPreview.test.ts
• Updated apps/web/src/components/mission-control/ArtifactBrowser.tsx
• Added Evidence Pack v2 preview and copy-to-clipboard action
• Added apps/web/src/components/mission-control/ArtifactBrowser.test.tsx
• Updated scripts/validate_d4c_operator_loop.sh
• Updated .github/workflows/d4c-operator-loop.yml

Commits:

• 92d92fe4207eabfe98d1ecfef4f84bd6388d630d evidence preview utility
• d7899af2ab0d704af75192386b9e996892b7a34f evidence preview tests
• 1178fc255614dd4a661df829bdea28587616719f Artifacts tab preview
• d078fc4159c0775062f071648a17f3b4437d618b preview styling
• c5911a8ad12f615aa921431fe98a472d70b08b15 ArtifactBrowser tests
• 22f5cfa662fccd9afeab15eb1471845688f62fd6 validation script update
• 9add6f672463afe19fd6353a43493163433c2652 CI path filter update

Anti-sprawl status: clean. This reuses the existing Artifacts tab and run records. No new report endpoint, store, dashboard, or evidence pipeline was added.

Validation command:
bash scripts/validate_d4c_operator_loop.sh

[JH9384]

D4C Phase 2 progress: Outcome Capture UI is implemented in the existing Operator Briefing panel.

Completed:

• Added apps/web/src/components/mission-control/RecommendationOutcomeCapture.tsx
• Wired it into OperatorBriefingPanel.tsx
• Added RecommendationOutcomeCapture.test.tsx
• Updated OperatorBriefingPanel.test.tsx
• Updated scripts/validate_d4c_operator_loop.sh

Commits:

• b7933e440d5fbe554f6e0fbe935740a6c91fc609 outcome capture component
• d10608ea03d75eed046747f20274059cf8b0983b briefing integration
• 7cb9befaa9395c890ed6a339ca96fc66f4fa84ab component tests
• 2663895eaa94d69d36f5772f9128e7727cc094ab briefing tests
• e3fa2d39264b75b35ec6f45bf1b16bccb0478c48 validation script update

Anti-sprawl status: clean. This reuses /api/uar/recommendations/outcome and linked recommendation IDs from fleet_summary.top_signal.linkage. No new outcome table, endpoint, store, or fleet-specific trust score was added.

Validation command:
bash scripts/validate_d4c_operator_loop.sh

[JH9384]

D4C Phase 2 progress: Focus Mode is implemented as the simplified operator view inside the existing Dashboard.

Completed:

• Added apps/web/src/components/mission-control/FocusModePanel.tsx
• Added Focus tab to apps/web/src/components/Dashboard.tsx
• Added apps/web/src/components/mission-control/FocusModePanel.test.tsx
• Updated apps/web/src/components/Dashboard.test.tsx
• Updated scripts/validate_d4c_operator_loop.sh

Commits:

• 13d9929e239d07926cbe93adb1c33632223a6d17 focus mode panel
• 149d89e1bde54c3f21082d63df518cae1e97108e dashboard tab
• 8ba91004b4328f08bc2c188d6a7435ac2005cfd2 focus tests
• 31f4f3aa61a1a2d14be152b6ce4d5d579f4782c8 dashboard handoff tests
• 1b2c667ada1413c935cd6ea4a602ff81f0b7e586 validation script update

Anti-sprawl status: clean. Focus Mode reuses Mission Control, fleet linkage, ReplayExplorer handoff, Evidence tab routing, and RecommendationOutcomeCapture. No new dashboard app, store, endpoint, or workflow was added.

Validation command:
bash scripts/validate_d4c_operator_loop.sh