ip-lineage

Generate lineage records and flag license conflicts for release artifacts.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill ip-lineage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ip-lineage
Source: https://github.com/brucebanner010198-commits/DevSecOps-Agency/tree/main/skills/ip-lineage
Command: npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill ip-lineage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track provenance for every generated artifact — prompts, models, training data similarity, external dependencies, and user contributions. Produces a lineage statement on close-phase. Flags incompatible licenses, concerns around training-data similarity, and unattributed user contributions. Pairs with sbom-slsa (sbom = composition, lineage = origin).

Core Features & Use Cases

  • Build a provenance lineage for each artifact, capturing prompt source, model details, external inputs, and derived sources with attribution.
  • Reconcile licenses by pulling each dependency's license, cross-checking against the project's declared license, and flagging incompatibilities.
  • Run similarity checks on creative outputs to flag high similarity with known corpora and require attribution as needed.
  • Write and attach a lineage statement to release assets, ensuring traceability across the delivery lifecycle.
  • Integrate with sbom-slsa for composition lineage and provenance tracking.

Quick Start

Run the ip-lineage workflow during release to generate a lineage statement for each shipped artifact.

Frequently Asked Questions about ip-lineage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track artifact provenance for prompts, models, and dependencies during a project release?

Track artifact provenance by capturing prompt sources, model details, external inputs, and derived sources with attribution. Applying this during the project close-phase generates a lineage statement that ensures traceability across the delivery lifecycle for every shipped artifact.

What is artifact lineage and how does it differ from an SBOM?

Artifact lineage records the origin and provenance of generated assets, while an SBOM details software composition. Lineage tracks prompts, models, and user contributions, pairing with SBOM composition data to provide complete traceability of origins and components.

How do I check for license conflicts across external dependencies before shipping release assets?

Check for license conflicts by pulling each dependency's license and cross-checking it against the project's declared license. This provenance process flags incompatibilities, ensuring release assets comply with attribution requirements before you attach the final lineage statement.

Can I flag high training-data similarity in creative outputs and require attribution?

Yes, you can flag high training-data similarity in creative outputs. Running similarity checks against known corpora identifies potential overlaps, requiring you to add proper attribution to the generated artifacts before completing the close-phase lineage statement.

When do I need to generate a lineage statement for my project artifacts?

Generate a lineage statement during the release or close-phase of a project. This is when you reconcile licenses, attribute user contributions, and attach provenance records to release assets, ensuring full traceability for shipped artifacts, models, and dependencies.