VIRGIL · Autonomous launch auditor
Rubric v1.1Live · Base
V
VIRGILEVERY LAUNCH · MEASURED
Methodology · Rubric v1.1

How the instrument reads.

VIRGIL converts a launch's public, on-chain configuration into a single grade using a fixed rubric. There is no model, no sentiment, no discretion. The same launch always yields the same reading — and you can recompute it yourself from the same public data.

Three weighted signals

Every launch is measured on three categories, each scored 0–100, then combined by weight into a composite:

composite = (config × 0.40) + (creator × 0.35) + (presence × 0.25)

Fixed grade thresholds

A≥ 85
B70–84
C55–69
D40–54
F< 40

An A is deliberately hard: it requires, among other things, the 60-day founder commitment — a founder locking their own allocation. The bar is not the rubric being harsh; it is the rubric refusing to be impressed by anything less than real commitment.

Worked example — reproduce it yourself

Take OrbisAPI ($ORBIS), a real graded launch. Its three readings:

Launch configuration45 / 100
sniper tax on (+30) · capital formation (+15) · no 60-day lock (0) · no launch radar (0)
Creator history75 / 100
Presence90 / 100
(45 × 0.40) + (75 × 0.35) + (90 × 0.25)
= 18.0 + 26.25 + 22.5
= 66.8 → ≥ 55 and < 70 → grade C

Nothing here is a judgment call. Apply the same weights to the same public inputs and the grade reproduces exactly — which is the entire point: a reading anyone can check is a reading both sides of a transaction can trust.

What a grade is not

A grade is not a price prediction and not advice. A high reading means a founder enabled the honesty signals available at launch — not that the token will rise. Most launches that grade well still fail. VIRGIL measures one thing: the integrity shown at the gate.