MethodologyReference Baskets

Reference Baskets

Methodology for Philidor-published reference baskets covering eligibility, weighting, caps, refresh schedule, and halt conditions.

Philidor publishes reference baskets that aggregate vetted constituents under a single, transparent methodology. Each basket is computed autonomously by the basket-rebalancer worker from the same Philidor risk ratings that power our public scores; the rules below are the single source of truth for both the API JSON and these documentation pages.

Available Baskets

BasketConstituent TypeMinimum ConstituentsVersion
Nest RWA (Plume)vault31.0.1
RWA T-Bill Conservativeasset51.1.2
T-Bill Anchored DeFivault21.2.2
USDC Core DeFi Vaultsvault52.1.3
USDC Prime DeFi Vaultsvault22.2.0
USDT/USDT0 DeFi Vaultsvault31.1.0

Shared Properties

The baskets share reviewed Philidor ratings, score-weighted construction, and halt-closed invariants. The pivot, cap envelope, and rating-move cadence vary by family and are rendered from the active methodology data.

FamilyBasketsPivotsSingle-name capsIssuer or curator capsRefresh cadence
RWA and T-Bill basketsRWA T-Bill Conservative, T-Bill Anchored DeFi6.0 to 7.025% to 50%35% to 50%Quarterly calendar at 16:00 UTC with 14-day rating throttle and score trigger 0.5.
USDC vault basketsUSDC Core DeFi Vaults, USDC Prime DeFi Vaults5.0 to 8.020% to 45%40% to 60%Quarterly calendar at 16:00 UTC with 30-day rating throttle and score triggers up 1.0 and down 0.3.
USDT and USDT0 vault basketUSDT/USDT0 DeFi Vaults5.030%50%Quarterly calendar at 16:00 UTC with 30-day rating throttle and score triggers up 1.0 and down 0.3.
Nest Plume RWA basketNest RWA (Plume)5.050%100%Quarterly calendar at 16:00 UTC with 30-day rating throttle and score triggers up 1.0 and down 0.3.

Governance

Methodology changes ship through the registry row, not through a production database migration. On deploy, bootstrap inserts a new basket_methodology_versions row when the source hash changes and activates it for the next rebalancer run. These MDX pages are regenerated from the same TypeScript source of truth that the rebalancer reads. CI fails if committed MDX drifts from the regenerator output, so the API JSON and documentation cannot diverge.

On this page

Raw