YG Yusuf Ghyasi FOUNDER · ENGINEER
Profile 01 Agaro 03 Work 04 Doctrine 05 Research Contact
← ARCHIVE TF-009
ATLAS FEDERAL INTELLIGENCE FLAGSHIP

From Award Records to an Intelligence Layer

Gathering SAM.gov and USAspending data is table stakes. Finding TF-009 is what Atlas does next: an AI research layer that profiles companies, their recent awards, the award amounts, and the vehicles they win through, with every claim traceable to a record.

YUSUF GHYASI September 8, 2026 11 MIN READ

The pipeline described in the previous finding produces clean data. Clean data is not intelligence. Nobody makes a decision because a database is normalized. Intelligence is what happens when a system answers the questions a federal contractor actually wakes up with: who is winning work like mine, where are they winning it, through which vehicles, at what values, and what changed since I last looked. This finding is about the layer Atlas built to answer those, and the role the AI model plays in it.

The unit of analysis is the company

Federal data is organized around awards. Customers think about companies. The bridge between those two views is the first product decision: Atlas maintains a living profile per company, assembled from its award and transaction records. Recent awards in chronological order. Award amounts, separated honestly into ceiling versus obligated versus outlaid. The vehicles those awards ride on, because a GSA schedule, an IDIQ contract, a GWAC, and a BPA are not interchangeable, and which vehicle a competitor holds tells you what they can bid on next without recompete. Agency mix, NAICS mix, place of performance patterns, and teaming relationships visible in the data.

Building that profile is where the AI model earns its place. The records themselves are fragmented: a company’s history spans thousands of transactions with inconsistent naming, amendments, and multi award vehicles where “the company won” needs unpacking into which pool, which task orders, which ceiling. The model’s job is research at scale: reading across those records and producing a coherent company profile that a human analyst would take days to assemble and that refreshes continuously as new records land.

Grounding is not optional

An AI layer over factual data lives or dies on grounding, and in federal sales, being confidently wrong is worse than having no answer. So every claim the research layer produces carries provenance: the specific award or transaction records behind it, linked and inspectable. The model summarizes and organizes records. It does not invent figures. Where the data is silent, for example obligations not yet reported by an agency, the profile says so rather than interpolating.

The architecture that makes this work is retrieval first. Questions against a company or a market resolve to targeted queries against the canonical entities, the model works from the returned records, and its output is a structured summary with citations, not free prose. When a customer clicks a number, they land on the award records that produced it. That click is the entire trust model.

Research as a standing process, not a report

The second departure from the analyst model is that research never finishes. Atlas watches the feeds continuously, and when new records touch a company a customer tracks, a competitor wins an adjacent award, a vehicle a customer depends on approaches expiry, a new solicitation matches a capability profile, the research layer updates the affected profiles and decides whether the change is worth surfacing.

That decision, to surface or not, is deliberately where the autonomy stops. The system notices on its own. It acts only by raising the finding to a human, never by contacting anyone, drafting a bid, or committing anything on the customer’s behalf. In a domain where a wrong autonomous action is unacceptable, the initiative lives entirely in the noticing, and the acting stays gated.

What the layer enables

The reason this layer matters commercially is that it converts public data into customer software. A federal contractor using Atlas gets competitor profiles, vehicle intelligence, and change alerts that would otherwise require a research team, and the same substrate powers the things I build for individual clients: market maps, capture targets, capability matches. The finding I would leave another builder with is the shape of it. Gather the public data honestly. Normalize it with provenance. Then let a model do what models are actually good at, reading volume and organizing it into answers, while the architecture guarantees that every answer still points back at the records. That is an intelligence layer. Everything less is a search box over a spreadsheet.

ATLASAI-RESEARCHGOVCONSAM.GOVUSASPENDINGINTELLIGENCE