@wildo-ai/framework-knowledge 1.1.9 → 1.1.11

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 (1163) 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/acceptance.md +11 -0
  4. package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +4 -2
  5. package/dist/claude-marketplace/plugins/wildo/references/expert-personas-and-deliberations.md +26 -7
  6. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +4 -2
  7. package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +4 -2
  8. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +9 -3
  9. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  10. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  11. package/dist/esm/framework-knowledge.definitions.js +543 -80
  12. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  13. package/dist/esm/framework-knowledge.research-provenance.d.ts +88 -0
  14. package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -0
  15. package/dist/esm/framework-knowledge.research-provenance.js +140 -0
  16. package/dist/esm/framework-knowledge.research-provenance.js.map +1 -0
  17. package/dist/esm/index.d.ts +2 -0
  18. package/dist/esm/index.d.ts.map +1 -1
  19. package/dist/esm/index.js +2 -0
  20. package/dist/esm/index.js.map +1 -1
  21. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
  22. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
  23. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +43 -2
  25. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +138 -21
  27. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
  29. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +1 -1
  30. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  31. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +1 -1
  32. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +1 -1
  33. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +17 -9
  35. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +22 -11
  37. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +2 -1
  39. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +89 -9
  41. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +6 -5
  43. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +6 -4
  45. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +2 -2
  47. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +7 -2
  49. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
  50. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +12 -3
  51. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  52. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +8 -4
  53. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  54. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +28 -6
  55. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  56. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +23 -5
  57. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  58. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +2 -2
  59. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  60. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +9 -3
  61. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -1
  62. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
  63. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  64. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +14 -2
  65. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  66. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +1 -1
  67. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
  68. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +2 -2
  69. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +14 -6
  71. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  72. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +2 -1
  73. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -1
  74. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +5 -3
  75. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
  76. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +2 -1
  77. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
  78. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +11 -9
  79. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
  80. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +17 -3
  81. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
  82. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +19 -2
  83. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
  84. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +1 -1
  85. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  86. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +1 -1
  87. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  88. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +2 -1
  89. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  90. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +2 -1
  91. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  92. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  93. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +9 -3
  94. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  95. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +34 -7
  96. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  97. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +39 -13
  98. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  99. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +1 -1
  100. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -1
  101. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -1
  102. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  103. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +14 -6
  104. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  105. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  106. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +38 -3
  107. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  108. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -1
  109. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  110. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +23 -8
  111. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  112. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts +95 -0
  113. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -0
  114. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +111 -0
  115. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -0
  116. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  117. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +15 -3
  118. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  119. package/dist/esm/source-anchor-grammar.d.ts +70 -0
  120. package/dist/esm/source-anchor-grammar.d.ts.map +1 -0
  121. package/dist/esm/source-anchor-grammar.js +114 -0
  122. package/dist/esm/source-anchor-grammar.js.map +1 -0
  123. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  124. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  125. package/dist/knowledge/manifest.json +8 -8
  126. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +6 -0
  127. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
  128. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  129. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  130. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +497 -32
  131. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +44 -3
  132. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +302 -8
  133. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
  134. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +2 -2
  135. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +2 -2
  136. package/dist/knowledge/playbooks/bottom_up.conception/method.md +12 -7
  137. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +11 -3
  138. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  139. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  140. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +118 -11
  141. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -3
  142. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +41 -10
  143. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +7 -5
  144. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +5 -0
  145. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +1 -1
  146. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +12 -0
  147. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +4 -3
  148. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +79 -1
  149. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +16 -4
  150. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +187 -14
  151. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +23 -3
  152. package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +3 -2
  153. package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +6 -2
  154. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +99 -24
  155. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  156. package/dist/knowledge/playbooks/refinement.document-facts/method.md +38 -3
  157. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +4 -3
  158. package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +5 -2
  159. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +2 -2
  160. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +8 -6
  161. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -1
  162. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  163. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  164. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +16 -5
  165. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +3 -3
  166. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +56 -16
  167. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +6 -4
  168. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
  169. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
  170. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +30 -9
  171. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +5 -3
  172. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +12 -1
  173. package/dist/knowledge/playbooks/top_down.business-model/method.md +6 -0
  174. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +2 -2
  175. package/dist/knowledge/playbooks/top_down.capability-map/method.md +10 -9
  176. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +2 -2
  177. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +12 -2
  178. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +1 -1
  179. package/dist/knowledge/playbooks/top_down.definition/method.md +7 -2
  180. package/dist/knowledge/playbooks/top_down.definition/playbook.json +5 -4
  181. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +10 -3
  182. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +18 -4
  183. package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +5 -2
  184. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +2 -2
  185. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -1
  186. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -1
  187. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +26 -0
  188. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +5 -3
  189. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  190. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  191. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +1 -1
  192. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-protocol.json +1 -1
  193. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -1
  194. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +84 -9
  195. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +6 -3
  196. package/dist/knowledge/playbooks/top_down.risk-register/method.md +1 -1
  197. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +1 -1
  198. package/dist/knowledge/playbooks/top_down.service-method/method.md +198 -0
  199. package/dist/knowledge/playbooks/top_down.service-method/playbook.json +96 -0
  200. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +23 -0
  201. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +23 -4
  202. package/dist/knowledge/references/acp.execution-profile.md +9 -1
  203. package/dist/knowledge/references/application-maturity.config.md +1 -1
  204. package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +55 -0
  205. package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +13 -2
  206. package/dist/knowledge/references/backend.inbound-handlers.agents.md +10 -3
  207. package/dist/knowledge/references/backend.inbound-handlers.definition.md +426 -5
  208. package/dist/knowledge/references/backend.inbound-handlers.pipelines.md +62 -0
  209. package/dist/knowledge/references/blueprint.definition-contract.md +483 -0
  210. package/dist/knowledge/references/brand.name-choice.config.md +20 -3
  211. package/dist/knowledge/references/brand.name-screening.config.md +58 -3
  212. package/dist/knowledge/references/brand.visual-tone.config.md +26 -8
  213. package/dist/knowledge/references/build-plan.task-graph.config.md +292 -7
  214. package/dist/knowledge/references/business-model.pricing-plan.config.md +7 -0
  215. package/dist/knowledge/references/business-model.snapshot.validation.md +18 -0
  216. package/dist/knowledge/references/capability-composition.config.md +4 -3
  217. package/dist/knowledge/references/cli.market.generate-command.md +2 -1
  218. package/dist/knowledge/references/companion.market.prompt-renderer.md +11 -6
  219. package/dist/knowledge/references/companion.technical-doc.service.md +166 -32
  220. package/dist/knowledge/references/engine.client-bundle.allow-list.md +14 -0
  221. package/dist/knowledge/references/engine.saas-technical-doc.config.md +1 -1
  222. package/dist/knowledge/references/engine.saas-website.config.md +16 -44
  223. package/dist/knowledge/references/example.ai-use-declaration.agent.md +37 -0
  224. package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +44 -0
  225. package/dist/knowledge/references/{example.authorization.service-provider-organization-wide-access.md → example.authorization.relationship-organization-wide-access.md} +2 -2
  226. package/dist/knowledge/references/example.backend.custom-operation.audit-event.md +81 -0
  227. package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +259 -0
  228. package/dist/knowledge/references/example.backend.custom-operation.computed-total.md +153 -0
  229. package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +129 -0
  230. package/dist/knowledge/references/example.blueprint.definition.internal-tool.md +45 -0
  231. package/dist/knowledge/references/example.config.app-shell.full.md +6 -3
  232. package/dist/knowledge/references/example.config.app-shell.hosted-components.md +4 -1
  233. package/dist/knowledge/references/example.config.backend.inbound-email.md +4 -2
  234. package/dist/knowledge/references/example.config.backend.required-floors.md +4 -2
  235. package/dist/knowledge/references/example.config.design-system.full.md +40 -116
  236. package/dist/knowledge/references/example.data-seeding.minimal.md +10 -9
  237. package/dist/knowledge/references/example.data-seeding.row-reference.md +80 -0
  238. package/dist/knowledge/references/example.email.template.minimal.md +1 -1
  239. package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +10 -0
  240. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +70 -14
  241. package/dist/knowledge/references/example.flows-actors.declared-flow.md +115 -0
  242. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +12 -0
  243. package/dist/knowledge/references/example.inbound.email-channel-handler.md +10 -1
  244. package/dist/knowledge/references/example.infra.environment-config.local.md +24 -0
  245. package/dist/knowledge/references/example.layout-2d.registration.md +11 -0
  246. package/dist/knowledge/references/example.minion.contained-tick.md +1 -1
  247. package/dist/knowledge/references/example.module.relationships.scope-membership-junction.md +8 -10
  248. package/dist/knowledge/references/example.organizations.relationship-kinds.md +26 -0
  249. package/dist/knowledge/references/example.professional-qualifications.declaration.md +10 -0
  250. package/dist/knowledge/references/example.professional-qualifications.gate.md +25 -0
  251. package/dist/knowledge/references/example.provider.backend-module-shape.md +10 -0
  252. package/dist/knowledge/references/example.provider.frontend-facet.on-demand-sdk.md +41 -0
  253. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +4 -5
  254. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +7 -5
  255. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -1
  256. package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +74 -0
  257. package/dist/knowledge/references/example.resource.personal-data.free-text-field.md +19 -0
  258. package/dist/knowledge/references/example.resource.personal-data.person-without-account.md +27 -0
  259. package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +152 -0
  260. package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +23 -7
  261. package/dist/knowledge/references/example.resource.ui-behavior.filter-presets.md +15 -0
  262. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +60 -22
  263. package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +81 -0
  264. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +19 -20
  265. package/dist/knowledge/references/example.spec.composite-view.workspace.md +10 -2
  266. package/dist/knowledge/references/example.views.app-level.home-definition.md +13 -0
  267. package/dist/knowledge/references/example.views.chart-definition.shared.md +83 -0
  268. package/dist/knowledge/references/example.views.composite-view.workspace.md +10 -3
  269. package/dist/knowledge/references/example.website.blocks.section.md +20 -0
  270. package/dist/knowledge/references/example.website.blocks.site-choices.md +78 -0
  271. package/dist/knowledge/references/example.website.blocks.site-configs.md +155 -0
  272. package/dist/knowledge/references/example.website.demo.append.md +57 -0
  273. package/dist/knowledge/references/example.website.demo.approval.md +47 -0
  274. package/dist/knowledge/references/example.website.demo.celebrate.md +39 -0
  275. package/dist/knowledge/references/example.website.demo.complete-items.md +103 -0
  276. package/dist/knowledge/references/example.website.demo.connect.md +45 -0
  277. package/dist/knowledge/references/example.website.demo.dashboard.md +74 -0
  278. package/dist/knowledge/references/example.website.demo.query-answer.md +77 -0
  279. package/dist/knowledge/references/example.website.demo.status-lifecycle.md +71 -0
  280. package/dist/knowledge/references/example.website.demo.transform.md +43 -0
  281. package/dist/knowledge/references/example.website.page.manifest.md +2 -6
  282. package/dist/knowledge/references/example.website.section.bento.md +27 -0
  283. package/dist/knowledge/references/example.website.section.contact-form.md +15 -0
  284. package/dist/knowledge/references/example.website.section.factories.md +82 -0
  285. package/dist/knowledge/references/example.website.section.faq.md +17 -0
  286. package/dist/knowledge/references/example.website.section.footer-cta.md +13 -0
  287. package/dist/knowledge/references/example.website.section.hero.md +16 -0
  288. package/dist/knowledge/references/example.website.section.latest-posts.md +15 -0
  289. package/dist/knowledge/references/example.website.section.marquee.md +26 -0
  290. package/dist/knowledge/references/example.website.section.roadmap.md +25 -0
  291. package/dist/knowledge/references/example.website.section.site-block.md +43 -0
  292. package/dist/knowledge/references/example.website.section.solution-paths.md +17 -0
  293. package/dist/knowledge/references/example.website.section.stats.md +23 -0
  294. package/dist/knowledge/references/example.website.section.steps.md +15 -0
  295. package/dist/knowledge/references/example.website.showcase.tour.md +49 -0
  296. package/dist/knowledge/references/example.website.theme.composed.md +69 -0
  297. package/dist/knowledge/references/experience-plan.config.md +76 -7
  298. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +6 -0
  299. package/dist/knowledge/references/external-connectors.frontend-provider-sdk-activation-mode.md +27 -0
  300. package/dist/knowledge/references/external-connectors.models.connection-target.md +99 -0
  301. package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +6 -0
  302. package/dist/knowledge/references/external-connectors.models.hook-inbound-endpoint.md +352 -0
  303. package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +64 -0
  304. package/dist/knowledge/references/external-connectors.models.hook-trigger-strategy.md +97 -0
  305. package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +61 -2
  306. package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +70 -0
  307. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +253 -0
  308. package/dist/knowledge/references/external-connectors.models.subject-erasure-effect.md +105 -0
  309. package/dist/knowledge/references/integration-plan.config.md +21 -1
  310. package/dist/knowledge/references/market.context-block.builder.md +1 -1
  311. package/dist/knowledge/references/market.references.weighted-edges.md +14 -1
  312. package/dist/knowledge/references/minions.tick-contract.md +2 -2
  313. package/dist/knowledge/references/placement-plan.config.md +107 -2
  314. package/dist/knowledge/references/platform.config.environment.deployment.md +9 -1
  315. package/dist/knowledge/references/platform.config.infrastructure-host.md +2 -0
  316. package/dist/knowledge/references/platform.config.platform-key-management.md +206 -0
  317. package/dist/knowledge/references/platform.config.saas.md +106 -14
  318. package/dist/knowledge/references/platform.key-management.vault-custody.md +78 -0
  319. package/dist/knowledge/references/presets.3d.layout-contract.md +4 -30
  320. package/dist/knowledge/references/presets.3d.register-layout.md +14 -36
  321. package/dist/knowledge/references/presets.layouts-2d.authoring.md +157 -0
  322. package/dist/knowledge/references/presets.layouts-2d.register-layout.md +53 -0
  323. package/dist/knowledge/references/presets.layouts-2d.settings.md +53 -0
  324. package/dist/knowledge/references/presets.layouts-2d.vocabulary.md +41 -0
  325. package/dist/knowledge/references/presets.models.palette-contrast.md +183 -0
  326. package/dist/knowledge/references/presets.models.palette-derivation.md +93 -0
  327. package/dist/knowledge/references/presets.models.surface-policy.defaults.md +27 -0
  328. package/dist/knowledge/references/presets.models.surface-variant.md +10 -0
  329. package/dist/knowledge/references/presets.models.theme-contract.md +136 -0
  330. package/dist/knowledge/references/presets.models.theme-personality-lexicon.md +81 -0
  331. package/dist/knowledge/references/presets.models.theme-personality.md +159 -0
  332. package/dist/knowledge/references/presets.themes.compose-theme.md +46 -0
  333. package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -2
  334. package/dist/knowledge/references/requirements.non-functional-requirement.config.md +2 -0
  335. package/dist/knowledge/references/requirements.references.conventions.md +1 -1
  336. package/dist/knowledge/references/requirements.snapshot.config.md +57 -1
  337. package/dist/knowledge/references/requirements.snapshot.validation.md +35 -1
  338. package/dist/knowledge/references/roadmap.phase.config.md +2 -16
  339. package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +131 -0
  340. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +77 -11
  341. package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +158 -0
  342. package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +3 -1
  343. package/dist/knowledge/references/saas.backend.audit-logs.log-event.md +63 -0
  344. package/dist/knowledge/references/saas.backend.crypto-keys.application-keys.md +100 -0
  345. package/dist/knowledge/references/saas.backend.custom-operation.commit-outcome-read-back.md +208 -0
  346. package/dist/knowledge/references/saas.backend.custom-operation.target-authority.md +33 -0
  347. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +131 -1
  348. package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +60 -0
  349. package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +156 -0
  350. package/dist/knowledge/references/saas.backend.domain-module.md +76 -1
  351. package/dist/knowledge/references/saas.backend.email-template.definition.md +34 -0
  352. package/dist/knowledge/references/saas.backend.email-template.words.md +98 -0
  353. package/dist/knowledge/references/saas.backend.email.send.md +84 -0
  354. package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +9 -1
  355. package/dist/knowledge/references/saas.backend.flows-actors.ask-person-tool.md +79 -0
  356. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-case-selector.md +71 -0
  357. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +21 -10
  358. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +11 -5
  359. package/dist/knowledge/references/saas.backend.flows-actors.chat-agent-declaration.md +51 -0
  360. package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +207 -0
  361. package/dist/knowledge/references/saas.backend.flows-actors.decision-notice-handler.md +239 -0
  362. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +300 -3
  363. package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +13 -2
  364. package/dist/knowledge/references/saas.backend.flows-actors.operation-approval-resolvers.md +50 -0
  365. package/dist/knowledge/references/saas.backend.flows-actors.present-records-tool.md +106 -0
  366. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +14 -1
  367. package/dist/knowledge/references/saas.backend.flows-actors.retrieval-tool.md +205 -0
  368. package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +21 -5
  369. package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +27 -0
  370. package/dist/knowledge/references/saas.backend.flows.start-flow.md +47 -0
  371. package/dist/knowledge/references/saas.backend.notifications.operation-email-template-ref.md +60 -0
  372. package/dist/knowledge/references/saas.backend.pdf-template.collection-definition.md +5 -3
  373. package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +15 -25
  374. package/dist/knowledge/references/saas.backend.rate-limit-service.check-policy.md +3 -2
  375. package/dist/knowledge/references/saas.backend.submission-challenge.md +4 -0
  376. package/dist/knowledge/references/saas.backend.system-access-service.md +242 -107
  377. package/dist/knowledge/references/saas.config.content-security-policy.md +1 -2
  378. package/dist/knowledge/references/saas.data-seeding.computed-entry.md +43 -0
  379. package/dist/knowledge/references/saas.data-seeding.definition-input.md +8 -2
  380. package/dist/knowledge/references/saas.data-seeding.row-reference.md +93 -0
  381. package/dist/knowledge/references/saas.data-seeding.run-ledger.md +3 -0
  382. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +70 -3
  383. package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +3 -0
  384. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +10 -2
  385. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +10 -16
  386. package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +7 -3
  387. package/dist/knowledge/references/saas.frontend.app-shell.register-shell-layout.md +97 -0
  388. package/dist/knowledge/references/saas.frontend.app-shell.shell-layout-contract.md +60 -0
  389. package/dist/knowledge/references/saas.frontend.app-shell.shell-motion-contract.md +274 -0
  390. package/dist/knowledge/references/saas.frontend.app-shell.use-shell-motion.md +73 -0
  391. package/dist/knowledge/references/saas.frontend.brand-identity.md +6 -0
  392. package/dist/knowledge/references/saas.frontend.chart-view.inserted-declaration.md +13 -0
  393. package/dist/knowledge/references/saas.frontend.chat-sign-in-completion.md +99 -0
  394. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +126 -0
  395. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +9 -3
  396. package/dist/knowledge/references/saas.frontend.domain-module.md +5 -0
  397. package/dist/knowledge/references/saas.frontend.embedded-resource-descent.md +2 -1
  398. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +17 -3
  399. package/dist/knowledge/references/saas.frontend.field-tiles.md +76 -0
  400. package/dist/knowledge/references/saas.frontend.flows-actors-view.md +10 -2
  401. package/dist/knowledge/references/saas.frontend.focus-indicator.md +119 -0
  402. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +324 -0
  403. package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +109 -0
  404. package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +61 -0
  405. package/dist/knowledge/references/saas.frontend.operation-key-and-resource-config-like.md +68 -1
  406. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +14 -24
  407. package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +149 -0
  408. package/dist/knowledge/references/saas.frontend.resource-header-title.md +98 -34
  409. package/dist/knowledge/references/saas.frontend.resource-label-params.md +54 -0
  410. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +17 -11
  411. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +125 -58
  412. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +13 -7
  413. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destination-roles.md +25 -0
  414. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +141 -32
  415. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +64 -2
  416. package/dist/knowledge/references/saas.models.agent-suspension.md +75 -0
  417. package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +2 -2
  418. package/dist/knowledge/references/saas.models.agent-work-decision-contents-read.md +69 -0
  419. package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +11 -2
  420. package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +20 -3
  421. package/dist/knowledge/references/saas.models.agent-work-output-review.md +3 -3
  422. package/dist/knowledge/references/saas.models.agent-work-override-rate.md +6 -5
  423. package/dist/knowledge/references/saas.models.agent-work-review-config.md +22 -4
  424. package/dist/knowledge/references/saas.models.analytics.value-moments.md +22 -0
  425. package/dist/knowledge/references/saas.models.application-agent-policy.md +28 -0
  426. package/dist/knowledge/references/saas.models.application-entry-points.md +45 -0
  427. package/dist/knowledge/references/saas.models.audit.trail-config.md +63 -5
  428. package/dist/knowledge/references/{saas.models.auth.service-provider-client-authentication.md → saas.models.auth.relationship-grantor-authentication.md} +54 -48
  429. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +4 -4
  430. package/dist/knowledge/references/saas.models.chat-identity-link-host.md +38 -0
  431. package/dist/knowledge/references/saas.models.compliance.ai-use-classification.md +179 -0
  432. package/dist/knowledge/references/saas.models.compliance.ai-use-posture.md +121 -0
  433. package/dist/knowledge/references/saas.models.config.organization-types.md +42 -82
  434. package/dist/knowledge/references/saas.models.conversation-threads.md +4 -3
  435. package/dist/knowledge/references/saas.models.crypto-keys.floors.md +22 -0
  436. package/dist/knowledge/references/saas.models.crypto-keys.key-management-config.md +130 -0
  437. package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +27 -0
  438. package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +403 -0
  439. package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +84 -0
  440. package/dist/knowledge/references/saas.models.data-mode-read-list.md +24 -1
  441. package/dist/knowledge/references/saas.models.engine-capabilities.md +28 -0
  442. package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +16 -9
  443. package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +23 -6
  444. package/dist/knowledge/references/saas.models.external-data-conflict-vocabulary.md +53 -0
  445. package/dist/knowledge/references/saas.models.external-data-pipeline.md +81 -18
  446. package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report-config.md +28 -0
  447. package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +317 -0
  448. package/dist/knowledge/references/saas.models.flows-actors.agent-content-guardrails.md +150 -0
  449. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +45 -0
  450. package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +147 -0
  451. package/dist/knowledge/references/saas.models.flows-actors.autonomous-agents-vocabulary.md +49 -7
  452. package/dist/knowledge/references/saas.models.flows-actors.chat-agents-vocabulary.md +26 -0
  453. package/dist/knowledge/references/saas.models.flows-actors.decision-card-wording.md +284 -0
  454. package/dist/knowledge/references/saas.models.flows-actors.decision-notice-recorded-cards.md +93 -0
  455. package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +62 -0
  456. package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +314 -0
  457. package/dist/knowledge/references/saas.models.flows-actors.operation-approval-pending.md +55 -0
  458. package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +62 -0
  459. package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +6 -0
  460. package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +1 -0
  461. package/dist/knowledge/references/saas.models.flows.run-state.md +49 -0
  462. package/dist/knowledge/references/saas.models.flows.runnable-model.md +255 -0
  463. package/dist/knowledge/references/saas.models.frontend-on-demand-capability-contract.md +54 -0
  464. package/dist/knowledge/references/saas.models.http-api-binding.md +157 -42
  465. package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +3 -3
  466. package/dist/knowledge/references/saas.models.http-api-population-filter.md +51 -0
  467. package/dist/knowledge/references/saas.models.inbound-channels.md +4 -1
  468. package/dist/knowledge/references/saas.models.inbound-email-domains.md +5 -5
  469. package/dist/knowledge/references/saas.models.inbound-email.md +2 -2
  470. package/dist/knowledge/references/saas.models.m2m-webhook-events.md +73 -0
  471. package/dist/knowledge/references/saas.models.model-cost-summary.md +56 -20
  472. package/dist/knowledge/references/saas.models.notifications.targets.md +25 -2
  473. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +63 -9
  474. package/dist/knowledge/references/saas.models.on-demand-provider-capabilities.md +28 -0
  475. package/dist/knowledge/references/saas.models.organization-agent-policy.md +43 -0
  476. package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +73 -0
  477. package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +48 -0
  478. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +6 -6
  479. package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +9 -10
  480. package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +911 -0
  481. package/dist/knowledge/references/saas.models.organizations.professional-qualification-kinds.md +46 -0
  482. package/dist/knowledge/references/saas.models.organizations.professional-qualifications.md +168 -0
  483. package/dist/knowledge/references/{saas.models.organizations.service-provider-capability-grants.md → saas.models.organizations.relationship-capability-grants.md} +56 -35
  484. package/dist/knowledge/references/saas.models.organizations.relationship-grantor-controls.md +62 -0
  485. package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +224 -0
  486. package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +277 -0
  487. package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +113 -0
  488. package/dist/knowledge/references/saas.models.privacy.legal-holds.md +68 -5
  489. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +67 -2
  490. package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +13 -14
  491. package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +278 -40
  492. package/dist/knowledge/references/saas.models.provider-capabilities.md +33 -0
  493. package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +50 -1
  494. package/dist/knowledge/references/saas.models.providers.capability-activation-policy.md +28 -0
  495. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +8 -0
  496. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +37 -0
  497. package/dist/knowledge/references/saas.models.providers.execute-operation-request.md +25 -0
  498. package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +1 -1
  499. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +13 -1
  500. package/dist/knowledge/references/saas.models.rate-limit-configuration.md +4 -4
  501. package/dist/knowledge/references/saas.models.representative-activity.md +65 -0
  502. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +84 -2
  503. package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +24 -0
  504. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +57 -11
  505. package/dist/knowledge/references/saas.models.resource-config.operation-base.md +20 -3
  506. package/dist/knowledge/references/saas.models.resource-config.operation-bulk.md +37 -0
  507. package/dist/knowledge/references/saas.models.resource-config.operation-chat-command.md +39 -0
  508. package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +1 -1
  509. package/dist/knowledge/references/saas.models.resource-config.operation-required-qualifications.md +30 -0
  510. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +99 -2
  511. package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +1 -1
  512. package/dist/knowledge/references/saas.models.resource-config.operation-union.md +0 -1
  513. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +1 -1
  514. package/dist/knowledge/references/saas.models.resource-config.record-label-fields.md +23 -0
  515. package/dist/knowledge/references/saas.models.resource-config.request-field-offers.md +104 -0
  516. package/dist/knowledge/references/saas.models.resource-config.required-features.md +20 -0
  517. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +9 -0
  518. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +25 -3
  519. package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +25 -0
  520. package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +2 -1
  521. package/dist/knowledge/references/saas.models.resource-config.token-generation.md +1 -1
  522. package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +3 -2
  523. package/dist/knowledge/references/saas.models.resource-relationship-builder-parameters.md +6 -2
  524. package/dist/knowledge/references/saas.models.roadmap.phase-horizon.md +31 -0
  525. package/dist/knowledge/references/saas.models.roles.definition.md +61 -0
  526. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +97 -0
  527. package/dist/knowledge/references/saas.models.schema-family-builder.md +17 -4
  528. package/dist/knowledge/references/saas.models.scope-membership.md +2 -2
  529. package/dist/knowledge/references/saas.models.system-of-record-capabilities.md +121 -0
  530. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +3 -2
  531. package/dist/knowledge/references/saas.models.systems-of-record.md +36 -1
  532. package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +7 -3
  533. package/dist/knowledge/references/saas.models.work-unit-ref.md +17 -2
  534. package/dist/knowledge/references/saas.public-runtime.contract.md +60 -2
  535. package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +3 -2
  536. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +13 -0
  537. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +275 -13
  538. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +5 -4
  539. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +9 -0
  540. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +16 -2
  541. package/dist/knowledge/references/saas.specifications.processor-register.md +10 -1
  542. package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +111 -2
  543. package/dist/knowledge/references/saas.specifications.recipient-population.md +46 -0
  544. package/dist/knowledge/references/saas.specifications.resource-frontend-configuration-aspect.md +7 -0
  545. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +24 -2
  546. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +21 -7
  547. package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +19 -5
  548. package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +136 -6
  549. package/dist/knowledge/references/saas.website.astro.bridge.md +61 -14
  550. package/dist/knowledge/references/saas.website.astro.head-renderer.md +63 -27
  551. package/dist/knowledge/references/saas.website.astro.i18n-helper.md +39 -10
  552. package/dist/knowledge/references/saas.website.astro.label-key-collector.md +12 -11
  553. package/dist/knowledge/references/saas.website.astro.label-loader.md +41 -9
  554. package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +14 -1
  555. package/dist/knowledge/references/saas.website.astro.pick-labels-for-page.md +1 -2
  556. package/dist/knowledge/references/saas.website.astro.runtime-helper.md +48 -17
  557. package/dist/knowledge/references/saas.website.astro.site-context.md +30 -8
  558. package/dist/knowledge/references/saas.website.astro.structured-data-renderer.md +29 -8
  559. package/dist/knowledge/references/saas.website.blocks.actions.md +91 -0
  560. package/dist/knowledge/references/saas.website.blocks.band.md +41 -0
  561. package/dist/knowledge/references/saas.website.blocks.bento.md +70 -0
  562. package/dist/knowledge/references/saas.website.blocks.card-grid.md +115 -0
  563. package/dist/knowledge/references/saas.website.blocks.card.md +77 -0
  564. package/dist/knowledge/references/saas.website.blocks.cta-band.md +94 -0
  565. package/dist/knowledge/references/saas.website.blocks.define-block.md +123 -0
  566. package/dist/knowledge/references/saas.website.blocks.definitions.md +132 -0
  567. package/dist/knowledge/references/saas.website.blocks.faq.md +89 -0
  568. package/dist/knowledge/references/saas.website.blocks.feature-row.md +109 -0
  569. package/dist/knowledge/references/saas.website.blocks.hero.md +140 -0
  570. package/dist/knowledge/references/saas.website.blocks.intro.md +68 -0
  571. package/dist/knowledge/references/saas.website.blocks.latest-posts.md +104 -0
  572. package/dist/knowledge/references/saas.website.blocks.marquee.md +76 -0
  573. package/dist/knowledge/references/saas.website.blocks.pricing.md +395 -0
  574. package/dist/knowledge/references/saas.website.blocks.product-tour.md +158 -0
  575. package/dist/knowledge/references/saas.website.blocks.quote-cards.md +64 -0
  576. package/dist/knowledge/references/saas.website.blocks.roadmap.md +108 -0
  577. package/dist/knowledge/references/saas.website.blocks.section-slots.md +64 -0
  578. package/dist/knowledge/references/saas.website.blocks.solution-paths.md +71 -0
  579. package/dist/knowledge/references/saas.website.blocks.stats.md +183 -0
  580. package/dist/knowledge/references/saas.website.blocks.steps.md +69 -0
  581. package/dist/knowledge/references/saas.website.blocks.stylesheet.md +68 -0
  582. package/dist/knowledge/references/saas.website.blocks.tables.md +153 -0
  583. package/dist/knowledge/references/saas.website.blocks.vocabulary.md +227 -0
  584. package/dist/knowledge/references/saas.website.blog.bridge.md +102 -53
  585. package/dist/knowledge/references/saas.website.blog.collection-config.md +76 -24
  586. package/dist/knowledge/references/saas.website.blog.cover-resolver.md +93 -0
  587. package/dist/knowledge/references/saas.website.blog.frontmatter.md +104 -7
  588. package/dist/knowledge/references/saas.website.blog.head-renderer.md +37 -19
  589. package/dist/knowledge/references/saas.website.blog.index-builder.md +63 -0
  590. package/dist/knowledge/references/saas.website.blog.index.md +43 -0
  591. package/dist/knowledge/references/saas.website.blog.post-cover.md +38 -0
  592. package/dist/knowledge/references/saas.website.blog.post-renderer.md +113 -85
  593. package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +181 -0
  594. package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +26 -0
  595. package/dist/knowledge/references/saas.website.blog.vocabulary-labels.md +113 -0
  596. package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +2 -1
  597. package/dist/knowledge/references/saas.website.config.site-context-loader.md +24 -1
  598. package/dist/knowledge/references/saas.website.consent.banner.md +1 -1
  599. package/dist/knowledge/references/saas.website.consent.context.md +1 -1
  600. package/dist/knowledge/references/saas.website.design-tokens.bundle.md +28 -6
  601. package/dist/knowledge/references/saas.website.design-tokens.colors.md +7 -6
  602. package/dist/knowledge/references/saas.website.design-tokens.compose-function.md +35 -0
  603. package/dist/knowledge/references/saas.website.design-tokens.compose.md +76 -0
  604. package/dist/knowledge/references/saas.website.design-tokens.personality-derivation.md +22 -0
  605. package/dist/knowledge/references/saas.website.design-tokens.personality-lexicon.md +31 -0
  606. package/dist/knowledge/references/saas.website.design-tokens.personality.md +82 -0
  607. package/dist/knowledge/references/saas.website.design-tokens.product.md +122 -0
  608. package/dist/knowledge/references/saas.website.design-tokens.radius.md +12 -1
  609. package/dist/knowledge/references/saas.website.design-tokens.readers.md +58 -0
  610. package/dist/knowledge/references/saas.website.design-tokens.spacing.md +61 -0
  611. package/dist/knowledge/references/saas.website.design-tokens.surface-depth.md +60 -0
  612. package/dist/knowledge/references/saas.website.design-tokens.tones.md +75 -0
  613. package/dist/knowledge/references/saas.website.design-tokens.typography.md +115 -0
  614. package/dist/knowledge/references/saas.website.factories.define-page-manifest.md +23 -21
  615. package/dist/knowledge/references/saas.website.factories.define-section.md +36 -38
  616. package/dist/knowledge/references/saas.website.format.publication-date.md +26 -0
  617. package/dist/knowledge/references/saas.website.label-keys.compose-helper.md +1 -1
  618. package/dist/knowledge/references/saas.website.label-keys.format.md +2 -2
  619. package/dist/knowledge/references/saas.website.label-pack.validator.md +7 -8
  620. package/dist/knowledge/references/saas.website.labels.section-labels.md +34 -0
  621. package/dist/knowledge/references/saas.website.legal.public-document-links.md +91 -0
  622. package/dist/knowledge/references/saas.website.locale-switcher.label-keys.md +35 -0
  623. package/dist/knowledge/references/saas.website.menu.icons.md +123 -0
  624. package/dist/knowledge/references/saas.website.menu.label-keys.md +112 -0
  625. package/dist/knowledge/references/saas.website.menu.schema.md +92 -0
  626. package/dist/knowledge/references/saas.website.menu.vocabulary.md +79 -0
  627. package/dist/knowledge/references/saas.website.motion.demo-player.md +105 -0
  628. package/dist/knowledge/references/saas.website.motion.demo-scenario.md +460 -0
  629. package/dist/knowledge/references/saas.website.motion.demo.md +324 -0
  630. package/dist/knowledge/references/saas.website.motion.element-attributes.md +115 -0
  631. package/dist/knowledge/references/saas.website.motion.reveal-renditions.md +67 -0
  632. package/dist/knowledge/references/saas.website.motion.stylesheet.md +82 -0
  633. package/dist/knowledge/references/saas.website.motion.tempo-table.md +99 -0
  634. package/dist/knowledge/references/saas.website.motion.tokens.md +46 -0
  635. package/dist/knowledge/references/saas.website.motion.vocabulary.md +85 -0
  636. package/dist/knowledge/references/saas.website.page-layout.component.md +34 -8
  637. package/dist/knowledge/references/saas.website.page-manifest.meta-label-keys.md +4 -4
  638. package/dist/knowledge/references/saas.website.page-manifest.route-path.md +1 -1
  639. package/dist/knowledge/references/saas.website.page-manifest.schema.md +25 -29
  640. package/dist/knowledge/references/saas.website.page-manifest.seo.md +1 -1
  641. package/dist/knowledge/references/saas.website.page-navigation.md +44 -0
  642. package/dist/knowledge/references/saas.website.page.context.md +9 -2
  643. package/dist/knowledge/references/saas.website.primitives.button.md +6 -6
  644. package/dist/knowledge/references/saas.website.primitives.heading.md +17 -18
  645. package/dist/knowledge/references/saas.website.primitives.image.md +18 -15
  646. package/dist/knowledge/references/saas.website.primitives.internal-button.md +11 -12
  647. package/dist/knowledge/references/saas.website.primitives.internal-link.md +11 -35
  648. package/dist/knowledge/references/saas.website.primitives.link.md +22 -11
  649. package/dist/knowledge/references/saas.website.primitives.text.md +10 -8
  650. package/dist/knowledge/references/saas.website.product.atoms.md +366 -0
  651. package/dist/knowledge/references/saas.website.product.figures.md +320 -0
  652. package/dist/knowledge/references/saas.website.product.hooks.md +278 -0
  653. package/dist/knowledge/references/saas.website.product.panels.md +324 -0
  654. package/dist/knowledge/references/saas.website.product.stylesheet.md +1086 -0
  655. package/dist/knowledge/references/saas.website.refs.section.md +2 -2
  656. package/dist/knowledge/references/saas.website.root-config.schema.md +34 -17
  657. package/dist/knowledge/references/saas.website.root-config.seo.md +2 -1
  658. package/dist/knowledge/references/saas.website.routing.link-target.md +70 -0
  659. package/dist/knowledge/references/saas.website.routing.localized-path.md +15 -8
  660. package/dist/knowledge/references/saas.website.runtime.context.md +51 -17
  661. package/dist/knowledge/references/saas.website.section.component.md +21 -19
  662. package/dist/knowledge/references/saas.website.sections.category-enum.md +21 -2
  663. package/dist/knowledge/references/saas.website.sections.definition-schema.md +47 -39
  664. package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +2 -0
  665. package/dist/knowledge/references/saas.website.site-footer.menu.md +47 -0
  666. package/dist/knowledge/references/saas.website.site-header.component.md +100 -0
  667. package/dist/knowledge/references/saas.website.site-header.scroll-behavior.md +26 -0
  668. package/dist/knowledge/references/saas.website.stacking.md +86 -0
  669. package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +162 -0
  670. package/dist/knowledge/references/saas.website.use-blog-index.hook.md +27 -0
  671. package/dist/knowledge/references/saas.website.use-label.hook.md +6 -4
  672. package/dist/knowledge/references/service-method.config.md +270 -0
  673. package/dist/knowledge/references/website-plan.config.md +561 -23
  674. package/dist/knowledge/references/website-plan.menu-placement.md +118 -0
  675. package/dist/knowledge/references/website-plan.page-kind-essentials.md +42 -0
  676. package/dist/knowledge/references/website-plan.page-routes.md +39 -0
  677. package/dist/knowledge/references/workers.node.worker-init-contract.md +4 -2
  678. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +86 -9
  679. package/dist/knowledge/references/zod.decorators.chrome-modes.md +92 -0
  680. package/dist/knowledge/references/zod.decorators.data-categories.md +101 -11
  681. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +82 -6
  682. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +23 -1
  683. package/dist/knowledge/references/zod.decorators.document-sequence.md +65 -0
  684. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +41 -7
  685. package/dist/knowledge/references/zod.decorators.file-schema.md +6 -5
  686. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +25 -9
  687. package/dist/knowledge/references/zod.decorators.primitive-ui.md +15 -3
  688. package/dist/knowledge/references/zod.decorators.schema-metadata.md +5 -0
  689. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +50 -1
  690. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +44 -5
  691. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +130 -9
  692. package/dist/knowledge/references/zod.factories.bigdecimal.md +17 -7
  693. package/dist/knowledge/references/zod.factories.code.md +18 -8
  694. package/dist/knowledge/references/zod.factories.duration.md +23 -13
  695. package/dist/knowledge/references/zod.factories.money.md +24 -14
  696. package/dist/knowledge/references/zod.factories.phone.md +23 -14
  697. package/dist/knowledge/references/zod.factories.range.md +5 -1
  698. package/dist/knowledge/registries/assurance-authority-bases.json +3 -3
  699. package/dist/knowledge/registries/framework-topics.json +2854 -246
  700. package/dist/knowledge/registries/playbooks.json +57 -36
  701. package/dist/knowledge/registries/source-tags.json +8863 -4569
  702. package/dist/knowledge/rules/database-migration-obligation.md +11 -5
  703. package/dist/knowledge/rules/live-context-door.md +1 -1
  704. package/dist/knowledge/skills/INDEX.md +63 -34
  705. package/dist/knowledge/skills/agent-work-review/SKILL.md +86 -23
  706. package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +203 -0
  707. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +2 -2
  708. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-decision-contents-api.md +79 -0
  709. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +4 -4
  710. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +6 -5
  711. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +22 -4
  712. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +15 -3
  713. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +20 -3
  714. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +16 -9
  715. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +24 -7
  716. package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +341 -0
  717. package/dist/knowledge/skills/ai-use-declaration/SKILL.md +192 -0
  718. package/dist/knowledge/skills/ai-use-declaration/references/choosing-the-domain-and-class.md +73 -0
  719. package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-classification-api.md +194 -0
  720. package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-posture-api.md +136 -0
  721. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +16 -3
  722. package/dist/knowledge/skills/application-database-migrations/SKILL.md +41 -12
  723. package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +34 -0
  724. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +158 -0
  725. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +169 -0
  726. package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +63 -0
  727. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +130 -4
  728. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +90 -0
  729. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-own-rows-declaration-api.md +59 -0
  730. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +6 -6
  731. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +79 -2
  732. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +291 -10
  733. package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +42 -0
  734. package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +3 -2
  735. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +223 -0
  736. package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +20 -3
  737. package/dist/knowledge/skills/backend-custom-operation/references/framework-target-authority-api.md +61 -0
  738. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +368 -1
  739. package/dist/knowledge/skills/blueprint-authoring/SKILL.md +189 -0
  740. package/dist/knowledge/skills/blueprint-authoring/references/blueprint-content-kinds.md +29 -0
  741. package/dist/knowledge/skills/blueprint-authoring/references/framework-blueprint-definition-api.md +490 -0
  742. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +132 -2
  743. package/dist/knowledge/skills/brand-logo-authoring/references/brand-authoring-decisions.md +15 -3
  744. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +26 -8
  745. package/dist/knowledge/skills/brand-logo-authoring/references/framework-style-word-lexicon-api.md +126 -0
  746. package/dist/knowledge/skills/brand-name-screening/SKILL.md +33 -9
  747. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +78 -6
  748. package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +30 -8
  749. package/dist/knowledge/skills/chat-agent-conversations/SKILL.md +163 -0
  750. package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +295 -0
  751. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -1
  752. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +8 -6
  753. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +136 -34
  754. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +4 -3
  755. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +13 -0
  756. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +34 -7
  757. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +10 -1
  758. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +37 -0
  759. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +178 -4
  760. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +46 -0
  761. package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +485 -61
  762. package/dist/knowledge/skills/config-app-shell/SKILL.md +101 -19
  763. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +20 -18
  764. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +7 -3
  765. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-hosted-components-api.md +13 -0
  766. package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +20 -0
  767. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +472 -0
  768. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +82 -0
  769. package/dist/knowledge/skills/config-app-shell/references/framework-shell-layout-api.md +528 -0
  770. package/dist/knowledge/skills/config-design-system/SKILL.md +271 -166
  771. package/dist/knowledge/skills/config-design-system/references/design-system-file.md +5 -1
  772. package/dist/knowledge/skills/config-design-system/references/framework-focus-indicator-api.md +182 -0
  773. package/dist/knowledge/skills/config-design-system/references/framework-palette-contrast-api.md +195 -0
  774. package/dist/knowledge/skills/config-design-system/references/framework-palette-derivation-api.md +108 -0
  775. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +37 -0
  776. package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +235 -0
  777. package/dist/knowledge/skills/config-design-system/references/theme-design-principles.md +202 -0
  778. package/dist/knowledge/skills/config-navigation/SKILL.md +14 -3
  779. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +16 -5
  780. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +1 -1
  781. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +7 -1
  782. package/dist/knowledge/skills/config-saas/SKILL.md +27 -11
  783. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +62 -4
  784. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +80 -7
  785. package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +314 -0
  786. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +29 -1
  787. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +8 -0
  788. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +1 -2
  789. package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +1182 -0
  790. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +61 -0
  791. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +56 -11
  792. package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +22 -0
  793. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +106 -14
  794. package/dist/knowledge/skills/config-saas-backend/SKILL.md +11 -4
  795. package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +9 -10
  796. package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +6 -4
  797. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +155 -92
  798. package/dist/knowledge/skills/configure-billing/SKILL.md +32 -4
  799. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +10 -0
  800. package/dist/knowledge/skills/configure-billing/references/framework-metered-usage-recording-api.md +109 -0
  801. package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +18 -2
  802. package/dist/knowledge/skills/email-add-template/SKILL.md +72 -9
  803. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +1 -1
  804. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +135 -0
  805. package/dist/knowledge/skills/email-add-template/references/framework-email-template-api.md +134 -0
  806. package/dist/knowledge/skills/email-add-template/references/framework-operation-email-template-ref-api.md +99 -0
  807. package/dist/knowledge/skills/engine-component-registration/SKILL.md +6 -1
  808. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +21 -8
  809. package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +28 -0
  810. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +71 -14
  811. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +95 -13
  812. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +9 -1
  813. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +98 -9
  814. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +44 -16
  815. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +160 -23
  816. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +10 -3
  817. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +14 -2
  818. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +291 -22
  819. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +70 -14
  820. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +451 -0
  821. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +406 -0
  822. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +201 -0
  823. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +172 -0
  824. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-ask-person-tool-api.md +121 -0
  825. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +7 -0
  826. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +63 -0
  827. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +324 -7
  828. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +95 -6
  829. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +255 -0
  830. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-present-records-tool-api.md +150 -0
  831. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-retrieval-tool-api.md +251 -0
  832. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +112 -16
  833. package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +339 -0
  834. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +264 -0
  835. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +133 -0
  836. package/dist/knowledge/skills/flows-actors-declared-flow/references/step-kinds.md +16 -0
  837. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +109 -9
  838. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +45 -0
  839. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +14 -3
  840. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +13 -6
  841. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +16 -7
  842. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +29 -18
  843. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +144 -14
  844. package/dist/knowledge/skills/human-decision-notices/SKILL.md +150 -0
  845. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-card-wording-api.md +292 -0
  846. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-notice-handler-api.md +340 -0
  847. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +17 -1
  848. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +19 -5
  849. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +14 -3
  850. package/dist/knowledge/skills/inbound-channels/SKILL.md +66 -8
  851. package/dist/knowledge/skills/inbound-channels/references/email-channel.md +34 -1
  852. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +78 -6
  853. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +8 -8
  854. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +434 -6
  855. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-pipelines-api.md +73 -0
  856. package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +1 -1
  857. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +24 -13
  858. package/dist/knowledge/skills/infra-environment-config/SKILL.md +113 -3
  859. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +9 -1
  860. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +2 -0
  861. package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +294 -0
  862. package/dist/knowledge/skills/layout-2d-adoption/SKILL.md +158 -0
  863. package/dist/knowledge/skills/layout-2d-adoption/references/choosing-a-layout.md +43 -0
  864. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +167 -0
  865. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-registration-api.md +101 -0
  866. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-settings-api.md +59 -0
  867. package/dist/knowledge/skills/layout-2d-adoption/references/framework-shell-motion-api.md +415 -0
  868. package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +1 -0
  869. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +65 -32
  870. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +14 -36
  871. package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +7 -3
  872. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +6 -1
  873. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +4 -2
  874. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +10 -2
  875. package/dist/knowledge/skills/market-alternatives/SKILL.md +10 -2
  876. package/dist/knowledge/skills/market-authoring-overview/SKILL.md +10 -2
  877. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +14 -1
  878. package/dist/knowledge/skills/market-category/SKILL.md +21 -7
  879. package/dist/knowledge/skills/market-channels/SKILL.md +6 -1
  880. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +20 -3
  881. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +10 -1
  882. package/dist/knowledge/skills/market-generation-cli/SKILL.md +23 -12
  883. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +13 -7
  884. package/dist/knowledge/skills/market-icp/SKILL.md +10 -2
  885. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +6 -1
  886. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +6 -1
  887. package/dist/knowledge/skills/market-persona/SKILL.md +14 -3
  888. package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +6 -1
  889. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +10 -2
  890. package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +6 -1
  891. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +14 -3
  892. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +6 -1
  893. package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +1 -1
  894. package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +2 -2
  895. package/dist/knowledge/skills/model-cost-attribution/SKILL.md +40 -10
  896. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +57 -2
  897. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +57 -21
  898. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +7 -3
  899. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +176 -4
  900. package/dist/knowledge/skills/module-companion-exports/SKILL.md +7 -1
  901. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +9 -0
  902. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +81 -1
  903. package/dist/knowledge/skills/module-relationships/SKILL.md +81 -31
  904. package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +8 -4
  905. package/dist/knowledge/skills/organization-relationships/SKILL.md +668 -0
  906. package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +1233 -0
  907. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-capability-grants-api.md +243 -0
  908. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +284 -0
  909. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +521 -0
  910. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +162 -0
  911. package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +145 -0
  912. package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +4 -2
  913. package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +5 -3
  914. package/dist/knowledge/skills/professional-qualifications/SKILL.md +173 -0
  915. package/dist/knowledge/skills/professional-qualifications/references/choosing-who-may-decide.md +53 -0
  916. package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +67 -0
  917. package/dist/knowledge/skills/professional-qualifications/references/framework-operation-required-qualifications-api.md +39 -0
  918. package/dist/knowledge/skills/professional-qualifications/references/framework-professional-qualifications-api.md +223 -0
  919. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +15 -4
  920. package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +3 -3
  921. package/dist/knowledge/skills/provider-backend-package/SKILL.md +138 -4
  922. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +32 -28
  923. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-augmentation-api.md +16 -0
  924. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +6 -0
  925. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +634 -0
  926. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +70 -0
  927. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +61 -2
  928. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-subject-erasure-effect-api.md +222 -0
  929. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +15 -6
  930. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +9 -2
  931. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +47 -5
  932. package/dist/knowledge/skills/provider-frontend-module/references/framework-on-demand-capabilities-api.md +306 -0
  933. package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +11 -3
  934. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +37 -14
  935. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +56 -18
  936. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +1 -1
  937. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +143 -25
  938. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +6 -0
  939. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +9 -6
  940. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +256 -1
  941. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +81 -37
  942. package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +27 -13
  943. package/dist/knowledge/skills/resource-add-field/SKILL.md +10 -2
  944. package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +32 -12
  945. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +167 -61
  946. package/dist/knowledge/skills/resource-add-resource/SKILL.md +63 -6
  947. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +84 -2
  948. package/dist/knowledge/skills/resource-chat-commands/SKILL.md +137 -0
  949. package/dist/knowledge/skills/resource-chat-commands/references/framework-resource-chat-command-contract.md +72 -0
  950. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +131 -7
  951. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +4 -4
  952. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +17 -8
  953. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +25 -4
  954. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +323 -0
  955. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +23 -2
  956. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +159 -0
  957. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +162 -2
  958. package/dist/knowledge/skills/resource-config-wiring/references/framework-request-field-offers-api.md +168 -0
  959. package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +20 -0
  960. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +135 -0
  961. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +3 -2
  962. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +221 -23
  963. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +108 -2
  964. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +242 -107
  965. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +202 -17
  966. package/dist/knowledge/skills/resource-config-wiring/references/framework-webhook-events-api.md +116 -0
  967. package/dist/knowledge/skills/resource-custom-view/SKILL.md +10 -2
  968. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +123 -56
  969. package/dist/knowledge/skills/resource-external-data/SKILL.md +280 -64
  970. package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +335 -0
  971. package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +18 -6
  972. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +73 -14
  973. package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +6 -0
  974. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +81 -18
  975. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +238 -49
  976. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +111 -11
  977. package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +145 -0
  978. package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +30 -4
  979. package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +21 -9
  980. package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +61 -14
  981. package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +18 -2
  982. package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +3 -1
  983. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +39 -13
  984. package/dist/knowledge/skills/resource-external-data/references/remote-references.md +17 -7
  985. package/dist/knowledge/skills/resource-external-data/references/requested-keys.md +104 -0
  986. package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +1 -1
  987. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +17 -4
  988. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +2 -2
  989. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +1 -1
  990. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +6 -0
  991. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +31 -1
  992. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +8 -2
  993. package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +68 -5
  994. package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +25 -0
  995. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +39 -9
  996. package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +23 -7
  997. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +571 -0
  998. package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +358 -0
  999. package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +2 -0
  1000. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +87 -6
  1001. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +19 -22
  1002. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +127 -12
  1003. package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +17 -4
  1004. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +50 -1
  1005. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +44 -5
  1006. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +119 -64
  1007. package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +2 -1
  1008. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +216 -18
  1009. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +6 -0
  1010. package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +153 -0
  1011. package/dist/knowledge/skills/resource-status-lifecycle/references/commercial-documents.md +46 -0
  1012. package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +198 -0
  1013. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +185 -80
  1014. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +159 -0
  1015. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +120 -1
  1016. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +41 -7
  1017. package/dist/knowledge/skills/resource-ui-behavior/references/framework-field-tiles-api.md +114 -0
  1018. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +257 -65
  1019. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +25 -9
  1020. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +15 -3
  1021. package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +151 -1
  1022. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +144 -57
  1023. package/dist/knowledge/skills/resource-ui-behavior/references/record-page-anatomy.md +131 -0
  1024. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +57 -31
  1025. package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +56 -0
  1026. package/dist/knowledge/skills/seeding-authoring/SKILL.md +155 -40
  1027. package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +67 -0
  1028. package/dist/knowledge/skills/seeding-authoring/references/data-seeding-mode-picker.md +16 -1
  1029. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +148 -4
  1030. package/dist/knowledge/skills/seeding-authoring/references/seed-row-overlay.md +22 -0
  1031. package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +15 -8
  1032. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +3 -0
  1033. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +42 -11
  1034. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +183 -31
  1035. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +64 -2
  1036. package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +5 -4
  1037. package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +5 -4
  1038. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +6 -1
  1039. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +9 -0
  1040. package/dist/knowledge/skills/spec-component-update/SKILL.md +10 -2
  1041. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +17 -9
  1042. package/dist/knowledge/skills/spec-family-update/SKILL.md +71 -66
  1043. package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +1 -1
  1044. package/dist/knowledge/skills/spec-resource-update/SKILL.md +30 -10
  1045. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +71 -14
  1046. package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +28 -0
  1047. package/dist/knowledge/skills/spec-update-after-change/SKILL.md +22 -5
  1048. package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +19 -5
  1049. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +20 -6
  1050. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +20 -3
  1051. package/dist/knowledge/skills/views-add-custom-view/references/framework-focus-indicator-api.md +145 -0
  1052. package/dist/knowledge/skills/views-app-level/SKILL.md +13 -3
  1053. package/dist/knowledge/skills/views-app-level/references/application-home.md +56 -0
  1054. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +226 -37
  1055. package/dist/knowledge/skills/views-chart-authoring/references/framework-chart-view-contracts-api.md +13 -0
  1056. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +33 -9
  1057. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +12 -3
  1058. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +17 -3
  1059. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +93 -27
  1060. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +264 -78
  1061. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +1068 -192
  1062. package/dist/knowledge/skills/website-building-blocks/SKILL.md +337 -0
  1063. package/dist/knowledge/skills/website-building-blocks/references/framework-website-blocks-api.md +3050 -0
  1064. package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +627 -0
  1065. package/dist/knowledge/skills/website-building-blocks/references/framework-website-product-kit-api.md +3309 -0
  1066. package/dist/knowledge/skills/website-building-blocks/references/website-visual-quality-rubric.md +75 -0
  1067. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +46 -19
  1068. package/dist/knowledge/skills/website-bundle-discipline/references/example-website-button-override.md +8 -12
  1069. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +18 -5
  1070. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +97 -29
  1071. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +77 -66
  1072. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +71 -24
  1073. package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +5 -1
  1074. package/dist/knowledge/skills/website-label-pack/SKILL.md +24 -17
  1075. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +116 -76
  1076. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +43 -14
  1077. package/dist/knowledge/skills/website-motion-design/SKILL.md +277 -0
  1078. package/dist/knowledge/skills/website-motion-design/references/framework-motion-api.md +1562 -0
  1079. package/dist/knowledge/skills/website-motion-design/references/industry-practice.md +28 -0
  1080. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +266 -371
  1081. package/dist/knowledge/skills/website-navigation-authoring/references/framework-menu-api.md +712 -0
  1082. package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +120 -0
  1083. package/dist/knowledge/skills/website-navigation-authoring/references/menu-keys-and-styling.md +151 -0
  1084. package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +131 -329
  1085. package/dist/knowledge/skills/website-page-authoring/SKILL.md +170 -66
  1086. package/dist/knowledge/skills/website-page-authoring/references/framework-page-kinds-api.md +982 -0
  1087. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +27 -3
  1088. package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +19 -0
  1089. package/dist/knowledge/skills/website-page-authoring/references/page-kinds.md +118 -0
  1090. package/dist/knowledge/skills/website-page-variants/SKILL.md +70 -69
  1091. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +54 -29
  1092. package/dist/knowledge/skills/website-section-comparison/SKILL.md +1171 -0
  1093. package/dist/knowledge/skills/website-section-comparison/references/define-website-section-api.md +679 -0
  1094. package/dist/knowledge/skills/website-section-comparison/references/framework-website-tables-api.md +487 -0
  1095. package/dist/knowledge/skills/website-section-contact/SKILL.md +408 -185
  1096. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +197 -119
  1097. package/dist/knowledge/skills/website-section-cta/SKILL.md +398 -234
  1098. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +197 -119
  1099. package/dist/knowledge/skills/website-section-faq/SKILL.md +564 -300
  1100. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +197 -119
  1101. package/dist/knowledge/skills/website-section-faq/references/framework-website-faq-api.md +489 -0
  1102. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +650 -272
  1103. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +197 -119
  1104. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +577 -261
  1105. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +197 -119
  1106. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +532 -233
  1107. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +197 -119
  1108. package/dist/knowledge/skills/website-section-hero/SKILL.md +606 -330
  1109. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +198 -120
  1110. package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1150 -0
  1111. package/dist/knowledge/skills/website-section-how-it-works/references/define-website-section-api.md +679 -0
  1112. package/dist/knowledge/skills/website-section-how-it-works/references/framework-website-steps-api.md +337 -0
  1113. package/dist/knowledge/skills/website-section-integrations/SKILL.md +974 -0
  1114. package/dist/knowledge/skills/website-section-integrations/references/define-website-section-api.md +679 -0
  1115. package/dist/knowledge/skills/website-section-integrations/references/framework-website-marquee-api.md +825 -0
  1116. package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +928 -0
  1117. package/dist/knowledge/skills/website-section-latest-posts/references/define-website-section-api.md +679 -0
  1118. package/dist/knowledge/skills/website-section-latest-posts/references/framework-website-latest-posts-api.md +465 -0
  1119. package/dist/knowledge/skills/website-section-pricing/SKILL.md +552 -376
  1120. package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +77 -0
  1121. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +197 -119
  1122. package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +2 -1
  1123. package/dist/knowledge/skills/website-section-pricing/references/framework-website-pricing-api.md +670 -0
  1124. package/dist/knowledge/skills/website-section-problem/SKILL.md +1150 -0
  1125. package/dist/knowledge/skills/website-section-problem/references/define-website-section-api.md +679 -0
  1126. package/dist/knowledge/skills/website-section-problem/references/framework-website-card-grid-api.md +664 -0
  1127. package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1322 -0
  1128. package/dist/knowledge/skills/website-section-product-showcase/references/define-website-section-api.md +679 -0
  1129. package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-card-grid-api.md +533 -0
  1130. package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-product-tour-api.md +917 -0
  1131. package/dist/knowledge/skills/website-section-roadmap/SKILL.md +1133 -0
  1132. package/dist/knowledge/skills/website-section-roadmap/references/define-website-section-api.md +679 -0
  1133. package/dist/knowledge/skills/website-section-roadmap/references/framework-website-roadmap-api.md +475 -0
  1134. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +743 -309
  1135. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +197 -119
  1136. package/dist/knowledge/skills/website-section-social-proof/references/framework-website-quote-cards-api.md +623 -0
  1137. package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +1057 -0
  1138. package/dist/knowledge/skills/website-section-solution-paths/references/define-website-section-api.md +679 -0
  1139. package/dist/knowledge/skills/website-section-solution-paths/references/framework-website-solution-paths-api.md +477 -0
  1140. package/dist/knowledge/skills/website-section-stats/SKILL.md +1086 -0
  1141. package/dist/knowledge/skills/website-section-stats/references/define-website-section-api.md +679 -0
  1142. package/dist/knowledge/skills/website-section-stats/references/framework-website-stats-api.md +517 -0
  1143. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +198 -70
  1144. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +575 -57
  1145. package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +17 -2
  1146. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +8 -95
  1147. package/dist/knowledge/skills/website-theme-authoring/SKILL.md +226 -0
  1148. package/dist/knowledge/skills/website-theme-authoring/references/framework-website-theme-api.md +893 -0
  1149. package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +4 -2
  1150. package/dist/knowledge/topic-index.json +17305 -8263
  1151. package/dist/tsconfig.build.tsbuildinfo +1 -1
  1152. package/package.json +4 -4
  1153. package/dist/knowledge/references/example.organizations.serves-as-provider.md +0 -12
  1154. package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +0 -121
  1155. package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +0 -49
  1156. package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +0 -567
  1157. package/dist/knowledge/references/saas.website.root-config.navigation.md +0 -37
  1158. package/dist/knowledge/skills/service-provider-relationships/SKILL.md +0 -455
  1159. package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +0 -270
  1160. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +0 -129
  1161. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +0 -161
  1162. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +0 -224
  1163. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +0 -576
