Conservation Accounting¶
Track conserved quantities across transformations so losses, leaks, substitutions, duplications, and hidden transfers become visible.
The Diagnostic Story¶
Symptom: Something that should be preserved is being transformed — converted, transferred, reformatted, reallocated — and at each step direct visibility into whether it actually survived diminishes. By the time a discrepancy surfaces, the transformation chain is long enough that finding the leak, duplication, or substitution is difficult. The system assumes conservation because the process was followed, not because conservation was verified.
Pivot: Define what must be conserved, set an accounting boundary, and record each transformation or transfer explicitly. Specify equivalence rules for different representations of the same quantity, then reconcile expected and observed states after each step so variance demands an explanation rather than being silently absorbed.
Resolution: Loss, leakage, substitution, and hidden transfer become visible as reconciliation failures rather than mysteries discovered long after the fact. The system can distinguish genuine transformation from unauthorized change, and provenance integrity is maintained across the full chain.
Reach for this when you hear…¶
[financial audit] “Cash went into the conversion process and a different amount came out — we need a reconciliation that shows exactly where the variance occurred, not just that it did.”
[supply chain] “We track inventory at intake and at shipment, but units are disappearing in the middle and nobody has a record of the intermediate movements.”
[data pipeline] “The row counts match downstream but three fields got silently coerced to null during the transform — if we had a conservation check we'd have caught that before it hit production.”
Mechanisms / Implementations¶
- Mass Balance (
mass_balance): As a method, this mechanism implements conservation accounting for material inputs, outputs, accumulation, waste, and residuals in physical processes. - Energy Accounting (
energy_accounting): As a method, this mechanism tracks energy inputs, conversions, losses, storage, and useful work across an energy boundary. - Financial Ledger (
financial_ledger): As a artifact, this mechanism records debits, credits, balances, transfers, and adjustments so monetary value can be reconciled. - Inventory Reconciliation (
inventory_reconciliation): As a procedure, this mechanism compares expected inventory records with observed stock, shipments, consumption, spoilage, and returns. - Chain-of-Custody Record (
chain_of_custody_record): As a document, this mechanism documents possession and transfer events so a conserved item, sample, artifact, or evidence object remains accounted for. - Data Lineage Map (
data_lineage_map): As a artifact, this mechanism shows how data elements move and transform across systems so records, fields, and derived values can be checked for loss or duplication. - Quota or Credit Ledger (
quota_or_credit_ledger): As a artifact, this mechanism tracks issuance, transfer, redemption, expiration, and retirement of credits, quotas, allowances, tokens, or entitlements. - Responsibility Accounting Matrix (
responsibility_accounting_matrix): As a template, this mechanism maps obligations, risks, or duties before and after delegation, reorganization, automation, or outsourcing. - Variance Report (
variance_report): As a document, this mechanism summarizes mismatches between expected and observed conserved quantities and records the explanation, escalation, or correction. - Chain-of-Custody Record
- Data Lineage Map
- Energy Accounting
- Financial Ledger
- Inventory Reconciliation
- Mass Balance: Applies conservation bookkeeping across a declared boundary so a hazard that 'disappears' from one channel must reappear as an outflow somewhere — and the unaccounted gap localises the leak.
- Quota or Credit Ledger
- Responsibility Accounting Matrix
- Variance Report
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (3)
- Conservation Laws: Quantities remain constant.
- Data Integrity: Accuracy and consistency preserved.
- Transaction: All-or-nothing operations.
Also references 8 related abstractions
- Access Control: Restrict system access.
- Accountability: Responsibility for actions.
- Boundary: Defines system limits.
- Closure: Ensures operations remain within a set.
- Equivalence Relation: Groups elements into equivalence classes.
- Invariance: Properties unchanged under transformation.
- Relation: Describes associations or dependencies.
- Transparency: Open processes.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Boundary Leakage Accounting · subtype · recognized
Accounts for conserved quantities that appear to vanish because hidden inputs, outputs, leaks, or externalities cross the assumed boundary.
Transformation Integrity Accounting · subtype · recognized
Checks that something remains accounted for when it changes form, representation, unit, denomination, or state.
Custody Conservation Accounting · domain variant · recognized
Accounts for a physical or digital item through handoffs so possession, identity, and transfer remain explainable.
Obligation Conservation Accounting · governance variant · candidate
Tracks responsibilities, risks, liabilities, or duties across delegation, outsourcing, reorganization, automation, or policy change.
Quota/Credit Conservation Accounting · domain variant · recognized
Tracks credits, allowances, quotas, tokens, or entitlements so issuance, transfer, redemption, and retirement do not create hidden duplicates or phantom balances.
Physical Balance Accounting · domain variant · recognized
Applies conservation accounting to material, energy, or physical-process flows within an explicitly defined boundary.