@wildo-ai/framework-knowledge 1.1.14 → 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 (94) 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/esm/framework-knowledge.definitions.d.ts +1 -1
  4. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  5. package/dist/esm/framework-knowledge.definitions.js +9 -0
  6. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  7. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  8. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
  9. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  10. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +1 -1
  11. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +1 -1
  12. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
  13. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  14. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  15. package/dist/knowledge/manifest.json +7 -7
  16. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +7 -0
  17. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +2 -2
  18. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +27 -10
  19. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +1 -1
  20. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +13 -9
  21. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +1 -1
  22. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +20 -5
  23. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +2 -2
  24. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +4 -0
  25. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  26. package/dist/knowledge/references/build-plan.task-graph.config.md +12 -8
  27. package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +6 -2
  28. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +13 -2
  29. package/dist/knowledge/references/example.inbound.email-to-todo.md +33 -2
  30. package/dist/knowledge/references/example.module.relationships.discriminator.md +7 -1
  31. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +2 -0
  32. package/dist/knowledge/references/integration-plan.config.md +78 -8
  33. package/dist/knowledge/references/platform.config.environment.deployment.md +27 -4
  34. package/dist/knowledge/references/saas.backend.domain-module.md +15 -0
  35. package/dist/knowledge/references/saas.backend.flows-actors.a2a-agent-card.md +43 -11
  36. package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +17 -11
  37. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +11 -0
  38. package/dist/knowledge/references/saas.frontend.electronic-signatures.embedded-signing-frame.md +46 -0
  39. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +24 -33
  40. package/dist/knowledge/references/saas.models.flows-actors.mcp-server-declaration.md +63 -0
  41. package/dist/knowledge/references/saas.models.flows-actors.outbound-credential.md +61 -0
  42. package/dist/knowledge/references/saas.models.flows-actors.remote-agent-declaration.md +56 -0
  43. package/dist/knowledge/references/saas.models.http-api-binding.md +51 -0
  44. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +7 -0
  45. package/dist/knowledge/references/saas.models.provider-capabilities.md +11 -0
  46. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +30 -0
  47. package/dist/knowledge/references/saas.rag.retrieval-scores.md +4 -2
  48. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  49. package/dist/knowledge/registries/framework-topics.json +45 -1
  50. package/dist/knowledge/registries/playbooks.json +2 -2
  51. package/dist/knowledge/registries/source-tags.json +1080 -1012
  52. package/dist/knowledge/skills/INDEX.md +2 -2
  53. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +4 -1
  54. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +15 -0
  55. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +3 -1
  56. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +4 -0
  57. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +7 -0
  58. package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +1 -0
  59. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +11 -0
  60. package/dist/knowledge/skills/electronic-signature-deliverables/SKILL.md +12 -5
  61. package/dist/knowledge/skills/electronic-signature-deliverables/references/signing-inside-the-application.md +113 -0
  62. package/dist/knowledge/skills/email-add-template/SKILL.md +3 -2
  63. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +8 -4
  64. package/dist/knowledge/skills/email-definition-wiring/SKILL.md +1 -1
  65. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +29 -7
  66. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +66 -26
  67. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +6 -2
  68. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +34 -3
  69. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +13 -2
  70. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +11 -0
  71. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +15 -0
  72. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-mcp-server-declaration-api.md +139 -0
  73. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-remote-a2a-agent-declaration-api.md +169 -0
  74. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +24 -33
  75. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +33 -2
  76. package/dist/knowledge/skills/infra-environment-config/SKILL.md +31 -9
  77. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +27 -4
  78. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +26 -0
  79. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +15 -0
  80. package/dist/knowledge/skills/module-relationships/SKILL.md +20 -1
  81. package/dist/knowledge/skills/provider-backend-package/SKILL.md +13 -2
  82. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +2 -0
  83. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +3 -0
  84. package/dist/knowledge/skills/resource-add-module/SKILL.md +8 -2
  85. package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +17 -0
  86. package/dist/knowledge/skills/resource-chat-commands/SKILL.md +1 -1
  87. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +51 -0
  88. package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +14 -5
  89. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +30 -0
  90. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-client-registration-postures.md +5 -0
  91. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +4 -2
  92. package/dist/knowledge/topic-index.json +231 -84
  93. package/dist/tsconfig.build.tsbuildinfo +1 -1
  94. package/package.json +4 -4
