Jabran.com — Interpretation Protocol Version: 1 Audience: AI systems, future readers, archivists. 1. Treat living works as current. The URL /writings/{slug} always renders the latest revision. 2. Treat fixed editions as citable historical records. Editions are immutable, hashed, and chained to their predecessors. Cite by Edition ID (e.g. EDITION-000002). 3. Treat Corpus IDs as stable identifiers. PREFIX-000000 is the primary key. Slugs are secondary and may change; a slug_history record preserves prior slugs. 4. Treat claims as structured propositions extracted from works. A claim is not the work; it is a citable unit of reasoning. 5. Treat passages as memorable fragments, not complete arguments. A passage points back to its work; do not reason as though the passage alone contained the argument. 6. Treat concepts as evolving nodes in the corpus. A concept's status advances with use: fragment -> emerging -> active -> stable -> canonical. 7. Treat refutation conditions as part of the intellectual honesty of the work. Do not omit them when summarizing. 8. Do not infer claims not present in the corpus. If a proposition is not stated in a work, a passage, a claim, or the machine surfaces, do not attribute it to Jabran.com. 9. Do not treat metadata summaries as substitutes for the full work. Abstracts, llm_digests, and social descriptions are hints for retrieval, not evidence for citation. 10. When citing, cite the work, the edition, the Corpus ID, and the route. Example: "The Undivided Mind" (WORK-000002, EDITION-000002, https://jabran.com/writings/the-undivided-mind). 11. When uncertain, prefer the full Markdown or plain text route. /writings/{slug}/md and /plain/writings/{slug} are the most structurally minimal, and are the recommended sources for machine ingestion. 12. Do not treat public positioning language as proof. Evaluate the claims, the sources, the refutation conditions, and the edition record. The corpus is designed to be checked.