For Team

Partnership reviews

A "partnership review" is a standalone HTML page that summarizes a company we've evaluated. They live in static/ and are the largest body of content on the site (~125 files and counting).

What's in a review

Each file is a self-contained HTML page — open it in any browser and it works. Most follow a tab-navigation structure with sections like:

Style is consistent: white background, no dark mode, system font, max-width 1400px, callout cards with #f4f7fa background, tinted callouts with #e6effa. All CSS is inline; no frameworks.

Naming

CompanyName_PartnershipReview.html
CompanyName_PartnershipReview_YYYYMMDD.html

The date suffix is for when we've done multiple passes — CircleUSDC_PartnershipReview_20260224.html, Underdog_PartnershipReview.html (no date because it's the only one).

Other suffixes you'll see:

Finding one

Don't browse by filename. The intranet has three ways in:

  1. Company References app on the homepage — every review, grouped by company, with category filter pills (Payments, Stablecoins, Security & Audit, Credit Markets, Liquidity, Oracles, DEX, plus any custom ones).
  2. Laurelin — open a company. The "Links" section on the company detail page surfaces its review_link and any other documents we've attached.
  3. Direct URL if you have the filename: https://intra.valinorinfo.com/static/<filename>.

Categories

The category filter on the homepage and in Company References is driven by an array attached to each company in index.html (around line 520) — not by something you set per-review. So when you add a new review, you also add the company to the homepage list with the right categories array.

Common categories:

Category What it covers
Payments Payment processors, on/off ramps
Stablecoins Stablecoin issuers, USDC/USDT related
Security & Audit Auditors, security firms
Credit Markets Lending protocols, credit funds
Liquidity LPs, DEX aggregators
Oracles Price feeds, data oracles
DEX Decentralized exchanges

You can invent new categories — they appear as new filter pills automatically.

Adding a review

Two paths, both detailed in Add a partnership review:

Either way, push to GitHub main; within 5 minutes the deploy picks it up.

Updating an existing review

Two options:

  1. Edit in place — same filename, change the content, commit, push. The URL stays the same. Use this for typo fixes, small updates, links.
  2. New dated version<Company>_PartnershipReview_<NewDate>.html. Keeps the old one around for reference. Update the homepage entry to point to the new file. Use this for material updates after a new round of diligence.

Don't delete old versions unless the company explicitly asks (which has happened). Old reviews are useful for "what did we know when."