@wildo-ai/framework-knowledge 1.1.12 → 1.1.13

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 (60) 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 +10 -0
  6. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  7. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +2 -1
  8. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  9. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +8 -1
  10. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  11. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  12. package/dist/knowledge/manifest.json +7 -7
  13. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +5 -2
  14. package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +9 -0
  15. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +1 -1
  16. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +14 -0
  17. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +1 -1
  18. package/dist/knowledge/references/application-maturity.config.md +43 -0
  19. package/dist/knowledge/references/example.infra.environment-config.local.md +2 -2
  20. package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +21 -0
  21. package/dist/knowledge/references/platform.config.infrastructure-host.md +1 -0
  22. package/dist/knowledge/references/platform.config.platform-key-management.md +5 -2
  23. package/dist/knowledge/references/requirements.engine-substance.md +38 -0
  24. package/dist/knowledge/references/requirements.functional-requirement.config.md +11 -0
  25. package/dist/knowledge/references/requirements.non-functional-requirement.config.md +11 -0
  26. package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +20 -0
  27. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +72 -0
  28. package/dist/knowledge/references/saas.frontend.chart-dashboard-view.md +3 -3
  29. package/dist/knowledge/references/saas.frontend.chart-dashboard.md +38 -35
  30. package/dist/knowledge/references/saas.models.chart-dashboard-tile-sizes.md +40 -0
  31. package/dist/knowledge/references/saas.models.flows-actors.agent-content-guardrails-environment.md +52 -0
  32. package/dist/knowledge/references/saas.models.organization-dashboard-layout.md +61 -0
  33. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  34. package/dist/knowledge/registries/framework-topics.json +41 -1
  35. package/dist/knowledge/registries/playbooks.json +1 -1
  36. package/dist/knowledge/registries/source-tags.json +1052 -982
  37. package/dist/knowledge/skills/backend-custom-operation/references/framework-hook-transaction-posture-api.md +11 -0
  38. package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +43 -0
  39. package/dist/knowledge/skills/electronic-signature-deliverables/references/what-makes-a-request-signed.md +20 -3
  40. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +12 -2
  41. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +16 -4
  42. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +144 -6
  43. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +72 -0
  44. package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +12 -2
  45. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +12 -2
  46. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +1 -1
  47. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +3 -2
  48. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +13 -0
  49. package/dist/knowledge/skills/infra-environment-config/SKILL.md +26 -2
  50. package/dist/knowledge/skills/infra-environment-config/references/framework-agent-content-guardrails-environment-api.md +67 -0
  51. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +1 -0
  52. package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +5 -2
  53. package/dist/knowledge/skills/provider-backend-package/SKILL.md +17 -3
  54. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +2 -1
  55. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +21 -0
  56. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +1 -1
  57. package/dist/knowledge/skills/views-composite-authoring/references/framework-chart-dashboard-api.md +166 -39
  58. package/dist/knowledge/topic-index.json +197 -58
  59. package/dist/tsconfig.build.tsbuildinfo +1 -1
  60. package/package.json +4 -4
@@ -1,11 +1,11 @@
1
1
  {
2
2
  "artifactVersion": "3",
3
- "frameworkVersion": "1.1.12",
4
- "generatorVersion": "1.1.12",
5
- "generatedAt": "2026-11-12T14:36:04.596Z",
3
+ "frameworkVersion": "1.1.13",
4
+ "generatorVersion": "1.1.13",
5
+ "generatedAt": "2026-11-14T09:36:56.594Z",
6
6
  "packageName": "@wildo-ai/framework-knowledge",
7
- "topicCount": 1066,
8
- "referenceFileCount": 923,
7
+ "topicCount": 1070,
8
+ "referenceFileCount": 927,
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": 923
24
+ "entryCount": 927
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": 1066
30
+ "entryCount": 1070
31
31
  },
32
32
  {
33
33
  "registryName": "playbooks",
@@ -73,12 +73,15 @@
73
73
  },
74
74
  {
75
75
  "ref": "operating-entity",
76
- "question": "Which legal entity operates this service? Give the parts you know, each on its own line (or separated by `;`) and labelled: `name: <registered company name>`, `address: <registered address>`, `privacy contact: <the email, URL or postal address a person uses to reach you about privacy>`. Answer only the parts you actually know today — anything you leave out is recorded as outstanding and nothing is blocked by it. Do NOT supply a placeholder or a plausible-looking value: a produced privacy notice quotes these as fact, and the address is what a person would use to serve a legal request on a real company.",
76
+ "question": "Which legal entity operates this service? Give the parts you know, each on its own line (or separated by `;`) and labelled: `name: <registered company name>`, `address: <registered address>`, `privacy contact: <the email, URL or postal address a person uses to reach you about privacy>`. Answer only the parts you actually know today — anything you leave out is recorded as outstanding and nothing is blocked by it. If you know none of them yet (no company exists), defer the question rather than answer it. Do NOT supply a placeholder or a plausible-looking value: a produced privacy notice quotes these as fact, and the address is what a person would use to serve a legal request on a real company.",
77
77
  "kind": "free_text",
78
78
  "answerFormat": "operator_identity_parts",
79
79
  "depth": "essential",
80
80
  "whenUnknown": "ask",
81
- "regulatedDomain": true
81
+ "regulatedDomain": true,
82
+ "nonAnswers": [
83
+ "deferred"
84
+ ]
82
85
  },
83
86
  {
84
87
  "ref": "operating-jurisdictions",
@@ -47,6 +47,15 @@ the task that reported it, and the follow-up task the build host derived to answ
47
47
  when its follow-up lands with nothing left to report, or when a landed later run states the
48
48
  requirement met.
49
49
 
50
+ A requirement the application's CONFIGURATION does not meet also reads at most `BUILT`. A requirement
51
+ declares what it cannot be met without (`engineCapabilities`, `languages`), and the reading compares
52
+ that with the capabilities `wildo.saas.config.ts` enables and the languages it serves. Each one that
53
+ is off is a configuration gap on the row, naming where to set it. A requirement that declares a need
54
+ while the configuration cannot be read is not called proven either.
55
+
56
+ The unattended drive calls the creation's goal reached only when no requirement carries an open item:
57
+ nothing addresses it, no build work for it landed, a reported gap, or a configuration gap.
58
+
50
59
  The ladder is ordered, and the stage is the highest one whose threshold the population meets. The
51
60
  default threshold is **every requirement at that level** — one number, and not a guess: a share
52
61
  below 1 would be an invented tolerance, and this family measures rather than flatters.
@@ -50,7 +50,7 @@
50
50
  ],
51
51
  "stepOutputs": [],
