Start Here: Publishers and Developers

For publishers

Start with one work and identify the public facts that a reader or machine may inspect: title, edition or release version, publisher, permitted destinations, access conditions, and explicit exclusions. Keep manuscripts, reader lists, contracts, and unapproved editorial material outside that public record.

• Create a source/provenance record for the approved inputs.
• Have an accountable editor approve the record and each release.
• Publish a metadata-only Context Pack or Release Manifest first.
• State what changed whenever a public version changes.

For developers

Treat a Context Pack as a contract for discovery and scope, not as permission to crawl or reproduce protected content. Start by consuming the public JSON, preserving its version and provenance fields, and declining requests that exceed its stated access boundary.

• Fetch only explicitly public endpoints.
• Store the release version alongside any derived output.
• Show provenance and exclusions in your interface.
• Design entitlement checks before connecting protected content to tools.

Use the public demo

The Maha Principle Context Pack is a read-only, metadata-only demonstration. Inspect the human page and its two JSON records, then use the local Source Ledger Validator to check a record in your own browser without uploading it.