Civilian Mutual-Aid Resource Ledger
What reciprocal balance, local reserve gap, and unmet need follow from recorded receipts and consent-gated pending allocations?
Worked example
Civilian partners can record who supplies staff time, funds and delivered goods. Compare each participant in native units and document whether it can withdraw safely.
In the fictional staff-sharing exercise, participants record 15 staff-hours as received and still need 25 more. Another 5 staff-hours may be allocated in the scenario. They remain separate from work already received.
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.
- Initial resources across participants 120 staff-hours
- Recorded receipts (not offers) 15 staff-hours
- Total requirement gap at recorded resource balances 25 staff-hours
- Total local reserve gap at recorded resource balances 0 staff-hours
- Pending allocation with declared participant consent 5 staff-hours
- Conditional allocation scenario unmet need 20 staff-hours
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
Accounts for declared participant resources, local minimums, needs, and distinct authorized, accepted, allocated, and received assistance. Method version 0.2.0. Cannot authorize assistance, choose an allocation, determine geopolitical merit, predict delivery, or convert an offer into a receipt.
| Input | Unit / type | Required interpretation |
|---|---|---|
| participants — Participant resources, local minimums, needs, offers, and consent | records / json | All quantities share one explicit unit. requiredNeed is the total participant requirement, not additional aid demand. |
| transfers — Authorized, accepted, allocated, and physically received assistance | records / json | Record each state separately. received ≤ allocated ≤ accepted ≤ authorized. Pending allocations require both parties’ consent. The scenario requires each sender to have enough recorded resources before counting pending incoming aid. |
| comparison — Optional declared alternatives for shared CORE-008 Pareto comparison | separate declared dimensions / json | Supply dimensions and alternatives using CORE-008 schemas. Optional comparison parameters may include explicit weights and normalization; none are invented. |
Visible mathematics / decision rules
observed remaining(i) = resources(i) + received incoming(i) − received outgoing(i).
net reciprocal balance(i) = received incoming(i) − received outgoing(i).
pending allocation = allocated − received, counted in the scenario only when both participants declare authorized consent.
need shortfall(i) = max(requiredNeed(i) − observed remaining(i), 0).
local minimum gap(i) = max(localMinimum(i) − observed remaining(i), 0).
What this result cannot establish
- Separate participant accounts retain staff-hours, direct fiscal costs, disclosures, services, goods, and observed benefits in native units. No unlike outputs are added.
- All resources are assumed fungible within one exact unit and common accounting period. No currency/unit conversion, travel time, service quality, or delivery probability is inferred.
- Consent is explicitly declared, not independently verified. A withdrawn or absent participant stays visible and stops pending transfers involving that participant.
- Historical receipts remain visible even after withdrawal; they do not authorize future activity. Authorized offers, acceptance, allocation, and receipt are never treated as interchangeable.
- The period ledger conserves resources in aggregate but does not establish within-period chronology or the legal authority to send or receive assistance.
- Net fiscal cost covers only supplied recorded line items in one exact currency, price basis and year. An empty direct-cost list leaves cost unknown; missing cost categories cannot be assumed zero.
- Recorded resource balances fund pending dispatches independently. An unsupported dispatch leaves the pending scenario unresolved, even if its net balance appears nonnegative after counting pending inbound aid.
What would falsify the assumptions?
- A receipt discrepancy, consent withdrawal, non-fungible resource, or understated local minimum can invalidate the allocation scenario.
- Independent dispatch, receipt, local-service, and consent records can contradict each supplied ledger state.
- Total observed remaining resources must equal initial resources; reciprocal balances sum to zero. A manual ledger produces the same arithmetic.
- This is arithmetic, not a causal or approval model. MAR adds no demonstrated benefit when a manual ledger is identical; overcommitted reserves or missed withdrawals add risk.
- 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": "staff-hours",
"origin": "synthetic",
"sources": [
{
"id": "SYN-001",
"kind": "synthetic",
"label": "Fictional example",
"url": null
}
],
"participants": [
{
"id": "A",
"label": "Fictional locality A",
"unit": "staff-hours",
"consent": "authorized",
"resources": 100,
"localMinimum": 60,
"requiredNeed": 60,
"authorizedOffer": 30,
"accounting": {
"staffHours": 15,
"budget": {
"unit": "USD minor units; nominal 2027",
"directCosts": [
{
"label": "Recorded coordination expense",
"value": 20000,
"unit": "USD minor units; nominal 2027",
"sourceReference": "SYN-001"
}
],
"fiscalOffsets": [
{
"label": "Recorded reimbursement",
"value": 5000,
"unit": "USD minor units; nominal 2027",
"sourceReference": "SYN-001"
}
]
},
"disclosures": [
{
"label": "Aggregate staff capacity",
"purpose": "Fictional civilian mutual-aid planning",
"sensitivity": "Aggregate fictional data only"
}
],
"serviceCoverage": [
{
"label": "Requests served",
"value": 60,
"unit": "requests",
"sourceReference": "SYN-001"
}
],
"deliveredGoods": [],
"observedBenefits": [
{
"label": "Recorded forms completed",
"value": 12,
"unit": "forms",
"sourceReference": "SYN-001"
}
],
"dependencies": [
{
"provider": "Local records",
"fallback": "tested",
"withdrawalEffect": "Local independent records remain usable"
}
],
"withdrawal": {
"canWithdraw": true,
"conditions": "Pending assistance stops when either participant withdraws"
}
}
},
{
"id": "B",
"label": "Fictional locality B",
"unit": "staff-hours",
"consent": "authorized",
"resources": 20,
"localMinimum": 20,
"requiredNeed": 60,
"authorizedOffer": 0,
"accounting": {
"staffHours": 3,
"budget": {
"unit": "USD minor units; nominal 2027",
"directCosts": [
{
"label": "Recorded coordination expense",
"value": 1000,
"unit": "USD minor units; nominal 2027",
"sourceReference": "SYN-001"
}
],
"fiscalOffsets": []
},
"disclosures": [],
"serviceCoverage": [
{
"label": "Requests served",
"value": 35,
"unit": "requests",
"sourceReference": "SYN-001"
}
],
"deliveredGoods": [
{
"label": "Recorded civilian packages",
"value": 4,
"unit": "packages",
"sourceReference": "SYN-001"
}
],
"observedBenefits": [],
"dependencies": [
{
"provider": "Fictional shared channel",
"fallback": "none",
"withdrawalEffect": "Further reconciliation becomes unavailable"
}
],
"withdrawal": {
"canWithdraw": true,
"conditions": "Local service decisions remain local"
}
}
}
],
"transfers": [
{
"id": "T1",
"from": "A",
"to": "B",
"unit": "staff-hours",
"authorized": 30,
"accepted": 25,
"allocated": 20,
"received": 15
}
]
},
"parameters": {}
}Expected checks
{
"initialResources": 120,
"recordedReceipts": 15,
"totalNeedShortfall": 25,
"totalLocalMinimumGap": 0,
"pendingEligibleAllocation": 5,
"scenarioNeedShortfall": 20,
"netA": -15,
"netB": 15,
"recordedNetFiscalA": 15000,
"recordedNetFiscalB": 1000
}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.
- UNDRR: Sendai Framework monitoring — Country-reported indicators have coverage limits; no causal program effect is inferred. 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.