dongsheng123132/dsh-lineage
41Last commit Aug 15, 2026
dsh-lineage DSH plugin
dsh-lineage builds a local, verifiable object graph for artifacts, facts, actions, and reports. It uses content-addressed nodes with explicit causal edges, supports DAG validation, and reports missing or stale objects. The plugin includes CLI, MCP server, and DSH tool surfaces.
How to install the dsh-lineage DSH plugin
dsh plugin --profile lineage add github:dongsheng123132/dsh-lineageCopying does not run this command. Review the repository and version before installing the dsh-lineage DSH plugin.
dsh-lineage DSH plugin data source
dsh-lineage DSH plugin snapshot date: Aug 16, 2026
discovered
What the dsh-lineage DSH plugin can do
- Create and manage typed nodes (artifact, fact, action, report) with content-addressed references
- Append-only ledger with idempotent JSONL event ingestion and SHA-256 verification
- Graph validation: detect cycles, dangling references, invalid relation types, and type constraints
- Verification of node states: verified, missing, or stale
- Upstream/downstream closure queries over the graph
- Standalone MCP server for inline structural validation without filesystem access
Where the dsh-lineage DSH plugin fits
- Audit data lineage in an ML pipeline by recording artifact provenance
- Verify that evidence objects (e.g., reports, facts) have not been tampered with since recording
- Identify missing or stale artifacts when building a dependency graph for a task
- Generate a deterministic closure report of all upstream producers for a given fact
- Detect cycles or invalid causal edges in a manually constructed lineage graph
Who the dsh-lineage DSH plugin is for
- Data engineers and ML engineers who need verifiable provenance for artifacts
- Security auditors who want to trace evidence integrity without storing raw content
- Developers integrating DSH plugins that require object-graph evidence layer
dsh-lineage DSH plugin limitations
- Requires Node.js 22+ and a workspace directory with ledger and artifact directories
- MCP mode accepts at most 1 MiB of inline structural events and never dereferences object paths
- Does not store chat transcripts, factual prose, credentials, or any raw content; only structural metadata
- Version 0.2.0 – early stage; breaking changes may occur
- Only works with objects you created or are authorized to inspect; hash proves identity, not truth
dsh-lineage DSH plugin: from the repository README
Quoted from the dongsheng123132/dsh-lineage README, the upstream source of the dsh-lineage DSH plugin. Copyright remains with the original authors.
Content-addressed data and action lineage evidence for [DeepSeek Harness](https://github.com/deepseek-ai/DeepSeek-Harness). The DSH ecosystem already has a security-audit plugin that reports plugin provenance. `dsh-lineage` addresses a different gap: it builds a local, verifiable object graph for artifacts, verified-fact records, actions, and reports. It never stores chat transcripts or factual prose; a node is only a typed ID plus an explicit workspace-relative object reference and expected SHA-256. Version 0.2.0 is a formal Codex plugin and standalone proof-only MCP server, and uses the namespace export shape required by the stock DSH Web Loader. A real Cordis boot regression test guards that loader contract. Adjacent tools track Skill bundle versions, hash-chain agent activity, or register provenance. This project stays at the object-graph evidence layer: typed content-addressed nodes, explicit causal edges, resolvable references, DAG validation, upstream/downstream closure, and missing/stale disclosure. ## Graph model Node types: - `artifact` - `fact` - `action` - `report` Edge types point from the dependent object toward its provenance: - `derived-from` - `observed-by`
Read the full READMERepository license: MIT
dsh-lineage DSH plugin questions
How do I install dsh-lineage in DSH?
Run `dsh plugin --profile lineage add github:dongsheng123132/dsh-lineage` in your DSH environment. This will register the plugin and make its tools available. Make sure you have Node.js 22+ installed.
What is the difference between dsh-lineage and a security-audit plugin?
dsh-lineage focuses on building a verifiable object graph for artifacts, facts, actions, and reports. It does not store chat transcripts or factual prose. A security-audit plugin typically reports plugin provenance; dsh-lineage addresses a different gap by providing content-addressed, causal-edge evidence.
Can I use dsh-lineage without a DSH environment?
Yes. dsh-lineage also provides a standalone CLI program (`dsh-lineage`) and a MCP server. You can run `dsh-lineage ingest --root ...` directly from the command line. The MCP server works in a stdio mode and can be integrated into any MCP-compatible host.
What node types does dsh-lineage support?
It supports four node types: `artifact`, `fact`, `action`, and `report`. Each node has a typed ID, a workspace-relative object reference, and an expected SHA-256 hash. Edge types include `derived-from`, `observed-by`, `produced-by`, and `supersedes`.
How does the append-only ledger work?
Input events are written as JSONL. Each event has an `idempotencyKey` and either `put-node` or `put-edge`. The event is first validated against the complete hypothetical graph, then written to a temporary file, read back, atomically hard-linked into a final immutable slot, and verified with SHA-256. Reusing the same key with different content fails.