docs: explain typed business decisions - #119
Draft
abrichr wants to merge 2 commits into
Draft
Conversation
abrichr
marked this pull request as draft
August 8, 2026 19:03
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.
Adds a dedicated typed business-decision concept and separates declared business choices from operational halt recovery across the runtime, Execute, OEM, qualification, and outcome documentation.\n\nThe remote contract is documented as an opaque task plus a separately reviewed presentation artifact. The Execute discriminator is documented as a target contract that depends on the pending Types and Cloud integration.\n\nValidation:\n- mkdocs build --strict\n- git diff --check