OASW(SO/LIC) Accelerator Event - July 2026 (GoColosseum)
Submission status: Selected. Per the portal, Selected means the submission was found technically meritorious and is under evaluation/consideration.
1BCT / 82nd Airborne - Operation Epic Fury challenge (GoColosseum)
Submission status: Submitted. Industry challenge from 1st Brigade Combat Team (1BCT), 82nd Airborne Division (CENTCOM AOR, Operation Epic Fury) for rapidly deployable commercial solutions in contested tactical environments. Polybolos portal submission: Advanced Tactical UAS, Edge Compute, Network, Inferencing Solutions.
AFRL engagement - April 2026
COMMAND HOTL materials were provided to Air Force Research Laboratory contacts at their request:
- Col Christopher Rondeau (AFRL/RQ): after receiving the package, requested permission to share it with additional colleagues while building out this portfolio; permission granted (portfolio review / distribution interest).
- Isaac Weintraub, PhD (Control Science Center, Air Warfare Directorate / RA): detailed technical Q&A on risk awareness, weaponeering, kinematics, and coordination. He wrote that the exchange helped him understand "the state of the art" and what can be gained through future partnerships, and indicated he would convey SBIR topic materials and/or partnering.
That is attributed scientific and portfolio dialogue.
Technology maturity
Command HOTL is assessed at TRL 5 (lab / SITL / controlled demo / Lattice developer sandbox). Decision-C2 / human-on-the-loop authority lineage. Lattice
Sandbox / interoperability evidence (including documented scale publish-ingest work) supports Lattice-edge integration feasibility. Not a production Lattice mesh claim. Independent of Anduril; samples are not Anduril products. Inquiries: Contact@Polybolos.org
CAGE: 1AVY9 · UEI: RUSHH9B2UQV3 · Polybolos Institute
A door-level publish load harness. It authenticates (OAuth + Sandboxes
Bearer), firehoses PUT /api/v1/entities for N synthetic AIR tracks, and
prints a JSON scoreboard (ok / fail / HTTP 403, wall time, PUTs/sec,
latency p50/p95).
It measures the Lattice REST publish path only.
Why publish it: Sandbox swarm injects often hit an HTTP 403 intake
cliff. Teams that paper over that with client-side sleeps look like they
misread the platform. This repo documents the honest method: firehose,
count accepts and 403s, report first_fail_index. That is how you show you
actually understand Lattice Sandboxes behavior under load.
| Target | What you should expect | How to read it |
|---|---|---|
--target mock |
Clean 5k / 10k accepts when mock-lattice is healthy | Proves the harness and your machine loop |
--target live |
Often a mid-swarm HTTP 403 cliff (ok > 0, then rejects) | Proves you hit a real Sandboxes intake limit |
| Live with many 403s | Exit code still 0 | 403 is evidence, not a failed tool run |
| Mock with 0 ok | Exit code 1 | Harness / mock wiring is broken |
Correct use: publish the scoreboard, including http_403 and
first_fail_index. That shows you exercised Lattice honestly.
Incorrect use: adding permanent PUT throttling so live always shows 10k/10k green. That hides the sandbox cliff this repo is meant to surface.
| Target | Behavior |
|---|---|
--target mock |
Embedded anduril-mock-lattice (default CI path) |
--target live |
Real Sandboxes via LATTICE_* env |
Optional: SOAK_MOCK_FAIL_AFTER_N=109 simulates a sandbox-style 403 cliff on mock.
# needs sibling anduril-mock-lattice (or --mock-url)
python -m soak --target mock --n 5000 --pretty
python -m soak --target mock --n 10000 --pretty
# live sandbox (load LATTICE_ENDPOINT CLIENT_ID CLIENT_SECRET ENV_TOKEN)
python -m soak --target live --n 5000 --pretty
python -m soak --auth-only --target live{
"n_requested": 5000,
"ok": 5000,
"fail": 0,
"http_403": 0,
"wall_s": 12.3,
"puts_per_sec": 406.5,
"latency_ms_p50": 2.1,
"latency_ms_p95": 4.0,
"policy": "firehose (no publish throttle); 403 is Lattice-side evidence"
}- HOTL / Core / ThreatQueue / kin-checksum / Apollonius
- Inbound stream soak
- Permanent client-side rate limiting
pip install -r requirements-dev.txt
pytest -qMIT - see LICENSE.
This repository is the open foundation (MIT).
Polybolos Institute also maintains a proprietary catalog of additional capabilities that are not published here. Contact us to discuss production deployment and commercial licensing.