Clause BIB: Bibliography

What the clause requires

What the public text does not state

• Every bibliography entry

What it means for you

The bibliography is where the base standard names the papers and standards it draws on. It is not normative and it creates no duty. It is still useful, because it tells a reviewer which constructions and which prior work the committee had in view.

The record does not list the entries. A bibliography assembled from citations found elsewhere would look complete and could misattribute a reference. The page states the location and leaves the content to the purchased text. When the base standard is bought, the bibliography is a short read and a useful check on whether the team has understood the lineage of the two cipher families.

For the buyer, the bibliography is a reading list for the engineering team, not an evidence item. The record marks it as supporting material and keeps it out of the evidence sheet in the kit, so the register stays focused on artefacts an auditor will ask for. A design rationale that cites the purchased bibliography is a nice extra, not a required row.

The page also marks a boundary. The ISO public preview stops before the bibliography, so the record cannot say which papers are listed or whether a paper is normative in another document. Rather than guess, the page gives the location, the role and the limit. That is the same treatment every unheld unit receives.

Evidence to keep

What an auditor or a customer is likely to ask for

Artefact	Owner	Why it matters
Reading list or design rationale that cites the purchased bibliography	Engineering	Shows the team read the standard s sources, not only a summary.

How to verify it

No audit test. This page is supporting material.

Dates

The kit plan for clause BIB sets the evidence review at 17 June 2027, 90 days before the estimated publication date of 15 September 2027.

Cross references

• 1 Scope
• 6 Deoxys-TBC
• 7 Skinny

Where this comes from