Philidor Docs
Risk Framework

Platform & Strategy (40%)

Protocol and strategy resilience vector: maturity, audit depth, strategy complexity, dependency factors, and incident caps.

This vector measures the probability that protocol code or strategy design causes loss.

Formula

base_score = (lindy_score + audit_score + strategy_score) / 3
platform_score = base_score * worst_dependency_factor * count_discount

1) Lindy Score

Continuous maturity curve from deployment age.

lindy_score = 10 * (1 - e^(-days_live / 365))

Longer proven runtime raises score; very new deployments score lower.

2) Audit Score

Audit depth and diversity improve score; no audit is heavily penalized.

  • no audit: severe constraint
  • standard audit coverage: incremental uplift
  • broader independent review: stronger confidence

3) Strategy Score

Strategy complexity increases operational and technical risk.

Examples:

  • simple lending / isolated lending: high strategy score
  • multi-market routing / auto-compound: moderate
  • yield aggregation / leveraged / derivatives: lower

4) Dependency Factors (Worst-Of)

The platform score is bounded by its weakest dependency, not the product of all dependencies. The worst safety factor among all dependencies is applied, plus a small count discount for additional dependencies.

Safety factors by dependency tier:

  • Prime (score 8+): 0.95x (5% haircut)
  • Core (score 5-7.9): 0.80x (20% haircut)
  • Edge (score below 5): 0.50x (50% haircut)

Count discount: 3% per additional dependency beyond the first, with a floor of 0.85x.

5) Incident Decay Caps

Recent protocol incidents impose hard caps that relax over time. Caps are severity-aware:

Major incident (unresolved):

  • within 30 days: cap at 2
  • within 90 days: cap at 5
  • within 180 days: cap at 8

Major incident (resolved):

  • within 30 days: cap at 5
  • within 90 days: cap at 8

Minor incident:

  • within 30 days: cap at 8

Beyond these windows the penalty expires entirely.

6) Notes For v4.1

  • Asset methodology changed materially in v4.1.
  • Platform vector remains an active 40% component and still contributes materially to total score.
  • Final vault score can still be constrained by asset-quality drag and cap logic outside this vector.

On this page

Raw