Six risks across every vault we score
vault_risk_dimensionsSIX RISKS, NOT ONE WORD, across every vault we score. A risk band is a weighted whole and a reader takes it as a summary of everything, which it is not: ours weighs drawdown, crowding, exit, concentration and consistency, and it contains NO reading of who may move the money. Two vaults read low while a multisig needing a single signature controlled them. So this groups what is already measured into market, liquidity, concentration and operating risk, ADDS the controller as its own dimension, and ADDS evidence — how much of the vault we could read at all. There is deliberately NO overall figure: a composite would be the number everybody quotes and nobody can check. THE FINDING IS FREE: population says how many scored vaults carry a band that reads BETTER than one of their own dimensions, and how many of those read worse on a dimension the band never contained — which is the number to read before trusting any one word on this platform. THE LIST IS PAID (dimensions.read): which vaults, with each one’s six levels, what it holds, and a sentence naming the disagreement. locked says when it is withheld, so an empty items is never mistaken for no matches — denominators.matchedTheFilter counts them either way. For ONE vault the whole table is FREE at vault_check, which also computes what else it could not see. Filter with dimension and level to run the screen that matters, e.g. the vaults whose controller reads high.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| level | No | The level to keep. With `dimension` it applies to that one; alone it keeps any vault reading this on ANY dimension, which is the fastest way to find everything that reads `severe` somewhere. | |
| limit | No | Rows to return, 1 to 200, default 50. The population figures are over EVERYTHING scored and never over the page. | |
| offset | No | Rows to skip, for walking a long list. `denominators.matchedTheFilter` is the total to walk. | |
| dimension | No | Keep only vaults with a READING on this dimension, and with `level` keep only those at that level. Without `level` it keeps every vault whose dimension read at all, which excludes the unread — an unread dimension is our coverage and never a level. | |
| disagreeing | No | Send `true` to keep only the vaults whose overall band reads BETTER than at least one of their own dimensions. This is the screen the dimensions exist for: it is where reading the single word would have misled you. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| asOf | No | When this was assembled. Each row carries its own `asOf`: the scores were taken at different moments, so this is a register of readings and not a snapshot. | |
| items | Yes | PAID. One row per vault: `slug`, `name`, `tvlUsd`, `band`, `levels` keyed by dimension, `coverage` with the component COUNTS behind the evidence dimension, `worseThanBand`, `outsideTheBand`, `says` and `asOf`. EMPTY where withheld, which `locked` states — never read an empty list here as no matches. | |
| limits | Yes | What this route does not do: nothing here is a new measurement, and its evidence dimension counts components only — `coverage.cannotSeeCount` is 0 for every vault and means NOT COMPUTED HERE, not "nothing was unreadable". The per-vault `vault_check` computes it properly and is free. | |
| locked | No | Null for a caller entitled to the list. Otherwise it names the capability, the number of free rows, and says plainly that the rest is withheld rather than absent. | |
| withheld | Yes | How many matching vaults are NOT in `items`. Zero for an entitled caller. For everybody else it is the difference between what matched and the free rows, so a short list is never mistaken for a short population. | |
| population | Yes | FREE. `scored` is the denominator, `disagreeing` how many carry a band better than one of their dimensions, `withARiskOutsideTheBand` how many read worse on a dimension the band does not contain, `byDimension` which dimension does it and how often, and `says` the finding in a sentence. Computed over everything scored, BEFORE any filter: a headline over a filtered set would be a headline about the filter. | |
| denominators | Yes | What every figure above is over: `openVaults`, `scored`, `neverScored` (named rather than left to subtraction, because a vault nobody scored must never read as one that scored well), `matchedTheFilter` and `returned`. |