regulated-case-workbench release-control desk proof-oriented workflow

Show the release path, not just a beige description of it.

Regulated Case Workbench is a user-friendly flow for hard case operations: intake enters with context, evidence stays attached, redaction is previewed before release, approvals stay explicit, and export leaves with a signed manifest. This static front door is intentionally lightweight, but it should still feel like a real control surface with proof signals.

Open runtime brief Open summary pack See intake pack
Runtime contracts FastAPI routes make the release path inspectable over HTTP instead of hidden in slides.
Grounded review Reviewer claims only move forward after evidence, policy context, and redaction agree.
Delivery signal Static front door, Docker, CI, and Terraform scaffolding make the repo feel buildable, not decorative.
01

Case intake

Start with jurisdiction, domain, urgency, and missing evidence so the queue reads like a real desk.

02

Evidence review

Inspect linked evidence before trusting any narrative summary or release recommendation.

03

Redaction preview

See what leaves the system, what is masked, and where policy boundaries stay visible.

04

Approval gate

Reviewer ownership, policy disposition, and release status read as explicit workflow states.

05

Export handoff

Export only when preview, signature, and audit proof agree on the same release story.

What reviewers can verify

This repo is stronger when it reads like a release-control product, not a generic compliance page.

  • Case inbox, case detail, handoff brief, and reviewer assignment stay connected.
  • Grounded evidence review appears before policy or release claims.
  • Redaction preview and policy checks stay explicit before export.
  • Runtime scorecard, signature proof, and audit feed close the workflow.
Static on purpose: the public page is a lightweight front door, while the full FastAPI + browser workbench remains in-repo for local review.

Read + verify

Open the public runtime contracts that show the workflow behind this front door.

  • Runtime brief — review the strongest route map, workflow posture, and proof boundary.
  • Summary pack — inspect the strongest public proof bundle in one response.
  • Multimodal intake pack — inspect intake lanes, approval checkpoints, and release boundaries.
Local evidence path: run make verify, then open /api/runtime/brief, /api/runtime/scorecard, and /api/handoff-brief?case_id=case-1007. Public proof intentionally stays on live routes instead of private GitHub docs.