Feature Specification · Example edition
Make the edge cases part of the design.
This fictional specification covers approving a handover entry. Approval means the owner has reviewed the reference and its context; it does not automatically change file sharing.
| State | Meaning | Allowed next step |
|---|---|---|
| Draft | Entry is being prepared | Submit for review |
| In review | Owner is checking the entry | Approve or return to draft |
| Approved | Reference and context were checked | Reopen when content changes |
| Archived | Entry is retained for history | Restore to draft |
Main flow
The author supplies a title, purpose, reference, and update owner. The reviewer checks the content and either approves it or returns it with a concrete reason.
Validation and recovery
A missing reference prevents submission and should be explained beside the field. If the reference becomes unavailable after approval, show that condition and preserve the entry for repair.
Permission boundary
Approval is a content state, not authorization to publish or grant access. The implementation must use the actual platform’s permission model and make any separate sharing action explicit.