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>

docs/ideas/proposals/automated-compliance-spec.md

@@ -0,0 +1,35 @@
+# Automated Compliance Agent Specification
+
+## Goals
+- Provide continuous compliance monitoring for financial operations across BlackRoad OS.
+- Automate evidence collection and alerting for violations.
+- Reduce manual review cycles by routing low-risk checks through agents.
+
+## Non-Goals
+- Replacing human sign-off for regulated actions.
+- Building full audit dashboard UI (handled in Prism).
+
+## User Flows
+1. Operator defines compliance controls and thresholds.
+2. Agent ingests events from operator/orchestrator pipelines.
+3. Violations trigger alerts, tickets, or auto-mitigations.
+4. Weekly digest summarizes control posture and exceptions.
+
+## Agent Flows
+- Schedule periodic scans of transaction and access logs.
+- Apply rule packs for KYC/AML-sensitive actions with `Regulated Risk` scoring from the prioritization framework.
+- Escalate to human review when confidence < threshold or contradictions surface.
+
+## Risks
+- False positives causing alert fatigue.
+- Missed edge cases in financial flows; mitigated via shadow mode before enforcement.
+- Data privacy handling when aggregating evidence.
+
+## Dependencies
+- `blackroad-os-operator` event streams and control registry.
+- Identity lineage from `concept-0001` (SIG Factor Tree Identity Assignment).
+- RFC approval if schemas change for evidence logging.
+
+## Links
+- Idea source: `idea-0003` (Compliance agent sketches).
+- Future RFC placeholder: `rfc-0003` once schema impacts are defined.