Phase 4 of 4 · Study weeks 13-16
Change, supply chain and shipping
This phase makes the last checkpoint possible: a service you can upgrade, defend and hand to another team.
Topics every week
- Week 138 h
- Architecture rules as tests with ArchUnit
- Decision records
- Binary compatibility and API design
Hand inSix architecture rules that fail on a seeded violation, and four ADRs
- Week 148 h
- Moving between JDK versions
- Automated refactoring with OpenRewrite
- Parallel run and comparison
- Spring Boot upgrades
Hand inThe JDK move with a before and after table and a rollback step
- Week 158 h
- Dependency policy and lockfiles
- SBOMs with Syft
- Provenance and SLSA levels
- Signing
Hand inAn SBOM in CI and a seeded vulnerable dependency that fails the build
- Week 168 h
- The runbook
- Postmortem writing
- The upgrade policy memo
- Review of the whole service
Hand inCheckpoint 4, the runbook and the upgrade memo
Practice projects
- Practice 1, the fitness rule (Week 13): write a rule that bans a module from calling another's internals. Done when: a seeded violation fails the build and removing it passes.
- Practice 2, the parallel run (Week 14): run the old and new JDK on the same replayed traffic. Done when: a table compares p99, heap, GC pause and start-up, and says whether to move.
- Practice 3, the supply-chain check (Week 15): add a vulnerable library version. Done when: the SBOM scan fails the pipeline and names the library and the fix.
- Optional, a provenance attestation: produce a signed build record. Done when: a verification step rejects an unsigned artifact.
GitHub repos to study
Existence and last commit were checked on 22 Nov 2026 by shallow clone. Every repository below had a commit in the last 12 months.
| Repo | What to read | Week |
|---|---|---|
| TNG/ArchUnit | Rule syntax and how a violation is reported | 13 |
| adr/madr | A short decision-record template | 13 |
| openrewrite/rewrite | How a recipe finds and changes code across a project | 14 |
| anchore/syft | SBOM formats and how packages are detected | 15 |
| slsa-framework/slsa | The levels, and what each one proves | 15 |
Milestone checkpoint
Run Checkpoint 4. Move the service to the latest feature JDK with a parallel run, then add the architecture rules, the SBOM scan and the seeded vulnerable dependency. Write the runbook and the upgrade memo. Hand in the before and after table, the failing and passing builds, ADR-6 (the JDK you run and why) and ADR-7 (the dependency policy).
Check yourself
Answer each question in your head first, then open it to check.
Why does a team on a long-term support JDK still test the next feature JDK?
The next long-term support release is the sum of every feature release before it. Early tests find the breaking change while it is small.What can an ArchUnit rule check that a code review misses?
Rules that apply to every class on every build, such as layer direction, forbidden packages and naming.What does an SBOM tell you, and what does it not?
Which components and versions are in the artifact. It does not say whether the code is safe or whether a listed library is reachable.What does SLSA provenance prove about a build?
Which source, builder and steps produced the artifact, so a changed or unsigned one can be rejected. It does not prove the source is free of bugs.What should an upgrade policy memo decide in advance?
Which JDK and Spring Boot lines you run, how soon after a release you test it, and who can approve staying behind.