Wire the Pipeline to the Package
Updated
AdvancedWhat you'll learn
~18 min- Wire pipeline evidence into the control catalog so the package regenerates from delivery events
- Use deterministic export as the release gate for compliance artifacts
- Keep the human gates that must survive automation - and remove the ones that should not
Two systems, one wire
Lesson 6.1 located the process gap precisely: evidence arrives continuously, then waits for humans to assemble it into a package on a calendar. This lesson closes that gap with a wire between two systems this training’s ecosystem already built.
On one side: the evidence push pipeline - this site’s DevSecOps Foundations training and its capstone pattern (Evidence as a Push Pipeline - in short, for readers starting here: every pipeline run pushes a bundle - scan outputs, test results, provenance - mapped to control IDs, into an append-only store; evidence models declared as data say what-proves-what with freshness contracts). On the other side: this training’s catalog-driven assessment machinery (2.1’s evidence contracts, 3.1’s collectors and verdicts, 2.3’s deterministic exports). The wire diagram connects them:
pipeline run completes (build/scan/test/deploy) -> evidence bundle pushed: outputs + control-ID manifest + provenance (commit, pipeline, artifact hashes) [the DevOps push] -> bundle lands in the evidence store (3.2): content-addressed, WORM, provenance digests -> the CATALOG's evidence contracts (2.1) recognize the bundle: these entries name pipeline-pushed evidence types alongside collector-pulled ones - push and pull are PEERS feeding one contract -> the evaluator (3.1) re-runs affected controls: strict-AND, 800-53A vocabulary, coverage accounting updated -> the EXPORTS regenerate (2.3): OSCAL, docs site, Word package -> byte-equality gate: if nothing assessment-relevant changed, output is byte-identical -> NO-OP. If something changed -> a DIFF, routed to humans as a reviewable changeRead the last step twice, because it’s the design’s center of gravity: determinism (2.3) is what makes a self-updating package safe. Without it, every pipeline run would churn the package and reviewers would drown in noise — automation would reduce assurance. With it, the package is quiet until reality changes, and when reality changes, the package diff is the change review: one firewall control’s verdict flipping to partial shows up as three legible lines in a generated SSP, not as a regenerated document nobody re-reads. The byte-equality gate is thereby promoted from CI hygiene to the release gate for compliance artifacts — package versions are cut exactly when reality diffs, at the cadence of change rather than the cadence of quarters. That’s authorization-as-stream’s engineering half: the stream is a sequence of small, reviewed, provenance-carrying package diffs.
Which humans stay in the loop
Automating the assembly line does not automate the judgments - and the design is honest only if its gate structure names which gates survive:
SURVIVES AUTOMATION (judgment gates): AUTOMATED AWAY (assembly toil):- implementation statements: authored - collating evidence into by humans, always (2.2's line holds - binders by hand the wire moves evidence, never claims) - re-typing verdicts into- verdict-flip review: a control changing documents state is a human-reviewed diff before - regenerating exports and the package version ships diffing them by eye- the acceptance itself: the AO (or their - noticing that evidence ongoing-authorization mechanism) decides; went stale (freshness the wire feeds the decision a stream contracts page someone instead of a quarterly binder instead)The failure mode to design against is the middle one quietly disappearing: a package that re-versions on every verdict flip without review recreates 3.1’s automation theater one level up — tooling attesting to tooling, now with the AO’s signature downstream of it (2.2’s warning, industrialized). The verdict-flip review is cheap (it’s a diff), and it’s the human link that makes the stream trustworthy.
Prompt first: close the loop on one control
Switch your workspace agent to Plan mode on controls/SC-7.yaml, your evaluator config, and your export pipeline (if you do not have live exports or files handy, ask it to generate a small Meridian practice sample from the lesson’s scenario first):
Plan how to wire SC-7 end-to-end so pipeline-pushed evidence and collector feeds both trigger the evaluator, regenerate exports only on a verdict change, and open a reviewable diff for the ISSO.Check that the plan or draft covers:
- Extending
controls/SC-7.yamlso its evidence contract names pipeline-pushed bundle types (scan SARIF and deploy manifest) alongside collector-pulled feeds - Subscribing the evaluator to evidence-store events for those types, re-running strict-AND checks, and updating
coverage.md - Regenerating package exports behind the byte-equality gate so an ISSO pull request opens only when a verdict actually flips
- A staging drill that injects a deliberate misconfiguration and measures the latency from pipeline event to reviewable package diff for your Lesson 6.1 gap statement
If the draft regenerates and commits new package versions on every passing build, follow up with: Gate export commits on the byte-equality check so the package updates only when a control verdict flips.
One control first, drilled and measured, then scaled by contract: the same incremental discipline every migration in this training family follows.
The DevSecOps training’s evidence models carry expected cadence and stale-after thresholds per evidence type. Once the wire is live, those freshness contracts are not metadata - they are your continuous-monitoring SLA, mechanically checkable: a control whose evidence goes stale flips to an evidence-gap state (3.1’s warning band) and pages the owner, BEFORE an assessor finds the hole. Quarterly programs discover staleness at reassessment; wired programs discover it at the stale-after threshold. That difference, repeated across every control, is most of what ‘continuous’ means in practice.
Six weeks after the wire goes live, a teammate proposes removing the verdict-flip review: 'the evaluator is strict-AND and the exports are deterministic - the review step just adds latency to a mechanically correct pipeline.' What is the strongest correct response?
Key takeaway
The wire joins the DevSecOps Foundations training’s evidence push to this training’s catalog machinery: bundles land content-addressed, contracts recognize them, verdicts re-run, exports regenerate — and the byte-equality gate turns determinism into the release gate, so the package versions exactly when reality changes, as a reviewable diff. Keep the judgment gates (statements authored, flips reviewed, acceptance decided); automate only assembly. Pilot one control, drill it, measure the evidence-to-package lag — that number is the process leg closing. Next: naming the frameworks all this machinery already practices.