@wildo-ai/framework-knowledge 1.1.15 → 1.1.16

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 (53) 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/creation-state.md +4 -1
  4. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  5. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  6. package/dist/esm/framework-knowledge.definitions.js +4 -0
  7. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  8. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  9. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +6 -4
  10. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  11. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  12. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  13. package/dist/knowledge/manifest.json +7 -7
  14. package/dist/knowledge/playbooks/bottom_up.build/method.md +10 -8
  15. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +1 -1
  16. package/dist/knowledge/references/backend.inbound-handlers.definition.md +2 -1
  17. package/dist/knowledge/references/example.electronic-signature.engagement-letter-tool.md +54 -0
  18. package/dist/knowledge/references/example.module.relationships.discriminator.md +7 -0
  19. package/dist/knowledge/references/saas.backend.flows-actors.decision-notice-handler.md +7 -0
  20. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +5 -0
  21. package/dist/knowledge/references/saas.backend.flows-actors.present-records-tool.md +5 -2
  22. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +19 -0
  23. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +21 -0
  24. package/dist/knowledge/references/saas.models.flows-actors.decision-card-wording.md +9 -0
  25. package/dist/knowledge/references/saas.models.flows.run-state.md +9 -0
  26. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  27. package/dist/knowledge/registries/framework-topics.json +11 -1
  28. package/dist/knowledge/registries/playbooks.json +1 -1
  29. package/dist/knowledge/registries/source-tags.json +1019 -1002
  30. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +20 -4
  31. package/dist/knowledge/skills/config-app-shell/SKILL.md +4 -0
  32. package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +2 -0
  33. package/dist/knowledge/skills/electronic-signature-deliverables/SKILL.md +58 -15
  34. package/dist/knowledge/skills/electronic-signature-deliverables/references/signing-inside-the-application.md +1 -1
  35. package/dist/knowledge/skills/electronic-signature-deliverables/references/what-makes-a-request-signed.md +32 -5
  36. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +5 -4
  37. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +5 -0
  38. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +15 -0
  39. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-present-records-tool-api.md +5 -2
  40. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-remote-a2a-agent-declaration-api.md +55 -17
  41. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +9 -0
  42. package/dist/knowledge/skills/human-decision-notices/SKILL.md +5 -1
  43. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-card-wording-api.md +9 -0
  44. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-notice-handler-api.md +7 -0
  45. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +2 -1
  46. package/dist/knowledge/skills/module-relationships/SKILL.md +7 -0
  47. package/dist/knowledge/skills/provider-backend-package/SKILL.md +19 -2
  48. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +21 -0
  49. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +5 -0
  50. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +19 -0
  51. package/dist/knowledge/topic-index.json +104 -70
  52. package/dist/tsconfig.build.tsbuildinfo +1 -1
  53. package/package.json +4 -4
