Get Started

[A.RD / WP-006 / APPLIED INTELLIGENCE RESEARCH]

Mission-Prioritized
Intelligence Delivery

The value of intelligence is not established by how much reaches an operator. It is established by whether the right information arrives in time to support the right decision.

MPID is a proposed research framework for governing the relevance, sequence, presentation, and delivery of intelligence against an authorized mission. It is intended to improve decision speed without sacrificing evidentiary discipline, human authority, or operational awareness—even when communications capacity becomes severely constrained.

01 / DECISION ADVANTAGEMake what matters visible sooner.
02 / INFORMATION INTEGRITYPreserve why it should be believed.
03 / DELIVERY CONTINUITYProtect relevance under constraint.
WP-006 / MPID Applied intelligence systems / Research draft Revision 0.1 · 02 Nov 2026

Intelligence systems have become increasingly capable of gathering, correlating, and distributing information. Yet greater information availability does not necessarily produce faster or better decisions. The unresolved engineering problem is how to determine which intelligence warrants attention, what context must accompany it, and how delivery should change as mission requirements and operating conditions evolve.

The mission determines intelligence priority. The communications environment determines delivery capacity. Decision authority remains with the responsible human.

00 / ABSTRACT & RESEARCH POSITION

From information throughput to decision advantage.

Mission-Prioritized Intelligence Delivery (MPID) proposes that intelligence delivery should be governed by the needs of the assigned mission and its authorized decision requirements, rather than by arrival order, source volume, or transport availability alone. The framework distinguishes the significance of information from confidence in its correctness, the urgency of its use, its sensitivity, and the practical feasibility of delivery.

MPID is intended to function under ordinary network conditions as well as in congested, intermittent, degraded, or denied environments. Under normal connectivity, prioritization should reduce the time required to identify consequential changes. Under constrained connectivity, it should determine what can be delivered first without stripping away the context necessary to interpret it responsibly. During complete disconnection, it should preserve an intelligible local state and prepare authorized information for subsequent reconciliation; it cannot provide remote updates across a nonexistent link.

This publication defines a proposed analytical architecture, preliminary engineering requirements, a representative synthetic scenario, and a validation method. It makes no claim that an operational MPID implementation exists or that its proposed performance benefits have been demonstrated.

Research hypothesis

Against comparable conventional delivery methods, mission-bound intelligence prioritization will reduce the time required for an operator to reach a justified decision while preserving or improving decision accuracy, critical-event awareness, and evidentiary traceability. The hypothesis is falsifiable; improved speed alone is insufficient evidence of success.

01 / OPERATIONAL PROBLEM

Receiving information is not the same as understanding what requires a decision.

Contemporary operating environments generate reports from sensors, human observers, communications systems, historical records, automated processes, and external sources. Many are useful. Some are redundant. Others are incomplete, derivative, misleading, or unrelated to the immediate objective. A uniform feed may preserve arrival order while giving an operator little help distinguishing consequential change from routine background activity.

Three constraints intersect. Human attention is finite: sorting irrelevant information consumes time and can obscure critical developments. Information reliability is uneven: a repeated claim may appear corroborated when several reports share one source. Delivery capacity is variable: networks may offer considerable throughput at one moment and very little at another. None of these constraints can be solved by bandwidth alone.

The risk is not simply that an important report is transmitted late. It may arrive promptly but be buried among competing notifications, presented without its contradictions, or framed as actionable before sufficient evidence exists. Faster transmission can therefore coexist with slower or less reliable decision-making.

Why more bandwidth is not a complete answer.

Additional communications capacity expands the possible information flow. It does not determine which intelligence matters, whether its claims are independent, whether its useful life has expired, or which decision requirement it supports. Satellite, terrestrial, mesh, and radio technologies are essential parts of the communications environment; MPID examines a different layer of responsibility.

