eden-v1-agent-data-contract-draft

v1 agent data contract (draft) � managed promotions

Linear	EDEN-1713
Repository artifact	knowledge/clients/eden/governance-martech-delivery-model/eden-v1-agent-data-contract-draft.md
Status	Draft � human review. Not policy until published.

Purpose

Define required artifacts for any change promoted from the innovation / staging plane into managed production (analytics, eden-os-rimo, and other repos listed in governance docs).

Required promotion packet fields

Field	Description	Example
Staging artifact ID / link	Commit SHA, PR URL, or staging build ID	https://github.com/org/repo/pull/123
Scope / systems touched	Repos, GCP projects, Segment, Cloudflare, Ads surfaces	analytics, BQ dataset X, Ads offline conversions
Risk class	Low / medium / high (align with EDEN-1715 matrix)	Medium
Expected outcomes	What changes for downstream consumers	�Mart Y adds refill flag Z�
Evidence / checks	Tests run, QA notes, screenshots for UI paths	dbt test, link to staging validation
Rollback plan	Steps + owner + time expectation	Revert PR; flush cache; owner @�
Approvals	Named approvers per matrix	Per EDEN-1715

Rules

1. No packet → no merge on managed production paths (may use waiver doc with incident commander approval; define waivers in EDEN-1716 break-glass policy).
2. Bot and agent authors satisfy the same fields or attach an explicit waiver with scope limits and expiry.

Open questions (human)

• Canonical publication path: Brainforge vault vs Eden KB vs managed repo docs/ � assign one owner.
• CI enforcement timing: template-only (Phase 1) vs required GitHub Action later.