monogate-graph
monogate-graph is an evidence/dependency graph toolkit for Monogate-style
artifact workflows.
monogate-graph reads small JSON graph files and emits dependency order, cycle
warnings, blocked-node summaries, critical-path estimates, action queues, and
DOT exports.
The Python import module is eml_graph.
It does not certify evidence, prove release readiness, or make public claims.
CLI
monogate-graph validate examples/simple_release_gate.json
monogate-graph summary examples/simple_release_gate.json
monogate-graph topo examples/simple_release_gate.json
monogate-graph blocked examples/simple_release_gate.json
monogate-graph action-queue examples/simple_release_gate.json
monogate-graph export-dot examples/simple_release_gate.json
monogate-graph export-dot examples/kernel_observatory_export.json --out /tmp/observatory.dot
# Compatibility alias:
eml-graph validate examples/simple_release_gate.json
Kernel Observatory Integration
Kernel Observatory can export its cards into the eml-graph JSON shape:
python tools/kernel_observatory/observatory.py --build
python tools/kernel_observatory/observatory.py \
--export-eml-graph /tmp/monogate_kernel_observatory_v0/observatory_graph.json
PYTHONPATH=src python -m eml_graph.cli validate \
/tmp/monogate_kernel_observatory_v0/observatory_graph.json
PYTHONPATH=src python -m eml_graph.cli action-queue \
/tmp/monogate_kernel_observatory_v0/observatory_graph.json
The example examples/kernel_observatory_export.json is a small fixture for the
same export shape. It is intentionally much smaller than the live Observatory
graph.
Graph Shape
{
"graph_id": "example",
"nodes": [
{
"id": "tests",
"label": "Tests",
"status": "pass",
"weight": 1,
"evidence_paths": ["tests/result.json"],
"risk_flags": []
}
],
"edges": [
{"source": "tests", "target": "release", "type": "depends_on"}
]
}
Edge direction means target depends on source, so topological order lists
prerequisites first.
Boundaries
- graph output is planning/evidence structure, not certification.
Metadata
Release files for monogate-graph 0.1.1
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 | Actions |
|---|---|---|---|---|
| monogate_graph-0.1.1.tar.gz | 9.7 kB | Without provenance | Details for monogate_graph-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| monogate_graph-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for monogate_graph-0.1.1-py3-none-any.whl |
Total release size: 18.9 kB
Release files / monogate_graph-0.1.1.tar.gz
| Download URL | monogate_graph-0.1.1.tar.gz |
|---|---|
| Size | 9.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
70b7d4984ce04e1a2db43baf0bdd58e95d5a8e05847d090274bdbbaf01886899
|
|
BLAKE2b-256 checksum How to use checksums |
ad4a91488d0d3580278655ae50e4e195337c1a9b09c054f2d85a9d5dabd35619
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Release files / monogate_graph-0.1.1-py3-none-any.whl
| Download URL | monogate_graph-0.1.1-py3-none-any.whl |
|---|---|
| Size | 9.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
289b29c6bad805e5057b94f9606fe4c6e5e82ce1bc788e53a9b54f6f8b51c9ea
|
|
BLAKE2b-256 checksum How to use checksums |
c054d03f0d173b252b526736887f6a8580f66f37843ad4480e1b6b9920f444aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Security for monogate-graph 0.1.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.