docs: refresh contributor handbook

Author: mikehostetler

lib/agent_jido/ecosystem/package.ex

@@ -114,6 +114,9 @@ defmodule AgentJido.Ecosystem.Package do
               github_url: Zoi.string(description: "GitHub repository URL") |> Zoi.optional(),
               github_org: Zoi.string(description: "GitHub organization") |> Zoi.default("agentjido"),
               github_repo: Zoi.string(description: "GitHub repository name") |> Zoi.optional(),
+              tech_lead:
+                Zoi.string(description: "Canonical GitHub-handle-first owner or tech lead for the package")
+                |> Zoi.optional(),
               elixir: Zoi.string(description: "Required Elixir version") |> Zoi.optional(),
               ecosystem_deps:
                 Zoi.any(description: "List of ecosystem package id strings this depends on")

priv/content_plan/docs/contributors/_hub.md

@@ -10,20 +10,24 @@
   destination_route: "/docs/contributors",
   ecosystem_packages: ["jido", "agent_jido"],
   learning_outcomes: ["Find the canonical ecosystem-level contribution standards",
-   "Identify which contributor checklist or policy page applies to a package change"],
+   "Identify which contributor page answers package ownership, support, quality, roadmap, or governance questions"],
   order: 1,
   prerequisites: [],
