Require archival and backup for anything in the Mother Brain warehouse that is not reconstructable from source
Situation
While Karl demoed the customer-journey view built on the data warehouse - 15 million events and growing, hosted on GCP - Peter asked how much of it is reconstructable if it is all destroyed. Karl said everything should be recreatable. Peter said he expects that is true and kept the instruction anyway: when Ian is slotted under Wallace, have Ian run archival and backup against anything that is not recreatable. He explicitly excused Karl from doing the work himself.
Reasoning
The value is the audit rather than the backup. Karl belief that everything is recreatable is untested, and the exercise of checking is what surfaces whatever is not - a set nobody can enumerate without looking. Peter kept a check whose stated purpose is weak precisely because its failure mode is informative. He also routed the work to Ian rather than adding it to Karl critical path, which gets it done without slowing the thing Karl is actually here to do.
Additional Context
Mother Brain and the journeys view were built by a contractor as personal-scale infrastructure and are now used by Peter, Bjorn and Lindsay. Karl is deciding Monday whether to extend his contract, which makes the window for capturing what only he knows a narrow one.
Observed Evidence
Direct quote from the Fathom transcript, including Peter keeping the instruction after Karl asserted everything should be recreatable.
Matching Patterns
Confidence Breakdown
Reasoning Depth Analysis
Related Context
fathom
Just from a data retention, disaster recovery perspective, this all gets destroyed. How much of this is reconstructable from the source data? And if the answer is not 100 percent, one of the first things you should do when you slot Ian under Wallace - you do not have to do this part, but just ask him to get archival and backup stuff running against anything here that is not recreatable. ... I expect that it is, but just anything that is not, have him go back up.
Outcome
No outcome recorded yet.
Decision ID: 0a87dd20-7e1b-4ece-9a1f-bdd879696975