What happens in a session

Available today

Once a repo is activated and the MCP server is wired, coding with Claude Code is the same as before, with governed memory working around the edges. Here is what actually happens, mapped to the concepts behind each moment.

The lifecycle of one turn

1. You submit a prompt. Before the agent reasons, the connector injects this workspace’s confirmed, trusted decisions and rules into context. The agent sees your team’s constraints alongside your request. This is Injection, and it runs client-side.

2. The agent works, and can ask governed memory. Through the MCP server, the agent can query the corpus mid-task and get grounded, cited answers instead of guessing. This is Ask from inside the session.

3. The connector captures the work. Prompts, decisions, tool calls, and any documents the agent produces are recorded as evidence, born pending. Produced docs are indexed so they are retrievable. This is Capture.

4. Contradictions get surfaced. If a fresh decision conflicts with the approved corpus, the connector can flag it, open a triage case, and even steer the live session so you catch it while the agent is still working, not in review.

5. The enforcement gate observes, and can deny. Pre-action, the gate watches what the agent is about to do. Today it records and passes through for everything except the armed notes-location rule, which can return a real block. This is Enforcement, observe-first.

What is trusted, and what is not

Nothing captured in a session is trusted just because it happened. It is born pending and stays pending until a human promotes it. So a session can propose new knowledge freely without polluting what the next session grounds on. The promotion step is Reviewing & promoting knowledge.

Note

This is the trust model in motion: the session generates evidence generously, and the corpus only grows when you accept it. See the trust model.

Local by default

Injection is a local read. Capture writes to local state first. What, if anything, leaves your machine is governed by explicit settings, not assumed. The configuration & privacy page is the full account of local-first behavior and the telemetry defaults.

Checking a session after the fact

You do not have to watch this happen live. After a turn or a session you can review what the connector did and whether it helped:

• mla status shows whether Meetless is active for the repo and the current scan-cache counts.
• mla summary recaps the session.
• mla turn recaps a single turn.

The command reference lists these in full.