For attorneys, compliance officers, and audit teams. The regulatory mapping behind Eagle's operating posture — how the platform aligns to 28 CFR Part 23, the governance SOP, audit-log architecture, and the categorical hard lines that bound the product. The plain-language version of this material is on the About page.
28 CFR Part 23 is the federal regulation governing criminal intelligence systems operating under federally-funded grants. Eagle.report does not claim to be a criminal intelligence system within the regulatory definition — but every component that touches pattern detection or aggregated case data treats Part 23 as the operational floor. The four functional areas of Part 23 (collection, dissemination, audit/review, governance) and how Eagle implements each:
Information is retained only when reasonable suspicion exists that the subject is involved in criminal conduct relevant to a cargo-theft case. Single-incident touches do not generate retention.
Pattern output is referred only to LE personnel with right-to-know and need-to-know on a specific active case. No bulk disclosure, no resale, no commercial product built on pattern data.
Every read, every write, every referral is logged. Audit trail designed to survive Brady and Daubert challenges three years after the fact.
Standing operating procedure document, drafted by a senior analyst hire and reviewed by transactional counsel with intelligence-handling experience. Available on request to FMCSA, NICB, RISS, and any LE partner.
The Eagle governance SOP is a standing operational document, drafted by the senior intelligence advisor and reviewed by transactional counsel with intelligence-handling experience. It is filed as the controlling policy for every pattern-detection decision, every referral to law enforcement, and every retention determination.
The SOP governs every Eagle workflow that touches pattern data, case linkages, or any subject identifier (named individual, MC, DOT, address, phone). It does not govern intake-level workflows on a single active case (those are governed by the case-team visibility tier rules).
Every pattern flag entering analyst review terminates in one of three determinations. The negative-case (insufficient) determinations are logged with the same rigor as positive referrals — see § 5.
Eagle's open-source intelligence ingest is mediated through licensed vendor relationships (e.g., social-graph providers, public-records aggregators). Direct scraping is prohibited. This posture is structural: it shifts terms-of-service compliance to the vendor and provides a contractual audit chain.
The audit log is the load-bearing technical artifact for Eagle's compliance posture. It is designed to survive hostile defense review under Brady disclosure and Daubert reliability challenges three years after the fact.
Logs are append-only, write-once-read-many (WORM) storage with cryptographic chain-of-custody. Periodic Merkle-root attestation against a third-party witness service provides external tamper-evidence. Log retention exceeds the longest applicable statute of limitations for the case types Eagle touches.
The negative-case discipline log records pattern flags that were reviewed and dismissed. This is a load-bearing 28 CFR Part 23 practice: it prevents drift into permanent watch lists, documents analyst judgment, and proves the analyst layer is not a rubber stamp.
Without negative-case discipline, an "investigative lead worth attention" can quietly accrete into a de facto watch list — the failure mode most likely to trigger 42 U.S.C. § 1983 exposure and 28 CFR Part 23 audit findings. The NCL is the structural prevention.
Plain-language version of this material is on the About page. The statutory anchors below are the legal floor.
Cargo-theft cases that go to federal prosecution will face defense motions on the reliability of any pattern-derived evidence. Eagle's audit architecture is designed to produce, under subpoena, the complete record of what was decided, by whom, on what basis, and with what reasoning.
Eagle's negative-case discipline log is the load-bearing artifact for Brady compliance. If a pattern detector was evaluated on a defendant and produced an "insufficient" determination, that determination is logged and producible.
If a federal magistrate evaluates the reliability of Eagle-derived pattern evidence under Daubert, the audit log + governance SOP + 28 CFR Part 23 procedural compliance documentation are designed to constitute the reliability showing.
Cross-reference of all federal statutes, regulations, and agency policy documents Eagle's compliance posture is anchored to.
For verified law-enforcement partners, prosecutorial offices, and counsel reviewing the Eagle.report compliance posture: the full governance SOP, audit-log schema, and OSINT vendor-licensing terms are available on request.
Contact liaison@eagle.report with your agency, role, and the specific compliance area you'd like to review. Typical turnaround: 24 hours for verified-partner requests.
The About page covers the same material in the form a working LEO would prefer.