A recent USSOCOM handheld HF prototype solicitation explicitly calls for beyond-line-of-sight voice and data communications when conventional satellite and line-of-sight links are denied, degraded, or destroyed. Its narrowband requirements include low data rates down to 75 bits per second, adaptive link operation, and short position-reporting messages. The document is evidence of a stated requirement for resilient communications, not evidence that MPID has been requested, funded, or validated by USSOCOM. [R1, supplied solicitation, §§2 and 5.1]

A resilient connection can carry the wrong information first. MPID asks what the system should deliver before it asks how much the link can carry.

02 / GOVERNING PRINCIPLES

Priority must be justified by the mission, not manufactured by the system.

MPID extends Aerellus's Mission Primacy (WP-001) doctrine from presentation and analytical restraint into intelligence delivery. The information environment may change the operational picture; it does not acquire independent authority to redefine the assigned mission.

01Mission binding

An item's operational relevance must be attributable to a versioned objective, decision requirement, credible exception, or explicitly delegated responsibility.

02Evidentiary separation

Direct observation, source assertion, inference, analytical assessment, and authorized direction must remain distinguishable through prioritization and delivery.

03Independent dimensions

Mission relevance, confidence, urgency, sensitivity, and delivery feasibility are distinct considerations; no opaque composite number should silently substitute for them.

04Explainable promotion

The system must record why an item received prominence or transmission priority and what would cause that disposition to change.

05Preserve the record

Deprioritization is not deletion. Retained information must remain retrievable, reassessable, and governed by applicable retention and access rules.

06Human decision authority

The system may recommend, sequence, and alert. Mission changes, tasking, or consequential action require the appropriate accountable authority.

Importantly, an uncertain report may merit immediate attention when its potential consequences and relationship to the mission justify escalation. The alert must still identify the uncertainty. Priority does not certify truth. Conversely, a well-corroborated fact need not dominate an operator's view when it has no bearing on the current decision.

03 / MPID RESEARCH SCOPE

Information Dominance and Battlefield Awareness operate within MPID.

MPID is the overarching research framework. Information Dominance and Battlefield Awareness are related internal capability areas, not competing titles or separate delivery architectures.

Information Dominance

Concerns the ability to identify consequential information, understand its evidentiary standing, manage competing claims, and direct attention toward authorized decisions.

Within MPID, its principal questions are: what matters, why does it matter, how well is it supported, and who needs to know?

Battlefield Awareness

Concerns the continuous interpretation of operational conditions, changes, dependencies, and relevant uncertainties affecting the mission.

Within MPID, its principal questions are: what has changed, whose operating picture is affected, and what decision window remains?

Delivery Continuity is the supporting engineering concern that preserves these functions as connectivity changes. MPID should be useful in a high-capacity operations center and in a constrained field environment, although the interface and transmission policy may differ. Its design should remain adaptable to defense, emergency response, infrastructure protection, and other authorized operational settings.

04 / PROPOSED SYSTEM ARCHITECTURE

Separate deciding what matters from deciding how to send it.

MPID should not be embedded as a special feature of a particular radio, satellite provider, or visualization product. It is proposed as a policy-governed intelligence layer between information producers, operational decision requirements, and authorized delivery destinations.

FIG. 01 / PROPOSED, NOT DEPLOYEDLogical separation of mission-governed priority from transport selection and delivery.

Foundational information objects.

MISSIONAuthoritative context

Mission identifier and version, assigned objectives, decision requirements, responsible actors, escalation rules, and validity period.

INTEL_ITEMEvidence-bearing record

Claim or observation, source identity or protection category, event and receipt times, confidence rationale, dependency links, contradictions, and applicable handling restrictions.

RELEVANCEMission relationship

Explicit connection to a decision requirement, reason for prominence, known consequences, and the policy used to evaluate it.

DELIVERYBounded transmission

Recipient authorization, package dependencies, urgency, expiration, acknowledgement requirement, delivery attempt history, and permitted transport paths.

DISPOSITIONReviewable outcome

Displayed, deferred, withheld by policy, expired, superseded, or reconciled; includes actor, system version, and rationale.

