Identity, Ethics, Career — What Kind of Builder You Become

The capstone. Confront the ethics questions PM capability raises and no framework answers: engagement design, pricing leverage over dependent users, sunset obligations, the demand-it-or-we-walk customer, the refusal lines, AI data ethics. Write the final edit of the position document and read the diff against M0's version. The diff is the curriculum. The refusal lines are the production runbook: responses decided in advance, under low pressure, so the high-pressure version is retrieval, not generation. Most ethics failures in product work happen not because the operator was unethical but because the decision arrived under pressure with no prior reflection on file. The per-product audit is code review for a solo operator: you can't get a second pair of eyes from a teammate, so you institutionalize the second pass yourself — incomplete, and better than no review. The position document is the architecture decision record for your career: what was decided, why, what alternatives were considered, what was deliberately refused — the artifact that outlives the specific products. And the M0-to-M14 diff is the git log: a year of commits tells a story no single commit tells. Most builders never write the document, so the diff is invisible — the work happened, but the record didn't. The discipline is making the record, so the next five years build on this year instead of replaying it.