docs: finish governance cleanup - #6
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates several documentation files, including AGENTS.md, docs/README.md, and docs/product/product-philosophy.md, to clarify document authority, status, and boundaries. It establishes that the Product Requirements Document (PRD) governs in case of conflicts with draft documents, lists new planning and architecture documents, and removes hardcoded local user paths. The review feedback recommends minor wording improvements for clarity and precision, such as explicitly naming the documents in conflict clauses and using "statuses" instead of "limits" when referring to document metadata states.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
|
||
| This document is the draft home for durable product principles. Its `Draft` | ||
| status means the wording remains open to revision and does not carry the same | ||
| authority as the accepted PRD. When the documents conflict, the PRD governs. |
There was a problem hiding this comment.
To avoid ambiguity about which documents are being referred to, specify 'this document' and 'the PRD' explicitly.
| authority as the accepted PRD. When the documents conflict, the PRD governs. | |
| authority as the accepted PRD. If this document conflicts with the PRD, the PRD governs. |
| Use each document according to its metadata. The PRD and ADR-0001 are accepted | ||
| direction; the roadmap is active planning; the product philosophy, technology | ||
| stack, and implementation plan retain their stated draft or proposed limits. |
There was a problem hiding this comment.
Using 'statuses' or 'authority levels' is more precise than 'limits' when referring to the metadata states (like Draft or Proposed) of these documents.
| Use each document according to its metadata. The PRD and ADR-0001 are accepted | |
| direction; the roadmap is active planning; the product philosophy, technology | |
| stack, and implementation plan retain their stated draft or proposed limits. | |
| Use each document according to its metadata. The PRD and ADR-0001 are accepted | |
| direction; the roadmap is active planning; the product philosophy, technology | |
| stack, and implementation plan retain their stated draft or proposed statuses. |
1 participant
What changed
Why
These changes close the remaining documentation-governance drift before implementation begins without introducing a duplicate truth-boundary ADR.
Validation
git diff --checkpassed