From 6c284742a7e3bd2fbd319b75a406e9ab5e6c42be Mon Sep 17 00:00:00 2001 From: Raghu Betina Date: Mon, 12 Oct 2026 05:28:44 -0500 Subject: [PATCH] Name a stubbed Policy rule in the first run 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 app-session 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 and the Drawing Board's notes do. A Chrome that cannot start is still a gap in the laptop's setup. Before the deploy no README lists a Policy, so the rule holds on both sides of it. --- workshop-kit/scripts/linux/app-instructions.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/workshop-kit/scripts/linux/app-instructions.md b/workshop-kit/scripts/linux/app-instructions.md index da261a6..79d139d 100644 --- a/workshop-kit/scripts/linux/app-instructions.md +++ b/workshop-kit/scripts/linux/app-instructions.md @@ -14,10 +14,11 @@ except on testing, where the app's `AGENTS.md` and README govern. ## Setup and specs - After Compile, set up the app, build its assets and run its specs as its README says, before the first preview. In that first run, a spec that fails through behavior the README's **Behavior to write** lists is work to do: - write that behavior until its specs pass. A stub raises `NotImplementedError`, and a deletion outcome First Draft - left out fails its spec with `RecordNotDestroyed`. If Chrome itself cannot start, this laptop's setup is missing - something; any other failure in that run is a First Draft defect. Either way, tell the user which spec failed and - its error. Never edit or delete a generated spec to make it pass. + write that behavior until its specs pass. A stubbed scope raises `NotImplementedError`, a stubbed Policy rule + returns `false`, and a deletion outcome First Draft left out fails its spec with `RecordNotDestroyed`. Write every + item that section lists, including a denying rule no failing spec names. If Chrome itself cannot start, this + laptop's setup is missing something; any other failure in that run is a First Draft defect. Either way, tell the + user which spec failed and its error. Never edit or delete a generated spec to make it pass. - System specs drive Chrome on this laptop directly; there is no Selenium container to start or stop. ## Web app