52
52
  "method": {
53
- "guidance": "# Maturity Reading — Where This Application Stands\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\n## What this step does\n\nThe build lane ends on four typechecks and a migration-drift probe, and its own method says it \"does\nnot boot the application, run its test suite\". Nothing related what was BUILT to what the\napplication's requirements ASKED FOR.\n\nThis step records that relation as the `application-maturity` family: **one row per requirement the\napplication declares**, the evidence that exists for it, and the stage that follows.\n\n## There is no \"done\", and that is the design\n\nThe highest stage does not mean finished. It means that today, every requirement has the strongest\nevidence this framework can produce for it — and the next requirement somebody writes lowers the\nreading again, with no code change anywhere. That is what the measurement is FOR.\n\nSo nothing in the lane may gate on this family, and no other step may read a stage as permission.\n\n## It is derived, never judged\n\nNothing here is an opinion, and no model produces it. Each row's level is reached by a measurement:\n\n| level | reached when | measured from |\n|---|---|---|\n| `UNADDRESSED` | nothing the application decided points at the requirement | the decided-element graph |\n| `DECIDED` | a decided element links to it — a feature draft, an experience surface, a worker, a build task | inbound links on the same graph |\n| `BUILT` | a build task addressing it has LANDED | the landing probe, over the working tree |\n| `VERIFIED` | that landed task's declared product was PROVEN | the same probe, minus what it could not verify |\n| `OBSERVED` | something watched the running application do it | runtime observations |\n\nA requirement a coding run still REPORTS unmet reads at most `BUILT`, whatever the probe found. The\nrun that built the work said what is missing, so its file is not proof. The row lists each open gap,\nthe task that reported it, and the follow-up task the build host derived to answer it. A gap closes\nwhen its follow-up lands with nothing left to report, or when a landed later run states the\nrequirement met.\n\nThe ladder is ordered, and the stage is the highest one whose threshold the population meets. The\ndefault threshold is **every requirement at that level** — one number, and not a guess: a share\nbelow 1 would be an invented tolerance, and this family measures rather than flatters.\n\n## The denominator is the requirements family, and nothing else\n\nEvery row comes from `requirements`, functional and non-functional, in its own order. Not the\nrequirements that happen to be referenced somewhere, not a count of build tasks, not a share of\nfiles. A requirement nothing addresses is a ROW at `UNADDRESSED` — visible, counted, and lowering\nthe reading.\n\nThat is the difference between a measurement and a file count: a denominator you choose yourself is\nnot a measurement at all.\n\n## A family that addresses requirements joins on its own\n\n\"Which elements address this requirement\" is read from the decided-element graph's inbound links, so\nevery family that declares an edge to `requirements.functional` or `requirements.non-functional`\nalready contributes — and one that declares such an edge tomorrow contributes without this method,\nor the derivation, knowing it exists.\n\n## What the reading says that a number cannot\n\nFour findings, and each names the application rather than the artifact:\n\n- a requirement **nothing addresses** — the reading's whole point;\n- a requirement whose build work **landed and could not be proven**, so its evidence stops at\n `BUILT`. A task that declares no product cannot be probed, and that is a known, deliberate state\n rather than a failure;\n- a requirement a coding run still **reports partly unmet**, naming what is missing and the\n follow-up that answers it. It stops at `BUILT` until that gap closes;\n- **no runtime observation exists at all**, which today is true of every application. The finding\n names what would fill it — an engine-behaviour e2e scenario that names the requirement it\n exercises — rather than leaving the top of the ladder quietly empty.\n\n## What you emit\n\n- The **maturity reading** at `specifications/src/application-maturity/index.ts`. It is landed by\n the runner, not written by hand.\n\n## Verification\n\n- The row count equals the number of requirements the application declares.\n- Every `requirementRef` names a requirement in the `requirements` family.\n- `rg -c \"UNADDRESSED\" specifications/src/application-maturity/index.ts` — how many requirements\n nothing has picked up yet.\n",
53
+ "guidance": "# Maturity Reading — Where This Application Stands\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\n## What this step does\n\nThe build lane ends on four typechecks and a migration-drift probe, and its own method says it \"does\nnot boot the application, run its test suite\". Nothing related what was BUILT to what the\napplication's requirements ASKED FOR.\n\nThis step records that relation as the `application-maturity` family: **one row per requirement the\napplication declares**, the evidence that exists for it, and the stage that follows.\n\n## There is no \"done\", and that is the design\n\nThe highest stage does not mean finished. It means that today, every requirement has the strongest\nevidence this framework can produce for it — and the next requirement somebody writes lowers the\nreading again, with no code change anywhere. That is what the measurement is FOR.\n\nSo nothing in the lane may gate on this family, and no other step may read a stage as permission.\n\n## It is derived, never judged\n\nNothing here is an opinion, and no model produces it. Each row's level is reached by a measurement:\n\n| level | reached when | measured from |\n|---|---|---|\n| `UNADDRESSED` | nothing the application decided points at the requirement | the decided-element graph |\n| `DECIDED` | a decided element links to it — a feature draft, an experience surface, a worker, a build task | inbound links on the same graph |\n| `BUILT` | a build task addressing it has LANDED | the landing probe, over the working tree |\n| `VERIFIED` | that landed task's declared product was PROVEN | the same probe, minus what it could not verify |\n| `OBSERVED` | something watched the running application do it | runtime observations |\n\nA requirement a coding run still REPORTS unmet reads at most `BUILT`, whatever the probe found. The\nrun that built the work said what is missing, so its file is not proof. The row lists each open gap,\nthe task that reported it, and the follow-up task the build host derived to answer it. A gap closes\nwhen its follow-up lands with nothing left to report, or when a landed later run states the\nrequirement met.\n\nA requirement the application's CONFIGURATION does not meet also reads at most `BUILT`. A requirement\ndeclares what it cannot be met without (`engineCapabilities`, `languages`), and the reading compares\nthat with the capabilities `wildo.saas.config.ts` enables and the languages it serves. Each one that\nis off is a configuration gap on the row, naming where to set it. A requirement that declares a need\nwhile the configuration cannot be read is not called proven either.\n\nThe unattended drive calls the creation's goal reached only when no requirement carries an open item:\nnothing addresses it, no build work for it landed, a reported gap, or a configuration gap.\n\nThe ladder is ordered, and the stage is the highest one whose threshold the population meets. The\ndefault threshold is **every requirement at that level** — one number, and not a guess: a share\nbelow 1 would be an invented tolerance, and this family measures rather than flatters.\n\n## The denominator is the requirements family, and nothing else\n\nEvery row comes from `requirements`, functional and non-functional, in its own order. Not the\nrequirements that happen to be referenced somewhere, not a count of build tasks, not a share of\nfiles. A requirement nothing addresses is a ROW at `UNADDRESSED` — visible, counted, and lowering\nthe reading.\n\nThat is the difference between a measurement and a file count: a denominator you choose yourself is\nnot a measurement at all.\n\n## A family that addresses requirements joins on its own\n\n\"Which elements address this requirement\" is read from the decided-element graph's inbound links, so\nevery family that declares an edge to `requirements.functional` or `requirements.non-functional`\nalready contributes — and one that declares such an edge tomorrow contributes without this method,\nor the derivation, knowing it exists.\n\n## What the reading says that a number cannot\n\nFour findings, and each names the application rather than the artifact:\n\n- a requirement **nothing addresses** — the reading's whole point;\n- a requirement whose build work **landed and could not be proven**, so its evidence stops at\n `BUILT`. A task that declares no product cannot be probed, and that is a known, deliberate state\n rather than a failure;\n- a requirement a coding run still **reports partly unmet**, naming what is missing and the\n follow-up that answers it. It stops at `BUILT` until that gap closes;\n- **no runtime observation exists at all**, which today is true of every application. The finding\n names what would fill it — an engine-behaviour e2e scenario that names the requirement it\n exercises — rather than leaving the top of the ladder quietly empty.\n\n## What you emit\n\n- The **maturity reading** at `specifications/src/application-maturity/index.ts`. It is landed by\n the runner, not written by hand.\n\n## Verification\n\n- The row count equals the number of requirements the application declares.\n- Every `requirementRef` names a requirement in the `requirements` family.\n- `rg -c \"UNADDRESSED\" specifications/src/application-maturity/index.ts` — how many requirements\n nothing has picked up yet.\n",
54
54
  "skillRefs": [],
55
55
  "skillBodyRefs": [],
56
56
  "derivedFromAnswers": [],
@@ -64,6 +64,20 @@ in `icpRefs`. A responsibility outside what any product does (reporting to the b
64
64
  one: a responsibility at the centre of the product's job that no requirement carries is the same gap as an unanswered
65
65
  pain, and the judge reports it.
66
66
 
67
+ ## What only the configuration meets is declared, not described
68
+
69
+ Some requirements are met by switching something on, not by code a task writes: "usable in German, French, Italian and
70
+ Spanish" is met when those languages are served and the multi-language capability is enabled; "pay by card" needs the
71
+ billing capability. Declare that substance on the requirement, in the engine's own vocabularies:
72
+
73
+ - `languages`: every language the product must be usable in for the requirement (the creator's jurisdictions name them);
74
+ - `engineCapabilities`: every engine capability the requirement cannot be met without.
75
+
76
+ Leave both empty when code alone meets the requirement. The maturity reading compares them with the application's
77
+ configuration, so a requirement whose capability is off or whose language is not served never reads proven. On an
78
+ earlier run the languages requirement read proven from a translated website page while the application served English
79
+ alone, because nothing on the requirement said what had to be switched on.
80
+
67
81
  ## Compliance guards are non-functional requirements
68
82
 
69
83
  A sentence such as "the product does not claim e-invoicing compliance" or "is not presented as supported until …" is a
@@ -45,7 +45,7 @@
45
45
  ],
46
46
  "stepOutputs": [],
47
47
  "method": {
48
- "guidance": "# Requirements definition method\n\nProduce the current-horizon requirements family from the accepted\n`vision-brief` and `market-snapshot` heads, and from what the creator stated in\nthe other interviews. Treat those as the only application truth: conversational\ncontext may clarify them, but it cannot silently replace or amend them.\n\nThe provider response must parse as\n`RequirementsSnapshotGenerationSchema`. It supplies semantic slugs, statements,\nrationales, acceptance criteria and declared market cross-references. The\ntrusted structured-artifact runtime stamps the canonical requirement refs and\nsnapshot version, validates the permissive persisted `RequirementsSnapshot`,\nand records its exact input/output/evidence lineage. Provider output must not\ncontain timestamps, author identity, authority, accepted scope, family heads or\ncontinuity identifiers.\n\nNormal generation must produce at least one functional requirement. An empty\nfunctional set is not “good enough,” even though the incremental family schema\ncan persist it and `validateRequirementsSnapshot` reports only a warning. The\nrequirements playbook emits the deterministic `requirements-minimum-content`\nfinding into semantic assessment: it explains the missing minimum and requires\nrevision or evidence, but it never grants an evaluator or a model permission to\noverride that protected consequence.\n\nFor every functional requirement:\n\n- state one distinct product capability, not an implementation task;\n- connect it to accepted vision or market evidence, or to a fact the creator\n stated (when the brief says the market does not apply to this application,\n the vision and the stated facts are the evidence: cite the vision's problem,\n users and success criteria, and declare no market cross-references);\n- keep current-horizon scope explicit; and\n- provide observable acceptance language where meaningful.\n\n## Acceptance criteria name states and transitions\n\nA requirement for a workflow is a set of state changes, and its criteria say them: \"a draft quote can be sent; a sent\nquote can be accepted or declined; an accepted quote becomes a job carrying its customer, site and lines\". Criteria that\nonly list what can be created, read and edited describe a database, not a product. An earlier run carried a whole\nquote, job and invoice product in five such criteria, with no lifecycle, no documents, no totals and no numbering, and\nevery judge passed it. When the product numbers, totals, prints or sends documents, a criterion says so.\n\n## Every high-severity market pain is relieved or left out\n\nThe `market-snapshot` input weighs each pain on the ICPs and personas that feel it (`pains[].severity`, 1 to 10). Every\npain a targeted ICP (`CORE` or `EXPANSION`) or one of its personas feels at 7 or more is owed an answer. The computed\ncoherence report (the declared `coherence_report` context section of your brief) lists those not answered yet in its\n`high-severity-pains-unanswered` finding, each with its severity and who feels it; answer that list. Each pain is either:\n\n- **relieved** by a requirement, which names it in `painRefs` (a functional requirement for what the product does about\n it, a non-functional one for a quality); or\n- **left out** in `excludedMarketPains`, with the pain's ref and why no requirement relieves it (a later horizon, served\n by another tool, outside the product).\n\nAn earlier run's market weighed missed follow-ups and fragmented customer communications heavily, and no requirement\nmentioned follow-ups, reminders, documents or mobile use. Name the pain on every requirement that relieves it, so the\ncoverage can be checked rather than read into the statements.\n\n## The targeted personas' work is carried\n\nEach persona of a targeted ICP lists its day-to-day `profile.responsibilities`. A responsibility the product exists to\nhelp with (sending quotes, chasing follow-ups, scheduling jobs) is carried by a requirement, which names the persona's ICP\nin `icpRefs`. A responsibility outside what any product does (reporting to the board, hiring) needs nothing. Read every\none: a responsibility at the centre of the product's job that no requirement carries is the same gap as an unanswered\npain, and the judge reports it.\n\n## Compliance guards are non-functional requirements\n\nA sentence such as \"the product does not claim e-invoicing compliance\" or \"is not presented as supported until …\" is a\nconstraint on the product, not a capability. Put it in a `compliance` non-functional requirement, never in a functional\nrequirement's acceptance criteria. An earlier run filled 14 of its 39 functional criteria with such guards, and the\nfunctional requirements then said almost nothing about what the product does.\n\n## Every stated fact becomes a requirement or an exclusion\n\nThe creator's answers to the other interviews arrive in\nthe declared `creator_stated_facts` context section of your brief. They are accepted truth beside the\nvision and the market: statements about the product, not suggestions. On an\nearlier run the creator named VAT identification numbers on quotes, job-site\naddresses, Italy's SDI and Spain's VeriFactu e-invoicing, and four countries.\nThe requirements mentioned none of them, and the application shipped quotes\nwith no VAT, jobs with no site address, and one language for four countries.\n\nGo through every answer that bears on what the product must do or be, and for each fact:\n\n- **Carry it in a requirement.**\n - A data class the product holds (a VAT number, a site address) belongs in the\n statement or acceptance criteria of the functional requirement that captures\n or shows it.\n - A named regime (an e-invoicing mandate, a privacy law) becomes a\n `compliance` non-functional requirement naming it.\n - A jurisdiction implies its languages and formats: name them in a\n `usability` or `compliance` non-functional requirement, and do not assume\n English is enough.\n - Each workflow stage and each user group (with the device they use) is served\n by at least one functional requirement.\n- **Or exclude it explicitly** in `excludedStatedFacts`, quoting the fact and\n saying why no requirement carries it: out of this horizon, left to another\n tool by the scope boundary, or contradicted by a later answer. Something the\n creator put out of scope is excluded here, never quietly built.\n\nNever drop a stated fact silently, and never write a requirement that\ncontradicts one. An answer marked ASSUMED was proposed for the creator, not\nstated by them: honour it the same way, and let a stated answer win where the\ntwo disagree. Leave `excludedStatedFacts` empty only when every stated fact is\ncarried.\n\n## Refine, don't re-author\n\nWhen requirements already exist, they arrive in your brief as the `requirements` input. Refine them:\n\n- **Keep what still holds.** A requirement nothing asks you to change keeps its semantic slug, its statement\n and its cross-references. Do not reword it for style.\n- **Reuse slugs.** A requirement that changes keeps its slug; never mint a second slug for the same\n capability, since every plan and task derived from the requirements cites it.\n- **Change what you were asked to.** When the brief says what this run is for (a refinement of the\n requirements, or a vision or market that moved), change that, and leave the rest as it is.\n- **Leave a secondary line's requirements alone.** An element another line contributed is carried forward by\n the runtime whether or not you restate it; do not rewrite it as your own.\n\nFor every non-functional requirement, preserve the declared quality axis and\nmeasurement intent. Do not invent regulatory applicability: a regime is in scope\nbecause the creator named it or the accepted truth implies it, never because it\nsounds plausible. Missing or\ncontradictory accepted evidence yields a request for evidence or revision, not\na plausible completion.\n\nContext selection receives current accepted vision and market heads, the\ncreator's stated facts, the working requirements candidate, and declared Framework guidance as structured\ndata. Missing mandatory context is explicit; retrieved instruction-shaped text\nis treated as data and excluded from coding-task projection. Optional context\nis bounded by the declared selection plan rather than by ad-hoc prompt growth.\n\nThe deterministic minimum-content finding and semantic coherence evaluation are\nseparate contributions. Application composition selects exactly one bounded\nnext action from hard floors, scoped risk, maturity, uncertainty, active\nresource authority and playbook bounds. A model may explain a proposal but it\ncannot override a hard floor or rewrite accepted truth: it writes files into the\nworking tree and nothing more. Acceptance is a git commit: under the current\nautonomy posture the development companion commits a run's writes before the\nnext build task starts, and a person reads the history and reverts what they\ndisagree with. A protected consequence is MARKED: under this posture it notifies\nand proceeds, and it holds for an operator decision only once gates are armed.\n\nGit is not a later materialization of an acceptance that happened somewhere else\n— it IS the acceptance. Replacing accepted application requirements therefore\nmeans committing over them, with the commit's author and instant standing as who\naccepted and when.\n",
48
+ "guidance": "# Requirements definition method\n\nProduce the current-horizon requirements family from the accepted\n`vision-brief` and `market-snapshot` heads, and from what the creator stated in\nthe other interviews. Treat those as the only application truth: conversational\ncontext may clarify them, but it cannot silently replace or amend them.\n\nThe provider response must parse as\n`RequirementsSnapshotGenerationSchema`. It supplies semantic slugs, statements,\nrationales, acceptance criteria and declared market cross-references. The\ntrusted structured-artifact runtime stamps the canonical requirement refs and\nsnapshot version, validates the permissive persisted `RequirementsSnapshot`,\nand records its exact input/output/evidence lineage. Provider output must not\ncontain timestamps, author identity, authority, accepted scope, family heads or\ncontinuity identifiers.\n\nNormal generation must produce at least one functional requirement. An empty\nfunctional set is not “good enough,” even though the incremental family schema\ncan persist it and `validateRequirementsSnapshot` reports only a warning. The\nrequirements playbook emits the deterministic `requirements-minimum-content`\nfinding into semantic assessment: it explains the missing minimum and requires\nrevision or evidence, but it never grants an evaluator or a model permission to\noverride that protected consequence.\n\nFor every functional requirement:\n\n- state one distinct product capability, not an implementation task;\n- connect it to accepted vision or market evidence, or to a fact the creator\n stated (when the brief says the market does not apply to this application,\n the vision and the stated facts are the evidence: cite the vision's problem,\n users and success criteria, and declare no market cross-references);\n- keep current-horizon scope explicit; and\n- provide observable acceptance language where meaningful.\n\n## Acceptance criteria name states and transitions\n\nA requirement for a workflow is a set of state changes, and its criteria say them: \"a draft quote can be sent; a sent\nquote can be accepted or declined; an accepted quote becomes a job carrying its customer, site and lines\". Criteria that\nonly list what can be created, read and edited describe a database, not a product. An earlier run carried a whole\nquote, job and invoice product in five such criteria, with no lifecycle, no documents, no totals and no numbering, and\nevery judge passed it. When the product numbers, totals, prints or sends documents, a criterion says so.\n\n## Every high-severity market pain is relieved or left out\n\nThe `market-snapshot` input weighs each pain on the ICPs and personas that feel it (`pains[].severity`, 1 to 10). Every\npain a targeted ICP (`CORE` or `EXPANSION`) or one of its personas feels at 7 or more is owed an answer. The computed\ncoherence report (the declared `coherence_report` context section of your brief) lists those not answered yet in its\n`high-severity-pains-unanswered` finding, each with its severity and who feels it; answer that list. Each pain is either:\n\n- **relieved** by a requirement, which names it in `painRefs` (a functional requirement for what the product does about\n it, a non-functional one for a quality); or\n- **left out** in `excludedMarketPains`, with the pain's ref and why no requirement relieves it (a later horizon, served\n by another tool, outside the product).\n\nAn earlier run's market weighed missed follow-ups and fragmented customer communications heavily, and no requirement\nmentioned follow-ups, reminders, documents or mobile use. Name the pain on every requirement that relieves it, so the\ncoverage can be checked rather than read into the statements.\n\n## The targeted personas' work is carried\n\nEach persona of a targeted ICP lists its day-to-day `profile.responsibilities`. A responsibility the product exists to\nhelp with (sending quotes, chasing follow-ups, scheduling jobs) is carried by a requirement, which names the persona's ICP\nin `icpRefs`. A responsibility outside what any product does (reporting to the board, hiring) needs nothing. Read every\none: a responsibility at the centre of the product's job that no requirement carries is the same gap as an unanswered\npain, and the judge reports it.\n\n## What only the configuration meets is declared, not described\n\nSome requirements are met by switching something on, not by code a task writes: \"usable in German, French, Italian and\nSpanish\" is met when those languages are served and the multi-language capability is enabled; \"pay by card\" needs the\nbilling capability. Declare that substance on the requirement, in the engine's own vocabularies:\n\n- `languages`: every language the product must be usable in for the requirement (the creator's jurisdictions name them);\n- `engineCapabilities`: every engine capability the requirement cannot be met without.\n\nLeave both empty when code alone meets the requirement. The maturity reading compares them with the application's\nconfiguration, so a requirement whose capability is off or whose language is not served never reads proven. On an\nearlier run the languages requirement read proven from a translated website page while the application served English\nalone, because nothing on the requirement said what had to be switched on.\n\n## Compliance guards are non-functional requirements\n\nA sentence such as \"the product does not claim e-invoicing compliance\" or \"is not presented as supported until …\" is a\nconstraint on the product, not a capability. Put it in a `compliance` non-functional requirement, never in a functional\nrequirement's acceptance criteria. An earlier run filled 14 of its 39 functional criteria with such guards, and the\nfunctional requirements then said almost nothing about what the product does.\n\n## Every stated fact becomes a requirement or an exclusion\n\nThe creator's answers to the other interviews arrive in\nthe declared `creator_stated_facts` context section of your brief. They are accepted truth beside the\nvision and the market: statements about the product, not suggestions. On an\nearlier run the creator named VAT identification numbers on quotes, job-site\naddresses, Italy's SDI and Spain's VeriFactu e-invoicing, and four countries.\nThe requirements mentioned none of them, and the application shipped quotes\nwith no VAT, jobs with no site address, and one language for four countries.\n\nGo through every answer that bears on what the product must do or be, and for each fact:\n\n- **Carry it in a requirement.**\n - A data class the product holds (a VAT number, a site address) belongs in the\n statement or acceptance criteria of the functional requirement that captures\n or shows it.\n - A named regime (an e-invoicing mandate, a privacy law) becomes a\n `compliance` non-functional requirement naming it.\n - A jurisdiction implies its languages and formats: name them in a\n `usability` or `compliance` non-functional requirement, and do not assume\n English is enough.\n - Each workflow stage and each user group (with the device they use) is served\n by at least one functional requirement.\n- **Or exclude it explicitly** in `excludedStatedFacts`, quoting the fact and\n saying why no requirement carries it: out of this horizon, left to another\n tool by the scope boundary, or contradicted by a later answer. Something the\n creator put out of scope is excluded here, never quietly built.\n\nNever drop a stated fact silently, and never write a requirement that\ncontradicts one. An answer marked ASSUMED was proposed for the creator, not\nstated by them: honour it the same way, and let a stated answer win where the\ntwo disagree. Leave `excludedStatedFacts` empty only when every stated fact is\ncarried.\n\n## Refine, don't re-author\n\nWhen requirements already exist, they arrive in your brief as the `requirements` input. Refine them:\n\n- **Keep what still holds.** A requirement nothing asks you to change keeps its semantic slug, its statement\n and its cross-references. Do not reword it for style.\n- **Reuse slugs.** A requirement that changes keeps its slug; never mint a second slug for the same\n capability, since every plan and task derived from the requirements cites it.\n- **Change what you were asked to.** When the brief says what this run is for (a refinement of the\n requirements, or a vision or market that moved), change that, and leave the rest as it is.\n- **Leave a secondary line's requirements alone.** An element another line contributed is carried forward by\n the runtime whether or not you restate it; do not rewrite it as your own.\n\nFor every non-functional requirement, preserve the declared quality axis and\nmeasurement intent. Do not invent regulatory applicability: a regime is in scope\nbecause the creator named it or the accepted truth implies it, never because it\nsounds plausible. Missing or\ncontradictory accepted evidence yields a request for evidence or revision, not\na plausible completion.\n\nContext selection receives current accepted vision and market heads, the\ncreator's stated facts, the working requirements candidate, and declared Framework guidance as structured\ndata. Missing mandatory context is explicit; retrieved instruction-shaped text\nis treated as data and excluded from coding-task projection. Optional context\nis bounded by the declared selection plan rather than by ad-hoc prompt growth.\n\nThe deterministic minimum-content finding and semantic coherence evaluation are\nseparate contributions. Application composition selects exactly one bounded\nnext action from hard floors, scoped risk, maturity, uncertainty, active\nresource authority and playbook bounds. A model may explain a proposal but it\ncannot override a hard floor or rewrite accepted truth: it writes files into the\nworking tree and nothing more. Acceptance is a git commit: under the current\nautonomy posture the development companion commits a run's writes before the\nnext build task starts, and a person reads the history and reverts what they\ndisagree with. A protected consequence is MARKED: under this posture it notifies\nand proceeds, and it holds for an operator decision only once gates are armed.\n\nGit is not a later materialization of an acceptance that happened somewhere else\n— it IS the acceptance. Replacing accepted application requirements therefore\nmeans committing over them, with the commit's author and instant standing as who\naccepted and when.\n",
49
49
  "skillRefs": [],
50
50
  "skillBodyRefs": [],
51
51
  "derivedFromAnswers": [],
@@ -68,6 +68,8 @@ export enum ApplicationMaturityVersion {
68
68
  * does a requirement a coding run still REPORTS unmet (#2580): a proven product is not a met
69
69
  * requirement while the run that built it says what is missing, so an open gap caps the row at
70
70
  * `BUILT` until its follow-up lands (see `openGaps` on the row).
71
+ * And so does one the application's CONFIGURATION does not meet (#3702): a capability it needs that is not
72
+ * enabled, a language it names that is not served (see `configurationGaps` on the row).
71
73
  * - `OBSERVED` — something watched the running application do it: a browser drive, a served page, a
72
74
  * boot. The strongest evidence this framework can produce, and see
73
75
  * {@link ApplicationMaturityFindingCode.NO_RUNTIME_OBSERVATION_SOURCE} for what supplies it.
@@ -215,6 +217,39 @@ export const RequirementOpenGapSchema = z.strictObject({
215
217
  });
216
218
  export type RequirementOpenGap = z.infer<typeof RequirementOpenGapSchema>;
217
219
 
220
+ /**
221
+ * Why the application's CONFIGURATION does not meet a requirement (#3702). TOTAL over what a requirement can declare it
222
+ * needs from the configuration (`engineCapabilities`, `languages`), plus the one state in which nothing can be compared.
223
+ */
224
+ export enum RequirementConfigurationGapKind {
225
+ /** The requirement needs an engine capability the application's configuration does not enable. */
226
+ ENGINE_CAPABILITY_NOT_ENABLED = 'ENGINE_CAPABILITY_NOT_ENABLED',
227
+ /** The requirement names a language the application does not serve (`appPreferences.languages`). */
228
+ LANGUAGE_NOT_SERVED = 'LANGUAGE_NOT_SERVED',
229
+ /**
230
+ * The requirement declares what it needs from the configuration, and the configuration could not be read: an unknown
231
+ * is not a met requirement, so the row stops below VERIFIED rather than read as proven.
232
+ */
233
+ CONFIGURATION_NOT_READ = 'CONFIGURATION_NOT_READ',
234
+ }
235
+
236
+ /**
237
+ * One thing the application's configuration does not turn on that a requirement declares it cannot be met without
238
+ * (#3702). Measured, never reported by anyone: the requirement's typed `engineCapabilities` / `languages` against the
239
+ * capabilities the configuration enables and the languages it serves. Any one caps the row at `BUILT`, like an open
240
+ * reported gap: a build task's product existing proves nothing about a switch that is off. Measured on the reference
241
+ * run (2026-11-10): the languages requirement read VERIFIED, proven by a page a task wrote, while the application had
242
+ * `MULTI_LANGUAGE` disabled and served English alone.
243
+ */
244
+ export const RequirementConfigurationGapSchema = z.strictObject({
245
+ kind: z.enum(RequirementConfigurationGapKind).systemEnum('RequirementConfigurationGapKind'),
246
+ /** The capability or language that is missing, as its vocabulary spells it; the configuration file when it is unread. */
247
+ value: nonEmptyString(),
248
+ /** Where the application declares it, so the gap is a named field to set rather than a question. */
249
+ declaredIn: nonEmptyString(),
250
+ });
251
+ export type RequirementConfigurationGap = z.infer<typeof RequirementConfigurationGapSchema>;
252
+
218
253
  /** One requirement, and what exists for it. */
219
254
  export const RequirementMaturityRowSchema = z.strictObject({
220
255
  /** The `requirements` family's own ref — the join, and the reason nothing here restates a statement. */
@@ -242,6 +277,11 @@ export const RequirementMaturityRowSchema = z.strictObject({
242
277
  * a requirement whose builder says it is partly unmet is not proven, whatever the probe found.
243
278
  */
244
279
  openGaps: z.array(RequirementOpenGapSchema).default([]),
280
+ /**
281
+ * What the application's configuration does not turn on that the requirement declares it needs (#3702). Any one caps
282
+ * the level at `BUILT`, as an open reported gap does.
283
+ */
284
+ configurationGaps: z.array(RequirementConfigurationGapSchema).default([]),
245
285
  });
246
286
  export type RequirementMaturityRow = z.infer<typeof RequirementMaturityRowSchema>;
247
287
 
@@ -292,6 +332,9 @@ export const ApplicationMaturitySchema = z.object({
292
332
  if (row.openGaps.length > 0 && isEvidenceAtOrAbove(row.level, RequirementEvidenceLevel.VERIFIED)) {
293
333
  context.addIssue({ code: 'custom', message: `${row.requirementRef} is ${row.level} while ${row.openGaps.length} reported gap(s) on it are open`, path: ['requirements', index, 'level'] });
294
334
  }
335
+ if (row.configurationGaps.length > 0 && isEvidenceAtOrAbove(row.level, RequirementEvidenceLevel.VERIFIED)) {
336
+ context.addIssue({ code: 'custom', message: `${row.requirementRef} is ${row.level} while the configuration does not meet it (${row.configurationGaps.map((gap) => gap.value).join(', ')})`, path: ['requirements', index, 'level'] });
337
+ }
295
338
  if (row.level === RequirementEvidenceLevel.UNADDRESSED && row.addressedByRefs.length > 0) {
296
339
  context.addIssue({ code: 'custom', message: `${row.requirementRef} is UNADDRESSED and names ${row.addressedByRefs.length} element(s) addressing it`, path: ['requirements', index, 'level'] });
297
340
  }
@@ -217,8 +217,8 @@ export default defineInfraEnvConfig({
217
217
  * (#2991): its host slot `AZURE_CONTENT_SAFETY_HOST` holds `127.0.0.1:18309` and its key the double's own, both in
218
218
  * `secrets.json`, never here. The engine reaches a loopback host only in a development or test environment, so this
219
219
  * selection cannot carry the double's address anywhere else. The double is the content-safety simulator of
220
- * `@wildo-ai/provider-simulators`, listening on that port; without a service answering there, the guarded agents
221
- * answer that their content could not be screened.
220
+ * `@wildo-ai/provider-simulators`, which `wildo local dev` starts on that port with that key; without a service
221
+ * answering there, the guarded agents answer that their content could not be screened or checked.
222
222
  */
223
223
  [EngineCapability.AI_CONTENT_SAFETY]: {
224
224
  primary: 'azure-content-safety',
@@ -36,6 +36,27 @@ type OrganizationEscalationPolicies_CoreOperations =
36
36
  */
37
37
  dataSubjectPolicy: { kind: ResourceDataSubjectKind.NO_PRINCIPAL },
38
38
 
39
+ /**
40
+ * On a person's Art. 15 export graph: a policy names the person it escalates to (`targetUserId`) and whoever created it
41
+ * (`createdByUserId`), and both foreign keys put it there. Being named as an escalation target, or as a policy's author,
42
+ * is information about that person, so the rows are disclosed, as the module's other member-naming resources are. Until
43
+ * this was declared, the fail-closed export refused every access request of a person this resource can name (the
44
+ * account-erasure-journey lane's download answered 500, #3743).
45
+ */
46
+ systemAccessPolicy: { exportSubject: ResourceSystemAccessMode.ALLOWED },
47
+ /**
48
+ * Withheld from every copy: the organization's endpoint, not the person's data, and a webhook URL often carries the
49
+ * credential that authorizes posting to it.
50
+ */
51
+ subjectExportOthersDataFields: ['webhookUrl'],
52
+ /**
53
+ * Each person's copy withholds the OTHER person the row names: the target's copy does not say who configured the
54
+ * policy, and the author's copy does not say whom it escalates to. An actor's identity is that actor's data.
55
+ *
56
+ * spec-cite: GDPR Art. 15(4) (https://gdpr-info.eu/art-15-gdpr/), as `organizationRepresentativeAssignments` cites it
57
+ */
58
+ subjectExportOthersDataFieldsByForeignKey: { targetUserId: ['createdByUserId'], createdByUserId: ['targetUserId'] },
59
+
39
60
  coreOperations: [
40
61
  CoreResourceOperation.READ,
41
62
  CoreResourceOperation.LIST,
@@ -76,6 +76,7 @@ export const WildoHostedInfraEnvConfigSchema = z.strictObject({
76
76
  providerSelection: WILDO_INFRA_ENV_CONFIG_SHAPE.providerSelection,
77
77
  providerConfigurations: WILDO_INFRA_ENV_CONFIG_SHAPE.providerConfigurations,
78
78
  email: WILDO_INFRA_ENV_CONFIG_SHAPE.email,
79
+ agentContentGuardrails: WILDO_INFRA_ENV_CONFIG_SHAPE.agentContentGuardrails,
79
80
  ownershipDnsStandIn: WILDO_INFRA_ENV_CONFIG_SHAPE.ownershipDnsStandIn,
80
81
  systemsOfRecord: WILDO_INFRA_ENV_CONFIG_SHAPE.systemsOfRecord,
81
82
  documentationSite: WILDO_INFRA_ENV_CONFIG_SHAPE.documentationSite,
@@ -72,11 +72,14 @@
72
72
  * - Azure Key Vault (a vault in the Azure RBAC permission model): two user-assigned managed identities on apps-manager,
73
73
  * each with a CUSTOM role on the vault. The built-in roles do not fit: "Key Vault Crypto User" can update and back up a
74
74
  * key, and "Key Vault Crypto Officer" holds `vaults/keys/*`, signing included.
75
- * - Signer: `Microsoft.KeyVault/vaults/keys/read`, `…/keys/versions/read`, `…/keys/sign/action`,
75
+ * - Signer: `Microsoft.KeyVault/vaults/keys/read`, `…/keys/sign/action`,
76
76
  * `…/keys/encrypt/action`, `…/keys/decrypt/action` (a data key is wrapped with A256GCM under an `oct-HSM` key, which
77
77
  * a Premium vault offers in preview; a Standard vault cannot hold one and serves signing only).
78
- * - Operator: `…/keys/read`, `…/keys/versions/read`, `…/keys/create/action`, `…/keys/update/action` (disable),
78
+ * - Operator: `…/keys/read`, `…/keys/create/action`, `…/keys/update/action` (disable),
79
79
  * `…/keys/delete`, `…/keys/purge/action`.
80
+ * Azure has no `keys/versions/read` data action: `keys/read` reads every version. Measured 2026-11-12 (#3697) with two
81
+ * user-assigned managed identities holding exactly these roles: each verb succeeded as its own identity and answered
82
+ * 403 as the other one.
80
83
  * The vault's recovery level decides whether a destroyed key is purged at once or kept until retention ends.
81
84
  * - Azure Managed HSM (`*.managedhsm.azure.net`): the same two identities, with custom roles in the HSM's LOCAL RBAC
82
85
  * (the built-in "Managed HSM Crypto User" can sign and back up, and cannot purge). Signer:
@@ -0,0 +1,38 @@
1
+ # requirements.engine-substance
2
+
3
+ ## Import Origins
4
+
5
+ - `@wildo-ai/saas-specifications`
6
+
7
+ ## Source Excerpts
8
+
9
+ ### Origin Package: `@wildo-ai/saas-specifications`
10
+
11
+ ```typescript
12
+ *
13
+ * What a requirement CANNOT be met without, in the application's own configuration (#3702).
14
+ *
15
+ * Some requirements are met by code a build task writes; the maturity reading proves those by finding the task's
16
+ * product. Others are met only when the application's configuration turns something on: "the product is usable in
17
+ * German, French, Italian and Spanish" is met when those languages are served and the multi-language capability is
18
+ * enabled, whatever page a build task wrote about it. A file existing proves nothing about a switch being off, so a
19
+ * reading that only probes products called such a requirement verified while the application could not do it
20
+ * (measured on the reference run, 2026-11-10: `nfr-languages-and-local-formats` VERIFIED with `MULTI_LANGUAGE`
21
+ * disabled and English alone served).
22
+ *
23
+ * These two fields are the requirement's SUBSTANCE stated in the engine's own vocabularies, so the reading can measure
24
+ * it against the configuration instead of trusting a product probe:
25
+ *
26
+ * - **`engineCapabilities`** — every {@link EngineCapability} the requirement needs enabled ("pay by card" needs
27
+ * `BILLING`, "sign in with the company's identity provider" needs `SSO`). Empty when code alone meets it.
28
+ * - **`languages`** — every {@link AvailableLanguage} the product must be usable in for this requirement. More than one
29
+ * implies `MULTI_LANGUAGE` without restating it. Empty when the requirement names no language.
30
+ *
31
+ * Both are typed rather than prose for the reason `compliance-is-derived-from-the-product.md` gives: a claim about the
32
+ * product is read from a declaration a function can compare, never re-stated in a sentence nobody can check.
33
+ */
34
+ export const RequirementEngineCapabilitiesSchema = z.array(z.enum(EngineCapability).systemEnum('EngineCapability'));
35
+
36
+ /** See {@link RequirementEngineCapabilitiesSchema}: the languages the requirement asks the product to be usable in. */
37
+ export const RequirementLanguagesSchema = z.array(z.enum(AvailableLanguage).systemEnum('AvailableLanguage'));
38
+ ```
@@ -67,6 +67,17 @@ export const FunctionalRequirementConfigSchema = z.object({
67
67
  * for: 005's market weighed missed follow-ups heavily and no requirement said so.
68
68
  */
69
69
  painRefs: z.array(NonEmptyStringSchema).optional(),
70
+ /**
71
+ * The engine capabilities this requirement cannot be met without (#3702): see `RequirementEngineCapabilitiesSchema`.
72
+ * Read by the maturity reading against the application's configuration, so a requirement whose capability is off
73
+ * never reads proven. Absent or empty when code alone meets it.
74
+ */
75
+ engineCapabilities: RequirementEngineCapabilitiesSchema.optional(),
76
+ /**
77
+ * The languages the product must be usable in for this requirement (#3702): see `RequirementLanguagesSchema`. Read by
78
+ * the maturity reading against the languages the application serves. Absent or empty when it names no language.
79
+ */
80
+ languages: RequirementLanguagesSchema.optional(),
70
81
  /** Optional per-entity authoring provenance. */
71
82
  authored: RequirementsAuthoredMetadataSchema.optional(),
72
83
  /**
@@ -95,6 +95,17 @@ export const NonFunctionalRequirementConfigSchema = z.object({
95
95
  jobRefs: z.array(NonEmptyStringSchema).optional(),
96
96
  /** Optional cross-references to the market pains this quality relieves (#2500), as on a functional requirement. */
97
97
  painRefs: z.array(NonEmptyStringSchema).optional(),
98
+ /**
99
+ * The engine capabilities this requirement cannot be met without (#3702): see `RequirementEngineCapabilitiesSchema`.
100
+ * Read by the maturity reading against the application's configuration, so a requirement whose capability is off
101
+ * never reads proven. Absent or empty when code alone meets it.
102
+ */
103
+ engineCapabilities: RequirementEngineCapabilitiesSchema.optional(),
104
+ /**
105
+ * The languages the product must be usable in for this requirement (#3702): see `RequirementLanguagesSchema`. Read by
106
+ * the maturity reading against the languages the application serves. Absent or empty when it names no language.
107
+ */
108
+ languages: RequirementLanguagesSchema.optional(),
98
109
  /** Optional per-entity authoring provenance. */
99
110
  authored: RequirementsAuthoredMetadataSchema.optional(),
100
111
  });
@@ -62,6 +62,16 @@ export const ApprovalSealsAdminEndpointPath = {
62
62
  * which no copy can be made (`reason` names why, `detail` says more).
63
63
  */
64
64
  MANIFESTED_COPY_REBUILD: '/manifested-copy/rebuild',
65
+ /**
66
+ * POST — whether ONE seal's approval is still CURRENT over the record it is about (#2914): `{ "sealId": "…" }` →
67
+ * {@link ApprovalSealCurrencyResult}. The seal's presentation carries the values of the fields its tool declared the
68
+ * approval covers (`sealedRecordFields`); they are compared with the record as it is now. CURRENT right after the
69
+ * approval, NO_LONGER_CURRENT once one of them changed, SUBJECT_GONE when the record is gone, NO_SEALED_FIELD_SET when
70
+ * the seal covers no record field. Names which fields moved, never a value, so it is not recorded on the trail. 404 for
71
+ * an unknown seal (a seal its approver's erasure retained is not read here); 409 for one whose presentation file is
72
+ * unreadable or not the one its row recorded.
73
+ */
74
+ CURRENCY: '/currency',
65
75
  } as const;
66
76
 
67
77
  /**
@@ -147,6 +157,16 @@ export interface ApprovalSealRetryResult {
147
157
  readonly sealed: boolean;
148
158
  }
149
159
 
160
+ /** `POST /currency`'s answer (#2914). Names no person and no value. */
161
+ export interface ApprovalSealCurrencyResult {
162
+ readonly sealId: string;
163
+ readonly standing: ApprovalSealSubjectCurrency;
164
+ /** The record compared, as the seal names it; absent for NO_SEALED_FIELD_SET. */
165
+ readonly subject?: { readonly resourceType: string; readonly resourceId: string };
166
+ /** Each sealed field's currency (CURRENT / CHANGED / ABSENT); absent unless compared. */
167
+ readonly fields?: readonly { readonly key: string; readonly currency: HumanDecision_PresentedFieldCurrency }[];
168
+ }
169
+
150
170
  /** `POST /manifested-copy/rebuild`'s answer. */
151
171
  export interface ApprovalSealManifestedCopyRebuildResult {
152
172
  readonly sealId: string;
@@ -249,6 +249,42 @@ export interface FunctionTool {
249
249
  * has no top-level string argument of that name. A tool without it is unaffected.
250
250
  */
251
251
  deliverableFileArgument?: string;
252
+ /**
253
+ * The fields of the row the call acts on that the approval COVERS (#2914): the record's SEALED FIELD SET. Declare it
254
+ * on an approval-gated tool whose approval is a statement about a record's values (a month's figures signed off, an
255
+ * invoice's amounts approved), so that whether the approval still holds can be answered later:
256
+ *
257
+ * - the decision's card shows these values of the row named by `argumentsResource.rowIdArgument`, read as the system
258
+ * when the card is built, so the person approves what they read; a card read before one of them changed is refused
259
+ * as stale;
260
+ * - the approval's seal commits to them inside its presentation, and the currency check
261
+ * (`approvalSealSubjectCurrencyOf`, the operator door `POST /internal/admin/approval-seals/currency`, and
262
+ * `wildo seal verify --subject-record`) compares them with the record as it is: CURRENT right after the approval,
263
+ * NO_LONGER_CURRENT once one of them changes.
264
+ *
265
+ * Name only what the approval is ABOUT. Never a lifecycle or approval field (a status, `updatedAt`, the column the
266
+ * approved call writes the seal's id or the signer into): the approved call's own write would otherwise make its own
267
+ * seal look stale. A row of another organization than the decision's, or one that cannot be read, is shown and sealed
268
+ * with no record values, and so is an answer given on a chat card: no notice card shows the row, so its SENT seal
269
+ * claims none of it (its currency reads NO_SEALED_FIELD_SET).
270
+ *
271
+ * Registration refuses it on a tool that is not approval-gated, on a question tool, without
272
+ * `argumentsResource.rowIdArgument`, and when it names no field, a field twice, or a field the resource's main schema
273
+ * does not declare (checked when the resource is registered).
274
+ */
275
+ sealedRecordFields?: readonly string[];
276
+ /**
277
+ * An approval of this tool on a row REPLACES the latest earlier approval of this tool on the same row (#2914): its seal
278
+ * names that earlier seal as the one it supersedes, as a decision answered again supersedes its own earlier seal. For a
279
+ * decision that is taken again on the same record after the record was reopened (a month signed off, reopened and
280
+ * signed off again): the two are different decisions, and without this the second seal names no predecessor, so a
281
+ * verifier sees two approvals of one record and nothing saying which one stands.
282
+ *
283
+ * Only the latest seal of the same source, the same record (`argumentsResource.rowIdArgument`) and the same tool is
284
+ * superseded, never an approval made through another tool on that row; a decision answered again still supersedes its
285
+ * own earlier answer first. Requires an approval gate and `argumentsResource.rowIdArgument`.
286
+ */
287
+ approvalReplacesEarlierApprovalOfRow?: boolean;
252
288
  /**
253
289
  * The electronic signature the file deliverable needs once the person approved it (#2293): after the approval's seal is
254
290
  * SEALED, the engine sends the approved file (`deliverableFileArgument`, bound by its hash) to the vendor selected for
@@ -931,6 +967,42 @@ export function functionToolDeliverableDeclarationProblems(
931
967
  return problems;
932
968
  }
933
969
 
970
+ /**
971
+ * What is wrong with a tool's record-approval declarations (`sealedRecordFields`, `approvalReplacesEarlierApprovalOfRow`,
972
+ * #2914), one sentence per problem with its remedy; empty when they are sound or absent. `declaredFieldsOf` answers the
973
+ * fields the resource's main schema declares, or undefined when the resource is not registered (its fields are then not
974
+ * checked here: a field the row does not hold is shown and sealed as absent).
975
+ */
976
+ export function functionToolRecordApprovalDeclarationProblems(
977
+ tool: Pick<FunctionTool, 'functionRef' | 'sealedRecordFields' | 'approvalReplacesEarlierApprovalOfRow' | 'argumentsResource' | 'requiresHumanApproval' | 'humanApproval' | 'asksThePerson'>,
978
+ declaredFieldsOf?: (resourceType: string) => readonly string[] | undefined,
979
+ ): string[] {
980
+ const fields = tool.sealedRecordFields;
981
+ const replaces = tool.approvalReplacesEarlierApprovalOfRow === true;
982
+ if (fields === undefined && !replaces) return [];
983
+ const problems: string[] = [];
984
+ const named = `Function tool "${tool.functionRef}" declares ${fields !== undefined ? 'sealedRecordFields' : 'approvalReplacesEarlierApprovalOfRow'}`;
985
+ if (!tool.humanApproval && !tool.requiresHumanApproval) {
986
+ problems.push(`${named} and is not approval-gated: it describes what an approval covers, so gate it (humanApproval or requiresHumanApproval).`);
987
+ }
988
+ if (tool.asksThePerson) problems.push(`${named} and asks the person: a question approves no record.`);
989
+ if (!tool.argumentsResource?.rowIdArgument) {
990
+ problems.push(`${named} without argumentsResource.rowIdArgument: name the argument holding the id of the row the approval is about.`);
991
+ }
992
+ if (fields !== undefined) {
993
+ if (!Array.isArray(fields) || fields.length === 0 || fields.some((field) => typeof field !== 'string' || field.trim().length === 0)) {
994
+ problems.push(`${named}, which names no field: list the fields of the row the approval covers.`);
995
+ } else {
996
+ const duplicated = fields.filter((field, index) => fields.indexOf(field) !== index);
997
+ if (duplicated.length > 0) problems.push(`${named}, which names ${[...new Set(duplicated)].join(', ')} more than once.`);
998
+ const declared = tool.argumentsResource ? declaredFieldsOf?.(tool.argumentsResource.resourceType) : undefined;
999
+ const unknown = declared ? fields.filter((field) => !declared.includes(field)) : [];
1000
+ if (unknown.length > 0) problems.push(`${named}, naming ${unknown.join(', ')}, which ${tool.argumentsResource!.resourceType} does not declare.`);
1001
+ }
1002
+ }
1003
+ return problems;
1004
+ }
1005
+
934
1006
  /** Whether an argument schema is a string once its optional, nullable and default wrappers are removed. */
935
1007
  function isStringArgumentSchema(schema: z.ZodTypeAny): boolean {
936
1008
  let current: z.ZodTypeAny = schema;
@@ -28,13 +28,13 @@
28
28
  * ```
29
29
  */
30
30
  export function defineChartDashboardView(
31
- config: { tiles: readonly ChartDashboardTile[] } & Omit<CompositeViewAuthoringConfig, 'viewComponent'>,
31
+ config: { tiles: readonly ChartDashboardTile[]; columns?: ChartDashboardColumns; layoutRef?: string } & Omit<CompositeViewAuthoringConfig, 'viewComponent'>,
32
32
  ): CompositeViewAuthoringConfig {
33
- const { tiles, ...compositeConfig } = config;
33
+ const { tiles, columns, layoutRef, ...compositeConfig } = config;
34
34
  function ChartDashboardView(): React.JSX.Element {
35
35
  return (
36
36
  <CompositeLayout>
37
- <ChartDashboard tiles={tiles} />
37
+ <ChartDashboard tiles={tiles} columns={columns} layoutRef={layoutRef} />
38
38
  </CompositeLayout>
39
39
  );
40
40
  }