# Public Community Roadmap

This roadmap covers public artifacts and community infrastructure. It does not describe private product internals or unpublished research.

## Now: Foundation

- Establish one GitHub Discussions hub and four clear routes: Learn, Use, Contribute, Partner.
- Publish machine-readable license and contribution boundaries.
- Repair repository descriptions, licenses, citations, and cross-links.
- Add repeatable metadata, link, YAML, and secret-boundary audits.
- Improve Hugging Face cards for artifact-specific use and discussion.

## Next: Participation

- Collect documentation repairs, safe fixtures, public use cases, baselines, and independent experiments.
- Run one public research session and one artifact build session.
- Publish weekly summaries only when there is substantive external activity.
- Recognize accepted contributions in release notes and public ledgers.

## Later: Product Learning

- Identify repeated reliability problems that public artifacts cannot solve alone.
- Offer bounded private diagnostics and design-partner evaluations.
- Productize only a workflow that appears repeatedly across independent users.

## Thirty-Day Test

The initial experiment targets 10 meaningful external participants, five public results or artifact improvements, three returning participants, and three qualified design-partner conversations. These are experimental thresholds, not forecasts.

If targeted invitations and two public sessions produce fewer than three meaningful external participants, the response is to revisit the value proposition, target audience, onboarding friction, and artifact usability. It is not to launch another forum.

See [community/ACTIVATION_30_DAY_PLAN.md](community/ACTIVATION_30_DAY_PLAN.md) for the operating plan and definitions.