The Digital Thread keeps who the asset is, which effects were permitted on it, and what was observed, across its mission life.
Mission assets change custody, software, and permitted uses. A parts list or a wiki page does not prove which effect was authorized at a given time.
Program, sustainment, and mission-ops teams that must reconstruct an asset's governed history for review, not a public encyclopedia of platforms.
Hood supplies a HIOP-backed lifecycle record: identity of the asset, CRUSHIA decisions about effects on that asset, and Fossil evidence of what followed. Hood does not operate the mission.
Effects on the asset are evaluated as bounded requests: this actor, this asset, this effect, now. Historical permission does not automatically extend to a new effect class.
A time-ordered thread of identity bindings, authority decisions, and observed outcomes for that asset. It is a Hood record, not a classified intelligence product.
Described as an evaluation and mission-integration direction. Delivery requires written scope. No fielded military use is claimed here.
Not a classified system, not an ATO, and not evidence of a live program of record. Simulated/not-live until a written Hood engagement says otherwise.