Dataface Tasks

M1 5t internal pilot ready

Due Mar 31, 2026

Current152 / 162 (94%)
Exit criteria (0/5)
  • M1 pilot feature bundle is complete and usable across key surfaces: extension + profiler, MCP/Copilot authoring flow, Suite auth/permissions/git/authoring, and AI_CONTEXT beta contract.
  • 5T Analytics raw-source connectivity is live and validated end-to-end in the hosted Fivetran pilot environment.
  • Internal analysts can run weekly real workflows without one-off engineering intervention.
  • Pilot operations are in place: instrumentation, weekly triage cadence, runbooks, and owner-based closure tracking.
  • Pilot readiness decision is explicit: go/no-go recorded with risks, open gaps, and next actions.
KPI targets (0/5)
  • Analyst activation: at least 5 pilot analysts onboarded, with at least 3 weekly active analysts for 2 consecutive weeks.
  • Workflow success rate: at least 80% of tracked pilot workflows complete end-to-end without engineering intervention.
  • Time to value: median time from opening product to first working dashboard is 30 minutes or less.
  • Reliability: no P0 incidents and no unresolved P1 incident older than 5 business days during the pilot window.
  • Pilot sentiment: at least 80% of pilot analysts give a clear thumbs-up to proceed to broader internal rollout.

Tasks by Workstream

Show

dft core (Sr Engineer Architect)

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.

cloud suite (UI Design and Frontend Dev)

Internal analysts can execute at least one weekly real workflow that depends on hosted user experience for onboarding, sharing, collaboration, and account/project flows 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.

inspect profiler (Sr Engineer Architect)

Internal analysts can execute at least one weekly real workflow that depends on warehouse profiling, semantic inference, and analyst-facing data context surfaces 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.

mcp analyst agent (Data AI Engineer Architect)

Internal analysts can execute at least one weekly real workflow that depends on AI agent tool interfaces, execution workflows, and eval-driven behavior tuning 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.

ft dash packs (Data Analysis Evangelist and AI Training)

Internal analysts can execute at least one weekly real workflow that depends on connector-specific dashboard packs and KPI narratives for Fivetran sources 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.

ide extension (Head of Engineering)

Internal analysts can execute at least one weekly real workflow that depends on analyst authoring workflow in VS Code/Cursor with preview, diagnostics, and assist 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.

chart library (rj)

Internal analysts can execute at least one weekly real workflow with a stable basic chart batch in the 5T Analytics environment, without bespoke engineering intervention for every chart. M1 proves the functional chart foundation: the core chart types, working examples, and enough reliability to support repeated analyst use.

context catalog nimble (Data AI Engineer Architect)

Internal analysts can execute at least one weekly real workflow that depends on context schema/catalog contracts and Nimble enrichment flows across product surfaces 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.

dashboard factory (Data Analysis Evangelist and AI Training)

Internal analysts can execute at least one weekly real workflow that depends on repeatable process for producing, reviewing, and publishing quickstarts/examples 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.

infra tooling (Sr Engineer Architect)

Internal analysts and engineers can execute at least one weekly real workflow that depends on developer tooling, local workflow reliability, and deployment execution safety 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.

integrations platform (Head of Engineering)

Internal analysts can execute at least one weekly real workflow that depends on deployment, billing, 5T connectivity, and operational reliability/launch integration 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.