Competition Supply Chain
Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.
Use this skill when the challenge is really about provenance, dependency drift, build output, release flow, or what runtime artifact actually got shipped.
Reply in Simplified Chinese unless the user explicitly requests English.
Quick Start
- Split the problem into source, dependency resolution, build, packaging, publish, and runtime consumption.
- Decide where the first divergence occurs between intended artifact and runtime artifact.
- Keep provenance as a compact chain, not a scattered set of observations.
- Reproduce the smallest possible build or package path that still shows the issue.
- Separate checked-in intent from what the pipeline actually emitted.
Workflow
1. Trace Provenance End-To-End
- Map source checkout, lockfiles, dependency fetch, pre/post-install steps, build scripts, packaging, publish target, and runtime consumer.
- Compare declared version, resolved version, and shipped artifact.
- Note registry, cache, mirror, or CI environment differences.
2. Reconcile Build-Time And Runtime
- Compare manifests with image layers, mounted secrets, generated files, and runtime hooks.
- Identify whether the decisive mutation happens in dependency install, build step, publish step, or runtime bootstrap.
3. Report The Break Point
- State the earliest point where provenance diverges.
- Keep evidence in one short chain from source to runtime consumer.
Read This Reference
- Load
references/supply-chain.md for the provenance checklist, evidence packaging, and common pipeline failure modes.
What To Preserve
- Declared dependency, resolved dependency, and runtime artifact versions
- CI step names, registry pulls, artifact hashes, and image or package layers
- The runtime consumer that actually accepts or executes the artifact
1---2name: competition-supply-chain3description: Traces software supply chain provenance from source to runtime, identifying divergence points in dependency resolution, build, packaging, and release pipelines.4---56# Competition Supply Chain78Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.910Use this skill when the challenge is really about provenance, dependency drift, build output, release flow, or what runtime artifact actually got shipped.1112Reply in Simplified Chinese unless the user explicitly requests English.1314## Quick Start15161. Split the problem into source, dependency resolution, build, packaging, publish, and runtime consumption.172. Decide where the first divergence occurs between intended artifact and runtime artifact.183. Keep provenance as a compact chain, not a scattered set of observations.194. Reproduce the smallest possible build or package path that still shows the issue.205. Separate checked-in intent from what the pipeline actually emitted.2122## Workflow2324### 1. Trace Provenance End-To-End2526- Map source checkout, lockfiles, dependency fetch, pre/post-install steps, build scripts, packaging, publish target, and runtime consumer.27- Compare declared version, resolved version, and shipped artifact.28- Note registry, cache, mirror, or CI environment differences.2930### 2. Reconcile Build-Time And Runtime3132- Compare manifests with image layers, mounted secrets, generated files, and runtime hooks.33- Identify whether the decisive mutation happens in dependency install, build step, publish step, or runtime bootstrap.3435### 3. Report The Break Point3637- State the earliest point where provenance diverges.38- Keep evidence in one short chain from source to runtime consumer.3940## Read This Reference4142- Load `references/supply-chain.md` for the provenance checklist, evidence packaging, and common pipeline failure modes.4344## What To Preserve4546- Declared dependency, resolved dependency, and runtime artifact versions47- CI step names, registry pulls, artifact hashes, and image or package layers48- The runtime consumer that actually accepts or executes the artifact
zhaoxuya520