IDKMesh implementation reference

Use these alongside the capability truth matrix and the getting-started guide:

Module map — every direct idkmesh/*.py module, grouped by responsibility and linked to its versioned contract.
CLI and HTTP quick reference — shipped commands, routed local endpoints, read-only client, and runnable examples.
As-built implementation architecture — current source paths, lifecycle boundaries, and separated authority.
Troubleshooting and operator help — installation, SQLite, local API, verifier evidence, sandbox and tests.
Dated code/documentation audit — precise review scope, source revision, unverified areas, and next steps.

For machine-readable protocol truth use schemas; for complete HTTP payload rules consult the Control Tower Local API contract. Historical design catalogs are not a statement that an endpoint ships today.

Maintenance discipline: add or update documentation in the same PR when a CLI command, routed endpoint, module authority, source binding, schema, or safety boundary changes. Verify against current merged source and exact-head CI before publishing stronger claims.

This site is open source. Improve this page.