Release 1 · The Acquired Book
Seven documents, one release
Design
Every Data Vault choice, argued: business keys, hashing, satellites per source, ghost records, inspectors and auditors, decisions D-1 to D-52.
ReadProduct definition
Mary's questions, the metrics they need, the open points settled, and the named releases.
ReadPost-implementation guide
What shipped, the evidence, and every difference from the plan, with why.
ReadQA certification
The QA cycle: preparation, the build, the tests, the comparisons, and the verdict on six gates.
ReadNext · What We Knew When, in QA
Four more documents
The design, test plan and implementation guide above are one set, worked as each release adds to them, so they now carry both releases.
Mart design
Mary's questions served from the conformed mart: its grains, its keys, and the meaning each measure carries.
ReadPost-implementation guide
What the next release shipped, the evidence, and every difference from the plan, with why.
ReadQA certification
The next release's QA cycle: preparation, the build, the tests and the verdict, filled in as it runs.
ReadCode review
The review of the next release's code: what was checked against data, each finding and where it stands.
ReadReading them
Kept as they are worked
The documents keep the team's working shorthand: decisions are numbered (D-1, D-2), questions are Q-numbered, and answers such as “1y” record who agreed what and when. Every claim points to its evidence.
Start with the design
Every Data Vault choice in this platform, argued and tied to its evidence.
Read the design