One call returns the architecture facts and the constraints other engineers wrote down — the two things a coding agent cannot infer from the file in front of it. The attestation at the end is what makes its work reviewable: which rules it checked, which elements moved, and where it could not tell.
A context source for coding agents. It answers what this project is, which rules cover the file about to be edited, what changed recently, what is currently flagged, and what the working diff actually touches.
- A project digest — architecture, tech stack, data model, rules — retrievable whole or drilled into by path
- Per-file context: the architecture elements a file belongs to and the constraints that apply to it
- The current findings, with a short curated shortlist of what needs attention first
- A change log of which architecture elements and rules moved, when, and by whom
- The blast radius of the working diff: touched elements, triggered rules, files that map to nothing
- A two-phase commit attestation: draft it, then write it with your own status per rule
- Cross-session memory, so what an earlier session learned is readable by the next one
- A hosted server by URL, or a local one launched through the CLI
A gjalla project. The hosted server is a URL plus a browser approval; the local one runs through the CLI, which already holds the configuration, so the MCP config carries no keys.
One command plus a key — pip install gjalla[mcp], then supply credentials