Methodology
From source file to public record
BlueBook treats each release as a traceable record set. The public page is the last stop, not the source of truth. When a record is wrong, the correction path starts with the original file and moves forward through document reading, summary writing, indexing, and presentation.
Preserving the source
Each released file keeps its original source link and identifying metadata. The original document remains the reference point whenever a public page, summary, or correction is checked.
Reading the documents
Text documents are read as source text, while image-only pages are described from the page image. Those notes help identify names, dates, places, objects, and quotes without replacing the source file.
Writing public summaries
Draft summaries are written from the source text and page descriptions, then shown with visible source links and review notes. The site should make clear what came from the record and what is editorial framing.
Corrections
Correction reports are checked against the original file first. When something is wrong, the fix should start at the earliest incorrect step so the same error does not reappear elsewhere.
Correction evidence required
A report is actionable when it identifies the page, the incorrect public field, the expected source-backed value, and the source file or quote that supports the change. If the source is ambiguous, BlueBook should mark the record uncertain rather than forcing a confident claim.