State it precisely
The public ledger records the text, disposition, evidence level, scope, and risk of each homepage claim.
Inspect 14 claims ↗Public evidence dossier · v1.4.2 snapshot
Proof should survive the pitch.
Every material claim on this page resolves to public source, an observed run, or a machine-readable receipt. The limits travel with the evidence.
The measured snapshot
One version. One scope. Five facts.
These figures describe the cited public package source and CI run. They are historical evidence, not rolling counters or a promise of fitness for every environment.
- implemented primitives
- 34
- tests passed in the cited CI job
- 2,463
- third-party Core runtime dependencies
- 0
- Python version in public CI
- 3.13
- source license
- Apache 2.0
Scope: hummbl-governance v1.4.2, classified Alpha. Public CI run 32904924444 reported 2,463 passed and 3 skipped. The public workflow ran Python 3.13 and did not collect coverage.
The evidence chain
A claim is only the first link.
Useful proof connects the words a visitor sees to the artifact that supports them, the run that exercised it, and the boundary on what may be inferred.
Pin the artifact
Package claims resolve to the v1.4.2 tag, full Git commit, source path, and normalized file hash.
Open commit b1b0581 ↗Show the run
The public Actions job records the command, Python version, conclusion, passed tests, and skipped tests.
Inspect CI run 32904924444 ↗Carry the limits
The receipt states what the evidence establishes and what it does not: repository CI is not production suitability.
Read the package receipt ↗Two different records
Repository proof and a live observation.
The records answer different questions. Keeping them separate prevents a small public probe from becoming a broad production claim.
What did the public repository establish?
Source metadata, primitive inventory, file hashes, and one successful public CI job on Python 3.13.
Inspect the complete receipt ↗Did a published package emit one public receipt?
Yes. One GET on the named Worker produced receipt r-7e400da03299. Its scope is that surface and timestamp only.
Inspect the scoped observation ↗Reproduce the repository check
Take the evidence off this website.
The receipt is an index. The public repository and its pinned tag are the artifacts. Run the same collection command in your own Python 3.13 environment.
terminal · public source snapshot
git clone https://github.com/hummbl-io/oss.git
cd oss
git checkout hummbl-governance/v1.4.2
cd packages/hummbl-governance
python -m pip install -e ".[test]"
python -m pytest --collect-only -q testsThe evidence receipt records 2,466 tests collected locally. The pass claim comes from the separate public CI execution linked above.
Assurance boundary
What this proof does not say.
- Production suitability
- A successful repository test job does not establish safe or suitable operation in a particular production system.
- Broad production use
- The public probe records one scoped GET. It is not customer evidence or a general “production-tested” claim.
- Public non-repudiation
- HMAC authenticity is checkable by parties holding the shared secret. It is not public-key proof of an independent identity.
- Complete integration
- A primitive governs only actions routed through it. Identity, key protection, evidence capture, monitoring, and response remain system responsibilities.
From evidence to action
Build the first boundary.
Start with one agent action, define its authority, put the decision in the execution path, and preserve the result.