@wildo-ai/framework-knowledge 1.1.13 → 1.1.15

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (133) hide show
  1. package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
  2. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
  3. package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +12 -4
  4. package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +4 -0
  5. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  6. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  7. package/dist/esm/framework-knowledge.definitions.js +9 -0
  8. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  9. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  10. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
  11. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +1 -1
  13. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +1 -1
  14. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
  15. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  16. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  17. package/dist/knowledge/manifest.json +7 -7
  18. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +7 -0
  19. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +2 -2
  20. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +27 -10
  21. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +1 -1
  22. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +13 -9
  23. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +1 -1
  24. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +6 -0
  25. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +1 -1
  26. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +20 -5
  27. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +2 -2
  28. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +15 -2
  29. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  30. package/dist/knowledge/references/build-plan.task-graph.config.md +12 -8
  31. package/dist/knowledge/references/engine.client-bundle.allow-list.md +6 -0
  32. package/dist/knowledge/references/example.backend.addon-wiring.module.md +5 -1
  33. package/dist/knowledge/references/example.backend.custom-operation.declared-refusal-code.md +6 -0
  34. package/dist/knowledge/references/example.config.navigation.full.md +14 -0
  35. package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +6 -2
  36. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +13 -2
  37. package/dist/knowledge/references/example.inbound.email-to-todo.md +33 -2
  38. package/dist/knowledge/references/example.module.relationships.discriminator.md +7 -1
  39. package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +1 -1
  40. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +8 -2
  41. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +2 -0
  42. package/dist/knowledge/references/integration-plan.config.md +78 -8
  43. package/dist/knowledge/references/platform.config.environment.deployment.md +84 -5
  44. package/dist/knowledge/references/saas.backend.custom-operation.hook-transaction-posture.md +12 -1
  45. package/dist/knowledge/references/saas.backend.domain-module.md +15 -0
  46. package/dist/knowledge/references/saas.backend.flows-actors.a2a-agent-card.md +43 -11
  47. package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +17 -11
  48. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +11 -0
  49. package/dist/knowledge/references/saas.backend.system-access-service.md +30 -1
  50. package/dist/knowledge/references/saas.frontend.app-shell.shell-motion-contract.md +30 -0
  51. package/dist/knowledge/references/saas.frontend.electronic-signatures.embedded-signing-frame.md +46 -0
  52. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +24 -33
  53. package/dist/knowledge/references/saas.models.flows-actors.mcp-server-declaration.md +63 -0
  54. package/dist/knowledge/references/saas.models.flows-actors.outbound-credential.md +61 -0
  55. package/dist/knowledge/references/saas.models.flows-actors.remote-agent-declaration.md +56 -0
  56. package/dist/knowledge/references/saas.models.frontend-provider-public-config-contract.md +6 -0
  57. package/dist/knowledge/references/saas.models.http-api-binding.md +51 -0
  58. package/dist/knowledge/references/saas.models.privacy.data-residency.md +188 -31
  59. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +7 -0
  60. package/dist/knowledge/references/saas.models.provider-capabilities.md +11 -0
  61. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +9 -0
  62. package/dist/knowledge/references/saas.models.resource-config.operation-condition-parameters.md +8 -1
  63. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +30 -0
  64. package/dist/knowledge/references/saas.rag.retrieval-scores.md +4 -2
  65. package/dist/knowledge/references/saas.specifications.processor-register.md +10 -0
  66. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  67. package/dist/knowledge/registries/framework-topics.json +45 -1
  68. package/dist/knowledge/registries/playbooks.json +2 -2
  69. package/dist/knowledge/registries/source-tags.json +1175 -1107
  70. package/dist/knowledge/skills/INDEX.md +2 -2
  71. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +9 -2
  72. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +15 -0
  73. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +3 -1
  74. package/dist/knowledge/skills/backend-custom-operation/references/declared-refusal-codes.md +28 -1
  75. package/dist/knowledge/skills/backend-custom-operation/references/framework-hook-transaction-posture-api.md +21 -1
  76. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +15 -2
  77. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +16 -0
  78. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +197 -31
  79. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +7 -0
  80. package/dist/knowledge/skills/config-app-shell/references/framework-shell-layout-api.md +30 -0
  81. package/dist/knowledge/skills/config-navigation/SKILL.md +14 -0
  82. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +19 -0
  83. package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +1 -0
  84. package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +15 -1
  85. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +11 -0
  86. package/dist/knowledge/skills/electronic-signature-deliverables/SKILL.md +12 -5
  87. package/dist/knowledge/skills/electronic-signature-deliverables/references/signing-inside-the-application.md +113 -0
  88. package/dist/knowledge/skills/email-add-template/SKILL.md +3 -2
  89. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +8 -4
  90. package/dist/knowledge/skills/email-definition-wiring/SKILL.md +1 -1
  91. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +29 -7
  92. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +66 -26
  93. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +6 -2
  94. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +34 -3
  95. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +13 -2
  96. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +11 -0
  97. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +15 -0
  98. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-mcp-server-declaration-api.md +139 -0
  99. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-remote-a2a-agent-declaration-api.md +169 -0
  100. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +24 -33
  101. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +33 -2
  102. package/dist/knowledge/skills/infra-environment-config/SKILL.md +39 -13
  103. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +84 -5
  104. package/dist/knowledge/skills/layout-2d-adoption/references/framework-shell-motion-api.md +30 -0
  105. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +26 -0
  106. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +15 -0
  107. package/dist/knowledge/skills/module-relationships/SKILL.md +20 -1
  108. package/dist/knowledge/skills/provider-backend-package/SKILL.md +13 -2
  109. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +2 -0
  110. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-public-config-api.md +6 -0
  111. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +3 -0
  112. package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +4 -1
  113. package/dist/knowledge/skills/resource-add-module/SKILL.md +8 -2
  114. package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +17 -0
  115. package/dist/knowledge/skills/resource-chat-commands/SKILL.md +1 -1
  116. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +6 -2
  117. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +4 -3
  118. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +30 -1
  119. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +51 -0
  120. package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +14 -5
  121. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +30 -0
  122. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-client-registration-postures.md +5 -0
  123. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +4 -2
  124. package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +3 -2
  125. package/dist/knowledge/skills/resource-status-lifecycle/references/framework-operation-condition-parameters-api.md +8 -1
  126. package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +3 -3
  127. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +8 -2
  128. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +5 -1
  129. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +6 -0
  130. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +6 -0
  131. package/dist/knowledge/topic-index.json +326 -179
  132. package/dist/tsconfig.build.tsbuildinfo +1 -1
  133. package/package.json +4 -4
