This page summarizes why the predictive-guidance capability merits serious review. It does not present historical simulation results as proof of performance against current threats.
Surviving summaries describe six-degree-of-freedom work on the earlier HAG implementation. Because the complete original Coleman/Mann report is not presently available for public linking, this item is treated as contextual rather than primary public evidence.
Government evaluators compared guidance performance without access to the proprietary algorithms and identified a possible follow-on path.
Radiance Technologies conducted additional engineering work, while Lt. Gen. Henry “Trey” Obering documented the Missile Defense Agency view that HAG “warrants further evaluation.”
HAG object code was integrated into a government-controlled, high-fidelity six-degree-of-freedom interceptor simulation for a phased comparative test.
Michael C. Schexnayder described a long government and independent test history and reported improved performance against selected maneuvering targets while retaining performance against nonmaneuvering targets.
A staged, protected approach was identified: object-code screening and simulation first, then hardware-in-the-loop and flight testing if performance justified progression.
The Army’s public-release report describes a black-box comparison in which the proprietary design was not disclosed to the test team. After integration and optimization, the configuration was locked for runs of record. Baseline and predictive-guidance cases used the same platform, compilers, initial seeds, and target-state information; the terminal guidance code was the controlled difference.
The Army also reported that no single guidance law performed well against every threat. Its conclusion emphasized the value of combining guidance approaches—a particularly relevant point for a complementary guidance layer rather than an all-purpose replacement.
The public report found added performance in 12 principal cases, parity in four more, and no single guidance law best across every threat.
The results support examining a predictive layer as a complement to selected modern guidance architectures.
How does a modern implementation compare with the selected current baseline against today’s representative threats?
The surviving record points to an accumulation of non-performance barriers: source-code disclosure, intellectual-property protection, classified-access requirements, personnel dependency, contracting structure, facility-clearance issues, and export-control or provenance questions.
A protected object-code-first pathway was later identified, but the program did not progress through contemporary hardware-in-the-loop and flight testing. The technical question was therefore never definitively settled through the full modern validation sequence.
This account does not allege conspiracy, theft, sabotage, or deliberate suppression. It distinguishes promising simulation evidence from the transition steps that were never completed.
The strongest use of the historical record is not to claim operational proof. It is to justify an efficient modern test in which the customer controls the architecture, threat set, interfaces, metrics, and decision gates.
Each source should be judged for what it establishes—and for what it does not. Public documents are linked directly when appropriate; additional records can be reviewed in a controlled setting.
Establishes the public Army test design, black-box integration, threat-set structure, comparative result, and conclusion. The linked edition preserves the Army report and places separately labeled commentary beside it.
Does not establish: operational certification or performance against current hypersonic threats.
Open the report and labeled commentary →Supports the sequence of external review and the documented 2004 judgment that the concept warranted further evaluation.
Does not establish: adoption by MDA or present-day superiority.
Request controlled review →Supports the length and seriousness of the historical government and independent test record and reported improvement for selected interceptors.
Does not establish: the separate 98–99 percent performance claim or current operational readiness.
Request controlled review →Documents a practical protected sequence: examine object code and simulation performance, then move to HIL and flight testing if justified.
Does not establish: that those later stages were completed.
Request controlled review →Controlled technical review
Source documents can be made available for an appropriate technical review, subject to intellectual-property, security, and export-control safeguards.
hello@hittokill.com