prep docs and service updates

docs/events/prep/2025-11-20-advisoryai-orchestrator-followup.md

@@ -0,0 +1,16 @@
+# Escalation Follow-up Prep — PREP-ESCALATION-FOLLOW-UP-ADVISORYAI-ORCHESTR
+
+Status: Draft (2025-11-20)
+Owners: Planning · AdvisoryAI Guild · Orchestrator Service Guild · Notifications Guild
+Scope: Track follow-up actions and ETAs for overdue AdvisoryAI evidence bundle schema and Orchestrator/Notifications envelopes.
+
+## Follow-up actions
+- Request revised ETA from AdvisoryAI for evidence bundle schema + payload notes; log hash placeholder and target drop date.
+- Request revised ETA from Orchestrator/Notifications for capsule envelope and notification samples; confirm subject names and retention policy.
+- If no ETA by 2025-11-21, escalate to Wave 150/140 leads and mark dependent sprint tasks BLOCKED explicitly with this reference.
+
+## Recording commitments
+- Capture responses (ETA/date + owner) in this file under a new “Commitments” section and mirror them into sprints 110/140/150/160/161/162/165.
+
+## Handoff
+This file is the published artefact for PREP-ESCALATION-FOLLOW-UP-ADVISORYAI-ORCHESTR. Update once responses arrive; if still silent by 2025-11-21, annotate with “No response” and keep dependents BLOCKED.

docs/events/prep/2025-11-20-orchestrator-notifications-schema-handoff.md

@@ -0,0 +1,18 @@
+# Orchestrator / Notifications Schema Handoff Prep — PREP-ORCHESTRATOR-NOTIFICATIONS-SCHEMA-HANDOF
+
+Status: Draft (2025-11-20)
+Owners: Orchestrator Service Guild · Notifications Guild · Planning
+Scope: Capture the exact deliverables needed for the overdue schema handoff so downstream EvidenceLocker/ExportCenter/TimelineIndexer work can proceed.
+
+## Expected deliverables
+- **Capsule envelope schema** including `replay_id`, `dsse_envelope_hash`, `tenant_id`, `timeline_cursor`, `event_id`, `occurred_at`.
+- **Transport bindings** for NATS/Redis topics with subject names and durable stream config; retention and dedupe requirements.
+- **Samples**: at least one signed capsule example and one notification example referencing a replay record.
+- **Versioning**: place canonical schema in `docs/events/orchestrator-scanner-events.md` and bump version tag; add samples under `docs/events/samples/`.
+
+## Acceptance for unblock
+- Schema + samples merged and checksummed; subject naming confirmed.
+- Hash and version recorded back into sprint trackers (160, 161, 162, 165) under Decisions & Risks.
+
+## Handoff
+Use this document as the published prep artefact for PREP-ORCHESTRATOR-NOTIFICATIONS-SCHEMA-HANDOF.