Prerequisite and dependency mapping

Problem

Future connector pack capabilities—such as cross-connector joins, real-time refresh, or AI-assisted pack authoring—each depend on prerequisites in the Dataface platform (new chart types in graph-library, streaming execution in dft-core, metadata APIs for connector schemas). These dependencies are not mapped, so when a future opportunity is prioritized, the team discovers missing prerequisites late, causing delays and re-planning. Mapping dependencies now means that prerequisite work can be opportunistically included in current milestones, dramatically reducing the startup cost when those future capabilities are greenlit.

Context

• Future work on connector-specific dashboard packs and KPI narratives for Fivetran sources will fail or stall if its hidden dependencies stay implicit, so this task should make the enabling conditions visible before anyone commits implementation effort.
• The goal is to understand which technical, product, operational, or partner-side prerequisites gate the most important next bets.
• Expected touchpoints include dashboard pack YAML, dbt/example assets, connector fixtures, and quickstart docs, adjacent workstream plans, external dependencies, and any architectural decisions that would constrain later options.

Possible Solutions

• A - Let each future initiative discover its own blockers as it starts: workable short term, but it creates repeated surprise and thrash.
• B - Recommended: produce a dependency map for the most important future directions: identify technical enablers, ownership gaps, sequencing constraints, and external dependencies up front.
• C - Treat everything as blocked until all possible prerequisites are solved: safe on paper, but too broad to be useful.

Plan

1. List the future directions most likely to matter for connector-specific dashboard packs and KPI narratives for Fivetran sources and enumerate the dependencies each one appears to require.
2. Group those dependencies into themes such as architecture, data/contracts, operations, design, or external approvals and identify likely owners.
3. Highlight the prerequisites that unlock multiple future paths and the ones that are too speculative to prioritize yet.
4. Turn the highest-value prerequisites into sequenced follow-up tasks or explicit decision points rather than leaving them buried in notes.

Implementation Progress

Review Feedback

• [ ] Review cleared