docs(ess): implementation code comes from the specification; release 0.19.1 - #53
Merged
Merged
Conversation
- ess:specifying gains "Implementation code comes from the specification": implement behind `ess generate synthesize` output by filling the generated Behavior/Query obligations, commit the generated tree and hold it with a regenerate-and-diff check; never hand-transcribe entities, commands, events, errors or views - While synthesize refuses a specification: file the refusal on beyond10x/ess, and cross-check any hand-written model against the compiled IR field by field (names alone are not enough) - ess:testing-conformance: a green suite proves only the fields its expectations read, and an any_of guard gets one witness - Why: a hand-transcribed model passed a 669-scenario suite with every entity field unchecked Refs: task:ess-synthesized-implementation
- Workspace, all ten plugin manifests and the Skill version lines move to 0.19.1; CHANGELOG gains the 0.19.1 section. - task:ess-synthesized-implementation moves to implemented. task check: exit 0. agentplugins-check tools: exit 1, from the upstream drift 0.19.0 already recorded: aep 0.65.0 and ess 0.43.0 are newer than verified.json, and aep:planning spells `aep plan artifact divergences`, which aep 0.65.0 does not have. The commands the new ess sections spell pass against ess 0.43.0. verified.json does not move; no trial round was run.
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.
The ess skills now say where implementation code comes from:
ess generate synthesize, never a hand transcription.ess:specifying: new section "Implementation code comes from the specification" (fill the generated…Behavior/…Queryobligations, commit the generated tree, regenerate-and-diff in the gate; while synthesize refuses, file the gap and cross-check a hand-written model against the compiled IR field by field).ess:testing-conformance: a green suite proves only the fields its expectations read; one witness perany_of.task check: exit 0. agentplugins-check tools: exit 1 on the same three upstream problems 0.19.0 recorded; the new spellings pass against ess 0.43.0.