Files
wifi-densepose/docs/adr/coherence-engine/ADR-CE-018-pattern-restriction-bridge.md
ruv d803bfe2b1 Squashed 'vendor/ruvector/' content from commit b64c2172
git-subtree-dir: vendor/ruvector
git-subtree-split: b64c21726f2bb37286d9ee36a7869fef60cc6900
2026-02-28 14:39:40 -05:00

49 lines
1.4 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# ADR-CE-018: Pattern-to-Restriction Bridge
**Status**: Accepted
**Date**: 2026-01-22
**Parent**: ADR-014 Coherence Engine Architecture
## Context
RuvLLM's `ReasoningBank` stores successful patterns with verdicts. Prime-Radiant's restriction maps define constraints. These can reinforce each other:
- Successful patterns → what "coherence" looks like
- Failed patterns → what "incoherence" looks like
## Decision
**ReasoningBank patterns feed learned restriction map training.**
Bridge process:
```rust
impl PatternToRestrictionBridge {
fn learn_from_verdict(&mut self, pattern_id: PatternId, verdict: Verdict) {
if verdict.success_score > 0.8 {
// Success: train ρ to produce zero residual
self.restriction_maps[pattern_id]
.train(source, target, zero_residual);
} else {
// Failure: train ρ to produce high residual
self.restriction_maps[pattern_id]
.train(source, target, failure_residual);
}
}
}
```
## Consequences
### Benefits
- Experience improves constraint accuracy
- Successful patterns define "good" coherence
- Failed patterns help detect future failures
### Risks
- Biased patterns lead to biased constraints
- Need sufficient positive and negative examples
## References
- ADR-014: Coherence Engine Architecture, "RuvLLM Integration"
- ruvllm/src/reasoning_bank/