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

Checkpoint: File edits

rUv0d5eeeae0c3c
diff --git a/v3/@claude-flow/guidance/docs/adrs/ADR-G005-proof-envelope.md b/v3/@claude-flow/guidance/docs/adrs/ADR-G005-proof-envelope.md
index cf35c02033..b92e13329e 100644
--- a/v3/@claude-flow/guidance/docs/adrs/ADR-G005-proof-envelope.md
+++ b/v3/@claude-flow/guidance/docs/adrs/ADR-G005-proof-envelope.md
@@ -77,6 +77,7 @@ The ledger supports temporal queries: `getEventsInRange(startMs, endMs)`, `getRe
- **In-memory storage.** The current implementation stores events in an in-memory array. Mitigation: `RunLedger` accepts a `maxEvents` constructor parameter (default 0 = unlimited). When set, the oldest 10% of events are evicted in a batch splice when the limit is exceeded (see ADR-G026). Events can also be exported and cleared periodically via `exportEvents()` and `clear()`.
- **No cryptographic chaining.** The current implementation uses UUIDs and guidance hashes but does not implement full hash-chain linking (each event's hash includes the previous event's hash). This is a future enhancement.
+- **Signing key is required.** The `createProofChain()` factory requires `{ signingKey: string }` as of ADR-G026. Callers must provide an explicit HMAC key; there is no fallback. The `RuvBotBridgeConfig` exposes a `proofSigningKey` field for this purpose.
- **Clock dependency.** Timestamps rely on `Date.now()`, which can be manipulated on the host. Mitigation: in production, timestamps should be sourced from a trusted time service.
## Alternatives Considered