docs(SUP-1588): clarify memory stack closeout

[levineam]

Summary

• clarify the jarvOS/OpenClaw/GBrain memory-stack operating model after the hardening closeout
• document that local Ollama mxbai-style embeddings require a controlled GBrain embedding migration, not a provider flip
• reinforce noisy-first daily audits, tracker-backed follow-up, and memory-wiki as diagnostics rather than a GBrain import source

Verification

• npm test
• git diff --check

Paperclip

• SUP-1588

Summary by CodeRabbit

Documentation

• Updated operational and architectural guidance for handling embedding model provider changes across multiple platform documentation sections.
• Enhanced maintenance procedures with detailed migration steps, preflight checks, database backup procedures, vector dimension validation, and rollback strategies.
• Added comprehensive rollout patterns and audit procedures for GBrain embedding updates, including retrieval evaluation comparisons and health verification.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 50f926aa-badf-4609-be77-22b731cc48d7

📥 Commits

Reviewing files that changed from the base of the PR and between 18f7d91 and 6306fc5.

📒 Files selected for processing (5)

• README.md
• docs/architecture/jarvos-architecture.md
• modules/README.md
• modules/jarvos-gbrain/README.md
• runtimes/openclaw/README.md

---

📝 Walkthrough

Walkthrough

Documentation across the repository is standardized to treat GBrain embedding provider changes as data migrations. Detailed procedures are documented in the GBrain module README, integrated into architecture and production operational patterns, and summarized at the module and repository level.

Changes

GBrain Embedding Provider Migration Guidance

Layer / File(s)	Summary
GBrain embedding provider change procedures modules/jarvos-gbrain/README.md	Detailed procedural documentation for changing GBrain embedding providers, including preflight steps (stats/doctor, retrieval evals), backup procedures, dimension verification, vector store reinitialization when dimensions differ, and post-migration validation using before/after evaluation comparison.
Architecture and operational guardrails docs/architecture/jarvos-architecture.md, runtimes/openclaw/README.md	Architecture document metadata updated and new "Operational guardrails" subsection added specifying rollout audit steps, follow-up tracking process, and GBrain embedding-provider migration requirements integrated into the validated operating pattern. OpenClaw memory-ops cron pattern extended with noisy-first rollout approach and daily status delivery, plus embedding provider migration steps with evidence/dimension verification.
Module and repository-level documentation modules/README.md, README.md	Module README adds "Embedding provider rule" for @jarvos/gbrain specifying that live store embedding-model-family changes require backup, dimension verification, and migration/re-embed with rollback proof. Root README adds "Embedding maintenance" guidance to production OpenClaw setup section with concrete example of mxbai-embed-large as private default.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

Possibly related PRs

• levineam/jarvOS#29: Both PRs update the same OpenClaw/GBrain "memory ops" maintenance/audit documentation (e.g., runtimes/openclaw/README.md and modules/jarvos-gbrain/README.md), with this PR extending that loop by adding embedding-provider-change migration steps and dimension verification.
• levineam/jarvOS#17: This PR extends the newly introduced @jarvos/gbrain documentation with embedding-provider "treat as migration" + dimension-check/eval guidance that directly matches the module's gbrain sync/embed and retrieval eval/doctor workflow added in PR #17.

Poem

🐰 A rabbit hopped through docs today,
Embedding migrations now have their way!
Backup and check those vector dimensions,
Re-evaluate with careful intentions—
From GBrain's depths to ops in production! 🧠✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'docs(SUP-1588): clarify memory stack closeout' directly relates to the main changes, which clarify the jarvOS memory-stack operating model, GBrain embedding migration procedures, and daily audit practices across multiple documentation files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch SUP-1588-memory-stack-docs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}