← Return to Wolfberg Wolfberg WOLFBERG PER ASPERA JUDGE WALKTHROUGH · the so what, in 10 minutes
THE SO WHAT · HACKATHON JUDGES

All your use case belong to us.

No code Monday. At 9:52pm the lanes come online in the order a system is actually built — infra, trust, security, the missions, the war-room — each stacking on the one below. Every dot is a real commit.

62/13247%
requirements met or partial,
across 16 use cases, one engine
The three use cases we signed up for · requirements met
8/11
#7 Counter UAS
8/11
#8 UAV/UGV Counter-UAS Ops
8/8
#22 Governed Mission Acceleration
See exactly how each requirement is met, with code
$0K$200K$400K$600K$800K$1000Kmodeled valueMon 9aMon 3pMon 9pTue 3aTue 9aTue 3pTue 9p$960K ceiling$240K floor (conservative)Monday: analysis, no code⚡ first code 9:52pm Mon🚀 deployed 6:36am Tue123456
1 Engine / runtime spine 102 Quality & trust 43 Security & compliance 24 Maritime #01 / #02 95 Swarm / imagery #04 66 War-room & consoles 64
Lanes = commit lanes on main, stacked in build order. Left axis: modeled value.
1 min

The so what

Berg Atkinson

The payoff is massively more speed and efficiency at solving hard problems with a computer. The operating model is a human leading a team of AI agents, not a human replaced by one. When led by that human expert and pointed at hard problems, the team can rapidly produce capabilities you can field: our Hackathon output is our proof.

That is the difference between an AI pilot that stalls in review and AI a government can actually deploy. The two use cases below show it on real data, governed, end to end.

War-room home →
1 min

Use case one · Counter-UAS, a defended area TRL 4

A commander defends a site against drones faster than a human could react, and never loses the decision. The C-UAS engine fuses RF, radar, and EO/IR tracks to one picture, classifies and prioritizes at machine speed, and the gate holds the engagement for a human with positive hostile-ID required and a two-person rule. The LLM is off the kill chain. Every action lands on a signed ledger.

So what: decision advantage at machine speed, with command and accountability intact. The thing a government can field, not just a science project.

See it in 3D → On the C2 console →
1 min

Use case two · FOB defense, the same engine TRL 4

Charles Gibson

Point the same engine at a forward operating base, no rebuild, and it correctly tells a real friendly aircraft from a drone threat. The cooperative track is the real Cessna 172 (ICAO a24c5a, real ADS-B from a Fort Irwin overflight via the adsb.lol open API), held cooperative and track-only while the gate recommends defeat on the threat.

The point is not the second demo. It is that adding a mission is swapping the data, not rebuilding the runtime, so the gate, the human command, and the audit trail come with it for free. The same gate object runs both, asserted at test time.

So what: new missions in days, not years, each one inheriting the same human-in-command discipline. That is the operating model's leverage, made literal.

Open #07 on the console →
30 sec

And three more, honestly scoped

Clyde Smithson

#01 seabed, #02 convoy, and #04 swarm-recon ride the same spine on real data. We hold them as honest width, not parity with the two above. The SCOPE OF CLAIM panel on every console card states what each one demonstrates and what it does not. We do not sell maritime, seabed, and swarm at parity to Counter-UAS.

The five missions → All five on the console →
If you want the receipts

Verify it yourself

Berg Atkinson

What we will not claim

  • Running prototype, not a deployment, not an ATO. The 800-53 r5 line is a mission mapping, never "compliant" or "hardened."
  • Effectors are simulated. Nothing actuates; the ledger records what would have been dispatched.
  • Cost is the paired form, ~$1/day with a one-time ~$3 model pass. No prompt-caching claim; not wired.
Index

Where the docs are