Skip to main content

Capstone: Onboard a Project and Ship an ADW PR

This is the graduation project for the ADW Track. Everything from Module 0 through Module 8 comes together here: you will take a real (or sandbox) project from "not on ADW" to "has a human-gated PR built by ADW," end to end, in your own hands.

Certificate on track completion

Completing the capstone checklist below and passing its quiz completes the ADW Track. Track completion is what triggers the Academy's completion record for this track — check the Academy home for how your completion is recognized.

What "done" looks like​

By the end of this capstone you should be able to point to:

  1. A project with a valid lat.md/ grounding it.
  2. That project's CI enforcing lat check as a required status.
  3. That project registered as a manifest so it feeds the company atlas.
  4. A working ADW entry point wired for wherever the project actually lives (pipeline 9 + targetRepo, or the GitHub adw-issue-trigger.yml).
  5. At least one draft PR, opened by ADW (local or cloud — your choice, and local is a completely legitimate choice for this capstone), that a human (you, or a teammate) then reviews and merges.

Nothing here requires the cloud path specifically — Module 8 was explicit that local is the correct default. The point of the capstone is the full loop, not proving you can drive the more complex path.

Capstone checklist​

Work through this in order — each step depends on the one before it.

1. Choose your project​

  • Pick a project: a real one you own or support, or a disposable sandbox repo if you'd rather not risk a live project for your first end-to-end run.
  • Note whether it lives in Azure DevOps or on GitHub — this determines your Module 6/7 entry-point path.

2. Ground it​

  • Create (or confirm) lat.md/ with at least one section describing what the project does and why, following the leading-paragraph rule from Module 2.
  • Add at least one [[wiki link]] and one // @lat: (or # @lat:) code reference tying a section to real code.
  • Run lat check locally and confirm it passes with zero errors.

3. Gate it​

  • Add (or confirm) a CI step that runs lat check on every PR.
  • Confirm that check is configured as a required status — not merely advisory. If you can't change branch protection settings yourself, get whoever can to flip this with you before moving on; a gate nobody enforces isn't a gate.

4. Register it​

  • Register the project as a manifest so it's known to feed the company atlas (Module 7). Confirm with whoever owns atlas registration if you're not sure it's already done.

5. Wire your ADW entry point​

Pick the path matching where your project lives:

  • ADO path: Confirm the ADW-Agents container identity has Contribute + Create-PR granted on this specific repo.
  • GitHub path: Add .github/workflows/adw-issue-trigger.yml, the ANTHROPIC_API_KEY repo secret, and the adw label.

6. Run the loop and ship​

  • Pick one small, real, low-risk task on the project.
  • Dispatch it — locally with ops digest runner --local, or via your wired cloud entry point (label an issue adw, or dispatch pipeline 9 with targetRepo set to your project).
  • Watch it move through classify → plan → implement → maker-checker → commit (Gemini Flash message) → draft PR.
  • If it's a web-UI project, confirm a RESULTS.md and walkthrough were produced, and that the promotion would have been refused had they been missing (Module 5).
  • Review the draft PR yourself as if you were the assigned reviewer: read the diff, read the evidence (if any), and only then merge it.

7. Reflect​

  • Write two or three sentences on what you'd do differently if you ran this again — a rough estimate of local vs. cloud cost of that run, anything that surprised you, or a gate that caught something.

Wastey says

When that checkbox on step 6 — the human merge — is checked, you've completed the actual loop this whole track has been building toward. That's the graduation artifact: not a certificate first, a shipped PR first.

Knowledge check​

Which of these is required for the capstone's "done" definition?
What must be true of the lat check CI gate for the capstone to count it as wired correctly?
For a GitHub-hosted capstone project, what three things need to be wired for the ADW entry point?

Your certificate​

Complete every module (and pass its knowledge check) plus this capstone to earn your Agentic Developer Workflow certificate. It appears here automatically the moment the track is complete — print it or save it as a PDF.

Checking your progress…