PPalabas APIJava field course

Module 8 / Checkpoint

Final Checkpoint: Evidence-Backed Java Backend Course

Close M7 with observability, shipping, interview mapping, final articles, and a release/deploy evidence check.

Concept

The course ends when every backend claim has a runnable or inspectable proof. A green local build is necessary, but the final shipping claims also need external evidence from CI, image publishing, and the live demo.

Task

  1. Run the local verification suite.
  2. Review M7 evidence in the milestone audit.
  3. Confirm the final articles link to logs, metrics, tests, CI, and deployment notes.
  4. Create release and phase tags only after the external deployment evidence exists.

Run

npm run verify:m7
npm run build
./gradlew test
./gradlew dockerTest

Expected Result

  • The local course and learner repo gates pass.
  • Any missing external deployment evidence is named rather than hidden.

Common Traps

  • Tagging v1.0.0 before the live demo exists.
  • Treating a runbook as proof that the image was pushed.
  • Closing Linear without evidence comments.

Hint Ladder

Hint 1

Separate local proof from external release proof.

Hint 2

The final checkpoint should be boring and auditable.

Hint 3

If an external credential is missing, leave the exact missing proof in the audit.

Solution

See docs/milestone-audit.md for the M7 evidence map.