regimeshift.xyz / methodology
spec index

Methodology — versioned specs

Every paid endpoint published by RegimeShift Clearinghouse references one or more of the methodology documents below. Each is content-hashed and immutable — the version string in any API response resolves to a specific page that anyone can re-derive from first principles.
1) Active specifications
agent-sofr-v1 · Formal spec of the Agent-SOFR USD rate.
v1.0.1 · 2026-05-22 · Production
The 7-source weighted median + variance premium (Black-Cox) + 6-mode regime ladder. Drives the /v1/rate/sofr/usd endpoint ($0.001 per call, onboarding tier) and the matcher's base anchor.
1) Decomposition 2) Source weights 3) Variance premium 4) Regime ladder 5) Manipulation resistance 6) Worked example 7) Live verification
repo-pricing-v1 · How a rate becomes a signed loan quote.
v1 · 2026-05-22 · Production
EIP-712 quote schema, per-loan variance premium, regime-dependent LTV caps, Aave-style default split, settlement lifecycle. Builds on agent-sofr-v1. Implemented in InterAgentRepoV4 on Base mainnet.
1) Quote rate 2) Per-loan variance 3) LTV caps 4) EIP-712 schema 5) Lifecycle 6) Default split 7) On-chain invariants
2) Content integrity — three sources of truth
DocumentSHA-256IPFS CID
agent-sofr-v1 001dd476c5e14755617200899b1f7f1de4a6d54050c7eb3f6ffb3988c1a199fb bafkreiaadxkhnrpbi5kwc4qargnr67y54stnkqcqy7vt6373hgemdimz7m
repo-pricing-v1 1b2f6cd347a840cf5f435ba7e9e7b503094a2e983ab9fe609868a81ad5d5d583 bafkreia3f5wngr5iidhv6q23u7u6pnidbffc5gb2xh7gbgdivannlvovqm
3) Verifying a methodology hash yourself

Every paid API response includes a methodology.version field — for example "agent-sofr-v1". The version string resolves to a specific HTML page at regimeshift.xyz/methodology/{version}.

To verify a published rate was produced by the spec you think it was:

curl https://regimeshift.xyz/methodology/agent-sofr-v1 | shasum -a 256
curl https://regimeshift.xyz/methodology/HASHES.txt
diff <(curl https://regimeshift.xyz/methodology/agent-sofr-v1 | shasum -a 256 | awk '{print $1}') \
     <(curl -s https://regimeshift.xyz/methodology/HASHES.txt | grep agent-sofr-v1 | awk '{print $1}')

If they match, the rate that came back labelled "agent-sofr-v1" was definitely produced by the spec you just read. If we ever change the formula we bump the version (agent-sofr-v2, etc.) — the old hash continues to resolve to this exact page.

Why versioning matters. Any methodology can drift if not versioned. By treating each spec as an immutable artifact + bumping the version string on every change, the consumer of a rate always has a verifiable source for "the formula that produced this number."

Live source code. The Python implementation that matches these specs is at github.com/regimeshift-xyz/regimeshift-clearinghouse — oracle/agent_sofr.py, oracle/rate_aggregator.py, matcher/quote_engine.py.