pbs step 5 FAILEDp.433 -- content and relationships, in the SOURCE — RuntimeError: `pbs`'s natural_key does not resolve to bare columns of `pbs_story_class`. …
edgar_docs step 5 FAILEDp.433 -- content and relationships, in the SOURCE — MemoryError: …
aapb step 5Now (2026-10-25 09:20, OWED): 113527 table(s) had two EQUALLY good provider surfaces offered and `aapb` declares nothing that separates them. …
What tripped it (2026-10-16 04:28): p.433 -- content and relationships, in the SOURCE — AttributeError: 'dict' object has no attribute 'lower'
… and 6 more.
The walk stops here: the next rank is not released until this is answered.
Band 1 — Extraction (Remote Sources → Local System) · book 450-451 (station) - 433, 436-437 (method) - 501 (hierarchies) · grain: one source per walk sheet
Most shops profile a sample and hope. Here, no source earns a row in the warehouse until its every value has been measured wall-to-wall — nulls, extremes, cardinality, key integrity — on instruments that can fail and say so. The flaws we find are named and written down, not discovered by Campers later.
The contract — what each step must produce
| # | step | page | what the book requires |
|---|---|---|---|
| 2 | IDENTIFY: the lane exists in the register | p.450-451 | "As soon as a candidate data source is identified, a light profiling assessment should be made" -- the trigger is IDENTIFICATION, not landing |
| 3 | LIGHT STRATEGIC ASSESSMENT (captures + shelf + cards) | p.450 | "a light profiling assessment ... to determine its suitability for inclusion in the data warehouse and provide an early go/no go decision" |
| 4 | REVIEWING RESULTS | p.450-451 | "provide an early go/no go decision ... Early disqualification of a data source is a responsible step" |
| 5 | TACTICAL PROFILE of a live provider sample | p.451, 502 | "a lengthy tactical data profiling effort should occur to squeeze out as many problems as possible" -- and p.502 states WHAT IT MUST CONTAIN: "Source… |
| 6 | MEASURE THE PROVIDER, NOT ITS DOCS | p.433 | "explore the actual content and relationships in the source system rather than relying on perhaps incomplete or outdated documentation" |
| 7 | THE FLAW LIST + THE CONVERSION BURDEN | p.433 | "verify the data exists in a usable state, or at least its flaws can be managed, and understand what it takes to convert it into the dimensional… |
| 8 | CANDIDATE FACTS: counts and amounts | p.437 | "identifies the counts and amounts generated by the measurement event's source system" |
| 9 | HIERARCHY VERDICT | p.501 | "investigate whether hierarchical relationships in the dimension data are perfectly clean ... either clean it up or acknowledge that it is not a… |
| 10 | THE DECLARATIONS -- the walk's real product | p.451 | "detailed specifications that are either 1) sent back to the originator ... or 2) form requirements for the data quality processing described in… |
| 11 | THE EXPECTATION NOTE TO BRAINTRUST STAFF | p.451 | "set the business sponsors' expectations regarding realistic development schedules, limitations in the source data, and the need to invest in better… |
| 12 | THE WALK IS REPEATABLE | p.436 | "Ongoing analyses of the source system and systematic data profiling during the design sessions" -- SS1 is not a one-time gate |
| 14 | THE LANDING (blocked until step 9's SIGN) | p.421 (Develop Physical Database Model, under the Physical Design heading on p.420) | "There are several additional sets of tables that need to be designed and deployed as part of the DW/BI system, including staging tables to support… |
