AESOP — Regulatory Mapping

The Concept

Regulated environments require documented evidence that AI systems do what they were specified to do. Most platforms generate regulatory documents from scratch. AESOP takes a different approach: you bring your own approved templates (ISO 13485 validation protocols, change control forms, risk registers, audit SOPs). AESOP reads them, identifies the fields that need data, maps them to evidence your pipeline already generated, and produces completed documents ready for QMS filing. AESOP is evidence infrastructure, not a regulatory authority.

How to Access

Upload Templates

Upload regulatory templates to the governance vault (Documents page). Tag them as Validation Protocol, Change Control, Risk Register, etc.

Run Your Evaluation Pipeline

Run your evaluation pipeline -- the data AESOP generates becomes the evidence source.

Open Regulatory Mapping

Open Regulatory Mapping from the project page or sidebar. Select templates, review field mappings, generate completed documents.

Evidence Mapping

Analysis

Template Analysis

The agent reads your template, identifies every fillable field (blank lines, placeholders, empty table cells), and maps each to an AESOP data source.

Control

Human Review Gate

Before any document is generated, you review every field mapping. Accept, reject, or reassign fields to different data sources. No auto-generation without your approval.

Output

Completed Documents

Generated documents preserve your template structure exactly. Evidence fields are populated with real data. Fields needing human judgment are marked with clear placeholders.

Data Sources

Intended use --> State Change Hypothesis (Build)

Test protocol --> Eval scenario library

Test evidence --> Certification report + scores

Risk identification --> Safety + Bias agent findings

Risk mitigation --> Repair cycle output

Residual risk --> Certification level (Platinum/Gold/Silver/Bronze)

Change description --> Version diff from Repair

Change rationale --> Repair change summary

Pre/post evidence --> Score delta across cycles

Monitoring plan --> Maintenance plan from Launch Package

The Process

Upload Templates

Upload your org's regulatory templates to the governance vault. Use specific doc types: Validation Protocol, Change Control, Risk Register, Audit SOP.

Analyze Templates

Select templates and click Analyze. The agent identifies fillable fields and proposes data source mappings. Results are cached -- analyzing the same template twice uses the cached result unless you click Re-analyze.

Review Mappings

Each field shows: name, location in template, proposed AESOP source, confidence level (high/medium/low). You can accept, reject, or reassign any field to a different source via dropdown. Fields requiring signatures or subjective decisions are auto-tagged as "Requires Human Input."

Generate Documents

Click Approve & Generate. The agent produces a completed document preserving your template structure. Fields with unavailable data (e.g., no repair cycle has run yet) show clear placeholders explaining what's missing.

Review & File

Preview the completed document inline, download as markdown, and mark as reviewed. Completed documents are stored in your governance vault tagged as regulatory outputs.

Regulatory Mapping does not certify agents for regulated use. That decision belongs to your quality team. AESOP produces evidence that feeds into your QMS.