IMP-076: Explain contract execution, evaluation and returned results - #19
Merged
Merged
Conversation
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.
Updates the documentation introduction and authoring guide. Defines executor/evaluator, result including evidence, assessment and out/error while mapping them to existing function/responsibility interfaces.
Part of IMP-076, following the agreed language: “Contract authoring is expressing intent by composing requirements.”
This PR builds on the merged IMP-063 terminology changes. The coordinated canonical definitions live in openprose-language #3; merge it with or before dependent explanations. Historical evidence and versioned identifiers retain their original wording. Intent capture and contract-adequacy tooling remain deferred under IMP-078.
Validation: pnpm check (typecheck, lint, spelling), 93 tests, deterministic Next build and 28 internal-link checks passed. All 42 standalone preview smoke checks passed. No model-backed prebuild or deployment.
Complete PR matrix, validation and integration order.