Daily inventory and confirmed receipts
How much demand can the declared stock, confirmed receipts and daily service capacity cover?
Worked example
A municipal fuel depot can enter the diesel it can actually use, confirmed deliveries, expiry, and daily dispatch capacity. Check the first shortfall before assuming that a new shipment solves it.
The fictional depot starts with 100 barrels of diesel. On day one it can deliver 70 of the 90 barrels requested. With carryover enabled, the depot fills those remaining requests on day two. The two-day total is 130 barrels delivered, and day one still counts as a shortfall.
Try it yourself
The calculator opens with the fictional example already filled in. Change one input, choose Calculate locally, and compare the result to the original values below. Use Reset fictional fixture to start over.
An unknown result means the available inputs do not support a value. Check the calculator’s Warnings tab for what is missing or uncertain.
- New demand 130 barrels
- Demand served under stated constraints 130 barrels
- Closing stock 0 barrels
- Final carried backlog 0 barrels
- Demand still unserved at the end or lost 0 barrels
- Demand coverage 100 %
Import local JSON or CSV
Files stay in this browser. Maximum 1 MiB. JSON imports are recalculated. CSV supports flat observation tables, with column types taken from the displayed fixture. Empty cells become null.
Compare the arrangements
Keep physical resources and evaluation conditions equal. With identical inputs, all three approaches produce identical arithmetic. The comparison refuses material differences in declared conditions; it does not verify those declarations.
Privacy: comparison inputs may contain sensitive notes or operational details. Storage is off by default. Do not enter personal records or sensitive infrastructure details. Reproduction exports include supplied inputs and notes, including raw small-cell inputs suppressed from CORE-009 result tables. Suppression of displayed results does not make a reproduction export safe to publish.
Executive brief and reproducible export
Review for personal, confidential or sensitive material before saving or sharing. No automatic submission occurs.
Read the generated brief
Method, inputs and limits
Conserves a single physical stock over at most 365 declared daily periods. Offers, accepted commitments and physically received quantities remain separate. Method version 0.2.0. Establish delivery reliability, future demand, rights to resources, or a political or health outcome.
| Input | Unit / type | Required interpretation |
|---|---|---|
| initialStock — Opening physical stock | observations.unit / number | Use the supplied schema and declared units. Minimum 0. |
| initialOffers — Opening outstanding offers | observations.unit / number | Use the supplied schema and declared units. Minimum 0. |
| initialAccepted — Opening accepted but unreceived commitments | observations.unit / number | Use the supplied schema and declared units. Minimum 0. |
| days — Daily demand, offer, acceptance, receipt, expiry and capacity ledger | observations.unit / json | Each day requires day, unit, demand, offered, accepted, received, expired and capacity. Receipts arrive before service. Expiry is capped to stock available when it applies. |
| carryBacklog — Carry unmet demand to the next day | boolean / boolean | Use the supplied schema and declared units. |
| startDate — Calendar date of day one | ISO date / text | Optional YYYY-MM-DD date. All days follow consecutively. |
| expiryTiming — When expired stock becomes unavailable | timing / text | Use before_service or after_service. The default is after_service for previously saved inputs. |
Visible mathematics / decision rules
available = opening stock + received
served = min(available − before-service expiry, daily capacity, current demand + carried backlog)
expired = min(available, declared expiry) before service, or min(available − served, declared expiry) after service
closing stock = opening stock + received − expired − served
accepted outstanding = opening accepted + newly accepted − received
What this result cannot establish
- Bounded implementation from supplied acceptance checks and restored CORE definitions; scope choices are explicit below.
- A deterministic accounting exercise, not a forecast. All daily flows are amounts during the day, never rates.
- Expiry is supplied and applied at the chosen point in each day. Use before_service for lots already unusable when distribution starts. No lot age or expiry date is inferred.
- Accepted commitments may remain unreceived. Unaccepted offers never enter physical stock. Backlog has no automatic expiry.
- A spreadsheet using the same ledger gives the same result; MAR adds no arithmetic benefit.
What would falsify the assumptions?
- Assumptions fail if receipts, expiry, stock or demand omit a relevant flow.
- An independent physical count or signed receipt could contradict the closing stock.
- Every row must conserve physical stock and commitment balances.
- Reconcile the same ledger manually without AI.
- This is arithmetic on declared observations or a fictional exercise, never a causal estimate.
- MAR adds risk if its ledger diverges from verified receipts or a manual ledger; no benefit is established by matching arithmetic.
- Assumptions fail if the supplied definitions, units, period, scope or source records are wrong or incomplete.
- An independent source audit or replication may contradict an input or the recorded dependency.
- This method creates no resources. Physical conservation is checked in the inventory and transfer ledgers; descriptive graphs and checklists are not resource-flow models.
- The same equations and review checklist can be reproduced with a spreadsheet or structured human-only process.
- This is deterministic arithmetic, a descriptive comparison or a structured governance check, not a fitted causal effect or forecast. Fictional inputs remain an exercise.
- Equal or worse measured errors, net review effort, disclosure burden or fallback under MAR would show no added benefit or added risk; no improvement is assumed.
Reproducible fictional fixture and independently calculated expectations
This fixture is synthetic. It does not describe a country, government, company or event.
{
"observations": {
"unit": "barrels",
"origin": "synthetic",
"sources": [
{
"id": "SYN-001",
"kind": "synthetic",
"label": "Fictional demonstration A",
"url": null
}
],
"initialStock": 100,
"initialOffers": 0,
"initialAccepted": 0,
"days": [
{
"day": 1,
"unit": "barrels",
"demand": 90,
"offered": 20,
"accepted": 20,
"received": 20,
"expired": 0,
"capacity": 70
},
{
"day": 2,
"unit": "barrels",
"demand": 40,
"offered": 10,
"accepted": 10,
"received": 10,
"expired": 0,
"capacity": 100
}
],
"startDate": "2026-01-01"
},
"parameters": {
"carryBacklog": true,
"expiryTiming": "after_service"
}
}Expected checks
{
"totalServed": 130,
"closingStock": 0,
"finalBacklog": 0
}Download input fixtureAuthoritative background references
- U.S. GAO: Cost Estimating and Assessment Guide — Published 12 March 2020. Estimation and sensitivity guidance; no endorsement of this implementation. Reviewed 2026-11-09. Reference, not endorsement or validation.
These sources inform definitions or review practices. They do not validate this implementation or endorse MAR.