How to Preserve One Version of Truth Using 37 Systems and a Parrot
Preface, by the Archivist
The manuscript was found in Chamber Three, beside the assembly. It was bound in a material the Conservator has declined to name on the record. Its title page bore the inscription reproduced above. Its author has been identified, with the qualifications customary to claims of this kind, as Lucifer Gorgonzola Butt[1] — a name treated by the external scholarly literature as either an attribution, an editorial pseudonym, an act of self-effacement, or an early example of corporate doxxing of a deceased employee. The dispute is older than the manuscript, and the Bureau takes no position.
The manuscript is presented in the original numbering, in its original instructional register, with footnotes added by the expedition staff where intervention on behalf of subsequent readers was judged necessary. Voices are attributed at the foot of each note. Several steps are elided in the source; those omissions are not ours, and are flagged at the point of elision.
The Bureau formally recommends that this manuscript be regarded as an artifact rather than a guide. Several Systems on the recommended list remain in production. Several of their vendors retain counsel.
— the Archivist
The Manuscript
Step 1.
Acquire a System of Record.[2] This System shall hold the canonical version of every operationally significant entity in the enterprise. The System shall be selected on the basis of an analyst’s quadrant, a salesperson’s enthusiasm, and the executive sponsor’s previous employer.
Step 2.
Acquire a second System of Record. The second System shall hold a different canonical version of every operationally significant entity. The selection criteria for the second System shall be that the first System is, upon reflection, “not quite right for everything.”
Step 3.
Acquire a System of Engagement.[3] This System shall be marketed as customer-facing. Its definitions shall not match either of the first two Systems, by intention, on the grounds that customer-facing data has different requirements.
Step 4.
Acquire a Warehouse Management System. This shall be the third System to claim authoritative truth about Inventory, and the second System to claim authoritative truth about Customer.[4]
Step 5.
Acquire a Manufacturing Execution System. This shall be the fourth System to claim authoritative truth about Inventory; the second to claim authoritative truth about Part; and the first to claim authoritative truth about Work Order, which it shall jealously guard against the General Ledger’s later interpretation of the same noun.
Step 6.
Acquire a Customer Relationship Management System.[5] The CRM shall hold a definition of Customer that disagrees with all preceding definitions of Customer, with documented intent. The documented intent shall not be re-read after the third quarter following implementation.
Step 7.
Acquire a Business Intelligence platform. The BI platform’s purpose is to reconcile the preceding definitions into a single dashboard. The dashboard shall not match any of the preceding definitions. The discrepancy shall be reported as a modeling decision and shall not appear in any audit report.
Steps 8 through 13.
Acquire six additional Systems, in the following order: the General Ledger (Step 8), the billing engine (Step 9), the contract lifecycle platform (Step 10), the procurement suite (Step 11), the expense-management application (Step 12), and the treasury workstation (Step 13).
The documentation for the six Systems is preserved in Appendix A. Appendix A was misfiled in the procurement suite (Step 11) and could not be recovered for this edition.[6]
Step 14.
Acquire a parrot.[7]
The parrot shall be installed between Systems 9 and 10 — that is, between billing and contract lifecycle — where the throughput requirements exceed what the licensed ETL transport can accommodate during peak hours. The parrot’s responsibilities shall include the verbal recitation of seventeen field values, in order, from System 9’s output queue, to System 10’s intake clerk. The parrot shall be paid in seeds. The parrot’s accuracy, when audited, shall exceed that of System 11’s automated transformation layer by approximately four percent.
The parrot shall be named Gerald. The parrot is, for the purposes of all subsequent numbering, System 14.
Step 15.
Install Integration Platform-as-a-Service. The iPaaS shall provide adapters, transformers, and routing logic. The adapters shall not work without customization. The customizations shall not survive the iPaaS vendor’s annual update. The iPaaS subscription shall renew automatically.
Step 16.
Install a second Integration Platform-as-a-Service, on the grounds that the first iPaaS is “not quite right for everything.”
Steps 17 through 22.
These steps concern the appointment, training, salary banding, pension provisions, and ceremonial vesting of the Reconciliation Clerk and are not reproduced here for reasons of length. The Reconciliation Clerk’s role is described in the historical literature as “the person who knows where the discrepancies are buried.” The Reconciliation Clerk is to be promoted only upon retirement.
Step 23.
Construct the Reconciliation Assembly.
The Assembly shall occupy a chamber no smaller than eleven thousand square feet. Its purpose, according to the bronze plate affixed near the intake, shall be to update the customer’s address. Operation proceeds as follows.
A stylus shall record the new address onto a tablet. The tablet shall be conveyed by rail to a translation room, where it shall be rendered into a second tongue and pressed onto a second tablet, in accordance with the standing schema mapping from the Warehouse Management System (System 4) to the procurement suite (System 11). The second tablet shall be reviewed by a clerk forbidden by ritual to consult the first.
A discrepancy bell shall ring in approximately ninety-one percent of cases. The discrepancies shall be logged in a third tablet and forwarded to a chamber the expedition was never permitted to enter.
The second tablet, having been signed in red wax by an officer whose office has been vacant for two hundred years, shall be carried by Gerald[8] to an aqueduct, dropped into the aqueduct, retrieved downstream by a child, dried, filed, and entered into the billing engine (System 9), which is the System the next outgoing invoice shall consult, except in the case of statements over $10,000, in which case the invoice shall consult System 14.[9]
A fourth tablet, generated entirely separately, shall serve as the source of truth for the customer’s address in the marketing newsletter.
Step 24.
Affix the bronze plate.
Step 25.
Schedule the Quarterly Reconciliation.
The Quarterly Reconciliation shall identify the discrepancies the Reconciliation Assembly has not, in the preceding quarter, resolved. The Reconciliation shall produce a Discrepancy Register. The Discrepancy Register shall be distributed to the Reconciliation Clerk, who shall be the only party authorized to read it.
Step 26.
Schedule the Month-End Close.
The Month-End Close shall reconcile the General Ledger (System 8) to the Subsystems. The Subsystems shall not reconcile to the General Ledger. The variance shall be posted to a suspense account named, in the original tongue, the Account of Mortal Forgetting, and rendered in modern usage as Other Adjustments.
Steps 27 through 30.
These steps concern auditor briefings and are not reproduced here, as their content has been superseded by the operative version of the Sarbanes-Oxley liturgy.[10]
Step 31.
Engage a Systems Integrator.
The Integrator shall be paid by the hour. The Integrator shall produce a Future-State Architecture diagram in which the 37 Systems are replaced with the 37 Systems, configured slightly differently, and bracketed by a layer of new Systems whose function is to manage the existing Systems. The Future-State Architecture diagram shall be approved. Implementation shall begin. Implementation shall continue past the Integrator’s career.
Step 32.
Train the workforce.
Training shall consist of a four-hour module taken on the first day of employment, followed by the discovery, over the next three years, that the actual System operates differently from the System described in the training. The discovery shall be made by each employee independently, and shall not be entered into the knowledge base, the identification of which is discussed in footnote 10.
Step 33.
Establish the Shadow Systems.
The Shadow Systems shall arise spontaneously from the workforce’s accommodation to the 37 Systems and shall not appear on the architecture diagram. The Shadow Systems shall include not less than 412 spreadsheets, 47 Microsoft Access databases, 19 SharePoint lists, 6 Monday.com boards, a binder titled How We Actually Do It kept in the controller’s office, and a parrot.
Note: this parrot is not Gerald. This parrot has not been named, as a precaution.
Step 34.
File the Audit Report.
The Audit Report shall describe a System that does not, in production, exist anywhere. The Audit Report shall be approved. The Auditor shall be paid.
Step 35.
Renew the Annual Subscriptions.
The Subscriptions shall renew automatically. The Subscriptions shall not be reviewed, as the act of reviewing the Subscriptions would require coordinating across the parties responsible for each System, and no party with such authority exists.
Step 36.
Initiate the Replacement Project.
The Replacement Project shall be announced at the conclusion of the third year and shall propose to consolidate the 37 Systems into 14. The Replacement Project shall acquire 23 new Systems while retaining 31 of the original 37, on the grounds that several of the original Systems are “not quite right for everything but are too embedded to replace.”
The Replacement Project shall, upon completion, be celebrated as a Single Source of Truth.
Step 37.
Acquire a second parrot.
Joint Statement, on Filing
The undersigned were each asked, on completion of the recovery, to record what each thought ought to be recorded. The statements are reproduced in the order received.
The Cataloguer. The manuscript ends here. There is no Step 38, and no evidence of one having existed.
The Archivist. Every System enumerated above continues to be sold under the same name today, by the same vendors, to the same customers, who buy them in the same combinations and reconcile them, where they reconcile at all, through the same architecture. Whether the manuscript describes an ancient practice that survived to the present, or a present practice that was retroactively ancient-ified by someone who had grown tired of explaining it, cannot be determined. The two readings are operationally indistinguishable.
The Veterinary Consultant. Gerald, if alive, would be approximately two thousand years old. No parrot of this age has been produced for inspection. Gerald is presumed dead. Inquiries to that effect have been forwarded to System 14, which has not replied.
Counsel. The Bureau’s recommendation, on filing, was that the vaults be re-sealed and the inscription strengthened. The recommendation was acknowledged. The recommendation was not heeded. The vaults remain open. Counsel notes the foregoing in lieu of further comment.
The Archivist, again. There is, in the end, one observation the manuscript will not make and which the Bureau has elected to make on its behalf. The 37 Systems do not preserve one version of truth. They preserve thirty-seven versions of truth, plus the parrot’s. The dashboard reconciles to none of them.
The operational canon — the one authoritative, adjudicated record of how the business is actually operating — is a single thing or it is no thing at all. Anything else is the vaults still being open.
Filed May 2026. Companion essays for the curious: “The Operational Canon” (the doctrine implied here, stated plainly), “What the System Deserves” (the moral accounting of the three parties to the present arrangement), “The Bookkeeper’s Inheritance” (the architectural origin of the disease, told without the parrot).
A minority strand of the secondary literature reads the name as a corruption — Rube Goldberg having been an American newspaper cartoonist of the early twentieth century whose work depicted unnecessarily complex contrivances achieving banal results. The reading is etymologically suggestive and chronologically impossible, the manuscript predating Goldberg by a margin that has not been fully reconciled. The Translator takes no position. — the Translator ↩︎
The original term, in the language of the manuscript, has no settled translation. System of Record is the consensus reading. A minority reading would render it System of Vague Authority Whose Authority Is Routinely Overridden. — the Translator ↩︎
The distinction between a System of Record and a System of Engagement is the subject of a substantial secondary literature, none of which agrees with itself. The reader is advised to note the distinction and accept that two Systems will be acquired. — the Archivist ↩︎
No two Systems on the present list employ the same primary key for Customer. This is presented in the manuscript as a feature. — the Cataloguer ↩︎
One commentator has argued that the CRM is in fact the parrot from Step 14, and that the entire enterprise has been the long, slow re-discovery of this fact. The argument is unfashionable but has not been refuted. — the Translator ↩︎
Appendix A was misfiled inside the procurement suite documented at Step 11. Retrieval has not been attempted. — the Cataloguer ↩︎
The species is not specified. An African Gray would be most appropriate to the recitation task described in this step, but the species’ suitability for the additional duties enumerated in Step 23 has not been established. — the Veterinary Consultant ↩︎
The practicability of a parrot carrying a clay tablet of the weight implied by the dimensions given in this step has been formally questioned. The manuscript is explicit on the point. — the Veterinary Consultant ↩︎
That is: the parrot. — the Cataloguer ↩︎
The knowledge base referenced at Step 32 cannot be identified from the surviving text. The manuscript’s internal numbering would place it among the auditor-briefing Systems elided in Steps 27 through 30. The practice of housing knowledge bases under audit governance, and of ensuring they are not consulted by anyone in operations, is one Counsel declines to characterize further. — Counsel ↩︎