DOCUMENTATION / K MAPS

Trace an API as an implementation chain

K Maps connect indexed endpoints to frontend callers, handlers, schemas, database models, tests, findings, and runtime evidence.

Read the chain

CALLER → ROUTE → HANDLER → SCHEMA → MODEL → TEST

Every node carries its source path, line, parser method, and confidence. Missing links are indexing gaps to investigate—not proof that a dependency does not exist.

Contract states

Planned — specified before implementation.
Untested — indexed, but no current runtime proof exists.
Mismatched — caller and provider disagree, or replay failed.
Verified — the active revision has passing proof.
Stale — code changed after the latest proof.

Open source references

In an IDE surface, selecting a file reference asks the host bridge to open that exact file and line in the editor. In the local browser dashboard, the same reference remains inspectable without granting arbitrary filesystem execution.

Evidence

A run stores bounded, redacted request and response details, assertions, timing, environment snapshot, and source revision. Credentials and common secret fields are removed before persistence.