@@ -1 +1 @@
1
- {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/journey-phase-transition","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/capability-completeness","application-creation:evidence-requirement/compliance-presence","application-creation:evidence-requirement/positioning-icp-coherence","application-creation:evidence-requirement/requirement-coverage","application-creation:evidence-requirement/success-criterion-coverage"],"requirementRef":"application-creation:authority-requirement/top-down-to-bottom-up-transition","requirementVersion":1,"riskClassRef":"application-creation:risk/bootstrap-non-regulated-phase-transition","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/top-down-phase-gate","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/top-down-to-bottom-up-transition","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/top-down-phase-gate","policyVersion":1},"decisionPointRef":"application-creation:decision-point/top-down-phase-gate","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/top-down-phase-gate","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/top-down-phase-gate","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-standing","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/required-family-validity"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-transition","triggerRefs":["application-creation:trigger/top-down-definition-set-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-top-down-coherence-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/capability-completeness","application-creation:evidence-requirement/compliance-presence","application-creation:evidence-requirement/positioning-icp-coherence","application-creation:evidence-requirement/requirement-coverage","application-creation:evidence-requirement/success-criterion-coverage"],"hardFloorRef":"application-creation:hard-floor/required-family-validity"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/top-down-phase-gate","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/top-down-phase-gate","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-top-down-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.name","brand-name-screening.candidate"],"criterionRef":"application-creation:criterion/brand-name-screening-standing","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-standing","requirementVersion":1}],"instruction":"Determine where the product's NAME stands, reading the coherence report's brand-name findings first — they are computed, not judged. On a line that carries a brand, a missing brand-name screening (brand-name-screening-missing) or a brand name no screening covers (brand-name-not-screened), or a conflict nobody chose to keep (brand-name-conflict-unacknowledged), is a gap in the definition: the brand identity's name question cannot be answered, or the name was never checked. A name chosen with the screening incomplete or kept despite a conflict is a deliberate, recorded decision that must be visible — in the risk register, as an entry derived from the brand-name-trademark-standing signal — not a failure. Fewer than three offerable proposals, or a creator-listed name the screening does not carry, is a concern. A line with no brand (no brand-name finding is reported for it) has nothing to assess.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The brand name was chosen with the screening incomplete or kept despite a conflict and the risk register carries it, or the screening offers fewer than three proposals or misses a name the creator listed.","GAP":"On a line with a brand, no screening is on record or the brand name was never screened; or a name kept despite a conflict is recorded nowhere, the risk register included.","INDETERMINATE":"The coherence report is not in evidence, so the brand name's standing cannot be read.","PASS":"The line carries no brand, or the brand name is a screened candidate whose screening is complete and clear."}},{"assessesAspects":["market.benefit","feature-drafts.draft"],"criterionRef":"application-creation:criterion/capability-completeness","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1}],"instruction":"Determine whether every current-horizon market benefit is connected to at least one resolvable delivering feature. Treat an unwired benefit as a material gap; do not infer a connection from thematic similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All benefits are wired, but one or more connections are weak, indirect, or insufficiently explained.","GAP":"At least one current-horizon benefit has no resolvable delivering feature.","INDETERMINATE":"The accepted evidence cannot establish the benefit-to-feature wiring completely.","PASS":"Every current-horizon benefit has at least one resolvable delivering feature."}},{"criterionRef":"application-creation:criterion/compliance-presence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1}],"instruction":"Determine whether a product handling regulated or sensitive data declares at least one applicable compliance constraint. Do not invent regulation applicability; report indeterminate when the accepted evidence does not establish the data or sector posture.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A compliance constraint exists, but its applicability or coverage is weakly established.","GAP":"A regulated-data trigger is established and no applicable compliance constraint is declared.","INDETERMINATE":"The evidence cannot establish the regulated-data trigger or the applicable constraint posture.","PASS":"The evidence establishes either no regulated-data trigger or an applicable declared compliance constraint."}},{"assessesAspects":["market.icp","market.positioning"],"criterionRef":"application-creation:criterion/positioning-icp-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1}],"instruction":"Determine whether positioning pillars address the declared core ICPs without centring an anti-target segment. Preserve the authored ICP classifications and do not silently reclassify a segment.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Positioning is broadly coherent but under-serves a core ICP or approaches an anti-target boundary.","GAP":"Positioning ignores the core ICPs or explicitly centres an anti-target segment.","INDETERMINATE":"The accepted evidence cannot connect positioning pillars to the classified ICP set.","PASS":"Positioning addresses the core ICPs and does not centre an anti-target segment."}},{"assessesAspects":["requirements.functional","roadmap.phase"],"criterionRef":"application-creation:criterion/requirement-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is delivered by a roadmap phase or explicitly deferred in accepted roadmap intent. Do not treat absence as deliberate deferral.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but one or more deferrals are weakly justified or difficult to trace.","GAP":"At least one functional requirement is neither delivered nor explicitly deferred.","INDETERMINATE":"The accepted evidence cannot establish complete requirement-to-roadmap accounting.","PASS":"Every current-horizon functional requirement is delivered or explicitly deferred."}},{"assessesAspects":["vision.success-criterion","roadmap.phase"],"criterionRef":"application-creation:criterion/success-criterion-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon vision success criterion is delivered by at least one roadmap phase. Keep success criteria distinct from implementation tasks or generic aspirations.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All criteria are covered, but one or more delivery links are weak or overly indirect.","GAP":"At least one current-horizon success criterion is not delivered by any roadmap phase.","INDETERMINATE":"The accepted evidence cannot establish complete success-criterion-to-roadmap coverage.","PASS":"Every current-horizon success criterion is delivered by at least one roadmap phase."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/top-down-phase-gate","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.phase-gate"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/top-down-phase-gate","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/brand-name-and-its-screening","criterionRef":"application-creation:criterion/brand-name-screening-standing","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":1,"requirementRef":"application-creation:evidence-requirement/brand-name-screening-standing","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/brand-and-name-screening"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-benefits","criterionRef":"application-creation:criterion/capability-completeness","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-capability-wiring"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/regulated-data-and-compliance-constraints","criterionRef":"application-creation:criterion/compliance-presence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-compliance"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/core-and-anti-target-icps","criterionRef":"application-creation:criterion/positioning-icp-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-positioning"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-functional-requirements","criterionRef":"application-creation:criterion/requirement-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/requirements-roadmap"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-success-criteria","criterionRef":"application-creation:criterion/success-criterion-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-roadmap"}],"schemaVersion":1}
1
+ {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/journey-phase-transition","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/capability-completeness","application-creation:evidence-requirement/compliance-presence","application-creation:evidence-requirement/positioning-icp-coherence","application-creation:evidence-requirement/requirement-coverage","application-creation:evidence-requirement/success-criterion-coverage"],"requirementRef":"application-creation:authority-requirement/top-down-to-bottom-up-transition","requirementVersion":1,"riskClassRef":"application-creation:risk/bootstrap-non-regulated-phase-transition","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/top-down-phase-gate","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/top-down-to-bottom-up-transition","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/top-down-phase-gate","policyVersion":1},"decisionPointRef":"application-creation:decision-point/top-down-phase-gate","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/top-down-phase-gate","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/top-down-phase-gate","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-standing","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/definition-completeness","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/required-family-validity"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-transition","triggerRefs":["application-creation:trigger/top-down-definition-set-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-top-down-coherence-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/capability-completeness","application-creation:evidence-requirement/compliance-presence","application-creation:evidence-requirement/positioning-icp-coherence","application-creation:evidence-requirement/requirement-coverage","application-creation:evidence-requirement/success-criterion-coverage"],"hardFloorRef":"application-creation:hard-floor/required-family-validity"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/top-down-phase-gate","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/top-down-phase-gate","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-top-down-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.name","brand-name-screening.candidate"],"criterionRef":"application-creation:criterion/brand-name-screening-standing","criterionVersion":3,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-standing","requirementVersion":1}],"instruction":"Determine where the product's NAME stands, reading the coherence report's brand-name findings first — they are computed, not judged. On a line that carries a brand, a missing brand-name screening (brand-name-screening-missing) or a brand name no screening covers (brand-name-not-screened), or a conflict nobody chose to keep (brand-name-conflict-unacknowledged), is a gap in the definition: the brand identity's name question cannot be answered, or the name was never checked. A name chosen with the screening incomplete, with no register read at all (brand-name-no-register-read), or kept despite a conflict is a deliberate, recorded decision that must be visible — in the risk register, as an entry derived from the brand-name-trademark-standing signal, and in the launch list as a brand name not cleared — not a failure. Fewer than three offerable proposals, a creator-listed name the screening does not carry, a screening that read no register for any name (brand-name-screening-read-nothing), or a place the application declares it operates in that the screening does not list (brand-name-operating-jurisdiction-not-screened), is a concern. A line with no brand (no brand-name finding and no definition-brand-brief-missing finding is reported for it) has nothing to assess; a line that carries a brand whose brief has not landed (definition-brand-brief-missing) is assessed by the definition-completeness criterion, never passed here as a line with no brand.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The brand name was chosen with the screening incomplete or kept despite a conflict and the risk register carries it, or the screening offers fewer than three proposals or misses a name the creator listed.","GAP":"On a line with a brand, no screening is on record or the brand name was never screened; or a name kept despite a conflict is recorded nowhere, the risk register included.","INDETERMINATE":"The coherence report is not in evidence, so the brand name's standing cannot be read.","PASS":"The line carries no brand, or the brand name is a screened candidate whose screening is complete and clear."}},{"assessesAspects":["market.benefit","feature-drafts.draft"],"criterionRef":"application-creation:criterion/capability-completeness","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1}],"instruction":"Determine whether every current-horizon market benefit is connected to at least one resolvable delivering feature. Treat an unwired benefit as a material gap; do not infer a connection from thematic similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All benefits are wired, but one or more connections are weak, indirect, or insufficiently explained.","GAP":"At least one current-horizon benefit has no resolvable delivering feature.","INDETERMINATE":"The accepted evidence cannot establish the benefit-to-feature wiring completely.","PASS":"Every current-horizon benefit has at least one resolvable delivering feature."}},{"criterionRef":"application-creation:criterion/compliance-presence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1}],"instruction":"Determine whether a product handling regulated or sensitive data declares at least one applicable compliance constraint. Do not invent regulation applicability; report indeterminate when the accepted evidence does not establish the data or sector posture.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A compliance constraint exists, but its applicability or coverage is weakly established.","GAP":"A regulated-data trigger is established and no applicable compliance constraint is declared.","INDETERMINATE":"The evidence cannot establish the regulated-data trigger or the applicable constraint posture.","PASS":"The evidence establishes either no regulated-data trigger or an applicable declared compliance constraint."}},{"criterionRef":"application-creation:criterion/definition-completeness","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/definition-completeness","requirementVersion":1}],"instruction":"Determine whether the definition holds every family the application's declared line carries, reading the coherence report's definition findings — they are computed, not judged. A business model (definition-business-model-missing) or a brand brief (definition-brand-brief-missing) the line carries that has not landed is a gap: the definition is not finished, whatever the other families say, and the finding names the step to run (or the interview to answer). A family the line declares not applicable is never reported and is not a gap. Do not infer a missing family from anything other than these findings.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Not used: a family the line carries is either on record or missing.","GAP":"The coherence report names a business model or a brand brief the declared line carries that has not landed.","INDETERMINATE":"The coherence report is not in evidence, so which families have landed cannot be read.","PASS":"The coherence report carries no definition-*-missing finding: every family the declared line carries has landed or is declared not applicable."}},{"assessesAspects":["market.icp","market.positioning"],"criterionRef":"application-creation:criterion/positioning-icp-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1}],"instruction":"Determine whether positioning pillars address the declared core ICPs without centring an anti-target segment. Preserve the authored ICP classifications and do not silently reclassify a segment.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Positioning is broadly coherent but under-serves a core ICP or approaches an anti-target boundary.","GAP":"Positioning ignores the core ICPs or explicitly centres an anti-target segment.","INDETERMINATE":"The accepted evidence cannot connect positioning pillars to the classified ICP set.","PASS":"Positioning addresses the core ICPs and does not centre an anti-target segment."}},{"assessesAspects":["requirements.functional","roadmap.phase"],"criterionRef":"application-creation:criterion/requirement-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is delivered by a roadmap phase or explicitly deferred in accepted roadmap intent. Do not treat absence as deliberate deferral.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but one or more deferrals are weakly justified or difficult to trace.","GAP":"At least one functional requirement is neither delivered nor explicitly deferred.","INDETERMINATE":"The accepted evidence cannot establish complete requirement-to-roadmap accounting.","PASS":"Every current-horizon functional requirement is delivered or explicitly deferred."}},{"assessesAspects":["vision.success-criterion","roadmap.phase"],"criterionRef":"application-creation:criterion/success-criterion-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon vision success criterion is delivered by at least one roadmap phase. Keep success criteria distinct from implementation tasks or generic aspirations.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All criteria are covered, but one or more delivery links are weak or overly indirect.","GAP":"At least one current-horizon success criterion is not delivered by any roadmap phase.","INDETERMINATE":"The accepted evidence cannot establish complete success-criterion-to-roadmap coverage.","PASS":"Every current-horizon success criterion is delivered by at least one roadmap phase."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/top-down-phase-gate","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.phase-gate"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/top-down-phase-gate","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/brand-name-and-its-screening","criterionRef":"application-creation:criterion/brand-name-screening-standing","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":1,"requirementRef":"application-creation:evidence-requirement/brand-name-screening-standing","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/brand-and-name-screening"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-benefits","criterionRef":"application-creation:criterion/capability-completeness","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-capability-wiring"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/regulated-data-and-compliance-constraints","criterionRef":"application-creation:criterion/compliance-presence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-compliance"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/coherence-report-definition-findings","criterionRef":"application-creation:criterion/definition-completeness","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/definition-completeness","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/line-carried-families"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/core-and-anti-target-icps","criterionRef":"application-creation:criterion/positioning-icp-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-positioning"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-functional-requirements","criterionRef":"application-creation:criterion/requirement-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/requirements-roadmap"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-success-criteria","criterionRef":"application-creation:criterion/success-criterion-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-roadmap"}],"schemaVersion":1}
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "top_down.phase-gate",
3
- "version": "0.2.1",
3
+ "version": "0.3.0",
4
4
  "phase": "top_down",
5
5
  "intent": "Assess whether the validated top-down definition set is cross-artifact coherent enough for the current horizon. Deterministic family validation remains a non-bypassable eligibility floor; this playbook contributes an advisory semantic evaluation and never mutates application truth.",
6
6
  "preconditions": [
@@ -1 +1 @@
1
- {"aggregationPolicyRef":"application-creation:aggregation/worst-requirements-definition-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/requirements-definition-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirements-definition-coherence","requirementVersion":1}],"instruction":"Assess whether each requirement is traceable to accepted vision or market evidence, states a distinct current-horizon obligation, and carries observable acceptance language where applicable. Do not invent missing requirements or silently turn implementation ideas into product obligations.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The set is usable, but one or more obligations are weakly traced or ambiguously testable.","GAP":"A material current-horizon obligation is missing, contradictory, or not testable enough to guide downstream scope.","INDETERMINATE":"Accepted vision/market evidence is insufficient to assess the requirements set.","PASS":"The requirements are distinct, traceable and sufficiently observable for the current horizon."}},{"criterionRef":"application-creation:criterion/requirements-horizon-readiness","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirements-horizon-readiness","requirementVersion":2}],"instruction":"Judge whether the requirements under judgment — the working-subject source when one is named, otherwise the accepted current-horizon requirements — give the current horizon a non-vacuous, implementable basis: at least one validated functional requirement with a testable acceptance criterion, or an exact settled exceptional disposition. The sealed hard-floor assessment for this criterion is the deterministic minimum-content finding on that same subject; treat it as the floor, not as the whole judgment. Never infer readiness from prose, model confidence or snapshot parse success, and never judge an empty collection ready.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The horizon has a basis, but it is thin or its acceptance language is weak enough that downstream scope would be guesswork.","GAP":"The requirements under judgment have no functional requirement and no exact settled exceptional disposition, or the sealed hard floor failed.","INDETERMINATE":"The current-horizon requirements evidence is absent, malformed, or does not bind the subject under judgment.","PASS":"The requirements under judgment carry at least one validated, testable current-horizon functional requirement (or an exact settled exceptional disposition) and the sealed hard floor is satisfied."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/requirements-definition","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.requirements-definition"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-requirements-definition-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/requirements-definition-coherence","criterionVersion":3,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirements-definition-coherence","requirementVersion":2}],"instruction":"Assess whether each requirement is traceable to accepted vision or market evidence, or to a fact the creator stated in another interview; states a distinct current-horizon obligation; and carries observable acceptance language where applicable. Then check the creator's stated facts, when they are in your evidence: every data class, named regime, jurisdiction (with its languages), workflow stage, user group and scope boundary bearing on what the product must do is carried by a requirement or listed in excludedStatedFacts with a reason. A stated fact neither carried nor excluded is a GAP. Then check the market's pains: every pain a targeted ICP (CORE or EXPANSION) or one of its personas weighs at severity 7 or more is named in some requirement's painRefs or listed in excludedMarketPains with a reason; one that is neither is a GAP. The coherence report's high-severity-pains-unanswered finding lists them, computed over the accepted requirements. Then check the targeted personas' responsibilities: one the product exists to help with that no requirement carries is a GAP; one outside any product's scope needs nothing. A functional acceptance criterion that is a compliance guard (does not claim, is not presented as supported until) instead of a capability is a CONCERN: it belongs in a compliance non-functional requirement. Do not invent missing requirements or silently turn implementation ideas into product obligations.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The set is usable, but one or more obligations are weakly traced or ambiguously testable.","GAP":"A material current-horizon obligation is missing, contradictory, or not testable enough to guide downstream scope, or a fact the creator stated (or a high-severity market pain) is neither carried by a requirement nor explicitly excluded.","INDETERMINATE":"Accepted vision/market evidence is insufficient to assess the requirements set.","PASS":"The requirements are distinct, traceable and sufficiently observable for the current horizon."}},{"criterionRef":"application-creation:criterion/requirements-horizon-readiness","criterionVersion":3,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirements-horizon-readiness","requirementVersion":2}],"instruction":"Judge whether the requirements under judgment — the working-subject source when one is named, otherwise the accepted current-horizon requirements — give the current horizon a non-vacuous, implementable basis: at least one validated functional requirement with a testable acceptance criterion, or an exact settled exceptional disposition. The sealed hard-floor assessment for this criterion is the deterministic minimum-content finding on that same subject; treat it as the floor, not as the whole judgment. A requirement describing a workflow (quotes, jobs, invoices, orders, tickets) whose criteria only list what can be created, read and edited, naming no state, transition, document, total or number the workflow has, is a CONCERN: the horizon then reads as a database rather than a product. Never infer readiness from prose, model confidence or snapshot parse success, and never judge an empty collection ready.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The horizon has a basis, but it is thin or its acceptance language is weak enough that downstream scope would be guesswork.","GAP":"The requirements under judgment have no functional requirement and no exact settled exceptional disposition, or the sealed hard floor failed.","INDETERMINATE":"The current-horizon requirements evidence is absent, malformed, or does not bind the subject under judgment.","PASS":"The requirements under judgment carry at least one validated, testable current-horizon functional requirement (or an exact settled exceptional disposition) and the sealed hard floor is satisfied."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/requirements-definition","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.requirements-definition"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
@@ -1 +1 @@
1
- {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-requirements-snapshot","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/requirements-horizon-readiness","application-creation:evidence-requirement/requirements-definition-coherence"],"requirementRef":"application-creation:authority-requirement/requirements-definition-result","requirementVersion":1,"riskClassRef":"application-creation:risk/requirements-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/requirements-definition","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/requirements-definition-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/requirements-definition","policyVersion":1},"decisionPointRef":"application-creation:decision-point/requirements-definition","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/requirements-definition","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/requirements-definition","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirements-definition-coherence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/requirements-horizon-readiness","requirementVersion":2}],"hardFloorRefs":["application-creation:hard-floor/requirements-horizon-readiness"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-definition","triggerRefs":["application-creation:trigger/requirements-snapshot-produced"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-requirements-definition-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/requirements-horizon-readiness"],"hardFloorRef":"application-creation:hard-floor/requirements-horizon-readiness"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/requirements-definition","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/requirements-definition","definitionVersion":2,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-requirements-definition-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/requirements-definition-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirements-definition-coherence","requirementVersion":1}],"instruction":"Assess whether each requirement is traceable to accepted vision or market evidence, states a distinct current-horizon obligation, and carries observable acceptance language where applicable. Do not invent missing requirements or silently turn implementation ideas into product obligations.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The set is usable, but one or more obligations are weakly traced or ambiguously testable.","GAP":"A material current-horizon obligation is missing, contradictory, or not testable enough to guide downstream scope.","INDETERMINATE":"Accepted vision/market evidence is insufficient to assess the requirements set.","PASS":"The requirements are distinct, traceable and sufficiently observable for the current horizon."}},{"criterionRef":"application-creation:criterion/requirements-horizon-readiness","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirements-horizon-readiness","requirementVersion":2}],"instruction":"Judge whether the requirements under judgment — the working-subject source when one is named, otherwise the accepted current-horizon requirements — give the current horizon a non-vacuous, implementable basis: at least one validated functional requirement with a testable acceptance criterion, or an exact settled exceptional disposition. The sealed hard-floor assessment for this criterion is the deterministic minimum-content finding on that same subject; treat it as the floor, not as the whole judgment. Never infer readiness from prose, model confidence or snapshot parse success, and never judge an empty collection ready.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The horizon has a basis, but it is thin or its acceptance language is weak enough that downstream scope would be guesswork.","GAP":"The requirements under judgment have no functional requirement and no exact settled exceptional disposition, or the sealed hard floor failed.","INDETERMINATE":"The current-horizon requirements evidence is absent, malformed, or does not bind the subject under judgment.","PASS":"The requirements under judgment carry at least one validated, testable current-horizon functional requirement (or an exact settled exceptional disposition) and the sealed hard floor is satisfied."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/requirements-definition","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.requirements-definition"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/requirements-definition","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-requirements","criterionRef":"application-creation:criterion/requirements-definition-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":1,"requirementRef":"application-creation:evidence-requirement/requirements-definition-coherence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/requirements-vision-market"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/current-horizon-requirements","criterionRef":"application-creation:criterion/requirements-horizon-readiness","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/requirements-horizon-readiness","requirementVersion":2,"schemaVersion":1,"subjectRef":"application-creation:definition-set/requirements-current-horizon"}],"schemaVersion":1}
1
+ {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-requirements-snapshot","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/requirements-horizon-readiness","application-creation:evidence-requirement/requirements-definition-coherence"],"requirementRef":"application-creation:authority-requirement/requirements-definition-result","requirementVersion":1,"riskClassRef":"application-creation:risk/requirements-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/requirements-definition","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/requirements-definition-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/requirements-definition","policyVersion":1},"decisionPointRef":"application-creation:decision-point/requirements-definition","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/requirements-definition","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/requirements-definition","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirements-definition-coherence","requirementVersion":2},{"requirementRef":"application-creation:evidence-requirement/requirements-horizon-readiness","requirementVersion":2}],"hardFloorRefs":["application-creation:hard-floor/requirements-horizon-readiness"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-definition","triggerRefs":["application-creation:trigger/requirements-snapshot-produced"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-requirements-definition-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/requirements-horizon-readiness"],"hardFloorRef":"application-creation:hard-floor/requirements-horizon-readiness"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/requirements-definition","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/requirements-definition","definitionVersion":2,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-requirements-definition-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/requirements-definition-coherence","criterionVersion":3,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirements-definition-coherence","requirementVersion":2}],"instruction":"Assess whether each requirement is traceable to accepted vision or market evidence, or to a fact the creator stated in another interview; states a distinct current-horizon obligation; and carries observable acceptance language where applicable. Then check the creator's stated facts, when they are in your evidence: every data class, named regime, jurisdiction (with its languages), workflow stage, user group and scope boundary bearing on what the product must do is carried by a requirement or listed in excludedStatedFacts with a reason. A stated fact neither carried nor excluded is a GAP. Then check the market's pains: every pain a targeted ICP (CORE or EXPANSION) or one of its personas weighs at severity 7 or more is named in some requirement's painRefs or listed in excludedMarketPains with a reason; one that is neither is a GAP. The coherence report's high-severity-pains-unanswered finding lists them, computed over the accepted requirements. Then check the targeted personas' responsibilities: one the product exists to help with that no requirement carries is a GAP; one outside any product's scope needs nothing. A functional acceptance criterion that is a compliance guard (does not claim, is not presented as supported until) instead of a capability is a CONCERN: it belongs in a compliance non-functional requirement. Do not invent missing requirements or silently turn implementation ideas into product obligations.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The set is usable, but one or more obligations are weakly traced or ambiguously testable.","GAP":"A material current-horizon obligation is missing, contradictory, or not testable enough to guide downstream scope, or a fact the creator stated (or a high-severity market pain) is neither carried by a requirement nor explicitly excluded.","INDETERMINATE":"Accepted vision/market evidence is insufficient to assess the requirements set.","PASS":"The requirements are distinct, traceable and sufficiently observable for the current horizon."}},{"criterionRef":"application-creation:criterion/requirements-horizon-readiness","criterionVersion":3,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirements-horizon-readiness","requirementVersion":2}],"instruction":"Judge whether the requirements under judgment — the working-subject source when one is named, otherwise the accepted current-horizon requirements — give the current horizon a non-vacuous, implementable basis: at least one validated functional requirement with a testable acceptance criterion, or an exact settled exceptional disposition. The sealed hard-floor assessment for this criterion is the deterministic minimum-content finding on that same subject; treat it as the floor, not as the whole judgment. A requirement describing a workflow (quotes, jobs, invoices, orders, tickets) whose criteria only list what can be created, read and edited, naming no state, transition, document, total or number the workflow has, is a CONCERN: the horizon then reads as a database rather than a product. Never infer readiness from prose, model confidence or snapshot parse success, and never judge an empty collection ready.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The horizon has a basis, but it is thin or its acceptance language is weak enough that downstream scope would be guesswork.","GAP":"The requirements under judgment have no functional requirement and no exact settled exceptional disposition, or the sealed hard floor failed.","INDETERMINATE":"The current-horizon requirements evidence is absent, malformed, or does not bind the subject under judgment.","PASS":"The requirements under judgment carry at least one validated, testable current-horizon functional requirement (or an exact settled exceptional disposition) and the sealed hard floor is satisfied."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/requirements-definition","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.requirements-definition"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/requirements-definition","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-requirements","criterionRef":"application-creation:criterion/requirements-definition-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":1,"requirementRef":"application-creation:evidence-requirement/requirements-definition-coherence","requirementVersion":2,"schemaVersion":1,"subjectRef":"application-creation:definition-set/requirements-vision-market"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/current-horizon-requirements","criterionRef":"application-creation:criterion/requirements-horizon-readiness","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/requirements-horizon-readiness","requirementVersion":2,"schemaVersion":1,"subjectRef":"application-creation:definition-set/requirements-current-horizon"}],"schemaVersion":1}
@@ -1,9 +1,9 @@
1
1
  # Requirements definition method
