Contribute
You do not need permission and you do not need to be an expert. Pick a script or a language, bring evidence, and let the work speak. Read the Charter first — it is short and it is what keeps this project open to everyone, everywhere.
Brand new to GitHub? Start here
GitHub is where the code and the registries live. A few concepts, each linked to a plain explanation and an official guide:
| Concept | What it means | Learn |
|---|---|---|
| Repository | A project folder with full history. | Wikipedia · GitHub docs |
| Fork | Your own copy of a repo to work in freely. | Wikipedia · GitHub docs |
| Branch | A parallel line of work inside a repo. | Wikipedia · GitHub docs |
| Commit | A saved, described change. | Wikipedia · GitHub docs |
| Pull request (PR) | Proposing your change be merged in. | Wikipedia · GitHub docs |
| Issue | A tracked task, proposal, or question. | GitHub docs |
| Git | The version-control system underneath. | Wikipedia · git-scm |
Ask an AI to walk you through it
Stuck? Open a ready-made prompt in your assistant of choice (click-through — it pre-fills the question):
▶ Claude: “how do I fork project-ilm and open a PR?”
▶ ChatGPT: “how do I fork project-ilm and open a PR?”
▶ Claude: “help me add a new script projection table to ILM”
▶ ChatGPT: “help me write an ILM language keyword registry”
What to work on
Add a script
Pick a pending or encoded script in the 3D explorer or table. Add one Unicode→Devanagari-hub projection table row. The kernel never changes.
Propose a script →Add a language
Write a keyword registry
(construct,native_keyword,romenagri) and run the langspec generator → a standard doc + a
compile-verified program. Even a dialect or your own idiolect.
Validate / invalidate
Bring independent checks or adversarial tests against any claim. Disagreement with evidence is welcome and valued.
Open a validation →The rules (from the Charter)
- Evidence over authority. Back claims with a verifiable DOI (Zenodo / OSF / journal). Bring your own validators and invalidators.
- Publish first, then PR. Timestamp and, ideally, publish or file before the pull request, to protect your authorship.
- Academic / technical only. No political, religious, or communal content. Respect national narratives; the layer is narrative-neutral.
- No primary sociolinguistic data. Contribute derived, published, citable artifacts — not community field data.
- Compatible licenses only. Code GPL-3.0-or-later; docs CC BY 4.0. You are responsible for your contribution's license. Maintainers may decline or later remove non-compliant material.
- Low-resource languages welcome. Provide a widely-supported pivot language for review; keep the original DOI-verifiable.
Process documents
CONTRIBUTING · Code of Conduct · Governance · Charter · Open an issue