Skip to content

armgit / ruflo

Public Imported from GitHub
0

🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated

docs(ruflo-mods): refuse-risky refuses nearly every ruflo mod unless it is listed

Dragan Spiridonov620651e22af1
diff --git a/plugins/ruflo-mods/README.md b/plugins/ruflo-mods/README.md
index 8aeaea60a4..e44e46cf89 100644
--- a/plugins/ruflo-mods/README.md
+++ b/plugins/ruflo-mods/README.md
@@ -18,7 +18,10 @@ These enable `ruflo-mods@ruflo`, `ruflo-swarm@ruflo` and `ruflo-console@ruflo`,
- **ruflo-mods and ruflo-console** run only where function hooks are on. With them off, or with Claude Code's rollout switch off, they do nothing, and the classic hooks keep every event.
- **ruflo-swarm** loads its commands, skills and agents even without function hooks. With them on, it is also a mod that can run host commands (pane actions you start).
- **The ruflo marketplace is cloned on first use.** Each teammate's first trusted, interactive Claude Code start clones `github.com/ruvnet/ruflo`. A headless `claude -p` on a fresh config loads nothing. Once the marketplace is cloned, which `ruflo init` does, `claude -p` loads the mods too.
-- **Optional hardening:** set `pluginConfigs["ruflo-mods@ruflo"].options.modTrust = "refuse-risky"` with `modTrustAllow` in user or managed settings (e.g. `"ruflo-swarm@ruflo,ruflo-console@ruflo"`: both run host commands, so `refuse-risky` refuses them otherwise). Project settings cannot set it. The default is `observe`, which names what each later mod can do and blocks nothing. `ruflo-protector@ruflo` (Project Anatole, ADR-453) is an expected `modTrustAllow` entry: it hooks `tool.check` to deny rule-marked-block calls in `enforce` mode, so `refuse-risky` refuses it otherwise. When its status file exists, `/ruflo-mods` shows one `protector:` row (mode, open alerts, blocked).
+- **Optional hardening:** set `pluginConfigs["ruflo-mods@ruflo"].options.modTrust = "refuse-risky"` with `modTrustAllow` in user or managed settings. Project settings cannot set it. The default is `observe`, which names what each later mod can do and blocks nothing.
+ - **`refuse-risky` refuses nearly every ruflo mod unless it is listed.** Almost all of them write their own status file (`$.fs.write`), and most also hook `tool.call` to guard memory writes; both count as risky. So `modTrustAllow` has to name **every** ruflo mod you want to keep (`name@ruflo`), not just the ones that run host commands (`ruflo-swarm@ruflo`, `ruflo-console@ruflo`) or answer tool verdicts (`ruflo-protector@ruflo`, Project Anatole, ADR-453).
+ - **Build the list from `observe` first.** In `observe`, each later mod gets one `ruflo mod trust: <name> (<name>@<marketplace>) loaded; <what it can do>` line. Add the provenance of each one you keep to `modTrustAllow`, then switch to `refuse-risky`. A mod you did not list is refused with a message naming the entry to add.
+ - When `ruflo-protector`'s status file exists, `/ruflo-mods` shows one `protector:` row (mode, open alerts, blocked).
## Install and repair
@@ -97,7 +100,7 @@ Claude Code reads a plugin's options from `pluginConfigs["ruflo-mods@ruflo"].opt
| `selfCheck` | `true` | Startup self-check (ADR-404 addendum): once per session, a toast when a ruflo plugin your settings enable is missing from the ruflo marketplace clone with no cached install (Claude Code then skips it without a word), with the one-line repair. Read-only; fixed text; never adds anything for the model. |
| `grounding` | `false` | Status only (ADR-487): `/ruflo-mods` gains `grounding: RuvNet Brain: on / not installed / installed, disabled / unknown`, read from `installed_plugins.json` and your settings. It detects Stuart Kerr's optional third-party [ruvnet-brain](https://github.com/stuinfla/ruvnet-brain) plugin by name only; it never calls, installs, blocks or rewrites anything, and ruflo works the same without it |
| `modTrust` | `observe` | `observe` / `refuse-risky` / `off`: the mod trust gate. Evidence: [capability review](../../v3/docs/validation/mod-capability-review-2026-10.md) |
-| `modTrustAllow` | empty | Comma-separated plugin ids (`name@marketplace`, e.g. `ruflo-swarm@ruflo,ruflo-console@ruflo`) the gate never refuses. Evidence: [capability review](../../v3/docs/validation/mod-capability-review-2026-10.md) |
+| `modTrustAllow` | empty | Comma-separated plugin ids (`name@marketplace`, e.g. `ruflo-swarm@ruflo,ruflo-console@ruflo`) the gate never refuses. Under `refuse-risky`, list every ruflo mod you use: nearly all write a status file or hook `tool.call`. Evidence: [capability review](../../v3/docs/validation/mod-capability-review-2026-10.md) |
| `guidanceContext` | `false` | Screened lexical excerpts (at most five, 4096 characters) from a compiler-exported guidance projection; advisory, cannot authorize tool calls. Design in [ADR-447](../../v3/docs/adr/ADR-447-native-mod-guidance-observation-loop.md); evidence: [native guidance](../../v3/docs/validation/ADR-447-native-guidance-evidence.md) |
| `guidanceLearning` | `false` | Unverified activity observations for independent review; no training or promotion. Evidence: [native guidance](../../v3/docs/validation/ADR-447-native-guidance-evidence.md) |