Contributing to lingtai-kernel

August 10, 2026 · View on GitHub

Thank you for helping improve the LingTai Python runtime. GitHub discovers this root file as the repository contributing guide.

Start here

Community and safety

Workflow

Use a branch and worktree for non-trivial changes, keep changes focused, and open pull requests rather than pushing directly to main.

git fetch origin main
git worktree add -b <branch-slug> .worktrees/<slug> origin/main
cd .worktrees/<slug>

Before changing code or architecture documents, read the repository-local kernel development skill, then the nearest ANATOMY.md to navigate the layer and the paired CONTRACT.md (when governed) to learn its interface and Behavior promises. When the component has agent-observable behavior, read its paired BEHAVIORS.md and follow the Contract ⇄ Behaviors ⇄ Anatomy tridirectional linkage: changing one requires re-checking the other two. The development skill owns the change workflow; the root documents own the structural and interface rules. Follow those routes instead of copying their checklists here.

Before requesting review, run the narrow tests relevant to your change and at least git diff --check. For code changes, prefer targeted pytest runs plus any package/build checks affected by the diff. Run tests/test_architecture_documents.py when changing the distributed Anatomy or Contract systems.

Root hygiene

The repository root is reserved for entry points, legal files, build metadata, and tool files that must live at root. The canonical repository-local development router lives in dev-guide-skill/; ANATOMY.md and CONTRACT.md are the normative distributed system roots. Long-form references, language variants, plans, and archival material belong under docs/.