-  purpose: "Section root organizing contributor-facing policy, package standards, and shared ecosystem workflows",
-  related: ["docs/contributors/package-quality-standards", "docs/guides/_hub", "docs/reference/_hub"],
+  purpose: "Section root organizing contributor-facing policy, package ownership, roadmap, and shared ecosystem workflows",
+  related: ["docs/contributors/ecosystem-atlas", "docs/contributors/package-support-levels",
+   "docs/contributors/package-quality-standards", "docs/contributors/roadmap",
+   "docs/contributors/contributing", "docs/contributors/governance-and-team"],
   prompt_overrides: %{
-    document_intent: "Create the contributors section hub that routes maintainers and outside contributors to canonical ecosystem contribution guidance.",
-    required_sections: ["Overview", "Start Here", "What Belongs Here"],
-    must_include: ["One-line description of the package quality standards page",
-     "Clear statement that this section is the canonical contributor policy surface for the Jido ecosystem"],
-    must_avoid: ["Duplicating the full checklist from child pages", "Long prose"],
-    required_links: ["/docs/contributors/package-quality-standards", "/docs/guides", "/docs/reference"],
+    document_intent: "Create the contributors section hub that routes maintainers and outside contributors to the canonical ecosystem handbook pages.",
+    required_sections: ["Section Contents", "Common Entry Points"],
+    must_include: ["Clear distinction between `/community` and `/docs/contributors`",
+     "One-line description of each contributor page"],
+    must_avoid: ["Duplicating the full content of child pages", "Long prose"],
+    required_links: ["/docs/contributors/ecosystem-atlas", "/docs/contributors/package-support-levels",
+     "/docs/contributors/package-quality-standards", "/docs/contributors/roadmap",
+     "/docs/contributors/contributing", "/docs/contributors/governance-and-team", "/community"],
     min_words: 150,
-    max_words: 400,
+    max_words: 450,
     minimum_code_blocks: 0,
     diagram_policy: "none",
     section_density: "minimal",
@@ -33,10 +37,10 @@
 ---
 ## Content Brief
 
-Section root for Contributors. Organizes canonical contributor policy and ecosystem package standards.
+Section root for Contributors. Organizes canonical contributor policy, ownership, roadmap, and ecosystem package standards.
 
 ### Validation Criteria
 
-- Makes it obvious this is the contributor-facing standards area
-- Links directly to package quality standards
-- Keeps copy compact and easy to reference from PRs
+- Makes it obvious this is the contributor-facing handbook
+- Distinguishes `/community` from `/docs/contributors`
+- Links directly to all six contributor child pages

priv/content_plan/docs/contributors/contributing.md

@@ -0,0 +1,44 @@
+%{
+  priority: :high,
+  status: :outline,
+  title: "Contributing Guide",
+  repos: ["agent_jido"],
+  tags: [:docs, :contributors, :contributing],
+  audience: :beginner,
+  content_type: :guide,
+  destination_collection: :pages,
+  destination_route: "/docs/contributors/contributing",
+  ecosystem_packages: ["jido", "agent_jido"],
+  learning_outcomes: ["Find the right contribution lane",
+   "Understand how to start small and how stewardship works"],
+  order: 5,
+  prerequisites: [],
+  purpose: "Contributor-facing guide for entering Jido contribution work across code, docs, testing, and stewardship",
+  related: ["docs/contributors/package-quality-standards", "docs/contributors/governance-and-team",
+   "docs/community/_hub"],
+  prompt_overrides: %{
+    document_intent: "Write the contributing page as a lightweight guide to participation and flow.",
+    required_sections: ["Contribution Lanes", "Lightweight Contribution Flow", "How to Start Small"],
+    must_include: ["Code, docs, examples, testing, and community contribution lanes",
+     "Explanation that package stewardship is a contribution path"],
+    must_avoid: ["Heavy process language", "Community CTA duplication that belongs on `/community`"],
+    required_links: ["/community", "/docs/contributors/package-quality-standards",
+     "/docs/contributors/governance-and-team"],
+    min_words: 350,
+    max_words: 900,
+    minimum_code_blocks: 0,
+    diagram_policy: "none",
+    section_density: "minimal",
+    max_paragraph_sentences: 2
+  }
+}
+---
+## Content Brief
+
+Contributor-facing guide for how people join and work in the ecosystem.
+
+### Validation Criteria
+
+- Makes it clear contributors can start small
+- Covers package stewardship as a lightweight path
+- Links to `/community` for social entry rather than duplicating it

priv/content_plan/docs/contributors/ecosystem-atlas.md

@@ -0,0 +1,49 @@
+%{
+  priority: :high,
+  status: :outline,
+  title: "Ecosystem Atlas",
+  repos: ["agent_jido"],
+  tags: [:docs, :contributors, :ecosystem, :ownership],
+  audience: :intermediate,
+  content_type: :reference,
+  destination_collection: :pages,
+  destination_route: "/docs/contributors/ecosystem-atlas",
+  ecosystem_packages: ["jido", "jido_action", "jido_signal", "jido_ai", "req_llm"],
+  learning_outcomes: ["Find the current public package roster and ownership map",
+   "Distinguish support label from release state and package purpose"],
+  order: 2,
+  prerequisites: [],
+  purpose: "Contributor-facing public package roster organized by the current brainstorm ecosystem groups with support level, owner, release state, and purpose",
+  related: ["docs/contributors/package-support-levels", "docs/contributors/roadmap",
+   "ecosystem/overview"],
+  prompt_overrides: %{
+    document_intent: "Write the Ecosystem Atlas page as a concise contributor-facing package roster.",
+    required_sections: ["Integration / Framework", "Core / Runtime", "AI / LLM",
+     "Messaging", "Harness / CLI", "Planning / Control", "Runtime / Interfaces",
+     "Runtime / Distributed", "Memory / Storage", "Observability / Telemetry",
+     "Developer Tools / UI", "Automation / Bots", "Evaluation / Testing"],
+    must_include: ["One compact markdown table per category",
+     "Columns for package, support, owner, release, and purpose",
+     "Short note that deeper package pages live under `/ecosystem`",
+     "Group names aligned to the current `jido_brainstorm` ecosystem inventory"],
+    must_avoid: ["Private packages", "Long package-by-package narrative"],
+    required_links: ["/ecosystem", "/docs/contributors/package-support-levels",
+     "/docs/contributors/roadmap"],
+    min_words: 500,
+    max_words: 1200,
+    minimum_code_blocks: 0,
+    diagram_policy: "none",
+    section_density: "minimal",
+    max_paragraph_sentences: 2
+  }
+}
+---
+## Content Brief
+
+Contributor-facing package roster for the public Jido ecosystem.
+
+### Validation Criteria
+
+- Includes only public packages
+- Groups packages by the current brainstorm ecosystem sections
+- Shows owner handles and release state distinctly from support level

priv/content_plan/docs/contributors/governance-and-team.md

@@ -0,0 +1,43 @@
+%{
+  priority: :medium,
+  status: :outline,
+  title: "Governance and Team Structure",
+  repos: ["agent_jido"],
+  tags: [:docs, :contributors, :governance, :team],
+  audience: :intermediate,
+  content_type: :guide,
+  destination_collection: :pages,
+  destination_route: "/docs/contributors/governance-and-team",
+  ecosystem_packages: ["jido", "agent_jido"],
+  learning_outcomes: ["Understand how Jido makes decisions",
+   "Understand how repository ownership and cross-cutting teams fit together"],
+  order: 6,
+  prerequisites: [],
+  purpose: "Contributor-facing governance page describing the BDFL model, repository ownership, and cross-cutting teams",
+  related: ["docs/contributors/ecosystem-atlas", "docs/contributors/contributing"],
+  prompt_overrides: %{
+    document_intent: "Write the governance page as a direct explanation of responsibility and decision making.",
+    required_sections: ["Governance Model", "Repository Ownership", "Cross-Cutting Teams", "Inactive Ownership"],
+    must_include: ["Mike Hostetler as BDFL",
+     "Community team present without a named lead unless updated elsewhere",
+     "Documentation lead as TBD unless updated elsewhere"],
+    must_avoid: ["Corporate or bureaucratic language", "Hidden ownership assumptions"],
+    required_links: ["/docs/contributors/ecosystem-atlas", "/docs/contributors/contributing"],
+    min_words: 350,
+    max_words: 900,
+    minimum_code_blocks: 0,
+    diagram_policy: "none",
+    section_density: "minimal",
+    max_paragraph_sentences: 2
+  }
+}
+---
+## Content Brief
+
+Contributor-facing governance and responsibility guide.
+
+### Validation Criteria
+
+- Explains the lightweight BDFL model clearly
+- Makes repository ownership explicit and links to the atlas
+- Covers inactive ownership handling and cross-cutting teams

priv/content_plan/docs/contributors/package-quality-standards.md

@@ -15,16 +15,18 @@
   order: 10,
   prerequisites: ["docs/contributors/_hub"],
   purpose: "Canonical contributor-facing checklist for Jido ecosystem package quality, CI, documentation coverage, and GitOps-style release readiness",
-  related: ["docs/reference/configuration", "docs/guides/testing-agents-and-actions", "ecosystem/overview"],
+  related: ["docs/contributors/ecosystem-atlas", "docs/contributors/package-support-levels",
+   "docs/reference/configuration", "docs/guides/testing-agents-and-actions", "ecosystem/overview"],
   source_files: ["GENERIC_PACKAGE_QA.md"],
   prompt_overrides: %{
     document_intent: "Create the canonical package standards page contributors and agents should use to verify Jido ecosystem package quality requirements.",
-    required_sections: ["Scope", "Package Structure", "Shared Building Blocks", "Quality Gates", "Release Workflow", "Contributor Checklists"],
-    must_include: ["Explicit `mix quality` policy",
-     "GitOps-style release workflow expectations",
+    required_sections: ["Fast Path Checklist", "How to use this page", "Package Structure", "Shared Building Blocks", "Quality Gates", "Release Workflow", "Contributor Checklists"],
+    must_include: ["Short explanation that quality standards are distinct from support levels",
+     "Explicit `mix quality` policy", "GitOps-style release workflow expectations",
      "Contributor checklists for new packages, first release, and ongoing maintenance"],
     must_avoid: ["Package-specific implementation details that belong in per-repo docs"],
-    required_links: ["/docs/contributors", "/docs/reference", "/ecosystem"],
+    required_links: ["/docs/contributors", "/docs/contributors/ecosystem-atlas",
+     "/docs/contributors/package-support-levels", "/docs/reference", "/ecosystem"],
     min_words: 900,
     max_words: 2200,
     minimum_code_blocks: 3,
@@ -40,6 +42,8 @@ Canonical checklist and standards page for public Jido ecosystem packages. This
 
 ### Validation Criteria
 
+- Includes a fast review path near the top
+- Distinguishes quality standards from support level and package roster pages
 - Covers repo structure, quality gates, docs coverage, CI, and release workflow
 - States the canonical package policies clearly enough to link from PRs
 - Includes actionable checklists, not just prose

priv/content_plan/docs/contributors/package-support-levels.md

@@ -0,0 +1,42 @@
+%{
+  priority: :high,
+  status: :outline,
+  title: "Package Support Levels",
+  repos: ["agent_jido"],
+  tags: [:docs, :contributors, :support, :taxonomy],
+  audience: :intermediate,
+  content_type: :reference,
+  destination_collection: :pages,
+  destination_route: "/docs/contributors/package-support-levels",
+  ecosystem_packages: ["jido", "jido_ai", "req_llm"],
+  learning_outcomes: ["Understand the meaning of Stable, Beta, and Experimental",
+   "Avoid confusing support labels with roadmap priority or release state"],
+  order: 3,
+  prerequisites: [],
+  purpose: "Canonical support taxonomy for public Jido packages",
+  related: ["docs/contributors/ecosystem-atlas", "docs/contributors/roadmap"],
+  prompt_overrides: %{
+    document_intent: "Write the package support levels page as a tight policy reference.",
+    required_sections: ["Support Levels", "What This Label Is And Is Not", "When To Use Each Label"],
+    must_include: ["Clarification that support level is not packaging status",
+     "Clarification that support level is not roadmap priority"],
+    must_avoid: ["Package-by-package roster detail"],
+    required_links: ["/docs/contributors/ecosystem-atlas", "/docs/contributors/roadmap"],
+    min_words: 300,
+    max_words: 800,
+    minimum_code_blocks: 0,
+    diagram_policy: "none",
+    section_density: "minimal",
+    max_paragraph_sentences: 2
+  }
+}
+---
+## Content Brief
+
+Canonical support taxonomy for public Jido packages.
+
+### Validation Criteria
+
+- Keeps definitions separate from package assignments
+- Explains how contributors should choose a support label
+- Distinguishes support commitment from release state and roadmap sequencing

priv/content_plan/docs/contributors/roadmap.md

@@ -0,0 +1,42 @@
+%{
+  priority: :medium,
+  status: :outline,
+  title: "Contributors Roadmap",
+  repos: ["agent_jido"],
+  tags: [:docs, :contributors, :roadmap],
+  audience: :intermediate,
+  content_type: :guide,
+  destination_collection: :pages,
+  destination_route: "/docs/contributors/roadmap",
+  ecosystem_packages: ["jido", "jido_chat", "jido_harness"],
+  learning_outcomes: ["Understand the current milestone and next milestone",
+   "See how roadmap timing differs from support commitment"],
+  order: 4,
+  prerequisites: [],
+  purpose: "Contributor-facing roadmap page translating milestone and epic planning into a compact public guide",
+  related: ["docs/contributors/package-support-levels", "docs/contributors/ecosystem-atlas"],
+  prompt_overrides: %{
+    document_intent: "Write a concise contributor-facing roadmap page from the current milestone planning.",
+    required_sections: ["Major Milestones", "Current Milestone", "Next Milestone", "Active Epics"],
+    must_include: ["Current milestone, next milestone, and active epics",
+     "Clarification that roadmap timing differs from support level"],
+    must_avoid: ["Backlog-level detail", "Long historical narrative"],
+    required_links: ["/docs/contributors/package-support-levels", "/docs/contributors/ecosystem-atlas"],
+    min_words: 350,
+    max_words: 900,
+    minimum_code_blocks: 0,
+    diagram_policy: "none",
+    section_density: "minimal",
+    max_paragraph_sentences: 2
+  }
+}
+---
+## Content Brief
+
+Contributor-facing roadmap for the public Jido ecosystem.
+
+### Validation Criteria
+
+- Preserves milestone names and leads from source planning
+- Keeps the page directional rather than backlog-like
+- Explains how roadmap relates to the atlas and support levels

priv/ecosystem/ash_jido.md

@@ -12,6 +12,7 @@
   github_url: "https://github.com/agentjido/ash_jido",
   github_org: "agentjido",
   github_repo: "ash_jido",
+  tech_lead: "@mikehostetler",
   maturity: :stable,
   support_level: :stable,
   hex_status: "unreleased",

priv/ecosystem/jido.md

@@ -15,6 +15,7 @@
   github_url: "https://github.com/agentjido/jido",
   github_org: "agentjido",
   github_repo: "jido",
+  tech_lead: "@mikehostetler",
   elixir: "~> 1.17",
   maturity: :stable,
   support_level: :stable,