@@ -1,11 +1,11 @@
1
1
  {
2
2
  "artifactVersion": "3",
3
- "frameworkVersion": "1.1.15",
4
- "generatorVersion": "1.1.15",
5
- "generatedAt": "2026-11-17T16:03:09.086Z",
3
+ "frameworkVersion": "1.1.16",
4
+ "generatorVersion": "1.1.16",
5
+ "generatedAt": "2026-11-18T19:00:50.034Z",
6
6
  "packageName": "@wildo-ai/framework-knowledge",
7
- "topicCount": 1074,
8
- "referenceFileCount": 931,
7
+ "topicCount": 1075,
8
+ "referenceFileCount": 932,
9
9
  "payload": {
10
10
  "topicIndexPath": "topic-index.json",
11
11
  "registriesDirectory": "registries",
@@ -21,13 +21,13 @@
21
21
  "registryName": "source-tags",
22
22
  "filePath": "registries/source-tags.json",
23
23
  "description": "Source-derived tag registry for extracted framework references.",
24
- "entryCount": 931
24
+ "entryCount": 932
25
25
  },
26
26
  {
27
27
  "registryName": "framework-topics",
28
28
  "filePath": "registries/framework-topics.json",
29
29
  "description": "Topic registry derived from extracted framework-knowledge tags.",
30
- "entryCount": 1074
30
+ "entryCount": 1075
31
31
  },
32
32
  {
33
33
  "registryName": "playbooks",
@@ -36,11 +36,12 @@ never a "done".
36
36
  - **`bottom_up.assemble-verify`** — does the built application assemble? The
37
37
  deterministic verification set over the application's packages and the migration
38
38
  drift probe.
39
- - **`top_down.expert-personas`** — the staffing step, here only to repair: a build task
40
- can change an input an expert's charter reads (the design system, for the art director
41
- and the design-system guardian), and a panel then refuses to seat the stale charter.
42
- The dispatch child runs it ITSELF after its wave (`staffingRepair` in its result) and the
43
- held steps run in the next wave, so you rarely select it.
39
+ - **`top_down.expert-personas`** — the staffing step, here only to repair: an input an
40
+ expert's charter reads can move during the build (the brand, the vision), and a panel then
41
+ refuses to seat the stale charter. The build's own changes to the design system and the
42
+ accepted mark do not make a charter stale while the build is unfinished. The dispatch child
43
+ starts the staffing step ITSELF the moment a step is held, beside its wave (`staffingRepair`
44
+ in its result), and the held steps run once it lands, so you rarely select it.
44
45
  - **`bottom_up.maturity-reading`** — what the built application is WORTH against the
45
46
  requirements it was asked to satisfy: which are addressed, by what evidence, and the
46
47
  stage that puts it at. This is what the lane ends on. Assembly says the code compiles;
@@ -65,9 +66,10 @@ between rounds unblocks its dependents without re-planning.
65
66
  runs as many tasks at once as the build parallelism allows. A second child in the same
66
67
  round would start a second wave beside it and double the width the person chose.
67
68
  - **Stale charters never end the lane.** A step whose panel refused them is held, every
68
- other task keeps running, and the dispatch child runs the staffing step after its wave.
69
- Keep dispatching. Select `top_down.expert-personas` yourself only when the dispatch
70
- result's `staffingRepair` says it failed and the staffing step is on offer.
69
+ other task keeps running, and the dispatch child starts the staffing step beside its wave.
70
+ Keep dispatching. `staffingRepair` with `inFlight` is not a failure: the staffing step is
71
+ still running, so never select it then. Select `top_down.expert-personas` yourself only
72
+ when `staffingRepair` says the staffing step failed and it is on offer.
71
73
  - **A parked question waits for the creator.** A coding run that parked on a question
72
74
  is answered on the creation surface; the task is re-dispatched when it is.
73
75
 
@@ -39,7 +39,7 @@
39
39
  }
40
40
  ],
