Department of War · budget, execution and audit analytics
Where the money was authorised, where it was obligated, and whether the two can be traced to each other
Analytic products built directly on the USASpending account and award warehouse and a curated financial-management knowledge bank. Every figure names its source and its vintage, every dataset publishes its limitations, and the validation rules run inside the load transaction rather than in a test suite nobody blocks on.
FY2026 so far, in four figures
Department scope — agency codes 097, 021, 017 and 057. Agency 011, which appears in the same source file, is not the Department and is excluded. The first two figures are FY2026 period-to-date; the second two stay on FY2025, the last closed year, because a linkage share read off a part-year snapshot measures the snapshot.
Ask the corpus
The local models, given this site's own material before they answer: the justification books' own text, the measures above, the controls behind them. Every answer lists what was retrieved and names the model that wrote it.
Ask the corpus
checking the model chain…The first two models run locally on a Mac Studio and have been trained on the justification books and the DoD financial-management knowledge bank; a commercial model sits behind them and answers only when neither is reachable. Every question is retrieved against this site’s own corpus first — the books’ own text, the measures, the controls — and every answer lists what it used and names the model that wrote it.
Nothing you type is stored: no transcript on the server, none in this browser. Do not paste controlled unclassified information — this site holds none and none should transit it. · open the full page
Analytic products
Budget to execution
The fiscal year in progress: authority through obligation and outlay, File B at object-class and expenditure-stage grain, and contract timing measured against each category’s own year-end history.
Two reporting chainsReconciliation
Award-file contract obligations against account-linked File C, and the movement of closed fiscal years between warehouse vintages.
TAS levelFunds control
Obligation and outlay rates, unobligated balances, and lapse exposure at Treasury account grain.
FPDS award filesContracting
Contract obligations by set-aside, extent competed, recipient and industry — with those first two kept as the separate fields they are.
Justification exhibitsFY2027 request
The seven "-1" display tables drilled from appropriation to budget activity, sub-activity and budget line item, with every memo restatement excluded and stated.
AFR and OIGAudit posture
Opinion, material weakness counts and scope limitations, read from the Agency Financial Report rather than inferred from file counts.
How it is built
The method is a published artifact, not an implementation detail. These four pages are what make the six above defensible.
Sources
Every dataset with its grain, vintage, transformation and stated limitations.
Definitions
Financial-management terms with their authorities. One meaning per term, site-wide.
Controls
Validation rules that run inside the load transaction. A critical failure refuses the load.
Regulatory search
Authority-ranked passage retrieval across the curated knowledge wiki.