@@ -93,20 +93,35 @@ places and whether it is inside.
93
93
  *
94
94
  * Opt-in. Absent means the application states no residency and nothing is refused, which is not the same as "anywhere":
95
95
  * the documents then say no residency is declared.
96
+ *
97
+ * ## A second, weaker promise: stored at rest (`storedAtRestTerritories`, #2294, decided by Paul 2026-11-15)
98
+ *
99
+ * Most SaaS vendors' "data residency" keeps data AT REST in a region while processing it elsewhere (Notion, Slack,
100
+ * Atlassian, Sentry…), so `territories` refuses them. `storedAtRestTerritories` admits such a vendor when every place its
101
+ * chosen region keeps data at rest (`storageRegionTerritories` on its profile) lies inside it. It is a separate field and
102
+ * never a looser reading of `territories`: a storage-only vendor is never INSIDE the processing residency, its entry says
103
+ * `inside-at-rest`, and the documents state that weaker promise for it by name. Opt-in: absent, nothing changes.
96
104
  */
97
105
  export const ApplicationDataResidencySchema = z
98
106
  .strictObject({
99
107
  /** The places the data may be stored and processed in. A vendor region counts as inside when every place it covers is inside one of these. */
100
- territories: z.array(JurisdictionSlugSchema).min(1),
108
+ territories: z.array(JurisdictionSlugSchema).min(1)
109
+ .describe('The places the data may be stored and processed in, as jurisdiction slugs (`eu`, `de`, `ch`, `us`; the EEA is `eu`, `is`, `li` and `no`). A vendor region counts as inside when every place it covers is inside one of these.'),
110
+ /** The places a vendor may keep the data AT REST in while processing it elsewhere (opt-in, the weaker promise). */
111
+ storedAtRestTerritories: z.array(JurisdictionSlugSchema).min(1).optional()
112
+ .describe('Opt-in, the weaker promise: the places a vendor that processes elsewhere may keep the data at rest in. A vendor whose chosen region processes outside `territories` is admitted when every place that region stores data at rest lies inside one of these, and the documents say so for it. Absent: no vendor is admitted on storage alone.'),
101
113
  })
102
114
  .superRefine((residency, context) => {
103
- const duplicates = residency.territories.filter((territory, index) => residency.territories.indexOf(territory) !== index);
104
- if (duplicates.length > 0) {
105
- context.addIssue({
106
- code: 'custom',
107
- path: ['territories'],
108
- message: `data residency territory ${[...new Set(duplicates)].map((slug) => `"${slug}"`).join(', ')} is declared more than once`,
109
- });
115
+ for (const field of ['territories', 'storedAtRestTerritories'] as const) {
116
+ const listed = residency[field] ?? [];
117
+ const duplicates = listed.filter((territory, index) => listed.indexOf(territory) !== index);
118
+ if (duplicates.length > 0) {
119
+ context.addIssue({
120
+ code: 'custom',
121
+ path: [field],
122
+ message: `data residency territory ${[...new Set(duplicates)].map((slug) => `"${slug}"`).join(', ')} is declared more than once`,
123
+ });
124
+ }
110
125
  }
111
126
  });
112
127
  export type ApplicationDataResidency = z.infer<typeof ApplicationDataResidencySchema>;
@@ -148,8 +163,20 @@ export function organizationDataResidencyRefusal(
148
163
  + 'narrow: nothing has placed its providers in named places. Declare the application\'s residency first.';
149
164
  }
150
165
  const outside = organization.territories.filter((territory) => !application.territories.some((resident) => jurisdictionReachCovers(resident, territory)));
151
- if (outside.length === 0) return null;
152
- return `The organization's data residency names ${outside.join(', ')}, outside the application's (${application.territories.join(', ')}). `
166
+ if (outside.length > 0) {
167
+ return `The organization's data residency names ${outside.join(', ')}, outside the application's (${application.territories.join(', ')}). `
168
+ + 'An organization can only narrow the application\'s residency: name places inside it.';
169
+ }
170
+ // The weaker promise narrows the same way, and only where the application made it (#2294).
171
+ if (organization.storedAtRestTerritories === undefined) return null;
172
+ if (application.storedAtRestTerritories === undefined) {
173
+ return 'The organization admits vendors on storage at rest (storedAtRestTerritories), and the application does not: an organization '
174
+ + 'can only narrow the application\'s residency. Remove storedAtRestTerritories, or declare it on the application first.';
175
+ }
176
+ const appStored = application.storedAtRestTerritories;
177
+ const storedOutside = organization.storedAtRestTerritories.filter((territory) => !appStored.some((resident) => jurisdictionReachCovers(resident, territory)));
178
+ if (storedOutside.length === 0) return null;
179
+ return `The organization's at-rest residency names ${storedOutside.join(', ')}, outside the application's (${appStored.join(', ')}). `
153
180
  + 'An organization can only narrow the application\'s residency: name places inside it.';
154
181
  }
155
182
 
@@ -203,6 +230,40 @@ export function effectiveDataResidencyTerritories(
203
230
  }
204
231
  return [...kept].sort((left, right) => left.localeCompare(right));
205
232
  }
