Aleph doesn’t hand you a compliance score. It hands you a list of requirements, each one naming the exact provision behind it — down to the paragraph, like 16 CFR 1110.11(a)(1) — so you can read the rule yourself and decide whether we got it right.
A green tick tells you what some software concluded. It doesn’t tell you what rule it applied, whether that rule is the current one, or whether it applies to your product at all.
When an inspector, a customer’s quality team or your own counsel asks why you did something, “the software said so” is not a position. The citation is what turns a checklist into a defense.
Being pointed at “16 CFR Part 1110” and told something applies still leaves you reading the whole part to find the sentence. The paragraph is where the obligation actually sits.
Each requirement in Aleph carries its own citation. A requirement cannot exist in the system without one.
Not “Part 1110” but 16 CFR 1110.11(a)(1). A part, a section, and the specific paragraph — the level at which you can actually read the sentence that creates the duty.
Citations reach both the Code of Federal Regulations — 16 CFR for consumer products, 21 CFR for food and cosmetics — and the underlying statutes at 15 and 21 U.S.C. where the duty starts in the law itself — plus the California statute and regulations behind Prop 65.
The requirement list carries a version stamp, and each source records when someone last read it from the primary text — so when a requirement is corrected, we can tell which answers came from the earlier reading.
Foreign Supplier Verification Programs, cited through 21 CFR Part 1 — the subpart L sections covering hazard analysis, supplier evaluation, verification activities and records.
Children’s Product Certificates and General Certificates of Conformity, cited through 16 CFR 1107 and 1110, plus the certification duty at 15 U.S.C. 2063(a)(1).
California’s warning requirements and cosmetics obligations under MoCRA at 21 U.S.C. — each requirement carrying the provision it derives from.
Naming the paragraph tells you where a requirement comes from and lets you check it against the regulation yourself. It is not a legal opinion, and Aleph does not tell you that you are compliant — it keeps the record of what you did, cited, so that you or your counsel can make that judgment. Regulations change, so check a citation against the current text before you rely on it.