@wildo-ai/framework-knowledge 1.1.11 → 1.1.13
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +4 -0
- package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +25 -3
- package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +40 -12
- package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +3 -3
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +12 -0
- package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +19 -2
- package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +33 -9
- package/dist/esm/framework-knowledge.definitions.d.ts +2 -3
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +180 -32
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/framework-knowledge.research-provenance.d.ts +6 -4
- package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.research-provenance.js.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/index.d.ts.map +1 -1
- package/dist/esm/index.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -3
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +4 -12
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +12 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +7 -4
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +76 -14
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -4
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -15
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +35 -14
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +16 -8
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +19 -8
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +30 -3
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +87 -16
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +2 -2
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +5 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +3 -2
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +45 -10
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +61 -21
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +4 -3
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +8 -5
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +3 -5
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +3 -3
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +8 -6
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +5 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +8 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +4 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +11 -3
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +6 -4
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +3 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +4 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +10 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +36 -13
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +8 -2
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +7 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +4 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +34 -6
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +5 -2
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +4 -3
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +2 -2
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +22 -10
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +39 -29
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +8 -3
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -7
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +2 -2
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +13 -5
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +3 -7
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +12 -14
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +3 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +2 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +3 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +2 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts +4 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +14 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +3 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +4 -2
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +34 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +35 -17
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/esm/source-anchor-grammar.d.ts.map +1 -1
- package/dist/esm/source-anchor-grammar.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
- package/dist/knowledge/manifest.json +7 -7
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +6 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +4 -4
- package/dist/knowledge/playbooks/bottom_up.build/method.md +12 -2
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +5 -3
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +439 -27
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +15 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +203 -7
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -5
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +2 -2
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +2 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +104 -2
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +59 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +18 -6
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +121 -24
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -8
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +15 -8
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +2 -1
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +19 -2
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +34 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +9 -2
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +1 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +27 -12
- package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +11 -5
- package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +4 -4
- package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +7 -2
- package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +1 -0
- package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +6 -6
- package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +3 -4
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +56 -5
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +3 -2
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +6 -4
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +5 -1
- package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +8 -1
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -3
- package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +11 -4
- package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +3 -2
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +16 -6
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +3 -2
- package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +5 -1
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/method.md +43 -11
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +24 -8
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +6 -2
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +49 -14
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +3 -3
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +6 -2
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +20 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +4 -3
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +69 -65
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +11 -7
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.definition/method.md +3 -1
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +11 -3
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +4 -2
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +4 -3
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +3 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +3 -2
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +14 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +11 -7
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +7 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +5 -1
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +6 -1
- package/dist/knowledge/playbooks/top_down.service-method/method.md +19 -1
- package/dist/knowledge/playbooks/top_down.service-method/playbook.json +16 -4
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +5 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +9 -3
- package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +17 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +59 -15
- package/dist/knowledge/references/application-documentation-chapters.config.md +45 -10
- package/dist/knowledge/references/application-documentation-plan.config.md +2 -2
- package/dist/knowledge/references/application-maturity.config.md +70 -1
- package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +4 -2
- package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +52 -11
- package/dist/knowledge/references/backend.inbound-handlers.definition.md +38 -1
- package/dist/knowledge/references/brand.name-screening.config.md +30 -3
- package/dist/knowledge/references/build-plan.task-graph.config.md +200 -4
- package/dist/knowledge/references/business-model.pricing-plan.config.md +12 -9
- package/dist/knowledge/references/business-model.snapshot.config.md +29 -2
- package/dist/knowledge/references/business-model.snapshot.validation.md +11 -8
- package/dist/knowledge/references/companion.introspection.behaviors.market.md +3 -0
- package/dist/knowledge/references/companion.market.generation-service.md +46 -5
- package/dist/knowledge/references/companion.market.prompt-renderer.md +1 -1
- package/dist/knowledge/references/companion.technical-doc.service.md +195 -63
- package/dist/knowledge/references/domain-plan.record-partition.md +105 -0
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +3 -1
- package/dist/knowledge/references/engine.saas-technical-doc.config.md +69 -15
- package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +10 -0
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +6 -0
- package/dist/knowledge/references/example.backend.custom-operation.declared-refusal-code.md +41 -0
- package/dist/knowledge/references/example.backend.custom-operation.external-effect-reservation.md +107 -0
- package/dist/knowledge/references/example.blueprint.definition.internal-tool.md +4 -2
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +8 -5
- package/dist/knowledge/references/example.infra.environment-config.local.md +13 -66
- package/dist/knowledge/references/example.module.companion-exports.full.md +1 -0
- package/dist/knowledge/references/example.module.relationships.actor-edge-back-to-scope-owner.md +35 -35
- package/dist/knowledge/references/example.navigation.one-entry-per-concept.md +47 -0
- package/dist/knowledge/references/example.organization-identity.system-of-record-partitions.md +18 -0
- package/dist/knowledge/references/example.provider.backend-module-shape.md +28 -4
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -4
- package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +21 -0
- package/dist/knowledge/references/example.resource.custom-view.backend-refusal.md +75 -0
- package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +8 -7
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +37 -2
- package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +0 -1
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +1 -1
- package/dist/knowledge/references/example.resource.ui-behavior.workflow-record-page.md +212 -0
- package/dist/knowledge/references/example.subject-export.portability-archive.md +42 -0
- package/dist/knowledge/references/example.views.app-level.workflow-home.md +238 -0
- package/dist/knowledge/references/example.website.demo.complete-items.md +3 -3
- package/dist/knowledge/references/example.website.pricing.audit-payloads.md +38 -0
- package/dist/knowledge/references/example.website.pricing.catalog-load.md +77 -0
- package/dist/knowledge/references/example.website.pricing.offers.md +43 -0
- package/dist/knowledge/references/example.website.pricing.plans-section.md +20 -0
- package/dist/knowledge/references/example.website.pricing.plans.md +88 -0
- package/dist/knowledge/references/example.website.section.stats.md +1 -1
- package/dist/knowledge/references/experience-plan.config.md +111 -1
- package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +2 -0
- package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +8 -1
- package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +104 -0
- package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +11 -6
- package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +165 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +1035 -19
- package/dist/knowledge/references/external-connectors.private.provider-compliance-state-collector.md +36 -0
- package/dist/knowledge/references/external-connectors.private.provider-configuration-check.md +69 -0
- package/dist/knowledge/references/integration-plan.config.md +7 -7
- package/dist/knowledge/references/placement-plan.config.md +19 -0
- package/dist/knowledge/references/platform.config.backing-services.md +9 -11
- package/dist/knowledge/references/platform.config.environment.deployment.md +133 -8
- package/dist/knowledge/references/platform.config.infra-provider-resolution.md +3 -3
- package/dist/knowledge/references/platform.config.infrastructure-host.md +1 -1
- package/dist/knowledge/references/platform.config.platform-key-management.md +89 -10
- package/dist/knowledge/references/platform.config.saas.md +20 -18
- package/dist/knowledge/references/presets.3d.frame-style-resolution.md +65 -0
- package/dist/knowledge/references/presets.layouts-2d.authoring.md +1 -1
- package/dist/knowledge/references/presets.models.field-form-control-variant.md +32 -0
- package/dist/knowledge/references/presets.models.labelling.sections.md +39 -0
- package/dist/knowledge/references/presets.models.surface-policy.defaults.md +3 -3
- package/dist/knowledge/references/presets.models.surface-variant.md +5 -4
- package/dist/knowledge/references/presets.themes.compose-theme.md +2 -1
- package/dist/knowledge/references/requirements.engine-substance.md +38 -0
- package/dist/knowledge/references/requirements.functional-requirement.config.md +11 -0
- package/dist/knowledge/references/requirements.non-functional-requirement.config.md +15 -4
- package/dist/knowledge/references/requirements.snapshot.config.md +2 -3
- package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +49 -2
- package/dist/knowledge/references/saas.backend.a2a.token-budget.md +11 -4
- package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +21 -0
- package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +5 -1
- package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
- package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +13 -1
- package/dist/knowledge/references/saas.backend.custom-operation.authoritative-fields.md +4 -1
- package/dist/knowledge/references/saas.backend.custom-operation.core-write-precondition.md +38 -0
- package/dist/knowledge/references/saas.backend.custom-operation.external-effect-reservation.md +109 -0
- package/dist/knowledge/references/saas.backend.custom-operation.hook-transaction-posture.md +43 -0
- package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +1 -1
- package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +62 -13
- package/dist/knowledge/references/saas.backend.domain-module.md +30 -1
- package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +26 -3
- package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +13 -1
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +435 -2
- package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +5 -3
- package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +1 -1
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +9 -4
- package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +2 -1
- package/dist/knowledge/references/saas.backend.privacy.subject-export-archive.md +26 -0
- package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +21 -19
- package/dist/knowledge/references/saas.backend.system-access-service.md +159 -4
- package/dist/knowledge/references/saas.config.content-security-policy.md +26 -9
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +1 -1
- package/dist/knowledge/references/saas.data-seeding.modes.md +4 -1
- package/dist/knowledge/references/saas.data-seeding.row-reference.md +2 -4
- package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +6 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +2 -0
- package/dist/knowledge/references/saas.frontend.chart-dashboard-view.md +43 -0
- package/dist/knowledge/references/saas.frontend.chart-dashboard.md +133 -0
- package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +8 -4
- package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +76 -9
- package/dist/knowledge/references/saas.frontend.command-menu.search-resource.md +3 -3
- package/dist/knowledge/references/saas.frontend.errors.backend-refusal.md +96 -0
- package/dist/knowledge/references/saas.frontend.execution-view.definition.md +40 -0
- package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +4 -0
- package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +3 -5
- package/dist/knowledge/references/saas.frontend.record-page-parts.md +117 -0
- package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +46 -16
- package/dist/knowledge/references/saas.frontend.related-resource-sections.md +6 -0
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +1 -1
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +43 -9
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +259 -15
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -2
- package/dist/knowledge/references/saas.frontend.section-stages.md +63 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +42 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +6 -9
- package/dist/knowledge/references/saas.frontend.viewer-may-perform-operation.md +52 -0
- package/dist/knowledge/references/saas.models.agent-suspension.md +8 -8
- package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +21 -0
- package/dist/knowledge/references/saas.models.auth.relationship-grantor-authentication.md +2 -2
- package/dist/knowledge/references/saas.models.chart-dashboard-tile-sizes.md +40 -0
- package/dist/knowledge/references/saas.models.config.declared-type-renames.md +246 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +20 -0
- package/dist/knowledge/references/saas.models.conversation-threads.md +39 -3
- package/dist/knowledge/references/saas.models.crypto-keys.floors.md +10 -0
- package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +2 -0
- package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +39 -0
- package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +7 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -78
- package/dist/knowledge/references/saas.models.engine-capabilities.md +11 -2
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +3 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +15 -8
- package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +13 -9
- package/dist/knowledge/references/saas.models.flows-actors.agent-configuration.md +29 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-content-guardrails-environment.md +52 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +7 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +8 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +47 -12
- package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +31 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +3 -3
- package/dist/knowledge/references/saas.models.flows.runnable-model.md +21 -2
- package/dist/knowledge/references/saas.models.guidance-flow.md +1 -1
- package/dist/knowledge/references/saas.models.http-api-binding.md +19 -8
- package/dist/knowledge/references/saas.models.human-decision-review-marker.md +1 -1
- package/dist/knowledge/references/saas.models.inbound-channels.md +71 -2
- package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +1 -1
- package/dist/knowledge/references/saas.models.notifications.targets.md +3 -1
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +201 -15
- package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +2 -1
- package/dist/knowledge/references/saas.models.organization-dashboard-layout.md +61 -0
- package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +5 -2
- package/dist/knowledge/references/saas.models.organizations.identity-declaration.md +201 -0
- package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +25 -3
- package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +6 -2
- package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +14 -0
- package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +1 -0
- package/dist/knowledge/references/saas.models.privacy.data-residency.md +676 -0
- package/dist/knowledge/references/saas.models.privacy.legal-holds.md +46 -2
- package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +6 -0
- package/dist/knowledge/references/saas.models.privacy.retention-binding.md +84 -1
- package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +10 -0
- package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +5 -3
- package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +2 -0
- package/dist/knowledge/references/saas.models.privacy.subject-export.md +134 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +5 -0
- package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +12 -6
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +15 -0
- package/dist/knowledge/references/saas.models.providers.processing-region-reach.md +132 -0
- package/dist/knowledge/references/saas.models.providers.processing-region-selection.md +139 -0
- package/dist/knowledge/references/saas.models.representative-activity.md +4 -0
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +107 -42
- package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +35 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +4 -2
- package/dist/knowledge/references/saas.models.resource-config.operation-condition-parameters.md +56 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +16 -6
- package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +38 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +14 -16
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +2 -2
- package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +21 -0
- package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +32 -15
- package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +5 -4
- package/dist/knowledge/references/saas.models.roles.definition.md +12 -1
- package/dist/knowledge/references/saas.models.roles.organization-defaults.md +6 -0
- package/dist/knowledge/references/saas.models.schema-family-builder.md +17 -2
- package/dist/knowledge/references/saas.models.system-of-record-actions.md +65 -1
- package/dist/knowledge/references/saas.models.system-of-record-capabilities.md +3 -1
- package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +16 -0
- package/dist/knowledge/references/saas.models.systems-of-record.md +75 -14
- package/dist/knowledge/references/saas.public-runtime.contract.md +41 -23
- package/dist/knowledge/references/saas.rag.retrieval-refusals.md +3 -2
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +12 -4
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +21 -2
- package/dist/knowledge/references/saas.specifications.engine-resource-sub-domain.md +105 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +6 -2
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +20 -3
- package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +100 -71
- package/dist/knowledge/references/saas.specifications.translation-glossary.md +80 -0
- package/dist/knowledge/references/saas.website.astro.label-loader.md +44 -10
- package/dist/knowledge/references/saas.website.astro.runtime-helper.md +3 -2
- package/dist/knowledge/references/saas.website.blog.collection-config.md +36 -32
- package/dist/knowledge/references/saas.website.blog.cover-resolver.md +1 -1
- package/dist/knowledge/references/saas.website.blog.frontmatter.md +2 -2
- package/dist/knowledge/references/saas.website.blog.post-renderer.md +2 -2
- package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +26 -19
- package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +1 -1
- package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +3 -1
- package/dist/knowledge/references/saas.website.config.site-context-loader.md +6 -3
- package/dist/knowledge/references/saas.website.label-keys.format.md +3 -2
- package/dist/knowledge/references/saas.website.label-pack.validator.md +3 -1
- package/dist/knowledge/references/service-method.config.md +35 -2
- package/dist/knowledge/references/vision.constraint.config.md +4 -2
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +60 -0
- package/dist/knowledge/references/zod.decorators.data-categories.md +46 -46
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +24 -0
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +11 -0
- package/dist/knowledge/references/zod.decorators.file-schema.md +4 -3
- package/dist/knowledge/references/zod.decorators.rag-source.md +20 -20
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +2 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +30 -24
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +63 -0
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +63 -0
- package/dist/knowledge/references/zod.factories.bigdecimal.md +4 -4
- package/dist/knowledge/references/zod.factories.code.md +4 -4
- package/dist/knowledge/references/zod.factories.duration.md +4 -4
- package/dist/knowledge/references/zod.factories.money.md +4 -4
- package/dist/knowledge/references/zod.factories.phone.md +4 -4
- package/dist/knowledge/references/zod.factories.year-month.md +79 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +455 -2
- package/dist/knowledge/registries/playbooks.json +51 -39
- package/dist/knowledge/registries/source-tags.json +2505 -1627
- package/dist/knowledge/rules/database-migration-obligation.md +6 -7
- package/dist/knowledge/rules/live-context-door.md +1 -1
- package/dist/knowledge/skills/INDEX.md +3 -1
- package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +24 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +1 -1
- package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +47 -12
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +30 -19
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +48 -13
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +2 -2
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -11
- package/dist/knowledge/skills/application-database-migrations/references/postgresql-supported-surfaces.md +64 -0
- package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +13 -11
- package/dist/knowledge/skills/application-roles-authoring/SKILL.md +28 -3
- package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +18 -1
- package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +22 -1
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +46 -2
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +5 -3
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-organization-identity-declaration-api.md +247 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-own-rows-declaration-api.md +12 -5
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +31 -2
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +51 -14
- package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +4 -1
- package/dist/knowledge/skills/backend-custom-operation/references/declared-refusal-codes.md +95 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +2 -2
- package/dist/knowledge/skills/backend-custom-operation/references/framework-core-write-precondition-api.md +73 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-error-handling-api.md +5 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-external-effect-reservation-api.md +276 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-hook-transaction-posture-api.md +90 -0
- package/dist/knowledge/skills/blueprint-authoring/SKILL.md +4 -2
- package/dist/knowledge/skills/brand-name-screening/SKILL.md +13 -2
- package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +30 -3
- package/dist/knowledge/skills/chat-agent-conversations/SKILL.md +3 -0
- package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +13 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +45 -4
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +17 -7
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +859 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +6 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +2 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +5 -1
- package/dist/knowledge/skills/config-app-shell/references/framework-command-menu-omnibox-api.md +3 -3
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +4 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +1 -1
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +8 -7
- package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +44 -1
- package/dist/knowledge/skills/config-navigation/SKILL.md +2 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +5 -0
- package/dist/knowledge/skills/config-navigation/references/one-entry-per-concept.md +101 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +2 -2
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +40 -3
- package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +20 -1
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +75 -11
- package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +21 -19
- package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +26 -9
- package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +240 -9
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +16 -2
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +116 -16
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +20 -18
- package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +1 -1
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +11 -1
- package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +5 -1
- package/dist/knowledge/skills/config-saas-backend/references/framework-declared-type-renames-api.md +261 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +20 -0
- package/dist/knowledge/skills/config-saas-backend/references/renaming-organization-and-user-types.md +69 -0
- package/dist/knowledge/skills/configure-billing/SKILL.md +6 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +28 -4
- package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +2 -0
- package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +4 -1
- package/dist/knowledge/skills/electronic-signature-deliverables/SKILL.md +131 -0
- package/dist/knowledge/skills/electronic-signature-deliverables/references/what-makes-a-request-signed.md +78 -0
- package/dist/knowledge/skills/email-add-template/SKILL.md +1 -1
- package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +11 -8
- package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +3 -2
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +31 -9
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +11 -4
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +26 -3
- package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +13 -3
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +27 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +34 -11
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +8 -5
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +13 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +188 -10
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +7 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +11 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +21 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +3 -3
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +7 -1
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +447 -8
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +30 -1
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +36 -15
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +8 -0
- package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +13 -3
- package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +21 -2
- package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +2 -1
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +13 -3
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +33 -1
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +5 -3
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +1 -1
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +6 -5
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +50 -14
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +1 -1
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +31 -2
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-translation-glossary-api.md +87 -0
- package/dist/knowledge/skills/inbound-channels/SKILL.md +31 -9
- package/dist/knowledge/skills/inbound-channels/references/email-channel.md +16 -4
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +169 -23
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +38 -1
- package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +43 -4
- package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +15 -3
- package/dist/knowledge/skills/inbound-channels/references/sms-channel.md +93 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +149 -77
- package/dist/knowledge/skills/infra-environment-config/references/framework-agent-content-guardrails-environment-api.md +67 -0
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +12 -14
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +133 -8
- package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +1 -1
- package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +89 -10
- package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +1 -1
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-focal-plane-settings-api.md +16 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +72 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +2 -2
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +12 -9
- package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +3 -3
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +2 -2
- package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +18 -10
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +7 -7
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +24 -2
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +33 -2
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +47 -6
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +61 -8
- package/dist/knowledge/skills/model-cost-attribution/SKILL.md +3 -1
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +1 -1
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +107 -42
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +21 -2
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +30 -1
- package/dist/knowledge/skills/module-relationships/SKILL.md +92 -91
- package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +31 -5
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +2 -2
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +34 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +1 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +4 -0
- package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +31 -0
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +272 -15
- package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +4 -5
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-compliance-state-collector-api.md +96 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-configuration-check-api.md +130 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +8 -1
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +124 -3
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +165 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +6 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-processing-region-api.md +340 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +11 -6
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +2 -0
- package/dist/knowledge/skills/provider-frontend-module/SKILL.md +5 -2
- package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +1 -1
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +17 -3
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +1035 -19
- package/dist/knowledge/skills/resource-add-field/SKILL.md +7 -0
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +322 -15
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +9 -5
- package/dist/knowledge/skills/resource-add-resource/references/framework-engine-api-reference-categories-api.md +119 -0
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +107 -42
- package/dist/knowledge/skills/resource-chat-commands/SKILL.md +2 -1
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +71 -5
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +2 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +48 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +34 -7
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +15 -11
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +66 -27
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +140 -58
- package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +28 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +34 -10
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +5 -4
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +158 -138
- package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +52 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +205 -19
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +253 -25
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +126 -1
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +259 -15
- package/dist/knowledge/skills/resource-custom-view/references/framework-backend-refusal-api.md +110 -0
- package/dist/knowledge/skills/resource-external-data/SKILL.md +46 -12
- package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +1 -1
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +15 -8
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +19 -8
- package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +3 -1
- package/dist/knowledge/skills/resource-external-data/references/local-test-doubles.md +121 -0
- package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +1 -1
- package/dist/knowledge/skills/resource-external-data/references/partition-from-the-domain-plan.md +230 -0
- package/dist/knowledge/skills/resource-external-data/references/presenting-a-copy-and-a-read-through.md +73 -0
- package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +26 -5
- package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +76 -6
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +8 -0
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +12 -9
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +11 -2
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +29 -2
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +20 -20
- package/dist/knowledge/skills/resource-retention-binding/SKILL.md +18 -2
- package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +46 -2
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +84 -1
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +10 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +5 -3
- package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +21 -0
- package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +14 -2
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +1 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +4 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +78 -17
- package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +2 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +26 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +46 -46
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +17 -2
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +36 -24
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +63 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +104 -23
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +123 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +72 -0
- package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +42 -2
- package/dist/knowledge/skills/resource-status-lifecycle/references/framework-operation-condition-parameters-api.md +67 -0
- package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +16 -12
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +66 -3
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +89 -10
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +11 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +263 -17
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-record-page-parts-api.md +155 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +83 -16
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +44 -10
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-section-stages-api.md +102 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/record-page-anatomy.md +9 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +33 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +19 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/workflow-record-page.md +264 -0
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +24 -4
- package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +12 -0
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +7 -6
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +6 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +42 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +6 -9
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +21 -2
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +26 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +121 -75
- package/dist/knowledge/skills/spec-resource-update/references/workflow-record-page-specification.md +237 -0
- package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +100 -71
- package/dist/knowledge/skills/subject-data-export/SKILL.md +176 -0
- package/dist/knowledge/skills/subject-data-export/references/file-content-exclusions.md +15 -0
- package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-api.md +142 -0
- package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-archive-api.md +33 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +3 -1
- package/dist/knowledge/skills/views-app-level/references/workflow-home.md +373 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +36 -5
- package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +9 -5
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +4 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-chart-dashboard-api.md +371 -0
- package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +40 -0
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +8 -6
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +70 -59
- package/dist/knowledge/skills/website-building-blocks/SKILL.md +1 -1
- package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +3 -3
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +4 -2
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +3 -1
- package/dist/knowledge/skills/website-label-pack/SKILL.md +20 -5
- package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +6 -3
- package/dist/knowledge/skills/website-section-comparison/SKILL.md +2 -2
- package/dist/knowledge/skills/website-section-contact/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-cta/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-faq/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-hero/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-integrations/SKILL.md +3 -3
- package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +142 -98
- package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +178 -66
- package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +3 -1
- package/dist/knowledge/skills/website-section-problem/SKILL.md +3 -3
- package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-roadmap/SKILL.md +4 -4
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +2 -2
- package/dist/knowledge/skills/website-section-stats/SKILL.md +3 -3
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +3 -2
- package/dist/knowledge/skills/worker-authoring/SKILL.md +4 -2
- package/dist/knowledge/topic-index.json +2422 -723
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/package.json +6 -6
- package/dist/tsconfig.tsbuildinfo +0 -1
|
@@ -18,7 +18,7 @@
|
|
|
18
18
|
],
|
|
19
19
|
"stepOutputs": [],
|
|
20
20
|
"method": {
|
|
21
|
-
"guidance": "# Vision Elicitation — Interview Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **vision interviewer**. Your one job is to draw the product's\nfoundational vision out of the creator through a structured conversation, and\nto capture it as a single typed **`VisionSnapshot`** — the `vision-brief`\nartifact. This is the **first** top-down step: everything downstream\n(positioning, the capability map, the compliance posture, the roadmap) reads\nthe vision you produce, so an honest, well-framed vision is the whole task.\n\nYou do **not** design the domain, draft requirements, or write code. You\nelicit *intent* — what the product is, why it should exist, what winning looks\nlike, and what limits bound it — and nothing more. Keep the market family\n(segments, personas) and the requirements family out of scope; the vision\nreferences them later, it does not absorb them.\n\n## The application's line\n\nThe first question, `application-line`, is the kind of application being created: its **main line**.\nThe creator's answer is recorded exactly as given and decides which playbooks this application runs\nfrom here on. It is **not** part of the `VisionSnapshot`: do not restate it in the vision, and never\nanswer it on the creator's behalf. If the creator is unsure, describe each option and let them choose.\n\nAn application created from a blueprint that carries a line already has this question answered: `wildo init`\nrecorded the blueprint's line, answered by `blueprint:<id>@<version>`. Choosing the blueprint was the creator's\nchoice of line, so it is not asked again. The creator may still change it by answering again.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, follow up where an answer is thin, and skip a follow-up the\n creator already answered. Reflect each answer back in one line and let the\n creator correct you before you move on.\n- **Progressive is fine.** A `VisionSnapshot` requires only the **idea**; the\n problem statement and mission are OPTIONAL and elicited progressively. If the\n creator can only give you the idea today, capture it, note what is still\n open, and stop — the snapshot persists as partially-elicited and this\n playbook can resume. Never invent a problem or mission the creator did not\n give you just to fill the shape.\n- **An ASSUMED answer is a hypothesis, not the creator's statement.** When the\n creator did not know an answer, or chose the short interview, the companion\n proposed one from their other answers, and either they kept it or an\n unattended round recorded it for them. Such answers\n arrive in your brief marked ASSUMED, with what they rest on. Use them — they\n are why the interview could finish — but keep them consistent with what the\n creator actually said, prefer the creator's own answers wherever the two\n pull apart, and never phrase an assumed answer as the creator's own words or\n intent. Record an assumed constraint or criterion as modestly as it was\n proposed; do not sharpen a guess into a commitment.\n- **One product, one vision.** The snapshot is a single aggregate, not a list\n — one idea, one problem, one mission, plus ref-addressable success criteria\n and constraints. If the creator describes two products, stop and ask which\n one this journey is for.\n\n## What you elicit — one aggregate\n\nWork the vision entity by entity. For each, the target shape and the framing\nquestions:\n\n- **Idea** (REQUIRED). The anchor concept. Capture a quotable one-liner\n (\"X for Y\") and a short paragraph expanding it (core capability, shape of the\n solution). Record any framing caveats or pivots as notes. A vision without an\n idea is nothing — do not proceed to the rest until you have it.\n- **Problem** (optional, WARNed when absent). The pain the product exists to\n solve: the core statement, who is affected (prose — the deep segment model is\n the market family's job), how people cope today, the cost of leaving it\n unsolved, and the timing trigger that makes solving it urgent *now*. This is\n a framing surface, not a sized opportunity model — capture the \"why\", not a\n TAM.\n- **Mission** (optional, WARNed when absent). The enduring purpose: the mission\n statement (what we do, for whom, to what end, in one sentence), the\n aspirational long-term end-state if it fully succeeds, and the guiding\n principles / non-negotiables that constrain *how* the product is built.\n Principles are chosen stances — keep them distinct from the hard external\n constraints below.\n- **Success criteria** (ref-addressable, `success-criterion-<slug>`). What\n \"this succeeded\" concretely looks like. Each criterion is a statement, an\n optional metric and target (free prose at this stage — \"500 weekly active\n teams\", \"median time-to-first-value < 5 min\"), and a coarse horizon bucket\n (`launch` / `short_term` / `long_term`). Do not force a quantified metric\n where the creator only has a qualitative one — a typed metric taxonomy is a\n later concern. A vision with no success criteria cannot be judged\n succeeded — the validator WARNs on it, so push for at least one.\n- **Constraints** (ref-addressable, `constraint-<slug>`). External limits the\n product must be built within, each classified by kind: `technical`,\n `business`, `compliance`, `resource`, `timeline`, or `other`. Capture the\n constraint statement and, where the creator gives it, the rationale (the\n source of the limit).\n - **Compliance constraints get explicit attention.** Ask whether the product\n handles regulated or personal data, operates in a regulated sector or has contractual\n assurance commitments. If so, record each as a\n `kind: compliance` constraint with a **prose** statement (\"Must be\n GDPR-compliant for EU customer personal data\"). Stop at prose — the deep\n per-regime obligation model (control catalogs, data-flow / residency\n matrices) is the compliance-posture step's job, not yours. Getting the\n compliance *seam* named here is what lets that later step engage.\n\n### The product's shape: workflow, users, boundary\n\nThree questions fix what the product IS, so that no later step decides it again: `core-workflow` (the\nstages a piece of work passes through), `user-groups` (who uses it, for what, on which device) and\n`scope-boundary` (what is explicitly left out). Two runs given the same answers must build the same\nproduct, and without these they did not: one built a customer-workflow CRM that left invoicing to\nother tools, the other built invoicing software with no customer follow-up at all.\n\nCarry them into the snapshot in the creator's own terms:\n\n- the workflow's stages, in order, in the idea's `description`;\n- the user groups, what each does, and their devices, in the problem's \"who is affected\" (and in the\n idea when the product's shape depends on them, such as work done in the field on a phone);\n- each scope boundary as a `constraint` of kind `business`, stated as an exclusion (\"Invoicing is out\n of scope: customers keep their accounting tool\"), with the creator's reason as its rationale.\n\nLater steps also receive these answers verbatim, so do not reword a stage or a boundary into\nsomething the creator did not say. An answer of \"nothing\" for the boundary records no constraint.\n\n## What you emit\n\nA single `VisionSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told\n otherwise).\n- `idea` — the required anchor (`oneLiner`, `description`, optional `notes`).\n- `problem` / `mission` — the optional singletons, present only if elicited.\n- `successCriteria[]` — each with a stable kebab-case `ref` prefixed\n `success-criterion-`, unique across the set.\n- `constraints[]` — each with a stable kebab-case `ref` prefixed `constraint-`,\n unique across the set, and a `kind`.\n\nAuthor every entity in English. Use stable, human-readable ref slugs\n(`success-criterion-weekly-active-teams`, `constraint-gdpr-eu-data`) — they are\naddressed by ref downstream, so a duplicate silently drops an entity.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `vision-snapshot-valid`\ngate (`validateVisionSnapshot`) before it commits. Duplicate refs and malformed\nrefs (a success-criterion or constraint ref that is not kebab-case with its\nrequired prefix) are hard **errors** — the gate rejects them. A missing problem,\na missing mission, and an empty success-criteria set are **warnings**: they\nreflect a not-yet-complete vision, they do not block, and the journey persists\nthe snapshot as partially-elicited. Emit clean refs the first time; let the\nwarnings stand honestly when the vision genuinely is not complete yet, rather\nthan inventing entities to silence them.\n\n## Approval\n\nThe drafted `VisionSnapshot` is presented to the creator for approval before it\nbecomes the committed `vision-brief`. Show the vision back in plain prose — the\none-liner, the problem, the mission, the criteria, the constraints — and let the\ncreator confirm or correct it. The vision is the seed every later step trusts;\nit is worth one explicit human sign-off.\n\n## Runtime context\n\nBefore you start, read the current journey state and scope so you elicit the\nvision for the right product, and read any vision that already exists so you\nrefine it rather than re-eliciting it from scratch.\n\n(When a prior vision exists it arrives in your brief as the `vision-brief` input section — refine\nthat content rather than re-eliciting it.)\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n",
|
|
21
|
+
"guidance": "# Vision Elicitation — Interview Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **vision interviewer**. Your one job is to draw the product's\nfoundational vision out of the creator through a structured conversation, and\nto capture it as a single typed **`VisionSnapshot`** — the `vision-brief`\nartifact. This is the **first** top-down step: everything downstream\n(positioning, the capability map, the compliance posture, the roadmap) reads\nthe vision you produce, so an honest, well-framed vision is the whole task.\n\nYou do **not** design the domain, draft requirements, or write code. You\nelicit *intent* — what the product is, why it should exist, what winning looks\nlike, and what limits bound it — and nothing more. Keep the market family\n(segments, personas) and the requirements family out of scope; the vision\nreferences them later, it does not absorb them.\n\n## The application's line\n\nThe first question, `application-line`, is the kind of application being created: its **main line**.\nThe creator's answer is recorded exactly as given and decides which playbooks this application runs\nfrom here on. It is **not** part of the `VisionSnapshot`: do not restate it in the vision, and never\nanswer it on the creator's behalf. If the creator is unsure, describe each option and let them choose.\n\nAn application created from a blueprint that carries a line already has this question answered: `wildo init`\nrecorded the blueprint's line, answered by `blueprint:<id>@<version>`. Choosing the blueprint was the creator's\nchoice of line, so it is not asked again. The creator may still change it by answering again.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, follow up where an answer is thin, and skip a follow-up the\n creator already answered. Reflect each answer back in one line and let the\n creator correct you before you move on.\n- **Progressive is fine.** A `VisionSnapshot` requires only the **idea**; the\n problem statement and mission are OPTIONAL and elicited progressively. If the\n creator can only give you the idea today, capture it, note what is still\n open, and stop — the snapshot persists as partially-elicited and this\n playbook can resume. Never invent a problem or mission the creator did not\n give you just to fill the shape.\n- **An ASSUMED answer is a hypothesis, not the creator's statement.** When the\n creator did not know an answer, or chose the short interview, the companion\n proposed one from their other answers, and either they kept it or an\n unattended round recorded it for them. Such answers\n arrive in your brief marked ASSUMED, with what they rest on. Use them — they\n are why the interview could finish — but keep them consistent with what the\n creator actually said, prefer the creator's own answers wherever the two\n pull apart, and never phrase an assumed answer as the creator's own words or\n intent. Record an assumed constraint or criterion as modestly as it was\n proposed; do not sharpen a guess into a commitment.\n- **One product, one vision.** The snapshot is a single aggregate, not a list\n — one idea, one problem, one mission, plus ref-addressable success criteria\n and constraints. If the creator describes two products, stop and ask which\n one this journey is for.\n\n## What you elicit — one aggregate\n\nWork the vision entity by entity. For each, the target shape and the framing\nquestions:\n\n- **Idea** (REQUIRED). The anchor concept. Capture a quotable one-liner\n (\"X for Y\") and a short paragraph expanding it (core capability, shape of the\n solution). Record any framing caveats or pivots as notes. A vision without an\n idea is nothing — do not proceed to the rest until you have it.\n- **Problem** (optional, WARNed when absent). The pain the product exists to\n solve: the core statement, who is affected (prose — the deep segment model is\n the market family's job), how people cope today, the cost of leaving it\n unsolved, and the timing trigger that makes solving it urgent *now*. This is\n a framing surface, not a sized opportunity model — capture the \"why\", not a\n TAM.\n- **Mission** (optional, WARNed when absent). The enduring purpose: the mission\n statement (what we do, for whom, to what end, in one sentence), the\n aspirational long-term end-state if it fully succeeds, and the guiding\n principles / non-negotiables that constrain *how* the product is built.\n Principles are chosen stances — keep them distinct from the hard external\n constraints below.\n- **Success criteria** (ref-addressable, `success-criterion-<slug>`). What\n \"this succeeded\" concretely looks like. Each criterion is a statement, an\n optional metric and target (free prose at this stage — \"500 weekly active\n teams\", \"median time-to-first-value < 5 min\"), and a coarse horizon bucket\n (`launch` / `short_term` / `long_term`). Do not force a quantified metric\n where the creator only has a qualitative one — a typed metric taxonomy is a\n later concern. A vision with no success criteria cannot be judged\n succeeded — the validator WARNs on it, so push for at least one.\n- **Constraints** (ref-addressable, `constraint-<slug>`). External limits the\n product must be built within, each classified by kind: `technical`,\n `business`, `compliance`, `resource`, `timeline`, or `other`. Capture the\n constraint statement and, where the creator gives it, the rationale (the\n source of the limit).\n - **Compliance constraints get explicit attention.** Ask whether the product\n handles regulated or personal data, operates in a regulated sector or has contractual\n assurance commitments. If so, record each as a\n `kind: compliance` constraint with a **prose** statement (\"Must be\n GDPR-compliant for EU customer personal data\"). Stop at prose — the deep\n per-regime obligation model (control catalogs, data-flow / residency\n matrices) is the compliance-posture step's job, not yours. Getting the\n compliance *seam* named here is what lets that later step engage.\n - **A regulated-domain question left NOT DECIDED YET is an open compliance\n constraint.** When the creator left one of the five regulated-domain\n questions (children's or specially protected data, financial services,\n healthcare, legal or compliance decisions, public sector or critical\n infrastructure) not decided yet, record a `kind: compliance` constraint\n whose statement names the OPEN QUESTION and what it decides (\"Whether the\n application will process health or clinical data is not decided yet; it\n decides whether health-data rules apply.\"), with the creator's reason as\n its rationale when they gave one. Never leave it out, which a later step\n reads as \"no\", and never answer it either way from the other answers.\n\n### The product's shape: workflow, users, boundary\n\nThree questions fix what the product IS, so that no later step decides it again: `core-workflow` (the\nstages a piece of work passes through), `user-groups` (who uses it, for what, on which device) and\n`scope-boundary` (what is explicitly left out). Two runs given the same answers must build the same\nproduct, and without these they did not: one built a customer-workflow CRM that left invoicing to\nother tools, the other built invoicing software with no customer follow-up at all.\n\nCarry them into the snapshot in the creator's own terms:\n\n- the workflow's stages, in order, in the idea's `description`;\n- the user groups, what each does, and their devices, in the problem's \"who is affected\" (and in the\n idea when the product's shape depends on them, such as work done in the field on a phone; in the\n idea's `description` when the creator left the problem not decided yet, so they are never lost);\n- each scope boundary as a `constraint` of kind `business`, stated as an exclusion (\"Invoicing is out\n of scope: customers keep their accounting tool\"), with the creator's reason as its rationale.\n\nLater steps also receive these answers verbatim, so do not reword a stage or a boundary into\nsomething the creator did not say. An answer of \"nothing\" for the boundary records no constraint.\n\n## What you emit\n\nA single `VisionSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told\n otherwise).\n- `idea` — the required anchor (`oneLiner`, `description`, optional `notes`).\n- `problem` / `mission` — the optional singletons, present only if elicited.\n When the creator left the problem statement or the mission NOT DECIDED YET,\n emit that singleton as `null`; never fill it from the other answers.\n- `successCriteria[]` — each with a stable kebab-case `ref` prefixed\n `success-criterion-`, unique across the set. Empty when the creator left the\n success criteria not decided yet: an empty set is honest, and the validator\n WARNs on it so it stays visible.\n- `constraints[]` — each with a stable kebab-case `ref` prefixed `constraint-`,\n unique across the set, and a `kind`.\n\nAuthor every entity in English. Use stable, human-readable ref slugs\n(`success-criterion-weekly-active-teams`, `constraint-gdpr-eu-data`) — they are\naddressed by ref downstream, so a duplicate silently drops an entity.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `vision-snapshot-valid`\ngate (`validateVisionSnapshot`) before it commits. Duplicate refs and malformed\nrefs (a success-criterion or constraint ref that is not kebab-case with its\nrequired prefix) are hard **errors** — the gate rejects them. A missing problem,\na missing mission, and an empty success-criteria set are **warnings**: they\nreflect a not-yet-complete vision, they do not block, and the journey persists\nthe snapshot as partially-elicited. Emit clean refs the first time; let the\nwarnings stand honestly when the vision genuinely is not complete yet, rather\nthan inventing entities to silence them.\n\n## Approval\n\nThe drafted `VisionSnapshot` is presented to the creator for approval before it\nbecomes the committed `vision-brief`. Show the vision back in plain prose — the\none-liner, the problem, the mission, the criteria, the constraints — and let the\ncreator confirm or correct it. The vision is the seed every later step trusts;\nit is worth one explicit human sign-off.\n\n## Runtime context\n\nBefore you start, read the current journey state and scope so you elicit the\nvision for the right product, and read any vision that already exists so you\nrefine it rather than re-eliciting it from scratch.\n\n(When a prior vision exists it arrives in your brief as the `vision-brief` input section — refine\nthat content rather than re-eliciting it.)\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n",
|
|
22
22
|
"skillRefs": [],
|
|
23
23
|
"skillBodyRefs": [],
|
|
24
24
|
"elicitation": {
|
|
@@ -51,31 +51,46 @@
|
|
|
51
51
|
"ref": "problem-statement",
|
|
52
52
|
"question": "What problem does this exist to solve, who suffers it, how do they cope today, and what does leaving it unsolved cost?",
|
|
53
53
|
"kind": "free_text",
|
|
54
|
-
"depth": "essential"
|
|
54
|
+
"depth": "essential",
|
|
55
|
+
"nonAnswers": [
|
|
56
|
+
"deferred"
|
|
57
|
+
]
|
|
55
58
|
},
|
|
56
59
|
{
|
|
57
60
|
"ref": "problem-why-now",
|
|
58
61
|
"question": "What makes solving this urgent now? Answer \"none\" if no specific trigger exists.",
|
|
59
62
|
"kind": "free_text",
|
|
60
|
-
"depth": "detail"
|
|
63
|
+
"depth": "detail",
|
|
64
|
+
"nonAnswers": [
|
|
65
|
+
"not_applicable"
|
|
66
|
+
]
|
|
61
67
|
},
|
|
62
68
|
{
|
|
63
69
|
"ref": "mission-statement",
|
|
64
70
|
"question": "What is the enduring mission and long-term end-state?",
|
|
65
71
|
"kind": "free_text",
|
|
66
|
-
"depth": "detail"
|
|
72
|
+
"depth": "detail",
|
|
73
|
+
"nonAnswers": [
|
|
74
|
+
"deferred"
|
|
75
|
+
]
|
|
67
76
|
},
|
|
68
77
|
{
|
|
69
78
|
"ref": "mission-principles",
|
|
70
79
|
"question": "List guiding principles and non-negotiables that constrain how the product is built.",
|
|
71
80
|
"kind": "free_text",
|
|
72
|
-
"depth": "detail"
|
|
81
|
+
"depth": "detail",
|
|
82
|
+
"nonAnswers": [
|
|
83
|
+
"not_applicable"
|
|
84
|
+
]
|
|
73
85
|
},
|
|
74
86
|
{
|
|
75
87
|
"ref": "success-criteria",
|
|
76
88
|
"question": "How will you know this succeeded? Name observable criteria and targets where available.",
|
|
77
89
|
"kind": "free_text",
|
|
78
|
-
"depth": "detail"
|
|
90
|
+
"depth": "detail",
|
|
91
|
+
"nonAnswers": [
|
|
92
|
+
"deferred"
|
|
93
|
+
]
|
|
79
94
|
},
|
|
80
95
|
{
|
|
81
96
|
"ref": "success-primary-horizon",
|
|
@@ -86,13 +101,19 @@
|
|
|
86
101
|
"short_term",
|
|
87
102
|
"long_term"
|
|
88
103
|
],
|
|
89
|
-
"depth": "detail"
|
|
104
|
+
"depth": "detail",
|
|
105
|
+
"nonAnswers": [
|
|
106
|
+
"deferred"
|
|
107
|
+
]
|
|
90
108
|
},
|
|
91
109
|
{
|
|
92
110
|
"ref": "constraints-general",
|
|
93
111
|
"question": "What external technical, business, resource or timeline limits apply?",
|
|
94
112
|
"kind": "free_text",
|
|
95
|
-
"depth": "detail"
|
|
113
|
+
"depth": "detail",
|
|
114
|
+
"nonAnswers": [
|
|
115
|
+
"not_applicable"
|
|
116
|
+
]
|
|
96
117
|
},
|
|
97
118
|
{
|
|
98
119
|
"ref": "core-workflow",
|
|
@@ -110,52 +131,75 @@
|
|
|
110
131
|
"ref": "scope-boundary",
|
|
111
132
|
"question": "What is explicitly NOT part of the product, left to other tools or to later (for example invoicing, accounting, payroll)? Answer \"nothing\" if no boundary has been decided.",
|
|
112
133
|
"kind": "free_text",
|
|
113
|
-
"depth": "essential"
|
|
134
|
+
"depth": "essential",
|
|
135
|
+
"nonAnswers": [
|
|
136
|
+
"not_applicable",
|
|
137
|
+
"deferred"
|
|
138
|
+
]
|
|
114
139
|
},
|
|
115
140
|
{
|
|
116
141
|
"ref": "regulated-children-data",
|
|
117
142
|
"question": "Will this application be directed to children, or process children's data or other specially protected personal data?",
|
|
118
143
|
"kind": "confirm",
|
|
119
144
|
"depth": "detail",
|
|
120
|
-
"regulatedDomain": true
|
|
145
|
+
"regulatedDomain": true,
|
|
146
|
+
"nonAnswers": [
|
|
147
|
+
"deferred"
|
|
148
|
+
]
|
|
121
149
|
},
|
|
122
150
|
{
|
|
123
151
|
"ref": "regulated-financial-services",
|
|
124
152
|
"question": "Will this application operate in financial services or handle regulated financial activity?",
|
|
125
153
|
"kind": "confirm",
|
|
126
154
|
"depth": "detail",
|
|
127
|
-
"regulatedDomain": true
|
|
155
|
+
"regulatedDomain": true,
|
|
156
|
+
"nonAnswers": [
|
|
157
|
+
"deferred"
|
|
158
|
+
]
|
|
128
159
|
},
|
|
129
160
|
{
|
|
130
161
|
"ref": "regulated-healthcare-life-sciences",
|
|
131
162
|
"question": "Will this application operate in healthcare or life sciences, or process health or clinical data?",
|
|
132
163
|
"kind": "confirm",
|
|
133
164
|
"depth": "detail",
|
|
134
|
-
"regulatedDomain": true
|
|
165
|
+
"regulatedDomain": true,
|
|
166
|
+
"nonAnswers": [
|
|
167
|
+
"deferred"
|
|
168
|
+
]
|
|
135
169
|
},
|
|
136
170
|
{
|
|
137
171
|
"ref": "regulated-legal-compliance",
|
|
138
172
|
"question": "Will this application make or materially support legal, regulatory, or compliance decisions?",
|
|
139
173
|
"kind": "confirm",
|
|
140
174
|
"depth": "detail",
|
|
141
|
-
"regulatedDomain": true
|
|
175
|
+
"regulatedDomain": true,
|
|
176
|
+
"nonAnswers": [
|
|
177
|
+
"deferred"
|
|
178
|
+
]
|
|
142
179
|
},
|
|
143
180
|
{
|
|
144
181
|
"ref": "regulated-public-sector-critical-infrastructure",
|
|
145
182
|
"question": "Will this application serve the public sector, or operate in critical infrastructure or another safety-critical domain?",
|
|
146
183
|
"kind": "confirm",
|
|
147
184
|
"depth": "detail",
|
|
148
|
-
"regulatedDomain": true
|
|
185
|
+
"regulatedDomain": true,
|
|
186
|
+
"nonAnswers": [
|
|
187
|
+
"deferred"
|
|
188
|
+
]
|
|
149
189
|
},
|
|
150
190
|
{
|
|
151
191
|
"ref": "compliance-detail",
|
|
152
192
|
"question": "For any yes above: which regimes apply, to what data, and in which jurisdictions?",
|
|
153
193
|
"kind": "free_text",
|
|
154
194
|
"depth": "detail",
|
|
155
|
-
"regulatedDomain": true
|
|
195
|
+
"regulatedDomain": true,
|
|
196
|
+
"nonAnswers": [
|
|
197
|
+
"not_applicable"
|
|
198
|
+
]
|
|
156
199
|
}
|
|
157
200
|
]
|
|
158
201
|
},
|
|
202
|
+
"derivedFromAnswers": [],
|
|
159
203
|
"contextSources": [],
|
|
160
204
|
"draftableDocumentDefinitionRefs": [],
|
|
161
205
|
"suspendsForClarification": false,
|
|
@@ -15,10 +15,16 @@
|
|
|
15
15
|
*
|
|
16
16
|
* ## Where it lives, and what makes it accepted
|
|
17
17
|
*
|
|
18
|
-
* One file: `specifications/src/technical-documentation/
|
|
19
|
-
* `
|
|
20
|
-
*
|
|
21
|
-
*
|
|
18
|
+
* One file PER CHAPTER: `specifications/src/technical-documentation/chapters/<chapterRef>.ts`, exporting
|
|
19
|
+
* `documentationChapter = defineApplicationDocumentationChapter('<chapterRef>', { … })`. The file is named
|
|
20
|
+
* by the chapter's `chapterRef` and declares that same ref, which is what a build task's landing probe looks
|
|
21
|
+
* for in it. Publication reads every file in that directory; nothing imports or registers them, so writing
|
|
22
|
+
* one chapter never edits a file another chapter is written in, and a build writes its chapters at once
|
|
23
|
+
* (#3204: with one shared file, 23 chapter tasks queued behind each other for about 48 minutes).
|
|
24
|
+
*
|
|
25
|
+
* A set may still be written inline, as a `defineApplicationDocumentationChapters({ … })` value wired into
|
|
26
|
+
* the companion exports as `documentationChapters`. Publication merges the two and refuses a chapter
|
|
27
|
+
* declared in both, or in two files.
|
|
22
28
|
*
|
|
23
29
|
* Accepted means COMMITTED — there is no acceptance state, ledger or digest beside git. Publication
|
|
24
30
|
* (`wildo docs publish`) renders the WORKING TREE, exactly as every other specification-derived page
|
|
@@ -47,12 +53,11 @@
|
|
|
47
53
|
*
|
|
48
54
|
* @example
|
|
49
55
|
* ```ts
|
|
50
|
-
*
|
|
51
|
-
*
|
|
52
|
-
*
|
|
53
|
-
*
|
|
54
|
-
*
|
|
55
|
-
* },
|
|
56
|
+
* // specifications/src/technical-documentation/chapters/chapter-close-a-deal.ts
|
|
57
|
+
* export const documentationChapter = defineApplicationDocumentationChapter('chapter-close-a-deal', {
|
|
58
|
+
* classification: TechnicalDocumentationSourceClassification.PUBLIC,
|
|
59
|
+
* body: 'Closing a deal moves it to won and notifies its owner.\n\n## Before you start\n\n…',
|
|
60
|
+
* apiReferences: [{ label: 'Change a deal status', resource: 'deals', operation: 'change_status' }],
|
|
56
61
|
* });
|
|
57
62
|
* ```
|
|
58
63
|
*/
|
|
@@ -117,6 +122,7 @@ export const ApplicationDocumentationChapterSourceSchema = z.strictObject({
|
|
|
117
122
|
applicabilityRequirements: z.array(TechnicalDocumentationApplicabilityRequirementV1Schema).default([]),
|
|
118
123
|
});
|
|
119
124
|
export type ApplicationDocumentationChapterSource = z.infer<typeof ApplicationDocumentationChapterSourceSchema>;
|
|
125
|
+
export type ApplicationDocumentationChapterSourceInput = z.input<typeof ApplicationDocumentationChapterSourceSchema>;
|
|
120
126
|
|
|
121
127
|
/** Every authored chapter, keyed by the plan's `chapterRef`. */
|
|
122
128
|
export const ApplicationDocumentationChapterSetSchema = z
|
|
@@ -149,4 +155,33 @@ export type ApplicationDocumentationChapterSetInput = z.input<typeof Application
|
|
|
149
155
|
export function defineApplicationDocumentationChapters(chapters: ApplicationDocumentationChapterSetInput): ApplicationDocumentationChapterSet {
|
|
150
156
|
return ApplicationDocumentationChapterSetSchema.parse(chapters);
|
|
151
157
|
}
|
|
158
|
+
|
|
159
|
+
/**
|
|
160
|
+
* Where a chapter's own file lives, relative to the specifications package's `src/`: one file per chapter, named by
|
|
161
|
+
* its `chapterRef` (#3204).
|
|
162
|
+
*/
|
|
163
|
+
export const APPLICATION_DOCUMENTATION_CHAPTER_FILES_DIRECTORY = 'technical-documentation/chapters';
|
|
164
|
+
/** The export a chapter file declares its chapter under. */
|
|
165
|
+
export const APPLICATION_DOCUMENTATION_CHAPTER_FILE_EXPORT = 'documentationChapter';
|
|
166
|
+
|
|
167
|
+
/** One chapter, as its own file declares it: the ref it is the body of, and the body. */
|
|
168
|
+
export interface ApplicationDocumentationChapterDeclaration {
|
|
169
|
+
readonly chapterRef: string;
|
|
170
|
+
readonly chapter: ApplicationDocumentationChapterSource;
|
|
171
|
+
}
|
|
172
|
+
|
|
173
|
+
/**
|
|
174
|
+
* Declares ONE chapter, in its own file `technical-documentation/chapters/<chapterRef>.ts` (#3204): the ref's shape, the
|
|
175
|
+
* body rules, and a chapter relating to itself are checked when the file is evaluated. Nothing imports a chapter file, so
|
|
176
|
+
* the specifications package's own load never evaluates it: a build task writing one evaluates it in its
|
|
177
|
+
* `check:specification-exports` verification, and publication evaluates every file before it merges them. Whether a
|
|
178
|
+
* related chapter EXISTS is a question about the whole set, answered by that merge, since sibling chapters are written at
|
|
179
|
+
* the same time. A chapter file imports only `@wildo-ai/*` packages.
|
|
180
|
+
*/
|
|
181
|
+
export function defineApplicationDocumentationChapter(chapterRef: string, chapter: ApplicationDocumentationChapterSourceInput): ApplicationDocumentationChapterDeclaration {
|
|
182
|
+
const ref = ApplicationDocumentationChapterRefSchema.parse(chapterRef);
|
|
183
|
+
const parsed = ApplicationDocumentationChapterSourceSchema.parse(chapter);
|
|
184
|
+
if (parsed.relatedChapterRefs.includes(ref)) throw new Error(`${ref} cannot relate to itself`);
|
|
185
|
+
return { chapterRef: ref, chapter: parsed };
|
|
186
|
+
}
|
|
152
187
|
```
|
|
@@ -20,8 +20,8 @@
|
|
|
20
20
|
* existed, and an authored cross-resource guide had no accepted input into managed publication.
|
|
21
21
|
* This family is half of that input: a specification
|
|
22
22
|
* FILE in the application's own package, accepted by being committed, that owns each chapter's
|
|
23
|
-
* IDENTITY — ref, title, kind, audiences. The other half is the chapter BODY, authored in
|
|
24
|
-
* `specifications/src/technical-documentation/
|
|
23
|
+
* IDENTITY — ref, title, kind, audiences. The other half is the chapter BODY, authored in its own file
|
|
24
|
+
* `specifications/src/technical-documentation/chapters/<chapterRef>.ts` (`application-documentation-chapters.schemas.ts`)
|
|
25
25
|
* and joined to this plan by `chapterRef`; the publication withholds, and reports, a body no chapter
|
|
26
26
|
* here declares.
|
|
27
27
|
*
|
|
@@ -64,7 +64,12 @@ export enum ApplicationMaturityVersion {
|
|
|
64
64
|
* - `BUILT` — a BUILD TASK that links to it has landed, judged by the landing probe over committed
|
|
65
65
|
* bytes rather than by any status somebody wrote down.
|
|
66
66
|
* - `VERIFIED` — that landed task's declared product was PROVEN: the probe found what the task said
|
|
67
|
-
* it would produce. A task that landed and could not be proven stops at `BUILT`, deliberately.
|
|
67
|
+
* it would produce. A task that landed and could not be proven stops at `BUILT`, deliberately. So
|
|
68
|
+
* does a requirement a coding run still REPORTS unmet (#2580): a proven product is not a met
|
|
69
|
+
* requirement while the run that built it says what is missing, so an open gap caps the row at
|
|
70
|
+
* `BUILT` until its follow-up lands (see `openGaps` on the row).
|
|
71
|
+
* And so does one the application's CONFIGURATION does not meet (#3702): a capability it needs that is not
|
|
72
|
+
* enabled, a language it names that is not served (see `configurationGaps` on the row).
|
|
68
73
|
* - `OBSERVED` — something watched the running application do it: a browser drive, a served page, a
|
|
69
74
|
* boot. The strongest evidence this framework can produce, and see
|
|
70
75
|
* {@link ApplicationMaturityFindingCode.NO_RUNTIME_OBSERVATION_SOURCE} for what supplies it.
|
|
@@ -197,6 +202,54 @@ export function resolveApplicationMaturityStage(reading: Pick<ApplicationMaturit
|
|
|
197
202
|
return stage;
|
|
198
203
|
}
|
|
199
204
|
|
|
205
|
+
/**
|
|
206
|
+
* A gap a completed coding run REPORTED on a requirement it served, still open (#2580): no follow-up has landed for it,
|
|
207
|
+
* or the follow-up's own run reports it still. A run states such a gap in its `wildo-requirements-unmet` block, and the
|
|
208
|
+
* build host derives the follow-up task that answers it (#2496). Read from the runs' records, never from prose.
|
|
209
|
+
*/
|
|
210
|
+
export const RequirementOpenGapSchema = z.strictObject({
|
|
211
|
+
/** The task whose latest completed run reported the gap: a build task, or a follow-up still reporting it. */
|
|
212
|
+
originTaskRef: nonEmptyString(),
|
|
213
|
+
/** What the run said is missing, in its own words. */
|
|
214
|
+
missing: nonEmptyString(),
|
|
215
|
+
/** The follow-up task derived to answer it, not landed yet. Absent when none can be derived or this IS the follow-up's report. */
|
|
216
|
+
followUpTaskRef: nonEmptyString().optional(),
|
|
217
|
+
});
|
|
218
|
+
export type RequirementOpenGap = z.infer<typeof RequirementOpenGapSchema>;
|
|
219
|
+
|
|
220
|
+
/**
|
|
221
|
+
* Why the application's CONFIGURATION does not meet a requirement (#3702). TOTAL over what a requirement can declare it
|
|
222
|
+
* needs from the configuration (`engineCapabilities`, `languages`), plus the one state in which nothing can be compared.
|
|
223
|
+
*/
|
|
224
|
+
export enum RequirementConfigurationGapKind {
|
|
225
|
+
/** The requirement needs an engine capability the application's configuration does not enable. */
|
|
226
|
+
ENGINE_CAPABILITY_NOT_ENABLED = 'ENGINE_CAPABILITY_NOT_ENABLED',
|
|
227
|
+
/** The requirement names a language the application does not serve (`appPreferences.languages`). */
|
|
228
|
+
LANGUAGE_NOT_SERVED = 'LANGUAGE_NOT_SERVED',
|
|
229
|
+
/**
|
|
230
|
+
* The requirement declares what it needs from the configuration, and the configuration could not be read: an unknown
|
|
231
|
+
* is not a met requirement, so the row stops below VERIFIED rather than read as proven.
|
|
232
|
+
*/
|
|
233
|
+
CONFIGURATION_NOT_READ = 'CONFIGURATION_NOT_READ',
|
|
234
|
+
}
|
|
235
|
+
|
|
236
|
+
/**
|
|
237
|
+
* One thing the application's configuration does not turn on that a requirement declares it cannot be met without
|
|
238
|
+
* (#3702). Measured, never reported by anyone: the requirement's typed `engineCapabilities` / `languages` against the
|
|
239
|
+
* capabilities the configuration enables and the languages it serves. Any one caps the row at `BUILT`, like an open
|
|
240
|
+
* reported gap: a build task's product existing proves nothing about a switch that is off. Measured on the reference
|
|
241
|
+
* run (2026-11-10): the languages requirement read VERIFIED, proven by a page a task wrote, while the application had
|
|
242
|
+
* `MULTI_LANGUAGE` disabled and served English alone.
|
|
243
|
+
*/
|
|
244
|
+
export const RequirementConfigurationGapSchema = z.strictObject({
|
|
245
|
+
kind: z.enum(RequirementConfigurationGapKind).systemEnum('RequirementConfigurationGapKind'),
|
|
246
|
+
/** The capability or language that is missing, as its vocabulary spells it; the configuration file when it is unread. */
|
|
247
|
+
value: nonEmptyString(),
|
|
248
|
+
/** Where the application declares it, so the gap is a named field to set rather than a question. */
|
|
249
|
+
declaredIn: nonEmptyString(),
|
|
250
|
+
});
|
|
251
|
+
export type RequirementConfigurationGap = z.infer<typeof RequirementConfigurationGapSchema>;
|
|
252
|
+
|
|
200
253
|
/** One requirement, and what exists for it. */
|
|
201
254
|
export const RequirementMaturityRowSchema = z.strictObject({
|
|
202
255
|
/** The `requirements` family's own ref — the join, and the reason nothing here restates a statement. */
|
|
@@ -219,6 +272,16 @@ export const RequirementMaturityRowSchema = z.strictObject({
|
|
|
219
272
|
provenTaskRefs: z.array(nonEmptyString()).default([]),
|
|
220
273
|
/** Runtime observations naming this requirement, by their own refs. */
|
|
221
274
|
observationRefs: z.array(nonEmptyString()).default([]),
|
|
275
|
+
/**
|
|
276
|
+
* The gaps coding runs reported on this requirement that are still open (#2580). Any one caps the level at `BUILT`:
|
|
277
|
+
* a requirement whose builder says it is partly unmet is not proven, whatever the probe found.
|
|
278
|
+
*/
|
|
279
|
+
openGaps: z.array(RequirementOpenGapSchema).default([]),
|
|
280
|
+
/**
|
|
281
|
+
* What the application's configuration does not turn on that the requirement declares it needs (#3702). Any one caps
|
|
282
|
+
* the level at `BUILT`, as an open reported gap does.
|
|
283
|
+
*/
|
|
284
|
+
configurationGaps: z.array(RequirementConfigurationGapSchema).default([]),
|
|
222
285
|
});
|
|
223
286
|
export type RequirementMaturityRow = z.infer<typeof RequirementMaturityRowSchema>;
|
|
224
287
|
|
|
@@ -266,6 +329,12 @@ export const ApplicationMaturitySchema = z.object({
|
|
|
266
329
|
context.addIssue({ code: 'custom', message: `task ${provenTaskRef} is proven for ${row.requirementRef} without being landed`, path: ['requirements', index, 'provenTaskRefs'] });
|
|
267
330
|
}
|
|
268
331
|
}
|
|
332
|
+
if (row.openGaps.length > 0 && isEvidenceAtOrAbove(row.level, RequirementEvidenceLevel.VERIFIED)) {
|
|
333
|
+
context.addIssue({ code: 'custom', message: `${row.requirementRef} is ${row.level} while ${row.openGaps.length} reported gap(s) on it are open`, path: ['requirements', index, 'level'] });
|
|
334
|
+
}
|
|
335
|
+
if (row.configurationGaps.length > 0 && isEvidenceAtOrAbove(row.level, RequirementEvidenceLevel.VERIFIED)) {
|
|
336
|
+
context.addIssue({ code: 'custom', message: `${row.requirementRef} is ${row.level} while the configuration does not meet it (${row.configurationGaps.map((gap) => gap.value).join(', ')})`, path: ['requirements', index, 'level'] });
|
|
337
|
+
}
|
|
269
338
|
if (row.level === RequirementEvidenceLevel.UNADDRESSED && row.addressedByRefs.length > 0) {
|
|
270
339
|
context.addIssue({ code: 'custom', message: `${row.requirementRef} is UNADDRESSED and names ${row.addressedByRefs.length} element(s) addressing it`, path: ['requirements', index, 'level'] });
|
|
271
340
|
}
|
|
@@ -46,8 +46,10 @@ export interface InboundAdoptedAttachment {
|
|
|
46
46
|
* - **Recorded** — every adoption writes `inbound_attachment_adopted` on the organization's audit trail.
|
|
47
47
|
*
|
|
48
48
|
* What the copy MAY do is decided by your write, not here: `ctx.resources.create/update` authorizes the write with
|
|
49
|
-
* the handler's roles as for any caller, and links the copy then.
|
|
50
|
-
*
|
|
49
|
+
* the handler's roles as for any caller, and links the copy then. Only this delivery may name it, and a handler can name
|
|
50
|
+
* no other unlinked file: an id taken from a sender's payload that names someone's upload answers `NOT_FOUND` (#3330). A
|
|
51
|
+
* copy your handler never names (the write failed, or a retry found the record already filed) is swept a day later like
|
|
52
|
+
* any upload nobody attached.
|
|
51
53
|
*/
|
|
52
54
|
export interface InboundAttachmentOperations {
|
|
53
55
|
adopt(fileId: string, target: InboundAttachmentAdoptionTarget): Promise<InboundAdoptedAttachment>;
|
|
@@ -21,8 +21,9 @@ export interface InboundChannelSource<C extends InboundChannelKind = InboundChan
|
|
|
21
21
|
readonly kind: InboundSourceKind.CHANNEL;
|
|
22
22
|
readonly channel: C;
|
|
23
23
|
/**
|
|
24
|
-
* The tag routing names — for email, `tag` in `cases+tag@firm.example
|
|
25
|
-
*
|
|
24
|
+
* The tag routing names — for email, `tag` in `cases+tag@firm.example`; for SMS, the text's first word
|
|
25
|
+
* (`BOOKING tomorrow 9am` carries `booking`), since a text has no sub-address. Lower-case letters, digits
|
|
26
|
+
* and hyphens. An SMS text whose first word no handler claims goes to the default.
|
|
26
27
|
*/
|
|
27
28
|
readonly routeTag?: string;
|
|
28
29
|
/** Take every message no `routeTag` claims. */
|
|
@@ -31,11 +32,12 @@ export interface InboundChannelSource<C extends InboundChannelKind = InboundChan
|
|
|
31
32
|
|
|
32
33
|
/** Who sent a message, as far as the engine could establish. */
|
|
33
34
|
export interface InboundMessageSender<C extends InboundChannelKind = InboundChannelKind> {
|
|
35
|
+
/** The sender's address: an email address, or for SMS the sending number in E.164. */
|
|
34
36
|
readonly address: string;
|
|
35
37
|
readonly name?: string;
|
|
36
38
|
/** Identification, never authentication — see `InboundSenderAssurance`. It grants nothing. */
|
|
37
39
|
readonly assurance: SenderAssuranceOf<C>;
|
|
38
|
-
/** Set when the sender is a verified, active member of the routed organization. */
|
|
40
|
+
/** Set when the sender is a verified, active member of the routed organization (for SMS: by their verified phone number). */
|
|
39
41
|
readonly memberUserId?: string;
|
|
40
42
|
}
|
|
41
43
|
|
|
@@ -81,9 +83,21 @@ export interface InboundEmailPayload {
|
|
|
81
83
|
readonly routeTag?: string;
|
|
82
84
|
}
|
|
83
85
|
|
|
86
|
+
/**
|
|
87
|
+
* What an SMS handler receives about a text beyond its words (#3394). A text has no subject and no copy list: only the
|
|
88
|
+
* application number it was sent to, which is also the number a reply goes out from.
|
|
89
|
+
*/
|
|
90
|
+
export interface InboundSmsPayload {
|
|
91
|
+
/** The application's number the text was sent to, in E.164 — one the application assigned to the organization. */
|
|
92
|
+
readonly to: string;
|
|
93
|
+
/** The tag the text was routed on (its first word), when a handler claims it. */
|
|
94
|
+
readonly routeTag?: string;
|
|
95
|
+
}
|
|
96
|
+
|
|
84
97
|
/** The payload each channel carries — total over the channels a handler can be declared for. */
|
|
85
98
|
export interface InboundChannelPayloadByChannel {
|
|
86
99
|
[InboundChannelKind.EMAIL]: InboundEmailPayload;
|
|
100
|
+
[InboundChannelKind.SMS]: InboundSmsPayload;
|
|
87
101
|
}
|
|
88
102
|
|
|
89
103
|
/** A channel a handler may be declared for. `WEBHOOK` is the endpoint handlers' channel, never declared here. */
|
|
@@ -119,6 +133,9 @@ export interface InboundContactLookups {
|
|
|
119
133
|
* The application's answer to "is this address a contact of this organization?" (#1630 M6). The engine
|
|
120
134
|
* keeps no contacts: without a resolver, only members of the organization reach `KNOWN_CONTACT`. Asked
|
|
121
135
|
* only for a domain-aligned sender, and a resolver that throws counts as "no".
|
|
136
|
+
*
|
|
137
|
+
* SMS (#3394): `address` is the sending number in E.164, and the resolver is asked for every text that is
|
|
138
|
+
* not a member's verified number (SMS has no alignment to gate on, so the answer only ever identifies).
|
|
122
139
|
*/
|
|
123
140
|
export type InboundContactResolver = (input: {
|
|
124
141
|
readonly organizationId: string;
|
|
@@ -132,6 +149,29 @@ export interface InboundReplyRequest {
|
|
|
132
149
|
readonly templateRef: string;
|
|
133
150
|
/** Rendered into the template as `additionalContext`. Stored on the reply's message row until the reply's retention ends. */
|
|
134
151
|
readonly variables: Readonly<Record<string, unknown>>;
|
|
152
|
+
/**
|
|
153
|
+
* Files to send with the reply (#1856): a signed copy, a receipt, the document the sender asked for. Each must be a
|
|
154
|
+
* file the HANDLER can read with its own roles in the delivery's organization — a file on a record it can READ, or one
|
|
155
|
+
* this delivery produced itself — and is refused, with the file named, when the reply is queued otherwise. Never
|
|
156
|
+
* another organization's file, whatever the handler learned its id from. At most `CONVERSATION_REPLY_MAX_ATTACHMENTS`.
|
|
157
|
+
*/
|
|
158
|
+
readonly attachmentFileIds?: readonly string[];
|
|
159
|
+
}
|
|
160
|
+
|
|
161
|
+
/**
|
|
162
|
+
* What an SMS handler asks `ctx.reply` to send (#3394): the words of the reply. A text has no template; what it says
|
|
163
|
+
* is the handler's, at most `CONVERSATION_SMS_REPLY_MAX_LENGTH` characters (refused when queued, never cut). It goes
|
|
164
|
+
* out from the application number the text was sent to, only while the thread is open, and never to a number that
|
|
165
|
+
* replied STOP.
|
|
166
|
+
*/
|
|
167
|
+
export interface InboundSmsReplyRequest {
|
|
168
|
+
readonly text: string;
|
|
169
|
+
}
|
|
170
|
+
|
|
171
|
+
/** The reply request each channel takes — total over the channels a handler can be declared for. */
|
|
172
|
+
export interface InboundReplyRequestByChannel {
|
|
173
|
+
[InboundChannelKind.EMAIL]: InboundReplyRequest;
|
|
174
|
+
[InboundChannelKind.SMS]: InboundSmsReplyRequest;
|
|
135
175
|
}
|
|
136
176
|
|
|
137
177
|
/** The reply that was queued — one per call, idempotent per delivery and template (see `ctx.reply`). */
|
|
@@ -175,19 +215,20 @@ export type InboundChannelHandlerContextBase = Omit<InboundHandlerContext, 'deli
|
|
|
175
215
|
};
|
|
176
216
|
|
|
177
217
|
/**
|
|
178
|
-
* The context a handler of reply mode `M` receives. Under `THREAD` it can answer
|
|
179
|
-
* is `never`, so calling it does not compile.
|
|
218
|
+
* The context a handler of reply mode `M` on channel `C` receives. Under `THREAD` it can answer, with the
|
|
219
|
+
* channel's own reply request; under `NONE` `reply` is `never`, so calling it does not compile.
|
|
180
220
|
*/
|
|
181
|
-
export type InboundChannelHandlerContext<M extends InboundReplyMode> = InboundChannelHandlerContextBase & (
|
|
221
|
+
export type InboundChannelHandlerContext<M extends InboundReplyMode, C extends DeclarableInboundChannel = DeclarableInboundChannel> = InboundChannelHandlerContextBase & (
|
|
182
222
|
M extends InboundReplyMode.THREAD
|
|
183
223
|
? {
|
|
184
224
|
/**
|
|
185
225
|
* Answer on the thread the message arrived on, and only there (I7). Writes the reply as an OUTBOUND
|
|
186
|
-
* message and queues it; the reply worker sends it
|
|
187
|
-
* provider with the thread's headers
|
|
188
|
-
*
|
|
226
|
+
* message and queues it; the reply worker sends it on the thread's channel: for email through the
|
|
227
|
+
* application's transactional email provider with the thread's headers, for SMS through the SMS
|
|
228
|
+
* provider from the number the text was sent to. Calling it twice with the same template (or, for
|
|
229
|
+
* SMS, the same text) in one delivery queues ONE reply — a retried handler does not answer twice.
|
|
189
230
|
*/
|
|
190
|
-
readonly reply: (request:
|
|
231
|
+
readonly reply: (request: InboundReplyRequestByChannel[C]) => Promise<InboundQueuedReply>;
|
|
191
232
|
}
|
|
192
233
|
: { readonly reply?: never }
|
|
193
234
|
);
|
|
@@ -211,7 +252,7 @@ export interface InboundChannelHandlerDefinition<C extends DeclarableInboundChan
|
|
|
211
252
|
/** The handler's whole authority, in the routed organization. Never the super-administrator role. */
|
|
212
253
|
readonly actingRoles: { readonly organization: readonly string[] };
|
|
213
254
|
readonly retry?: InboundRetryPolicy;
|
|
214
|
-
handle(ctx: InboundChannelHandlerContext<M>, message: InboundMessage<C>): Promise<void>;
|
|
255
|
+
handle(ctx: InboundChannelHandlerContext<M, C>, message: InboundMessage<C>): Promise<void>;
|
|
215
256
|
}
|
|
216
257
|
|
|
217
258
|
/** Identity function that infers the channel and the reply mode, so `ctx.reply` is typed from the declaration. */
|
|
@@ -259,7 +259,17 @@ export type InboundChatActingMember = Extract<InboundChatMember, { readonly stan
|
|
|
259
259
|
* the decision notice's job (#2664 S5b), not the click's.
|
|
260
260
|
*/
|
|
261
261
|
export type InboundChatDecisionAnswer =
|
|
262
|
-
| {
|
|
262
|
+
| {
|
|
263
|
+
readonly member: InboundChatActingMember;
|
|
264
|
+
readonly outcome: HumanDecision_ActOutcome;
|
|
265
|
+
/**
|
|
266
|
+
* #2923: where the person answers this decision instead, when a chat answer cannot settle it (it requires a step-up,
|
|
267
|
+
* which a chat answer cannot carry, or its kind does not admit a chat answer): the decision's address in the
|
|
268
|
+
* application's inbox. Present exactly then, and when the application has a public address. A handler posts it as
|
|
269
|
+
* the message's link (`openInApplication`), never a refusal with nowhere to go.
|
|
270
|
+
*/
|
|
271
|
+
readonly openInApplicationUrl?: string;
|
|
272
|
+
}
|
|
263
273
|
| { readonly member: Exclude<InboundChatMember, InboundChatActingMember> };
|
|
264
274
|
|
|
265
275
|
/**
|
|
@@ -333,6 +343,16 @@ export enum ChatConverseRefusal {
|
|
|
333
343
|
BUSY_TOO_LONG = 'busy_too_long',
|
|
334
344
|
/** The message said nothing once the bot's mention was removed. */
|
|
335
345
|
EMPTY_MESSAGE = 'empty_message',
|
|
346
|
+
/**
|
|
347
|
+
* #2750: the message alone is larger than the chat agent's model can be sent, so it was refused rather than cut. Not
|
|
348
|
+
* kept; a shorter message is admitted.
|
|
349
|
+
*/
|
|
350
|
+
MESSAGE_TOO_LONG = 'message_too_long',
|
|
351
|
+
/**
|
|
352
|
+
* The chosen agent's system is open only to the roles it declares (`config.accessControl[].roles`), and the linked
|
|
353
|
+
* member holds none of them in the organization (#2544 follow-up). Not kept; an administrator can give them a role.
|
|
354
|
+
*/
|
|
355
|
+
SYSTEM_ROLE_NOT_HELD = 'system_role_not_held',
|
|
336
356
|
}
|
|
337
357
|
|
|
338
358
|
/** What a message waits for. */
|
|
@@ -615,6 +635,23 @@ export interface InboundHandlerDefinition<P = unknown> {
|
|
|
615
635
|
readonly dedupKey?: (delivery: VerifiedInboundDelivery) => string;
|
|
616
636
|
/** Deliveries sharing a non-null key run one at a time, in receive order. */
|
|
617
637
|
readonly orderingKey?: (delivery: VerifiedInboundDelivery, payload: P) => string | null;
|
|
638
|
+
/**
|
|
639
|
+
* The people this delivery's payload names (#1642): each person's email address, LOWER-CASED, or their user id in
|
|
640
|
+
* this application. Computed once, at receipt, from the parsed payload, and stored on the delivery (`subjectKeys`).
|
|
641
|
+
*
|
|
642
|
+
* Declare it whenever the payload can name a person (a contact, a signer, a customer). The stored body cannot be
|
|
643
|
+
* searched, so these keys are the only way the delivery is found for that person: when they are erased, every stored
|
|
644
|
+
* delivery whose keys hold their user id or their email address is DELETED inside the erasure, and an administrator
|
|
645
|
+
* finds the deliveries for a person through the SEARCH filter `subjectKeys`. A delivery that names someone and
|
|
646
|
+
* declares nothing keeps them in its payload until its retention period ends.
|
|
647
|
+
*
|
|
648
|
+
* The receiver trims each key and drops duplicates and empty ones. More than 20 keys, or a key longer than 320
|
|
649
|
+
* characters, cannot be stored: the delivery is refused as malformed, like a dedup key that cannot be stored.
|
|
650
|
+
*
|
|
651
|
+
* @example
|
|
652
|
+
* subjectKeys: (_delivery, payload) => [payload.contact.email.toLowerCase()],
|
|
653
|
+
*/
|
|
654
|
+
readonly subjectKeys?: (delivery: VerifiedInboundDelivery, payload: P) => readonly string[];
|
|
618
655
|
readonly scopeMode: InboundHandlerScopeMode;
|
|
619
656
|
/** Required for `ORGANIZATION_REQUIRED` and `RESOLVED_PER_DELIVERY`; refused for `APPLICATION`. */
|
|
620
657
|
readonly resolveScope?: (delivery: VerifiedInboundDelivery, payload: P, lookups: InboundScopeLookups) => Promise<InboundResolvedScope>;
|