Use this section as the public contributor handbook for Jido. It is the place to link when someone needs the canonical answer for package ownership, support commitments, quality bars, roadmap direction, or how contribution works across the ecosystem.

/community is the social entry point: Discord, public collaboration, and general ways to join in. /docs/contributors is the policy and ownership surface: the handbook contributors, maintainers, and reviewers can cite in issues, pull requests, and onboarding conversations.

Section Contents

• Ecosystem Atlas - public package roster by category with current support level, owner, release status, and purpose
• Package Support Levels - canonical meaning of Stable, Beta, and Experimental
• Package Quality Standards - package bar for repository structure, CI, docs, release hygiene, and review gates
• Observability and Error Reporting Standards - canonical policy for Logger, telemetry, sanitization, and Splode-backed error contracts
• Livebook Authoring Standards - canonical format for runnable docs notebooks, metadata, and drift tests
• Roadmap - current milestone, next milestone, and active epics shaping the ecosystem
• Contributing - who can contribute, where to start, and how lightweight contribution flow works
• Governance and Team Structure - BDFL model, repository ownership, cross-cutting teams, and stewardship expectations

Common Entry Points

• Package lookup or owner lookup: start with Ecosystem Atlas
• Release expectations or package review bar: use Package Support Levels and Package Quality Standards
• Logging, telemetry, or error-contract policy: use Observability and Error Reporting Standards
• Runnable tutorial or cookbook format: use Livebook Authoring Standards
• Where the project is heading and where help is useful now: use Roadmap and Contributing

Next steps

• Ecosystem Atlas - see the current public package roster and ownership map
• Contributing - find the right contribution lane and first step
• Community - join Discord and collaborate in public