Evidence Studio

Package reports into Markdown, PDF, JSON, share-link, executive, scheduled, and white-label artifacts

Evidence Studio

Evidence Studio upgrades /reports from a history browser into a branded artifact workspace. Each analysis history item becomes a package that can be reviewed, exported, shared, white-labeled, and scheduled for stakeholder follow-up.

Enterprise Evidence Rooms sit one layer above Evidence Studio. They can attach Evidence Studio artifacts while also packaging Code Genome, reform plans, policy simulation, deploy certification, billing proof, pilot status, Leadership Moat, and governance memory into one buyer-room contract.

Artifact Formats

  • Markdown: technical report for PRs, docs, implementation notes, and customer handoff.
  • PDF: print-ready report layout from the studio modal.
  • JSON: machine-readable evidence bundle with score, status, executive summary, evidence signals, white-label metadata, schedule plan, and source report.
  • Share link: deep link that opens the selected artifact in /reports?artifact=....
  • Executive summary: buyer-friendly interpretation of the report status and next action.
  • White-label kit: customer-safe brand slots, sanitization checklist, default client naming, and disclosure copy.
  • Scheduled delivery manifest: cadence, trigger, audience, and recipient guidance for weekly, monthly, or release-triggered delivery.

Status Rules

  • ready: strong score and no blocking evidence.
  • watch: usable internally, but needs review before external sharing.
  • blocked: low score, blocked readiness, failed validation, or critical security evidence.

The studio summary counts ready, watch, and blocked artifacts so operators can decide what is safe to send externally.

White-Label Guidance

White-label artifacts are intended to preserve evidence integrity while allowing agency or customer branding. Before sending externally:

  • remove internal workspace IDs, debug traces, provider metadata, and implementation-only notes;
  • replace source ownership language with the customer-safe project name;
  • keep score, evidence, and remediation findings intact;
  • add approval notes for blocked or watch-list findings.

Release Guardrails

  • Evidence package logic lives in lib/reports/evidence-studio.ts.
  • UI exports should consume the same artifact object, not build separate Markdown/JSON/PDF payloads.
  • Share links should remain deep links into /reports until public sharing permissions are added.
  • Scheduled delivery is a manifest in V5; actual email/automation delivery should be added with explicit permission, audit, and unsubscribe controls.