chore(consolidation): migrate from blackroad-os-ideas and blackroad-os-research

## Summary
- Migrates roadmaps and RFCs from `blackroad-os-ideas`
- Migrates research papers from `blackroad-os-research`
- Part of Phase 1 BlackRoad OS consolidation

## Files Added
- `docs/roadmap/` - 2025 roadmaps
- `docs/rfc/` - RFC templates
- `docs/ideas/` - Idea proposals
- `docs/papers/` - Research papers (PS-SHA, SIG, finance automation)
- `docs/research/` - Research prompts

## Test plan
- [ ] Verify docs build
- [ ] After merge, archive source repos

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Alexa Louise <YOUR_REAL_EMAIL@EXAMPLE.COM>
Co-authored-by: Claude <noreply@anthropic.com>
This commit is contained in:
Alexa Amundson
2025-11-30 12:32:38 -06:00
committed by GitHub
parent d03040419c
commit 8f94430012
25 changed files with 707 additions and 0 deletions

View File

@@ -0,0 +1,27 @@
# Contradiction Handling in BlackRoad OS
Agents operate in a trinary logic space (true, false, unknown) where contradictions are treated as signals rather than silent errors. BlackRoad OS treats conflicts as first-class events that demand routing, journaling, and potentially escalation to orchestrators or human operators.
## What is a Contradiction?
A contradiction occurs when two or more beliefs, observations, or recommended actions cannot simultaneously hold. Examples include conflicting risk assessments across agents or incompatible compliance flags in finance workflows.
## Escalation Mechanism
1. **Detection:** Agents flag contradictions when belief vectors clash or when policy checks diverge.
2. **Event emission:** A contradiction event is emitted to the orchestrator or higher-level mediator.
3. **Reconciliation:** The orchestrator aggregates evidence, applies policy (e.g., majority vote, priority weighting, or regulatory override), and proposes a resolution.
4. **Outcome recording:** Both accepted and rejected branches are recorded for transparency and future replay.
## Integration with PS-SHA∞
Contradiction resolution steps are journaled as PS-SHA∞ entries:
- Record the competing claims and confidence scores.
- Capture the chosen resolution rule and rationale.
- Link branches through `previousHash` values so discarded paths remain inspectable.
## TODOs
- Define standardized contradiction event payloads for ingestion by `blackroad-os-operator`.
- Prototype escalation thresholds in `/experiments/contradiction-sim` to tune sensitivity.