Phase 181FAEDA-EVIDENCE-CORRECTION-CLOSURE-PACKET-DESIGN-001reporting dashboard design only

Evidence Review Reporting Dashboard Design

A privacy-safe reporting dashboard design for review health, closure health, stale evidence, reopen trends, reviewer load, escalation pressure, and founder visibility before any reporting API or analytics worker exists.

Closure packet Review queue Control Export policy

Dashboard panels

queue to founder

Metric definitions

future safe KPIs

Consumer views

role-scoped reporting

Runtime reports

no API or worker

Reporting panels

What a future dashboard may show

review-queue-healthFounder/Admin, QA Lead

Review queue health

Shows future counts by queue lane, decision lane, escalation tier, and SLA aging without exposing evidence content.

closure-healthFounder/Admin, QA Lead

Closure health

Shows closed, reopened, restricted-hold, invalid, and incident-escalated closure states from the closure packet contract.

stale-evidence-watchQA Lead, Developer Lead

Stale evidence watch

Highlights evidence or proof older than the allowed review window, especially stale mobile proof and old route checks.

reopen-trend-watchFounder/Admin, QA Lead, Developer Lead

Reopen trend watch

Groups reopen triggers such as route failures, hub link removal, unsafe wording returning, or runtime implementation beginning.

reviewer-loadQA Lead only

Reviewer load

Shows future assignment pressure, backup reviewer coverage, maker-checker conflicts, and overdue reviewer lanes.

privacy-riskSecurity, Data Protection

Privacy risk

Tracks restricted hold, redaction backlog, forbidden category blocks, incident quarantine, and privacy class drift.

route-readinessDeveloper Lead, QA Lead

Route readiness

Summarizes future route 200 checks, broken links, hub wiring gaps, OS map gaps, and stale route identity mismatches.

founder-safe-summaryFounder/Admin

Founder-safe summary

Gives the founder a redacted view: health, risk, blockers, and trends without raw screenshots, private data, or provider secrets.

Metric definitions

Future KPIs with safe sources and rules

Open review items

Source: Phase 179 queue item status

Count draft, assigned, in_review, escalated, reopened, and quarantined items.

SLA risk

Source: Phase 179 aging rules

Count items close to SLA due date without showing evidence content.

Escalation pressure

Source: Phase 179 escalation tiers

Count T2-T5 items by lane and privacy class.

Closure rate

Source: Phase 180 decision states

Count closed states divided by closeable correction packets.

Reopen rate

Source: Phase 180 reopen triggers

Count reopened items over closed items for a selected period.

Privacy hold count

Source: Phase 180 privacy class

Count restricted, forbidden, redaction, and incident lanes only in aggregate.

Route readiness count

Source: Phase 180 route check status

Count pass/fail/blocked route checks without dumping URLs beyond allowed route labels.

Build proof status

Source: Phase 180 build check status

Count not_run, pass, fail, blocked for training and main copies.

Mobile proof status

Source: Phase 180 mobile check status

Count mobile proof pass/fail without raw screenshots.

Hub wiring gaps

Source: Phase 180 missing hub wiring type

Count missing founder, demo, control room, readiness, and OS links.

Unsafe wording recurrence

Source: Phase 180 unsafe-copy issue type

Count repeat unsafe wording by module family, not by private reviewer note.

Maker-checker gaps

Source: Phase 179/180 maker checker refs

Count sensitive items missing independent checker approval.

Reviewer overload

Source: Future reviewer assignment refs

Count assigned items by reviewer alias, not personal profile.

Privacy filters

What reporting must hide by design

aggregate_only

Show counts, rates, and categories instead of raw evidence text.

route_label_only

Show route labels and approved route paths only.

reviewer_alias_only

Show reviewer aliases or roles, not personal profiles.

privacy_bucket_only

Show public-safe/internal/restricted/forbidden buckets, not private payloads.

no_raw_screenshots

Dashboard must not render raw screenshots or file previews.

no_provider_details

No bucket names, provider keys, signed URLs, payment references, or credentials.

Trend watchers

Patterns that should not stay hidden

Repeated unsafe copy

Trigger: Unsafe wording returns after closure.

Response: Create copy guardrail note and reopen affected packets.

Route regression

Trigger: Closed route starts failing route checks.

Response: Reopen route identity and hub wiring proof.

Reviewer bottleneck

Trigger: One reviewer owns too many stale items.

Response: Escalate to QA lead and assign backup reviewer later.

Privacy class drift

Trigger: Public-safe evidence becomes restricted or forbidden.

Response: Move to security/data protection view and block founder demo.

Reopen cluster

Trigger: Same module repeatedly reopens for the same reason.

Response: Create module-level correction review before further phase work.

Hub wiring misses

Trigger: New gates are not connected into OS/control/founder/demo paths.

Response: Block completion until the navigation surface is corrected.

Financial wording risk

Trigger: Wallet, payout, COD, settlement, or partner rail wording becomes unsafe.