233
+
234
+ /**
235
+ * The residency a call for an organization must satisfy, both promises narrowed (#2294): the processing territories as
236
+ * {@link effectiveDataResidencyTerritories} computes them, and the at-rest ones the same way when BOTH residencies make
237
+ * that promise. An organization that does not admit storage-only vendors narrows the application's admission away; an
238
+ * application that does not, has nothing for an organization to narrow. `undefined` when the organization declares none.
239
+ */
240
+ export function effectiveDataResidency(
241
+ application: ApplicationDataResidency | undefined,
242
+ organization: OrganizationDataResidency | null | undefined,
243
+ ): ApplicationDataResidency | undefined {
244
+ const territories = effectiveDataResidencyTerritories(application, organization);
245
+ if (territories === undefined) return undefined;
246
+ const storedAtRestTerritories = organization?.storedAtRestTerritories === undefined
247
+ ? undefined
248
+ : application === undefined
249
+ ? [...organization.storedAtRestTerritories]
250
+ : application.storedAtRestTerritories === undefined
251
+ ? undefined
252
+ : narrowedTerritories(application.storedAtRestTerritories, organization.storedAtRestTerritories);
253
+ return { territories: [...territories], ...(storedAtRestTerritories === undefined ? {} : { storedAtRestTerritories }) };
254
+ }
255
+
256
+ /** Every place both lists contain, as the narrower of each pair; sorted. */
257
+ function narrowedTerritories(wider: readonly string[], narrower: readonly string[]): string[] {
258
+ const kept = new Set<string>();
259
+ for (const territory of narrower) {
260
+ for (const resident of wider) {
261
+ if (jurisdictionReachCovers(resident, territory)) kept.add(territory);
262
+ else if (jurisdictionReachCovers(territory, resident)) kept.add(resident);
263
+ }
264
+ }
265
+ return [...kept].sort((left, right) => left.localeCompare(right));
266
+ }
206
267
  ```
207
268
 
208
269
  ### Origin Package: `@wildo-ai/saas-models`
@@ -215,6 +276,12 @@ export function effectiveDataResidencyTerritories(
215
276
  export enum ProviderDataResidencyStatus {
216
277
  /** Every place the chosen region processes in lies inside the residency. */
217
278
  INSIDE = 'inside',
279
+ /**
280
+ * The weaker promise (`storedAtRestTerritories`, opt-in): the chosen region processes outside the residency, or nothing
281
+ * says where it processes, and every place it keeps data AT REST lies inside the at-rest territories. Admitted, and
282
+ * never INSIDE: the documents say the vendor stores the data in the region and processes it elsewhere.
283
+ */
284
+ INSIDE_AT_REST = 'inside-at-rest',
218
285
  /** The chosen region processes in at least one place outside the residency. */
219
286
  OUTSIDE = 'outside',
220
287
  /** The profile does not state which places the chosen region covers (a global region, or a map not yet researched). */
@@ -286,9 +353,30 @@ export interface ProviderDataResidencyEntry {
286
353
  readonly territories: readonly string[] | null;
287
354
  /** The places outside the residency, for {@link ProviderDataResidencyStatus.OUTSIDE}; empty otherwise. */
288
355
  readonly outsideTerritories: readonly string[];
356
+ /** The places the region keeps data at rest in, for {@link ProviderDataResidencyStatus.INSIDE_AT_REST}; `null` otherwise. */
357
+ readonly storageTerritories?: readonly string[] | null;
358
+ /**
359
+ * The account condition {@link storageTerritories} holds on (#3920), for {@link ProviderDataResidencyStatus.INSIDE_AT_REST}:
360
+ * what the operator attested by choosing the region. `null` when the map holds on the choice alone.
361
+ */
362
+ readonly storageCondition?: string | null;
289
363
  readonly status: ProviderDataResidencyStatus;
290
364
  }
291
365
 
366
+ /**
367
+ * Whether a provider at this status may be used under the residency (#2294): INSIDE, or INSIDE_AT_REST, the weaker promise
368
+ * the application opted into. Every admission site reads this, so a status added later is refused until it is placed here.
369
+ *
370
+ * A type guard, so a caller that returns early on an admitted status keeps an exhaustive switch over the rest (the
371
+ * placement below does): a plain boolean would leave INSIDE and INSIDE_AT_REST in the switch's type, which a strict
372
+ * program reports as a missing return.
373
+ */
374
+ export function providerDataResidencyAdmits(
375
+ status: ProviderDataResidencyStatus,
376
+ ): status is ProviderDataResidencyStatus.INSIDE | ProviderDataResidencyStatus.INSIDE_AT_REST {
377
+ return status === ProviderDataResidencyStatus.INSIDE || status === ProviderDataResidencyStatus.INSIDE_AT_REST;
378
+ }
379
+
292
380
  /** What the residency reads of a provider choice: who runs it, and in which region. */
293
381
  export type ProviderDataResidencyChoice = Pick<ApplicationProviderComplianceChoice, 'deploymentModel' | 'processingRegion'>;
294
382
 
@@ -358,6 +446,8 @@ function providerDataResidencyEntryOf(input: {
358
446
  processingRegion: choice.processingRegion,
359
447
  profileEstablished: established !== null,
360
448
  regionTerritories: established?.processingRegionTerritories?.[choice.processingRegion] ?? null,
449
+ regionStorageTerritories: established?.storageRegionTerritories?.[choice.processingRegion] ?? null,
450
+ regionStorageCondition: established?.storageRegionConditions?.[choice.processingRegion] ?? null,
361
451
  residency,
362
452
  });
363
453
  }
@@ -368,21 +458,37 @@ function vendorRegionDataResidencyEntry(input: {
368
458
  readonly processingRegion: string;
369
459
  readonly profileEstablished: boolean;
370
460
  readonly regionTerritories: readonly string[] | null;
461
+ readonly regionStorageTerritories: readonly string[] | null;
462
+ readonly regionStorageCondition: string | null;
371
463
  readonly residency: ApplicationDataResidency;
372
464
  }): ProviderDataResidencyEntry {
373
465
  const base = { providerRef: input.providerRef, processingRegion: input.processingRegion };
374
466
  if (!input.profileEstablished) {
375
467
  return { ...base, territories: null, outsideTerritories: [], status: ProviderDataResidencyStatus.NO_ESTABLISHED_PROFILE };
376
468
  }
377
- if (input.regionTerritories === null) {
378
- return { ...base, territories: null, outsideTerritories: [], status: ProviderDataResidencyStatus.TERRITORY_UNKNOWN };
379
- }
380
- const outsideTerritories = territoriesOutsideDataResidency(input.regionTerritories, input.residency);
469
+ const processing: ProviderDataResidencyEntry = input.regionTerritories === null
470
+ ? { ...base, territories: null, outsideTerritories: [], status: ProviderDataResidencyStatus.TERRITORY_UNKNOWN }
471
+ : (() => {
472
+ const outsideTerritories = territoriesOutsideDataResidency(input.regionTerritories, input.residency);
473
+ return {
474
+ ...base,
475
+ territories: [...input.regionTerritories],
476
+ outsideTerritories,
477
+ status: outsideTerritories.length === 0 ? ProviderDataResidencyStatus.INSIDE : ProviderDataResidencyStatus.OUTSIDE,
478
+ };
479
+ })();
480
+ // The processing promise first, always: a region inside it is INSIDE whatever it stores. The weaker one is asked only
481
+ // of a region the processing promise refuses, and only when the application opted into it (#2294).
482
+ if (processing.status === ProviderDataResidencyStatus.INSIDE) return processing;
483
+ const atRest = input.residency.storedAtRestTerritories;
484
+ if (atRest === undefined || input.regionStorageTerritories === null) return processing;
485
+ const storedOutside = input.regionStorageTerritories.filter((territory) => !atRest.some((resident) => jurisdictionReachCovers(resident, territory)));
486
+ if (storedOutside.length > 0) return processing;
381
487
  return {
382
- ...base,
383
- territories: [...input.regionTerritories],
384
- outsideTerritories,
385
- status: outsideTerritories.length === 0 ? ProviderDataResidencyStatus.INSIDE : ProviderDataResidencyStatus.OUTSIDE,
488
+ ...processing,
489
+ storageTerritories: [...input.regionStorageTerritories],
490
+ storageCondition: input.regionStorageCondition,
491
+ status: ProviderDataResidencyStatus.INSIDE_AT_REST,
386
492
  };
387
493
  }
388
494
 
@@ -403,6 +509,8 @@ export function dataResidencyEntriesOf(
403
509
  processingRegion: entry.choice.processingRegion!,
404
510
  profileEstablished: entry.offered !== null,
405
511
  regionTerritories: entry.regionTerritories,
512
+ regionStorageTerritories: entry.regionStorageTerritories,
513
+ regionStorageCondition: entry.regionStorageCondition,
406
514
  residency,
407
515
  }));
408
516
  }
@@ -448,6 +556,13 @@ export interface ProviderDataResidencyPlacement {
448
556
  readonly outcome: ProviderDataResidencyPlacementOutcome;
449
557
  /** The provider's vendor regions whose stated places all lie inside the residency, in the profile's order. */
450
558
  readonly regionsInside: readonly string[];
559
+ /**
560
+ * The vendor regions admitted only on the weaker promise (#3876): every place the region keeps data at rest lies inside
561
+ * the residency's `storedAtRestTerritories`, while it processes elsewhere. Empty when the residency declares no at-rest
562
+ * list, and never a region already in {@link regionsInside}. Read only when no region processes inside: a placement
563
+ * offers the stronger promise first.
564
+ */
565
+ readonly regionsInsideAtRest: readonly string[];
451
566
  /** The choice to write, for {@link ProviderDataResidencyPlacementOutcome.DERIVED} only. */
452
567
  readonly derivedChoice?: { readonly deploymentModel: ProviderDeploymentModel.VENDOR_HOSTED; readonly processingRegion: string };
453
568
  }
@@ -462,10 +577,16 @@ export interface ProviderDataResidencyPlacement {
462
577
  * Derived only when the residency leaves no choice: the provider is only offered vendor-hosted, exactly one of its
463
578
  * regions processes wholly inside, and no authored choice names a region. Everything else is a decision, and is
464
579
  * returned with the regions that would satisfy the residency so whoever takes it sees the options.
580
+ *
581
+ * When the application also declares an at-rest residency (#3876), a provider with NO region processing inside is placed
582
+ * on the weaker promise instead: derived when exactly one of its regions keeps everything at rest inside
583
+ * `storedAtRestTerritories`, a choice when several do. A region that processes inside always wins, because it keeps the
584
+ * stronger promise; a placement never trades it for a storage-only one.
465
585
  */
466
586
  export function placeProvidersInsideDataResidency(params: Parameters<typeof assessProviderProcessingAgainstDataResidency>[0]): readonly ProviderDataResidencyPlacement[] {
467
587
  return assessProviderProcessingAgainstDataResidency(params).flatMap((assessment): ProviderDataResidencyPlacement[] => {
468
- if (assessment.status === ProviderDataResidencyStatus.INSIDE) return [];
588
+ // An admitted provider needs no placement; an INSIDE_AT_REST one is admitted on the weaker promise the application made.
589
+ if (providerDataResidencyAdmits(assessment.status)) return [];
469
590
  const profile = Object.hasOwn(params.profilesByProviderRef, assessment.providerRef) ? params.profilesByProviderRef[assessment.providerRef] : undefined;
470
591
  const established = establishedProviderComplianceProfile(profile);
471
592
  const regionsInside = established === null
@@ -474,8 +595,15 @@ export function placeProvidersInsideDataResidency(params: Parameters<typeof asse
474
595
  const territories = established.processingRegionTerritories?.[region];
475
596
  return territories !== undefined && territoriesOutsideDataResidency(territories, params.residency).length === 0;
476
597
  });
598
+ const atRest = params.residency.storedAtRestTerritories;
599
+ const regionsInsideAtRest = established === null || atRest === undefined
600
+ ? []
601
+ : established.processingRegions.filter((region) => {
602
+ const stored = established.storageRegionTerritories?.[region];
603
+ return !regionsInside.includes(region) && stored !== undefined && territoriesOutsideDataResidency(stored, { territories: atRest }).length === 0;
604
+ });
477
605
  const placement = (outcome: ProviderDataResidencyPlacementOutcome): ProviderDataResidencyPlacement[] => [
478
- { providerRef: assessment.providerRef, assessment, outcome, regionsInside },
606
+ { providerRef: assessment.providerRef, assessment, outcome, regionsInside, regionsInsideAtRest },
479
607
  ];
480
608
  switch (assessment.status) {
481
609
  case ProviderDataResidencyStatus.NO_ESTABLISHED_PROFILE:
@@ -494,14 +622,17 @@ export function placeProvidersInsideDataResidency(params: Parameters<typeof asse
494
622
  if (assessment.status === ProviderDataResidencyStatus.NO_CHOICE && established.deploymentModels.includes(ProviderDeploymentModel.SELF_HOSTED)) {
495
623
  return placement(ProviderDataResidencyPlacementOutcome.DEPLOYMENT_MODEL_IS_A_CHOICE);
496
624
  }
497
- if (regionsInside.length === 0) return placement(ProviderDataResidencyPlacementOutcome.NO_REGION_INSIDE);
498
- if (regionsInside.length > 1) return placement(ProviderDataResidencyPlacementOutcome.SEVERAL_REGIONS_INSIDE);
625
+ // The stronger promise first: a region processing inside is never traded for one that only stores inside.
626
+ const candidates = regionsInside.length > 0 ? regionsInside : regionsInsideAtRest;
627
+ if (candidates.length === 0) return placement(ProviderDataResidencyPlacementOutcome.NO_REGION_INSIDE);
628
+ if (candidates.length > 1) return placement(ProviderDataResidencyPlacementOutcome.SEVERAL_REGIONS_INSIDE);
499
629
  return [{
500
630
  providerRef: assessment.providerRef,
501
631
  assessment,
502
632
  outcome: ProviderDataResidencyPlacementOutcome.DERIVED,
503
633
  regionsInside,
504
- derivedChoice: { deploymentModel: ProviderDeploymentModel.VENDOR_HOSTED, processingRegion: regionsInside[0]! },
634
+ regionsInsideAtRest,
635
+ derivedChoice: { deploymentModel: ProviderDeploymentModel.VENDOR_HOSTED, processingRegion: candidates[0]! },
505
636
  }];
506
637
  }
507
638
  }
@@ -516,16 +647,25 @@ export function placeProvidersInsideDataResidency(params: Parameters<typeof asse
516
647
  */
517
648
  export function dataResidencyPlacementStatement(placement: ProviderDataResidencyPlacement, residency: ApplicationDataResidency): string {
518
649
  const declared = residency.territories.join(', ');
650
+ const atRest = residency.storedAtRestTerritories?.join(', ');
519
651
  const at = `providerComplianceChoices.${placement.providerRef}`;
520
- const inside = placement.regionsInside.map((region) => `"${region}"`).join(', ');
652
+ // The candidates a placement chose among: the regions processing inside, else (#3876) the ones storing inside at rest.
653
+ const onlyAtRest = placement.regionsInside.length === 0 && placement.regionsInsideAtRest.length > 0;
654
+ const inside = (onlyAtRest ? placement.regionsInsideAtRest : placement.regionsInside).map((region) => `"${region}"`).join(', ');
521
655
  switch (placement.outcome) {
522
656
  case ProviderDataResidencyPlacementOutcome.DERIVED:
523
- return `Provider "${placement.providerRef}" processes in region "${placement.derivedChoice?.processingRegion}", the only one of its regions inside the data residency (${declared}).`;
657
+ return onlyAtRest
658
+ ? `Provider "${placement.providerRef}" uses region "${placement.derivedChoice?.processingRegion}", the only one of its regions keeping data at rest inside the at-rest residency (${atRest}). `
659
+ + `It processes outside the data residency (${declared}), so it is admitted on the weaker promise and the documents say so.`
660
+ : `Provider "${placement.providerRef}" processes in region "${placement.derivedChoice?.processingRegion}", the only one of its regions inside the data residency (${declared}).`;
524
661
  case ProviderDataResidencyPlacementOutcome.SEVERAL_REGIONS_INSIDE:
525
- return `Provider "${placement.providerRef}" has several regions inside the data residency (${declared}): ${inside}. Choose one as ${at}.processingRegion (deploymentModel VENDOR_HOSTED).`;
662
+ return onlyAtRest
663
+ ? `Provider "${placement.providerRef}" has several regions keeping data at rest inside the at-rest residency (${atRest}), none processing inside the data residency (${declared}): ${inside}. Choose one as ${at}.processingRegion (deploymentModel VENDOR_HOSTED).`
664
+ : `Provider "${placement.providerRef}" has several regions inside the data residency (${declared}): ${inside}. Choose one as ${at}.processingRegion (deploymentModel VENDOR_HOSTED).`;
526
665
  case ProviderDataResidencyPlacementOutcome.NO_REGION_INSIDE:
527
- return `Provider "${placement.providerRef}" has no region its profile states to process wholly inside the data residency (${declared}). `
528
- + 'Replace it with a provider that does, run it self-hosted if it is offered that way, or widen the residency.';
666
+ return `Provider "${placement.providerRef}" has no region its profile states to process wholly inside the data residency (${declared})`
667
+ + (atRest === undefined ? '' : `, nor to keep data at rest wholly inside the at-rest residency (${atRest})`)
668
+ + '. Replace it with a provider that does, run it self-hosted if it is offered that way, or widen the residency.';
529
669
  case ProviderDataResidencyPlacementOutcome.DEPLOYMENT_MODEL_IS_A_CHOICE:
530
670
  return `Provider "${placement.providerRef}" can be run by its vendor or by you: decide which as ${at}.deploymentModel`
531
671
  + (placement.regionsInside.length === 0 ? ` (none of its vendor regions lies inside the data residency, ${declared}).` : ` (vendor regions inside the data residency, ${declared}: ${inside}).`);
@@ -559,6 +699,7 @@ export function dataResidencyRefusalOf(
559
699
  : `providerComplianceChoices.${entry.providerRef}.processingRegion "${entry.processingRegion}"`;
560
700
  switch (entry.status) {
561
701
  case ProviderDataResidencyStatus.INSIDE:
702
+ case ProviderDataResidencyStatus.INSIDE_AT_REST:
562
703
  return null;
563
704
  case ProviderDataResidencyStatus.OUTSIDE:
564
705
  return `${where} processes in ${entry.outsideTerritories.join(', ')}, outside the declared data residency (${declared}). `
@@ -602,13 +743,14 @@ export function dataResidencyRefusalOf(
602
743
  * places goes only to a processor whose chosen region processes inside them.
603
744
  */
604
745
  export function assessProviderCallAgainstDataResidency(params: {
605
- readonly territories: readonly string[];
746
+ /** The residency the call must satisfy: both promises, narrowed for the organization ({@link effectiveDataResidency}). */
747
+ readonly residency: ApplicationDataResidency;
606
748
  readonly providerRef: string;
607
749
  readonly choice: ProviderDataResidencyChoice | undefined;
608
750
  readonly profile: ProviderComplianceProfile | undefined;
609
751
  readonly account: ProviderCallAccount;
610
752
  }): ProviderDataResidencyEntry | null {
611
- const residency: ApplicationDataResidency = { territories: [...params.territories] as ApplicationDataResidency['territories'] };
753
+ const { residency } = params;
612
754
  if (params.account === ProviderCallAccount.OWNER) {
613
755
  const established = establishedProviderComplianceProfile(params.profile);
614
756
  if (established !== null && providerIsAlwaysSelfHosted(established)) return null;
@@ -667,6 +809,8 @@ export function dataResidencyRefusals(entries: readonly ProviderDataResidencyEnt
667
809
  */
668
810
  export const RuntimeProviderDataResidencySchema = z.strictObject({
669
811
  territories: z.array(JurisdictionSlugSchema).min(1),
812
+ /** The opt-in at-rest territories (#2294), carried only when the application declares them. */
813
+ storedAtRestTerritories: z.array(JurisdictionSlugSchema).min(1).optional(),
670
814
  choices: z.record(z.string().min(1), z.strictObject({
671
815
  deploymentModel: z.enum(ProviderDeploymentModel),
672
816
  processingRegion: z.string().min(1).optional(),
@@ -684,6 +828,7 @@ export function runtimeProviderDataResidencyFor(input: {
684
828
  const choices = input.choices ?? {};
685
829
  return {
686
830
  territories: [...input.residency.territories],
831
+ ...(input.residency.storedAtRestTerritories === undefined ? {} : { storedAtRestTerritories: [...input.residency.storedAtRestTerritories] }),
687
832
  choices: Object.fromEntries([...new Set(input.providerRefs)].sort((left, right) => left.localeCompare(right))
688
833
  .filter((providerRef) => Object.hasOwn(choices, providerRef))
689
834
  .map((providerRef) => {
@@ -708,10 +853,22 @@ export function narrowRuntimeProviderDataResidency(
708
853
  if (runtime === undefined) return undefined;
709
854
  return {
710
855
  territories: [...runtime.territories],
856
+ ...(runtime.storedAtRestTerritories === undefined ? {} : { storedAtRestTerritories: [...runtime.storedAtRestTerritories] }),
711
857
  choices: Object.fromEntries(Object.entries(runtime.choices).filter(([providerRef]) => providerRefs.includes(providerRef))),
712
858
  };
713
859
  }
714
860
 
861
+ /**
862
+ * The application's declared residency as a runtime artifact carries it, both promises (#2294). The one reading the
863
+ * loader's re-check and the per-organization gate share, so neither can drop the at-rest territories the other applies.
864
+ */
865
+ export function applicationDataResidencyOfRuntime(runtime: RuntimeProviderDataResidency): ApplicationDataResidency {
866
+ return {
867
+ territories: [...runtime.territories],
868
+ ...(runtime.storedAtRestTerritories === undefined ? {} : { storedAtRestTerritories: [...runtime.storedAtRestTerritories] }),
869
+ };
870
+ }
871
+
715
872
  /**
716
873
  * The residency a runtime re-applies at load, over the providers it loaded: `providerRef` -> the refusal, for every one
717
874
  * that is not inside. The backend provider loader leaves each unresolved, so startup refuses naming it.
@@ -721,7 +878,7 @@ export function runtimeDataResidencyRefusalsByProvider(input: {
721
878
  readonly providerRefs: readonly string[];
722
879
  readonly profilesByProviderRef: Readonly<Record<string, ProviderComplianceProfile | undefined>>;
723
880
  }): ReadonlyMap<string, string> {
724
- const residency: ApplicationDataResidency = { territories: input.runtime.territories };
881
+ const residency = applicationDataResidencyOfRuntime(input.runtime);
725
882
  const refusals = new Map<string, string>();
726
883
  // Only the providers this host LOADED: a choice for one that failed to load for another reason must not replace that
727
884
  // reason, and a provider that is not loaded receives no call.
@@ -1048,6 +1205,13 @@ export interface ProviderComplianceChoiceAssessmentEntry {
1048
1205
  * region is chosen or the profile does not map it.
1049
1206
  */
1050
1207
  readonly regionTerritories: readonly string[] | null;
1208
+ /**
1209
+ * The places the chosen region keeps data at rest in, from the profile's `storageRegionTerritories` (#2294). `null` when
1210
+ * no region is chosen or the profile does not map its storage.
1211
+ */
1212
+ readonly regionStorageTerritories: readonly string[] | null;
1213
+ /** The condition the chosen region's storage map holds on, from `storageRegionConditions` (#3920); `null` when none. */
1214
+ readonly regionStorageCondition: string | null;
1051
1215
  }
1052
1216
 
1053
1217
  /** Assess ONE choice against the provider's profile. See {@link ProviderComplianceChoiceAssessment}. */
@@ -1091,6 +1255,8 @@ export function assessProviderComplianceChoices(params: {
1091
1255
  offered: established === null ? null : { deploymentModels: established.deploymentModels, processingRegions: established.processingRegions },
1092
1256
  regionReach: choice.processingRegion === undefined ? null : established?.processingRegionReach?.[choice.processingRegion]?.kind ?? null,
1093
1257
  regionTerritories: choice.processingRegion === undefined ? null : established?.processingRegionTerritories?.[choice.processingRegion] ?? null,
1258
+ regionStorageTerritories: choice.processingRegion === undefined ? null : established?.storageRegionTerritories?.[choice.processingRegion] ?? null,
1259
+ regionStorageCondition: choice.processingRegion === undefined ? null : established?.storageRegionConditions?.[choice.processingRegion] ?? null,
1094
1260
  };
1095
1261
  });
1096
1262
  }
@@ -93,6 +93,13 @@ export const PROVIDER_CAPABILITY_DISCLOSURES: Readonly<Record<BuiltinProviderCap
93
93
  carriedBy: 'each signer\'s name and email address, and the document sent for signature, which the vendor holds signed',
94
94
  linkableToSubjectByApplication: true,
95
95
  },
96
+ // Embedded signing: the signer's name and e-mail again, to open their signing page, and the page the vendor serves in a
97
+ // frame of the application, which reaches the vendor from the signer's browser with the application's origin.
98
+ [BUILTIN_PROVIDER_CAPABILITY.EMBEDDED_ELECTRONIC_SIGNATURE]: {
99
+ categories: [PersonalDataCategory.IDENTITY, PersonalDataCategory.CONTACT_DETAILS],
100
+ carriedBy: 'each signer\'s name and email address, sent again to open their signing page, and the signer\'s browser, which loads that page from the vendor',
101
+ linkableToSubjectByApplication: true,
102
+ },
96
103
  [BUILTIN_PROVIDER_CAPABILITY.BILLING]: {
97
104
  categories: [PersonalDataCategory.IDENTITY, PersonalDataCategory.CONTACT_DETAILS, PersonalDataCategory.FINANCIAL],
98
105
  carriedBy: 'the customer name and email address, and the payment, subscription and invoice records',
@@ -337,6 +337,36 @@ export const SHELL_GHOST_LAYER_ATTRIBUTE = 'data-shell-ghost-layer';
337
337
  /** The attribute every ghost carries, with its kind (`ShellGhostKind`). */
338
338
  export const SHELL_GHOST_ATTRIBUTE = 'data-shell-ghost';
339
339
 
340
+ /**
341
+ * The markers a still picture of an engine element must NOT carry: everything a query for the real element, or for a
342
+ * control inside it, finds it by. A picture (a discarded pane leaving, an image behind an expanded pane, a pressed row
343
+ * flying into its pane) is inert and takes no pointer, but it is still in the document while it fades, and a picture
344
+ * that kept these was found by those queries as though it were the thing it shows.
345
+ *
346
+ * Measured 2026-11-14 on Your Application (morph layout): a closed todo pane's picture kept `data-navigation-back` for the
347
+ * ~650ms it took to leave, so a lookup of the pane's back control found the picture's (#3764 had to wait it out in
348
+ * `browser-nav-zones`). It never took a click (inert, `pointer-events: none`: the point under it hit the list), but
349
+ * the zone's own back control is identified by that attribute, and a picture must not answer to it.
350
+ *
351
+ * Styling hooks (`data-slot`, `data-state`) are NOT here: a picture keeps the look of what it shows. A caller that
352
+ * needs a narrower picture strips more on its own.
353
+ */
354
+ export const SHELL_PICTURE_STRIPPED_ATTRIBUTES: readonly string[] = [
355
+ 'id',
356
+ // The engine's pane and region markers.
357
+ 'data-content-area',
358
+ 'data-panel-id',
359
+ 'data-zone-hidden',
360
+ 'data-zone-emphasized',
361
+ 'data-component-area',
362
+ SHELL_OBJECT_ATTRIBUTE,
363
+ // The engine's control hooks: a zone's back control, an operation's trigger, a navigation item, a rail entry.
364
+ 'data-navigation-back',
365
+ 'data-operation-id',
366
+ 'data-nav-item-id',
367
+ 'data-ref',
368
+ ];
369
+
340
370
  /** The two kinds of ghost. */
341
371
  export enum ShellGhostKind {
342
372
  /** A dismissed side pane, flying away. */
@@ -242,6 +242,20 @@ export const navigationLayoutConfig: NavigationLayout = {
242
242
  transitions: {
243
243
  /* A reference inside the pane stacks in the pane; back returns to the todo beneath. */
244
244
  [CoreResourceOperation.READ]: NavigationTransition.PUSH,
245
+ /*
246
+ * Mutations open a dialog from the pane exactly as they do from the page. A zone's map answers only for
247
+ * navigations started IN that zone (the resolver borrows primary's map for an overlay source, never for a
248
+ * pane), so a pane that named only READ sent "Edit" on a todo to the framework fallback: the form was pushed
249
+ * into the pane, took the todo's place, and wrote its URL (#3764). The layout's stated rule above is
250
+ * "mutations → overlay", and a todo is edited from the pane more often than from anywhere else.
251
+ */
252
+ [CoreResourceOperation.CREATE]: NavigationTransition.OVERLAY,
253
+ [CoreResourceOperation.UPDATE]: NavigationTransition.OVERLAY,
254
+ [CoreResourceOperation.DELETE]: NavigationTransition.OVERLAY,
255
+ [CoreResourceOperation.SEARCH]: NavigationTransition.OVERLAY,
256
+ },
257
+ appearance: {
258
+ overlay: OverlayAppearance.DIALOG,
245
259
  },
246
260
  onEmpty: ZoneEmptyBehavior.COLLAPSE,
247
261
  responsiveCollapse: {
@@ -80,6 +80,25 @@ never holds a residency `wildo config sync` would refuse. A provider with severa
80
80
  deployment model to choose, or a region of yours outside is left to you and listed by `wildo context
