[anentropic]

Next questions...

I'm skim reading the docs but I just want to know a bit more about the architecture

Does it produce artefacts that I can commit to version control and share with my team? Is it a tool that everyone runs locally in the project? Or there's a component (the wiki?) that I should deploy as an internal service?

[andreybavt]

When you install ktx, you'll have to initialize the project directory and ktx initializes a git repo there to assure the version controls.

ktx project directory is self-contained. The main 2 parts inside are :

- wiki: a collection of .md files

- semantic-layer: a collection of .yaml files

typically all these files are created/edited automatically during the ingestion, but you can also edit them by hand or even sync with a remote git.

ktx treats these files as sources and builds internal indexes in a sqlite db, located in projectDir/.ktx

The main way to use ktx is to start an mcp server by calling `ktx mcp start` it'll start an http server and multiple people will be able to connect it to their agents.

Hope this helps, happy to answer any other questions!

[anentropic]

Sounds like it produces yaml and markdown files that I could commit as project documentation/config?

[andreybavt]

yes, exactly