The proposed sequence is ingest → preserve provenance → evaluate mission relationship → check critical exceptions → construct a coherent intelligence package → authorize recipients → sequence delivery → record disposition → reconcile changes. Policies must be versioned and reviewable; a transport adapter must not silently change analytical conclusions.

Command-1 may provide a future integration surface for these services, while OVRSYT may serve as a demonstration environment. Their mention describes a possible architectural relationship, not existing MPID functionality.

05 / MISSION PRIORITY & DELIVERY BEHAVIOR

Priority is a decision, not a label inherited from the source.

A source may report an event as urgent. The system may also estimate urgency. Neither is sufficient without the governing mission context. Proposed priority determination considers decision consequence, time sensitivity, authorized recipients, source uncertainty, and the information needed to avoid a misleading interpretation. The outcome should be a reasoned policy disposition rather than an unexplained ranking.

P0Critical decision dependency

A credible condition requiring immediate awareness for a time-sensitive, authorized mission decision or defined safety exception. Preserve the minimum context needed to interpret its uncertainty and consequence.

P1Time-sensitive mission change

An important change likely to affect planned decisions, coordination, or the near-term operating picture.

P2Supporting mission intelligence

Relevant context, supporting evidence, and updates useful to the mission but not requiring immediate attention.

P3Deferred or contextual record

Routine, redundant, historical, or presently low-relevance information retained for reassessment and eventual authorized synchronization.

P0–P3 are research labels, not a military message-precedence standard, classification marking, or substitute for established communications handling procedures. Final policy must respect governing doctrine, legal obligations, information sensitivity, and operator authorization. These bands have not been operationally validated.

Required safeguards against prioritization error.

  • Dependency preservation: an alert must not arrive as an isolated assertion if its interpretation depends on omitted caveats, provenance, timing, or disconfirming evidence.
  • Source independence: multiple reports from one underlying origin must not be treated as independent corroboration simply because they enter through different channels.
  • Age and expiration: a delayed update must be marked stale or superseded when the relevant decision window has passed; it must not masquerade as current intelligence.
  • Bounded priority escalation: repeated urgent messages must not permanently starve lower-priority but mission-required information, acknowledgements, or safety-critical functions.
  • Authorized exceptions: credible unexpected threats, immediate safety concerns, and mandatory reporting obligations must be surfaced through clearly defined exception rules.
  • Challenge and override: authorized operators must be able to question a priority decision, inspect its basis, and record an override without rewriting the source record.

An urgent report may be uncertain. An accurate report may be irrelevant. A short report may be dangerously incomplete.

06 / CONNECTIVITY STATES & CONTINUITY

Communications degradation exposes the value of priority, but does not define it.

MPID's primary objective is faster, better-supported decisions under all connectivity conditions. Communications degradation is a high-priority validation condition because it forces explicit tradeoffs: when only a small part of the intelligence stream can be delivered, sequencing and contextual completeness become consequential.

STATE ANormal capacity

Prioritize attention and decision relevance even when transmission is inexpensive. Preserve supporting information without treating every new event as an immediate alert.

STATE BConstrained capacity

Sequence authorized packages by mission importance and usable decision window; suppress redundant retransmission where safe and preserve critical dependencies.

STATE CIntermittent connectivity

Queue bounded, expiring packages; track delivery state and version; use store-and-forward mechanisms where supported and avoid treating attempted transmission as confirmed receipt.

STATE DComplete denial

Expose the age and limits of locally held intelligence; retain eligible outgoing changes for future transmission. Do not imply remote situational awareness remains live while all relevant paths are unavailable.

STATE ERecovery

Reconcile acknowledgements, superseded facts, mission-version differences, and missed updates before presenting a restored picture as synchronized.

Do not confuse link adaptation with MPID.

