Depeg Duration Resolver Changelog: v3 archive
Historical release evidence. Return to current versions and the complete history index.
What this controls
Depeg Duration Resolver Changelog: v3 archive version history
Use this changelog to trace how Pharos changed the related scoring, data-source, threshold, or interpretation rules over time. Entries record the contract active at each release; archived rules are retained so historical charts and citations can be read against the rules active at the time.
Primary references
Latest version
Rollout Coverage Boundary Review
DDRR now treats rollout-active incidents whose reliable recovery or terminal evidence predates the DDRv2 public prediction contract as pre-lock coverage outcomes instead of live missed-lock debt.
Impact snapshot
- Coverage classification for incidents already active when DDRv2 was enabled is floored at the DDRv2 public-contract effective timestamp
- Historical terminal evidence before that boundary becomes terminal_before_prediction, not missed_lock_terminal
- The reviewer engine advances to ddr-reviewer-v3 so cached review snapshots are rebuilt under the corrected public audit contract
v3.04Jun 29, 2026Rollout Coverage Boundary Review
DDRR now treats rollout-active incidents whose reliable recovery or terminal evidence predates the DDRv2 public prediction contract as pre-lock coverage outcomes instead of live missed-lock debt.
- Coverage classification for incidents already active when DDRv2 was enabled is floored at the DDRv2 public-contract effective timestamp
- Historical terminal evidence before that boundary becomes terminal_before_prediction, not missed_lock_terminal
- The reviewer engine advances to ddr-reviewer-v3 so cached review snapshots are rebuilt under the corrected public audit contract
DetailsHide details
Rollout Coverage Boundary Review
DDRR now treats rollout-active incidents whose reliable recovery or terminal evidence predates the DDRv2 public prediction contract as pre-lock coverage outcomes instead of live missed-lock debt.
- Coverage classification for incidents already active when DDRv2 was enabled is floored at the DDRv2 public-contract effective timestamp
- Historical terminal evidence before that boundary becomes terminal_before_prediction, not missed_lock_terminal
- The reviewer engine advances to ddr-reviewer-v3 so cached review snapshots are rebuilt under the corrected public audit contract
Impact notes
- Coverage classification for incidents already active when DDRv2 was enabled is floored at the DDRv2 public-contract effective timestamp
- Historical terminal evidence before that boundary becomes terminal_before_prediction, not missed_lock_terminal
- The reviewer engine advances to ddr-reviewer-v3 so cached review snapshots are rebuilt under the corrected public audit contract
v3.03Jun 29, 2026DDRR-Calibrated Stage 1 Terminality
Uses reviewed DDRR outcomes to calibrate Stage 1 terminality: recent compromised/unbacked mint incidents now feed K1, while static very-high reserve concentration becomes severe K2 only when paired with a severe below-peg fingerprint or observed dependency impairment.
- Recent registry-reviewed mint-authority incidents can make K1 supply weaponization fire even when daily supply history misses the mint path
- Very-high-risk reserve concentration is elevated by default and severe only with a severe/catastrophic below-peg break or a frozen/dead dependency
- Stage 2 duration remains on duration-landmark-v1 because the DDRR duration sample is still too small and clustered for a fitted retune
DetailsHide details
DDRR-Calibrated Stage 1 Terminality
Uses reviewed DDRR outcomes to calibrate Stage 1 terminality: recent compromised/unbacked mint incidents now feed K1, while static very-high reserve concentration becomes severe K2 only when paired with a severe below-peg fingerprint or observed dependency impairment.
- Recent registry-reviewed mint-authority incidents can make K1 supply weaponization fire even when daily supply history misses the mint path
- Very-high-risk reserve concentration is elevated by default and severe only with a severe/catastrophic below-peg break or a frozen/dead dependency
- Stage 2 duration remains on duration-landmark-v1 because the DDRR duration sample is still too small and clustered for a fitted retune
Impact notes
- Recent registry-reviewed mint-authority incidents can make K1 supply weaponization fire even when daily supply history misses the mint path
- Very-high-risk reserve concentration is elevated by default and severe only with a severe/catastrophic below-peg break or a frozen/dead dependency
- Stage 2 duration remains on duration-landmark-v1 because the DDRR duration sample is still too small and clustered for a fitted retune
v3.02Jun 19, 2026Close-gap Tail Grouping and Superseded Alias Review
DDR incident grouping now treats live reopens inside the documented close-gap merge window as the same canonical incident even when the original start is days old, and DDRR follows superseded duplicate aliases to the current source event.
- Sealed live tails can be adopted when they reopen within 6 hours of the prior current source event closing
- Duplicate sealed incidents can be superseded through append-only errata and lineage while downstream reads resolve to the canonical incident key
- DDRR evaluates repaired canonical predictions against the effective current source event instead of scoring an older closed fragment as recovered
- The APXUSD June 2026 duplicate prediction is invalidated and treated as an alias of the unresolved June 2 incident
DetailsHide details
Close-gap Tail Grouping and Superseded Alias Review
DDR incident grouping now treats live reopens inside the documented close-gap merge window as the same canonical incident even when the original start is days old, and DDRR follows superseded duplicate aliases to the current source event.
- Sealed live tails can be adopted when they reopen within 6 hours of the prior current source event closing
- Duplicate sealed incidents can be superseded through append-only errata and lineage while downstream reads resolve to the canonical incident key
- DDRR evaluates repaired canonical predictions against the effective current source event instead of scoring an older closed fragment as recovered
- The APXUSD June 2026 duplicate prediction is invalidated and treated as an alias of the unresolved June 2 incident
Impact notes
- Sealed live tails can be adopted when they reopen within 6 hours of the prior current source event closing
- Duplicate sealed incidents can be superseded through append-only errata and lineage while downstream reads resolve to the canonical incident key
- DDRR evaluates repaired canonical predictions against the effective current source event instead of scoring an older closed fragment as recovered
- The APXUSD June 2026 duplicate prediction is invalidated and treated as an alias of the unresolved June 2 incident
v3.01Jun 6, 2026Live Context Input Wiring
Wired Stage 1's documented live-context inputs into the Worker DDR precompute path.
- Uses fresh DEWS sub-signals to derive bank-run and blacklist-surge inputs for K5 and K3
- Uses the same 7-day DEX TVL baseline selection as the liquidity API for K5 exit-collapse checks
- Hydrates the latest Safety Score history row so R5 mean-reversion anchors and related context use live report-card data
- Marks DDR runs degraded when these required context-source queries fail instead of scoring with silently absent inputs
DetailsHide details
Live Context Input Wiring
Wired Stage 1's documented live-context inputs into the Worker DDR precompute path.
- Uses fresh DEWS sub-signals to derive bank-run and blacklist-surge inputs for K5 and K3
- Uses the same 7-day DEX TVL baseline selection as the liquidity API for K5 exit-collapse checks
- Hydrates the latest Safety Score history row so R5 mean-reversion anchors and related context use live report-card data
- Marks DDR runs degraded when these required context-source queries fail instead of scoring with silently absent inputs
Impact notes
- Uses fresh DEWS sub-signals to derive bank-run and blacklist-surge inputs for K5 and K3
- Uses the same 7-day DEX TVL baseline selection as the liquidity API for K5 exit-collapse checks
- Hydrates the latest Safety Score history row so R5 mean-reversion anchors and related context use live report-card data
- Marks DDR runs degraded when these required context-source queries fail instead of scoring with silently absent inputs
v3.0Jun 4, 2026Forecast Readiness Contract
Added the shared DDR forecast-readiness contract for readiness-gated locks with immutable public metadata.
- Introduces the readiness-72h-v1 forecast-readiness version and a strict early-lock threshold
- Publishes row-level readiness components and reasons as forecast readiness, not a probability or confidence label
- Adds optional/defaulted lock trigger, readiness, and 72h backstop metadata to the public contract while preserving legacy rows
- Includes new immutable readiness metadata in public row hash payloads when present
DetailsHide details
Forecast Readiness Contract
Added the shared DDR forecast-readiness contract for readiness-gated locks with immutable public metadata.
- Introduces the readiness-72h-v1 forecast-readiness version and a strict early-lock threshold
- Publishes row-level readiness components and reasons as forecast readiness, not a probability or confidence label
- Adds optional/defaulted lock trigger, readiness, and 72h backstop metadata to the public contract while preserving legacy rows
- Includes new immutable readiness metadata in public row hash payloads when present
Impact notes
- Introduces the readiness-72h-v1 forecast-readiness version and a strict early-lock threshold
- Publishes row-level readiness components and reasons as forecast readiness, not a probability or confidence label
- Adds optional/defaulted lock trigger, readiness, and 72h backstop metadata to the public contract while preserving legacy rows
- Includes new immutable readiness metadata in public row hash payloads when present