Audit packet
2026-09-27 to 2026-09-27
Generated 2026-09-27 18:58:04 UTC · packet pk_tpnq6rPmArd_S0SY · format v2
Sample audit packet, built from public entities so anyone can inspect the deliverable. A customer packet covers the account holder's own monitored roster.
Anyone with the link can view this packet, including the monitored entity names on it. The packet is sealed and will not change; sharing the link shares the sealed evidence. Closing an account does not erase identity already sealed in issued packets.
Evidence downloads
Technical formats for archiving and independent verification. The PDF above is the copy to read; these are the copies to keep.
Review summary
- Monitored entities
- 1
- Included verification records
- 2
- Included check dates
- Loading dates...
- Packet proofs
- Signature and timestamp attached
The reporting period is not a claim of continuous monitoring. Each entity's monitored window and recorded cadence gaps appear below.
Account monitoring is sealed as 1 interval with recorded start and end reasons. Cadence is assessed only inside those intervals.
Recorded exclusion findings
Reading the complete sealed record summary...
Counts include repeated checks of the same entity. A potential match is not identity confirmation.
Coverage timelines are recorded for 1 of 1 entities. Check dates and source dates are separate. The packet documents evidence of diligence, not a compliance verdict.
Changes and cadence gaps
Recorded changes and gaps are separate from the exclusion-check findings in the summary. Expand an entity to inspect every recorded event.
Recorded changes · 0
No changes are recorded in this packet.
Recorded cadence gaps · 0
Coverage timelines are recorded for 1 of 1 monitored entities. Missing timelines are not zero-gap findings.
No gaps are listed in the recorded timelines.
Monitored entities
Open an entity for its dated outcomes, coverage timeline, and recorded statements.
THE BOEING COMPANY · 2 checksNU2UC8MX6NK1 · roster membership in packet: 2026-09-27 to 2026-09-27 · 1 monitoring interval
NU2UC8MX6NK1 · CAGE 08903 · vendor · matched by UEI · added to roster 2026-09-27
2 checks in the period · last 2026-09-27: SAM status Active; registration expiration 2026-11-13; no active exclusion record matched · exact UEI plus registry candidates · exclusion-match-v1
Coverage: first check 2026-09-27 · last check 2026-09-27 · 1 registration re-check · 1-day cadence
Account monitoring intervals
Monitored from 2026-09-27 06:20:56 UTC (still open at packet generation) · start: added to the roster
Verification records
Browse 2 verification records
Browse the 2 records sealed in this packet by entity, date, source, kind, and outcome. Each row links to its permanent record. The check date and source as-of date are shown separately.
0 records match · showing 0 to 0 · read from the sealed packet payload
No records in this packet match the filters above.
Sources
2 sealed source snapshots. Expand a source to inspect its dated snapshots, hashes, retrieval times, and recorded completeness facts. Source dates are not check dates or a promise of continuous coverage.
SAM.gov entity registrations · daily extract · 1 snapshot · as of 2026-09-27
SAM.gov Exclusions · 1 snapshot · as of 2026-09-26
Packet integrity
- Content checksum
- SHA-256 recorded
- Issuer signature
- Attached
- Scope: This packet · issued 2026-09-27 18:58:05 UTC
- Independent timestamp
- Attached (DigiCert)
- Timestamp states 2026-09-27 18:58:05 UTC.
- Daily-run inclusion proof
- Not attached
- Transparency Service receipt
- Not attached
- Browser validation
- Not checked in this browser
The attached issuer statement commits to the canonical bytes of this packet through a hash envelope. Attachment alone does not mean the signature or timestamp has been validated in this browser.
A daily-run inclusion proof is not an independent Transparency Service receipt. Integrity proofs do not establish source truth, data freshness, matching correctness, check execution time, or legal compliance.
Browser validation uses issuer key history fetched separately from this site. Offline validation requires a trusted copy obtained independently.
SCITT and technical integrity details
Packet integrity is separate from the proofs attached to each referenced verification record.
Packet content seal
faacefb334b97460ed60577c208e27062ca9f04ec8f2bbe0cd3f488efa6b0bec
format v2 · RFC 8785 (JCS)
Complete record index
2 records · 916 compressed bytes · gzip
sha256 80933c8426160abeb413ee8b7eaed7e8d007620dc83366eb9b1bcb19cfa32d99
Download the complete record indexIssuer signature and timestamp
SCITT Signed Statement issued 2026-09-27 18:58:05 UTC with PS256 over a SHA-256 hash envelope committing to the canonical packet bytes. Key zWmfXN5fsjZDIEJaTfLDOVVwGqRFekrmyGyHF4FXMYw. Statement SHA-256 6384ea244c14b33f0ee67dde7a3990a027f5bb57b46203268f17023e368569f9.
DigiCert timestamped the RFC 9921 signature imprint 2026-09-27 18:58:05 UTC under policy 2.16.840.1.114412.7.1. When valid, the timestamp establishes that the issuer signature existed no later than the Timestamp Authority's time. It does not prove source truth, matching correctness, check execution time, identity, or a legal outcome.
No independent Transparency Service receipt is attached.
This seal is the SHA-256 hash of the RFC 8785 canonical UTF-8 bytes of the packet payload. To recompute it, download the JSON, canonicalize its record field with RFC 8785, compute SHA-256 over those UTF-8 bytes, and compare it to the seal above. A mismatch detects changed canonical bytes. A matching checksum alone does not authenticate federal.contractors as issuer or establish independent time. The payload references every verification record by id, format version, and seal, so each referenced seal can be recomputed from its download. An audit packet documents that these checks ran against the sources listed, at the times stated. It is evidence of diligence, not a verdict.
Referenced daily monitoring runs
1 sealed daily run binds the scheduled record digests under dated RFC 9162 roots, and each record in a sealed run carries its own inclusion proof. The complete list is sealed in the packet JSON.
mr_mFwbqR5Oyv4YWojv · 1 records · complete
root 82fabe6926f0356f430b41be9dee705c8f3fee2d332e7a57ad3f947f725e1333
Methodology
Read methodology and regulatory coverage
Exclusion checks use the SAM.gov exclusions public extract. Each sealed record names the exact source snapshot, content hash, and source as-of date. Identities are established by exact UEI, exact CAGE code, or a name match confirmed by the account holder. Ambiguity is never silently resolved. A free SAM.gov search is sufficient for compliance with 2 CFR 180.300. This service sells documentation, coverage, and time. It is evidence of diligence, not a verdict.
Regulatory coverage map
This map states what the packet contains for each test area. It does not state how an auditor will judge the evidence.
2 CFR 200.332(a) and 2 CFR 180.300
This packet contains 0 monitored subrecipient entries, 0 dated check records linked to those entries, 0 customer-supplied certification or clause statements, and a per-entity coverage timeline.
2 CFR 200.318(h) with 2 CFR 180.300
This packet contains 1 monitored vendor or subcontractor entry, 2 dated check records linked to those entries, 0 customer-supplied certification or clause statements, and a per-entity coverage timeline.
Compliance Supplement Part 3, section I, Procurement and Suspension and Debarment
This packet contains 1 monitored entity, 2 sealed verification records, 0 detected changes, 1 sealed daily monitoring run, 2 source snapshots, 1 recorded monitoring interval, and 0 recorded monitoring interruptions for the selected period.
This packet: https://federal.contractors/packet/pk_tpnq6rPmArd_S0SY