Chronicle naming: align prose surfaces (fixes #83) - #94
Merged
Conversation
#83) Ledger -> Chronicle across docstrings, comments, doctrine wording, routing/annotation strings, regenerated lane notes, and app copy. Frozen per the issue: data/ledger/ paths, the ledger_fact column and field names, uk-admin-*/be-admin-* fact-id prefixes, Python identifiers, and machine summary keys. Routing strings sit outside the fact_id hash (verified: zero fact-id drift across the 1,080 regenerated rows). The two Populace-targets shape headers modernize to Microcosm per microcosm#639. sources/ archives and diagnosis/ audit records stay verbatim. Fixes #83 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Test comments/heading and the accounting-drift diagnostic now say Chronicle (machine keys stay frozen); new test_fact_accounting_drift_fails_loudly exercises the fact-list branch of the drift gate, mirroring the claims case. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements #83 exactly as proposed there: prose surfaces say Chronicle; frozen machine surfaces keep their legacy
ledgernames.Renamed (prose)
scorecard_db/(ingest_uk_externals,models,relationships,build_db,ingest_uk_deductions) andbe/ingest_jrc_country_report.py"ledger: …"→"chronicle: …"on staged facts (bothdata/ledger/*.jsonlregenerated viabuild_db)data/lanes.json+ app copy, dual-copy test green)docs/mechanics-audit.md,docs/SCHEMA_NOTES.md, both READMEsstartswith("chronicle"), error-message match)Frozen (unchanged, per #83)
data/ledger/committed paths;ledger_factcolumn/field names;uk-admin-*/be-admin-*fact-id prefixesLEDGER_PATH,_ledger_row) and machine summary keys ("ledger","ledger_facts","ledger_path")sources/archives (sha-pinned manifests) anddiagnosis/audit records — recorded text stays verbatimapp/src/globals.css"every figure in the ledger" — generic English, not the productVerified
ruff format --checkclean; post-suite tree drift zero (no-drift gates should pass)Post-merge: redeploy both Vercel projects (repo-linked + the dual-mount proxied one, #84 recipe) so the app copy updates.
🤖 Generated with Claude Code