-
Notifications
You must be signed in to change notification settings - Fork 1
Contributing (details)
Arun Soman edited this page Aug 31, 2026
·
1 revision
The README keeps the short version; this page is the dev onboarding.
git clone https://github.com/kannamma-labs/cie && cd cie
uv venv && uv pip install --python .venv/bin/python -e ".[mcp,http,dev]"
source .venv/bin/activate
python -m pytest -q # 312 passed as of v0.1.4- DoD = verified against the real environment, never written-only.
- Published claims footnoted to measured artifacts; misses published.
- Dated records (CHANGELOG, session logs) are never retro-edited.
- If code and this wiki disagree, the code wins and the wiki gets a PR.
-
roadmap.md— R1–R45 with status;todo.md— the same items at execution depth (file:line-verified plans) + the session log. - Starter issues: #17, #18, #19 (created from the repo-trust-signals work).
- Conformance harness:
python tool-test-lab/surface_conformance.py /tmp/sandbox /tmp/conf.jsonagainsttool-test-lab/approved_surface.json(135 tools, zero crashes).
- A how-to you wish existed (wiki PRs count).
- A TESTS-edge heuristic gap you can measure (the direct-calls heuristic came exactly from such a measurement).
- Conformance/ground-truth tests for a tool you use.
If code and this wiki disagree, the code wins — then this wiki gets a PR. Evidence lives in the repo, not here.
Start
How-tos
- Install & serve to your MCP client
- Choose your storage backend
- Run the Neo4j team mode
- Index & keep it fresh
- Ask impact questions
- Task & QA layer
- Semantic search
- Snapshot or serve HTTP
- Policies & the write boundary
- Troubleshoot
Reference
- Extraction pipeline
- Data model
- Tool reference
- Benchmarks
- Security & determinism
- Two tiers · Project layout · Docs index
Contribute