Chapter 06 · Accepted reporting source
How can many public records become one traceable body of evidence?
CSKE is the evidence engine beneath the stories. It preserves sources, normalizes reusable facts, records what is missing or uncertain, and gives each report an accepted query path back to evidence.
What the evidence shows
What supports this answer
- The reviewed architecture baseline records 703 tables, 1,475 physical foreign keys, and 301 views at its stated post-0363 accepted boundary, with 0364 not run.
- The visual ER delivery covers all 703 tables and 1,475 physical foreign keys through a high-level map, subject maps, family maps, and detailed diagrams.
- The sealed v2.0.1 visual delivery adds search and filtering, keyboard controls, accessible zoom labels, plain-language notation help, and an offline viewer for the 215 exact diagram-source files.
- Reporting contracts narrow what a reporter may claim and preserve distinctions such as source projection versus actual spending and NULL versus zero.
Why it matters
How this changes the question
Before CSKE, a person had to remember where each fact lived and mentally hold its meaning, date, source, and limitations while making a decision. The database makes that shared state of knowing repeatable and inspectable.
How it was created
The working method
- 1
Capture source identity and provenance before extracting reusable facts.
- 2
Normalize only where the source and governance rules support it.
- 3
Keep source evidence, accepted reporting views, and public narrative as separate layers.
- 4
Use fresh read-only queries for current SQL-backed reporting and show refresh failure honestly.
Limits and unresolved work
What this does not yet prove
- Object counts describe architecture, not completeness or correctness of every subject area.
- Some relationships are logical rather than enforced, and some source areas remain unnormalized or unavailable.
- The diagrams are a dated architecture working snapshot, not a live database administration interface.
Open the working evidence
Documents included in this shareable edition
Sources and methodology
These are the principal materials used for this chapter. They establish provenance, not an assertion that every source is complete, current, or officially adopted.
- ER Visual Delivery v2.0.1, sealed August 25, 2026.
- Database architecture and schema-integrity review at the baseline stated within that delivery.
- The public copy is curated to omit local operational evidence and private machine details; the source delivery’s Safari click-through and 637-entry checksum validation are preserved as release evidence.