Source Ledger · local-only utility · 26 July 2026
Provenance before personalization.
A source-aware publishing system needs a record of what it may use, what it must not expose, and which version it supplied. The Source Ledger Validator checks the smallest useful metadata contract for that work.
Validation runs in this browser only. Nothing is uploaded, saved, or sent to an AI model.
What a source ledger answers
- Identity: What work or authorized record is this?
- Version: Which source snapshot did a tool or reader use?
- Scope: What is included, and what is explicitly excluded?
- Access: Is it public metadata, authorized reader content, or something else?
- Distribution: Where is the machine-readable source of record?
What this validator does not do
It does not fact-check a book, evaluate copyright or platform-exclusivity terms, guarantee Schema.org compliance, secure a private corpus, or replace an editorial or legal review. Those are separate responsibilities in an actual publishing workflow.
How it fits the architecture
Phase 1 begins with source records and human approval. Phase 2 can create traceable reader-specific renderings. Phase 3 can expose only authorized context through constrained tools. The ledger is the prerequisite: without a clear source and access boundary, personalization becomes opaque content handling.
See the technical architecture and the metadata-only Maha Principle Context Record for a live example of the boundary.