Flowchart · 02 of 07 · What you change

What you change, and what the platform owns

The developer's surface is a push and one file. Everything in the larger box is the platform's: generated boilerplate, a shared catalog, the stage order, the telemetry and the events.

What you change, and what the platform owns Flowchart. On the left, the developer does two things: pushes to git and edits cicd.yaml. On the right, the platform owns the rest: Pipelines-as-Code reads platform-generated .tekton files and runs validate, build, test, deploy and release in order. Validate reads cicd.yaml fresh from the triggering commit. Every step emits a span into one trace per flow, and every stage emits a CDEvent that the broker uses to chain the next stage and that DORA metrics consume. YOUGLIDEPATH · THE PLATFORM OWNS ALL OF THISWEBHOOKREAD FRESH, EVERY RUNSPANSCDEVENTSgit pushany branch rulecicd.yamlthe one filePaCreads .tekton/validatefails fastbuildkaniko · signedtestTestkubedeploylower envsreleasegitops PROne trace per flowotel-cli span per step · TempoStage eventsbroker chains stages · DORAA fixed superset of stages, switched on by config. Not an arbitrary graph compiled per app.LEGENDWhat you editYour actionPlatform stageRecordConfig readTelemetry

Principle honored

Platform as a product: a small, stable contract for developers, and the engineering on the platform side.

What changes

  • .tekton/ files are generated at onboarding and never hand-edited.
  • cicd.yaml has no sync step and no second copy: it is read from the commit.
  • An undeclared stage never runs.

Fails fast

A bad cicd.yaml fails in validate, with a readable schema error, before any build starts.

Hangar · Glidepath