Evidence infrastructure — AESOP

Regulatory Mapping

Populate your organization’s approved regulatory templates with real pipeline evidence from AESOP, under a human review gate.

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 route: 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 it

1Upload
templates

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

2Run your
pipeline

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

3Open
Regulatory Mapping

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

Evidence mapping

AnalysisTemplate
Analysis

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

ControlHuman
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.

OutputCompleted
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

Template field	Evidence source — from AESOP
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

1Upload
templates

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

2Analyze
templates

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

3Review
mappings

Each field shows its name, location in the template, proposed AESOP source, and a confidence level (high / medium / low). Accept, reject, or reassign any field via dropdown. Signature and subjective fields are auto-tagged “Requires Human Input.”

4Generate
documents

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

5Review &
file

Preview the completed document inline, download as markdown, 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 the evidence that feeds your QMS.