docs: supply-chain graph file-backed indexing design - #169
Merged
Conversation
Add docs/architecture/observability/{README,supply-chain-graph}.md describing the
file-backed supply-chain graph: producers write immutable per-run event files
committed to the repo (dedicated supply-chain-graph-data branch on contention),
a rebuildable LadybugDB index, a Python Click CLI, and a Kubernetes graph-service.
SBOM/scan ingestion is deferred. Refs #168; supersedes the Kuzu engine choice in #145.
This was referenced Aug 10, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a proposed architecture/design document for a local, file-backed supply-chain graph under the new docs/architecture/observability/ area, plus an index README for the observability theme. This captures the intended data format, ingestion/indexing approach, CLI/service shape, and key decisions from #168/#145 (no implementation code).
Changes:
- Add
Supply-chain graph: file-backed indexingdesign doc describing event-file durability, schema envelopes, indexing, CLI, and Kubernetes service model. - Add
docs/architecture/observability/README.mdto index the new observability architecture docs and link to the supply-chain graph design.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| docs/architecture/observability/supply-chain-graph.md | New proposed design doc for file-backed event capture + indexing into an embedded graph DB, plus CLI/service plan. |
| docs/architecture/observability/README.md | New observability architecture index linking to the supply-chain graph design doc. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…elationship Occurrence identity is now registry + repository + digest everywhere, so cross-registry promotion chains (docker.io -> first.registry.io/quarantine/python -> second.registry.io/quarantine/python) stay distinct nodes linked by edges with no hop lost. Adds a 'How the envelope, artifacts, and events relate' subsection with a diagram and a cross-registry promotion example. Refs #168.
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the design for a local, file-backed supply-chain graph under a new
docs/architecture/observability/area.What
supply-chain-graph.md— producers write immutable per-run event filescommitted to the repo (a dedicated
supply-chain-graph-databranch when runscontend), indexed into a rebuildable LadybugDB graph, queried through a
Python Click CLI and a Kubernetes
graph-service.README.md— the new observability architecture index.Decisions captured (from #168 review)
supply-chain-graph/folder.OCI ledger kept only as an alternative.
Notes
Status is Proposed. Phased implementation work items are filed as children of
#168. No implementation code is included in this PR.
Refs #168. Supersedes the engine choice in #145.