Ecosystem roadmap

The roadmap separates shipped product paths from future integration work. It is intentionally scoped and does not imply release dates.

Documentation and adoption

• Keep one documentation portal with distinct Agent Lexicon and SkeinRank paths.
• Expand task-oriented tutorials without duplicating exhaustive repository reference docs.
• Add versioned documentation when compatibility guarantees stabilize.
• Publish migration notes when public schemas or CLI contracts change.

Agent Lexicon

• Deepen repository onboarding and review guidance.
• Expand CI examples for review-first and blocking terminology policies.
• Improve evidence quality for documentation markup, generated identifiers, and example-local names.
• Keep optional semantic suggestions separate from deterministic enforcement.
• Validate shared-workspace designs before presenting them as a networked product.

SkeinRank

• Harden the governance API and console for pilot deployments.
• Expand import, export, and reviewable handoff workflows.
• Improve runtime binding diagnostics and rollback documentation.
• Add more search-provider examples beyond the current Elasticsearch path.
• Continue reproducible cross-version terminology evaluation on additional documentation corpora.

Ecosystem integration

• Define an explicit, auditable handoff from repository lexicons to organization-level SkeinRank profiles.
• Preserve independent snapshots and provenance across the dev-time and runtime layers.
• Add integration examples only after the contracts are implemented and tested.

Evidence

• Keep canonical benchmark inputs, commits, labels, and reports public.
• Report label coverage, cutoffs, misses, and hard cases alongside headline metrics.
• Add new corpora and models without rewriting or hiding previous results.

Later

• production deployment and compatibility policy;
• broader provider and storage integrations;
• public demo datasets;
• team governance playbooks;
• hosted services only if their operational and security model is ready.