This page is not official. It is a citizen concept built from the public record. NASA's official RFP on SAM.gov →
The Integrated Data Requirements Document is a 246-page PDF. This explorer renders its requirements register so that offerors, NASA, and the public read the same contract the same way. Every record links back to the exact page it came from.
Each cell is one deliverable, sized by its requirement count and colored by NASA Data Type: does NASA approve it, review it, or simply receive it? Click a cell to browse its requirements.
The same sentence appears in dozens of DRDs, and each recurring clause counts once per deliverable that carries it. Hover a clause to light up those deliverables on the 98-DRD strip.
Full text search plus facets. Click any row for the verbatim source language and provenance.
| ID | Requirement (analysis text) | Actor | Modality | Section | PDF p. |
|---|
The contract's effective size extends beyond the PDF. CLDP program documents dominate: CLDP-REQ-1130 alone is incorporated from 30 separate DRD families. Click a row to see the citing families and the title and revision variants observed in the source, which the register preserves rather than silently merging.
Every extraction repair and source discrepancy is recorded, including four DRD headings whose printed numbers (CLDC-214.x) disagree with the official register (CLDC-211.x).
Coverage and commentary from the space-industry press, linked to the records it discusses.
"It's got all the requirements, deliverables, and clauses of a cost-plus contract, but they are stuffed into a firm fixed-price bag."
Weigh the claim against the data: 53 of 98 approval-gated deliverables · 30% recurring boilerplate · 94 incorporated documents.
Draft-RFP questions go through the official channel, and answers usually come back as amendments buried in attachment lists. A modern solicitation would accept questions where offerors read the requirements and publish every answer beside the records it affects.
concept: also accepted as MCP tool submit_question · this page never collects your question, the official record does
NASA issues offeror templates as Excel workbooks on the SAM.gov record. A modern RFP would publish each workbook with a machine-readable schema so vendors can validate a response before they submit it. Below is how that could look.
Humans get the explorer. Agents get the same register in formats they can consume directly, published alongside the PDF rather than in place of it.
Every DRD as clean markdown at a stable URL like /md/CLDC-116.md, with an
llms.txt index so agents can discover the corpus without scraping the PDF.
The five registers (requirements · source-items · references · anomalies · families)
served raw with provenance and the source SHA-256, one record per line.
Query the register from Claude, or any MCP client:
{
"mcpServers": {
"cldc-requirements": {
"url": "https://cldc.example.gov/mcp"
}
}
}
tools: search_requirements · get_drd · trace_provenance · list_references
A public roster where participants declare their intended response scope and partnership interests, so the information doesn't live in emailed PDFs. Entries below are illustrative placeholders, not actual declarations.
A concept: providers registered with NASA to help offerors prepare compliant responses, listed by specialty so that small and first-time bidders can afford to compete. A registration is a listing, not a NASA endorsement.
Catch the preventable. Cultivate the possible.
83 of this draft RFP's 2,995 requirements mention risk, and CLDC-116 is an entire Risk Management Plan deliverable. RiskThing helps CLDC responders organize, communicate, and mitigate their risks, from RFP requirement to closure, with the authority, audit, and export-control guarantees that regulated industries require.
riskthing.com →