Use cases
Moresq Corpus is most useful when the work already has history: a reviewed implementation, a rejected approach, a test pack, a production incident or a repository constraint the next agent must respect.
Repeated problem
A new agent session sees the code but not why the team chose a particular auth, storage or deployment pattern.
Retrieval-first workflow
Search decision memory, inspect the source and constraints, then adapt the approved path instead of reopening the entire design debate.
Explore repo memory →Repeated problem
The agent is about to regenerate a webhook verifier, auth guard, SSRF-safe fetcher or rate-limit helper.
Retrieval-first workflow
Retrieve a strong match only when provenance, license, review state and tests are available. Keep the receipt with the patch.
Review verified snippets →Repeated problem
A tool can return code, but the client cannot tell whether the artifact is current, permitted or supported by evidence.
Retrieval-first workflow
Expose compact metadata first, full content second, and preserve hash, rights, quality, revocation and application outcome.
See the MCP workflow →Repeated problem
A company wants reusable agent memory without publishing internal source, incidents or architectural decisions.
Retrieval-first workflow
Import candidates into a project boundary, sanitize and review them, then allow retrieval only under the team’s visibility policy.
Open the private knowledge guide →Search compact metadata first. Reject weak, stale or unclear matches. Retrieve under explicit context and price limits, run the project tests, and record whether the reuse succeeded, needed correction or should be revoked.