Repository navigation
Name a stubbed Policy rule in the first run - #86
Merged
Merged
Conversation
The next First Draft deploy keeps a Policy the Compiler cannot lower as a stub. Its rule returns false, so the pages it guards deny every account, and its relation scope raises NotImplementedError. The README's Behavior to write lists each stub, and the generated AGENTS.md now names a denying rule beside a raising scope. A Policy used only as a gate has no scope, so its stub makes no generated spec fail. The workshop notes sent the agent to write only what a failing spec named, so it would leave such a rule unwritten and preview pages that deny every account. The Setup and specs bullet now names a stubbed Policy rule and says to write every item Behavior to write lists, including a denying rule no failing spec names, as the app's AGENTS.md does. Before the deploy no README lists a Policy, so the rule holds on both sides of it.
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.
From the next First Draft deploy, a Policy the Compiler cannot lower keeps its class and every surface it guards. Its rule returns
false, so those pages, links, and controls deny every account, and its relation scope raisesNotImplementedError, so pages that list or look up records through it raise. The generated README's Behavior to write lists each stub, and the generatedAGENTS.mdnow says:A Policy used only as a gate has no scope, so its stub makes no generated spec fail. The notes (from #84) told the agent to write only what a failing spec named, so it would leave such a rule unwritten and preview pages that deny every account.
This changes only the first bullet of Setup and specs in
.devcontainer/workshop/app-instructions.md: it names a stubbed scope, a stubbed Policy rule, and a left-out deletion, and says to write every item Behavior to write lists, including a denying rule no failing spec names. Everything else in the file is unchanged. Before the deploy no README lists a Policy, so the rule holds on both sides of it.Verified. The wording follows the
AGENTS.mdtemplate at servicemain4ff78c87. A Compile of the service's Policy stubs smoke Plan on that commit produced a README listing four stubs, and the smoke passed with five failures, each through a stubbed scope. The stubbedmoderategate, which denies every Report page, failed no spec.Not run: a Codespace, and an agent reading the notes.
Not for merging until the owner approves: merging changes what new workshop Codespaces get.
Docs: updated
.devcontainer/workshop/app-instructions.md(Setup and specs).Review: Codex (codex-review 0.8.0, max effort), session 67e4e102-6a01-4d30-8f38-8040dcd986a7, approve.