One product decision. Two ways in.
PMs, designers, researchers, and engineers do not work from separate versions of the spec. They collaborate around the repository's intent.md, entering the same loop from the responsibility they hold.
Judgment entrance
Hold the product context?
Request a structured change in Pathmode without operating Git. The request carries the proposed value and reason against one exact repository revision.
Repository entrance
Operate the coding agent?
Let the agent consume the request and deliberately apply it to intent.md. Pathmode never overwrites the canonical file from the browser.
The loop rejoins at the server-derived diff. Researchers and designers check that their judgment survived, engineers check coherence and feasibility, and the explicitly responsible human authorizes or rejects the exact revision before implementation begins.
Choose the responsibility closest to yours.
These are starting points in one workflow, not separate products or permissions.
Evidence owners
Pathmode for Designers & Researchers
Keep private evidence outside Git, request the outcome or edge-case change in Pathmode, and verify that your judgment reached the exact intent.md revision.
Judgment owners
Pathmode for Product Managers
PMs should not need Git to change the product decision, and coding agents should not build from a floating copy. Request the change in Pathmode, then authorize the exact intent.md revision.
Repository operators
Pathmode for Engineering Leaders
The repository owns intent.md. Your coding agent consumes structured requests, applies them deliberately, and receives the exact-revision human verdict before implementation.
Weighing it against your stack? See how Pathmode compares