← Return to Wolfberg
Wolfberg Per Aspera · Full requirement breakdown · every requirement to code

How each requirement is met, line by line.

#22Governed Mission Acceleration - the use case we submitted 8 / 8

The operating model itself. Every requirement, in code.
RequirementStReceipt · code
Five solutions, at least one at TRL 4METFive governed missions on one engine (#08 air, #07 FOB, #01 seabed, #02 convoy, #04 swarm); #08 TRL 4 on real drone-track data. c2-missions/src/runner.ts
A human approves every irreversible action, with a live abortMETGraduated-authority gate + always-live ABORT→MANUAL bar. c2-gate/src/gate.ts
The AI is held off the decision path; assists and narrates, never authorsMETNo-model-call CI test on the gate path; narration role IAM-denied from the ledger. infra/modules/runtime/hardening.tf
A tamper-evident audit trail of every human-machine interactionMETEd25519-signed, SHA-256 hash-chained ledger + Merkle proofs + S3 Object-Lock WORM. core/src/ledger.ts
Authority and lawful posture scoped to each mission, enforced before any actionMETAuthority envelope per mission = ledger entry #1, enforced by the gate. contracts/src/authority-envelope.ts
One shared substrate; a new mission is a config change, not a new buildMETEvery mission imports the same runGovernedMission; a test asserts referential identity of the gate. test/one-engine.test.ts
Operation in denied or degraded conditions, reconciling on reconnectMETGreengrass v2 edge, on-device ledger, store-and-forward, reconcile-on-reconnect. infra/modules/edge
Real data, each mission's scope stated plainlyMETReal NOAA AIS / ADS-B / SkyFusion + a SCOPE OF CLAIM panel per card. datasets/REAL-CORPORA.md

#8UAV/UGV Counter-UAS Operations TRL 4 8 / 11

8 of 11 in code. 3 disclosed as physics/profile. 0 faked. (#4 Counter-UAS is a separate use case with no published requirements.)
Requirement (11)StReceipt · code
Multi-modal detection (RF, optical, acoustic, radar)PARTIALRF + radar + EO/IR fused; acoustic on the same SensorAdapter seam, designed not wired. c2-fusion/src/fuse.ts
Autonomous threat classification and prioritizationMETGNN + Kalman + JPDA fusion, LLM-free. c2-fusion/src/fuse.ts
Real-time trajectory predictionMETIMM prediction in fusion. c2-mission/src/missions/ch08.ts
Automated countermeasure selection and deploymentMETEffector selection/tasking (NINJA-EW, LEONIDAS-HPM), simulated. c2-mission/src/effector.ts
Integration with existing air defense systemsMETMITRE CoT over TAK; BSI Flex 335 / SAPIENT. c2-fusion/src/cot.ts
Friendly force identification and deconflictionMETReal ADS-B Cessna 172 (a24c5a) held cooperative; two-person rule. c2-mission/src/missions/ch07.ts
Operation in degraded network conditionsMETGreengrass v2 DDIL edge + store-and-forward. infra/modules/edge
Must operate in all weather conditionsDISCLOSEDWeather-independent by design (radar/RF physics; EO/IR the clear-air adjunct). Not separately modeled; stated, not faked.
Limited power availabilityDISCLOSEDGreengrass SWaP-constrained forward-node profile; demo runs on EC2 for reproducibility. No measured power budget claimed.
Restricted RF emissions in certain sectorsMETRF NO-EMIT sector enforced in the gate. c2-gate/src/gate.ts
Rules of Engagement (ROE) complianceMETGraduated authority, positive hostile-ID at weapons-tight, two-person rule. c2-gate/src/gate.ts
Verify: invariance.test.ts - 12 metamorphic transforms + negative control; 12/12 answer-key invariants reproduced.

#7 · #11 · #9The other built missions - honest width on the same spine

MissionMetWhat runs · code
#7 Maritime Infrastructure (our #01)0 / 7All 7 reqs are undersea autonomy (UUV nav, 30-day power, multi-physics seabed fusion) - deliberately not built (ITAR/classified). Governed surface-AIS layer runs on the shared spine. c2-width/src/maritime-mission.ts
#11 Supply Chain / Convoy (our #02)3 / 12Real-time risk + ROE (UNCLOS recommend-only) + denied/degraded on real NOAA AIS. Escort coordination, routing, EW scoped out. c2-width/src/maritime-fusion.ts
#9 Drone Swarm (our #04)2 / 11Edge processing + secure signed data on real SkyFusion imagery; a governed mapping mosaic, not a live swarm-coordination loop. c2-missions/src/mosaic-fusion.ts

The cross-cutting spine - the recurring requirement, met once

These recur in almost every use case. One engine satisfies them across all of them.
Requirement that recurs everywhereAppears inThe one artifact that meets it
Human approves every irreversible action#4 #6 #8 #9 #11 #16 #17 #19 #22c2-gate/src/gate.ts
Tamper-evident / comprehensive audit trail#8 #12 #16 #17 #19 #20 #22core/src/ledger.ts
Denied/degraded operation · store-and-forward#7 #8 #9 #10 #11 #15 #22infra/modules/edge
Grounding / citations / no hallucinated references#6 #15 #17 #18 #19 #22LLM off the decision path; every claim traces to a ledger record. hardening.tf
Same architecture, new domain by config not code#19 #21 #22Swap the adapter, keep the runtime: ais-adapter.ts · imagery-adapter.ts

Concepts that still meet requirements - via the spine (two with real infra)

Use caseMeetsHow · receipt
#20 FedRAMP Threat Detection real infra2+3 / 7NIST 800-53 mapping (SI/AU/IR/AC), GuardDuty/CloudTrail, audit-evidence export - real Terraform. .kiro/specs/security-800-53-mapping · infra/modules/observability
#21 Disaster Response Data Fusion architecture3+3 / 8Pluggable connectors + common model + near-real-time - our contract-first adapter pattern is "swap the source, keep the architecture." contracts/src/events.ts
#15 Intelligence Fusion (edge)3+1 / 7Austere-edge <500W, store-and-forward, explainable output with source attribution + confidence. infra/modules/edge
#19 Citizen Services Chatbot3+2 / 7Tamper-evident interaction log, human-escalation on confidence, config-driven multi-tenant substrate. core/src/ledger.ts + the gate
#16 Payment · #17 Policy · #10 Disaster · #12 Media1-2 eachHuman-in-loop checkpoints + comprehensive audit trails + grounding, inherited from the governed runtime the moment a domain adapter is built.
Code links resolve to main of WolfbergPerAspera-Team/wolfberg-peraspera-hackathon. Met/partial are our honest assessment; requirement counts are objective from the portal. Effectors simulated; running prototype on real open-source data under a synthetic tactical scenario; NIST 800-53 r5 mission mapping, not an ATO. ← back to the results