81
81
  launch-blockers` with the regions that would do; place it, then run the foundation again.
82
82
 
83
+ Many SaaS vendors keep data AT REST in the region you pick but process it elsewhere (support tools, chat,
84
+ document workspaces). Under `territories` alone they are refused. If you are willing to make the weaker promise
85
+ for them, add `storedAtRestTerritories` beside `territories`:
86
+
87
+ ```ts
88
+ operatorComplianceIdentity: {
89
+ dataResidency: { territories: ['eu'], storedAtRestTerritories: ['eu'] },
90
+ },
91
+ ```
92
+
93
+ A vendor whose chosen region processes outside `territories` is then admitted when every place that region keeps
94
+ data at rest, as its provider profile states (`storageRegionTerritories`), lies inside `storedAtRestTerritories`.
95
+ It never counts as inside the processing residency: its entry reads `inside-at-rest`, and the governed documents
96
+ say for it that the data is stored in the region and may be processed elsewhere. A vendor whose profile states no
97
+ storage places is still refused. The foundation keeps the list when it writes `territories`, places a provider on
98
+ it only when none of the provider's regions processes inside, and, when you have declared none, tells you which
99
+ regions declaring one over the same places would admit. It never declares one for you: the promise is yours.
100
+ An organization may narrow both lists, and one that declares no at-rest list admits no storage-only vendor.
101
+
83
102
  To see every part still owed, with the rest of what stands between the application and launch:
84
103
 
85
104
  ```bash