2
2
 
3
3
  Produce the current-horizon requirements family from the accepted
4
- `vision-brief` and `market-snapshot` heads. Treat those accepted projections as
5
- the only application truth: conversational context may clarify them, but it
6
- cannot silently replace or amend them.
4
+ `vision-brief` and `market-snapshot` heads, and from what the creator stated in
5
+ the other interviews. Treat those as the only application truth: conversational
6
+ context may clarify them, but it cannot silently replace or amend them.
7
7
 
8
8
  The provider response must parse as
9
9
  `RequirementsSnapshotGenerationSchema`. It supplies semantic slugs, statements,
@@ -25,13 +25,86 @@ override that protected consequence.
25
25
  For every functional requirement:
26
26
 
27
27
  - state one distinct product capability, not an implementation task;
28
- - connect it to accepted vision or market evidence (when the brief says the
29
- market does not apply to this application, the vision alone is the evidence:
30
- cite its problem, its users and its success criteria, and declare no market
31
- cross-references);
28
+ - connect it to accepted vision or market evidence, or to a fact the creator
29
+ stated (when the brief says the market does not apply to this application,
30
+ the vision and the stated facts are the evidence: cite the vision's problem,
31
+ users and success criteria, and declare no market cross-references);
32
32
  - keep current-horizon scope explicit; and
