Dataface Tasks

M0 Prototype

Status: Complete Date reached: 2026-02-27

Milestone requirements

  • Core Dataface concept validated (YAML -> dashboards).
  • Prototypes established across all workstreams.
  • Testing platform established (unit/integration/visual/JS/eval).
  • Docs/spec-as-code flow established.

Milestone tasks

Show

dft core (Sr Engineer Architect)

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.

cloud suite (UI Design and Frontend Dev)

A runnable prototype path exists for hosted user experience for onboarding, sharing, collaboration, and account/project flows, 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.

inspect profiler (Sr Engineer Architect)

A runnable prototype path exists for warehouse profiling, semantic inference, and analyst-facing data context surfaces, 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.

mcp analyst agent (Data AI Engineer Architect)

A runnable prototype path exists for AI agent tool interfaces, execution workflows, and eval-driven behavior tuning, 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.

ft dash packs (Data Analysis Evangelist and AI Training)

A runnable prototype path exists for connector-specific dashboard packs and KPI narratives for Fivetran sources, 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.

ide extension (Head of Engineering)

A runnable prototype path exists for analyst authoring workflow in VS Code/Cursor with preview, diagnostics, and assist, 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.

chart library (rj)

A runnable prototype path exists for visual language, chart defaults, interaction behavior, and differentiated styling, 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.

context catalog nimble (Data AI Engineer Architect)

A runnable prototype path exists for context schema/catalog contracts and Nimble enrichment flows across product surfaces, 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.

dashboard factory (Data Analysis Evangelist and AI Training)

A runnable prototype path exists for repeatable process for producing, reviewing, and publishing quickstarts/examples, 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.

infra tooling (Sr Engineer Architect)

A runnable prototype path exists for developer tooling, local workflow reliability, and deployment execution safety, 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.

integrations platform (Head of Engineering)

A runnable prototype path exists for deployment, billing, 5T connectivity, and operational reliability/launch integration, 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.