@@ -263,6 +263,7 @@ Reads and changes of application data that are recorded for review.
263
263
 
264
264
  | Event | Wire value | Severity | What it records |
265
265
  | --- | --- | --- | --- |
266
+ | `A2A_REMOTE_AGENT_CALL` | `a2a_remote_agent_call` | Information | |
266
267
  | `AGENT_BEHAVIOR_REPORT_RECEIVED` | `agent_behavior_report_received` | Warning, raised to Critical by an occurrence that says so | A person reported an agent's reply. |
267
268
  | `AGENT_BEHAVIOR_REPORTED_TURN_READ` | `agent_behavior_reported_turn_read` | Warning | An administrator read the reply a report is about, from the reporter's conversation (`readReportedTurn`): a person's conversation read by someone else, so every read is recorded, with whether the turn was still there. |
268
269
  | `AGENT_CONTENT_QUARANTINED` | `agent_content_quarantined` | Critical | A classifier found a prompt-injection attack in content somebody else wrote, and the agent's model never read it: a tool result reached it as a quarantine notice, or an inbound delivery did not start its turn (`contentSource`). |
@@ -475,7 +475,7 @@ record of its key, the issuer, and the disclosures the row still holds (the peop
475
475
  statement). Each export is recorded (`approval_seal_exported`); a seal kept after its approver's erasure
