V17.7 rigor infrastructure
Scholarly Verification and Corpus Consolidation
This section distinguishes a normalized source record from verified bibliographic metadata, a source-level citation from a claim-level locator, and structural completeness from scholarly completion. It also reconciles the live runtime counts into one canonical release manifest.
Canonical runtime
Count reconciliation
These figures are calculated from the live collections after every compatibility overlay has loaded. They are the authoritative V17.7 runtime counts.
Source control
Five-stage verification
Metadata verification, locator precision, direct primary inspection, and scholarly review are independent stages.
| Source | Metadata | Locator | Primary | Review | Overall |
|---|
Claim-level audit
Event-claim verification ledger
All 528 event-level statements are classified according to their actual source and locator support.
| Grade | Event | Claim | Status | Locator | Reason |
|---|
Editorial depth
Record-completeness dashboard
A record may be structurally valid while still lacking the summary, role, passage, object number, or source detail needed for publication-quality use.
Semantic integrity
Rules beyond broken-link testing
These checks test relationships between claims, events, sources, ranges, and genealogy endpoints.
Consolidation boundary
What V17.7 consolidates
V17.7 establishes one canonical runtime manifest and one verification ledger after the existing compatibility layers load. Legacy versioned data files remain in the package for backward compatibility, but their stale release counts are no longer authoritative. A later architectural release can replace the compatibility layers with generated canonical bundles without changing the research content.