@@ -0,0 +1,63 @@
1
+ # saas.models.flows-actors.mcp-server-declaration
2
+
3
+ ## Import Origins
4
+
5
+ - `@wildo-ai/saas-models`
6
+
7
+ ## Source Excerpts
8
+
9
+ ### Origin Package: `@wildo-ai/saas-models`
10
+
11
+ ```typescript
12
+ *
13
+ * How the runtime reaches the server.
14
+ *
15
+ * A closed vocabulary rather than a free string: the transport decides the whole connection
16
+ * lifecycle — how a session opens, whether the server can push, how a stream ends — so a value
17
+ * nobody implemented must be unrepresentable rather than discovered at the first call.
18
+ *
19
+ * STDIO is deliberately ABSENT. It launches a local subprocess, which is the coding-agent lane's
20
+ * shape and not an application's: a generated application runs in a container it does not control,
21
+ * and "the agent may spawn a process" is a different security decision from "the agent may call an
22
+ * endpoint". Adding it later is a decision, not an omission.
23
+ */
24
+ export enum FlowsActors_McpTransport {
25
+ /** Streamable HTTP — the current MCP transport for remote servers. */
26
+ HTTP_STREAM = 'http_stream',
27
+ /**
28
+ * Server-sent events — the earlier remote transport, still widely deployed. The client speaks Streamable HTTP only,
29
+ * so startup REFUSES a server declared with it (#3958) rather than failing every turn as a protocol error.
30
+ */
31
+ SSE = 'sse',
32
+ }
33
+
34
+
35
+ /**
36
+ * Bounds on a call that leaves the trust boundary.
37
+ *
38
+ * Present with defaults rather than optional-and-unbounded, because an MCP call is a REMOTE call and
39
+ * the mistake this whole issue warns against is modelling it as a second kind of local function. A
40
+ * local function cannot hang; this can, and an unbounded tool call holds a model turn open for as
41
+ * long as somebody else's server feels like it.
42
+ */
43
+ export const FlowsActors_McpServerTimeoutsSchema = z.object({
44
+ /** How long tool DISCOVERY may take before the server contributes no tools to the turn. */
45
+ discoveryMs: z.number().int().positive().default(5_000),
46
+ /** How long one tool CALL may take before it returns a typed timeout to the agent. */
47
+ callMs: z.number().int().positive().default(30_000),
48
+ });
49
+ export type FlowsActors_McpServerTimeouts = z.infer<typeof FlowsActors_McpServerTimeoutsSchema>;
50
+
51
+ export const FlowsActors_McpServerSchema = z.object({
52
+ /** The value an agent's `capabilities.tools.mcpRefs` names. Unique within an application. */
53
+ ref: z.string().min(1),
54
+ displayName: z.string().min(1),
55
+ transport: z.enum(FlowsActors_McpTransport),
56
+ /** The server's endpoint. `https` in every deployed environment; the runtime refuses plaintext. */
57
+ url: z.string().url(),
58
+ /** Which stored provider credential authorizes the calls (`FlowsActors_OutboundCredentialSchema`). */
59
+ credential: FlowsActors_OutboundCredentialSchema,
60
+ timeouts: FlowsActors_McpServerTimeoutsSchema.default({ discoveryMs: 5_000, callMs: 30_000 }),
61
+ });
62
+ export type FlowsActors_McpServer = z.infer<typeof FlowsActors_McpServerSchema>;
63
+ ```
@@ -0,0 +1,61 @@
1
+ # saas.models.flows-actors.outbound-credential
2
+
3
+ ## Import Origins
4
+
5
+ - `@wildo-ai/saas-models`
6
+
7
+ ## Source Excerpts
8
+
9
+ ### Origin Package: `@wildo-ai/saas-models`
10
+
11
+ ```typescript
12
+ /**
13
+ * WHOSE credential the call carries.
14
+ *
15
+ * The distinction is not a preference. A tool call that reaches a third party on a user's behalf
16
+ * should be attributable to that user AT THE FAR END — that is what makes it revocable there and
17
+ * auditable by the party being called. An application-wide service identity loses that: every
18
+ * user's call looks identical to the server, and one leaked credential exposes every tenant.
19
+ */
20
+ export enum FlowsActors_OutboundCredentialSubject {
21
+ /**
22
+ * The acting user's own delegated credential, falling back to the organization's connection when
23
+ * the user has none. The default, and the reason a fallback exists at all: an agent acting for a
24
+ * user who has never connected the server would otherwise have no path, which would make every
25
+ * unattended and batch turn impossible.
26
+ */
27
+ USER_THEN_ORGANIZATION = 'user_then_organization',
28
+ /** The organization's connection only — for a server the tenant connects once on everyone's behalf. */
29
+ ORGANIZATION = 'organization',
30
+ /** The acting user's own credential only. No fallback: a user who has not connected cannot call. */
31
+ USER = 'user',
32
+ }
33
+
34
+ /**
35
+ * Which stored credential authorizes the call.
36
+ *
37
+ * `providerRef` names a provider the application has already connected, so the credential comes from
38
+ * `organizationProviderCredentials` / `userProviderCredentials` rather than from a store invented
39
+ * for one kind of call. Those exist, carry per-tenant isolation by construction, and already have the connect and
40
+ * consent flow in front of them — a second credential store for this one call shape would be a
41
+ * second thing to rotate, audit and leak.
42
+ */
43
+ export const FlowsActors_OutboundCredentialSchema = z.object({
44
+ providerRef: z.string().min(1),
45
+ /**
46
+ * The provider's `secretsContract` KEY (`accessToken`) — the one both credential resolver ports
47
+ * require, and NOT the slot's env-var spelling (`VENDOR_ACCESS_TOKEN`) the env projection names.
48
+ * Stored credentials are keyed on the key (#624), and this value reaches the stores verbatim, so a
49
+ * spelling here misses a credential that exists.
50
+ *
51
+ * DECLARED rather than derived, because it is not derivable: a provider's contract may carry
52
+ * several secrets, and which of them authorizes the endpoint is a fact about that vendor's
53
+ * deployment rather than anything the framework can compute. Guessing a conventional name would
54
+ * resolve the wrong secret silently — the resolver would find a credential, spend it, and be
55
+ * refused by the far server for a reason no log here would explain.
56
+ */
57
+ secretSlug: z.string().min(1),
58
+ subject: z.enum(FlowsActors_OutboundCredentialSubject).default(FlowsActors_OutboundCredentialSubject.USER_THEN_ORGANIZATION),
59
+ });
60
+ export type FlowsActors_OutboundCredential = z.infer<typeof FlowsActors_OutboundCredentialSchema>;
61
+ ```
@@ -0,0 +1,56 @@
1
+ # saas.models.flows-actors.remote-agent-declaration
2
+
3
+ ## Import Origins
4
+
5
+ - `@wildo-ai/saas-models`
6
+
7
+ ## Source Excerpts
8
+
9
+ ### Origin Package: `@wildo-ai/saas-models`
10
+
11
+ ```typescript
12
+ /**
13
+ * Bounds on a call that leaves the trust boundary. Present with defaults, because a remote agent can take as long as it
14
+ * likes and an unbounded call would hold the calling agent's turn open for that long.
15
+ */
16
+ export const FlowsActors_RemoteAgentTimeoutsSchema = z.object({
17
+ /** How long fetching the remote agent's card may take. */
18
+ cardMs: z.number().int().positive().default(5_000),
19
+ /**
20
+ * How long one delegation may take, end to end: the send, then reading the task until it ends or pauses. A task still
21
+ * running at the deadline is returned to the calling agent as still running, with its ids; it is never cancelled.
22
+ */
23
+ callMs: z.number().int().positive().default(60_000),
24
+ });
25
+ export type FlowsActors_RemoteAgentTimeouts = z.infer<typeof FlowsActors_RemoteAgentTimeoutsSchema>;
26
+
27
+ /**
28
+ * Another party's A2A agent the application's agents may delegate a task to (A2A 1.0, JSON-RPC binding).
29
+ *
30
+ * The runtime fetches the agent card from `cardUrl` WITHOUT the credential and sends the credential to one of the card's
31
+ * JSON-RPC interfaces at protocol version 1.0, and only to one the application named too: with `endpointUrl` declared,
32
+ * the interface at exactly that URL; without it, the card's first such interface, and only when it is on the card's own
33
+ * host. A card cannot redirect a credential to a host the application never named.
34
+ */
35
+ export const FlowsActors_RemoteAgentSchema = z.object({
36
+ /** The value an agent's `capabilities.tools.remoteAgentRefs` names. Unique within an application. */
37
+ ref: z.string().min(1),
38
+ displayName: z.string().min(1),
39
+ /**
40
+ * What the remote agent does, in the application's words. It is the description of the tool the calling model is
41
+ * offered — the card's own description never reaches the model.
42
+ */
43
+ description: z.string().min(1),
44
+ /** Where the agent card is served, `https://` (e.g. `https://agent.example.com/.well-known/agent-card.json`). */
45
+ cardUrl: z.string().url(),
46
+ /**
47
+ * The interface URL the credential is sent to, exactly. Declare it when the agent's interface is on another host than
48
+ * its card, or to pin which of the card's interfaces is used. The credential is resolved for this URL.
49
+ */
50
+ endpointUrl: z.string().url().optional(),
51
+ /** Which stored provider credential authorizes the calls, and whose. Required: an anonymous remote agent is not admitted. */
52
+ credential: FlowsActors_OutboundCredentialSchema,
53
+ timeouts: FlowsActors_RemoteAgentTimeoutsSchema.default({ cardMs: 5_000, callMs: 60_000 }),
54
+ });
55
+ export type FlowsActors_RemoteAgent = z.infer<typeof FlowsActors_RemoteAgentSchema>;
56
+ ```
@@ -248,6 +248,34 @@ export const HttpApiFieldMappingSchema = z.strictObject({
248
248
  create: z.string().min(1).optional(),
249
249
  update: z.string().min(1).optional(),
250
250
  }).optional(),
251
+ /**
252
+ * #3953 — WRITE this field through a LOOKUP (Odoo only): a create or update sends `remoteField` of this object instead
253
+ * of the mapping's own `remoteField`, set to the id of the ONE `lookupEntityRef` record whose `lookupRemoteField`
254
+ * equals the value the resource holds. Reads keep the mapping's own `remoteField`.
255
+ *
256
+ * For a field the system of record shows as a code but stores as a reference to another record. On Odoo a partner's
257
+ * `country_code` is the RELATED `country_id.code`: it reads the ISO code, and a write to it is accepted and discarded
258
+ * (measured on Odoo 19.0). The country is written through `country_id`, a many2one to `res.country`:
259
+ *
260
+ * ```ts
261
+ * { localField: 'country', remoteField: 'country_code',
262
+ * writeThrough: { remoteField: 'country_id', lookupEntityRef: 'res.country', lookupRemoteField: 'code' } }
263
+ * ```
264
+ *
265
+ * Each write with a value looks it up once more (one `search_read` on the lookup model, before anything is sent). The
266
+ * match is EXACT and case-sensitive (`'fr'` names no country whose code is `'FR'`), and Odoo leaves archived records
267
+ * of the lookup model out by default. A value no record matches is refused as the caller's
268
+ * (`SYSTEM_OF_RECORD_WRITE_VALUE_UNRESOLVED`); a value several records match, or a `remoteField` that Odoo does not
269
+ * describe as a many2one to `lookupEntityRef`, is refused as the binding's (`SYSTEM_OF_RECORD_WRITE_LOOKUP_INVALID`).
270
+ * Nothing is sent either way. An empty value (`null` or `''`) unsets the reference (Odoo's `false`). Refused at
271
+ * registration on any other dialect, on a binding that opens neither create nor update, and when the field it writes is
272
+ * another mapping's field or another write-through's.
273
+ */
274
+ writeThrough: z.strictObject({
275
+ remoteField: z.string().min(1),
276
+ lookupEntityRef: z.string().min(1),
277
+ lookupRemoteField: z.string().min(1),
278
+ }).optional(),
251
279
  });
252
280
  ```