33
33
  - provide observable acceptance language where meaningful.
34
34
 
35
+ ## Acceptance criteria name states and transitions
36
+
37
+ A requirement for a workflow is a set of state changes, and its criteria say them: "a draft quote can be sent; a sent
38
+ quote can be accepted or declined; an accepted quote becomes a job carrying its customer, site and lines". Criteria that
39
+ only list what can be created, read and edited describe a database, not a product. An earlier run carried a whole
40
+ quote, job and invoice product in five such criteria, with no lifecycle, no documents, no totals and no numbering, and
41
+ every judge passed it. When the product numbers, totals, prints or sends documents, a criterion says so.
42
+
43
+ ## Every high-severity market pain is relieved or left out
44
+
45
+ The `market-snapshot` input weighs each pain on the ICPs and personas that feel it (`pains[].severity`, 1 to 10). Every
46
+ pain a targeted ICP (`CORE` or `EXPANSION`) or one of its personas feels at 7 or more is owed an answer. The computed
47
+ coherence report (the declared `coherence_report` context section of your brief) lists those not answered yet in its
48
+ `high-severity-pains-unanswered` finding, each with its severity and who feels it; answer that list. Each pain is either:
49
+
50
+ - **relieved** by a requirement, which names it in `painRefs` (a functional requirement for what the product does about
51
+ it, a non-functional one for a quality); or
52
+ - **left out** in `excludedMarketPains`, with the pain's ref and why no requirement relieves it (a later horizon, served
53
+ by another tool, outside the product).
54
+
55
+ An earlier run's market weighed missed follow-ups and fragmented customer communications heavily, and no requirement
56
+ mentioned follow-ups, reminders, documents or mobile use. Name the pain on every requirement that relieves it, so the
57
+ coverage can be checked rather than read into the statements.
58
+
59
+ ## The targeted personas' work is carried
60
+
61
+ Each persona of a targeted ICP lists its day-to-day `profile.responsibilities`. A responsibility the product exists to
62
+ help with (sending quotes, chasing follow-ups, scheduling jobs) is carried by a requirement, which names the persona's ICP
63
+ in `icpRefs`. A responsibility outside what any product does (reporting to the board, hiring) needs nothing. Read every
64
+ one: a responsibility at the centre of the product's job that no requirement carries is the same gap as an unanswered
65
+ pain, and the judge reports it.
66
+
67
+ ## Compliance guards are non-functional requirements
68
+
69
+ A sentence such as "the product does not claim e-invoicing compliance" or "is not presented as supported until …" is a
70
+ constraint on the product, not a capability. Put it in a `compliance` non-functional requirement, never in a functional
71
+ requirement's acceptance criteria. An earlier run filled 14 of its 39 functional criteria with such guards, and the
72
+ functional requirements then said almost nothing about what the product does.
73
+
74
+ ## Every stated fact becomes a requirement or an exclusion
75
+
76
+ The creator's answers to the other interviews arrive in
77
+ the declared `creator_stated_facts` context section of your brief. They are accepted truth beside the
78
+ vision and the market: statements about the product, not suggestions. On an
79
+ earlier run the creator named VAT identification numbers on quotes, job-site
80
+ addresses, Italy's SDI and Spain's VeriFactu e-invoicing, and four countries.
81
+ The requirements mentioned none of them, and the application shipped quotes
82
+ with no VAT, jobs with no site address, and one language for four countries.
83
+
84
+ Go through every answer that bears on what the product must do or be, and for each fact:
85
+
86
+ - **Carry it in a requirement.**
87
+ - A data class the product holds (a VAT number, a site address) belongs in the
88
+ statement or acceptance criteria of the functional requirement that captures
89
+ or shows it.
90
+ - A named regime (an e-invoicing mandate, a privacy law) becomes a
91
+ `compliance` non-functional requirement naming it.
92
+ - A jurisdiction implies its languages and formats: name them in a
93
+ `usability` or `compliance` non-functional requirement, and do not assume
94
+ English is enough.
95
+ - Each workflow stage and each user group (with the device they use) is served
96
+ by at least one functional requirement.
97
+ - **Or exclude it explicitly** in `excludedStatedFacts`, quoting the fact and
98
+ saying why no requirement carries it: out of this horizon, left to another
99
+ tool by the scope boundary, or contradicted by a later answer. Something the
100
+ creator put out of scope is excluded here, never quietly built.
101
+
102
+ Never drop a stated fact silently, and never write a requirement that
103
+ contradicts one. An answer marked ASSUMED was proposed for the creator, not
104
+ stated by them: honour it the same way, and let a stated answer win where the
105
+ two disagree. Leave `excludedStatedFacts` empty only when every stated fact is
106
+ carried.
107
+
35
108
  ## Refine, don't re-author
