Clarify scope vs process in Hierarchy of Truth

[rdryfoos]

Makes the constitution/PRD split explicit so agents don’t invent product scope from process docs.

Changes

• Constitution 1.2.1 — Hierarchy of Truth: product scope = PRD; engineering law = constitution; story maps outside the machine-checked chain
• CLAUDE.md — one-liner for cold agents
• traceability.md — Gate 2 proves the PRD is true of the system, not that it’s the right product
• README.md — Story Map reframed as a human planning aid; PRD listed first as authoritative scope

No product requirements or Gate 2 behavior changes.

  

Summary by CodeRabbit

• Documentation
  • Clarified that product scope and acceptance criteria are defined exclusively in the product requirements document.
  • Clarified the roles and hierarchy of project governance and planning documents.
  • Updated the governance document version and amendment date.
  • Reordered the core documents list for clearer prioritization.
  • Clarified Gate 2 traceability expectations and limitations.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9a0d9c92-a998-4be3-b520-0be5daabac8c

📥 Commits

Reviewing files that changed from the base of the PR and between ea6c810 and 302b820.

📒 Files selected for processing (4)

• .specify/memory/constitution.md
• CLAUDE.md
• README.md
• traceability.md

---

📝 Walkthrough

Walkthrough

Documentation updates clarify that product scope comes from HomesFlow.prd.md, process rules come from the constitution, external planning aids are informational, and Gate 2 covers authorization and acceptance-criteria traceability rather than product-direction validation.

Changes

Governance documentation alignment

Layer / File(s)	Summary
Product and process authority .specify/memory/constitution.md, CLAUDE.md, README.md	Defines the PRD as the product-scope authority, the constitution as the process authority, and reorders the core-document listing.
Gate 2 traceability scope traceability.md	Specifies registry-ID authorization, acceptance-criteria verification or debt tracking, and the exclusion of product-discovery validation.

Estimated code review effort: 1 (Trivial) | ~3 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/hierarchy-scope-vs-process-7716

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud