M3 Public Launch

Due May 31, 2026

Planned1 / 68 (1%)

Exit criteria (0/5)

☐ Paid Cloud plans live with Stripe lifecycle handling.
☐ dbt-core OSS release published with migration notes.
☐ Naming/domain rollout complete.
☐ fivetran.com launch surfaces live.
☐ Top 20 connector catalog with 5 dashboards each (target 100).

KPI targets (0/3)

☐ Trial-to-paid baseline established and monitored daily.
☐ Launch incident response coverage staffed.
☐ Launch support SLAs documented and met.

Tasks by Workstream

dft core (Sr Engineer Architect)

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.

☐Launch docs and external readiness — Publish external-facing documentation and examples for execution/runtime adapters that are executable by new users.
☐Launch operations and reliability readiness — Finalize operational readiness for versioning and migrations: telemetry, alerting, support ownership, and incident play…
☐Public launch scope completion — Complete launch-critical scope for YAML contract and normalizer with production-safe behavior and rollback clarity.
☐Publish dbt-core release — Release dbt-core package with install docs, compatibility matrix, and changelog notes.
☐Decide final dft product and CLI naming for public launch — Choose the final external name for dft/dataface before M3 launch, reconciling product positioning, CLI/docs impact, and…
☐Decide markdown report schema naming for boards versus faces — Settle the frontmatter and embed naming for markdown report objects before M3 ships, so report syntax, reusable grouped…
☐Declarative schema definition outside Python code — Define the Dataface YAML spec as a declarative schema document outside of Python Pydantic models — a YAML or JSON schem…
☐Scaffold faces index md and hello yaml in dft init Waiting on decide-markdown-report-schema-naming-for-boards-versus-faces, support-markdown-report-pages-in-faces-with-frontmatter-and-chart-board-embeds — Extend dft init to create a helpful /faces landing page plus hello.yml together, so a fresh repo serves a self-guided s…
☐Support markdown report pages in faces with frontmatter and chart board embeds Waiting on decide-markdown-report-schema-naming-for-boards-versus-faces — Add .md Dataface report pages under /faces with YAML frontmatter plus explicit chart and board embeds, compiling them i…
☐[P3] Support raw Vega-Lite specs in Dataface YAML — Allow raw Vega-Lite blocks in Dataface YAML for advanced use cases while preserving safety and compatibility checks.
☐Discuss authored chart width, height, and aspect ratio controls — Evaluate whether Dataface should expose chart-level width, height, and possibly aspect ratio in authored YAML for Vega-…
☐Extensible schema with custom elements and chart types — Enable users and plugin authors to extend the Dataface schema with custom element types — custom chart types, form inpu…
☐Wire up batch query prefetch before render — Add a prefetch step at the top of render that collects all visible chart queries, uses the existing batch.py infrastruc…

cloud suite (UI Design and Frontend Dev)

Launch scope for hosted user experience for onboarding, sharing, collaboration, and account/project flows 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.

☐Launch docs and external readiness — Publish external-facing documentation and examples for sharing and collaboration surface that are executable by new use…
☐Launch operations and reliability readiness — Finalize operational readiness for account/project lifecycle flows: telemetry, alerting, support ownership, and inciden…
☐Launch paid cloud suite experience — Deliver launch-ready onboarding, account settings, and billing-aware product surfaces for paid cloud users.
☐Public launch scope completion — Complete launch-critical scope for workspace and onboarding UX with production-safe behavior and rollback clarity.

inspect profiler (Sr Engineer Architect)

Launch scope for warehouse profiling, semantic inference, and analyst-facing data context surfaces 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.

☐Launch docs and external readiness — Publish external-facing documentation and examples for semantic inference and context quality that are executable by ne…
☐Launch operations and reliability readiness — Finalize operational readiness for analyst-facing inspector experience: telemetry, alerting, support ownership, and inc…
☐Public launch scope completion — Complete launch-critical scope for profiling pipeline with production-safe behavior and rollback clarity.
☐feat: chart decisions Phase 3 — inspector profile integration — Integrate chart-decision outputs into inspector profiles so profile insights can directly influence recommended visuali…

mcp analyst agent (Data AI Engineer Architect)

Launch scope for AI agent tool interfaces, execution workflows, and eval-driven behavior tuning 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.

☐Launch docs and external readiness — Publish external-facing documentation and examples for agent prompt/workflow behavior that are executable by new users.
☐Launch operations and reliability readiness — Finalize operational readiness for eval and guardrail framework: telemetry, alerting, support ownership, and incident p…
☐Public launch scope completion — Complete launch-critical scope for MCP tool execution model with production-safe behavior and rollback clarity.
☐Add deterministic candidate selection baselines for bounded text-to-SQL Waiting on build-bounded-non-one-shot-text-to-sql-stack-for-local-evals — Compare simple winner-selection heuristics such as first valid parse fewest grounding errors and best plan overlap befo…
☐Add latest regression delta dashboards for text-to-SQL evals Waiting on build-text-to-sql-failure-taxonomy-and-slice-dashboard — Show newly fixed newly broken and severity-shifted benchmark cases between runs so eval iteration can focus on concrete…
☐Add retrieval-side gold labels to text-to-SQL benchmark — Augment benchmark cases with expected tables columns and semantic targets so retrieval quality can be measured directly…
☐Add semantic SQL diff and partial-credit scoring — Score tables filters grouping aggregation ordering and other semantic components separately so near misses are measurab…
☐Add structured planning evals separate from final SQL quality Waiting on build-bounded-non-one-shot-text-to-sql-stack-for-local-evals — Evaluate planner outputs for table filter grain and metric selection independently from final SQL so planning quality c…
☐Build text-to-SQL failure taxonomy and slice dashboard — Classify benchmark failures by table column join filter aggregation grain ordering and syntax mistakes and surface thos…
☐Capture candidate plan and repair telemetry in eval artifacts Waiting on build-bounded-non-one-shot-text-to-sql-stack-for-local-evals — Persist planner outputs candidate rejection reasons repair attempts and winner selection metadata so bounded non-one-sh…
☐Compare question bundle variants for text-to-SQL evals Waiting on compare-text-to-sql-evals-with-question-aware-retrieval-vs-full-context-prompting — Run structured evals comparing full context against multiple bundle variants such as relationships plan hints and value…
☐Desktop app - lightweight wrapper around Dataface Cloud web UI — Build a desktop application that wraps the Dataface Cloud web interface. Provides native OS integration like menu bar,…
☐Patch-based AI edits for dashboard YAML — Instead of AI regenerating entire YAML files when refining dashboards, support targeted YAML patches inspired by json-r…
☐Schema-derived AI prompts from compiled types — Auto-generate LLM system prompts from the Dataface schema definition rather than hand-maintaining prompt templates. Ins…
☐Skill and tool quality evaluation framework — Build a framework to A/B test whether individual MCP skills improve agent output quality vs raw tool access. Measure sk…

ft dash packs (Data Analysis Evangelist and AI Training)

Launch scope for connector-specific dashboard packs and KPI narratives for Fivetran sources 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.

☐Launch docs and external readiness — Publish external-facing documentation and examples for dashboard narrative quality that are executable by new users.
☐Launch operations and reliability readiness — Finalize operational readiness for pack publishing workflow: telemetry, alerting, support ownership, and incident playb…
☐Public launch scope completion — Complete launch-critical scope for connector pack coverage with production-safe behavior and rollback clarity.
☐Release top 20 connector packs with 5 dashboards each — Publish 100 launch dashboards across top 20 Fivetran connectors with QA signoff.

ide extension (Head of Engineering)

Launch scope for analyst authoring workflow in VS Code/Cursor with preview, diagnostics, and assist 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.

☐Launch docs and external readiness — Publish external-facing documentation and examples for IDE diagnostics and guidance that are executable by new users.
☐Launch operations and reliability readiness — Finalize operational readiness for inspector/agent integration in IDE: telemetry, alerting, support ownership, and inci…
☐Public launch scope completion — Complete launch-critical scope for editor + preview workflow with production-safe behavior and rollback clarity.
☐Cross-dashboard changed charts view with canonical links — In the IDE extension, provide a unified view that lists every chart across all dashboards that is affected by changes:…

chart library (rj)

