5 min read

Project dashboard

The project dashboard surfaces three signals for every project: the Gate Verdict for the most recent sync run, the Drift Pressure Index (DPI), and the Near-Miss Ledger. This page explains what each one shows, how to read it, and what to do with it.

Gate Verdict

The verdict panel replaces the old pass/fail badge with a decomposed, auditable record of what the gate engine produced on this sync run. Selecting any completed or blocked sync run populates the panel.

• Lane badge -- ERR, WARN, INFO, or PASS. ERR always blocks; WARN blocks only if the count meets your configured threshold; INFO and PASS never block.
• Decomposed score -- the composite 0-100 breaking score broken out per finding, so you can see which item drove the total.
• Confidence band -- a low-high range with a basis label (for example 47-58 (closure-phase spread)) that shows how tight the evaluator agreement was. Narrow bands are high-confidence verdicts; wide bands mean reviewers should look more carefully.
• Reason codes -- one line per finding, naming the change kind, endpoint, field, and a human-readable explanation.
• Corpus citation -- every verdict ships with a pointer to the corpus evidence used to classify it. The citation links to the specific diff pattern in the classification reference.

Drift Pressure Index (DPI)

DPI is a single 0-1 number that summarises the latent drift risk on a project, independent of whether the most recent sync blocked. Two projects can both be passing today and still have very different DPI scores -- DPI captures the trajectory, not the verdict.

Formula

The current DPI score is a weighted blend of three signals:

DPI = 0.4 x near_miss_rate
    + 0.35 x drift_velocity
    + 0.25 x ood_novelty

• Near-miss rate -- blocked-then-passed sync runs over the last 30 days. Each near miss is evidence that your spec grazed a gate block.
• Drift velocity -- the slope of the breaking-score trend line across recent completed syncs. Positive velocity means you are moving toward a block.
• OOD novelty -- how unusual the current IR shape is versus the corpus, using the OOD spec detector. New API styles warrant extra caution.

Color coding

Interpretation: DPI reflects latent drift risk even when no block is active. A red DPI on a project that has not blocked yet means you are one or two commits away from the gate engaging -- an advance warning, not a verdict.

Empty state:a new project with fewer than three syncs has insufficient history to compute DPI. The gauge shows “No drift data yet” until enough history accrues.

Near-Miss Ledger

Every gate block is recorded as a near-miss entry. The ledger is the project’s institutional memory: a permanent, exportable record of every change that would have shipped a breaking API if the gate had not caught it.

What is recorded

• Date of the block
• Lane (ERR / WARN)
• Finding kinds that fired on the block
• Blast radius -- the number of SDK methods downstream of the affected endpoint
• Resolution -- whether the author fixed the spec, opened a drift exception, or abandoned the change

CSV export

Click Export CSVin the ledger panel to download every entry. The export is useful for budget-defense conversations -- “three blocks on GET /usersin 30 days means X SDK methods at risk” -- and for compliance audits that need proof of enforcement.

Empty state

A project with no gate blocks shows “No gate blocks yet -- drift protection is working.” That is the healthy state. The ledger is deliberately absent of informational noise; only real blocks are recorded.

When to act on each signal