SpaceSuit tracks not only the predicted encounter, but how the evidence behind that encounter evolves.

SpaceSuit is WhiteHorseBlade’s orbital decision-intelligence capability for adding longitudinal pair context and neighborhood phase-state context to conjunction assessment.

Traditional conjunction screening asks:

Which objects are predicted to come close?

SpaceSuit adds:

How did this candidate get here? What changed? Is the behavior persisting, relaxing, or changing because the underlying orbital information changed?

And beyond the pair:

What is happening in the surrounding orbital neighborhood at the same time?

SpaceSuit follows the relationship between a protected object and individual candidate objects across successive accepted orbital states.

It preserves:

Target-relative rank
Modeled minimum distance
Predicted TCA
Rank evolution
Pair-state changes
Repeated-state observations
TCA update support
Source identity
Source-chain changes
Orbital-state age
Provenance qualification and withholding

The objective is not simply to identify what is close now.

It is to help determine how the candidate became important, whether that importance persists as new information arrives, and whether an apparent change reflects geometry or a change in the evidence itself.

SpaceSuit also examines the broader promoted orbital neighborhood around the protected asset.

Using the GTFIS temporal-relational framework, SpaceSuit characterizes features including:

Phase
Lock
Persistence
Repeat behavior
Degrees of freedom
Silence
Horizon-band structure

This provides a second layer of information:

PAIR: What is happening between these two objects?

NEIGHBORHOOD: What kind of orbital environment surrounds the protected asset?

A significant individual candidate can therefore be distinguished from a broader change in the surrounding orbital field.

SpaceSuit’s frozen Longitudinal Conjunction Trajectory Discrimination Architecture — LCTDA V1 evaluates candidate relationships across successive strict as-of orbital-state snapshots.

LCTDA performs target-centered H0–72 screening across the accessible catalog population and maintains a longitudinal evidence ledger for candidate objects.

Rather than treating every screening result as an isolated event, LCTDA preserves the evolution of the candidate field while separating:

New catalog snapshots
New orbital pair states
Repeated identical pair states
Source changes
Provenance qualification changes

This prevents repeated processing or changing data sources from being mistaken for independent encounter confirmation.

Orbital information changes.

Its source matters.

Its age matters.

SpaceSuit therefore keeps raw geometry and operational evidence qualification separate.

A candidate can remain highly ranked in the underlying screening results while being withheld from the operator-qualified population when its source information no longer meets the applicable freshness policy.

SpaceSuit preserves both.

That gives operators visibility into:

What the geometry currently says

and

Whether the evidence supporting that result remains qualified for operational review

without silently erasing the historical result.

SpaceSuit can generate a longitudinal history for a specified candidate relative to a protected object.

An operator can inspect how that pair has evolved across accepted orbital states, including:

Rank
Minimum distance
TCA
Source
State freshness
Pair-state changes
Source-chain resets
Qualification status
TCA support

The result is a target-scoped evidence history answering a simple operational question:

SpaceSuit operates at two complementary scales.

What is happening to this specific candidate relationship?

What is happening in the surrounding promoted orbital neighborhood?

Together, these layers provide more context than a single conjunction snapshot.

We don’t just show the conjunction. We show how it got there, what changed along the way, and what the surrounding orbital neighborhood is doing at the same time.

LCTDA V1 was developed using the historical Iridium 33 / Cosmos 2251 collision.

The architecture was then frozen and independently replicated on the THOR-2A / CZ-4 debris encounter without post-result retuning.

In the THOR replay, the eventual encounter counterpart reached #1 at its first eligible observation and remained #1 through every subsequent anchor, while matched controls remained outside the Top 100.

SpaceSuit has also been evaluated against an external TraCSS OCM corpus.

In a completed static-OCM geometry/discrimination test, the frozen discrimination layer recovered:

Three additional detections were associated with the same co-located Nauka / Zarya pair across overlapping evaluation windows.

This test evaluates external geometry transfer and candidate discrimination.

It is not presented as validation of collision probability, maneuver recommendation, or certified operational collision prediction.

Additional longitudinal and operational-source validation remains ongoing.

SpaceSuit is not intended to replace the existing SSA ecosystem.

It is designed to complement:

CDMs
Orbital catalogs
Tracking networks
Orbit determination
Covariance analysis
Probability-of-collision tools
Maneuver planning systems
Operator conjunction-assessment workflows

SpaceSuit is an independent longitudinal analysis layer that helps operators understand how conjunction candidates are evolving, what changed, and why.

Traditional screening asks:

Which objects may come close?

SpaceSuit adds:

How has this candidate evolved relative to the protected asset and the surrounding candidate population?

Did the underlying pair state actually change?

Did the data source change?

Is the information still fresh enough to qualify?

Is the candidate persisting, relaxing, or reorganizing as new orbital information arrives?

What is happening in the surrounding orbital neighborhood?

Space Domain Awareness

Conjunction Triage

Satellite Fleet Monitoring

Constellation Operations

Orbital Traffic Intelligence

Protected-Asset Monitoring

Debris Analysis

Historical Replay

Longitudinal Pair Analysis

Mission Decision Support

SpaceSuit is evolving from operator-triggered analysis toward persistent orbital-state intelligence.

Planned development includes:

Automated orbital-state ingestion

Persistent target-centered screening

GP / SupGP / operator-ephemeris integration

Multi-source evidence comparison

Continuous longitudinal pair histories

Event-driven operator review

Encounter morphology and historical analog research

The governing principle remains:

WhiteHorseBlade is seeking collaboration with:

Satellite Operators

Government & Defense Organizations

Operational Ephemeris Partners

SSA / SDA Organizations

Research Institutions

Integration Partners

Strategic Capital

Legal Entity: GTFIS, LLC
Capability: WhiteHorseBlade SpaceSuit™
Founder: Christopher Wilkerson
UEI: FUAZC3HT5DX7
CAGE: 210E9
Location: Bowling Green, Kentucky
Email: quantummercury@gtfis.com
Web: GTFIS.com
IP: SpaceSuit patent pending

WhiteHorseBlade™ | Powered by GTFIS