---
title: "Depeg Duration Resolver Changelog"
canonical: "https://pharos.watch/methodology/depeg-resolver-changelog/archive/v1/"
description: "Depeg Duration Resolver Changelog - Pharos methodology version history."
---
# Depeg Duration Resolver Changelog
[All versions](https://pharos.watch/methodology/depeg-resolver-changelog/)
## v1.1 - Depeg Duration Resolver Reviewer
**Effective:** 2026-05-25
Added the Depeg Duration Resolver Reviewer (DDRR), the audit layer that scores stored DDR assessments against later canonical depeg-event outcomes.
- Stores quarter-hourly DDR assessment checkpoints and reviews the first checkpoint for each event under the current methodology
- Publishes recovery-likelihood accuracy and average observed-minus-DDR recovery-duration error on /depeg/ and GET /api/depeg-resolver-review
- Keeps pending, insufficient-signal, and data-issue rows visible while excluding them from scored headline accuracy
- Removes terminal-lifecycle assets from live DDR readouts while DDRR scores their stored predictions as terminal outcomes
Origin: Contemporaneous release record
Commits: Commit provenance not recorded
## v1.0 - Initial Depeg Duration Resolver
**Effective:** 2026-05-25
Launched the two-stage Depeg Duration Resolver: a mechanistic Resolution Outlook (terminal vs recoverable) and a stratified empirical duration estimate over recovered historical incidents.
- Stage 1 emits an ordinal verdict (recovery_likely / at_risk / recovery_unlikely / insufficient_signal) from kill signals and recovery anchors over structural metadata and the live depeg fingerprint
- Stage 2 emits a depth/direction/structural-class stratified landmark estimate with per-horizon (6h/24h/7d/30d) resolution likelihood, support-gated and Wilson-bounded
- Verdicts are calibrated domain reads, not fitted probabilities; audit-verdict gating is not used because event provenance is unpopulated
Origin: Contemporaneous release record
Commits: Commit provenance not recorded