@cratis/pi 7.31.0 → 7.32.0

package/package/corpus/skills/cratis-screenplay-command-surface/references/compliance.md

@@ -6,6 +6,7 @@
 ## Contents
 
 - Classify the value on its concept
+- Recover classification from C# with Arc 22.70.0
 - Declare the use separately
 - Identify the person, not the stream
 
@@ -63,6 +64,45 @@ This mapping is not admission: either marker, including qualifiers and scopes,
 still blocks executable binding with PLAY0268. Subject lineage is a different
 role, described below.
 
+## Recover classification from C# with Arc 22.70.0
+
+Reverse generation is not the C# provider mapping above. Source authority: Arc
+`v22.70.0:Documentation/backend/csharp/generating-a-screenplay.md` (Operational
+secrets), `Source/DotNET/Screenplay/Emission/Concepts/ConceptSyntaxBuilder.cs`
+and `Source/DotNET/Screenplay/Analysis/Types/PersonalDataMarkings.cs`.
+Check the generator package actually loaded; the CLI's bundle may be older.
+
+- Both `[Encrypted]` and `[NotAudited]` must be on the concept to recover
+  `secret`. Partial or member-specific markings report SP0058 (Information),
+  without adding `secret`; existing `pii` remains.
+- For `[Encrypted(EncryptionScope.Namespace)]` or Global plus `[NotAudited]`,
+  default output keeps bare `secret` and reports SP0061 (Information), naming
+  the unstated scope. It therefore implies Subject, not the source scope.
+  Set `ScreenplayOptions.AuthoringOnlyConstructs = true` (CLI adapter flag
+  `--authoring-only-constructs`) to state `secret scope namespace` or
+  `secret scope global` in the concept body. Subject stays implicit. Scope
+  is syntax-only: it raises no ESM version and grants no executable admission.
+  `pii secret` gets no scope because the providers ignore it.
+- A property or positional constructor parameter marked `[PII]` on a non-concept
+  type reports SP0062 (Information); the marking is not stated and no concept
+  is invented. Preserve the source protection, record the loss, and introduce a
+  personal-data concept in source or the intentional candidate.
+- Member `[PII]` promotes an existing concept to `pii` across all its uses.
+  SP0063 (Information) lists unmarked analyzed uses when the concept itself
+  lacks `[PII]`. Review that widening: explicitly classify the concept if the
+  meaning is shared, or separate personal and nonpersonal meanings into distinct
+  concepts. No SP0063 is reported if the concept is marked or all analyzed uses
+  are marked. Never remove protection merely to silence the diagnostic.
+- Protected identity concepts keep their identities/routes but lose their
+  annotations with SP0059 (Information, now worded `pii/secret`); record the
+  protection loss and use a surrogate identity, not a declassified payload value.
+
+Reasons, special/criminal qualifiers and purposes are not inferred. Changing
+scope for persisted events still needs a new generation. Every diagnostic is a
+loss or review item, including Information; see legacy-extraction
+[generate notes](../../cratis-screenplay-legacy-extraction/references/generate-notes.md)
+for the self-check contract and compiler-upgrade handling.
+
 ## Declare the use separately
 
 ```screenplay

package/package/corpus/skills/cratis-screenplay-legacy-extraction/SKILL.md

@@ -41,6 +41,7 @@ v19.32.0): `cratis-screenplay-toolchain` `references/versions.md`. Checked at th
 | --- | --- |
 | `generate` options, no default-file certainty (stdout when `--file` is absent), spec-project exclusion by name, `CLI0005/0009/0014-0017` | cli `v3.28.2:Source/Cli/Commands/Screenplay/{GenerateScreenplayCommand,GenerateScreenplaySettings,ScreenplayProjectSelection,ScreenplayDiagnosticCodes}.cs` |
 | `SP0016` (rule in code, computed message, `When`/`Unless` written as unconditional), `SP0024` (source did not compile) | Arc `v22.50.5:Source/DotNET/Screenplay/ScreenplayDiagnosticCodes.cs`, `Documentation/backend/csharp/generating-a-screenplay.md` |
+| Non-default secret scope in authoring mode, SP0061–SP0063, self-check contract on compiler upgrades | Arc `v22.70.0:Documentation/backend/csharp/generating-a-screenplay.md`, `Source/DotNET/Screenplay/Verification/ExpectedBindingDiagnostics.cs`; `references/generate-notes.md` |
 | `prologue start` is an interactive wizard that writes `cratis-prologue.json`; `interpret` resolves its language model from the Prologue file, then the global CLI configuration (cli#241 open) | cli `v3.28.2:Source/Cli/Commands/Prologue/{StartPrologueCommand,LlmOptionsResolver}.cs`, `Documentation/reference/prologue.md` |
 | Extractor effects (CDC enable, publication and replication slot), POST/PUT/DELETE only, 2 s correlation window, interpret payload (uncapped model outline and names, observed lists capped at 50, schema tables capped per schema observation), existing slot/publication reused; cleanup missing (Prologue#37) | Prologue `ad4bbe7:Source/Extractor/Sources/**`, `Source/Configuration/*`, `Source/Interpretation/EvidenceFormatter.cs` |
 | `then error`, `then denied`, `unique ... released by` | Screenplay `v4.66.0:Documentation/screenplay/{specifications,constraints}.md` |
@@ -154,8 +155,9 @@ chain per slice before handoff (evidence template); never manufacture references
      `unique ... on <every event that sets it>` with `released by`
      (`references/rule-modeling.md`);
    - preserve personal-data/secret protection and authorization found in code,
-     using bare `pii` / `secret` (4.127.0); deprecated marker repairs keep legal
-     notes intact, never guess a purpose or basis. Derive purpose/use/retention
+     using `pii` / `secret` and evidenced secret scope; Arc 22.70.0 recovery
+     losses (SP0061–SP0063) need review (`references/generate-notes.md`).
+     Deprecated marker repairs keep legal notes intact, never guess a purpose or basis. Derive purpose/use/retention
      declarations only from evidence or expert decisions; run `--check purposes`
      and inspect the processing record as prompts, not a legal verdict. Keep
      hand-joined legacy ids scalar; never infer composite parts by splitting text.

package/package/corpus/skills/cratis-screenplay-legacy-extraction/references/generate-notes.md

@@ -7,6 +7,8 @@
 - Coverage (what a provider reads)
 - Diagnostics are the loss list
 - Arc recovery and authoring-only options
+- Arc 22.70.0 compliance recovery
+- Generated-document self-check on compiler upgrades
 - Reading the output cheaply
 
 Flags verified with `cratis screenplay generate --help` on the version recorded in
@@ -17,9 +19,16 @@ cratis-screenplay-toolchain `references/versions.md`; behaviour from the cratis
 Screenplay.CritterStack `v0.24.0`. Version-specific capability facts belong in cratis-screenplay-toolchain
 `references/versions.md`.
 
-Current CLI is 3.50.0, with Screenplay 4.131.0 / Stage 4.67.0 /
-Arc.Screenplay 22.54.0 / Chronicle 19.32.0 / Fundamentals 7.22.8
-(`references/versions.md` in the toolchain; standalone Screenplay is 4.135.0).
+For the current standalone compiler and CLI bundle, use the toolchain's
+[version table](../../cratis-screenplay-toolchain/references/versions.md).
+The compliance and self-check sections below are source-checked at Arc 22.70.0
+(`Documentation/backend/csharp/generating-a-screenplay.md`,
+`Analysis/Types/{ConceptRegistry,PersonalDataMarkings,TypesTheDocumentCannotName}.cs`,
+`Emission/Concepts/ConceptSyntaxBuilder.cs`, `Emission/ProtectedIdentityAnnotations.cs`
+and `Verification/ExpectedBindingDiagnostics.cs` under `Source/DotNET/Screenplay/`).
+They require that generator release, not an older bundled adapter;
+a standalone compiler upgrade does not upgrade the generator.
+
 Option/admission evidence checked at CLI 3.41.0: released
 `GenerateScreenplaySettings.cs`, `ArcScreenplayGeneration.cs`, v7 planning specs
 and `Documentation/reference/screenplay.md`; older diagnostic probes below keep
@@ -107,6 +116,65 @@ Handler/reaction bodies, unresolved conditions and unproven origins still need
 source review. Do not infer generation/evolution/absence-assertion coverage from
 a package upgrade; read diagnostics and reconcile each recovered scenario.
 
+## Arc 22.70.0 compliance recovery
+
+A concept with both `[Encrypted]` and `[NotAudited]` becomes `secret`.
+Encryption or audit suppression alone, or only on a member, does not establish
+that concept-wide contract: SP0058 (Information) reports the partial marking
+without adding `secret`; an existing `pii` classification remains.
+
+- Subject scope, omitted or explicit, stays bare `secret`.
+- `[Encrypted(EncryptionScope.Namespace)]` plus `[NotAudited]` on the concept
+  emits bare `secret` by default and SP0061 (Information) names the unstated
+  `namespace` scope: the document instead implies Subject scope. Global behaves
+  the same way. Set `ScreenplayOptions.AuthoringOnlyConstructs = true` (CLI
+  adapter option `--authoring-only-constructs`) to emit `secret scope namespace`
+  or `secret scope global` in the concept body. Scope is syntax-only and does
+  not raise the ESM version; it does not make protected concepts executable.
+- A concept also marked `[PII]` becomes `pii secret`, with no emitted scope:
+  the C# providers render only `[PII]`; Chronicle rejects `[PII]` combined with
+  `[Encrypted]`. Do not add a scope the provider ignores.
+
+Member `[PII]` is read from properties and matching positional constructor
+parameters. Two losses that previously needed manual detection now have
+Information diagnostics:
+
+| Code | What the document says or loses | Resolve in source or the intentional candidate |
+| --- | --- | --- |
+| SP0062 | `[PII]` on a non-concept member (for example, a String) is not stated; the diagnostic names `Type.Member`. No concept is invented. | Introduce a personal-data concept with evidence-backed meaning; keep the original protection and record the lost marking until resolved. |
+| SP0063 | A member marking promotes its concept to `pii` everywhere; the diagnostic lists unmarked analyzed uses that acquire that classification. | Review every listed use. If all carry personal data, make the concept-wide classification explicit; if meanings differ, separate the concepts rather than remove `pii`. |
+
+SP0063 is absent when the concept itself has `[PII]` or every analyzed use is
+marked. Its list covers analyzed uses, not proof of all runtime use sites.
+Reasons, special/criminal qualifiers and processing purposes are not inferred.
+
+SP0059 (Information) reports that an identity concept's `pii/secret` annotations
+were left off because Screenplay rejects protected identifiers, destinations and
+stream ids (PLAY0515). The identity/route is retained, not the protection. Record
+that loss and design a surrogate identity; never treat the generated omission as
+authority to remove source protection. SP0058/SP0059 now say `secret` and
+`pii/secret`, not the deprecated `sensitive`/`@pii` vocabulary.
+See command-surface [compliance](../../cratis-screenplay-command-surface/references/compliance.md)
+for classification and persisted-event scope changes.
+
+## Generated-document self-check on compiler upgrades
+
+Arc compiles and binds its printed document. `ExpectedBindingDiagnostics` tolerates
+only exact known admission-limit messages (PLAY0268) and the permitted legacy
+consistency messages (PLAY0271), not every diagnostic with those codes.
+The loaded compiler's contract must list the code as neither retired nor reserved
+and include Error among its supported severities. A missing, retired, reserved or
+non-error-only code loses the exemption even if an old message still matches.
+Changed or unknown messages also fail closed.
+
+After upgrading Screenplay, rerun generation and inspect the self-check instead
+of carrying forward an old waiver. Unexpected binding errors become SP0056
+(Warning for standalone generation, Information for embedded generation); Arc's
+end-to-end gate rejects any SP0056 regardless of severity. Resolve a changed
+admission contract or report a generator defect; do not strip protection or widen
+the exemption. This check is distinct from a clean source-validation result and
+does not prove the model renders or executes.
+
 ## Reading the output cheaply
 1. V1 on `.ai-work/screenplay/<model-slug>/legacy/static` (folder mode) with the tool and
    command `cratis-screenplay-toolchain` selects, named with its version; record counts, do

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cratis/pi",
-  "version": "7.31.0",
+  "version": "7.32.0",
   "description": "Configuration-aware Cratis AI integration for Pi",
   "type": "module",
   "files": [