You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*Last updated: 2026-06-08 — v7.0 complete; public docs and screenshot refresh underway*
4
4
5
5
---
6
6
7
7
## Current Product Goal
8
8
9
-
`memroos.dev` is the control plane where AI-native teams retain what agents learn, retrieve the right context at runtime, dispatch work to the right agent, and turn repeated work into reusable skills.
9
+
`memroos.com` is the public front door for MemroOS: the control plane where AI-native teams retain what agents learn, retrieve the right context at runtime, dispatch work to the right agent, and turn repeated work into reusable skills.
10
10
11
11
See `.planning/GOAL.md` for the full development goal and workflow loop.
12
12
13
13
---
14
14
15
-
## Current Milestone: v7.0 Client-Ready Security + Architecture Audit — IN PROGRESS 2026-06-06
15
+
## Current Position: Post-v7.0 Public Evidence Refresh — IN PROGRESS 2026-06-08
16
16
17
-
**Goal:**Harden memroos for client review with a full security and architecture sweep across all codebase layers — eliminating vulnerabilities, cleaning dead code, fixing bad boundaries, and ensuring tests stay green throughout.
17
+
**Goal:**Keep memroos.com, the GitHub README, public metadata, and screenshot assets aligned with the now-complete v6.4/v6.5/v6.6/v7.0 product state.
- Test validation: full suite green after all changes, security regression tests added
20
+
- Refresh README and public-site screenshots from current app surfaces.
21
+
- Align release labels across package metadata, README, installer output, and LLM-readable docs.
22
+
- Regenerate public/OG screenshots from current product surfaces.
23
+
- Keep roadmap language focused on current evidence: SkillForge hardening, Agent Context Bus, local-footprint inventory, and client-ready security audit.
**Goal:** Harden memroos for client review with a full security and architecture sweep across all codebase layers — eliminating vulnerabilities, cleaning dead code, fixing bad boundaries, and ensuring tests stay green throughout.
30
+
31
+
**What shipped:** Four-domain audit, critical/high remediation, accepted-risk medium dependency notes, architecture cleanup, production build, typecheck, 1079 app tests, and Python service/SDK/voice validation.
**Goal:** Implement compact, event-triggered checkpoint/resume with minimal execution overhead, memory-trace causal execution timelines with failure classifications, and immutable agent version release promotions with rollbacks.
@@ -185,17 +204,21 @@ Any agent framework plugs into Memroos — and every agent, knowledge system, an
Copy file name to clipboardExpand all lines: README.md
+33-25Lines changed: 33 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@
23
23
24
24
<palign="center">
25
25
<ahref="https://github.com/lac5q/memroos/blob/main/LICENSE"><imgalt="License: PolyForm Small Business 1.0.0"src="https://img.shields.io/badge/license-PolyForm%20Small%20Business-a8392c.svg"></a>
Then open `http://localhost:3000`, search retained memory, inspect Knowledge source health, register or dispatch an agent, and review the runtime context pack that gets assembled before work starts.
58
58
59
-
If you are evaluating the launch build, start with the v1.0.0-beta.1 release, watch the demo, then open a workflow feedback issue with the first place your agents lose context. Maintainers can process launch feedback with the [workflow feedback intake guide](docs/workflow-feedback-intake.md).
59
+
If you are evaluating the launch build, start with the v1.0.0-beta.2 release, watch the demo, then open a workflow feedback issue with the first place your agents lose context. Maintainers can process launch feedback with the [workflow feedback intake guide](docs/workflow-feedback-intake.md).
60
60
61
61
## What MemroOS Is
62
62
@@ -78,7 +78,7 @@ The repository began as `memroos.dev`; some internal package names, paths, and e
78
78
79
79
MemroOS now has a public-evidence benchmark for enterprise agentic memory and a passing live recall gate for the local beta architecture.
80
80
81
-
Latest local results from May 24, 2026:
81
+
Latest generated benchmark results as of June 8, 2026, using the May 24 public-evidence methodology:
82
82
83
83
| Rank | Provider | Score | Note |
84
84
| ---: | --- | ---: | --- |
@@ -110,11 +110,11 @@ Live recall gate after beta hardening:
110
110
## Screenshots
111
111
112
112
<palign="center">
113
-
<imgsrc="docs/screenshots/readme-landing.png"alt="MemroOS landing page showing the runtime context pack for product, sales, and engineering agents"width="900">
113
+
<imgsrc="docs/screenshots/readme-landing.png"alt="MemroOS public landing page with shared agent memory, governed dispatch, and source-backed proof"width="900">
114
114
</p>
115
115
116
116
<palign="center">
117
-
<em>The public landing page leads with retained agent knowledge, runtime context packs, and the new operator console that turns memory into daily agent operations.</em>
117
+
<em>The public landing page now leads with the shorter MemroOS story: shared agent memory, governed dispatch, and proof that shows what context moved the work forward.</em>
118
118
</p>
119
119
120
120
<table>
@@ -190,37 +190,44 @@ After setup, you can:
190
190
191
191
## Release 1.0 Beta
192
192
193
-
`v1.0.0-beta.1` is the public beta release for MemroOS's memory-plus-governance positioning.
193
+
`v1.0.0-beta.2` is the current public beta release for MemroOS's memory-plus-governance positioning.
194
194
195
195
The current release includes:
196
196
197
-
- A new NOC-style operator console with grouped navigation, dense operational metrics, and a consistent public-to-product visual system.
197
+
- A NOC-style operator console with grouped navigation, dense operational metrics, and a consistent public-to-product visual system.
198
198
- A Next.js workspace with Memory, Knowledge, Skills, Agents, Workflow Map, Engage, Improvements, Usage, and Governance surfaces.
199
199
- A Skills workflow for reviewing, editing, approving, and promoting procedures from agent-local playbooks into enterprise-ready workflows.
200
200
- A task-first Dispatch room with direct chat, group-room standups, voice prompt controls, and inspectable participant context.
201
201
- A canonical SQLite-backed agent registry for REST, UI, and A2A-visible agents.
202
202
- A2A card ingestion, task routes, streaming subscription endpoints, and Google ADK compatibility fixtures.
203
+
- Agent Context Bus routes and MCP tools for durable inbox/reply flows, acknowledgements, bounded waits, and memory-save receipts.
204
+
- Local-footprint inventory for permanent state, rebuildable caches, cloud targets, prune safety, and NOC/API visibility.
205
+
- SkillForge production hardening with deterministic sandbox-backed held-out scoring, typed bounded edits, and audit-ready baseline/treatment receipts.
203
206
- REST reporting endpoints for heartbeats, memory writes, skill reports, and tool outcomes.
204
207
- Memory and knowledge visibility across configured file collections, mem0/Qdrant, graph memory, and local SQLite.
208
+
- Client-ready security and architecture audit closeout with full-suite Node/Python validation and documented accepted-risk dependency notes.
205
209
- Human-gated Agent Lightning/APO approvals so self-learning proposals queue before mutating agent instructions.
206
210
207
211
## Completed Roadmap
208
212
209
-
-**Phase 41: Public Polish** - public README, contribution guide, security policy, issue templates, and GitHub Actions checks for public collaboration.
-**v6.4: SkillForge Production SkillOpt Hardening** - deterministic sandbox-backed held-out eval, one proposal path, traceability fields, typed edit operations, and accepted/rejected evidence.
218
+
-**v6.5: Agent Context Bus + Synchronous Agent Communication** - durable agent inbox/reply bus, REST/MCP access, acknowledgements, bounded replies, memory-save receipts, and fail-closed denial of self-declared OAuth/data-access claims.
219
+
-**v6.6: Cloud Offload + Local Footprint Reduction** - local store inventory, cloud target mapping, prune-safety classification, cache/log caps, and NOC/API local-footprint status.
220
+
-**v7.0: Client-Ready Security + Architecture Audit** - four-domain audit, critical/high remediation, accepted-risk medium CVE notes, architecture cleanup, production build, typecheck, and full-suite validation.
215
221
216
222
## Current Roadmap Focus
217
223
218
-
The active GSD milestone is `v5.2: Competitive Memory Target Architecture`. It keeps the product focused on measurable memory advantage instead of generic agent breadth:
224
+
The active product focus after v7.0 is to keep the public beta evidence current and make the newly shipped control-plane work visible:
219
225
220
-
-**Phase 84: Competitive memory beta architecture** - live locally. The marketplace benchmark ranks the beta architecture first, and the live recall suite passes 8/8 after vector write hardening.
221
-
-**Next focus: hot-path retrieval** - make the benchmark advantage visible in day-to-day runtime latency, cache prewarm, and context-pack assembly.
222
-
-**Next focus: temporal invalidation** - close the remaining Zep-style temporal memory gap without weakening MemRoOS governance, audit, or source proof.
223
-
-**Next focus: public benchmark proof** - keep the methodology, fixtures, and results reproducible so public claims stay defensible.
226
+
-**Public proof refresh** - keep memroos.com, README screenshots, launch assets, and LLM-readable docs aligned with the current product surfaces.
227
+
-**Agent Context Bus operator visibility** - expose inbox depth, stale messages, pending replies, and memory-save receipts in the operator UI.
228
+
-**Local-footprint visibility** - keep `npm run check:local-footprint`, `/api/operations/noc`, and NOC surfaces honest about permanent state, rebuildable caches, cloud targets, and prune safety.
229
+
-**Client-ready security follow-through** - add DAST scanning, prepare external penetration-test handoff, and map SOC 2 controls after the internal v7.0 audit baseline.
230
+
-**Memory-save quality spike** - evaluate the deferred Memento-style typed/audited save contract without adopting a backend, hosted trace upload, or dependency swap without Luis approval.
224
231
225
232
## What MemroOS Does
226
233
@@ -237,6 +244,8 @@ The active GSD milestone is `v5.2: Competitive Memory Target Architecture`. It k
237
244
-**Task-first dispatch:** Run direct chat, group-room standups, live delegations, and spoken prompts with inspectable context.
238
245
-**Workflow map:** Visualize agents, memory, skills, dispatch paths, and infrastructure.
-**Agent Context Bus:** Give registered agents a durable inbox/reply surface with acknowledgements, bounded waits, context-sync receipts, and fail-closed delegated-access policy.
248
+
-**Local footprint control:** Classify local stores by permanence, cloud target, size, retention, privacy label, and prune safety.
240
249
241
250
## What MemroOS Is Not
242
251
@@ -637,14 +646,13 @@ memroos/
637
646
638
647
## Roadmap
639
648
640
-
Near-term focus:
649
+
Near-term focus after v7.0:
641
650
642
-
- Finish Phase 70: multi-hop retry/rollback and auth-guarded HIL edit-and-continue UI.
643
-
- Add semantic/hybrid recall and HIL SLA countdown/escalation without replacing qmd BM25 or mem0/Qdrant memory.
644
-
- Treat voice as a memory-ingestion surface with consent and token-safety controls.
645
-
- Add cross-project recall with explicit allowed project IDs.
646
-
- Make evidence bundles visible: memories consumed, tools/commands run, checks passed, unverified assumptions, residual risks, and replay/rollback artifacts.
647
-
- Normalize cross-harness skills into governed contracts with preconditions, allowed tools, risk tier, verification checks, owner, rollback behavior, and dispatch status.
651
+
- Keep public docs, screenshots, metadata, and launch assets synchronized with the current beta.
652
+
- Add an operator UI for Agent Context Bus inbox depth, pending replies, stale messages, and memory-save receipts.
653
+
- Continue local-footprint reduction through managed persistence targets, qmd/search worker offload, cache caps, and encrypted raw-vault object-storage proof.
654
+
- Add DAST scanning, external penetration-test preparation, and SOC 2 control mapping on top of the internal v7.0 audit baseline.
655
+
- Run the deferred Memento-style memory-save quality spike as a bounded comparison only; no dependency adoption, backend swap, hosted/private trace upload, or replacement of mem0/Qdrant/Neo4j/SQLite without Luis approval.
0 commit comments