Radio and network systems can adapt modulation, coding, routing, and throughput to changing conditions. Delay/Disruption-Tolerant Networking already addresses store-carry-forward operation over interrupted links, including the IETF Bundle Protocol [R2–R3]. MPID does not claim to invent those functions. Its proposed contribution is the mission-aware evaluation and application-level delivery policy that determines which coherent intelligence packages deserve scarce capacity.

A valid implementation might use existing quality-of-service mechanisms, DTN services, or approved application transports. Transport selection would be governed by available interfaces and security policy; MPID is not a reason to bypass network classification, compartment boundaries, encryption requirements, or communications-control orders.

Non-negotiable physical limit

With no viable communications path, no architecture can deliver new remote intelligence to a disconnected operator. MPID must instead support locally valid decisions from cached information, make freshness and uncertainty explicit, and resume properly authorized synchronization when capacity returns.

07 / ILLUSTRATIVE MISSION SCENARIO

Facility North: the information that matters is not always the information that arrives first.

Consider a synthetic field team tasked with maintaining awareness of a protected facility, reporting material changes, and supporting decisions by an authorized operations lead. Information arrives from routine maintenance logs, perimeter sensors, observation reports, and external reporting. This is an invented scenario for evaluating system behavior, not a description of an actual facility or deployment.

T+00Routine traffic

Numerous ordinary status records arrive. They are preserved but do not displace the active mission view merely because they are recent.

T+02Repeated assertion

Three channels repeat a possible access incident, but their content traces to one original report. The model must not inflate confidence by treating the reports as independent.

T+04Consequential change

A new sensor observation suggests a possible unauthorized entry. Its confidence is incomplete, but its potential consequence and decision window justify prominent, explicitly qualified delivery.

T+05Link degradation

Payload capacity drops sharply. The system must choose between transmitting a coherent critical update, routine events, or bulky supporting material.

T+08Contradictory evidence

A second independent observation weakens the earlier interpretation. The update must be elevated to recipients of the original warning, not silently appended to a deferred record.

T+12Connectivity returns

The delivery record is reconciled: which items were received, which expired, what changed, and which recipients may still be operating from outdated information.

Conventional sequence

Chronological or uniform handling may transmit lower-consequence items first. The operator must discover the mission-critical event, reconcile repeated claims, and identify the contradiction from a larger stream.

Proposed MPID sequence

Mission-linked changes are elevated with their provenance and qualifications. Lower-priority material is deferred where permitted; contradictory evidence is actively reconciled and returned to affected recipients.

Neither sequence can be declared superior by assertion. The experiment must measure decision time, correctness, critical omissions, false confidence, cognitive burden, and recovery consistency under identical data and connection profiles.

08 / PROPOSED ENGINEERING REQUIREMENTS

Research principles need inspectable system obligations.

MPID-001Mission binding

Each automated priority disposition shall cite a versioned mission requirement, accountable role, or defined exception policy.

MPID-002Evidence fidelity

Delivered intelligence shall preserve distinctions among observation, source assertion, inference, assessment, and authorized direction.

MPID-003Provenance

Items shall retain source lineage, source-dependence indicators, confidence rationale, relevant timestamps, and contradictory evidence references.

MPID-004Recipient governance

Prioritization shall not override classification, need-to-know, compartmentation, distribution, or other authorized access restrictions.

MPID-005Context completeness

A condensed or transmitted item shall contain or reference the information necessary to prevent a materially misleading interpretation.

MPID-006Adaptive sequencing

Delivery ordering shall be recalculated when mission priorities, item state, decision windows, or available link capacity materially change.

MPID-007Expiry & freshness

Every time-sensitive item shall expose event age, assessment age, expiration or supersession policy, and any uncertainty in time synchronization.

MPID-008Disruption handling

Where supported, the system shall queue eligible packages, preserve delivery state, and distinguish attempted, acknowledged, and verified application-level receipt.

MPID-009Reconciliation

Following disconnection, the system shall identify duplicates, conflicts, superseded reports, changed mission policies, and unresolved delivery gaps.

MPID-010Exception handling

