docs(sop): ground PROSE Expectations in SOPs#24
Merged
Conversation
Use Standard Operating Procedures (SOPs) as the contract base for the PROSE platform overview spec. - Update docs/specs/PROSE-platform-overview.md to explain that Expectations are derived from SOPs - Add SOP → PROSE → Tests workflow section - Add SOP basis column to the test-mapping table - Create docs/sops/ with 5 example SOPs (SOP-101 through SOP-202) - Update integration tests to reference their SOP basis
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uses Standard Operating Procedures (SOPs) as the contract base for the PROSE platform overview spec.
docs/specs/PROSE-platform-overview.mdto explain that Expectations are derived from SOPsdocs/sops/with 5 example SOPs (SOP-101 through SOP-202)Closes #67hv7i