rtl-buddy-graph-extract
Clean-room, stdlib-only extractor feeding the binding tier of
rtl-buddy's design knowledge graph (epic rtl_buddy#375): deterministic
extraction over verif Python and spec markdown into NetworkX node-link
JSON, plus a merge-graphs union used by rb graph build as a
cross-check.
It implements the CLI contract rtl_buddy/graph/extract.py consumes.
The contract is owned by rtl-buddy and evolves to serve it — it
descends historically from shapes once assumed of the upstream
Graphify project (the idea
source, credit where due), but rtl-buddy is fully decoupled from that
tool and claims no compatibility with it. See
docs/extract-contract.md for the full
contract.
Usage
rb-graph-extract extract --format node-link --output binding/graph.json \
verif/**/*.py spec/**/*.md
rb-graph-extract merge-graphs --format node-link --output merged.json \
design/graph.json config/graph.json binding/graph.json
Normally you never run it by hand — rb graph build invokes it when
installed and degrades gracefully when not.
- Only
--format node-linkis supported. - Deterministic only: there is no semantic/LLM pass and no flag to request one.
- No dependencies outside the Python standard library.
Installing (git pin until the first PyPI release)
There is no PyPI release yet. Consume it via a uv git source:
# pyproject.toml of the consuming project
[project.optional-dependencies]
graph-extract = ["rtl-buddy-graph-extract"]
[tool.uv.sources]
rtl-buddy-graph-extract = { git = "https://github.com/rtl-buddy/rtl-buddy-graph-extract" }
or as a standalone tool:
uv tool install git+https://github.com/rtl-buddy/rtl-buddy-graph-extract
Once a PyPI release exists the [tool.uv.sources] pin is dropped and
the dependency resolves normally.
Development
uv run --group test pytest
uv run --group lint ruff check .
uv run --group lint ruff format --check .
Versioning is tag-driven via hatch-vcs, matching rtl_buddy and rtl-buddy-view; the label-driven release workflow will be added when PyPI publishing is set up.
Metadata
Release files for rtl-buddy-graph-extract 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| rtl_buddy_graph_extract-0.1.0.tar.gz | 21.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rtl_buddy_graph_extract-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 33.8 kB
Release files / rtl_buddy_graph_extract-0.1.0.tar.gz
| Download URL | rtl_buddy_graph_extract-0.1.0.tar.gz |
|---|---|
| Size | 21.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cc3397e2064a3b809dfee55a4b746d0ce6bb306f49bd1d0c3d8f6e287930b300
|
|
BLAKE2b-256 checksum How to use checksums |
060bcd5539a847c0a549fd4bfb1c127da24ea9b23f493f343a3c7180b1ad6706
|
| 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 Aug 16, 2026.
Transparency logRelease files / rtl_buddy_graph_extract-0.1.0-py3-none-any.whl
| Download URL | rtl_buddy_graph_extract-0.1.0-py3-none-any.whl |
|---|---|
| Size | 12.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d53db953973d5202da4b62d280e51e3abbe2d9e7f335906a2fca86cac1a24eae
|
|
BLAKE2b-256 checksum How to use checksums |
ae361af1fd202203e11526e4c8a697b3e7d5fb4b577ed48cf39c3d8026789d3d
|
| 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 Aug 16, 2026.
Transparency log