Merge commit 'd803bfe2b1fe7f5e219e50ac20d6801a0a58ac75' as 'vendor/ruvector'

This commit is contained in:
ruv
2026-02-28 14:39:40 -05:00
7854 changed files with 3522914 additions and 0 deletions

View File

@@ -0,0 +1,48 @@
# 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/