Launch scope for the chart library is complete, externally explainable, and supportable: starter dashboard composition patterns exist beyond the playground, data-informed chart properties are driving more of the default behavior, 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.

☐Launch docs and external readiness — Publish external-facing documentation and examples for chart default behavior that are executable by new users.
☐Launch operations and reliability readiness — Finalize operational readiness for interaction/accessibility polish: telemetry, alerting, support ownership, and incide…
☐Public launch scope completion — Complete launch-critical scope for visual language system with production-safe behavior and rollback clarity.
☐feat: Brushing/selections with range variables — Add brushing and range-variable selections so charts can drive cross-filtered interactions and exploratory analysis.
☐Launch-ready chart quality pass — Execute final quality pass on launch chart templates for consistency, readability, and performance.
☐Starter dashboard composition patterns — Turn the basic chart corpus into deliberate starter dashboard patterns, beginning from playground examples and pushing…
☐Optimization: Batch Vega-Lite chart rendering for ~30% speedup — Batch Vega-Lite rendering to reduce chart render overhead and target roughly 30% performance improvement.

context catalog nimble (Data AI Engineer Architect)

Launch scope for context schema/catalog contracts and Nimble enrichment flows across product surfaces 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.

☐Launch docs and external readiness — Publish external-facing documentation and examples for context enrichment rules that are executable by new users.
☐Launch operations and reliability readiness — Finalize operational readiness for cross-surface context contract: telemetry, alerting, support ownership, and incident…
☐Public launch scope completion — Complete launch-critical scope for context schema model with production-safe behavior and rollback clarity.
☐Add join-path grounding to question-scoped context bundles Waiting on build-question-aware-schema-search-and-isolation-cli-over-inspect-json-and-dbt-metadata — Teach bundles to surface likely join paths and key relationships between retained tables so the SQL generator sees how…
☐Build lightweight value hints retrieval from inspect artifacts Waiting on build-question-aware-schema-search-and-isolation-cli-over-inspect-json-and-dbt-metadata — Expose cheap static filter-disambiguation hints such as enum-like values date ranges and high-signal categorical member…
☐QUERY_VALIDATOR foundation and first integrations — Build the first query validator path using SQLGlot plus schema profile grain and relationship context for query review…

dashboard factory (Data Analysis Evangelist and AI Training)

Launch scope for repeatable process for producing, reviewing, and publishing quickstarts/examples 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.

☐Launch docs and external readiness — Publish external-facing documentation and examples for quality rubric + review process that are executable by new users.
☐Launch operations and reliability readiness — Finalize operational readiness for publication throughput operations: telemetry, alerting, support ownership, and incid…
☐Public launch scope completion — Complete launch-critical scope for template production pipeline with production-safe behavior and rollback clarity.
☐Operationalize quickstart production line — Run weekly production cadence for quickstart/example dashboards with review gates and publish tracking.

infra tooling (Sr Engineer Architect)

Launch scope for developer tooling, local workflow reliability, and deployment execution safety 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.

☐M3 public launch closure, operations, and go-no-go — Own the M3 closure artifact: verify public-launch scope, operating readiness, launch checklists, and owner-based closur…
☑Pilot Claude Code auto mode instead of skip-permissions CompletedPR #784PR at 2026-03-24T22:08:59-07:00 — Anthropic shipped Claude Code auto mode: a classifier gates destructive or high-risk tool use while allowing routine ed…

integrations platform (Head of Engineering)

Launch scope for deployment, billing, 5T connectivity, and operational reliability/launch integration 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.

☐Launch docs and external readiness — Publish external-facing documentation and examples for billing/connectivity operations that are executable by new users.
☐Launch operations and reliability readiness — Finalize operational readiness for reliability + launch operations: telemetry, alerting, support ownership, and inciden…
☐Launch Stripe billing lifecycle — Implement Stripe product catalog, checkout, subscription lifecycle, and webhook-driven state sync.
☐Public launch scope completion — Complete launch-critical scope for platform deployment/integration path with production-safe behavior and rollback clar…
☐Integrate launch surfaces on fivetran.com Planned — Ship fivetran.com entry points, quickstart routing, and product messaging integration for launch.