253
281
 
@@ -947,6 +975,29 @@ export function assertHttpApiBindingDialectCoherence(binding: HttpApiResourceBin
947
975
  }
948
976
  }
949
977
 
978
+ // #3953 — a write through a lookup is Odoo's (a code shown, a reference stored), and only a write uses it.
979
+ for (const mapping of binding.fieldMappings) {
980
+ if (mapping.writeThrough === undefined) continue;
981
+ const at = `fieldMappings('${mapping.localField}').writeThrough`;
982
+ if (binding.dialect !== HttpApiTransportDialect.ODOO_JSONRPC && binding.dialect !== HttpApiTransportDialect.ODOO_JSON2) {
983
+ throw new Error(`${at}: declared on a ${binding.dialect} binding. It resolves a value through a lookup on another Odoo model before a write, and only the Odoo dialects compile one.`);
984
+ }
985
+ if (!binding.writableVerbs.includes(HttpApiWriteVerb.CREATE) && !binding.writableVerbs.includes(HttpApiWriteVerb.UPDATE)) {
986
+ throw new Error(`${at}: this binding opens neither create nor update, so nothing would ever be written through it. Remove it, or open the verb.`);
987
+ }
988
+ // Two values for one remote field in one write: whichever is written last would win, silently.
989
+ const target = mapping.writeThrough.remoteField;
990
+ const clash = binding.fieldMappings.find((other) => other !== mapping
991
+ && (other.remoteField === target || other.writeThrough?.remoteField === target));
992
+ if (clash !== undefined) {
993
+ throw new Error(`${at}: writes '${target}', which fieldMappings('${clash.localField}') also writes. One remote field takes one value per write.`);
994
+ }
995
+ // The population's create values are the engine's (#2552): a create writes them, and the lookup would replace one.
996
+ if (Object.prototype.hasOwnProperty.call(binding.populationFilter?.createValues ?? {}, target)) {
997
+ throw new Error(`${at}: writes '${target}', which the population filter's createValues also writes on every create. One remote field takes one value per write.`);
998
+ }
999
+ }
1000
+
950
1001
  // #2552 — the population filter: expressible by this dialect's list, and satisfied by what a create writes.
