Launch docs and external readiness

Problem

The context catalog has no external-facing documentation — no getting-started guides, no API references for the metadata contract, no examples showing how to use MCP tools or interpret enrichment output. New users outside the organization will have no path to understanding or adopting the system. Internal knowledge exists only in code, design docs, and tribal knowledge from the pilot, none of which is accessible or appropriate for public consumption.

Context

• Even if context schema/catalog contracts and Nimble enrichment flows across product surfaces works, launch will still fail if external users and operators cannot understand setup, limits, and expected behavior from publishable docs.
• This task is about making the product externally explainable: clear setup guidance, examples, troubleshooting, and boundary-setting around what is and is not supported at launch.
• Expected touchpoints include dataface/ai/, context-contract docs, eval wiring, and inspect-derived artifacts, user-facing docs, operator notes, and any examples or screenshots needed to make the launch story concrete.

Possible Solutions

• A - Ship with only internal notes and ad hoc examples: faster, but it shifts launch confusion onto support and sales conversations.
• B - Recommended: produce a focused external-readiness doc set: cover setup, primary workflows, limitations, troubleshooting, and operator/admin guidance where needed.
• C - Delay docs until after launch traffic appears: saves time now, but increases launch-day friction and inconsistent messaging.

Plan

1. Define the minimum documentation set needed for external users, internal operators, and anyone supporting context schema/catalog contracts and Nimble enrichment flows across product surfaces at launch.
2. Draft or update the core guides, examples, known-limits sections, and troubleshooting notes using the actual launch scope.
3. Review the docs against the product behavior and remove any claims that are not yet supportable in the code or operations model.
4. Link the publishable docs to follow-up maintenance owners so launch documentation does not drift immediately after release.

Implementation Progress

Review Feedback

• [ ] Review cleared