SCP-2614
Safe
~
medium confidence
SCP-2614
Expected annual
$883K
One-time setup
$286K
Annual recurring
$850K
Personnel
8
One-time setup and containment upgrades are moderate (~$286k) driven by room buildout, secure archival systems, and development of safe-handling tooling; annual operating costs are dominated by staff wages, ongoing research, and contingency/reserve budgets (~$850k/yr).
One-Time Capital Costs
Total: $286K
Annual Recurring Costs
Total: $850K/yr
Cost Scenarios
📊
Baseline
(baseline)
$850K/yr
Normal year with regular research activity, maintenance, and no major incidents.
scheduled sessions
routine maintenance
no incidents
🚨
Minor Incident
$900K/yr
Small unauthorized activation or brief staff exposure requiring overtime, short lockdown, and limited medical/forensic costs.
accidental activation
localized exposure
short containment response
🚨
Major Breach And Leak
$1.4M/yr
Unauthorized copy/large leak or major containment breach requiring extensive legal/PR intervention, large-scale remediation and use of reserves.
unauthorized publication/leak
large-scale exposure
court action/major PR campaign
🚨
Research Expansion
$1.1M/yr
Program decides to scale active mapping operations (more expeditions, higher storage, additional staff), increasing annual research spending.
funding approval for expanded mapping
continuous long-duration sessions
additional hires
Personnel
8 total
| Role | Count | Notes |
|---|---|---|
| Principal Investigator | 1 | [#11] Dr. Schmidt oversight; program allocation (salary portion included in staff_wages). |
| Research Assistant | 2 | [#12] Two RAs for observation, note-taking, and analysis (included in research staff budget). |
| Laboratory Technician | 1 | [#12] One technician for handling, cleaning, and equipment management (included in research staff budget). |
| Security Officer / MTF Agent | 4 | [#13] Four FTE-equivalents providing rotation coverage for monitoring during sessions (staffing cost included in staff_wages). |
Confidence Notes
Analyst notes provide detailed cost ranges for most line items and the object's Safe-class status reduces uncertainty, but anomalous and program-scale variables (research expansion, leak severity) introduce moderate uncertainty.