Attribute catalog
An attribute snapshot holds a loan’s finished figures as data: attributes
for money and counts, ratios for coverage and margins. Both are keyed by the
names below. This page lists the full fixed vocabulary, 124 attributes
and 21 ratios, generated from the same registry the snapshots are built
from. If a name is here, you can key on it.
Names are stable. If a snapshot does not include a name, the loan’s documents
did not state that figure. Keys are never dropped from a period map, so a
missing year inside an attribute reads null instead of disappearing. Value
formats follow the value conventions: money is a 2-decimal
string, ratios and percents carry 4 decimals.
Two families are named after things an analyst typed, so they cannot be listed here. They are described at the end of this page.
Every entry has a label and a unit, plus a basis where one applies
(every value it can take is listed under Basis below). A label marked
(as the return words it) follows the filed return’s own wording for that
line. Where per-form wordings are listed, the label changes with the form. A
ratio whose basis reads Per snapshot takes its basis from the years in that
snapshot: book where the return states books, tax elsewhere, and mixed when
the filed years disagree.
Filed return, tax basis
Figures as they appear on the filed business return. Every name starts with tax_return_tax_ and every entry has basis: "tax".
Filed return, book basis
Book-basis figures read from the same returns, present only on years where the return states a book reconciliation. Every name starts with tax_return_book_ and every entry has basis: "book".
Filed return ratios
Ratios built from the filed returns. Each carries a basis that says which family its figures came from.
Company-prepared statements
Figures from company-prepared statements, agings and debt schedules, never from a return. Every name starts with company_reported_.
Basis
basis says what kind of source a figure came from. A money attribute carries
a basis only when it was read from a filed return. Figures from company-prepared
statements and analyst-built aggregates carry none; their name prefix
(company_reported_, custom_) says where they belong. A ratio always
carries a basis, and a ratio marked Per snapshot above resolves to
tax_return_book, tax_return_tax or mixed from the years in that
snapshot.
DSCR recipes
Every debt-service coverage recipe saved on a loan’s business produces one
ratio, named dscr_<slug>. The slug is the recipe’s own name, lowercased, with
each run of characters outside a-z0-9 collapsed to a single _, the edges
trimmed, and the result capped at 48 characters. Two recipes whose names produce
the same slug are suffixed _2, _3 and so on, in the order the loan holds
them.
The label is DSCR (<recipe name>), the unit is ratio, and the basis is
tax_return_book or tax_return_tax. These ratios appear in final and
draft snapshots, because a recipe is analyst judgment applied on every save.
They never appear in the documents-only machine snapshot.
inputs.dscr_configs names every recipe saved on the loan, whether or not it
produced a figure.
Analyst-built ratios and stats
A figure an analyst built and placed on the spread appears under
custom_<slug>. The slug is the analyst’s own name for it, lowercased, with
each run of characters outside a-z0-9 collapsed to a single _, the edges
trimmed, capped at 48 characters, and trimmed again after the cap, so a key
never ends in _. An empty result reads visual.
A slug is claimed once per snapshot across both groups, in definition-id order,
with repeats suffixed _2, _3 and so on. It is claimed whether or not the
figure produced a value, so a year gaining a figure never renames its
neighbour. A figure that divides one value by another goes in ratios with
basis: custom. One that does not is an aggregate money figure and goes in
attributes.
Each one carries custom_visual_id, the definition’s own opaque id, which
stays the same across renames. Key on the slug and you accept rename churn; key
on the id and you do not. These appear in final and draft snapshots and
never in the documents-only machine snapshot. What the analyst built the
figure out of never leaves the workspace.