Memory remembers · Lore acts

Your docs are lying
to your agents.

Written process rots the day it ships, and your agents follow the official story straight into failure. Lore reads how your company actually works, writes the cited Skills your agents run, and flags the moment reality drifts from the doc.

Join the waitlist
Early design partnersFree during the first cohortHand-onboarded

Your scattered sources

One cited Skill agents run

Messy sources in · one cited SKILL.md out · loaded by Claude Code via MCP

Connects to the tools your team already lives in

Coming soon

The difference

A skill layer, not a memory layer.

Memory tools store notes for your agent to read, then it improvises. Lore writes the cited playbook your agent runs. Closer to a compiler than a search engine.

Memory layers

Mem0 · Zep · Letta · Glean

  • Store notes and hand them back on request
  • The agent reads them, then improvises a response
  • Relevance scores, not decisions. You never see which rule it used

Lore

The skill layer

  • Writes the cited playbook the agent executes
  • Every line links to the Slack message, PR, or email that set it
  • Re-emits the moment a rule changes, so it is never stale

We use a memory layer underneath. We’re not one. The artifact your agent runs is the SKILL.md and that’s the part nobody else is building.

The audit loop

Every run, logged.

When an agent loads a Skill or runs it on a ticket, the call lands here. Version, agent, outcome, duration. Failed runs flag the Skill for the next refresh.

Design partner program. 10 seats. Filling fast.

Connect your team.
Watch your agents stop guessing.

Be one of the ten teams whose agents run on real, cited process instead of guesswork. Connect Slack, GitHub, Linear, and email. Your first Skills land in an afternoon. We reply within 24 hours.

Self-hosted availableRuns in your PostgresData never leaves your perimeter