Repository navigation
Complete Workshop architecture-reset contracts - #33
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.
What changed
gnolith_status.semanticState.diagnosticv1 evidence and downstream fixturesWhy
The architecture reset requires one Workshop-owned data plane with truthful discovery, stable authorization semantics, secret-safe readiness evidence, and immutable downstream contracts. Final black-box review also showed that two singleton visibility clauses were being misread as OR, although canonical CNF makes clauses AND and atoms within each clause OR.
Impact
Downstreams receive one 52-tool catalog, a versioned status diagnostic envelope, stable validation for caller-hidden visibility policies, and assembled restart/search/audit coverage. No package is published or tagged by this PR.
Validation