Defined urgent safety and mission-critical exceptions shall remain reviewable and shall not be silently suppressed by routine mission filters.

MPID-011Audit & challenge

Users with appropriate authority shall be able to inspect, challenge, and override a priority disposition with an attributable record.

MPID-012Resource constraints

Queue growth, retransmissions, retention, storage limits, and priority starvation shall be bounded by documented policies and tested failure behavior.

These are provisional research requirements, not a product specification or evidence of compliance. Acceptance criteria, security boundaries, and quantitative thresholds must be established before implementation.

09 / COMPARATIVE TEST & VALIDATION

Decision quality is the constraint on decision speed.

The core MPID claim must be tested with controlled synthetic intelligence streams and repeatable mission tasks. An attractive interface, fewer notifications, smaller files, or higher network throughput cannot by themselves establish decision advantage.

Experimental design.

  1. Define a ground-truth scenario. Establish authorized objectives, decision windows, necessary evidence, plausible distractions, contradictions, and the correct or defensible decision criteria before testing.
  2. Use comparison conditions. Compare a chronological feed, a conventional urgency/traffic-priority approach, and a mission-bound MPID model with equivalent content, operator access, and network profiles.
  3. Vary the information environment. Introduce high reporting volume, duplicate-source propagation, uncertain urgent claims, contradictory independent evidence, and authorized mission changes.
  4. Vary communications independently. Repeat trials across adequate throughput, simulated low-rate links, intermittent windows, complete denial, and reconnection. Account for protocol and security overhead rather than assuming nominal link rate equals usable payload rate.
  5. Measure both benefit and harm. Use repeat trials and, where feasible, trained participant groups with counterbalanced scenarios to assess variation, learning effects, and over-reliance on system priority.
  6. Publish unfavorable outcomes. Disclose missed alerts, erroneous priority promotions, misleading condensation, stale intelligence, and cases where the baseline method performs as well or better.
Time to justified decision

Elapsed time from availability of the necessary evidence to a recorded decision meeting pre-established adequacy criteria.

Decision correctness & calibration

Quality of decisions and whether expressed confidence matches available evidence; compare quality at equivalent decision times.

Critical omission / late-delivery rate

Frequency with which required information fails to reach an authorized recipient before its defined decision window closes.

False promotion & distraction

Frequency and consequence of unsupported urgent alerts, source-dependence errors, and diverted operator attention.

Context & provenance fidelity

Ability to trace condensed messages back to observations, source lineage, contradictions, and relevant analytical limitations.

Degraded-link useful delivery

Share of decision-relevant packages delivered within their usable window, with size, overhead, and acknowledgment conditions recorded.

Recovery consistency

Discrepancies between authoritative and local states after reconnection, including superseded or duplicated items.

Operator cognitive burden

Time, interactions, workload measures, and comprehension tests needed to identify actionable information.

Falsification and failure criteria.

MPID should not be considered successful if it shortens apparent decision time by encouraging premature judgments, conceals contradictory evidence, loses mandatory context, promotes unreliable reporting without qualification, violates recipient authorization, or leaves recipients unaware that their local picture is stale. Nor should reduction in transmitted bytes be treated as a meaningful improvement if necessary intelligence arrives too late.

The principal evaluation is a tradeoff: does MPID improve timeliness while maintaining or improving the correctness, transparency, and authorization of decisions? No numerical improvement, superiority, or production readiness is claimed in this draft.

10 / LIMITATIONS, FAILURE MODES & SAFEGUARDS

Prioritization can create operational blindness if its assumptions are wrong.

MPID's principal risk is not merely technical malfunction. It is the possibility that a system trained or configured to recognize what matters will obscure the first evidence that the mission picture itself is incomplete. The framework must therefore make uncertainty, dissent, unexpected change, and authorized reassessment first-class behaviors.

RISK 01Mission overfitting

An unexpected but consequential event is filtered out. Safeguard: explicit high-consequence exceptions, reviewable suppressions, and periodic inspection of deferred information.

RISK 02Adversarial manipulation