Response: Escalate to finance/compliance wording review.

datetime

Future report generation timestamp.

reviewedAt

datetime|null

Future manual review timestamp.

Hard rules

Reporting dashboard is not analytics implementation

Phase 181 is reporting dashboard design only.

Do not create analytics APIs, reporting APIs, dashboard backends, database tables, materialized views, scheduled jobs, queues, workers, exports, CSVs, PDFs, or notifications here.

Do not render raw screenshots, private evidence content, CNIC, OTP, wallet PIN, bank detail, provider secret, payment credential, customer transcript, or production credential.

Dashboard metrics must be aggregate, privacy-filtered, and consumer-scoped.

Founder visibility is redacted visibility; it is not unrestricted evidence access.

Exports remain blocked until a separate reporting export policy gate exists.

Reporting packet

JSON preview

{
  "reportingDashboardId": "evidence_review_reporting_dashboard_design_181",
  "phase": "Phase 181",
  "route": "/business-pro/evidence-review-reporting-dashboard-design",
  "sourceReviewQueue": "evidence_review_queue_workflow_design_179",
  "sourceClosurePacket": "evidence_correction_closure_packet_design_180",
  "sourceGates": [
    "FAEDA-EVIDENCE-REVIEW-QUEUE-WORKFLOW-DESIGN-001",
    "FAEDA-EVIDENCE-CORRECTION-CLOSURE-PACKET-DESIGN-001"
  ],
  "designOnly": true,
  "createsReportingApi": false,
  "createsAnalyticsWorker": false,
  "createsDatabase": false,
  "createsMaterializedView": false,
  "createsExport": false,
  "createsNotification": false,
  "queueLanes": [
    "intake-triage",
    "security-review",
    "redaction-review",
    "maker-checker-review",
    "correction-loop",
    "demo-safe-review",
    "incident-quarantine"
  ],
  "reviewDecisionLanes": [
    "approve_internal",
    "approve_demo_safe",
    "needs_correction",
    "needs_redaction",
    "restricted_hold",
    "reject_duplicate",
    "reject_invalid",
    "quarantine_incident"
  ],
  "escalationTiers": [
    "T1",
    "T2",
    "T3",
    "T4",
    "T5"
  ],
  "closureDecisionStates": [
    "closed_demo_safe",
    "closed_internal_only",
    "closed_restricted_hold",
    "closed_rejected_invalid",
    "reopened_regression",
    "superseded_by_new_evidence",
    "escalated_incident"
  ],
  "reopenTriggers": [
    "Route returns non-200",
    "Hub link removed",
    "Unsafe wording returns",
    "Privacy class changes",
    "New evidence contradicts closure",
    "Runtime implementation begins",
    "Maker-checker conflict found"
  ],
  "verificationChecks": [
    "Fix matches original issue",
    "Route compiles and responds",
    "Hub links are connected",
    "No runtime authority added",
    "Privacy class preserved",
    "Proof is current",
    "Role scope is correct",
    "No fake finance claim",
    "No hidden inventory claim",
    "Acceptance condition satisfied"
  ],
  "dashboardPanels": [
    "review-queue-health",
    "closure-health",
    "stale-evidence-watch",
    "reopen-trend-watch",
    "reviewer-load",
    "privacy-risk",
    "route-readiness",
    "founder-safe-summary"
  ],
  "metricDefinitions": [
    "Open review items",
    "SLA risk",
    "Escalation pressure",
    "Closure rate",
    "Reopen rate",
    "Privacy hold count",
    "Route readiness count",
    "Build proof status",
    "Mobile proof status",
    "Hub wiring gaps",
    "Unsafe wording recurrence",
    "Maker-checker gaps",
    "Reviewer overload",
    "Founder blockers"
  ],
  "consumerViews": [
    "Founder/Admin",
    "QA Lead",
    "Security",
    "Data Protection",
    "Developer Lead",
    "Demo Lead"
  ],
  "privacyFilters": [
    "aggregate_only",
    "route_label_only",
    "reviewer_alias_only",
    "privacy_bucket_only",
    "no_raw_screenshots",
    "no_provider_details"
  ],
  "recordFields": [
    "reportViewId",
    "sourceQueueWorkflowId",
    "sourceClosurePacketId",
    "consumerRole",
    "metricKey",
    "metricScope",
    "aggregationWindow",
    "privacyFilter",
    "displayValue",
    "trendDirection",
    "riskLevel",
    "redactionStatus",
    "sourceDecisionStates",
    "sourceReopenTriggers",
    "safeNarrative",
    "drilldownAllowed",
    "exportAllowed",
    "generatedAt",
    "reviewedAt"
  ],
  "nextAllowedGate": "phase_182_evidence_reporting_export_policy_design"
}

Next build gate

Phase 182 is evidence reporting export policy design

After reporting visibility is designed, the next safe move is export policy: who may export, what is redacted, and which formats stay blocked.

Open export policy