476
476
  needs `--operator` and `--justification`. A person's own data export also carries their seals' key
477
477
  records (`verificationKeys`), and leaves out the requester and what was presented, which are other
478
- people's data. Seals are not part of a portability export: the operator made them. To verify a seal, `wildo seal verify <bundle.json>` reads `{ jws, keys, expectedIssuer?, disclosures?, erasedClaims?, deliverableFile?, manifestedCopy? }`, where each key is its stored record (`publishedVerificationKeys`: kid, public JWK,
478
+ people's data. Seals are not part of a portability export: the operator made them. To verify a seal, `wildo seal verify <bundle.json>` reads `{ jws, keys, expectedIssuer?, disclosures?, erasedClaims?, deliverableFile?, manifestedCopy?, vendorSignedCopies? }`, where each key is its stored record (`publishedVerificationKeys`: kid, public JWK,
479
479
  scope, scope id, issuer, state) and calls nothing. It pins ES256 from the key record, ignores any key
480
480
  the token names, refuses an organization key used for another tenant, checks each disclosure against
481
481
  its commitment, and reports content the seal commits to and the bundle does not give without failing
@@ -549,6 +549,20 @@ checks the seal, not the document. A copy that was not made, or is gone, is rebu
549
549
  `wildo seal rebuild-copy <sealId> --justification "…"`, recorded on the audit trail as