An attacker introduces repetitive or apparently urgent claims to monopolize attention or delivery capacity. Safeguard: provenance, source-dependence checks, bounded promotions, and competing explanations.

RISK 03Misleading compression

Short messages lose uncertainty, scope, or qualifiers. Safeguard: defined minimum semantic context, linked evidence, and rejection of unsafe condensation.

RISK 04Stale local picture

Disconnected recipients mistake cached state for current state. Safeguard: visible data age, validity windows, provenance, and explicit connectivity status.

RISK 05Authority drift

Priority suggestions become de facto commands. Safeguard: separation of recommendation from tasking, attribution, role controls, and human approval requirements.

RISK 06Security externalities

Queued or replicated intelligence increases exposure, and metadata reveals sensitive activity. Safeguard: threat-modelled storage and transmission, minimized metadata, crypto appropriate to environment, and approved access controls.

The architectural model neither establishes the truth of disputed reporting nor guarantees that human operators will avoid bias. Its value must be judged by observable performance and the visibility of failure. Established disruption-tolerant transport and security mechanisms, including those described by RFC 9171 and RFC 9172, should be evaluated where relevant rather than replaced without reason.

11 / RESEARCH & DEVELOPMENT ROADMAP

From published reasoning to a falsifiable capability.

  1. Publish the conceptual model. Define mission requirements, priority dimensions, evidence lineage, delivery state, exclusions, and authority boundaries.
  2. Build a deterministic simulation. Implement synthetic mission streams, multiple source dependencies, event-time semantics, priority policies, and replayable network conditions.
  3. Establish baselines. Compare against chronological and conventional urgency-based delivery methods before optimizing the MPID model.
  4. Test degraded and denied conditions. Simulate constrained link profiles, disconnection, expiration, receiver acknowledgment, and subsequent reconciliation.
  5. Introduce human assessment. Evaluate decision quality and workload with authorized, representative participants where practicable; separate interface effects from policy effects.
  6. Publish reproducible findings. Report scenario parameters, metrics, uncertainty, failure conditions, and architectural revisions; do not present untested claims as validated outcomes.
Current status / Research draft

MPID is a proposed Aerellus R&D initiative. The problem definition, conceptual architecture, preliminary requirements, and test methodology are presented for critical review. This is not a deployed capability, operationally assessed product, procurement response, government-endorsed activity, or completed technical validation.

At the research level, MPID should remain an independently testable architecture. Integration through Command-1 and demonstration through OVRSYT may be explored later only where they improve the clarity of evidence, interoperability, and evaluation.

12 / REFERENCES & SOURCE BOUNDARIES

Prior work, operational context, and original proposals.

MPID's prioritization model and proposed evaluation criteria are Aerellus research positions. The sources below establish related operational requirements and existing network approaches; they do not validate MPID or imply adoption by the cited organizations.

  1. [R2] Cerf et al., RFC 4838. Delay-Tolerant Networking Architecture, IRTF, 2007. Existing architecture for disrupted and intermittently connected networks.
  2. [R3] Burleigh, Fall & Birrane, RFC 9171. Bundle Protocol Version 7, IETF, 2022. Standardized store-carry-forward networking for stressed environments.
  3. [R4] Birrane & McKeever, RFC 9172. Bundle Protocol Security (BPSec), IETF, 2022. Defines integrity and confidentiality services for the Bundle Protocol.
  4. [R5] Aerellus, WP-001. Mission Primacy, discussion draft, 08 October 2026. Establishes mission authority over operational relevance and evidentiary restraint.
Publication status: Research draft · Revision 0.1 · 02 November 2026. Public, unclassified conceptual engineering material. Facility North is synthetic; technical requirements and experiments are proposed, not implemented or validated. Mention of USSOCOM, cited standards, or particular communications technologies does not imply sponsorship, certification, approval, operational deployment, or endorsement.
← Back to Whitepapers
Aerellus / Research & Development · Public, unclassified conceptual materials