🧬 Flask Track Docs

Regulatory Primer for Non-Scientists

This primer explains how compliance works in Flask Track using clear, non-technical language.

You do not need a scientific background to understand the concepts in this document.

The goal is to explain:

What “Compliance” Means

In simple terms, compliance means:

Flask Track automates much of this process so compliance becomes part of normal laboratory work rather than a separate paperwork process.

Why Compliance Matters

Laboratories often work with materials and procedures that require:

Examples include:

Regulators, auditors, and organizations need proof that this work was performed safely and correctly.

Flask Track provides that proof automatically through operational tracking and immutable records.

How Flask Track Thinks About Compliance

Flask Track treats compliance as a live operational system.

The platform continuously:

  1. Classifies the work being performed
  2. Determines which rules apply
  3. Enforces those rules during execution
  4. Collects evidence automatically
  5. Records operational history permanently

This happens in real time while laboratory work is occurring.

Built-In Regulatory Knowledge

Flask Track ships with preloaded regulatory and compliance knowledge.

Examples include:

Organizations can customize or expand these systems as needed.

What Biosafety Levels Mean

Biosafety Levels (BSL) describe how carefully biological work must be handled.

Examples:

Level General Meaning
BSL-1 Minimal risk laboratory work
BSL-2 Moderate-risk biological work
BSL-3 Higher-risk controlled environments

Higher biosafety levels generally require:

Flask Track uses these classifications automatically during compliance evaluation.

GMO & Recombinant DNA Tracking

Some laboratory work involves:

These activities may require:

Flask Track automatically tracks these relationships using structured regulatory tags.

Policy Documents

Flask Track may include preloaded policy and governance documents.

Examples include:

These documents provide operational guidance and support audit readiness.

Policies may also be attached directly to workflows, checklists, or compliance systems.

Classification

Flask Track automatically classifies laboratory work using regulatory tags.

A regulatory tag is a structured label describing regulatory or safety relevance.

Examples include:

Tags may be attached to:

This allows the system to understand the regulatory meaning of laboratory work automatically.

Example Classification

An Agrobacterium transformation workflow may automatically be classified as:

No manual spreadsheet tracking is required.

The system derives this automatically from operational relationships.

Compliance Frameworks

Compliance frameworks define how rules are enforced.

Frameworks may represent:

Frameworks determine:

Frameworks convert classification into operational enforcement.

Compliance Checklists

Checklists are the operational tasks users must complete to remain compliant.

Examples include:

Checklists appear automatically when the system determines they apply.

Checklist Scope

Not every checklist applies to every workflow.

Flask Track evaluates operational context such as:

This allows the system to apply requirements only when relevant.

Authorization Rules

Some actions may require additional authorization.

Examples include:

Depending on configuration, Flask Track may:

These controls happen before or during execution.

Runtime Compliance Monitoring

Compliance is monitored continuously while work is occurring.

Examples include:

This reduces the risk of missing important compliance steps.

Evidence Collection

Flask Track collects operational evidence directly during execution.

Examples include:

Evidence remains permanently linked to the operational work it supports.

Compliance Events

Compliance Events record operational issues and incidents.

Examples include:

Events help organizations preserve operational reality rather than relying on memory or informal reporting.

Corrective Actions

When issues occur, organizations may document corrective actions such as:

Corrective actions remain linked to the original operational issue.

Audits

Audits are formal reviews of compliance status.

Audits evaluate:

Each audit records:

Audit records become permanent historical records.

The Audit Log

Every important action in Flask Track is recorded in the immutable audit log.

Examples include:

Audit log records typically include:

The audit log cannot be modified or deleted.

Why Immutability Matters

Historical integrity is critical for compliance and audit readiness.

Flask Track preserves:

This ensures organizations can always reconstruct what happened historically.

Nothing is silently overwritten or hidden.

API & Automation

Flask Track also supports compliance-aware APIs and automation systems.

Organizations may:

API activity follows the same authorization and audit rules as the main application.

End-to-End Traceability

One of Flask Track’s core goals is complete traceability.

The system connects:

This creates a continuous operational history across the full laboratory lifecycle.

Simple Example

A laboratory workflow involving:

may automatically trigger:

As users perform work, Flask Track records:

This creates an operationally complete compliance record automatically.

Summary

Flask Track embeds compliance directly into day-to-day laboratory operations.

Rather than treating compliance as separate paperwork, the system continuously:

The result is a laboratory platform where safety, quality, operational accountability, and audit readiness are built directly into how work is performed every day.