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.”
When This Archetype Applies¶
Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.
Diagnostic problem
A quantity expected to be preserved crosses transformations or boundaries whose opacity permits loss, leakage, duplication, substitution, or hidden transfer.
What this problem means
The structural problem is opaque transformation. A system moves, converts, aggregates, deletes, delegates, or relabels something while still claiming that the relevant value or quantity has been preserved. Because the form changed, ordinary inspection can no longer tell whether the thing survived, leaked, duplicated, or was substituted.
This produces common symptoms: unexplained variance, shrinkage, phantom balances, orphaned obligations, hidden waste, or records that appear correct locally but fail to reconcile globally. The central tension is that transformation is necessary, but transformation weakens visibility unless the account is built into the transformation path.
Show the applicability expression
Applicability expression2 distinct conditions
groundedpartly groundedopen
2 conditions, all required.
2Required in every casenumbered 1–2
These hold no matter which pattern applies.
Quantity preserved across transitions · open
A quantity is expected to remain present or equivalent across conversion, migration, handoff, consumption, storage, or reallocation.
This proposition-sized condition was conservatively reconstructed from the authored trigger_conditions, structural_problem fields; the source file was not modified. In this condition set, the requirement is: A quantity is expected to remain present or equivalent across conversion, migration, handoff, consumption, storage, or reallocation.
Boundary leakage risk · grounded
The quantity crosses a boundary at which it could leak or be externalized.
This proposition-sized condition was conservatively reconstructed from the authored trigger_conditions, structural_problem fields; the source file was not modified. In this condition set, the requirement is: The quantity crosses a boundary at which it could leak or be externalized.
Other requirements and context (4)
Why these sit outside the expression
Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.
Application gate — it governs whether applying the archetype is appropriate or material, rather than defining the structural problem itself.
Supporting contextPreservation depends on conversion among forms, units, formats, states, accounts, or responsibility structures.
This proposition-sized condition was conservatively reconstructed from the authored trigger_conditions, structural_problem fields; the source file was not modified. In this archetype, the relevant contextual consideration is: Preservation depends on conversion among forms, units, formats, states, accounts, or responsibility structures. It helps interpret the situation or strengthens the practical case for examining the archetype.
Application gateThe cost of unexplained loss, duplication, manipulation, or dispute is material.
This proposition-sized condition was conservatively reconstructed from the authored trigger_conditions, structural_problem fields; the source file was not modified. In this archetype, the relevant application gate is: The cost of unexplained loss, duplication, manipulation, or dispute is material. It narrows when choosing or applying the archetype is warranted or decision-relevant.
Supporting contextExpected and observed balances, counts, records, obligations, or flows disagree.
This proposition-sized condition was conservatively reconstructed from the authored trigger_conditions, structural_problem fields; the source file was not modified. In this archetype, the relevant contextual consideration is: Expected and observed balances, counts, records, obligations, or flows disagree. It helps interpret the situation or strengthens the practical case for examining the archetype.
Supporting context groundings
Expected and observed balances, counts, records, obligations, or flows disagree.
domainPhantom Inventory— Diagnose a fulfilment miss against a record showing healthy stock as an information-state failure — the record overstating reality between audits — that silently suppresses replenishment, pointing the fix at reconciliation cadence rather than the pick face.
Coverage
1 of 2 conditions grounded · 1 open.
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: Holds an artifact's identity intact through every handoff by logging who held it, when, and what they did — an unbroken, tamper-evident chain of possession.
- Data Lineage Map
- Energy Accounting: Tracks energy through every conversion across a defined boundary — input, useful work, storage, and losses — so that energy, conserved in quantity but degraded in quality, is fully accounted rather than assumed.
- Financial Ledger: Records every transaction as balanced debits and credits so monetary value is conserved on the books — each period's opening balance, flows, and closing balance reconcile by construction.
- Inventory Reconciliation: Periodically counts physical stock against the book record and resolves the difference, so shrinkage, miscount, and unrecorded movement surface as a measured, explained adjustment rather than a silent drift.
- 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: Tracks each credit, allowance, or entitlement from issuance through transfer to retirement so a unit is created once and used once — never double-counted, double-spent, or left phantom.
- Responsibility Accounting Matrix: Maps every duty, risk, and obligation from its old owner to a named new owner across a reorganization, so responsibility relocates rather than evaporating in the gap between roles.
- Variance Report: Summarizes each mismatch between expected and observed quantities, filters it by materiality, and routes it to an owner for explanation, escalation, or correction — turning a reconciliation gap into an accountable action.
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.
Editorial Notes¶
Problem Classification¶
Classification: Identity, Provenance & Integrity Failure → Conservation, Record Integrity & Reconciliation
Problem kernel: transformation can hide loss, duplication, or substitution
Rationale: Something meant to persist changes form, owner, location, or representation without conservation accounting across the full path.
Independent corroboration: The earliest necessary condition in the frozen evidence is: A system changes the form, location, ownership, representation, or state of something that should be preserved, but the transformation path is opaque enough that loss, leakage, duplication, substitution, or hidden transfer can go unnoticed. That is a conservation record integrity and reconciliation problem because Supposedly equivalent records, descendants, or transformations permit hidden loss, duplication, corruption, inheritance drift, or unresolved authoritative conflict.
Review outcome: Independent reviewer agreement; high confidence.