@cratis/pi 7.36.1 → 7.38.0

package/package/corpus/skills/cratis-screenplay-modeling-lifecycle/references/stop-or-assume.md

@@ -28,6 +28,35 @@ user can accept, and approvals not yet given always stop.
 - One closed outcome per run. A run that neither progressed nor closed is a failure to report:
   say what blocked it and which question would unblock it.
 
+## Durable question notes
+
+Record each open modeling choice as a `question` note on its element in committed
+`.screenplay/notes.json`, not only chat/STATE.md or `description` text. Include the
+question, consequence and assumption in use (or blocked scope). Keep its returned
+note ID and address in STATE.md/packets; before an element exists, anchor to the
+application or nearest identified container and name the intended element in text.
+Never put secrets or personal data in note text, authors, refs or resolutions.
+
+Read model-authoring [model notes](../../cratis-screenplay-model-authoring/references/model-notes.md)
+when recording or answering questions: discover tools, list with pinned notes
+revision, `propose-model-notes`, review `read-proposal view=notes`, then authorized
+`apply`. If the installed bundle lacks notes, report the capability gap and carry
+an explicit note request to the owner; do not pretend a chat/description is a note.
+
+Cite the project's own decisions with `refs: [{ "id": "D123" }]`. When D123 is
+the answer, resolve with `by: "external-decision"` and required
+`ref: { "id": "D123" }`, explanatory text and a team-role author. The URL is
+optional and never fetched. Realize a resolved question as a specification for
+behavior, a description for meaning, or a project-owned decision record for
+consequential policy. Resolving is not implementation; a known refusal still
+needs `then error` or `then denied`. Reopen when the evidence ceases to answer it.
+
+Question gating is separate from V1: standalone Screenplay 4.144.0 has
+`--open-questions fail`; Cratis CLI 3.53.1 does not. Read toolchain
+`references/versions.md` "Model notes gate" when a phase requires no open questions.
+Product evidence: Screenplay `v4.144.0:Documentation/screenplay/model-notes.md:12-77,93-121`,
+`decisions/0045-model-notes-sidecar.md:40-79` and the model-authoring source table.
+
 ## Question format (STATE.md, packets, edit requests)
 `Qn <declaration address>: <what is missing or contradictory, one sentence> - matters because
 <consequence> - <assumption in use | blocked scope>`. Write it so a reader who has not opened
@@ -58,5 +87,7 @@ given for a named target. Approval is not repeated for the same scope.
 
 ## Unblocking
 A scope leaves `blocked` only when its question is answered; record the answer as a decision in
-STATE.md and, when durable, in the model's fenced `documentation`. Re-blocking a blocked scope is a no-op.
+STATE.md with its note ID, resolve the question note by evidence, and realize the
+answer in the model or decision record. Settled rationale may also go in fenced
+`documentation`. Re-blocking a blocked scope is a no-op.
 Blocked delivery scopes are reported in the packet; the main session creates any issue.

package/package/corpus/skills/cratis-screenplay-modeling-lifecycle/references/worked-example.md

@@ -84,8 +84,11 @@ module Berths
   specification can state the exact rejection. No `BerthReassigned` event was added to carry it.
 - The `Cannot` line in the persona resolves to the `HarbourOffice` policy and a `then denied`
   specification whose caller fixture carries a non-matching role.
-- Assumption Q1 lives in the feature documentation and in STATE.md (Open questions) with its address,
-  `Berths.Allocation`.
+- On Screenplay 4.144.0, record Q1 as a `question` note on `Berths.Allocation`:
+  "Is allocation always manual? Assuming manual allocation; an automatic route
+  would need an automation." The documentation carries the working assumption;
+  STATE.md carries the returned note ID. Read `stop-or-assume.md` "Durable
+  question notes" when recording or resolving it.
 - The documentation is rationale only: the rules themselves are enforced by the constraint, the policy
   and the specifications, not by the prose.
 - The constraint does not say a berth holds one boat at a time: a berth source may replace its

package/package/corpus/skills/cratis-screenplay-modeling-lifecycle/verification.json

@@ -4,6 +4,11 @@
   "fixtures": [],
   "assertions": [
     { "kind": "play-compiles" },
+    { "kind": "skill-contains", "value": "record it as a `question` note anchored to the element" },
+    { "kind": "skill-contains", "value": "`refs: [{ \"id\": \"D123\" }]`", "file": "references/stop-or-assume.md" },
+    { "kind": "skill-contains", "value": "`by: \"external-decision\"`", "file": "references/stop-or-assume.md" },
+    { "kind": "skill-contains", "value": "Realize a resolved question as a specification", "file": "references/stop-or-assume.md" },
+    { "kind": "skill-contains", "value": "Never put secrets or personal data", "file": "references/stop-or-assume.md" },
     { "kind": "skill-contains", "value": "Model first" },
     { "kind": "skill-contains", "value": "`Outcome:`" },
     { "kind": "skill-contains", "value": "V3 binding-ready" },

package/package/corpus/skills/cratis-screenplay-toolchain/SKILL.md

@@ -206,6 +206,10 @@ reason; blocked verdicts list codes and keep the protection they blocked on.
 - [ ] Any new example fence compiles with the standalone tool; unmarked fences also pass
       `cratis screenplay validate --warnings-as-errors`.
 
+Read [model notes gate](references/versions.md#model-notes-gate) when checking
+unresolved questions: standalone 4.144.0 has `--open-questions fail`; Cratis CLI
+3.53.1 does not. It is separate from compilation and `--warnaserror`.
+
 ## Route near misses
 
 - What to model, phases, gates: `cratis-screenplay-modeling-lifecycle`.