41
41
  "method": {
42
- "guidance": "# The Build Lane — the umbrella\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook produces nothing itself. It drives the steps that BUILD the application\nfrom its accepted conception — the build plan, the dispatch of its tasks, the assembly\ncheck — and it will end on the maturity reading: a stage against the requirements,\nnever a \"done\".\n\n## The children, and why the order is not written here\n\n- **`bottom_up.build-decompose`** — the build plan: an ordered task graph over the\n domain plan, the placement plan, the roadmap and the requirements, each task bound to\n an application skill and to what it produces. Its own gate makes it ineligible once\n the plan is fully landed and nothing upstream has moved.\n- **`bottom_up.build-dispatch`** — one WAVE per run: up to the application's build\n parallelism of ready tasks at once (`wildo workbench parallelism`, 5 by default), each\n routed by its target — a coding run in the workspace, or a companion-owned generation\n step (labels, logo, emails, seeds). The runs share the worktree; the wave repairs what\n they overwrote in each other when they have settled, then reports every run's outcome.\n With a build parallelism of `1` it is one task per run. Lands no family, so it is\n offered again every round — that is the loop.\n- **`bottom_up.build-scale`** — the same act as dispatch: it declares the same executor\n and starts the same wave. Prefer `bottom_up.build-dispatch`; selecting scale instead\n gains nothing, and selecting both in one round would start two waves side by side.\n- **`bottom_up.assemble-verify`** — does the built application assemble? The\n deterministic verification set over the application's packages and the migration\n drift probe.\n- **`top_down.expert-personas`** — the staffing step, here only to repair: a build task\n can change an input an expert's charter reads (the design system, for the art director\n and the design-system guardian), and a panel then refuses to seat the stale charter.\n The dispatch child runs it ITSELF after its wave (`staffingRepair` in its result) and the\n held steps run in the next wave, so you rarely select it.\n- **`bottom_up.maturity-reading`** — what the built application is WORTH against the\n requirements it was asked to satisfy: which are addressed, by what evidence, and the\n stage that puts it at. This is what the lane ends on. Assembly says the code compiles;\n the reading says what the application has become.\n\nNothing above is a sequence. The plan needs the conception; dispatch needs the plan;\nassembly needs the plan. Readiness is re-derived from git each round, so a task accepted\nbetween rounds unblocks its dependents without re-planning.\n\n## Selecting the next child\n\n- **Decompose once.** Re-decompose only when the decomposer's gate says an input has\n moved since the plan landed, when dispatch reports a task that cannot land, or when the\n decomposer is offered again after its own judge found the plan does not cover the domain\n plan (marked RE-OPENED in the round history) — then in refine mode, keeping the refs of\n what has landed, and aimed at the criterion that faulted.\n- **Dispatch while tasks remain.** Each round's objective names the tasks the previous\n round's wave dispatched and how each came out — the dispatch child returns those\n outcomes, so read them rather than assuming. Once every task has landed, dispatch is no longer\n offered at all and the remaining child is assemble-verify.\n- **One child per round.** The parallelism is INSIDE the dispatch child: its wave already\n runs as many tasks at once as the build parallelism allows. A second child in the same\n round would start a second wave beside it and double the width the person chose.\n- **Stale charters never end the lane.** A step whose panel refused them is held, every\n other task keeps running, and the dispatch child runs the staffing step after its wave.\n Keep dispatching. Select `top_down.expert-personas` yourself only when the dispatch\n result's `staffingRepair` says it failed and the staffing step is on offer.\n- **A parked question waits for the creator.** A coding run that parked on a question\n is answered on the creation surface; the task is re-dispatched when it is.\n\n## Composing an objective for a child\n\nFor dispatch: the tasks the previous round's wave dispatched, their outcomes, and what\nthe tasks ready now are expected to produce. For a refine decomposition: the task that could\nnot land and why. For assembly: nothing to compose — it runs the declared checks.\n\n## When to stop\n\nStop on the maturity reading. It is the decision this lane ends on, and it names a\nSTAGE rather than a completion — there is no \"done\" for an application, only a\nmeasurement against its requirements that moves every time a later run lands something. Stop when dispatch has reported a task\nthat cannot land twice, or a parked question waits on the creator, and say which. A\nfull build takes several runs of this lane; each resumes where readiness now stands.\n\n## What the creator reviews\n\nEach dispatched task's work in the application workspace, through `git status`, and\nthe assembly verdict. A task lands when its product is in the working tree and its run's\nchecks passed; the companion's build checkpoints commit it under the automatic posture, and\nunder a reviewing posture acceptance is the person's commit.\n",
42
+ "guidance": "# The Build Lane — the umbrella\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook produces nothing itself. It drives the steps that BUILD the application\nfrom its accepted conception — the build plan, the dispatch of its tasks, the assembly\ncheck — and it will end on the maturity reading: a stage against the requirements,\nnever a \"done\".\n\n## The children, and why the order is not written here\n\n- **`bottom_up.build-decompose`** — the build plan: an ordered task graph over the\n domain plan, the placement plan, the roadmap and the requirements, each task bound to\n an application skill and to what it produces. Its own gate makes it ineligible once\n the plan is fully landed and nothing upstream has moved.\n- **`bottom_up.build-dispatch`** — one WAVE per run: up to the application's build\n parallelism of ready tasks at once (`wildo workbench parallelism`, 5 by default), each\n routed by its target — a coding run in the workspace, or a companion-owned generation\n step (labels, logo, emails, seeds). The runs share the worktree; the wave repairs what\n they overwrote in each other when they have settled, then reports every run's outcome.\n With a build parallelism of `1` it is one task per run. Lands no family, so it is\n offered again every round — that is the loop.\n- **`bottom_up.build-scale`** — the same act as dispatch: it declares the same executor\n and starts the same wave. Prefer `bottom_up.build-dispatch`; selecting scale instead\n gains nothing, and selecting both in one round would start two waves side by side.\n- **`bottom_up.assemble-verify`** — does the built application assemble? The\n deterministic verification set over the application's packages and the migration\n drift probe.\n- **`top_down.expert-personas`** — the staffing step, here only to repair: an input an\n expert's charter reads can move during the build (the brand, the vision), and a panel then\n refuses to seat the stale charter. The build's own changes to the design system and the\n accepted mark do not make a charter stale while the build is unfinished. The dispatch child\n starts the staffing step ITSELF the moment a step is held, beside its wave (`staffingRepair`\n in its result), and the held steps run once it lands, so you rarely select it.\n- **`bottom_up.maturity-reading`** — what the built application is WORTH against the\n requirements it was asked to satisfy: which are addressed, by what evidence, and the\n stage that puts it at. This is what the lane ends on. Assembly says the code compiles;\n the reading says what the application has become.\n\nNothing above is a sequence. The plan needs the conception; dispatch needs the plan;\nassembly needs the plan. Readiness is re-derived from git each round, so a task accepted\nbetween rounds unblocks its dependents without re-planning.\n\n## Selecting the next child\n\n- **Decompose once.** Re-decompose only when the decomposer's gate says an input has\n moved since the plan landed, when dispatch reports a task that cannot land, or when the\n decomposer is offered again after its own judge found the plan does not cover the domain\n plan (marked RE-OPENED in the round history) — then in refine mode, keeping the refs of\n what has landed, and aimed at the criterion that faulted.\n- **Dispatch while tasks remain.** Each round's objective names the tasks the previous\n round's wave dispatched and how each came out — the dispatch child returns those\n outcomes, so read them rather than assuming. Once every task has landed, dispatch is no longer\n offered at all and the remaining child is assemble-verify.\n- **One child per round.** The parallelism is INSIDE the dispatch child: its wave already\n runs as many tasks at once as the build parallelism allows. A second child in the same\n round would start a second wave beside it and double the width the person chose.\n- **Stale charters never end the lane.** A step whose panel refused them is held, every\n other task keeps running, and the dispatch child starts the staffing step beside its wave.\n Keep dispatching. `staffingRepair` with `inFlight` is not a failure: the staffing step is\n still running, so never select it then. Select `top_down.expert-personas` yourself only\n when `staffingRepair` says the staffing step failed and it is on offer.\n- **A parked question waits for the creator.** A coding run that parked on a question\n is answered on the creation surface; the task is re-dispatched when it is.\n\n## Composing an objective for a child\n\nFor dispatch: the tasks the previous round's wave dispatched, their outcomes, and what\nthe tasks ready now are expected to produce. For a refine decomposition: the task that could\nnot land and why. For assembly: nothing to compose — it runs the declared checks.\n\n## When to stop\n\nStop on the maturity reading. It is the decision this lane ends on, and it names a\nSTAGE rather than a completion — there is no \"done\" for an application, only a\nmeasurement against its requirements that moves every time a later run lands something. Stop when dispatch has reported a task\nthat cannot land twice, or a parked question waits on the creator, and say which. A\nfull build takes several runs of this lane; each resumes where readiness now stands.\n\n## What the creator reviews\n\nEach dispatched task's work in the application workspace, through `git status`, and\nthe assembly verdict. A task lands when its product is in the working tree and its run's\nchecks passed; the companion's build checkpoints commit it under the automatic posture, and\nunder a reviewing posture acceptance is the person's commit.\n",
43
43
  "skillRefs": [],
44
44
  "skillBodyRefs": [],
45
45
  "derivedFromAnswers": [],
@@ -264,7 +264,8 @@ export type InboundChatDecisionAnswer =
264
264
  readonly outcome: HumanDecision_ActOutcome;
265
265
  /**
266
266
  * #2923: where the person answers this decision instead, when a chat answer cannot settle it (it requires a step-up,
267
- * which a chat answer cannot carry, or its kind does not admit a chat answer): the decision's address in the
267
+ * which a chat answer cannot carry, its kind does not admit a chat answer, or, #2797, the person is a representative
268
+ * whose granting organization asks a second factor a chat cannot prove): the decision's address in the
268
269
  * application's inbox. Present exactly then, and when the application has a public address. A handler posts it as
269
270
  * the message's link (`openInApplication`), never a refusal with nowhere to go.
270
271
  */
@@ -0,0 +1,54 @@
1
+ # example.electronic-signature.engagement-letter-tool
2
+
3
+
4
+ ## Usage Example
5
+
6
+ ```typescript
7
+ const RequestEngagementLetterSignature_InputSchema = z.object({
8
+ engagementId: z.string().min(1).describe('The engagement. Resolve it with resource.engagements.read.'),
9
+ letterFileId: z.string().min(1).max(200)
10
+ .describe('The id of the engagement\'s letter PDF: `engagementLetter.fileId` as resource.engagements.read returned it. The client signs this file, byte for byte.'),
11
+ });
12
+ type RequestEngagementLetterSignature_Input = z.infer<typeof RequestEngagementLetterSignature_InputSchema>;
13
+
14
+ /** The engagement's fields the client approves beside the letter: shown on the card and committed to by the seal. */
15
+ export const ENGAGEMENT_LETTER_SEALED_FIELDS = ['engagementReference', 'services', 'closeCadence', 'startsOn', 'endsOn'] as const;
16
+
17
+ export const requestEngagementLetterSignatureTool: FunctionTool = {
18
+ functionRef: REQUEST_ENGAGEMENT_LETTER_SIGNATURE_TOOL_REF,
19
+ authority: {
20
+ kind: FunctionToolAuthorityKind.NO_APPLICATION_DATA,
21
+ reason: 'It reads and writes nothing: once the client approves, the engine itself sends the approved letter for signature.',
22
+ },
23
+ effect: FunctionToolEffect.WRITE,
24
+ description:
25
+ 'Ask the client to sign the engagement letter electronically. Pass the engagement id and the id of its letter PDF '
26
+ + '(engagementLetter.fileId from resource.engagements.read); the firm uploads the letter on the engagement first. '
27
+ + 'The client\'s administrator approves the letter, then signs it inside the application, on the engagement\'s page. '
28
+ + 'Call it only when the user asks, then say it is waiting for the client\'s administrator.',
29
+ inputSchema: RequestEngagementLetterSignature_InputSchema,
30
+ personalDataOutput: {
31
+ kind: FunctionToolPersonalDataOutputKind.NOT_FROM_RECORDS,
32
+ reason: 'It returns the two ids it was called with and a fixed sentence; it reads no record.',
33
+ },
34
+ humanApproval: {
35
+ route: HumanDecision_RouteKind.ROLE,
36
+ eligibleRole: CORE_ORG_ROLES.ORG_ADMIN,
37
+ // Signing commits the client to the mandate.
38
+ riskLevel: ResourceOperationRiskLevel.HIGH,
39
+ },
40
+ argumentsResource: { resourceType: ClientEngagements_ResourceType.ENGAGEMENTS, rowIdArgument: 'engagementId' },
41
+ deliverableFileArgument: 'letterFileId',
42
+ sealedRecordFields: ENGAGEMENT_LETTER_SEALED_FIELDS,
43
+ // A letter re-issued and approved again replaces the earlier approval of the same engagement.
44
+ approvalReplacesEarlierApprovalOfRow: true,
45
+ electronicSignature: { requiredLevel: ElectronicSignature_Level.SIMPLE, signers: [FunctionTool_SignerSource.APPROVER] },
46
+ execute: async (args: RequestEngagementLetterSignature_Input) => ({
47
+ engagementId: args.engagementId,
48
+ letterFileId: args.letterFileId,
49
+ // What happens next is the engine's, within minutes and not here: the approved letter is sent for the approver's
50
+ // signature. Said as what WILL happen, never as done.
51
+ next: 'The client\'s administrator approved the letter. The application sends it for their signature within a few minutes; they sign it on the engagement\'s page.',
52
+ }),
53
+ };
54
+ ```
@@ -10,6 +10,13 @@
10
10
  {
11
11
  nature: RelationshipNature.COMPOSITION,
12
12
  foreignKeyField: 'todoId',
13
+ // OPTIONAL_CONTEXT, as for tasks: an occurrence is routed under its todo (the todo page lists them) AND directly
14
+ // under its organization, `/organizations/{organizationId}/todos-recurring-occurrences/{todosRecurringOccurrenceId}`.
15
+ // A record shown by id alone needs the second: the Todo Assistant's cards (`presentRecordsTool`) know the
16
+ // organization and the record, never its todo, so with only the nested route a card read "Unavailable" (no
17
+ // endpoint) and opened nothing (#4011). Every occurrence carries its own `organizationId` (the anchor above), so the
18
+ // organization-level route is confined by tenancy like every other organization resource.
19
+ accessScopeStrategy: ResourceRelationshipAccessScopeStrategy.OPTIONAL_CONTEXT,
13
20
  // Static discriminator: only applies when parent todo is RECURRING
14
21
  discriminator: { discriminatorField: todosRecurringTypeField, values: [Todos_RecurrenceType.RECURRING] },
15
22
  // LAZY: a recurring todo gains an occurrence every time it comes due, so a daily todo's set only grows, and deleting
@@ -200,6 +200,13 @@ export interface HumanDecisionNoticeContext {
200
200
  * `language` from the application's labels. A missing label shows its key.
201
201
  */
202
202
  readonly words: HumanDecisionNoticeWords;
203
+ /**
204
+ * The decision's address in the application's Decisions inbox (the frontend's public URL and the inbox path), for the
205
+ * link a card carries: a decision that asks fields, or has more options than a card shows, is answered there, so its
206
+ * card is that link alone (the Slack and Teams helpers' `openInApplication`). `undefined` in a process that knows no
207
+ * frontend it can name: post no link then, rather than invent one.
208
+ */
209
+ readonly decisionUrl: (decisionRef: string) => string | undefined;
203
210
  }
204
211
 
205
212
  /** The retry an application may tune. */
@@ -329,6 +329,11 @@ export interface FunctionTool {
329
329
  * you write by hand, whose input would not read back as records.
330
330
  */
331
331
  presentsRecords?: boolean;
332
+ /**
333
+ * The resources whose records the tool SHOWS as cards. Set by {@link presentRecordsTool}; registration refuses one a card
334
+ * cannot read ({@link presentRecordsAddressabilityProblems}, #4011).
335
+ */
336
+ presentedResourceTypes?: readonly ResourceType[];
332
337
  /**
333
338
  * The resources the tool SEARCHES through the retrieval index (#2300). Set by {@link retrievalTool}; startup refuses an
334
339
  * application whose retrieval tool names a resource that declares no `.ragSource()` field, which would otherwise
@@ -43,8 +43,10 @@ export const PRESENT_RECORDS_FUNCTION_REF = 'engine.present-records';
43
43
  * conversation's text only), so it reads a record again before acting on it.
44
44
  *
45
45
  * `resourceTypes` are the resources the agent may show. Grant only resources it can already read. Each needs a READ
46
- * operation reachable over HTTP, and its summary is the resource's authored summary layout, else the engine's default
47
- * from its summary fields.
46
+ * operation reachable over HTTP by the record's id and its tenancy alone, since a card knows no parent of its record:
47
+ * a resource routed only under a parent (`REQUIRES_CONTEXT`) is refused at startup, so route it under its tenancy too
48
+ * with `accessScopeStrategy: OPTIONAL_CONTEXT` on the parent edge. Its summary is the resource's authored summary
49
+ * layout, else the engine's default from its summary fields.
48
50
  *
49
51
  * Import path: `@wildo-ai/saas-backend-lib`.
50
52
  *
@@ -73,6 +75,7 @@ export function presentRecordsTool(options: {
73
75
  }),
74
76
  effect: FunctionToolEffect.READ,
75
77
  presentsRecords: true,
78
+ presentedResourceTypes: resourceTypes,
76
79
  personalDataOutput: { kind: FunctionToolPersonalDataOutputKind.NOT_FROM_RECORDS, reason: 'It returns which record ids were shown or unavailable, never their fields.' },
77
80
  authority: { kind: FunctionToolAuthorityKind.PRINCIPAL_RESOURCE_OPERATION },
78
81
  execute: async (args: PresentRecords_ToolInput, ctx: FunctionToolExecutionContext): Promise<PresentRecords_ToolResult> => {
@@ -122,6 +122,20 @@ export interface ResourceCompositeViewAuthoringConfig extends CompositeViewAutho
122
122
  * silently.
123
123
  */
124
124
  operationLike?: CoreResourceOperation;
125
+ /**
126
+ * The actor system whose conversations this view hosts ON ITS RECORD (#4043): the `systemRef` of the
127
+ * `FlowsActorsView` it renders with the record in that view's context.
128
+ *
129
+ * A conversation opened on a record is listed only there, so a link to it (a notice, an email: the
130
+ * conversation-link page) must open THIS view on that record rather than the system's standalone view, which
131
+ * lists another context. Declaring the system is what lets the engine find this view from a conversation, and it
132
+ * hands the linked conversation to the `FlowsActorsView` of that system inside it — the view's component passes
133
+ * nothing for it.
134
+ *
135
+ * Omitted when the view hosts no conversation. Resource composites only: an application-level view has no record,
136
+ * so its conversations are the standalone view's.
137
+ */
138
+ conversationSystemRef?: string;
125
139
  }
126
140
 
127
141
  export interface CompositeViewDefinition {
@@ -158,6 +172,11 @@ export interface CompositeViewDefinition {
158
172
  zoneContentMaxWidth?: ResponsiveMaxWidth;
159
173
  /** See {@link CompositeViewAuthoringConfig.zoneContentFillsHeight}. Mirrored from authoring. */
160
174
  zoneContentFillsHeight?: boolean;
175
+ /**
176
+ * See {@link ResourceCompositeViewAuthoringConfig.conversationSystemRef}. Mirrored from a RESOURCE composite's
177
+ * authoring by the registry, which is not Zod-parsed; an application-level definition never carries it.
178
+ */
179
+ conversationSystemRef?: string;
161
180
  }
162
181
 
163
182
  export type AppCompositeViewsConfig = Record<string, CompositeViewAuthoringConfig>;
@@ -234,6 +234,18 @@ export enum EngineSettingsDestinationRef {
234
234
  * owner/admin, the roles that bind a client to an agent.
235
235
  */
236
236
  AUTONOMOUS_AGENTS = 'autonomous-agents',
237
+ /**
238
+ * What THIS organization's declared FLOWS and ACTOR SYSTEMS did (#3990): every run on the actor plane, newest first,
239
+ * and each run's history, its tasks (what each actor was asked and produced) and, for a flow, the steps it went
240
+ * through, each with when it happened, in the reader's time zone. Org owner/admin, the people the route admits (an
241
+ * administrator of the organization through an organization-wide role, or the application super-administrator).
242
+ *
243
+ * Beside {@link AGENT_RUNS}, never merged into it: those are CONVERSATIONS (a chat, an A2A client's turn) with their
244
+ * transcripts, read under the execution resource's roles; these are the runs of declared systems, which no resource
245
+ * routes. No capability gate: a flow runs with no language model, so an application declaring flows and no
246
+ * `AI_LLM` still has activity to read; one declaring neither shows an empty list, and may remove the placement.
247
+ */
248
+ AGENT_ACTIVITY = 'agent-activity',
237
249
  /**
238
250
  * Which of the application's chat agents answers the organization's people on each chat connection (#2665): Slack,
239
251
  * Microsoft Teams. Org owner/admin, the roles the `organizationChatSettings` writes accept. A connection with no choice
@@ -363,6 +375,15 @@ export enum EngineSettingsDestinationRef {
363
375
  * application row. What a run consumed is answered to an application cost reader by the run's `usage` operation.
364
376
  */
365
377
  APPLICATION_AGENT_RUNS = 'application-agent-runs',
378
+ /**
379
+ * What the declared flows and actor systems did in EVERY organization (#3990): the same page as
380
+ * {@link AGENT_ACTIVITY}, across tenants, each run naming the organization it worked for. An APPLICATION-WIDE read, so
381
+ * it is admitted under the application's audit read policy (`resolveAuditApplicationReadAccess`): the
382
+ * super-administrator role alone under ROLE_BASED, and a live application access grant a second administrator signed
383
+ * under INDEPENDENT_APPROVAL. Every read is recorded (`PLATFORM_DIRECTORY_ACCESS`, naming the grant when there is one).
384
+ * Super-admin, the role the route admits.
385
+ */
386
+ APPLICATION_AGENT_ACTIVITY = 'application-agent-activity',
366
387
  /**
367
388
  * Which agents the application's super-administrator switched off for EVERY organization (#2843), each with the
368
389
  * justification it was suspended with, and the Suspend and Resume actions. Super-admin, the role both verbs require;
@@ -78,6 +78,15 @@ export type HumanDecisionPhrase =
78
78
  | { readonly kind: HumanDecisionPhraseKind.TOOL; readonly toolName: string }
79
79
  | { readonly kind: HumanDecisionPhraseKind.RESOURCE_OPERATION; readonly resourceType: string; readonly operationIdentifier: string };
80
80
 
81
+ /**
82
+ * The words of the button a chat copy of a decision carries when it is answered in the application only (#2797): a
83
+ * decision that asks values, or has more options than a card shows. What a decision-notice handler passes to its
84
+ * vendor helper's `openInApplication`, beside `ctx.decisionUrl(decisionRef)`.
85
+ */
86
+ export function humanDecisionOpenInApplicationPhrase(): HumanDecisionPhrase {
87
+ return { kind: HumanDecisionPhraseKind.LABEL, labelRef: 'noticeOpenInApplication' };
88
+ }
89
+
81
90
  /** The full key a LABEL, ROLE or TOOL phrase names in an application's label tree; `undefined` for TEXT, which names none. */
82
91
  export function humanDecisionPhraseLabelKey(phrase: HumanDecisionPhrase): string | undefined {
83
92
  switch (phrase.kind) {
@@ -14,6 +14,15 @@ export const FlowRun_NodeStateSchema = z.object({
14
14
  nodeType: z.enum(Flow_Node_Type),
15
15
  nodeRef: z.string().min(1),
16
16
  status: z.enum(FlowsActors_Status),
17
+ /**
18
+ * When the node took the status it carries, as an ISO instant (#3990): the trigger and a finish when the run reached
19
+ * them, a step when it completed, failed or began waiting, and a waiting step again when its question was answered or
20
+ * the run ended there. What the Agent activity page's flow timeline shows, in the reader's time zone.
21
+ *
22
+ * Optional because a run written before it was recorded carries none; a reader shows such a node without a time
23
+ * rather than inventing one.
24
+ */
25
+ statusAt: z.iso.datetime().optional(),
17
26
  /** What the step produced (a STEP that completed), JSON-safe. */
18
27
  output: z.json().optional(),
19
28
  /** Why the step failed, in words for the person reading the run (never a stack). */
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "assurance-authority-bases",
3
3
  "metadata": {
4
- "generatedAt": "2026-11-17T16:03:09.086Z",
4
+ "generatedAt": "2026-11-18T19:00:50.034Z",
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-17T16:03:09.086Z",
4
+ "generatedAt": "2026-11-18T19:00:50.034Z",
5
5
  "description": "Topic registry derived from extracted framework-knowledge tags."
6
6
  },
7
7
  "entries": {
@@ -792,6 +792,16 @@
792
792
  "referenceFilePath": "references/example.data-seeding.row-reference.md",
793
793
  "sourceReferenceCount": 1
794
794
  },
795
+ "example.electronic-signature.engagement-letter-tool": {
796
+ "topicId": "example.electronic-signature.engagement-letter-tool",
797
+ "title": "Example Electronic Signature Engagement Letter Tool",
798
+ "categories": [
799
+ "example",
800
+ "example.electronic-signature"
801
+ ],
802
+ "referenceFilePath": "references/example.electronic-signature.engagement-letter-tool.md",
803
+ "sourceReferenceCount": 1
804
+ },
795
805
  "example.email.template.minimal": {
796
806
  "topicId": "example.email.template.minimal",
797
807
  "title": "Example Email Template Minimal",
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "playbooks",
3
3
  "metadata": {
4
- "generatedAt": "2026-11-17T16:03:09.086Z",
4
+ "generatedAt": "2026-11-18T19:00:50.034Z",
5
5
  "description": "Compiled meta-workflow playbooks (app-creation methodology definitions)."
6
6
  },
7
7
  "entries": {