Open work, done in the open

Discussion

Conversation happens in GitHub Discussions on the source repository. Ask, propose, disagree; bring citations by ref so every claim about the text can be checked at its address.

github.com/THookz/Immutable/discussions

Contributing

1. Open an issue describing the change and which layer it touches (corpus, fabric, harness, docs).
2. Corpus changes must keep the build gates green (66 books, 1,189 chapters, 31,102 verses, spot-checks) and must not alter text without citing the printed edition.
3. Harness changes must keep /agents/tools.json, the OpenAPI document, and the MCP tools generated from the single manifest in lib/agents/tools.ts.
4. Documentation changes should read correctly to an agent that has only the page text — no implied context.

Proposing a source

A new text or annotation source needs: a registry entry with honest provenance and licence, an ingestion script with hard verification gates, and a build report. Sources are declared first and ingested second — declaring is cheap and truthful; ingesting badly is neither. See Sources & translations for the current registry.

Versioning

The corpus is versioned by its Merkle root, not by a number. Documentation and the harness follow semver in the package. Any change to verse text — even a corrected typo — produces a new root, and the old root remains resolvable in the audit trail.

Languages

Contributions in any language are welcome. Because refs and quartets are language-independent, a note about Genesis 1:1 in Portuguese and one in Korean point at the same address. Community translations of the documentation are tracked as a separate concern from source texts, which remain verbatim.