What was tested, and what was observed.

Catalog

Which situations can be shown

The catalog records 4 available demonstrations, 35 demonstration scenarios, and 4 demonstration concepts. Those words say which situations can be shown now. The count is not the evidence, and the catalog is not a test report.

Iron Trail is a mission setting. Its available demonstrations are The Path, The Track, The Eyes, The Eyes Again.

The Change, in the Iron Trail setting, is a demonstration concept about whether friendly identity is good enough to trust for mission-support use. Mission-support use of that identity stays constrained until it can be trusted.

Vector Lantern / False Motion remains a demonstration concept. The catalog does not treat environment-fidelity material as integrated V8Y validation.

Tested

What those available demonstrations are for

The available Iron Trail demonstrations keep three capabilities visible in a synthetic relevant environment. Observed results for those demonstrations are not published.

• Separating look-alike causes (Diagnose).
• Naming who can act (Act).
• Checking the required task rather than a healthy neighboring signal (Detect and Verify).

• Iron Trail / The Path — Two reports go stale together. It is for separating one shared path from two separate failures, which do not call the same owner. The check is that both required report flows are fresh again, rather than one radio that looks up. Exercised scope: Separating a shared-path failure from two endpoint failures on simulated scout and UAV report flows. Not published. Available in a briefing.
• Iron Trail / The Track — A track keeps arriving and looks wrong while the network path is still up. It is for separating a source that is losing integrity, a down network, and a fix that still looks valid. A person approves before the source changes. The check is integrity and track age on a source that can be trusted. Exercised scope: Separating a source losing integrity, a down network, and a fix that still looks valid on a simulated position-tracking flow. Not published. Available in a briefing.
• Iron Trail / The Eyes — The aircraft position still updates, and the people who need the pictures cannot use them. It is for separating a crowded path, a stopped camera, and a dying link, which need different owners. The check is that the pictures are usable again while position stays inside its limits. Exercised scope: Separating a crowded shared path, a stopped camera, and a failing link on simulated ISR picture and aircraft-position flows. Not published. Available in a briefing.
• Iron Trail / The Eyes Again — The same late pictures can come from a stopped camera or from the connection. It is for keeping those repairs apart. The check is that usable pictures return while the connection stays within the timing it already met. Exercised scope: Separating a stopped camera from a crowded shared connection when the path was already meeting its timing on simulated ISR picture flows. Not published. Available in a briefing.

Open the demonstration catalog

Observed

What was observed

The available demonstrations were exercised in a synthetic relevant environment. No baseline, degraded-state, or recovered measurements are published here. Results can be discussed in a briefing.

Historical sources in the catalog explain the situation a thread is drawn from. They do not show that V8Y solved those incidents.

What is shown today is the situation, the look-alike causes, who can act when the thread names that person, and the check. Measurements, a published name for the synthetic environment, and primary-source URLs are not in the catalog.

Limits

Environment limits

• The relevant environment in this assessment is synthetic.
• TRL 5 is company-assessed for defined core software. It is not an authority to operate and not a contract.
• The assessment does not cover every scenario in the catalog.
• It is not a production-scale result and not a government certification.
• Demonstrations are outputs of that work. They are not themselves the maturity certification.

Request

Request deeper evidence

Deeper evidence is requested through an evaluation conversation. The structure below is proposed. It is not a commitment.

A mission page is the setting. An available demonstration is a situation the catalog says can be shown now. The proposed evaluation below is a request to examine one situation the participants select.

Marketplace status is separate from this evidence. Awardable listings are on the government acquisition page. Awardable status is not a contract award, funding, endorsement, or technical certification.

Proposed

Proposed unclassified evaluation

Not a commitmentThis is a proposed structure for an unclassified evaluation. It is not a commitment, a funded engagement, or a schedule.

• Environment. A synthetic relevant environment for one catalog situation the participants select. The work stays inside the defined software capability described at company-assessed TRL 5. It is not an operational network, not an authority to operate, and not a claim that every catalog scenario will be exercised.
• Inputs. An unclassified description of the situation, the technology conditions the participant can share, and the mission consequence that has to be preserved or restored. No participant system is assumed to be integrated.
• Loop breaks. Where the loop can stop: detecting the condition, distinguishing the competing causes already named for that situation, supporting an action only inside permitted authority, and checking whether the required capability was preserved or restored.
• Authority constraints. Action stays inside the authority the participant already has. The evaluation does not grant release authority, command authority, or permission to change a participant system. Where a catalog thread says the software may only recommend, that limit stands.
• Success criteria. Participants agree in advance which capability has to be preserved or restored. Those criteria stay separate from observed results. This offer does not publish a measured result.
• Deliverables. A record of the selected situation, the competing causes that were distinguished, the authority limit that applied, what was shown, and what was not shown.
• Next decision. The participant decides whether to request a deeper look, continue through a marketplace listing, or stop. No date is attached to that decision.

A complementary technology or test-environment partner can use the same request. The partner does not have to sell resilience software.

Discuss an evaluation