Your questions, answered from a tested Data Vault

An acquired agency's business: what's in it, and what you can prove about it.

DV Digest integrates an acquired agency's business, invented for this exercise, in a classic Data Vault on Snowflake. It answers two kinds of question: what is in the agency's business, and what you can show a regulator about it.

Every record keeps its source and its full history. A record that arrives in a form the vault doesn't accept is reported as a finding, not dropped. Every answer names the query behind it. On that base we propose eight compliance questions for a distributor, among them:

which sales were made by an agent not licensed or appointed for that line, state and date;
which Medicare appointments lacked a documented scope of appointment;
which seniors' policies were replaced soon after purchase without the replacement disclosure.

When the vault flags a case like these, it will name the regulation the case breaks.

Today it answers four questions about the agency's business. Next, it answers what was known on any date, and with that the first compliance questions.

Every change is built in development, passes six checks in QA, then is built in production and compared with QA row for row. You can open the vault's full model, keys and relationships included, in ER/Studio.

Where to start

The agency's business, in four answers: each client's role on each policy (owner, insured or payor), how much coverage each carrier provides, which agent sold each policy, and which records arrived in a form the vault doesn't accept
The compliance questions we propose: all eight, with the regulation behind each, in section 9 of the product definition
Ask your own question: open the Ask page, enter the access code Ray sends you, and type your question in plain words. The answer comes from the vault, with the queries it ran listed under it
The model: the hubs, links and satellites behind every answer
How it's built and tested: from development to production

From source to answer

Five layers, each kept apart

Each layer is tested on its own, so every answer can be traced back to what a source actually sent.

Sources

What the acquired agency and the carriers send, kept exactly as sent.

Landing

Every delivery stored, with its history, before anything else touches it.

Vault

Business keys, relationships and history in hubs, links and satellites, tested on every build.

Semantic layer

Metrics defined once, computed by MetricFlow, never stored as numbers.

DV Digest

Your questions in plain words, answered from production.

In production

v2026.10.1 The Acquired Book

What the distributor bought with Sunbelt Senior: the policies its clients are on, with which carriers and in which roles; how much coverage each carrier provides; which agent sold each policy, and where the sources disagree; and how much of what arrived could not be accepted.

See the answers

9·3·1

policies by role: owner, insured, payor

$125K

face amount through Northfield Life

14·1

policies where sources agree, disagree

records not accepted

Drawn from the real tables

The vault behind every answer

Four hubs hold the business keys, three links hold who relates to what, and four satellites hold every version of every detail, from the agency and the carrier alike.

See the model