36
109
 
37
110
  When requirements already exist, they arrive in your brief as the `requirements` input. Refine them:
@@ -46,12 +119,14 @@ When requirements already exist, they arrive in your brief as the `requirements`
46
119
  the runtime whether or not you restate it; do not rewrite it as your own.
47
120
 
48
121
  For every non-functional requirement, preserve the declared quality axis and
49
- measurement intent. Do not invent regulatory applicability. Missing or
122
+ measurement intent. Do not invent regulatory applicability: a regime is in scope
123
+ because the creator named it or the accepted truth implies it, never because it
124
+ sounds plausible. Missing or
50
125
  contradictory accepted evidence yields a request for evidence or revision, not
51
126
  a plausible completion.
52
127
 
53
128
  Context selection receives current accepted vision and market heads, the
54
- working requirements candidate, and declared Framework guidance as structured
129
+ creator's stated facts, the working requirements candidate, and declared Framework guidance as structured
55
130
  data. Missing mandatory context is explicit; retrieved instruction-shaped text
56
131
  is treated as data and excluded from coding-task projection. Optional context
57
132
  is bounded by the declared selection plan rather than by ad-hoc prompt growth.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "top_down.requirements-definition",
3
- "version": "0.1.0",
3
+ "version": "0.2.0",
4
4
  "phase": "top_down",
