Atlas^™

Atlas shows what a development is connected to, and how those connections have moved.

It maintains the durable picture a signal has to be read against: companies, programs, ownership, relationships and dependencies, kept with their history so any date can be read as it was recorded.

Product scope and availability. These pages describe product roles and intended workflows. Product and source coverage are subject to qualification for each engagement. Production access requires separate approval. Public intake is closed.

When teams use it

Reading a competitorSee who holds adjacent awards, who receives sub-awards from whom, and through which partners.

Before teamingCheck a prospective partner's relationships and how they have changed over time.

When a supplier changes handsSee ownership and dependency structure, with the earlier relationship retained as earlier rather than overwritten.

A structural change, as Atlas records it

Synthetic specimen. No real company, agency or award.

A subcontractor on a watched program has a new parent; its sub-award from you is unchanged

Read as of1 Oct 2026

Compared with1 Jan 2026

Changed1 of 4 joins

Program office SPEC-P2Prime award to your organization. Unchanged.

Subcontractor ASub-award from your organization. Unchanged.

Subcontractor BParent: ~~Holding company X~~ Holding company Y, recorded 14 Aug 2026. The earlier parent stays on the record at its own dates.

Subcontractor CIdentifier could not be resolved to one entity. Held as unresolved rather than guessed.

Core workflows

What a Atlas user does

01Resolve an entity. One durable identity for a company or program, held across sources and over time.
02Read its relationships. Ownership, teaming, prime awards and sub-awards, each joined to the record it came from.
03Move through time. Read the structure as it was recorded at any date, not only as it looks today.
04See what changed. A changed relationship keeps the earlier one, dated, beside the current one.
05Hold the unresolved. An identifier that cannot be resolved stays unresolved rather than being guessed.
06Hand off. Open the same entity in Strike^™ or Vector^™ without losing your place.

Across Pyrnova^™

Atlas hands off on the same object

Evidence and governance

ProvenanceEvery relationship cites the source record it was drawn from and when that was retrieved.

HistoryStructure is added to, never rewritten. Earlier relationships stay readable at their own dates.

GapsWhat cannot be joined or resolved is shown as a gap, never drawn as a relationship.