v1.2 depth expansion

Problem

After v1.0 stabilization, the context catalog's metadata coverage will still be shallow in many areas — certain data sources, enrichment types, and relationship patterns that users need are not yet supported. Without expanding the depth of metadata coverage based on actual usage data and retention signals, the system will plateau at a level of utility that satisfies early adopters but fails to retain broader users who need richer context for their specific domains and data patterns.

Context

• This milestone should deepen context schema/catalog contracts and Nimble enrichment flows across product surfaces based on what users actually needed after the initial launch, not just what sounded interesting during planning.
• Expansion work is most valuable when it builds on stable foundations and clearly improves real workflows instead of reopening unresolved launch-quality debt.
• Expected touchpoints include dataface/ai/, context-contract docs, eval wiring, and inspect-derived artifacts, usage feedback, and any launch metrics or review artifacts that indicate where extra depth would matter most.

Possible Solutions

• A - Add the next roadmap ideas opportunistically: keeps momentum, but it risks building depth in areas users do not care about.
• B - Recommended: expand the highest-value workflows using observed usage and retention signals: keep scope tied to concrete evidence and stable foundations.
• C - Avoid depth work until a larger redesign is planned: safer, but it leaves real user demand unanswered for too long.

Plan

1. Review post-launch usage, support, and feedback to identify where deeper investment in context schema/catalog contracts and Nimble enrichment flows across product surfaces would most improve real workflows.
2. Define a focused expansion scope with explicit non-goals so new depth does not sprawl into adjacent or unproven ideas.
3. Implement or queue the selected enhancements along with the docs, QA, and migration notes needed to make them safe to adopt.
4. Measure whether the added depth changed user outcomes enough to justify further expansion in the same area.

Implementation Progress

Review Feedback

• [ ] Review cleared