Skip to content

Advisory supply-evidence gate: run OwnAudit ci-light profile after replay semantics are safe #44

Open

Description

@PhysShell

Classification

Problem

007 should not become a supply-chain scanner. It already has one job: isolate a target worktree, run an agent, execute gates, harvest evidence and preserve a run record.

Supply/provenance checks belong in OwnAudit as profile-driven evidence adapters. 007 should only invoke an OwnAudit profile and record the resulting artifacts.

Also, 007 currently has a known semantics gap tracked in #43: required gates that do not actually execute must not accidentally reduce to PASS. Until that is fixed, any supply-evidence gate must remain advisory/non-blocking.

Goal

Add a narrow integration path for an OwnAudit supply evidence profile:

[[gate]]
name = "supply-evidence-ci-light"
cmd = "python audit/supply/run.py --profile ci-light --target artifacts/bin --out artifacts/supply"
required = false

007 must treat this as just another gate command with artifact capture. It must not know SL001, SC005, SourceLink, NuGet signatures, Scorecard or SBOM semantics.

Required behavior

  1. The gate is advisory by default.
  2. The command path/profile is configured in the target repo, not hardcoded in 007.
  3. 007 records produced artifacts by digest, for example:
artifacts/supply/evidence.jsonl
artifacts/supply/supply.sarif
artifacts/supply/coverage.json
  1. If Run semantics: replayable event reducer and fail-closed required-gate verdicts #43 event streams are available, the gate result and artifact digests become replay-verifiable run events.
  2. Missing supply artifacts are visible as a gate/evidence limitation, not silently ignored.
  3. Required mode is allowed only after fail-closed gate semantics are implemented and tested.

Relationship to OwnAudit

OwnAudit owns supply evidence logic:

nuget-resolution-policy
sourcelink-debuggability
nuget-integrity
known-vuln
sbom
repo-posture
attestations
rebuild-lab

007 owns only:

run command
capture stdout/stderr
capture exit code
capture declared artifacts/digests
reduce/replay gate state

Suggested target gate file

For a target repository:

[[gate]]
name = "supply-evidence-ci-light"
cmd = "python audit/supply/run.py --profile ci-light --target artifacts/bin --out artifacts/supply"
required = false

[gate.artifacts]
paths = [
  "artifacts/supply/evidence.jsonl",
  "artifacts/supply/supply.sarif",
  "artifacts/supply/coverage.json"
]

The exact manifest shape may change with #43/#42. The semantic requirement is stable: 007 records the evidence; it does not interpret it.

Non-goals

Required controls

  1. Advisory supply gate passes/fails without changing overall required verdict.
  2. Required supply gate is rejected or blocked until required-gate semantics are fail-closed.
  3. Gate artifact digest changes after run sealing are caught by replay once Run semantics: replayable event reducer and fail-closed required-gate verdicts #43 lands.
  4. Missing artifact path is represented in the run evidence.
  5. Legacy runs without supply artifacts remain readable with explicit limitations.
  6. A target repo can remove the supply gate without breaking 007.

Acceptance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions