The people who can prove what happened in a barracks.
The services already run the systems of record for unaccompanied housing. We do not replace them. We sit above them and prove what they claim: that an obligation was met, a room was inspected, a work order was closed, a dollar did what it was meant to do.
Every figure traces to a named public source with a retrieval date and a digest — or the screen says plainly that it does not.
Two frames, one ledger
What the statute requires
FY2026 NDAA § 2832 orders a Department-wide plan for accurate, integrated real-property and unaccompanied-housing data — ten named elements, due to the House Armed Services Committee on 30 September 2026 — and is the first federal statute to use the words ghost occupancy. § 2831 sets an independent-inspection floor. UFC 4-721-01 sets the binding habitability standard.
Barracks Ledger holds every one of those obligations as data: authority, owner, due date, evidence slot — computed at today's date by a shared statutory clock, never typed. When the plan is submitted, it is read element by element against the ten the statute names.
What the Secretary set as the test
The Barracks Task Force has more than $1.2 billion behind it, and the Secretary said he will get monthly reports from it “to confirm work is getting accomplished,” as reported by Stars and Stripes. By the same report, the first $400 million bought furnishings and mattresses for 81 barracks, and roughly $101 million more went to door locks in 10 barracks and security systems in 13 — which barracks was not specified. Each service surveyed its barracks; none of that data has been made public, as the American Homefront Project reported.
“Unless you're actually showing things getting fixed and repaired, service members aren't going to really buy in.”a Barracks Task Force member, as reported by the American Homefront Project, 27 Aug 2026
The work may well be happening. Nobody outside the building can show it. Barracks Ledger holds each commitment beside what would prove it, and who holds that record.
What runs today, on public data
Also running: 15 ghost-occupancy vectors, enumerated, each with its detector or its stated blocker, and write-time prevention controls; a hash-chained, bitemporal evidence spine; a six-year condition trend from the Federal Real Property Profile; a machine-verified register of named barracks parsed from every year's budget book. In open-data mode the platform is a compliance and evidence shell — it knows what is owed and has never been handed a departmental record. It says so on every screen.
What it is not
- Not a property-management system. eMH, NexGen IT and BUILDER are terrain, not competitors.
- Not a resident portal, not construction tooling, not a composite index over pass/fail standards, not a blockchain.
- Not for sale to the party being verified. Government side only — never a privatized-housing operator.
- Not a source of counts. A keyword extract is not a population, and nothing on the platform is summed into a barracks-spend figure.
How it is built
- Statutory machinery is imported from a shared library and never reimplemented; deadlines are computed, not typed.
- Every sourced figure is checked at build time against the retrieved file it came from; a quote that is not verbatim fails the build.
- Simulated data is permitted only where labelled on the figure itself, never summed with a sourced number, and removable with one flag.
- Hosted on Google Cloud with app-native accounts and keyless deployment; demonstrations run on public data and never touch CUI.
See it working
The demonstration takes eight minutes, runs on public data, and needs no permission, no ATO and nothing from your installation. Write to the address below with a time that suits you.