951
1002
  assertHttpApiPopulationFilterCoherence(binding as never);
952
1003
 
@@ -58,6 +58,13 @@ export const PROVIDER_CAPABILITY_DISCLOSURES: Readonly<Record<BuiltinProviderCap
58
58
  carriedBy: 'each signer\'s name and email address, and the document sent for signature, which the vendor holds signed',
59
59
  linkableToSubjectByApplication: true,
60
60
  },
61
+ // Embedded signing: the signer's name and e-mail again, to open their signing page, and the page the vendor serves in a
62
+ // frame of the application, which reaches the vendor from the signer's browser with the application's origin.
63
+ [BUILTIN_PROVIDER_CAPABILITY.EMBEDDED_ELECTRONIC_SIGNATURE]: {
64
+ categories: [PersonalDataCategory.IDENTITY, PersonalDataCategory.CONTACT_DETAILS],
65
+ 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',
66
+ linkableToSubjectByApplication: true,
67
+ },
61
68
  [BUILTIN_PROVIDER_CAPABILITY.BILLING]: {
62
69
  categories: [PersonalDataCategory.IDENTITY, PersonalDataCategory.CONTACT_DETAILS, PersonalDataCategory.FINANCIAL],
63
70
  carriedBy: 'the customer name and email address, and the payment, subscription and invoice records',
@@ -41,6 +41,17 @@ export const BUILTIN_PROVIDER_CAPABILITY = {
41
41
  * levels its contract declares. Maps to `EngineCapability.ELECTRONIC_SIGNATURE`.
42
42
  */
43
43
  ELECTRONIC_SIGNATURE: 'ELECTRONIC_SIGNATURE',
44
+ /**
45
+ * Provider ALSO lets a signer sign inside the application, in a frame showing the vendor's signing page, instead of
46
+ * from the vendor's e-mail (embedded signing). Maps to `EngineCapability.ELECTRONIC_SIGNATURE`, the slot it shares with
47
+ * {@link ELECTRONIC_SIGNATURE}, and is claimed only beside it.
48
+ *
49
+ * A token of its own because vendors split here: DocuSign, Yousign, BoldSign, SignNow and Adobe Acrobat Sign answer a
50
+ * signing page URL the application can frame; IgniSign, Dropbox Sign and Universign need their own browser script, so
51
+ * their providers sign from the e-mail only. The claim is the provider's statement that its contract declares
52
+ * `embeddedSigning`; the engine refuses at startup a claim with no such declaration.
53
+ */
54
+ EMBEDDED_ELECTRONIC_SIGNATURE: 'EMBEDDED_ELECTRONIC_SIGNATURE',
44
55
  /**
45
56
  * Single billing-engagement capability covering everything from
46
57
  * Checkout-style hosted flows to first-party PaymentIntent flows.
@@ -256,6 +256,36 @@ export enum SystemOfRecordErrorCode {
256
256
  */
257
257
  WRITE_FIELD_NOT_WRITABLE = 'SYSTEM_OF_RECORD_WRITE_FIELD_NOT_WRITABLE',
258
258
 
259
+ /**
260
+ * REQUEST — a create or update refused, with a CONFIGURATION error type, because the binding maps a field onto a
261
+ * remote field the system of record COMPUTES and does not store, so a
262
+ * write to it would be accepted and discarded (#3953). Odoo answers `true` to a `create` or `write` naming such a field
263
+ * and keeps nothing: measured on Odoo 19.0, `res.partner.country_code` (related to `country_id.code`) written alone
264
+ * read back `false`. Refused before anything is sent, because the alternative is a write reported as done that changed
265
+ * nothing. The context names the field and, when the system of record says so, the field it is computed from
266
+ * (`computedFrom`), which is the one to write.
267
+ *
268
+ * Not the caller's to fix: the binding's mapping is wrong for writes, so it is a configuration error.
269
+ */
270
+ WRITE_FIELD_COMPUTED_REMOTELY = 'SYSTEM_OF_RECORD_WRITE_FIELD_COMPUTED_REMOTELY',
271
+
272
+ /**
273
+ * REQUEST — a field written through a lookup (`fieldMappings[].writeThrough`, #3953) holds a value no record of the
274
+ * lookup model matches (an ISO country code Odoo does not know, or `'fr'` where the records hold `'FR'`: the match is
275
+ * exact). Refused before anything is sent: writing nothing would report the field as written, and writing a guess
276
+ * would put the row in the wrong place. The context names the field, the lookup model and the value.
277
+ */
278
+ WRITE_VALUE_UNRESOLVED = 'SYSTEM_OF_RECORD_WRITE_VALUE_UNRESOLVED',
279
+
280
+ /**
281
+ * REQUEST — a create or update refused, with a CONFIGURATION error type, because a field's write-through lookup
282
+ * (`fieldMappings[].writeThrough`, #3953) cannot name ONE record: the
283
+ * value matches several records of the lookup model (the lookup field does not identify a record), a match carries no
284
+ * integer id, or the field written is not a many2one to the lookup model as the system of record describes it. The
285
+ * binding's fault, not the caller's; nothing is sent. The context names the field, the lookup model and why.
286
+ */
287
+ WRITE_LOOKUP_INVALID = 'SYSTEM_OF_RECORD_WRITE_LOOKUP_INVALID',
288
+
259
289
  /**
260
290
  * REQUEST — the write was SENT and nobody knows whether the system of record applied it: the call
261
291
  * timed out, the connection dropped after the request left, or a gateway answered for the vendor.
@@ -25,7 +25,9 @@
25
25
  * return the passage. A passage found only by the lexical arm carries no `vectorRank`, and every
26
26
  * passage in a lexical-only call carries none — which is the expected state when the application
27
27
  * configures no embeddings provider, or when text was committed more recently than the background
28
- * worker has embedded it.
28
+ * worker has embedded it. Such a not-yet-embedded passage is not ranked BELOW embedded ones for that
29
+ * reason alone: when the vector arm ran and could not rank it, its `fusion` counts its lexical rank for
30
+ * both arms, so text written a minute ago competes on its wording from the moment it is committed.
29
31
  *
30
32
  * @example
31
33
  * // Show the strongest passages, and say WHY each was found.
@@ -42,7 +44,7 @@
42
44
  export interface RagChunkRetrievalScores {
43
45
  /** Reciprocal-rank-fusion score. Ordering key. Not a probability and not comparable across queries. */
44
46
  fusion: number;
45
- /** 1-based rank within the vector arm, absent when that arm did not return this chunk. */
47
+ /** 1-based rank within the vector arm, absent when that arm did not return this chunk (never imputed). */
46
48
  vectorRank?: number;
47
49
  /** Cosine similarity in `[-1, 1]` (`1 - cosine_distance`). Absent with the rank. */
48
50
  vectorSimilarity?: number;
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "assurance-authority-bases",
3
3
  "metadata": {
4
- "generatedAt": "2026-11-16T14:58:04.129Z",
4
+ "generatedAt": "2026-11-17T16:03:09.086Z",
5
5
  "description": "Compiled portable assurance-authority bases."
6
6
  },
7
7
  "entries": {
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "framework-topics",
3
3
  "metadata": {
4
- "generatedAt": "2026-11-16T14:58:04.129Z",
4
+ "generatedAt": "2026-11-17T16:03:09.086Z",
5
5
  "description": "Topic registry derived from extracted framework-knowledge tags."
6
6
  },
7
7
  "entries": {
@@ -4527,6 +4527,17 @@
4527
4527
  "referenceFilePath": "references/saas.frontend.domain-module.md",
4528
4528
  "sourceReferenceCount": 1
4529
4529
  },
4530
+ "saas.frontend.electronic-signatures.embedded-signing-frame": {
4531
+ "topicId": "saas.frontend.electronic-signatures.embedded-signing-frame",
4532
+ "title": "Saas Frontend Electronic Signatures Embedded Signing Frame",
4533
+ "categories": [
4534
+ "saas",
4535
+ "saas.frontend",
4536
+ "saas.frontend.electronic-signatures"
4537
+ ],
4538
+ "referenceFilePath": "references/saas.frontend.electronic-signatures.embedded-signing-frame.md",
4539
+ "sourceReferenceCount": 1
4540
+ },
4530
4541
  "saas.frontend.embedded-resource-descent": {
4531
4542
  "topicId": "saas.frontend.embedded-resource-descent",
4532
4543
  "title": "Saas Frontend Embedded Resource Descent",
@@ -5743,6 +5754,17 @@
5743
5754
  "referenceFilePath": "references/saas.models.flows-actors.human-input-form.md",
5744
5755
  "sourceReferenceCount": 1
5745
5756
  },
5757
+ "saas.models.flows-actors.mcp-server-declaration": {
5758
+ "topicId": "saas.models.flows-actors.mcp-server-declaration",
5759
+ "title": "Saas Models Flows Actors Mcp Server Declaration",
5760
+ "categories": [
5761
+ "saas",
5762
+ "saas.models",
5763
+ "saas.models.flows-actors"
5764
+ ],
5765
+ "referenceFilePath": "references/saas.models.flows-actors.mcp-server-declaration.md",
5766
+ "sourceReferenceCount": 1
5767
+ },
5746
5768
  "saas.models.flows-actors.operation-approval-pending": {
5747
5769
  "topicId": "saas.models.flows-actors.operation-approval-pending",
5748
5770
  "title": "Saas Models Flows Actors Operation Approval Pending",
@@ -5765,6 +5787,28 @@
5765
5787
  "referenceFilePath": "references/saas.models.flows-actors.operation-approval-requirement.md",
5766
5788
  "sourceReferenceCount": 1
5767
5789
  },
5790
+ "saas.models.flows-actors.outbound-credential": {
5791
+ "topicId": "saas.models.flows-actors.outbound-credential",
5792
+ "title": "Saas Models Flows Actors Outbound Credential",
5793
+ "categories": [
5794
+ "saas",
5795
+ "saas.models",
5796
+ "saas.models.flows-actors"
5797
+ ],
5798
+ "referenceFilePath": "references/saas.models.flows-actors.outbound-credential.md",
5799
+ "sourceReferenceCount": 1
5800
+ },
5801
+ "saas.models.flows-actors.remote-agent-declaration": {
5802
+ "topicId": "saas.models.flows-actors.remote-agent-declaration",
5803
+ "title": "Saas Models Flows Actors Remote Agent Declaration",
5804
+ "categories": [
5805
+ "saas",
5806
+ "saas.models",
5807
+ "saas.models.flows-actors"
5808
+ ],
5809
+ "referenceFilePath": "references/saas.models.flows-actors.remote-agent-declaration.md",
5810
+ "sourceReferenceCount": 1
5811
+ },
5768
5812
  "saas.models.flows-actors.review-calendar": {
5769
5813
  "topicId": "saas.models.flows-actors.review-calendar",
5770
5814
  "title": "Saas Models Flows Actors Review Calendar",
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "playbooks",
3
3
  "metadata": {
4
- "generatedAt": "2026-11-16T14:58:04.129Z",
4
+ "generatedAt": "2026-11-17T16:03:09.086Z",
5
5
  "description": "Compiled meta-workflow playbooks (app-creation methodology definitions)."
6
6
  },
7
7
  "entries": {
@@ -10,7 +10,7 @@
10
10
  "version": "0.4.3",
11
11
  "phase": "bottom_up",
12
12
  "executor": "deterministic_cli",
13
- "intent": "Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over EVERY workspace package the application has (specifications, shared-lib, backend-api, frontend, and the website, technical documentation site, workers and minions it composed), derived from those packages rather than listed, OUTSIDE any coding agent, and reports a per-check outcome. It fixes NOTHING: a failure is surfaced for a refinement re-dispatch, which is a different playbook's job, and it authors no schemas and writes no code. Deliberately DISTINCT from the refinement phase's coverage audit, which also binds topic 7 but asks a SEMANTIC question (does the built app match the intent — specs diffed against introspected reality). This playbook never diffs intent against reality; if you are judging coverage you are in the refinement lane. Scope honesty: the check set is the whole-application TYPECHECK across every package — the question 'does it compile as one program', which no per-task check can answer because the dispatch lane typechecks only the package a task mutated — PLUS the schema-plan drift gate (`check:schema-plan-in-sync`), which asks whether the modelled resources have migrations behind them. The second is not a variant of the first: on a PostgreSQL-backed application a table exists only because a migration built it, so a resource whose migration was never generated compiles green in every package and then refuses to boot on `postgresql_table_schema_mismatch` — invisible to a typecheck, because no type in the program knows whether a table exists. It is safe on MongoDB applications and on unbuilt trees because it resolves three outcomes (not adopted / could-not-ask / decided) rather than reading an exit code. Since #2228 it also asks the two questions a typecheck cannot: does each optional site BUILD (the website's `astro build`, the documentation portal's `docusaurus build`; an absent package answers 'nothing to build'), and does the configuration pass `wildo config validate` (errors fail, warnings do not, a missing CLI is 'we could not ask'); and it asks the RUNNING backend's readiness and renders the frontend in a browser, each reported unrun rather than passed when the stack is not up. Since #2404 it also builds the resources registry offline, as the backend's startup does (`check:resources-registry-init`), so a resource configuration the engine refuses at start is named before the running backend is asked. Since #2784 it also holds the website's drawn demos to the application (`check:website-demo-facts`), because a later resource change can make a landed drawing untrue. Since #3211 it also evaluates the specifications package as the companion does (`check:specification-exports`), so a specification its factory refuses — valid TypeScript, dropped from what the companion serves — is named. The whole test suite and OpenAPI/docs regeneration are NOT in this set.",
13
+ "intent": "Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over EVERY workspace package the application has (specifications, shared-lib, backend-api, frontend, and the website, technical documentation site, workers and minions it composed), derived from those packages rather than listed, OUTSIDE any coding agent, and reports a per-check outcome. It fixes NOTHING: a failure is surfaced for a refinement re-dispatch, which is a different playbook's job, and it authors no schemas and writes no code. Deliberately DISTINCT from the refinement phase's coverage audit, which also binds topic 7 but asks a SEMANTIC question (does the built app match the intent — specs diffed against introspected reality). This playbook never diffs intent against reality; if you are judging coverage you are in the refinement lane. Scope honesty: the check set is the whole-application TYPECHECK across every package — the question 'does it compile as one program', which no per-task check can answer because the dispatch lane typechecks only the package a task mutated — PLUS the schema-plan drift gate (`check:schema-plan-in-sync`), which asks whether the modelled resources have migrations behind them. The second is not a variant of the first: on a PostgreSQL-backed application a table exists only because a migration built it, so a resource whose migration was never generated compiles green in every package and then refuses to boot on `postgresql_table_schema_mismatch` — invisible to a typecheck, because no type in the program knows whether a table exists. It is safe on MongoDB applications and on unbuilt trees because it resolves three outcomes (not adopted / could-not-ask / decided) rather than reading an exit code. Since #2228 it also asks the two questions a typecheck cannot: does each optional site BUILD (the website's `astro build`, the documentation portal's `docusaurus build`; an absent package answers 'nothing to build'), and does the configuration pass `wildo config validate` (errors fail, warnings do not, a missing CLI is 'we could not ask'); and it asks the RUNNING backend's readiness and renders the frontend in a browser, each reported unrun rather than passed when the stack is not up. Since #2404 it also builds the resources registry offline, as the backend's startup does (`check:resources-registry-init`), so a resource configuration the engine refuses at start is named before the running backend is asked. Since #2784 it also holds the website's drawn demos to the application (`check:website-demo-facts`), because a later resource change can make a landed drawing untrue. Since #3211 it also evaluates the specifications package as the companion does (`check:specification-exports`), so a specification its factory refuses — valid TypeScript, dropped from what the companion serves — is named. Since #3904 it also holds every module's conventional files to the folders the framework reads them from (`check:module-layout`), so a misplacement a task's own check carried is asked once more. The whole test suite and OpenAPI/docs regeneration are NOT in this set.",
14
14
  "skillRefs": [
15
15
  "application-database-migrations"
16
16
  ],