docs: org-wide contributor substrate update - #22
Merged
Conversation
📝 WalkthroughSummary by CodeRabbit
WalkthroughDocumentation-only changes across CONTRIBUTING.md, docs/FLEET_LABELS.md, and profile/README.md introducing a repo maturity model (seed → v0.1-packet → active → canonical), new maturity-related labels, agent permission and operator-authority rules, receipt requirements for governance PRs, and updated README metrics and FAQ content. ChangesRepo maturity and governance documentation
Estimated code review effort: 2 (Simple) | ~10 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/FLEET_LABELS.md`:
- Around line 44-53: The “Maturity labels” section in FLEET_LABELS.md mixes two
different concepts: repo maturity labels and issue-routing labels. Split the
list so `v0.1-packet` and `canonical-candidate` stay under a repo-maturity
section, while `agent-safe`, `agent-hold`, `operator-authority`, and
`decision-required` move to a separate routing/issue-state section; keep the
wording aligned with the actual organization labels and use the existing label
names as-is.
In `@profile/README.md`:
- Around line 33-60: Update the Repo maturity section in README to restore the
missing active tier so it matches the org guide. Adjust the maturity list and
any surrounding text that currently says HUMMBL repos move through three levels,
and make sure the progression includes seed, v0.1-packet, active, and canonical.
Keep the descriptions aligned with the repo labels and references already
mentioned in this section.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 61fddd25-7459-44f9-8bda-d51a70b76a90
📒 Files selected for processing (3)
CONTRIBUTING.mddocs/FLEET_LABELS.mdprofile/README.md
Comment on lines
+44
to
+53
| ## Maturity labels | ||
|
|
||
| These labels track where a repo sits in the HUMMBL maturity pipeline: | ||
|
|
||
| - **`v0.1-packet`** — Repo has a v0.1 boundary, prior art, schema, fixtures, and a receipt. Open for docs/schema/fixture contributions and agent-safe work. Not yet canonical. | ||
| - **`canonical-candidate`** — Repo has been proposed for HUMMBL canon and is under audit. Promotion requires an operator-authority decision and a receipt. | ||
| - **`agent-safe`** — Issue is safe for autonomous agent execution. Agents may pick it up, complete it, and open PRs without human pre-approval. | ||
| - **`agent-hold`** — Issue is blocked for agent execution. Agents must not start work until the hold is cleared. | ||
| - **`operator-authority`** — Issue requires an operator decision. Agents must not auto-complete, close, or merge these issues. | ||
| - **`decision-required`** — Issue requires a human decision before any further work proceeds. Distinct from `operator-authority` in that it may not carry governance authority, but still needs a human call. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Separate repo-maturity labels from routing labels.
v0.1-packet / canonical-candidate describe repo maturity, but agent-safe, agent-hold, operator-authority, and decision-required describe issue execution state. Keeping them under one "Maturity labels" section makes the taxonomy ambiguous.
Suggested split
-## Maturity labels
-
-These labels track where a repo sits in the HUMMBL maturity pipeline:
-
-- **`v0.1-packet`** — Repo has a v0.1 boundary, prior art, schema, fixtures, and a receipt. Open for docs/schema/fixture contributions and agent-safe work. Not yet canonical.
-- **`canonical-candidate`** — Repo has been proposed for HUMMBL canon and is under audit. Promotion requires an operator-authority decision and a receipt.
-- **`agent-safe`** — Issue is safe for autonomous agent execution. Agents may pick it up, complete it, and open PRs without human pre-approval.
-- **`agent-hold`** — Issue is blocked for agent execution. Agents must not start work until the hold is cleared.
-- **`operator-authority`** — Issue requires an operator decision. Agents must not auto-complete, close, or merge these issues.
-- **`decision-required`** — Issue requires a human decision before any further work proceeds. Distinct from `operator-authority` in that it may not carry governance authority, but still needs a human call.
+## Repo maturity labels
+
+- **`v0.1-packet`** — Repo has a v0.1 boundary, prior art, schema, fixtures, and a receipt. Open for docs/schema/fixture contributions and agent-safe work. Not yet canonical.
+- **`canonical-candidate`** — Repo has been proposed for HUMMBL canon and is under audit. Promotion requires an operator-authority decision and a receipt.
+
+## Routing and authority labels
+
+- **`agent-safe`** — Issue is safe for autonomous agent execution. Agents may pick it up, complete it, and open PRs without human pre-approval.
+- **`agent-hold`** — Issue is blocked for agent execution. Agents must not start work until the hold is cleared.
+- **`operator-authority`** — Issue requires an operator decision. Agents must not auto-complete, close, or merge these issues.
+- **`decision-required`** — Issue requires a human decision before any further work proceeds. Distinct from `operator-authority` in that it may not carry governance authority, but still needs a human call.As per coding guidelines, docs/FLEET_LABELS.md should accurately match the actual organization labels.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ## Maturity labels | |
| These labels track where a repo sits in the HUMMBL maturity pipeline: | |
| - **`v0.1-packet`** — Repo has a v0.1 boundary, prior art, schema, fixtures, and a receipt. Open for docs/schema/fixture contributions and agent-safe work. Not yet canonical. | |
| - **`canonical-candidate`** — Repo has been proposed for HUMMBL canon and is under audit. Promotion requires an operator-authority decision and a receipt. | |
| - **`agent-safe`** — Issue is safe for autonomous agent execution. Agents may pick it up, complete it, and open PRs without human pre-approval. | |
| - **`agent-hold`** — Issue is blocked for agent execution. Agents must not start work until the hold is cleared. | |
| - **`operator-authority`** — Issue requires an operator decision. Agents must not auto-complete, close, or merge these issues. | |
| - **`decision-required`** — Issue requires a human decision before any further work proceeds. Distinct from `operator-authority` in that it may not carry governance authority, but still needs a human call. | |
| ## Repo maturity labels | |
| - **`v0.1-packet`** — Repo has a v0.1 boundary, prior art, schema, fixtures, and a receipt. Open for docs/schema/fixture contributions and agent-safe work. Not yet canonical. | |
| - **`canonical-candidate`** — Repo has been proposed for HUMMBL canon and is under audit. Promotion requires an operator-authority decision and a receipt. | |
| ## Routing and authority labels | |
| - **`agent-safe`** — Issue is safe for autonomous agent execution. Agents may pick it up, complete it, and open PRs without human pre-approval. | |
| - **`agent-hold`** — Issue is blocked for agent execution. Agents must not start work until the hold is cleared. | |
| - **`operator-authority`** — Issue requires an operator decision. Agents must not auto-complete, close, or merge these issues. | |
| - **`decision-required`** — Issue requires a human decision before any further work proceeds. Distinct from `operator-authority` in that it may not carry governance authority, but still needs a human call. |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/FLEET_LABELS.md` around lines 44 - 53, The “Maturity labels” section in
FLEET_LABELS.md mixes two different concepts: repo maturity labels and
issue-routing labels. Split the list so `v0.1-packet` and `canonical-candidate`
stay under a repo-maturity section, while `agent-safe`, `agent-hold`,
`operator-authority`, and `decision-required` move to a separate
routing/issue-state section; keep the wording aligned with the actual
organization labels and use the existing label names as-is.
Source: Coding guidelines
Comment on lines
+33
to
+60
| ### v0.1-packet fleet | ||
|
|
||
| These repos have a v0.1 boundary, prior art, schema, fixtures, and a receipt. They are open for docs/schema/fixture contributions and agent-safe work. | ||
|
|
||
| | Category | Repos | | ||
| |----------|-------| | ||
| | Agent engineering | [agent-runtime-governance](https://github.com/hummbl-dev/agent-runtime-governance), [agent-handoffs](https://github.com/hummbl-dev/agent-handoffs), [agent-control-plane-patterns](https://github.com/hummbl-dev/agent-control-plane-patterns) | | ||
| | Governance / policy | [governance-as-code](https://github.com/hummbl-dev/governance-as-code), [policy-as-code](https://github.com/hummbl-dev/policy-as-code), [compliance-as-code](https://github.com/hummbl-dev/compliance-as-code) | | ||
| | Package / release | [packages](https://github.com/hummbl-dev/packages), [homebrew-tap](https://github.com/hummbl-dev/homebrew-tap), [scoop-bucket](https://github.com/hummbl-dev/scoop-bucket), [winget-manifests](https://github.com/hummbl-dev/winget-manifests), [nix](https://github.com/hummbl-dev/nix) | | ||
| | Evidence / research | [claim-evidence-ledger](https://github.com/hummbl-dev/claim-evidence-ledger), [research-source-packets](https://github.com/hummbl-dev/research-source-packets), [ai-source-verification](https://github.com/hummbl-dev/ai-source-verification) | | ||
| | Tool builder | [hummbl-governance](https://github.com/hummbl-dev/hummbl-governance), [base120](https://github.com/hummbl-dev/base120), [arbiter](https://github.com/hummbl-dev/arbiter), [mcp-server](https://github.com/hummbl-dev/mcp-server) | | ||
|
|
||
| Unlike LangChain and CrewAI (which focus on agent orchestration) or Microsoft's agent toolkits (which target Azure-hosted workflows), HUMMBL is a governance-only layer that works with any orchestrator and has zero vendor lock-in. | ||
|
|
||
| --- | ||
|
|
||
| ## Repo maturity | ||
|
|
||
| HUMMBL repos move through three maturity levels: | ||
|
|
||
| - **seed** — Early idea. No v0.1 boundary yet. Structure may change without notice. Not ready for outside contributors. | ||
| - **v0.1-packet** — Repo has a v0.1 boundary, prior art, schema, fixtures, and a receipt. Open for docs/schema/fixture contributions and agent-safe work. Not yet canonical. | ||
| - **canonical** — Audited, stable, and referenced as HUMMBL canon. Changes require operator authority and receipts. `hummbl-governance`, `base120`, and `mcp-server` are canonical. | ||
|
|
||
| A repo promoted from v0.1-packet to canonical requires an audit, an operator-authority decision, and a receipt. See `docs/FLEET_LABELS.md` for the `canonical-candidate` and `v0.1-packet` labels. | ||
|
|
||
| --- | ||
|
|
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Restore the active tier here.
This section says HUMMBL repos move through three maturity levels, but the org guide now defines seed, v0.1-packet, active, and canonical. That mismatch leaves contributors with conflicting maturity guidance.
Suggested fix
-HUMMBL repos move through three maturity levels:
+HUMMBL repos move through four maturity levels:
...
- **v0.1-packet** — Repo has a v0.1 boundary, prior art, schema, fixtures, and a receipt. Open for docs/schema/fixture contributions and agent-safe work. Not yet canonical.
+- **active** — Repo ships runnable code and is under continuous development. May or may not be canonical.
- **canonical** — Audited, stable, and referenced as HUMMBL canon. Changes require operator authority and receipts. `hummbl-governance`, `base120`, and `mcp-server` are canonical.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ### v0.1-packet fleet | |
| These repos have a v0.1 boundary, prior art, schema, fixtures, and a receipt. They are open for docs/schema/fixture contributions and agent-safe work. | |
| | Category | Repos | | |
| |----------|-------| | |
| | Agent engineering | [agent-runtime-governance](https://github.com/hummbl-dev/agent-runtime-governance), [agent-handoffs](https://github.com/hummbl-dev/agent-handoffs), [agent-control-plane-patterns](https://github.com/hummbl-dev/agent-control-plane-patterns) | | |
| | Governance / policy | [governance-as-code](https://github.com/hummbl-dev/governance-as-code), [policy-as-code](https://github.com/hummbl-dev/policy-as-code), [compliance-as-code](https://github.com/hummbl-dev/compliance-as-code) | | |
| | Package / release | [packages](https://github.com/hummbl-dev/packages), [homebrew-tap](https://github.com/hummbl-dev/homebrew-tap), [scoop-bucket](https://github.com/hummbl-dev/scoop-bucket), [winget-manifests](https://github.com/hummbl-dev/winget-manifests), [nix](https://github.com/hummbl-dev/nix) | | |
| | Evidence / research | [claim-evidence-ledger](https://github.com/hummbl-dev/claim-evidence-ledger), [research-source-packets](https://github.com/hummbl-dev/research-source-packets), [ai-source-verification](https://github.com/hummbl-dev/ai-source-verification) | | |
| | Tool builder | [hummbl-governance](https://github.com/hummbl-dev/hummbl-governance), [base120](https://github.com/hummbl-dev/base120), [arbiter](https://github.com/hummbl-dev/arbiter), [mcp-server](https://github.com/hummbl-dev/mcp-server) | | |
| Unlike LangChain and CrewAI (which focus on agent orchestration) or Microsoft's agent toolkits (which target Azure-hosted workflows), HUMMBL is a governance-only layer that works with any orchestrator and has zero vendor lock-in. | |
| --- | |
| ## Repo maturity | |
| HUMMBL repos move through three maturity levels: | |
| - **seed** — Early idea. No v0.1 boundary yet. Structure may change without notice. Not ready for outside contributors. | |
| - **v0.1-packet** — Repo has a v0.1 boundary, prior art, schema, fixtures, and a receipt. Open for docs/schema/fixture contributions and agent-safe work. Not yet canonical. | |
| - **canonical** — Audited, stable, and referenced as HUMMBL canon. Changes require operator authority and receipts. `hummbl-governance`, `base120`, and `mcp-server` are canonical. | |
| A repo promoted from v0.1-packet to canonical requires an audit, an operator-authority decision, and a receipt. See `docs/FLEET_LABELS.md` for the `canonical-candidate` and `v0.1-packet` labels. | |
| --- | |
| ### v0.1-packet fleet | |
| These repos have a v0.1 boundary, prior art, schema, fixtures, and a receipt. They are open for docs/schema/fixture contributions and agent-safe work. | |
| | Category | Repos | | |
| |----------|-------| | |
| | Agent engineering | [agent-runtime-governance](https://github.com/hummbl-dev/agent-runtime-governance), [agent-handoffs](https://github.com/hummbl-dev/agent-handoffs), [agent-control-plane-patterns](https://github.com/hummbl-dev/agent-control-plane-patterns) | | |
| | Governance / policy | [governance-as-code](https://github.com/hummbl-dev/governance-as-code), [policy-as-code](https://github.com/hummbl-dev/policy-as-code), [compliance-as-code](https://github.com/hummbl-dev/compliance-as-code) | | |
| | Package / release | [packages](https://github.com/hummbl-dev/packages), [homebrew-tap](https://github.com/hummbl-dev/homebrew-tap), [scoop-bucket](https://github.com/hummbl-dev/scoop-bucket), [winget-manifests](https://github.com/hummbl-dev/winget-manifests), [nix](https://github.com/hummbl-dev/nix) | | |
| | Evidence / research | [claim-evidence-ledger](https://github.com/hummbl-dev/claim-evidence-ledger), [research-source-packets](https://github.com/hummbl-dev/research-source-packets), [ai-source-verification](https://github.com/hummbl-dev/ai-source-verification) | | |
| | Tool builder | [hummbl-governance](https://github.com/hummbl-dev/hummbl-governance), [base120](https://github.com/hummbl-dev/base120), [arbiter](https://github.com/hummbl-dev/arbiter), [mcp-server](https://github.com/hummbl-dev/mcp-server) | | |
| Unlike LangChain and CrewAI (which focus on agent orchestration) or Microsoft's agent toolkits (which target Azure-hosted workflows), HUMMBL is a governance-only layer that works with any orchestrator and has zero vendor lock-in. | |
| --- | |
| ## Repo maturity | |
| HUMMBL repos move through four maturity levels: | |
| - **seed** — Early idea. No v0.1 boundary yet. Structure may change without notice. Not ready for outside contributors. | |
| - **v0.1-packet** — Repo has a v0.1 boundary, prior art, schema, fixtures, and a receipt. Open for docs/schema/fixture contributions and agent-safe work. Not yet canonical. | |
| - **active** — Repo ships runnable code and is under continuous development. May or may not be canonical. | |
| - **canonical** — Audited, stable, and referenced as HUMMBL canon. Changes require operator authority and receipts. `hummbl-governance`, `base120`, and `mcp-server` are canonical. | |
| A repo promoted from v0.1-packet to canonical requires an audit, an operator-authority decision, and a receipt. See `docs/FLEET_LABELS.md` for the `canonical-candidate` and `v0.1-packet` labels. | |
| --- |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@profile/README.md` around lines 33 - 60, Update the Repo maturity section in
README to restore the missing active tier so it matches the org guide. Adjust
the maturity list and any surrounding text that currently says HUMMBL repos move
through three levels, and make sure the progression includes seed, v0.1-packet,
active, and canonical. Keep the descriptions aligned with the repo labels and
references already mentioned in this section.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Org-wide contributor substrate update across three files in
.github:evidence-gatefrom the Projects table (kepthummbl-skills, which is not archived). Split Projects into "Canonical / active" and "v0.1-packet fleet" sections with the five fleet categories (agent engineering, governance/policy, package/release, evidence/research, tool builder). Added "Where to start" section linking tohummbl-dev/hummbl-devSTART_HERE.md. Added "Repo maturity" section explaining seed/v0.1-packet/canonical levels. Added "Q: What is a v0.1-packet repo?" to the FAQ. Updated test count from 1970 to 2027 (verified againsthummbl-governancecurrent collection).docs/FLEET_LABELS.md.v0.1-packet,canonical-candidate,operator-authority,agent-safe,agent-hold,decision-required,evidence-needed,implementation-bearing,pattern-reference,external-collab-ready) to the existing table. Added a "Maturity labels" section explaining v0.1-packet, canonical-candidate, agent-safe, agent-hold, operator-authority, and decision-required.Test plan
profile/README.mdin GitHub rendering — verify Projects tables, "Where to start", "Repo maturity", and FAQ render correctly.evidence-gateis removed andhummbl-skillsis retained (confirmed not archived viagh repo view).2027 collected testsmatcheshummbl-governance(confirmed viapytest --collect-only).CONTRIBUTING.md— verify contributor type table, agent permissions, operator-authority list, and receipts section render.docs/FLEET_LABELS.md— verify new labels appended without replacing existing rows, and "Maturity labels" section appears after the table.hummbl-dev/hummbl-dev.