docs: Archive Sprint 3500 (PoE), Sprint 7100 (Proof Moats), and additional sprints

Archive completed sprint documentation and deliverables:

## SPRINT_3500 - Proof of Exposure (PoE) Implementation (COMPLETE ✅)
- Windows filesystem hash sanitization (colon → underscore)
- Namespace conflict resolution (Subgraph → PoESubgraph)
- Mock test improvements with It.IsAny<>()
- Direct orchestrator unit tests
- 8/8 PoE tests passing (100% success)
- Archived to: docs/implplan/archived/2025-12-23-sprint-3500-poe/

## SPRINT_7100.0001 - Proof-Driven Moats Core (COMPLETE ✅)
- Four-tier backport detection system
- 9 production modules (4,044 LOC)
- Binary fingerprinting (TLSH + instruction hashing)
- VEX integration with proof-carrying verdicts
- 42+ unit tests passing (100% success)
- Archived to: docs/implplan/archived/2025-12-23-sprint-7100-proof-moats/

## SPRINT_7100.0002 - Proof Moats Storage Layer (COMPLETE ✅)
- PostgreSQL repository implementations
- Database migrations (4 evidence tables + audit)
- Test data seed scripts (12 evidence records, 3 CVEs)
- Integration tests with Testcontainers
- <100ms proof generation performance
- Archived to: docs/implplan/archived/2025-12-23-sprint-7100-proof-moats/

## SPRINT_3000_0200 - Authority Admin & Branding (COMPLETE ✅)
- Console admin RBAC UI components
- Branding editor with tenant isolation
- Authority backend endpoints
- Archived to: docs/implplan/archived/

## Additional Documentation
- CLI command reference and compliance guides
- Module architecture docs (26 modules documented)
- Data schemas and contracts
- Operations runbooks
- Security risk models
- Product roadmap

All archived sprints achieved 100% completion of planned deliverables.

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

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

docs2/data/events.md

@@ -0,0 +1,32 @@
+# Events and messaging
+
+Platform services emit strongly typed events with JSON schemas. Event files
+use the pattern <event-name>@<version>.json and samples mirror the version.
+
+Envelope types
+- Orchestrator events: versioned envelopes with idempotency keys and trace context.
+- Legacy Redis envelopes: transitional schemas used for older consumers.
+
+Orchestrator envelope fields (v1)
+- eventId, kind, version, tenant
+- occurredAt, recordedAt
+- source, idempotencyKey, correlationId
+- traceId, spanId
+- scope, payload, attributes
+
+Legacy envelope fields
+- eventId, kind, tenant, ts
+- scope, payload, attributes
+
+Versioning rules
+- Additive changes stay in the same version.
+- Breaking changes require a new @<version> schema and matching sample.
+- Consumers should pin and log unknown versions.
+
+Validation
+- Schemas and samples live under docs/events/ and docs/events/samples/.
+- Offline validation uses ajv-cli; keep schema checks deterministic.
+
+Related references
+- docs/events/README.md
+- docs/runtime/SCANNER_RUNTIME_READINESS.md