You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(orchestration): relabel Airflow/Dagster/Temporal as developer-extension examples + ADR-0021
Per the optional-scope decisions (ADR-0021): orchestration backends are developer
extension examples (Prefect is the shipped default), cloud connectors are
enterprise-only, DOCX/XLSX export will be implemented.
- Relabeled the 3 backend stubs (docstrings + NotImplementedError messages) and
test_orchestration_stubs.py match from 'Phase 0 stub' to 'developer-extension
example'. mypy + ruff clean, 3 tests pass.
- New ADR-0021 records all three dispositions (Phase 9 decision record).
- Completion-plan check-offs: Phase 9 orchestration + connector decisions, Phase 4
connector matrix decision, Phase 8 readiness (darkstar/python-ai/redis/PACS via
the new sidecars:readiness command).
Co-Authored-By: claude-flow <ruv@ruv.net>
Cloud Spanner) rendered as a "Coming Soon" grid in the add-source wizard, with
30
+
no implementation behind them.
31
+
-**Airflow / Dagster / Temporal** orchestration backends shipped as
32
+
`NotImplementedError` "Phase 0 stub"s (Prefect is the implemented default).
33
+
-**DOCX / XLSX** publish-export controls shown with "Coming soon" badges and no
34
+
backend.
35
+
36
+
Phase 9's acceptance is that every deferred optional surface becomes either a
37
+
closed decision record or a committed plan — not an indefinite placeholder.
38
+
39
+
## Decision (2026-06-21)
40
+
41
+
| Surface | Disposition | Rationale |
42
+
|---|---|---|
43
+
| Cloud warehouse connectors |**Enterprise-only**| Keep visible but gate behind an enterprise tier rather than implying imminent community availability. They remain a real roadmap commitment, scoped to Enterprise. |
44
+
| Airflow / Dagster / Temporal backends |**Developer-extension examples**| Prefect is the shipped orchestration backend. The other three are intentional extension points demonstrating the portable `OrchestrationBackend` seam — not core product promises. Relabeled accordingly (this ADR's commit). |
45
+
| DOCX / XLSX publish export |**Implement**| These are reasonable, bounded additions to the existing publish-export path; build the backends and wire the controls. |
46
+
47
+
## Consequences / status
48
+
49
+
-**Orchestration (done in this commit):** the three backend modules and their
50
+
test were relabeled from "Phase 0 stub" to "developer-extension example"
0 commit comments