type: workstream slug: dft-core name: dft core description: Open-source core runtime, YAML contract, compatibility, and release quality. owner: sr-engineer-architect status: active milestones: m0-prototype: |- A runnable prototype path exists for the YAML contract, compiler/normalizer, execution adapters, and release/versioning, with concrete artifacts that prove the flow works end-to-end in the current codebase. Core assumptions are documented, known constraints are explicit, and the team can explain what is real versus mocked without ambiguity. m1-ft-analytics-analyst-pilot: |- Internal analysts can execute at least one weekly real workflow that depends on the YAML contract, compiler/normalizer, execution adapters, and release/versioning in the 5T Analytics environment, without bespoke engineering intervention for every run. Instrumentation and feedback capture are in place so failures, friction points, and adoption gaps are visible and triaged with owners. m2-internal-adoption-design-partners: |- the YAML contract, compiler/normalizer, execution adapters, and release/versioning is hardened enough for regular use by multiple internal teams and initial design partners, with a predictable response loop for issues and requests. Quality expectations are documented, and prioritized improvements from real usage are actively incorporated into delivery. m3-public-launch: |- Launch scope for the YAML contract, compiler/normalizer, execution adapters, and release/versioning is complete, externally explainable, and supportable: user-facing behavior is stable, documentation is publishable, and operational ownership is explicit. Remaining gaps are non-blocking, risk-assessed, and tracked as post-launch follow-up rather than unresolved launch debt. m4-v1-0-launch: |- Post-launch stabilization is complete for the YAML contract, compiler/normalizer, execution adapters, and release/versioning: recurring incidents are reduced, support burden is lower, and quality gates are enforced consistently before release. The team has a repeatable operating model for maintenance, regression prevention, and measured reliability improvements. m5-v1-2-launch: |- v1.2 delivers meaningful depth improvements in the YAML contract, compiler/normalizer, execution adapters, and release/versioning based on observed usage and retention signals, not just roadmap intent. Enhancements improve real customer outcomes, and release readiness is demonstrated through metrics, regression coverage, and clear migration guidance where relevant. mx-far-future-ideas: |- Long-horizon opportunities for the YAML contract, compiler/normalizer, execution adapters, and release/versioning are captured as concrete hypotheses with user impact, prerequisites, and evaluation criteria. Ideas are ranked by strategic value and feasibility so future investment decisions can be made quickly with less rediscovery.
Open-source core runtime, YAML contract, compatibility, and release quality. This is the engine: the compile/execute/render pipeline that turns YAML dashboard definitions into executable queries and rendered output. Covers the CLI surface, the YAML spec and its normalizer, query execution against warehouses, and the HTML/SVG rendering layer. Owns the OSS release process, versioning contract, and migration story. Adjacent to but distinct from cloud-suite (which is the hosted UX on top of core) and graph-library (which owns chart design within core's rendering layer).
{{ workstream_milestone_rollup("dft-core") }}