deployed_

the weeks / Week 8 · Capstone

Capstone: package, publish, present

One of your agents becomes a product other systems can rely on.

Package your best agent as an MCP server a stranger's agent can use cold: tool descriptions written for a reasoning reader, rate limits, auth, a published eval report. Our harness is the stranger: it connects with no help from you and attempts real tasks. You record a five-minute walkthrough, present to the cohort, and include the one failure that taught you the most, written as a post-mortem.

It ends with

A live MCP endpoint, a published eval report, your decision log, the recorded walkthrough, and the final debrief.

Field notes

  • 7.6 When does one agent become several? program
  • 8.3 What breaks when two systems quietly disagree? program
  • 8.4 How does your agent plug into tools it has never seen? program
  • 10.3 Should the agent be allowed to improve itself? program
  • 11.2 How do you present numbers people can check? program
  • 11.3 How do you say "it didn't work"? program