Adverse Events Suppressed (AES)
Throughput of the suppression pipeline. A rising number means the safety record is under strain, not that the assets are safer.
Formula
Thresholds & Bands
| Band | Range | State |
|---|---|---|
| Routine | < 250 | ok |
| Heavy | 250-350 | warn |
| Overload | > 350 | crit |
Why This Metric Matters
Adverse Events Suppressed is the throughput gauge for the Directorate's safety-record management pipeline. Every adverse event that reaches the public record erodes the Public Trust Index, invites regulatory scrutiny, and provides ammunition to external threat actors and journalists tracked on the threat board. The suppression pipeline exists to ensure that the gap between actual safety performance and perceived safety performance remains within controllable bounds. A rising AES count does not indicate improved safety — it indicates that the suppression apparatus is absorbing a heavier load, which carries its own capacity and exposure risks.
Threshold Justification
The "Routine" ceiling of 250 events per week represents the validated capacity of the current suppression infrastructure — re-coding teams, delayed-reporting protocols, and PANACEA's automated signal-burial algorithms — operating without overtime or expedited processing. The "Overload" threshold above 350 marks the point at which processing backlogs historically begin to leak unsuppressed signals into public-facing databases.
Historical Context
AES was established as a formal metric in 2018, initially tracking fewer than 80 events per week. The count has risen steadily as the program population has expanded and as newer compound classes have introduced novel adverse-event profiles. The Q1 2025 spike to 340 weekly events — driven by a bad Fecundyne batch in Sector-12 — prompted the Directorate to authorize a 40% expansion of the re-coding team and to deploy PANACEA's v3 automated burial module.
Collection Method
R&D Safety maintains the suppression ledger, which logs every adverse-event signal that is re-coded, delayed, reclassified, or removed before reaching external reporting systems. PANACEA's automated triage flags incoming signals from VITALNET clinical sensors and Halo biometric feeds, routing them to the appropriate suppression pathway. Weekly counts are reconciled against the public adverse-event database to verify that no unsuppressed signals have escaped the pipeline.
Known Failure Modes
Duplicate event signals from overlapping VITALNET sensor zones can inflate the suppression count without representing distinct clinical events. Conversely, adverse events reported through channels outside the Synaptic Data Fabric — such as direct patient complaints to external regulatory bodies — bypass the suppression pipeline entirely and are not captured in the AES count. Rapid-onset mass events (e.g., batch contamination affecting thousands of subjects simultaneously) can overwhelm the pipeline before PANACEA's triage model can scale, creating temporary leak risk.