550
550
  `approval_seal_manifested_copy_rebuilt`; a seal whose copy is present is refused.
551
551
 
552
+ The same original may also have been signed through an electronic-signature vendor (the
553
+ `ELECTRONIC_SIGNATURE` capability): the vendor's copy is another file derived from it, with lineage role
554
+ `VENDOR_SIGNED_COPY`. A seal's bundle names every such copy of a SIGNED request that followed the seal
555
+ (`vendorSignedCopies`: the file id, the file its row says it derives from, the hash its row recorded).
556
+ `wildo seal verify <bundle.json> --vendor-signed-copy <file>` (repeatable) checks that the copy's first
557
+ revision, ending at a `%%EOF`, is the approved file, and reports which original it derives from. A copy
558
+ whose row names another original, or that does not start with the approved file, fails the seal (and,
559
+ when you call the verifier yourself, so do bytes that are not the ones the row recorded). Only a copy the
560
+ bundle names with these exact bytes is reported as
561
+ the signed copy your application recorded; a file the bundle does not name is reported as starting with
562
+ the approved file and nothing more, since anyone holding the original can append to it. The vendor's own
563
+ signature is not re-checked here: the engine validated it when the signed document arrived, and that
564
+ evidence is the signature request's `validationEvidence` file.
565
+
552
566
  ## Pinning your keys
