Skip to content

docs: org-wide contributor substrate update #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hummbl-dev merged 1 commit into from
Jul 5, 2026
Merged

docs: org-wide contributor substrate update #22

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
55 changes: 54 additions & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Contributing to HUMMBL

Thank you for your interest in contributing to HUMMBL projects.
Thank you for your interest in contributing to HUMMBL projects. This is the org-wide contributing guide for all repos in `hummbl-dev` that don't ship their own `CONTRIBUTING.md`.

## Guidelines

Expand All @@ -17,6 +17,59 @@ Thank you for your interest in contributing to HUMMBL projects.
4. Run the test suite (`python -m pytest tests/ -v`)
5. Open a pull request against `main`

## Choosing where to contribute

| Contributor Type | Best Entry |
|---|---|
| Agent engineer | agent-runtime-governance, agent-handoffs, agent-control-plane-patterns |
| Governance/policy | governance-as-code, policy-as-code, compliance-as-code |
| Package/release | packages, homebrew-tap, scoop-bucket, winget-manifests, nix |
| Evidence/research | claim-evidence-ledger, research-source-packets, ai-source-verification |
| Tool builder | hummbl-governance, base120, arbiter, mcp-server |

New to the org? Start at [hummbl-dev/hummbl-dev START_HERE.md](https://github.com/hummbl-dev/hummbl-dev/blob/main/START_HERE.md).

## 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.
- **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.

Promotion from v0.1-packet to canonical requires an audit, an operator-authority decision, and a receipt.

## What agents can and cannot do

**Agents CAN:**
- Work on docs, schema, and fixture contributions in v0.1-packet repos.
- Create PRs with receipts for governance-bearing changes.
- Close issues that have the required evidence attached.

**Agents CANNOT:**
- Make canonical decisions.
- Promote repos to canonical.
- Close operator-authority issues.
- Approve Phase 1 deployments.

If an issue carries the `operator-authority` or `decision-required` label, stop and hand off to a human.

## Operator authority required

The following decisions are pending operator authority. Agents must not auto-complete them:

- **homebrew-hummbl#3** — pending operator decision
- **mintlify-docs#3** — pending operator decision

## Receipts

Every PR that touches governance-bearing content must include a receipt. A receipt records what changed, why, what was verified, and the authority under which the change was made. PRs without a receipt on governance-bearing changes will be blocked until one is added. Use the `receipt:missing` / `receipt:complete` labels to track this.

## Labels

Label meanings are defined in [docs/FLEET_LABELS.md](docs/FLEET_LABELS.md). Use labels to route work, signal agent safety, and mark authority requirements. Key labels for contributors: `agent-safe`, `agent-hold`, `operator-authority`, `decision-required`, `evidence-needed`, `v0.1-packet`, `canonical-candidate`.

## Questions

Contact: reuben@hummbl.io
21 changes: 21 additions & 0 deletions docs/FLEET_LABELS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,27 @@ These labels are organization-level conventions for HUMMBL repositories. Individ
| `receipt:missing` | Work cannot close or merge until an expected receipt is added. |
| `receipt:complete` | Required audit receipt is present. |
| `risk:high` | Extra reviewer caution or owner involvement is required. |
| `v0.1-packet` | Repo has v0.1 boundary, prior art, schema, fixtures, and receipt. |
| `canonical-candidate` | Proposed for HUMMBL canon, under audit. |
| `operator-authority` | Issue requires operator decision, agents must not auto-complete. |
| `agent-safe` | Issue is safe for autonomous agent execution. |
| `agent-hold` | Issue is blocked for agent execution. |
| `decision-required` | Issue requires human decision before proceeding. |
| `evidence-needed` | Issue needs evidence/receipts before closure. |
| `implementation-bearing` | Repo ships runnable code. |
| `pattern-reference` | Repo is docs/schema/fixture only, no runtime code. |
| `external-collab-ready` | Repo is ready for outside contributor participation. |

## 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.
Comment on lines +44 to +53

@coderabbitai coderabbitai Bot Jul 5, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 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


## Usage policy

Expand Down
44 changes: 40 additions & 4 deletions profile/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,29 +2,62 @@

**HUMMBL is an open-source governance framework for multi-agent AI systems.** It provides delegation tokens, circuit breakers, kill switches, and append-only audit logging as Python-stdlib-only primitives -- no third-party runtime dependencies. Built for teams running production AI agent fleets who need deterministic safety controls, not probabilistic guardrails.

`1970 collected tests` | `120 mental models` | `0 runtime deps` | `Python 3.11-3.14` | `pip install hummbl-governance` | `Production since 2024`
`2027 collected tests` | `120 mental models` | `0 runtime deps` | `Python 3.11-3.14` | `pip install hummbl-governance` | `Production since 2024`

---

## Where to start

New to the org? Read **[START_HERE.md](https://github.com/hummbl-dev/hummbl-dev/blob/main/START_HERE.md)** in `hummbl-dev/hummbl-dev` for the fleet index, contributor entry points, and current operator-authority decisions.

If you are contributing for the first time, read the org-wide **[CONTRIBUTING.md](https://github.com/hummbl-dev/.github/blob/main/CONTRIBUTING.md)** for the contributor type table, agent permissions, and receipt requirements.

---

## Projects

### Canonical / active

| Project | What problem it solves | |
|---------|----------------------|---|
| **[hummbl-governance](https://github.com/hummbl-dev/hummbl-governance)** | Enforces agent permissions, cost budgets, and kill-switch authority in Python with 1970 collected tests and zero runtime dependencies. `pip install hummbl-governance` | [![PyPI](https://img.shields.io/pypi/v/hummbl-governance)](https://pypi.org/project/hummbl-governance/) [![Python](https://img.shields.io/pypi/pyversions/hummbl-governance)](https://pypi.org/project/hummbl-governance/) [![License](https://img.shields.io/github/license/hummbl-dev/hummbl-governance)](https://github.com/hummbl-dev/hummbl-governance/blob/main/LICENSE) |
| **[hummbl-governance](https://github.com/hummbl-dev/hummbl-governance)** | Enforces agent permissions, cost budgets, and kill-switch authority in Python with 2027 collected tests and zero runtime dependencies. `pip install hummbl-governance` | [![PyPI](https://img.shields.io/pypi/v/hummbl-governance)](https://pypi.org/project/hummbl-governance/) [![Python](https://img.shields.io/pypi/pyversions/hummbl-governance)](https://pypi.org/project/hummbl-governance/) [![License](https://img.shields.io/github/license/hummbl-dev/hummbl-governance)](https://github.com/hummbl-dev/hummbl-governance/blob/main/LICENSE) |
| **[base120](https://github.com/hummbl-dev/base120)** | Gives AI agents 120 validated mental models for structured reasoning with operator algebra and contract validation CLI. | [![License](https://img.shields.io/github/license/hummbl-dev/base120)](https://github.com/hummbl-dev/base120/blob/main/LICENSE) |
| **[mcp-server](https://github.com/hummbl-dev/mcp-server)** | Exposes Base120 frameworks to Claude, ChatGPT, and other LLMs via Model Context Protocol. | [![License](https://img.shields.io/github/license/hummbl-dev/mcp-server)](https://github.com/hummbl-dev/mcp-server/blob/main/LICENSE) |
| **[hummbl-agent](https://github.com/hummbl-dev/hummbl-agent)** | Provides registry-first deterministic agent lifecycle management. | [![License](https://img.shields.io/github/license/hummbl-dev/hummbl-agent)](https://github.com/hummbl-dev/hummbl-agent/blob/main/LICENSE) |
| **[arbiter](https://github.com/hummbl-dev/arbiter)** | Agent-aware code quality scoring — cyclomatic complexity, dependency analysis, test coverage, governance compliance. Grades repos A through F with evidence-backed findings. | [![License](https://img.shields.io/github/license/hummbl-dev/arbiter)](https://github.com/hummbl-dev/arbiter/blob/main/LICENSE) |
| **[hummbl-skills](https://github.com/hummbl-dev/hummbl-skills)** | HUMMBL Agent Skills — canonical skill definitions, CI-validated SKILL.md files, skill creation templates, and cross-agent skill export tooling. | [![License](https://img.shields.io/github/license/hummbl-dev/hummbl-skills)](https://github.com/hummbl-dev/hummbl-skills/blob/main/LICENSE) |
| **hummbl-transparency** *(private repository)* | HUMMBL AI Transparency Registry — structured, versioned, evidence-backed vendor prompt auditing, model behavior documentation, and system prompt change tracking. | Private |
| **[governed-compression](https://github.com/hummbl-dev/governed-compression)** | Governed vector and KV-cache compression research — CPU reference, reproducible benchmarks, tuple-based experiment logging. | [![License](https://img.shields.io/github/license/hummbl-dev/governed-compression)](https://github.com/hummbl-dev/governed-compression/blob/main/LICENSE) |
| **[evidence-gate](https://github.com/hummbl-dev/evidence-gate)** | Pre-publish source-verification rule library for HUMMBL governance content. Stdlib-only TOML rules + fixture harness. | [![License](https://img.shields.io/github/license/hummbl-dev/evidence-gate)](https://github.com/hummbl-dev/evidence-gate/blob/main/LICENSE) |
| **[hummbl-bibliography](https://github.com/hummbl-dev/hummbl-bibliography)** | HUMMBL Bibliography — provenance corpus, BibTeX citations, and position papers for Base120, HCC, BKI, and AI governance research. | [![License](https://img.shields.io/github/license/hummbl-dev/hummbl-bibliography)](https://github.com/hummbl-dev/hummbl-bibliography/blob/main/LICENSE) |

### 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.

---

Comment on lines +33 to +60

@coderabbitai coderabbitai Bot Jul 5, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 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.

## FAQ

**Q: What is HUMMBL?**
Expand All @@ -36,8 +69,11 @@ A: Run `pip install hummbl-governance`. Requires Python 3.11 or newer. No additi
**Q: What is Base120?**
A: Base120 is a library of 120 validated mental models organized into 6 domains (Perspective, Inversion, Composition, Decomposition, Recursion, Systems). It includes an operator algebra for composing models and a contract validation CLI. AI agents use Base120 for structured reasoning via the HUMMBL MCP server.

**Q: What is a v0.1-packet repo?**
A: A v0.1-packet repo has a defined v0.1 boundary, prior art references, a schema, fixtures, and a receipt. It is the maturity level between seed and canonical. v0.1-packet repos are open for docs, schema, and fixture contributions, and for agent-safe work, but are not yet HUMMBL canon. Promotion to canonical requires an audit and an operator-authority decision.

**Q: How is HUMMBL different from LangChain or CrewAI?**
A: LangChain and CrewAI are agent orchestration frameworks. HUMMBL is a governance layer that sits alongside any orchestrator. It answers "what is this agent allowed to do?" not "how do I chain agents together." HUMMBL has zero runtime dependencies, uses deterministic controls (not probabilistic), and is tested with 1970 collected tests across the published libraries, covering unit tests for individual components, integration tests for multi-component orchestration, and property-based tests that verify determinism and canonical-form invariants.
A: LangChain and CrewAI are agent orchestration frameworks. HUMMBL is a governance layer that sits alongside any orchestrator. It answers "what is this agent allowed to do?" not "how do I chain agents together." HUMMBL has zero runtime dependencies, uses deterministic controls (not probabilistic), and is tested with 2027 collected tests across the published libraries, covering unit tests for individual components, integration tests for multi-component orchestration, and property-based tests that verify determinism and canonical-form invariants.

---

Expand Down
Loading