Acquisition evaluator · interactive training witness

What happens after the vehicle receives sensor data?

Choose an exercise in the left control area. Watch how source observations, their limits, the crew display, and the commander's information brief change. The test uses the existing ATLAS commander-brief projectors and evidence scorer with a public VBK-inspired, vendor-neutral exercise contract.

MODEL ONLY — NOT A VBK EMULATOR CERTIFICATION. This exercise is not connected to a Bradley, Abrams, MAC, SCIP, MAF, TAK server, Army C2 enclave or Signal Sights device. It cannot reproduce undisclosed Army software, safety interlocks, proprietary sensors, real network timing, or effector control. No live targeting or effects exist.
MODELED TRAINING · LOCAL EXERCISE

Take the next information decision.

Review a fictional report, choose an information step, then watch the modeled handoff. Change a condition and see what still needs verification.

No real sensor, recipient or action is connected. Receipt, acknowledgment and understanding stay separate. This tab's replay is temporary; it is not a durable operational record.

Loading the local exercise…

Current modeled stateNot started

The model is loading. No action is being performed.

Authored sourceUnknown
Your reviewPending
Modeled linkUnknown
Scripted receiptNot sent
Modeled recipient availability
Unknown
Modeled acknowledgment
None
Recipient understanding
Unknown
Source observation offset
Unknown
Exercise elapsed time
0 s
Modeled receipt offset
Not produced
State revision
0

Times are fictional exercise offsets, not measured latency. A restored link never makes an old observation current.

Your next information step

Choose deliberately. The model pauses at each decision.

Inspect the modeled event trail

    Change one modeled condition

    Local rules recognize supported phrases. Unrecognized or ambiguous text changes nothing. Typing pauses the run.

    Preview first; confirm before the model changes.

    Help with this exercise

    The explanation above is produced by local rules.

    Optional network request, only when you ask. Use fictional details only. The request sends this modeled workflow and your question without account credentials. AI cannot make a choice or send a report.

    No AI request made. Local rules work without AI.

    1. See every stage, including what is missing

    SOURCE
    Existing Army/OEM system

    Proposed approved read-only data product; mock values here

    NORMALIZE
    ATLAS connector

    Source, units, observed time, evidence class and quality

    RECONCILE
    Evidence / tracks

    Do observations describe the same object? UNKNOWN until independently proven

    PRESENT
    Crew and commander

    Know, unknown, next information request, ownership

    VERIFY
    Recipient receipt

    NOT SENT in training; live source/recipient workflow is separate

    Choose a scenario

    Problem and operational context

    No exercise loaded

    ConditionUNKNOWN
    Ownship movement (fictional)UNKNOWN
    Current stage—
    Operator explanation—
    Exact source field visibility

    No measurement selected.

    Source / timeNOT CONNECTED
    Evidence classSIMULATION ONLY
    Read-only contractNot Army's actual ICD

    2. Soldier / vehicle crew

    What just happenedNO VERIFIED SENSOR INPUT
    Facts and source limitationsUNKNOWN
    Immediate information stepRequest an authorized sensor report

    3. Commander / protection staff

    Bottom lineNo operational report.
    What we knowUNKNOWN
    What we don't knowUNKNOWN
    Next human-reviewed information actionNo command
    Approval / effects boundaryNO EFFECTS AVAILABLE
    Recipient receiptNOT SENT

    4. What the Government evaluator can actually measure

    Track identity truth checkNOT FIELD VERIFIED

    No labeled track ledger yet.

    False recognition controlsNOT FIELD VERIFIED

    No simulated event counts toward 99.5% independently validated real-world accuracy.

    Receipt / authorityNOT SENT

    No military data link, crew authorization or recipient has been connected.

    What the trace contains
    Select a scenario to inspect trace provenance.

    5. How we interface with existing Army systems

    VBK physical connectivity does not imply permitted read access to its message contracts. This table describes candidate integration paths and the evidence required to qualify each one.

    Source / systemProposed integrationCurrently demonstratedNext required gate
    Bradley VBK Gen3 / MAC / MAFApproved read-only data product from OEM/Government gatewayPublic interface concept + vendor-neutral exercise schema onlyArmy ICD, version, physical connection and witness
    Acoustic arraysSource-specific sound feature and quality contractATLAS acoustic modules and synthetic test evidenceActual array, time sync and independent field truth
    RF, radar, EO/IRSeparate authorized adapter per device / data typeExisting ATLAS fusion/adapter software and bounded test harnessOEM schema, actual measurement fidelity and independent match performance
    TAK / CoTAuthorized information-only CoT exchange and named receiptExisting ATLAS software translator and partner routesApproved server/endpoints, recipient and actual transport witness
    Signal Sights / UnityVersioned ATLAS partner JSON snapshot → Unity presentationCode-backed partner API and Unity client patternPartner device/session witness, latency and role-specific usability
    Other Army / DoD programsOne approved ICD and supported transport adapter per programNOT universally integrated or certifiedSystem owner, data rights, compliance profile and an acceptance exercise
    The upcoming Ground Maneuver CSO permits Phase 1 concept and technical merit evidence. A training witness is a legitimate explanation of architecture—but does not replace a qualifying C-UAS sensor capability or the Government's performance questionnaire. The Spring 2027 physical demonstration is a later stage.