Eden monorepo + orchestration harness � blueprint (draft)
| |
|---|
| Linear | EDEN-1726 |
| Repository artifact | knowledge/clients/eden/governance-martech-delivery-model/eden-monorepo-orchestration-blueprint-draft.md |
| Status | Architecture review required � not implementation orders. |
Target consolidation
| Current repo / area | Role after consolidation | Notes |
|---|
analytics | Managed dbt + CI packages | Baseline dbt + GHA |
| Remo / Rimo-adjacent | Packages or subtree | Confirm exact repo names |
MarTech agent repo (eden-marketing-architecture-implementation) | Innovation plane packages | RBAC for agents |
Orchestration
- Lift Brainforge-hosted pipeline entrypoints into Eden-visible Dagster + dbt harness when infra ready.
- Dagster provides DAG-level permissions beyond README-only policy.
Phased migration (outline)
| Phase | Deliverable | Exit criterion |
|---|
| 1 | Folder taxonomy + ownership diagram | Signed by BF + Eden |
| 2 | CI entrypoints documented per package | Green builds |
| 3 | IAM for automation principals | Least privilege verified |
Risks
- Big-bang moves � prefer slice-by-slice migration with rollback branch strategy.
Open questions
- Final repo name / GitHub org.
- Which packages move first (recommend: analytics dbt core before agent harness).