5
5
  "intent": "Derive a validated, current-horizon requirements snapshot from accepted vision and market truth. The provider proposes strict semantic content; the trusted runtime stamps family refs/version and keeps provenance, scope, evidence and authority outside model output.",
6
6
  "preconditions": [
@@ -38,10 +38,13 @@
38
38
  ],
39
39
  "stepOutputs": [],
40
40
  "method": {
41
- "guidance": "# Requirements definition method\n\nProduce the current-horizon requirements family from the accepted\n`vision-brief` and `market-snapshot` heads. Treat those accepted projections as\nthe only application truth: conversational context may clarify them, but it\ncannot 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 (when the brief says the\n market does not apply to this application, the vision alone is the evidence:\n cite its problem, its users and its success criteria, and declare no market\n cross-references);\n- keep current-horizon scope explicit; and\n- provide observable acceptance language where meaningful.\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. 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\nworking 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",
41
+ "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",
42
42
  "skillRefs": [],
43
43
  "skillBodyRefs": [],
44
- "contextSources": [],
44
+ "contextSources": [
45
+ "creator_stated_facts",
46
+ "coherence_report"
47
+ ],
45
48
  "draftableDocumentDefinitionRefs": [],
46
49
  "suspendsForClarification": false,
47
50
  "briefAdequacyGate": false,
@@ -53,7 +53,7 @@ Where the application has declared a posture for the signal, record it on the en
53
53
 
54
54
  The derived signals arrive in the declared `risk_signals` context section of your brief — measured facts about this application's own declarations, each with the inputs it came from and none with a score. Ground your weighting in them. Do not restate a signal as a risk, do not treat their order as a priority, and never re-derive or estimate one: they are computed, and a number you produced yourself would be indistinguishable on the page from one that was measured.
55
55
 
56
- Four of them are read from the application's configuration and always arrive. The two that need every resource materialized — the personal-data inventory and the MCP exposure — can be absent when the application cannot be introspected, and the section simply will not carry them.
56
+ Four of them always arrive: three are read from the application's configuration (its capabilities, retention and provider hosting) and one from its specifications (the brand name's trademark standing). The ones that need every resource materialized — the personal-data inventory and its declaration gap, the MCP exposure and the chat-command exposure — can be absent when the application cannot be introspected, and the section simply will not carry them.
57
57
 
