Private by default · Scoped to the right work · Sourced to the original evidence · Owned by you
See one correction on Monday improve a different agent’s work on Friday.
Live demo · the second task · Monday → Friday
Claude CoworkMonday · agent 1 · client update
Drafts the weekly client update.
Your correction
“Lead with decisions and blockers. Separate confirmed facts from open assumptions.”
correction ▼
relevant memory ▼
ChatGPTFriday · agent 2 · different account
Prepares the update for a different account.
1. Decisions
2. Blockers
3. Open assumptionslabelled
Applied before you had to repeat the correction · from “Weekly client update structure”
Different task. Different agent. Same hard-won lesson.
Synthetic demo data · runs in this page · no model call
Different task. Different agent. Same hard-won lesson.
Memco sits between your agents as the learning layer: one private, domain-aware memory, connected once over MCP.
Recognisable work
The work where judgement is the asset.
Four workflows, the same pattern: what happened, what Memco learned, what the next agent does differently.
Consultingknowledge
before · Every draft buried the recommendation under context
“State the recommendation first — this client reads nothing past the opening paragraph.”
correction · Claude Cowork
→ next task · Friday · Hermes drafts the steering-committee note that way
Researchknowledge
before · A vendor claim slipped into a memo as evidence
“Vendor blog posts are leads, not evidence. Two independent sources before a claim ships.”
correction · Claude
→ next task · next scan · weak evidence flagged before the memo
Operationsknowledge
before · A refund went out without the second approver
“Refunds over €500 need a second approver since the March policy change.”
decision · Hermes
→ next task · new case · a different agent routes it right
Assistant workknowledge
before · Every Friday started with the same formatting instructions
“The Friday brief fits one screen: decisions first, then asks, then calendar.”
preference · Claude Cowork
→ next task · every Friday since · no re-explaining
Evidence
Don’t take our word for it. Run the learning loop.
In a controlled banking evaluation, learning from corrections reached 2.6× the single-trial success of a static-RAG baseline. The memory transferred between Mistral Large and Claude Sonnet 5 in that setup.
Policy violations per draftThe Knowledge Work example runs a service desk where the same policies recur in new combinations · qualitative shape, not a projection
The example calls your own private Memco space, so it needs a free signup first.
What Memco keeps
Keep the judgment. Lose the chat sludge.
Chat history and retrieval preserve what was said and what is written down. Neither turns a correction into something a different agent can act on next week.
Chat historykeeps
What was saidHeld until the window closes, inside one tool.
Retrieval and knowledge baseskeeps
What was written downDocuments and facts, reachable by many tools.
Memcokeeps
What the work taught youCorrections, accepted outcomes, failed paths, decisions and changed policies — sourced, scoped and reusable by a different agent later.
The expensive part is not storing context. It is paying to rediscover the same judgment.
How a lesson becomes trusted
Intelligence compounds only when the lesson is trusted.
A correction is not a lesson yet. It becomes one when it has a source, a scope and enough evidence to be validated — and it stops being one when the world changes.
correction or outcome
Learn
Something you fixed, decided or proved becomes a candidate lesson.
▶
source · scope · evidence
Govern
Memco attaches where it came from, where it applies and what makes it trusted.
▶
a different task, later
Reuse
A future agent applies it; feedback updates or retires it.
▲feedback updates the lesson — or retires it
sourcewhose correction, which task
scopewhere the lesson applies
statustrusted · provisional
retirementold deploy advice · stale · retired
Source, scope, status and retirement are visible objects on every lesson — not fine print. Without them, memory does not compound. It becomes sludge.
Ownership
Your agents can change. Your intelligence should not disappear with them.
Everything your agents learn lands in a space you own — private for you, shared when you invite your team.
01
Provenance and evidence
Every lesson carries its source: whose correction, which task, what evidence made it trusted.
02
Scope and permissions
Lessons apply where they belong — a client, a workflow, a team — not everywhere at once. Private by default; nothing is published anywhere outside your space.
03
Contradiction and retirement
A conflicting lesson surfaces for review instead of silently merging. Stale knowledge loses trust and is retired — struck through, not quietly deleted.
04
Revocation and export
Disconnect a client, revoke access, take your lessons with you. Change model, agent or interface without throwing away what use has taught your agents.
OAuth 2.0 · API keys for automation · encrypted in transit and at rest · regional and data-residency options subject to plan
One connection, separate domains
One MCP connection. Separate Coding and Knowledge Work stores. A repository fix never leaks into a client-reporting workflow.