Search, inspect, and record SIPS-owned Memory Fabric lessons. Use when a task needs prior lessons, recurring-fix memory, recall health, scoped historical context, or when a just-fixed bump or error should be recorded.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Use homebase_recall with the user's query and current repo root. Treat Memory Fabric as a SIPS-owned subsystem for recall, lesson capture, memory health, and future tooling.
Do not present recall as current proof. If a memory-derived fact is likely to drift, verify it with local files or runtime checks before using it as evidence.
When recall finds a relevant fix, cite the remembered boundary in the final answer and run the live command that proves the current repo still matches it.
After fixing any bump (failed command, wrong path, retry chain), record it immediately: run python3 scripts/memory_fabric_cli.py record from the SIPS plugin root with the symptom, the working fix, and repo scope (or memory_fabric_record on the codex-memory-fabric MCP when that host exposes it), then confirm it surfaces via homebase_recall. Unrecorded fixes recur across sessions.
Use the shared adaptation controller for structured investigations and bounded probes.
Prefer current v2 contracts and joint-prerequisite composition before new helpers.
Use additive counterexamples; preserve raw episodes when proposing procedures.
Policy trials are declarative proposals, never changes to evaluation or activation.
See docs/sips-06.md for request shapes, supported schemas, and research limits.
Use assumptions to expose conditional support and contradictions. Unverified evidence references do not establish truth; recompute after retraction. Manual teaching does not establish high confidence. See method API and command protocol.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Extract bounded, source-linked context from large files or many inputs. Use when context is too large, files are oversized, or a task needs concise excerpts.
The English summary is being prepared. Showing the original description.
Inspect SIPS Homebase status, manifest wiring, routes, host visibility, and MCP freshness. Use when asked for SIPS status, command center, host audit, plugin visibility, or whether Homebase is fresh.
The English summary is being prepared. Showing the original description.
Route a task through SIPS commands, agents, scripts, MCP tools, or bounded delegation. Use when asked to route, split, fan out, escalate, or choose the right SIPS path.
The English summary is being prepared. Showing the original description.
Turn failures, logs, symptoms, or flaky behavior into a compact repro and verification plan. Use when debugging needs a reproducible failure path.
The English summary is being prepared. Showing the original description.
Capture and develop a reusable skill, tool repair, or behavior improvement noticed while completing a task. Use when instructions are stale, a recurring workflow deserves a skill, or a tool contract fails in practice.
The English summary is being prepared. Showing the original description.
Plan browser, app, screenshot, or UI checks before visual claims. Use when a task includes app shots, visual QA, generated assets, or runtime UI proof.
The English summary is being prepared. Showing the original description.