orchestrator-kickoff-plan

Eden orchestrator kickoff plan

This plan operationalizes orchestrator-prompt-final.md against the current EDEN ticket block.

Scope and objective

• Scope: EDEN-1713, 1714, 1717, 1718, 1719, 1720, 1721, 1724, 1726, 1739, 1740, 1741
• Objective: move work from “policy intent” into enforceable ownership and reviewable execution artifacts.

Ticket mapping (what to execute now)

Ticket	Immediate action	Owner gate
EDEN-1713	Finalize v1 contract fields + publication path	Delivery + Eden sign-off
EDEN-1714	Approve staging vs managed boundaries	BF + Eden policy sign-off
EDEN-1717	Run principal parity inventory and publish PASS/FAIL	Human IAM approval
EDEN-1718	Complete Ads Data Manager trace worksheet	Human validation in Ads + GCP
EDEN-1719	Finalize refill semantics matrix with stakeholders	Marketing + clinical sign-off
EDEN-1720	Expand playbook outline to versioned operating playbook	Engineering review
EDEN-1721	Apply minimal analytics PR template in managed repos	Repo admin merge + branch protection
EDEN-1724	Seed generated pipeline catalog and manual overrides	Data Platform verification
EDEN-1726	Approve monorepo + orchestration blueprint sequencing	Architecture review
EDEN-1739	Execute discoverability RCA runbook and rank causes	Human RCA owner decision
EDEN-1740	Record refill-to-Ads verdict with evidence	Human attestation
EDEN-1741	Verify Dagster/dbt narrative vs actual linkage	Human attestation

Sub-agent operating model (design now, automate next)

Listening/risk agent

• Cadence: daily
• Writes: one Linear issue/comment with risk class, affected systems, links, requires-spike flag, recommended owner.
• Guardrail: human triage before opening new high-priority tickets.

Governance review agent

• Trigger: PR opened on managed repos or scheduled policy sweep.
• Writes: pass/fail checklist with evidence links to same Linear issue.
• Guardrail: block recommendation when contract/parity evidence missing.

Managed enforcement checklist (repo-specific)

• analytics / managed repos:
  • Branch protection + required checks
  • CODEOWNERS + required reviewers
  • Minimal PR template fields (Linear ID, scope, evidence, PII boundary attestation, rollback one-liner)
  • Merge blocked on missing contract/parity proof for activation paths
• eden-marketing-architecture-implementation:
  • Keep staging guardrails (.agents/, preflight, handoff docs)
  • Link external-change handoffs to Linear issue
  • Do not present staging controls as analytics enforcement

Canonical source of truth rules

1. Linear issue is the single canonical state for managed-impacting changes.
2. Staging handoff docs are linked artifacts, not backlog records.
3. Slack is notification-only; no scope or decision ownership.
4. If any source disagrees, Linear wins.

Done criteria for kickoff

• Every ticket above has:
  • one linked artifact in Linear attachments
  • one repo-relative path in comments or description
  • clear human review gate called out
• Orchestrator ownership statement is present in docs and project-level narrative.
• No claim that staging scripts enforce analytics policy.