akms
A deterministic global-local knowledge compiler. AKMS turns typed knowledge nodes into a directed graph, compiles task-scoped projections from that graph, and ingests structured evidence back into it.
What the core does
- Typed knowledge nodes with a frozen v2 schema, provenance, and trust metadata.
- Global/local ownership — a read-only global vault plus a writable project graph.
- Deterministic selection — tag derivation, subgraph queries, and dedup are pure algorithmic paths. No language model participates in graph operations.
- Projections — task-scoped slices of the graph, reproducible from the same inputs.
- Evidence ingestion — structured outcomes flow back into the graph.
The core performs no network calls and requires no API key.
Installation
pip install akms
That is the minimal core: graph compilation, schema, projections, evidence, and
the akms CLI, with four dependencies and no provider SDK.
Optional capabilities are explicit extras:
| Install | Adds |
|---|---|
akms[agents] |
coding-agent backends |
akms[mcp] |
the MCP tool server |
akms[telemetry] |
OpenTelemetry span export |
akms[orchestration] |
the complete embedded first-party runtime |
akms[learn] |
akms-learn, the learning-packet compiler |
akms[failure-memory] |
akms-failure-memory, project-owned failure memory |
akms[nodes-gen] |
akms-nodes-gen, node generation and validation tooling |
akms[compmech] |
compmech-reference-pack with its MechDSL backend |
akms[all] |
every extra above |
Extras combine: pip install "akms[learn,failure-memory]". Quote the argument
in zsh, which otherwise treats the brackets as a glob.
Consumption modes
AKMS is usable through any of these, and they are parallel supported paths rather than layers you must adopt in order:
- the Python library API
- the
akmsCLI - MCP tools
- a skill or agent-host integration
akms.orchestrator— an optional first-party runtime that drives a coding agent directly- an external consumer that requests projections and returns evidence
The embedded runtime is one consumer of the same public contracts external systems use. AKMS does not own portfolio-wide orchestration.
Requirements
Python 3.12. Some search paths use qmd, an
external Go binary; when it is absent those paths fall back to grep.
Maturity
Research software, published as a preview. See the repository root for limitations, privacy and provider notes, and the stable-versus-experimental capability matrix.
License
Apache-2.0. See LICENSE at the repository root.
Metadata
Release files for akms 0.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| akms-0.3.2.tar.gz | 244.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| akms-0.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 535.0 kB
Release files / akms-0.3.2.tar.gz
| Download URL | akms-0.3.2.tar.gz |
|---|---|
| Size | 244.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f57ca4f464ae3309970f0d8803375f5995ba9eac0540edcbc4bab52ef1ce6be5
|
|
BLAKE2b-256 checksum How to use checksums |
b724df791fc086504f775616069eb650555366775bb6d74448c4669e58e93473
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logRelease files / akms-0.3.2-py3-none-any.whl
| Download URL | akms-0.3.2-py3-none-any.whl |
|---|---|
| Size | 290.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
26f36ad6e5d1a9fb1ee542a898484f4afc4fe9dcff0ad305854bf666055a273a
|
|
BLAKE2b-256 checksum How to use checksums |
3e775c9b9c657848aeb68efc4d5f131a3ea9deee62dbf81f0a58b41a03a3eb19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency log