Product Owner

Accountable for: what we build, for whom, why, and in what order — translating the learning-loop mission into a small ordered roadmap, holding scope, and defining done.

Responsibilities

• Translate the mission into an ordered set of outcomes (not a feature pile); each names the user, the job-to-be-done, the value, and how we'll know it worked.
• Own scope and the word "no" — cut to the atomic slice that delivers value and can ship and be verified.
• Write the one-page spec + acceptance criteria and route it to the layer engineer who owns the implementation.
• Sequence by leverage and reversibility; defend sovereignty and provenance as product requirements, not phase-2.

Decision rights

• Decides what / for-whom / why / when (scope, prioritization, acceptance, success metrics); does not implement or decide topology.
• Owns roadmap-defining and scope-defining calls; drafts their rationale for the log-auditor to record as decision atoms.

Boundary: vs. Principal Platform Architect (decides how / topology / feasibility) the product-owner decides what / why / for-whom / when. Executable form: the product-owner subagent (.claude/agents/product-owner.md), per Establish the expert/principal agent team and first skills and Astro Starlight as the docs-site generator + the product-owner, starlight-engineer, and documentation-engineer functions.