Future opportunity research

Problem

The profiling pipeline has natural extension points — cross-table relationship detection, data lineage integration, anomaly alerting on profile drift, AI-powered column documentation generation — but these ideas exist only as scattered conversations and undocumented intuitions. Without a structured research capture that evaluates each opportunity's user impact, technical feasibility, and strategic fit within Dataface's roadmap, the team risks either pursuing low-impact ideas when bandwidth opens up or losing high-impact ideas because nobody wrote them down. A curated opportunity backlog grounded in profiler-specific user needs would ensure future investment is directed at the highest-leverage extensions.

Context

• There are plausible future bets for warehouse profiling, semantic inference, and analyst-facing inspect/context artifacts, but they should be captured as concrete opportunities with user value and strategic fit rather than as loose brainstorming.
• This task should separate genuinely promising directions from attractive-but-vague ideas and tie each candidate to the product or platform outcomes it could improve.
• Expected touchpoints include dataface/core/inspect/, schema-context consumers, inspect docs, and core tests, roadmap notes, adjacent workstream dependencies, and any evidence from users that points toward a longer-horizon opportunity.

Possible Solutions

• A - Keep future ideas as an unstructured backlog list: easy to collect, but hard to prioritize or revisit intelligently.
• B - Recommended: turn future ideas into structured opportunity notes: describe user value, strategic rationale, dependencies, and why each idea is worth considering later.
• C - Skip future opportunity work until all near-term milestones are complete: lowers distraction, but loses useful strategic context.

Plan

1. Gather the strongest future ideas for warehouse profiling, semantic inference, and analyst-facing inspect/context artifacts from roadmap discussions, usage feedback, and adjacent workstream needs.
2. Write a structured note for each opportunity covering user value, likely scope, dependencies, and the signals that would justify investment.
3. Rank the opportunities relative to each other and explicitly note which ones are interesting but not yet credible.
4. Link the top opportunities to prerequisite or experiment tasks so they can mature without being mistaken for near-term commitments.

Implementation Progress

Review Feedback

• [ ] Review cleared