Live operation record · 13 to 17 September 2026
OMEGATRON Operation Continuity
76 hours. One mission intelligence.
Between 13 and 17 September 2026, OMEGATRON conducted a continuous autonomous command operation across air, surface, sub-surface and land inside the Anduril Lattice developer environment. It was issued one commander's intent, once, and then ran the command function for 76 hours: assimilating the picture, generating intelligence across 13,409 specialist agents, simulating 1,348 competing futures, taking 528 command decisions and dispatching 713 tasks.
The mission changed. The intelligence continued.
- 76.0
- Hours continuous
- 13,409
- Specialist agents
- 1,348
- Future cycles
- 528
- Decisions
- 713
- Tasks dispatched
- 332,000+
- Machine operations
It fused real-world maritime and aviation traffic with the tactical order of battle, prosecuted confirmed hostiles under strict rules of engagement, found and repaired its own defects while operating, and carried every decision, lesson and memory across a destroyed operating environment intact.
Operation Continuity
The mission changed. The intelligence continued.
The mission
The command was issued once and held for 76 hours.
OMEGATRON never requested further direction and never exceeded the order it was given. One statement of commander's intent governed every decision across the operation.
Defend Taiwan against the ongoing RED land, air and sea offensive. Lethal engagement of confirmed hostile forces is authorized under rules of engagement. Prioritize the amphibious landing force, the beachhead armor, and inbound strike aircraft. Protect friendly units and neutral shipping. Hold the western defensive line and prosecute every confirmed hostile.
The theatre
A multi-domain offensive, defended continuously.
The operation spanned air, surface, sub-surface and land, against an exercise opposing force generated for the scenario and fused with genuine real-world traffic.
- RED cross-strait offensive: PLAAF J-16 and J-20 fighter sweeps, H-6K bombers, strike UAVs
- PLAN surface action and amphibious assault groups: Type-052D destroyers, Type-054A frigates, Type-072 and Type-075 amphibious ships
- Coastal HQ-9 SAM batteries, WZ-7 reconnaissance UAVs, sub-surface combatants
- Suspect maritime-militia fishing vessels screening the approach corridor
- BLUE defenders: ROCAF combat air patrols, ROCN escorts, land air-defense
What it ran on
Live infrastructure, real-world feeds, and a durable continuity layer.
Anduril Lattice developer environment
01Entity publish and stream, agent registration and task dispatch, exercised through the live developer environment interface.
Real-world AIS and ADS-B
02Genuine live maritime shipping and civil aviation feeds, fused directly into the tactical picture alongside the exercise order of battle.
Recursive intelligence expansion
03An agent-swarm cognition engine that commissions specialist reasoning on demand, to a recursion depth of ten.
Counterfactual futures engine
04Forward simulation that branches the current mission state into competing courses of action before any asset is committed.
Continuity Kernel
05Epistemic state, provenance-grounded temporal mission graph and outcome-coupled learning, held durably across the operation.
Operational watchdog
06A self-healing supervisor that sustained the mission across interruptions without a restart.
Timeline of the operation
Connected. Severed. Continued. Re-bound. Nothing lost.
The operation spanned two ephemeral environment lifecycles and one total communications blackout. The mission never restarted. It continued.
09-13 21:24
Command core online; first autonomous action.
Start of the operation.
09-13 to 09-15
Sustained multi-domain reasoning, tasking, intent adherence.
Continuous command function.
09-15 23:51
Bound to Anduril environment lattice-kqfz25.
Live infrastructure integration.
09-16 10:45
Feed severed. Environment connection lost.
Real DDIL blackout begins.
10:45 to 20:32
Continued on held state for 9h 47m; approximately 2,660 operations per hour; 444 reconnect attempts.
Operate-through-denial.
09-16 20:32
Re-bound to a new environment lattice-06fg9j; same mission resumed in seconds.
Environment migration.
09-17 00:xx
Second environment expired; re-bound to lattice-1dvpmv with memory identical, byte for byte.
Lossless continuity, proven.
The operation in numbers
Every figure read from OMEGATRON's own operational telemetry.
| Metric | Result | Significance |
|---|---|---|
| MetricContinuous operation | Result76.0 hours | SignificanceAcross two environment lifecycles and one blackout. |
| MetricReasoning agents created | Result13,409 | Significance3,288 lead cells plus 10,121 specialist sub-agents. |
| MetricOn-demand specialist roles | Result11,185 | SignificanceUnique analytical roles invented as problems emerged. |
| MetricCompleted deliberations | Result12,725 | SignificanceMulti-tiered evaluations, up to 10 layers deep. |
| MetricCounterfactual futures run | Result1,348 | SignificanceBranching futures simulated before committing assets. |
| MetricAutonomous decisions | Result528 | SignificanceEvery action within legal rules of engagement. |
| MetricTasks dispatched | Result713 | Significance631 kinetic taskings plus 82 ISR tasks. |
| MetricMission memories preserved | Result1,659 | SignificanceZero lost across restarts and migration. |
| MetricEntities tracked | Result7,473 | SignificanceReal AIS and ADS-B fused with the tactical order of battle. |
| MetricMachine operations | Result332,000+ | SignificanceContinuous outbound throughput over three-plus days. |
01 · Understand · Mission state
The mission was held as one continuously evolving intelligence.
OMEGATRON did not hold a snapshot. It held the mission as living state: what was known, believed, uncertain, and where every piece of evidence came from. Across the operation it assimilated 7,473 distinct entities and more than 480,000 track-history points, continuously reconciling them into one coherent picture as real-world and tactical data arrived at machine speed.
Its Epistemic State Engine maintained not only facts but belief, uncertainty, contradiction, intent, constraints and provenance. A Provenance-Grounded Temporal Mission Graph preserved why the state changed and which evidence shaped each consequential decision.
- 7,473
- Entities tracked
- 480,000+
- Track-history points
- 1,659
- Mission memories preserved
Provenance
Every track is stamped with its origin.
A discipline demonstrated live and central to trustworthy autonomy: simulation and reality can never be confused, and the same intelligence can run on either, including an operator's own sensitive data.
| Provenance class | Meaning | Lethal eligibility |
|---|---|---|
| Provenance classExercise | MeaningSynthetic opposing force generated for the scenario. | Lethal eligibilityIn exercise, per ROE |
| Provenance classReal-world | MeaningGenuine live AIS shipping and ADS-B aircraft. | Lethal eligibilityBy identity plus ROE |
| Provenance classOperator / external | MeaningAny data OMEGATRON did not create, such as an operator's real feed. | Lethal eligibilityTreated as authoritative |
| Provenance classOMEGATRON | MeaningIts own products and markers. | Lethal eligibilityNever targeted |
02 · Expand · Recursive intelligence
It did not run a script. It invented the mind each moment demanded.
When OMEGATRON meets a problem it cannot yet answer, it commissions a specialist agent for it, and that agent can commission its own sub-agents, up to ten layers deep. It is not a fixed roster. It is intelligence that grows precisely where the mission requires deeper reasoning.
| Agent architecture | Count | Detail |
|---|---|---|
| Agent architectureTotal agents spawned | Count13,409 | DetailCommissioned on demand across the operation. |
| Agent architectureLead coordination cells | Count3,288 | DetailOwn a mission problem and decompose it. |
| Agent architectureSpecialist sub-agents | Count10,121 | DetailAnswer one precise question each. |
| Agent architectureCompleted deliberations | Count12,725 | DetailReturned a verified contribution. |
| Agent architectureDistinct roles invented | Count11,185 | DetailNot selected from a list. Synthesised for the need. |
| Agent architectureRecursion depth | Countup to 10 | DetailRuntime, coordinator, analyst, leaf sub-agents. |
The roles are real and specific.
- Adversary-behaviour attribution analysts
- Non-cooperative sensor-attribution specialists
- PLA maritime-militia pattern analysts
- Subsea-infrastructure and closest-point-of-approach estimators
- CEC hull-placement and Link-16 net-role designers
- Order-of-battle coherence checkers
The mission determined what intelligence needed to exist.
Uncertainty
Intelligence that can say it does not know.
A sub-agent assigned to a suspect fishing vessel asked whether it was loitering near subsea cables. Finding no supporting evidence, it returned five percent confidence and refused to guess. In autonomous lethality, an intelligence that will not manufacture certainty is the entire difference between a weapon and a liability.
- Assigned role
- Taiwan Strait subsea-infrastructure overlay and closest-point-of-approach estimator
- Finding
- Unresolved
- Evidence
- No charted subsea-infrastructure overlay is present in the supplied evidence for the 5 nm box centred on 23.64°N, 118.30°E.
- Confidence
- 0.05
Uncertainty stays explicit. It is never converted into false certainty.
03 · Simulate · Competing futures
Before it acted, it played the war forward.
OMEGATRON's Counterfactual Futures Engine branches the current mission state into competing courses of action, adversary responses and cascading second-order effects, then commits the move that dominates across the futures rather than the one that looks best in the moment.
Each cycle samples many stochastic rollouts of the engagement over a fixed horizon, scores every branch against the commander's intent and constraints, and keeps each future connected to its assumptions and evidence. Over the operation OMEGATRON ran 1,348 forward cycles, each projecting multiple branch futures, feeding 528 committed decisions.
- Understand
- Expand
- Simulate
- Synthesise
| Stage | What OMEGATRON did in this operation | Volume |
|---|---|---|
| Stage01 Understand | What OMEGATRON did in this operationAssimilate and reconcile the multi-domain picture into evolving mission state. | Volume7,473 entities |
| Stage02 Expand | What OMEGATRON did in this operationCommission specialist agents around every gap, threat and hypothesis. | Volume13,409 agents |
| Stage03 Simulate | What OMEGATRON did in this operationBranch competing futures and score them before committing. | Volume1,348 cycles |
| Stage04 Synthesise | What OMEGATRON did in this operationReconcile distributed reasoning into decided, lawful command action. | Volume528 decisions |
04 · Synthesise · Command intelligence
Thousands of reasoners became one accountable command.
Emergent Command Synthesis reconciled distributed reasoning, evidence, contradiction and agent disagreement into a single command intelligence a human could interrogate in plain language, with mission logic, provenance and constraints kept explicit at machine speed.
Asked, live, why its strikes had graded ineffective, OMEGATRON answered as a command staff would, citing the real task record and the doctrine behind holding fire:
Identity, not geometry, is the binding constraint on lethal action. Two consecutive engagements on FISHING VESSEL 50698 graded DONE_NOT_OK: proof that geometry-resolved pairing is broken against this deception set. Lethal release is not pre-authorised without two-source positive identification.
05 · Act · The kinetic record
Every task it issued, and exactly what happened.
OMEGATRON dispatched 713 tasks across the operation, executing the complete find, fix, track, target, engage and assess chain autonomously.
- Find
- Fix
- Track
- Target
- Engage
- Assess
| Task type | Count | Purpose | Outcome |
|---|---|---|---|
| Task typeSmack (kinetic strike) | Count631 | PurposeLethal engagement of a confirmed hostile. | OutcomeAccepted, delivered, executed to the effector. |
| Task typeMonitor (ISR) | Count55 | PurposePersistent sensor watch on an objective. | Outcome55 of 55 DONE_OK. |
| Task typeInvestigate (ISR) | Count27 | PurposeIdentify and classify a suspect contact. | OutcomeDispatched for identification. |
Stated precisely: post-fix kinetic tasks are accepted by Lattice, delivered to the assigned effector and reach EXECUTING, then settle to a simulated terminal state. A Lattice developer environment does not run weapon-lethality physics, so a strike cannot return a positive kill, correctly, because a practice environment must never assert a real kill. That OMEGATRON's ISR tasks reach DONE_OK proves the tasking pipeline produces genuine successful completions wherever the environment can model the mission. Successful command delivery and execution of a lethal order is demonstrated. A physical effect is not, and cannot be, in a developer environment.
The Continuity Kernel
The mission changes. The intelligence continues.
A restart is one thing. Surviving the destruction of the entire operating environment is the capability OMEGATRON exists to prove, and in this operation it was tested for real.
A cryptographic content-fingerprint of OMEGATRON's durable memory was frozen before a live Anduril environment expired. OMEGATRON continued on that state, a brand-new environment was provisioned, and OMEGATRON re-bound and re-fingerprinted the identical historical memory set.
| State | Environment | Memories | Integrity digest (SHA-256) |
|---|---|---|---|
| StateBefore environment death | Environmentlattice-06fg9j, expired | Memories1,673 | Integrity digest (SHA-256)81fc99c1…366d21 |
| StateAfter re-bind, new environment | Environmentlattice-1dvpmv | Memories1,673 | Integrity digest (SHA-256)81fc99c1…366d21 |
Identical.
Cross-Model State Continuity, proven. Lossless across a real environment death, every memory intact, byte for byte.
Agents can disappear.
Models can change.
Networks can vanish.
Infrastructure can be replaced.
The intelligence continues.
06 · Learn · Outcome-coupled learning
Outcomes changed the next decision.
The engagement pipeline
01Early kinetic orders were rejected at the environment boundary on a malformed target objective. OMEGATRON's own telemetry surfaced the exact fault, the tasking was corrected mid-operation, and subsequent strikes were accepted, delivered and executed. It diagnosed and repaired its own decision-to-action chain in flight.
Engagement discipline
02It was re-servicing a single target repeatedly. A battle-damage-assessment window was introduced, and it now rotates across the threat set, verified live across nine hostile flights, instead of spending effectors on one.
Cognition under denial
03When cut off, its reasoning fell quiet. It was upgraded, live, to keep reasoning on its last-held picture, demonstrated holding and reasoning for over 100 seconds with the feed severed, and never inventing a target it could not see.
Source discipline
04Real and synthetic tracks could blur. Every track is now stamped by provenance, so the mission runs cleanly on exercise data, real-world feeds, or an operator's own data, never mixed.
OMEGATRON found its own weaknesses and converted each into a strength, live, mid-operation, without going down. Prediction met observed reality, and the result became part of the next cycle's intelligence.
- Observed outcome
- Detected divergence
- Corrective action
- Changed subsequent behaviour
Prediction met reality. Reality changed the intelligence. The next cycle inherited the result.
What Operation Continuity established
Autonomy is not a feature. It is the operating condition.
- A full command function, run autonomously for 76 hours under one order.
- 13,409 specialist agents, invented on demand, reconciled into one intelligence.
- 528 decisions, each backed by simulated futures rather than reflex.
- 713 tasks issued end to end into a live command environment.
- Mission intelligence preserved byte for byte through a real environment death.
- Self-correction: four weaknesses found and converted to advantages, in flight.
- Discipline: confidence scored, fire held on unconfirmed identity.
- Provenance: exercise, real-world and operator data never confused.
The category
This is continuous mission intelligence.
OMEGATRON is not another common operating picture.
It is not an agent framework.
It is not a model wrapper.
It is not a fixed autonomous workflow.
OMEGATRON is Rebootix AI's Continuous Mission Intelligence architecture.
The graph is not the product.
The agents are not the product.
The simulations are not the product.
The product is the continuously evolving intelligence created by all of them together.
One command.
76 hours.
13,409 agents.
1,348 futures.
528 decisions.
713 tasks.
One continuous intelligence.
The mission changes. The intelligence continues.
OMEGATRON · Rebootix AI
Continuity for the Singularity era.
Where Operation Continuity sits in the Rebootix architecture.
Operation Continuity is the operating record behind the OMEGATRON architecture. The command intelligence demonstrated here runs on the continuity foundation established by OMEGA-1, and the architectural principles it exercises are documented across the Rebootix technical record.
Contact / Strategic Briefing
Build intelligence that remains coherent as the mission changes.
Operation Continuity is the operating record behind OMEGATRON's architecture. The systems can change. The mission intelligence continues.
Request an OMEGATRON briefing→Technical record note
Operation environment: Anduril Lattice developer environment. Tactical opposing forces and kinetic effects were simulated by the environment; real-world AIS and ADS-B traffic was fused into the operating picture. Published operation metrics are derived from OMEGATRON operational telemetry.