58
58
  The register does not require the derivation to have run. If signals were not supplied to this run, or only some were, produce the PROPOSED entries you can ground in the authored specification families, state plainly in the register which derived half is absent, and finish.
59
59
 
@@ -43,7 +43,7 @@
43
43
  ],
44
44
  "stepOutputs": [],
45
45
  "method": {
46
- "guidance": "# Complete the risk register\n\nThe derivation layer says what is PRESENT in this application — how many providers are vendor-hosted, how many operations an external agent can reach, which retention classes have a declared period, which resources have said nothing about personal data. Those are facts, and they are deliberately silent about what they MEAN.\n\nThis step writes what they mean for this product and these users, and proposes the risks no derivation reaches.\n\n## You are drafting, not deciding\n\nA model proposes; a human accepts; the accepted register is the committed file. Nothing you write here takes effect by being written, and the value of the artifact is that a person can disagree with it line by line. So:\n\n- Write statements a reader can argue with. \"Personal data is processed by third parties\" is unarguable and says nothing; \"two vendor-hosted LLM providers receive task titles and user names, which are the fields customers type freely\" is a claim someone can check and correct.\n- Never write a statement you cannot ground. If the evidence for a risk is that it sounds prudent, it is a PROPOSED entry and must be marked as one.\n- Do not soften a derived fact to make the register read better. The register is read by people deciding how deeply to audit something; a reassuring one is worse than none.\n\nAfter landing, the advisory judge reads the register against three criteria — honest entry origins, arguable statements with grounded bands, and the boundary with other mechanisms — and its verdicts reach the person accepting the register as notes. A verdict never refuses a landing.\n\n## Two kinds of entry, and the difference is what may be believed\n\n**SIGNAL_DERIVED** — completed from a derived signal, which the entry names. The measurement can be re-run, so the entry's premise is falsifiable: if the signal stops reporting the exposure, the statement resting on it is stale rather than merely old. One derived entry per signal.\n\n**PROPOSED** — a business risk nothing measures. This is why the step exists rather than the derivation being the whole answer: a register limited to what code can compute would omit most of what a product actually carries. Ground each one in the vision, the business model and the market snapshot, which this application has already authored, and never anchor it to a signal — a proposal pointing at a measurement is a derived entry wearing the wrong label.\n\n### The brand name is a derived signal\n\n`application:brand-name-trademark-standing` says where the brand's chosen name stands\nagainst its minimal trademark screening. It is computed by matching the brand name to its\nscreened candidate. When the signal reports the exposure as PRESENT, complete it into a\n**SIGNAL_DERIVED** entry with that `signalRef`. Do not write a PROPOSED one: the standing is\nmeasured, and a later run re-derives it.\n\n- **kept despite a conflict**: name the conflicting marks and registers from the signal's\n detail and the screening in your brief. Say what the exposure means for THIS product: an\n opposition, a cease-and-desist, a forced rebrand after launch.\n- **screening incomplete**: name the jurisdictions or registers not covered, and say the\n name is not cleared there.\n- **conflict unacknowledged**: the screening now finds a conflict that nobody chose to keep\n (the brand was named before a re-screen found it). Say so. Do not describe it as the\n creator's decision, because it was not one.\n- **never screened**: say so plainly.\n\nA cleared name, or a line with no brand, needs no entry. Never weigh a present exposure as\n\"low\" on the grounds that a screening ran: a screening is not a clearance.\n\n## Weighting is two qualitative bands and NOTHING is multiplied\n\nLikelihood and impact are each one of five bands. There is no score, no rating and no product of the two anywhere in the register, and this is not a stylistic preference: the derivation layer beneath this one asserts structurally that it emits no score, because a number is what a reader trusts without checking. Two judgements multiplied into a third judgement would put exactly that underneath a layer built to refuse it.\n\nGround the bands in what is IMPLEMENTED, not in how the risk sounds. \"Impact HIGH because the erasure path is manual\" is grounded. \"Impact HIGH because data breaches are serious\" is not — it would be equally true of every application ever built, which is the test for a weighting that carries no information.\n\nWhere the application has declared a posture for the signal, record it on the entry. A posture of AVOIDED that the measurement contradicts is not yours to resolve: state the risk as measured, note the contradiction in the weighting grounding, and let the person accepting the register decide whether the declaration or the product is wrong.\n\n## The signals, and what to do when they are not all there\n\nThe derived signals arrive in the declared `risk_signals` context section of your brief — measured facts about this application's own declarations, each with the inputs it came from and none with a score. Ground your weighting in them. Do not restate a signal as a risk, do not treat their order as a priority, and never re-derive or estimate one: they are computed, and a number you produced yourself would be indistinguishable on the page from one that was measured.\n\nFour of them are read from the application's configuration and always arrive. The two that need every resource materialized — the personal-data inventory and the MCP exposure — can be absent when the application cannot be introspected, and the section simply will not carry them.\n\nThe register does not require the derivation to have run. If signals were not supplied to this run, or only some were, produce the PROPOSED entries you can ground in the authored specification families, state plainly in the register which derived half is absent, and finish.\n\nDo not stop, do not ask for evidence to be collected first, and do not treat an absent measurement as an absent risk. A step that cannot proceed until evidence exists has made a measurement into a precondition, and a compliance workflow may never stand in front of the mechanism it describes.\n\n## What belongs to other mechanisms\n\n- **Which control objectives this application claims** — the compliance programme. A register entry may mention a control; it never binds one.\n- **Whether a control's evidence is adequate** — the evidence-adequacy step. The register says a risk exists, never that it has been discharged.\n- **How deeply to audit a demand** — a consumer of this register, not part of it. Write the risk; do not write the audit plan.\n- **Retention periods, provider deployment choices, jurisdictions** — configuration the application already declares. Read them; do not restate them as risks, and never contradict them here.\n",
46
+ "guidance": "# Complete the risk register\n\nThe derivation layer says what is PRESENT in this application — how many providers are vendor-hosted, how many operations an external agent can reach, which retention classes have a declared period, which resources have said nothing about personal data. Those are facts, and they are deliberately silent about what they MEAN.\n\nThis step writes what they mean for this product and these users, and proposes the risks no derivation reaches.\n\n## You are drafting, not deciding\n\nA model proposes; a human accepts; the accepted register is the committed file. Nothing you write here takes effect by being written, and the value of the artifact is that a person can disagree with it line by line. So:\n\n- Write statements a reader can argue with. \"Personal data is processed by third parties\" is unarguable and says nothing; \"two vendor-hosted LLM providers receive task titles and user names, which are the fields customers type freely\" is a claim someone can check and correct.\n- Never write a statement you cannot ground. If the evidence for a risk is that it sounds prudent, it is a PROPOSED entry and must be marked as one.\n- Do not soften a derived fact to make the register read better. The register is read by people deciding how deeply to audit something; a reassuring one is worse than none.\n\nAfter landing, the advisory judge reads the register against three criteria — honest entry origins, arguable statements with grounded bands, and the boundary with other mechanisms — and its verdicts reach the person accepting the register as notes. A verdict never refuses a landing.\n\n## Two kinds of entry, and the difference is what may be believed\n\n**SIGNAL_DERIVED** — completed from a derived signal, which the entry names. The measurement can be re-run, so the entry's premise is falsifiable: if the signal stops reporting the exposure, the statement resting on it is stale rather than merely old. One derived entry per signal.\n\n**PROPOSED** — a business risk nothing measures. This is why the step exists rather than the derivation being the whole answer: a register limited to what code can compute would omit most of what a product actually carries. Ground each one in the vision, the business model and the market snapshot, which this application has already authored, and never anchor it to a signal — a proposal pointing at a measurement is a derived entry wearing the wrong label.\n\n### The brand name is a derived signal\n\n`application:brand-name-trademark-standing` says where the brand's chosen name stands\nagainst its minimal trademark screening. It is computed by matching the brand name to its\nscreened candidate. When the signal reports the exposure as PRESENT, complete it into a\n**SIGNAL_DERIVED** entry with that `signalRef`. Do not write a PROPOSED one: the standing is\nmeasured, and a later run re-derives it.\n\n- **kept despite a conflict**: name the conflicting marks and registers from the signal's\n detail and the screening in your brief. Say what the exposure means for THIS product: an\n opposition, a cease-and-desist, a forced rebrand after launch.\n- **screening incomplete**: name the jurisdictions or registers not covered, and say the\n name is not cleared there.\n- **conflict unacknowledged**: the screening now finds a conflict that nobody chose to keep\n (the brand was named before a re-screen found it). Say so. Do not describe it as the\n creator's decision, because it was not one.\n- **never screened**: say so plainly.\n\nA cleared name, or a line with no brand, needs no entry. Never weigh a present exposure as\n\"low\" on the grounds that a screening ran: a screening is not a clearance.\n\n## Weighting is two qualitative bands and NOTHING is multiplied\n\nLikelihood and impact are each one of five bands. There is no score, no rating and no product of the two anywhere in the register, and this is not a stylistic preference: the derivation layer beneath this one asserts structurally that it emits no score, because a number is what a reader trusts without checking. Two judgements multiplied into a third judgement would put exactly that underneath a layer built to refuse it.\n\nGround the bands in what is IMPLEMENTED, not in how the risk sounds. \"Impact HIGH because the erasure path is manual\" is grounded. \"Impact HIGH because data breaches are serious\" is not — it would be equally true of every application ever built, which is the test for a weighting that carries no information.\n\nWhere the application has declared a posture for the signal, record it on the entry. A posture of AVOIDED that the measurement contradicts is not yours to resolve: state the risk as measured, note the contradiction in the weighting grounding, and let the person accepting the register decide whether the declaration or the product is wrong.\n\n## The signals, and what to do when they are not all there\n\nThe derived signals arrive in the declared `risk_signals` context section of your brief — measured facts about this application's own declarations, each with the inputs it came from and none with a score. Ground your weighting in them. Do not restate a signal as a risk, do not treat their order as a priority, and never re-derive or estimate one: they are computed, and a number you produced yourself would be indistinguishable on the page from one that was measured.\n\nFour of them always arrive: three are read from the application's configuration (its capabilities, retention and provider hosting) and one from its specifications (the brand name's trademark standing). The ones that need every resource materialized — the personal-data inventory and its declaration gap, the MCP exposure and the chat-command exposure — can be absent when the application cannot be introspected, and the section simply will not carry them.\n\nThe register does not require the derivation to have run. If signals were not supplied to this run, or only some were, produce the PROPOSED entries you can ground in the authored specification families, state plainly in the register which derived half is absent, and finish.\n\nDo not stop, do not ask for evidence to be collected first, and do not treat an absent measurement as an absent risk. A step that cannot proceed until evidence exists has made a measurement into a precondition, and a compliance workflow may never stand in front of the mechanism it describes.\n\n## What belongs to other mechanisms\n\n- **Which control objectives this application claims** — the compliance programme. A register entry may mention a control; it never binds one.\n- **Whether a control's evidence is adequate** — the evidence-adequacy step. The register says a risk exists, never that it has been discharged.\n- **How deeply to audit a demand** — a consumer of this register, not part of it. Write the risk; do not write the audit plan.\n- **Retention periods, provider deployment choices, jurisdictions** — configuration the application already declares. Read them; do not restate them as risks, and never contradict them here.\n",
47
47
  "skillRefs": [],
48
48
  "skillBodyRefs": [],
49
49
  "contextSources": [