# Q-Branch / Bush School Evaluation Pack

**Audience:** Q-Branch / Bush School evaluator
**Generated:** 2026-07-29T02:04:51.650Z

## How to run the session
- This is not a timed demo. This is an inspection room.
- Start with NDA acknowledgement, then inspect the platform by echelon, mission thread, scenario, proposal claim, live proof, and honest limitation.
- Every major claim below links to a live route or endpoint; gaps and authority boundaries are stated in the same row as the claim.

## Start here
- NDA status: /api/legal/nda/status
- NDA acknowledgement: /api/legal/nda/acknowledge
- Evaluation room: /evaluate/q-branch
- Catalog JSON: /api/evaluate/q-branch/catalog

## Echelon lanes
### Team / squad
- Operator: SOF team, field observer, sensor node
- Question: Who is online, what do they see, and can they publish it to TAK/COP?
- Route: /tak-bridge
- Proof: /api/tak/directory
- Actions: Push operator-as-sensor; Use TAK yellow pages; Request connection; Verify CoT stream

### Company / battalion
- Operator: Commander, XO, S3, FSO, protection cell
- Question: Can the unit share COP, raise alerts, synchronize fires/protection, and preserve decisions?
- Route: /cop
- Proof: /api/cop/alerts-intel
- Actions: Open COP; Raise/inspect alert; Review BLUF/COA; Hand off to fires or workspace

### BCT / JTF
- Operator: Guard major, J3/S3, interagency planner
- Question: Can multiple organizations plan, release data, wargame branches, and execute across functions?
- Route: /joint-planning
- Proof: /api/route-action-drills/resolve?path=/joint-planning
- Actions: Create planning session; Invite units; Refresh shared COP; Draft coordinating instructions

### NATO / coalition
- Operator: Coalition liaison, allied unit, interagency cell
- Question: Can partners share the minimum necessary picture without collapsing into one vendor stack?
- Route: /ops-hub
- Proof: /api/company/identity
- Actions: Use role/echelon entry; Switch NATO language shell; Show released-data discipline; Open TAK/COP bridge

## Mission-thread lanes
### National Guard major / DSCA bridge
- Why it matters: Connects county/state EM, Guard C2, FEMA-aligned workflow, TAK, COP, and commander update needs.
- Route chain: /em-hub -> /hazards -> /cop -> /tak-bridge -> /joint-planning -> /sandbox
- Proof: /api/hazard-watch/status, /api/cop/alerts-intel, /api/tak/directory, /api/sandbox/scenarios

### SOF target-cycle and austere team support
- Why it matters: Shows operator-as-sensor, intelligence synthesis, target handoff, fires export boundaries, and DDIL posture.
- Route chain: /ops-hub -> /intel-live -> /cop -> /tak-bridge -> /kill-chain-simulation -> /gps-denied
- Proof: /api/prove/touch?behavior=1, /api/evaluate/cohesion-status, /api/tak/bridge-status, /api/ddil/status

### Combined arms: maneuver, fires, protection, sustainment
- Why it matters: Demonstrates warfighting functions as one mission thread rather than separate tools.
- Route chain: /cop -> /joint-planning -> /fire-mission -> /cram-dashboard -> /logistics -> /workspace
- Proof: /api/fires/export, /api/protection/prove, /api/ios/current, /api/prove/touch?fires=1

### Maritime / port / chokepoint / EO-IR
- Why it matters: Connects AIS, maritime anomaly, EO/IR synthetic CV data, and counter-mining/chokepoint narratives.
- Route chain: /maritime -> /cv-pipeline?surface=uxsai-eoir -> /intel-live -> /cop
- Proof: /api/cv-pipeline/generator/status, /api/cv-pipeline/generate-eoir, /api/evaluate/featured-catalog

### GPS-denied / DDIL / post-quantum posture
- Why it matters: Shows the system operating when GPS/backhaul is degraded and explains PQC/AI governance posture honestly.
- Route chain: /gps-denied -> /sandbox -> /evaluate/aces -> /cyber-ops
- Proof: /api/ddil/status, /api/prove/touch/ddil-demo, /api/company/identity, /api/ai-security/provider-health

### Counter-UAS / ESMS / secure-room spectrum
- Why it matters: Shows RF/spectrum sensing, C-UAS detection/classification, TAK handoff, evidence custody, and human release.
- Route chain: /scif -> /tak-bridge -> /cop -> /cram-dashboard -> /operator-detection
- Proof: /api/mesh/status, /api/tak/directory, /api/esms/tracks, /api/rf-classify/status

## Proposal-to-action proof matrix
### DLA Release 2 NV006/NV007 capability package
- Claim: Live capabilities can be proven from routes/endpoints, not proposal prose.
- Live action: Open pursuit prove and route action drill; verify capability truth and endpoint response.
- Route: /pursuit-prove
- Proof: /api/prove/pursuit-r2
- Scenario: Opportunity proof sandbox lane
- Limit: Operator still certifies final DSIP submission.

