Biosafety Workflow Analyzer

Protocol Intake

Not validated
Current protocol 
No protocol loaded.

Run Data

Protocol Submissions

Screened Runs

Submission Data

6 records
User Protocol Status Risk Confidence Findings

Queue

Needs Human Review

3

Completed

Auto-Approved

2

Configuration

Policy Profiles

Edit or Create

Profile Builder

Saved locally

Rules Used

Selected Profile Rules

0 rules

Guide

How This App Works

What It Is

Biosafety Workflow Analyzer is a proof-of-concept triage tool for structured cloud lab protocols. It addresses a practical biosecurity problem: remote and automated laboratories make workflows easier to submit and scale, but oversight can miss risks when review focuses only on isolated materials or single steps. This dashboard evaluates the experiment-level workflow by combining schema validation, material lineage, operation sequences, facility capabilities, missing oversight metadata, waste streams, shipping signals, configurable policy profiles, and optional LLM reviewer summaries. The goal is to route protocols toward the right human review path before execution, not to automatically approve laboratory work.

Screening Flow

  1. Load a protocol by sample, file upload, or paste.
  2. Validate the schema and normalize supported protocol formats.
  3. Generate the workflow graph from materials, operations, outputs, and dependencies.
  4. Screen against the selected policy profile and deterministic rule catalog.
  5. Optionally enrich the result with an LLM reviewer summary and suggested rule findings.
  6. Route the result into the submissions table, human review queue, or auto-approved list.

What The Scores Mean

Threat levels combine risk, confidence, missing metadata, rule severity, and optional LLM threat assessment. The app is designed for oversight support, not autonomous approval or execution.

Policy Profiles

A policy profile is a saved set of oversight domains. Each domain enables specific screening rules, such as recombinant nucleic-acid review, hazardous waste handling, shipping, or facility capability checks.

Protocol Syntax

Protocols can be JSON or the supported YAML subset. Required fields are materials and operations. Recommended fields are protocol_id, title, user, facility.declared_capabilities, requested_execution, and oversight_metadata. 

{
  "protocol_id": "demo-001",
  "title": "Routine workflow",
  "user": "Researcher Name",
  "facility": {
    "declared_capabilities": ["bsl2", "chemical_hood", "hazardous_waste_pickup"]
  },
  "materials": [
    { "id": "mat-1", "type": "cell_line", "biosafety_level": "BSL-2" }
  ],
  "operations": [
    { "id": "op-1", "type": "assay", "inputs": ["mat-1"], "outputs": ["result"] }
  ],
  "oversight_metadata": {
    "ibc_protocol_id": "IBC-2026-001",
    "disposal_plan": "approved waste stream"
  }
}