Repository navigation
Explain the verification loop and demonstrate failure-to-fix scoring - #1
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
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.
Explain why SStack verifies business outcomes before calling work done, and how failed checks return work to the engineer. Add a loop diagram, an illustrative portfolio allocation walkthrough, and a runnable synthetic failure/pass demonstration using the existing evaluation scorer.
The example keeps expected outcomes fixed and distinguishes scoring from independent live proof. It also explains fresh review after code changes, post-merge repairs, and current automation limits.
Validation: executed the embedded demo and matched both documented outputs; checked README links/text, shared lint/contracts, and the existing stack suite. No application or runtime code changed.