My Engineering Work
My engineering contribution is five source-backed changes to the integrated GCP supply-chain project. I adapted and hardened canonical identity, PR image scanning, exact claim verification, admission-reader access and immutable digest selection. The case studies below show each patch, its retained behavior and the evidence that supports it.
I also maintain this independent handbook to make those decisions inspectable. It connects the artifact, workflow authority, authenticated statements, selected Git state, admission result and runtime observation rather than presenting a list of tools.
- Canonical identity
Aligned repository, signer, provenance and desired-state references.
- Exact verification
Separated PR validation and guarded main release checks.
- Verifier & release
Scoped registry reader access and manually selected immutable digest.
Text equivalent and limits
- Aligned repository, signer, provenance and desired-state references.
- Separated PR validation and guarded main release checks.
- Scoped registry reader access and manually selected immutable digest.
Read the labeled relationships as the stated contract. Optional connections are dashed and explicitly labeled; comparisons do not imply a sequential handoff. This figure explains inspected code or recorded observations, not current cloud execution.
Five changes you can inspect
Section titled “Five changes you can inspect”| Engineering question | My concrete change |
|---|---|
| What must agree after repository integration? | Aligned canonical identity across GitOps source, signer/provenance expectations, ownership and metadata. |
| What can a PR validate without release authority? | Added a local PR image scan without pushing the image or granting the job OIDC permission. |
| What makes verification actually fail? | Enforced exact verification of the expected identity, digest and qualifying provenance/SPDX claims. |
| How does admission read the required claims? | Integrated a separate verifier reader for application images and Cosign metadata through GKE Workload Identity. |
| Who selects the artifact that runs? | Committed the selected immutable digest to Helm, separately from building and signing it. |
Each case links the full public commit and the retained source at cbbc807c0c150e106affa89fbb1b9e8349005749. Git metadata and GitHub associate all five commits with devSatym; each is an ancestor of this edition. They are unsigned commits, so the attribution is not cryptographic authorship proof. The case-study rationale is current engineering analysis unless the historical record says otherwise.
Adapted and integrated
Section titled “Adapted and integrated”The source project’s merge record documents the combination of application and infrastructure component histories. Imported nested infrastructure workflows remain provenance material; executable monorepo workflows live under the root .github/workflows path.
The five attributed changes extend that integrated system. They do not imply that I originally created every component or tool. Their exact scope matters: main restrictions are workflow guards rather than a ref-bound GCP federation condition; admission checks fewer provenance fields than CI; promotion is manual; and the init-container experiments establish only the fields actually exercised.
This handbook teaches the preserved GCP edition. The reviewed source main is Azure, while documentation main belongs to the independent private handbook. Neither the author’s identity nor Cloudflare hosting changes that implementation boundary. A historical checkout also needs deliberately rebound main-based identities and registry contracts before an owned reproduction.
Documented and maintained
Section titled “Documented and maintained”I maintain the explanation, reader navigation, static search, typed catalogues, source links, diagrams and classified evidence. The handbook records verifier field differences, scope exclusions, inactive paths, trade-offs and gaps alongside the happy path.
The website has its own build and publication trust model. Its source is private; its approved static output is public. The historical cluster’s admission policy does not protect this website. Current website validation and deployment receipts are recorded separately in website engineering, and the About page contains the owner-provided public profile.
Historical validation ownership
Section titled “Historical validation ownership”The source personal validation record reports a collection dated 23 August 2026; the capture addition preserves it in Git. These owner-recorded images differ from older upstream material under docs/evidence/.
The collection shows historical CI verification, GitOps/cluster observations, admission acceptance/rejection and a controlled Falco event. The strict-CI 27a94b0/a0073f8f artifact family is distinct from the selected live 32a90d family. No current cluster-health claim follows.
Wrong-trust changes signer and source expectations together. Both mixed-image fixtures exercise unsigned init containers, and Falco detects a shell after execution. Optional Discord delivery is not demonstrated. The evidence catalogue and case pages retain these boundaries. Website tests and newly drawn visuals do not rerun the cloud experiments.
Original implementation and upstream provenance
Section titled “Original implementation and upstream provenance”The pinned provenance record credits the application/security component to musaumakau/supply-chain-security and infrastructure/runtime component to musaumakau/gcp-infrastructure-modules. Their current branches are not claimed to equal the reviewed baseline.
Those components and their applicable license/attribution notices remain part of the system’s provenance. My claims here concern the specific adaptation, integration, hardening and documentation above. No invented employment impact, production adoption or sole original-creator claim is needed to explain that work.