graphify-okf-bridge
One knowledge layer for code and data. A bridge between Graphify code knowledge graphs and Google's Open Knowledge Format (OKF) v0.1 — so AI agents can traverse one connected graph from application code to warehouse tables.
Status: Phase 5 in progress (core pipeline — export/import/link/validate — is done; skill packaging, demo, and release are underway). See IMPLEMENTATION_PLAN.md for the roadmap and docs/proposal.md for the full pitch.
Quickstart
uv tool install graphify-okf-bridge # (once published — see IMPLEMENTATION_PLAN.md Phase 5d)
# or, from a checkout:
uv sync && uv run okf-bridge --help
okf-bridge validate <bundle-dir> # OKF §9 conformance check + warnings
okf-bridge export <graph.json> -o <bundle-dir> # graphify graph -> OKF bundle
okf-bridge import <bundle-dir> -o <graph.json> # OKF bundle -> mergeable graphify graph
okf-bridge link <graph.json> <bundle-dir> -o out.json --repo-root . # infer code<->data edges
okf-bridge install-skill [--project] # install the /okf-bridge Claude Code skill
A typical flow: graphify . your codebase, okf-bridge import a data catalog bundle, okf-bridge link the two, graphify merge-graphs them together, then graphify path/explain/query (or an MCP client, see demo/mcp.md) traverse the combined graph. Full worked example with a real public dbt project + GA4 in demo/README.md.
The mapping convention between Graphify's typed/confidence-tagged edges and OKF's markdown links — including the linker's signal priority and ambiguity policy — lives in spec/MAPPING.md and is normative for this repo.
Relationship to upstream
This is an independent bridge, not a fork of either project. It depends on the public graphifyy PyPI package and reads/writes plain OKF bundles — no upstream code is vendored except the fixtures in tests/fixtures/okf_official/ (Apache-2.0, UPSTREAM_LICENSE.md included) and a reference copy of the spec in spec/OKF_SPEC.md. The links: frontmatter extension this bridge uses to carry typed/confidence-tagged edges through OKF (§Export E7 in spec/MAPPING.md) is a candidate for upstream proposal to GoogleCloudPlatform/knowledge-catalog, since OKF v0.1 links are otherwise untyped.
Development
uv sync # install dev environment
uv run pytest # fast suite (integration tests deselected), <10s
uv run pytest -m integration # requires: uv tool install graphifyy
uv run ruff check . && uv run mypy src/ # lint + types
Proceed phase by phase — every session starts with: "Read CLAUDE.md and IMPLEMENTATION_PLAN.md. We are on Phase N. Confirm the DoD, write the phase's failing tests, then implement."
Repository layout
src/graphify_okf_bridge/okf/— pure OKF model/reader/writer/validator (extractable as its own library later).src/graphify_okf_bridge/exporter.py/importer.py/linker.py— pure functions over the graphify ↔ OKF mapping;cli.pyis a thin wrapper.src/graphify_okf_bridge/skill/SKILL.md— the Claude Code skill, installed viaokf-bridge install-skill.tests/fixtures/tiny_graph.json— real graphify output captured overtests/fixtures/tiny_repo, modeled exactly insrc/graphify_okf_bridge/graphify_io/schema.py. Seespec/MAPPING.md§1 for the observed shape and surprises (notably:.sqlfiles produce zero graph nodes in a stock graphify run — the linker reads them from disk instead).tests/fixtures/okf_official/{ga4,stackoverflow,crypto_bitcoin}— vendored official OKF bundles, used as golden read fixtures.demo/— end-to-end walkthrough (real dbt project + GA4) and MCP notes.
License
Apache-2.0. Vendored test fixtures under tests/fixtures/okf_official/ are from GoogleCloudPlatform/knowledge-catalog (Apache-2.0).
Metadata
Release files for graphify-okf-bridge 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 | Provenance | Actions |
|---|---|---|---|---|
| graphify_okf_bridge-0.1.0.tar.gz | 233.5 kB | Without provenance | Details for graphify_okf_bridge-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| graphify_okf_bridge-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for graphify_okf_bridge-0.1.0-py3-none-any.whl |
Total release size: 267.6 kB
Release files / graphify_okf_bridge-0.1.0.tar.gz
| Download URL | graphify_okf_bridge-0.1.0.tar.gz |
|---|---|
| Size | 233.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
90fe1dfa2686ef7b7a5c71950c6d0d6b9e9cc72beb96b2a930cda75571af459f
|
|
BLAKE2b-256 checksum How to use checksums |
e61c1e541ff77ede62ba7637748f0d8d4a342e1bcb5a275cbebec7a5535b8eee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.23 {"installer":{"name":"uv","version":"0.11.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / graphify_okf_bridge-0.1.0-py3-none-any.whl
| Download URL | graphify_okf_bridge-0.1.0-py3-none-any.whl |
|---|---|
| Size | 34.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
71593dd6be9bc2ab173e4ecd7da2fc4ad95cc7f429c42eca9fbee568fce29d6a
|
|
BLAKE2b-256 checksum How to use checksums |
d1a3366af9a59c37007b413b1a596474518f64a705e89783e1cdb1d11a66d123
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.23 {"installer":{"name":"uv","version":"0.11.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for graphify-okf-bridge 0.1.0
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.