State is a current view with accountable ownership
In this framework, a state record identifies the current product position and the authority behind it. It need not be stored in a database. A carefully maintained document can be structured if its fields and relationships are clear.
Do not confuse product state management with application runtime state or a UI state-management library. The subject here is the product agreement that guides development, not the data an application holds while a user clicks through it.
A useful view distinguishes accepted scope from proposed changes and unknowns. A summary that merges them into one confident narrative is not a trustworthy current agreement.
Fields that make the view inspectable
| Field | Purpose | Example value |
|---|---|---|
| Goal | Connect work to a user outcome. | Help account owners identify unresolved requests. |
| Accepted scope | Describe the current commitment. | A private list filtered by request status. |
| Non-goals | Prevent implicit expansion. | No public sharing or cross-account view. |
| Requirement status | Separate review from authorization. | R3 accepted; R4 proposed. |
| Decision references | Explain authority and rationale. | D-9 defines the initial audience. |
| Open questions | Keep uncertainty visible. | Retention period awaiting owner review. |
| Version and review | Support consistent handoffs. | Version 2, reviewed by the product owner. |
The example values describe a fictional initiative. Choose fields because they reduce ambiguity, not because a particular storage format demands them.
Change state through explicit transitions
A simple requirement lifecycle is proposed → in review → accepted → superseded or retired. These are working conventions, not universal statuses. Define who can make each transition and what evidence is needed.
An implementation task being completed does not, by itself, authorize a proposed requirement. Similarly, an accepted requirement may still be unimplemented. Keep approval status separate from delivery and verification status so “done” does not mean several incompatible things.
When a change is accepted, check the affected specification, tests, rollout notes, and related decisions. A state update without those dependency checks can leave several contradictory versions in circulation.
Example: a scope change that should not happen silently
Illustrative current agreement: the request list is visible only to account owners. During implementation, an agent proposes a public sharing link because it would simplify a review flow.
- Capture public sharing as a proposed change; do not add it to accepted scope.
- Identify the affected access rule and the decision that established it.
- Ask the owner to compare the benefit with the changed audience and disclosure consequences.
- If approved, create a new decision and a reviewed version of the access requirements.
- Update the current view and mark the old access rule superseded only to the extent specified by that decision.
If the proposal is rejected, leave the accepted state unchanged and preserve the rejected option in the history. The conversation can evolve without changing the product agreement.
State, memory, and history answer different questions
- State: what is the current accepted position?
- Decision history: why did that position change over time?
- Product memory: what knowledge and evidence should remain available for later work?
In practice, link these views rather than copying the same long explanation into all of them. A current state summary can cite a decision ID; the decision can cite the original research.
Start with a weekly consistency check: does every accepted requirement have an owner and an accepted reason, and can a reviewer tell which version guides current work? Use PM Harness as the surrounding process and controlled AI development to protect transitions during execution.