Roadmap: simplify, dogfood, release, and grow Concord Loom

[PullDakar]

Product outcome

Make Concord Loom simpler to adopt, safer to evolve, easier to release, and easier to discover.

P0 — simplify before expanding

• [P0] Establish a Repository Field Lab and friction feedback loop #28
• [P0] Replace mandatory role ownership with capability-first authority #29

P1 — make the product releasable and discoverable

• [P1] Define and dogfood a release lifecycle with enforceable quality gates #30
• [P1] Improve the public site for first-time onboarding and conversion #31
• [P1] Establish technical SEO and measurable organic search discovery #32
• [P1] Enforce Concord Loom self-dogfooding for repository changes #35

P2 — expand the ecosystem after the core workflow is proven

• [P2] Introduce a provider-neutral agent adapter and Claude conformance suite #33
• [P2] Define portable Cycle Packages and registry imports before building a marketplace #34

Sequencing rules

• Repository evidence may motivate a proposal; it does not accept product intent.
• Role simplification must preserve capability, independence, publication, and activation boundaries.
• Provider support follows a shared adapter contract and conformance suite.
• Cycle Package Specification and demonstrated reuse come before marketplace UI.
• Search Console submission is a baseline, not proof of indexing or ranking.
• Every successor remains non-self-activating.

Roadmap review

Review priority after the first Repository Field Lab cohort and after every release-cycle dry run. Record observed evidence separately from proposed reprioritization.