Etki¶
The only open-source tool that answers "is this in scope?" with contract evidence, code impact and historical effort.

Alpha
APIs, schema and screens may change. Intended for pilot/evaluation, not production.
For every incoming client request, Etki answers one question: is this in-scope, out-of-scope, or a Change Request; what is the effort; which code and which contract clause does it touch? It fuses three sources no other tool combines:
- Contract scope — clauses extracted into structured scope items, including the explicitly excluded ones.
- Code knowledge graph — modules, dependencies, complexity, churn — for impact analysis and effort.
- Historical effort — real time logged on similar past requests, used by analogy.
Every decision carries an auditable evidence chain that can be reconstructed for a contractual dispute. Built for analysts, developers and PMO alike. Copilot, not autopilot: the system recommends, a human makes the final call.
Where to go¶
- Getting started — the 5-minute no-API-key demo, quick start, fully air-gapped mode.
- Concepts — the load-bearing design decisions: evidence chain, two-evidence rule, first-class EXCLUDED scope, effort ranges.
- Decision memory — the git-versionable decision wiki (a pure DB projection), precedents from human overrides, disputed clauses, and graph retrieval.
- MCP — ask Claude "is this in scope?" and get the real Etki answer.
- Writing an adapter / plugin — connect your tracker, repo
host or document source without touching core code: as an in-tree PR, or as a
standalone plugin package against
etki-api(entry-point discovery, conformance suite, capability manifest). - Operations — deployment, backup, index refresh, plugin install/lockfile/policy.
Source, issues and discussions: github.com/yasinyaman/etki · License: Apache-2.0