553
567
 
554
568
  The host holds the keys and publishes their public halves, so on its own your application can only
@@ -292,6 +292,17 @@ export const BUILTIN_PROVIDER_CAPABILITY = {
292
292
  * levels its contract declares. Maps to `EngineCapability.ELECTRONIC_SIGNATURE`.
293
293
  */
294
294
  ELECTRONIC_SIGNATURE: 'ELECTRONIC_SIGNATURE',
295
+ /**
296
+ * Provider ALSO lets a signer sign inside the application, in a frame showing the vendor's signing page, instead of
297
+ * from the vendor's e-mail (embedded signing). Maps to `EngineCapability.ELECTRONIC_SIGNATURE`, the slot it shares with
298
+ * {@link ELECTRONIC_SIGNATURE}, and is claimed only beside it.
299
+ *
300
+ * A token of its own because vendors split here: DocuSign, Yousign, BoldSign, SignNow and Adobe Acrobat Sign answer a
301
+ * signing page URL the application can frame; IgniSign, Dropbox Sign and Universign need their own browser script, so
302
+ * their providers sign from the e-mail only. The claim is the provider's statement that its contract declares
303
+ * `embeddedSigning`; the engine refuses at startup a claim with no such declaration.
304
+ */
305
+ EMBEDDED_ELECTRONIC_SIGNATURE: 'EMBEDDED_ELECTRONIC_SIGNATURE',
295
306
  /**
296
307
  * Single billing-engagement capability covering everything from
297
308
  * Checkout-style hosted flows to first-party PaymentIntent flows.