### JTIC2S / joint fires interoperability
- Claim: C2/joint fires lane preserves human release and strict envelope discipline.
- Live action: Open COP or fires lane; generate/export proof payload with human-release caveat.
- Route: /fire-mission
- Proof: /api/prove/touch?fires=1
- Scenario: Combined arms fires handoff
- Limit: No live weapons release; export generation is not release authority.

### UxSAI synthetic EO/IR maritime data
- Claim: Deterministic maritime EO/IR data workbench produces labels, metadata, package hashes, COCO/YOLO.
- Live action: Open generator from CV pipeline; run quick package and inspect validation/export links.
- Route: /cv-pipeline?surface=uxsai-eoir
- Proof: /api/cv-pipeline/generator/status
- Scenario: Maritime EO/IR workbench
- Limit: Not radiometrically certified physics or diffusion generation.

### C-UAS / Every Soldier is a Sensor
- Claim: Spectrum/C-UAS observations promote to COP/TAK/evidence workflows with human release.
- Live action: Open secure-room spectrum and TAK yellow pages; create sensor/operator signal.
- Route: /scif
- Proof: /api/mesh/status
- Scenario: C-UAS + TAK handoff
- Limit: Jamming/effects require authorization; recommendation is not engagement.

### GPS-denied / DDIL resilience
- Claim: Mission state survives degraded network and can queue/sync under DDIL posture.
- Live action: Open GPS-denied and run DDIL prove chain.
- Route: /gps-denied
- Proof: /api/prove/touch/ddil-demo
- Scenario: DDIL earthquake / contested mission
- Limit: Fallback nav recommendations do not replace certified PNT hardware.

### FEMA / DSCA / EM dual-use
- Claim: Same platform supports emergency management, ESF routing, COP, CAP/WebEOC staging, and Guard DSCA.
- Live action: Open EM hub, hazard watch, COP, and sandbox emergency scenario.
- Route: /em-hub
- Proof: /api/hazard-watch/status
- Scenario: California earthquake / wildfire / DSCA
- Limit: No live IPAWS/HSIN/WebEOC write without sponsored credentials.

### PQC / AI governance / cyber posture
- Claim: AI and cyber posture are governed, cited, and bounded with explicit non-ATO/FedRAMP claims.
- Live action: Open cyber/AI posture and evaluator proof surface.
- Route: /cyber-ops
- Proof: /api/ai-security/provider-health
- Scenario: Post-quantum / AI governance review
- Limit: Not claiming completed FedRAMP, IL-5, FIPS module validation, or C3PAO.

## Scenario catalog
### Fight Tonight — MDMP/TLP
- Route: /sandbox
- Proof: /api/sandbox/scenarios?domain=Planning%20%26%20Readiness
- Use: Bush School planning test, Guard major, JTF staff, combined-arms rehearsal.

### California DDIL earthquake / DSCA
- Route: /sandbox
- Proof: /api/sandbox/scenarios?domain=Emergency%20Management
- Use: FEMA/state/local/Guard bridge; EOC + military support under degraded comms.

### C-UAS / fires / protection
- Route: /sandbox
- Proof: /api/sandbox/scenarios?domain=C-UAS%20%26%20Fires
- Use: SOF, base defense, event protection, layered detect-classify-recommend-act.

### SBIR / opportunity proof
- Route: /sandbox
- Proof: /api/sandbox/scenarios?domain=Opportunity%20Planning
- Use: Q-Branch/Bush School evaluator asks how proposal claims become live proof.

### Custom mission synthesizer
- Route: /sandbox
- Proof: /api/sandbox/scenarios/plan
- Use: Build scenario from their mission problem: Israel/Texas, FEMA, maritime, GPS-denied, SOF, C-UAS.

## Leave-behinds
- Reviewer brief: /evaluate/reviewer
- Featured demo: /evaluate/featured
- ACES proof: /evaluate/aces
- Demo pack: /demo-pack
- Capability statement: /capability-statement-combined
- TAK quickstart: /tak-bridge

## Next steps
- Confirm which lane Q-Branch wants to inspect first: Guard/DSCA, SOF, NATO/coalition, C-UAS, maritime, GPS-denied/DDIL, or proposal proof.
- Record attendees through the NDA direct-sign or operator-attested tour mode.
- Run one scenario through /sandbox and one live proof endpoint from the proposal-to-action matrix.
- After the session, send this tour pack plus reviewer brief, featured demo, ACES proof, demo pack, and capability statement links.

## Honest limits
- No autonomous lethal release; fires export is not weapons release.
- No live IPAWS, HSIN, WebEOC, or WFDSS writes without sponsored credentials.
- No completed FedRAMP, IL-5, FIPS module validation, or C3PAO claim.
- Q-Branch evaluation room is a curated static catalog; deeper downloadable packet/email automation can be added next.