This release is a pre-release and may not be stable for production use.
Agent Blackbox
Alpha recorder for agent workflows. Wrap a function, store signed event records with evidence digests and declared links, then inspect an incident or verify local record integrity.
Core Features
| Feature | Description |
|---|---|
| Trace decorator | Wrap agent functions and record runtime events |
| JEP-style event | Emits JEP Core 0.7-style J/D/T/V event objects with stable Event Identity |
| Declared links | Records parent relationships for incident review |
| Evidence digests | Records input/output/error digests |
| Local blackbox log | Stores JSONL event records for later review |
| Incident review | Reconstructs declared chain fragments around an incident |
| Integrity check | Verifies event hashes and Ed25519 signatures generated by this library |
Installation
Install the published distribution:
pip install --pre agent-blackbox-jep
The distribution is agent-blackbox-jep, the Python import is agent_blackbox,
and the CLI commands are agent-blackbox and blame-finder.
For local development:
pip install -e .
Basic Usage
from agent_blackbox import AgentBlackbox
blackbox = AgentBlackbox(storage="./blackbox_logs")
@blackbox.trace(agent_name="CoderAgent")
def write_code(requirement: str) -> str:
return "print('hello world')"
result = write_code("write a hello world")
# Review the latest event
event_hash = list(blackbox.events.keys())[-1]
report = blackbox.review_incident(event_hash)
print(report["candidate_failure_node"])
print(report["chain"])
Incident Review Output
Example:
{
"incident": "sha256:...",
"candidate_failure_node": "CoderAgent",
"diagnostic_summary": "The selected event has status failed. Review declared parents and evidence references.",
"review_score": 0.72,
"chain": [
{
"event_hash": "sha256:...",
"agent": "PlannerAgent",
"status": "success"
},
{
"event_hash": "sha256:...",
"agent": "CoderAgent",
"status": "failed"
}
],
"boundary": {
"not_legal_liability": true,
"not_factual_causality_proof": true,
"not_compliance_determination": true
}
}
CLI
Review an incident:
agent-blackbox review sha256:...
Show a chain tree:
agent-blackbox tree sha256:...
Verify an event:
agent-blackbox verify sha256:...
Boundary Statement
New events use Core 0.7
with Event Identity (who,id). Event Hash identifies the exact signed artifact
and is the lookup key in the local store. The trace decorator records judgments;
D/T/V events require explicit creation with their required fields.
Verification checks event integrity under the recorder's local key and the recorded links. It does not establish factual causality, legal responsibility or log completeness. See the current alpha releases for the packaged implementation.
License
MIT
Runtime and verification notes
See HARDENING.md for event extensions, key handling and import compatibility.
Metadata
Release files for agent-blackbox-jep 0.3.0a4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| agent_blackbox_jep-0.3.0a4.tar.gz | 13.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agent_blackbox_jep-0.3.0a4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.4 kB
Release files / agent_blackbox_jep-0.3.0a4.tar.gz
| Download URL | agent_blackbox_jep-0.3.0a4.tar.gz |
|---|---|
| Size | 13.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
361e1417433274acce17f48e36e4bde91e1158e5d011f437f3ba376b5d5f8f96
|
|
BLAKE2b-256 checksum How to use checksums |
e3dc5667ae6fd5cecb005ad61a055a898eea4b9ebc61792cbb265205bb700905
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / agent_blackbox_jep-0.3.0a4-py3-none-any.whl
| Download URL | agent_blackbox_jep-0.3.0a4-py3-none-any.whl |
|---|---|
| Size | 12.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
78c3fe75f458113218838d637767812bb8bae511a0e0ec8ed28a48ba3a1f723d
|
|
BLAKE2b-256 checksum How to use checksums |
fba262f3f2913542f5ae365661da70c556d93a34e23d684833e65cf9089aa9ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logSecurity for agent-blackbox-jep 0.3.0a4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for agent_blackbox_jep-0.3.0a4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.