KnowledgePersonal · source-linked · reviewable
Memory you can audit.
What one mission learns can help the next, with scope, sources, review controls, and a clear boundary between personal memory and planned organization memory.
The rollout stalled on a glibc < 2.35 base image. The constraint was recorded and worker base images are now pinned to distroless arm64 variants.
Simulated recall · click a query to drive itEvery answer carries its sources
Engineering knowledge has a half-life.
Every hard-won answer — why the build is pinned, who owns the keys, what broke last time — gets written somewhere it will never be found again.
▲ recovered by: interrupting whoever remembers
Chat threads
- holds
- the decision and the debate
- fate
- scrolled away in a week
Closed pull requests
- holds
- what changed and how
- fate
- the why never made it in
Runbooks and wikis
- holds
- how it worked at write time
- fate
- stale the sprint after
Senior engineers
- holds
- the real integration map
- fate
- context leaves with them
The fix
Knowledge should be written where the next mission looks first. Not where it happens to land.
Personal memory now. Organization memory when it ships.
Accepted, source-linked personal memory can help a later mission today. Organization-wide shared knowledge is Planned and remains labeled throughout this page.
Relevant to the current mission
Memory is retrieved against the current workspace and mission context instead of being injected as one undifferentiated archive.
workspace · repository scope
This constraint belongs to the registered checkout and mission that established it.
mission source
Source-linked by default
Accepted memory retains the source needed to inspect where the context came from.
accepted memory
The worker base image requires a compatible runtime.
mission local-042
Controlled by the user
Current controls include dismiss, forget, and hard delete paths for personal memory.
memory control
Remove context that is stale, irrelevant, or no longer wanted.
review action
Knowledge is a by-product of doing the work.
Personal memory remains reviewable. Accepted, source-linked context can become a better starting point for a later mission without turning every past detail into canon.
1write
Candidate forms
context stays source-linked
2write
User reviews
accept · dismiss · forget
3write
Memory retained
scoped personal context
4read
Later mission recalls
only when relevant
recall loops back into every new mission ↺
Want to see the write path in detail? Follow a full mission replay.
Mission anatomyKnowledge you can audit.
Every record carries its sources and a verification trail. When new work contradicts old knowledge, the record gets flagged — stale context is surfaced, never silently trusted.
DreamerPreviewReviews completed work while the system is quiet: detects repeated or contradictory knowledge and proposes evidence-linked records for promotion. You approve what becomes canon.
Checkout workloads run multi-arch; delivery matrix pinned.
verified 2d ago · PR #418 · arm-042
payments-v2 supersedes payments-v1 for all new integrations.
verified 5d ago · ADR-031
Staging deploys require manual approval from release captain.
contradicted by mission rel-118 · flagged for review
Worker base images must satisfy glibc ≥ 2.35 (from incident 2041).
proposed by Dreamer · evidence linked · awaiting promotion
Local now. Shared is Planned.
Personal memory starts on your linked Mac. Organization-wide shared memory is a Planned team capability, not current behavior.
Personal memory, on disk
Your agent’s memory lives with your repositories and execution — on your machine. Model calls go only to providers you configure.
Shared knowledge, governed
Architecture, ownership, and outcome records for the whole organization — with permissions, promotion review, and audit history.
Questions
Knowledge, precisely.
How the archive behaves. To see the write path in motion, follow a full mission replay.
01What carries across missions?+
Accepted, source-linked personal memory can be retrieved when it is relevant to a later mission.
02Can I remove memory?+
Yes. Current memory controls include dismiss, forget, and hard delete paths.
03Can I correct a memory card inline?+
Correctable is Preview. The service contract exists, but the current Desktop surface does not expose the edit-then-accept action.
04Can an organization share one memory set?+
Organization-wide shared knowledge is Planned and is not presented as current behavior.
Shared engineering knowledge
Stop re-explaining your own system.
Start with personal memory on your machine, free with your own keys. Grow into a shared knowledge base when your team is ready.
Personal memory ships with Desktop. Organization-wide shared memory is Planned.