@wildo-ai/framework-knowledge 1.1.4 → 1.1.5
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/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +227 -6
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts +19 -0
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js +47 -1
- package/dist/esm/framework-knowledge.loader.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/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
- 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 +1 -1
- 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 +125 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +177 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +213 -7
- 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 +326 -8
- 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 +5 -3
- 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 +21 -14
- 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 +57 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +63 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +132 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +179 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +67 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +76 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +5 -4
- 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 +10 -5
- 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 +67 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +82 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +25 -9
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +124 -7
- 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 +67 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +83 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +69 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +71 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -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 +1 -1
- 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 +71 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +88 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +97 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +156 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +115 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +152 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +188 -8
- 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 +167 -9
- 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 +171 -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 +146 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts +248 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js +248 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +157 -4
- 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 +172 -4
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +5 -4
- 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 +8 -7
- 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 +3 -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 +22 -3
- 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 +5 -3
- 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 +21 -12
- 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 +192 -27
- 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 +172 -33
- 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 +2 -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 +6 -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 +182 -5
- 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 +191 -5
- 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 +2 -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 +3 -2
- 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 +154 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +214 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +44 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +51 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -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 +2 -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 +2 -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 +6 -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 +2 -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 +2 -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 +2 -2
- 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 +7 -3
- 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 +32 -4
- 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 +27 -3
- 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 +2 -2
- 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 +4 -2
- 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 +199 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +227 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +5 -3
- 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 +18 -4
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +155 -4
- 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 +187 -4
- 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 +6 -5
- 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 +18 -17
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.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 -0
- package/dist/knowledge/manifest.json +9 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +75 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
- package/dist/knowledge/playbooks/bottom_up.build/method.md +79 -0
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +65 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +1122 -76
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +49 -13
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +671 -47
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -16
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +31 -35
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -16
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +95 -0
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +62 -0
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +80 -0
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +90 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +107 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +70 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +8 -8
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +14 -13
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +165 -0
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +74 -0
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +219 -140
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -22
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +138 -0
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +70 -0
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +87 -0
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +69 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +63 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +116 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +79 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +70 -0
- package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
- package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +68 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +873 -15
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +19 -12
- package/dist/knowledge/playbooks/refinement.document-facts/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.document-facts/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +186 -21
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -16
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +343 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +54 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +28 -11
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -17
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +8 -15
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +25 -49
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -17
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +101 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +209 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +68 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +42 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +39 -12
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +18 -66
- package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +43 -0
- package/dist/knowledge/playbooks/top_down.definition/method.md +103 -0
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +75 -0
- package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +48 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -44
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +43 -0
- package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +45 -0
- package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +247 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +71 -0
- 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/method.md +36 -69
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +12 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +11 -7
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -16
- package/dist/knowledge/playbooks/top_down.risk-register/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.risk-register/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +46 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +59 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +12 -5
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +15 -17
- package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +23 -14
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -17
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +13 -17
- package/dist/knowledge/references/acp.execution-profile.md +266 -0
- package/dist/knowledge/references/acp.host-configuration-inheritance.md +29 -0
- package/dist/knowledge/references/acp.permission-ceiling.md +105 -0
- package/dist/knowledge/references/acp.permission-escalation.md +37 -0
- package/dist/knowledge/references/application-documentation-chapters.config.md +152 -0
- package/dist/knowledge/references/application-documentation-plan.config.md +136 -0
- package/dist/knowledge/references/application-maturity.config.md +319 -0
- package/dist/knowledge/references/assertions.authored-metadata.config.md +1 -1
- package/dist/knowledge/references/assertions.specification.config.md +1 -1
- package/dist/knowledge/references/brand.asset.config.md +8 -16
- package/dist/knowledge/references/brand.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/brand.logo-direction.config.md +9 -7
- package/dist/knowledge/references/brand.snapshot.config.md +16 -2
- package/dist/knowledge/references/brand.snapshot.validation.md +0 -7
- package/dist/knowledge/references/build-plan.task-graph.config.md +581 -7
- package/dist/knowledge/references/business-model.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/business-model.pricing-plan.config.md +1 -1
- package/dist/knowledge/references/business-model.snapshot.validation.md +15 -0
- package/dist/knowledge/references/capability-composition.config.md +155 -0
- package/dist/knowledge/references/cli.market.utils.md +1 -0
- package/dist/knowledge/references/companion.technical-doc.service.md +453 -98
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +21 -0
- package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +20 -1
- package/dist/knowledge/references/engine.saas-technical-doc.config.md +8 -4
- package/dist/knowledge/references/engine.saas-website.config.md +22 -10
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +8 -12
- package/dist/knowledge/references/example.config.app-shell.full.md +42 -7
- package/dist/knowledge/references/example.config.backend.required-floors.md +4 -0
- package/dist/knowledge/references/example.config.design-system.full.md +3 -0
- package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +19 -7
- package/dist/knowledge/references/example.features.connected-feature.declaration.md +66 -0
- package/dist/knowledge/references/example.features.connected-feature.surface.md +42 -0
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +4 -3
- package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +6 -10
- package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
- package/dist/knowledge/references/example.infra.environment-config.local.md +88 -11
- package/dist/knowledge/references/example.milestones.module-definitions.md +73 -0
- package/dist/knowledge/references/example.minion.contained-tick.md +79 -0
- package/dist/knowledge/references/example.module.companion-exports.full.md +38 -3
- package/dist/knowledge/references/example.provider.backend-module-shape.md +31 -13
- package/dist/knowledge/references/example.provider.frontend-app.module.md +103 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +20 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +7 -3
- package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +30 -0
- package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +11 -0
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +3 -0
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +94 -10
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +79 -0
- package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
- package/dist/knowledge/references/example.worker.node-route.md +94 -0
- package/dist/knowledge/references/experience-plan.config.md +311 -0
- package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +132 -9
- package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +269 -0
- package/dist/knowledge/references/integration-plan.config.md +185 -0
- package/dist/knowledge/references/market.alternative.config.md +1 -1
- package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
- package/dist/knowledge/references/market.channel.config.md +3 -3
- package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
- package/dist/knowledge/references/market.gain.config.md +1 -1
- package/dist/knowledge/references/market.icp.config.md +2 -2
- package/dist/knowledge/references/market.job.config.md +1 -1
- package/dist/knowledge/references/market.message-template.config.md +2 -2
- package/dist/knowledge/references/market.objection.config.md +1 -1
- package/dist/knowledge/references/market.pain.config.md +1 -1
- package/dist/knowledge/references/market.persona.config.md +2 -2
- package/dist/knowledge/references/market.proof.config.md +1 -1
- package/dist/knowledge/references/market.snapshot.validation.md +15 -0
- package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
- package/dist/knowledge/references/market.trigger.config.md +1 -1
- package/dist/knowledge/references/minions.tick-contract.md +83 -0
- package/dist/knowledge/references/placement-plan.config.md +369 -0
- package/dist/knowledge/references/platform.config.application-database.md +5 -2
- package/dist/knowledge/references/platform.config.backing-services.md +0 -21
- package/dist/knowledge/references/platform.config.environment.deployment.md +206 -14
- package/dist/knowledge/references/platform.config.infra-provider-resolution.md +170 -0
- package/dist/knowledge/references/platform.config.infrastructure-host.md +87 -0
- package/dist/knowledge/references/platform.config.saas.md +261 -9
- package/dist/knowledge/references/presets.models.labelling.sections.md +14 -0
- package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
- package/dist/knowledge/references/requirements.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/requirements.snapshot.validation.md +15 -0
- package/dist/knowledge/references/roadmap.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/roadmap.snapshot.validation.md +15 -7
- package/dist/knowledge/references/saas.backend.a2a.token-budget.md +71 -0
- package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
- package/dist/knowledge/references/saas.backend.auth.federated-identity-provider-private-networks.md +62 -0
- package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +86 -0
- package/dist/knowledge/references/saas.backend.billing.catalog-sync-result.md +37 -0
- package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +24 -5
- package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +187 -0
- package/dist/knowledge/references/saas.backend.domain-module.md +25 -1
- package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +6 -0
- package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +22 -4
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +17 -4
- package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +84 -0
- package/dist/knowledge/references/saas.backend.health-readiness-contributor.md +73 -0
- package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +200 -0
- package/dist/knowledge/references/saas.backend.providers.operation-executor.md +51 -0
- package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +71 -0
- package/dist/knowledge/references/saas.backend.queue.worker-topology.md +39 -0
- package/dist/knowledge/references/saas.backend.system-access-service.md +51 -42
- package/dist/knowledge/references/saas.composition.scenario-apply.md +51 -0
- package/dist/knowledge/references/saas.config.content-security-policy.md +97 -0
- package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +91 -21
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +4 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +38 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +27 -27
- package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +65 -16
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +41 -11
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
- package/dist/knowledge/references/saas.frontend.billing-context.md +108 -0
- package/dist/knowledge/references/saas.frontend.brand-identity.md +38 -0
- package/dist/knowledge/references/saas.frontend.celebration-overlay-contract.md +41 -0
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
- package/dist/knowledge/references/saas.frontend.errors.user-facing-error-message.md +47 -0
- package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +7 -1
- package/dist/knowledge/references/saas.frontend.execution-view.definition.md +3 -3
- package/dist/knowledge/references/saas.frontend.flows-actors-view.md +7 -4
- package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +30 -48
- package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +24 -0
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
- package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
- package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +65 -0
- package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +127 -1
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +327 -11
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +198 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
- package/dist/knowledge/references/saas.market.generation-agent.md +26 -9
- package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
- package/dist/knowledge/references/saas.models.audit.trail-config.md +155 -0
- package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
- package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +82 -0
- package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +77 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +192 -0
- package/dist/knowledge/references/saas.models.config.registration.md +188 -0
- package/dist/knowledge/references/saas.models.config.tenant-teardown.md +81 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +173 -3
- package/dist/knowledge/references/saas.models.email.template-type.md +40 -0
- package/dist/knowledge/references/saas.models.engine-capabilities.md +85 -7
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +61 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +43 -4
- package/dist/knowledge/references/saas.models.features.definition-builders.md +162 -0
- package/dist/knowledge/references/saas.models.file-upload-grant.md +222 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +54 -5
- package/dist/knowledge/references/saas.models.governed-document-acceptance-mode.md +116 -0
- package/dist/knowledge/references/saas.models.guidance-flow.md +160 -0
- package/dist/knowledge/references/saas.models.http-api-binding.md +76 -110
- package/dist/knowledge/references/saas.models.milestone-celebration.md +69 -0
- package/dist/knowledge/references/saas.models.milestone-definition.md +209 -0
- package/dist/knowledge/references/saas.models.navigation.layout.md +2 -2
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +150 -0
- package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +70 -0
- package/dist/knowledge/references/saas.models.notifications.targets.md +138 -0
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +256 -0
- package/dist/knowledge/references/saas.models.onboarding-elements.md +375 -0
- package/dist/knowledge/references/saas.models.onboarding-trigger.md +52 -0
- package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +50 -0
- package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
- package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
- package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
- package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +8 -5
- package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +72 -0
- package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +50 -0
- package/dist/knowledge/references/saas.models.providers.capability-surface.md +58 -0
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +111 -0
- package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +156 -0
- package/dist/knowledge/references/saas.models.rate-limit-configuration.md +11 -1
- package/dist/knowledge/references/saas.models.relationship-handling-settings.md +23 -1
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -4
- package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +5 -4
- package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +69 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +15 -2
- package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +66 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-base.md +24 -1
- package/dist/knowledge/references/saas.models.resource-config.operation-cron-job.md +59 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +55 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +5 -4
- package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +158 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-step-up.md +77 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +6 -1
- package/dist/knowledge/references/saas.models.resource-config.queue-policy.md +49 -0
- package/dist/knowledge/references/saas.models.resource-config.required-features.md +84 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +10 -0
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +14 -0
- package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +111 -4
- package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +39 -0
- package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +48 -0
- package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +38 -0
- package/dist/knowledge/references/saas.models.resource-primary-scope.md +11 -2
- package/dist/knowledge/references/saas.models.scope-membership.md +3 -4
- package/dist/knowledge/references/saas.models.shared-saas-module.md +25 -0
- package/dist/knowledge/references/saas.models.systems-of-record.md +635 -0
- package/dist/knowledge/references/saas.public-runtime.contract.md +198 -1
- package/dist/knowledge/references/saas.rag.retrieval-result.md +19 -8
- package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +15 -36
- package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +9 -5
- package/dist/knowledge/references/saas.specifications.application-document-publication.generation.md +63 -0
- package/dist/knowledge/references/saas.specifications.application-document-release-set.contract.md +74 -0
- package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +123 -0
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +88 -7
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +774 -53
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +211 -14
- package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +364 -0
- package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
- package/dist/knowledge/references/saas.specifications.processor-register.md +333 -0
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +8 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
- package/dist/knowledge/references/saas.website.astro.bridge.md +64 -2
- package/dist/knowledge/references/saas.website.astro.head-renderer.md +32 -12
- package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -0
- package/dist/knowledge/references/saas.website.astro.robots-renderer.md +14 -1
- package/dist/knowledge/references/saas.website.blog.bridge.md +21 -1
- package/dist/knowledge/references/saas.website.consent.banner.md +218 -0
- package/dist/knowledge/references/saas.website.consent.context.md +162 -0
- package/dist/knowledge/references/saas.website.consent.gate.md +38 -0
- package/dist/knowledge/references/saas.website.page-layout.component.md +67 -1
- package/dist/knowledge/references/saas.website.page.context.md +4 -3
- package/dist/knowledge/references/saas.website.runtime.context.md +43 -7
- package/dist/knowledge/references/saas.website.section.context.md +3 -2
- package/dist/knowledge/references/saas.website.sections.category-enum.md +19 -20
- package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/website-plan.config.md +205 -0
- package/dist/knowledge/references/workers.node.worker-init-contract.md +57 -0
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +43 -2
- package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +51 -4
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +54 -1
- package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +35 -0
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +32 -5
- package/dist/knowledge/references/zod.decorators.file-nature-constraints.md +86 -0
- package/dist/knowledge/references/zod.decorators.file-readiness-metadata.md +67 -0
- package/dist/knowledge/references/zod.decorators.file-schema.md +90 -14
- package/dist/knowledge/references/zod.decorators.file-vocabularies.md +84 -0
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +140 -4
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
- package/dist/knowledge/references/zod.decorators.rag-source.md +6 -2
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +24 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +35 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +46 -12
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +31 -12
- package/dist/knowledge/references/zod.factories.address.md +118 -0
- package/dist/knowledge/references/zod.factories.code.md +2 -0
- package/dist/knowledge/references/zod.factories.duration.md +2 -0
- package/dist/knowledge/references/zod.factories.money.md +2 -0
- package/dist/knowledge/references/zod.factories.phone.md +14 -1
- package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
- package/dist/knowledge/registries/framework-topics.json +1215 -11
- package/dist/knowledge/registries/playbooks.json +454 -50
- package/dist/knowledge/registries/source-tags.json +3153 -1043
- package/dist/knowledge/rules/database-migration-obligation.md +110 -0
- package/dist/knowledge/rules/live-context-door.md +108 -0
- package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
- package/dist/knowledge/skills/INDEX.md +46 -11
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +80 -37
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +167 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +6 -3
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -3
- package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +5 -2
- package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +32 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +94 -3
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +50 -0
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +26 -19
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +25 -1
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +75 -12
- package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +137 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-error-user-guidance-api.md +112 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +72 -1
- package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +207 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +31 -1
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +8 -16
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +25 -9
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +135 -5
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +80 -17
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +369 -111
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +32 -10
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +103 -58
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +19 -13
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +142 -26
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +722 -23
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +348 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +123 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +74 -11
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +85 -19
- package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +70 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +43 -3
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
- package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
- package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +19 -10
- package/dist/knowledge/skills/config-navigation/SKILL.md +85 -2
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +2 -2
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +172 -0
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +146 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +86 -9
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +199 -0
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +179 -0
- package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +493 -0
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +153 -0
- package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +242 -0
- package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +161 -0
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +93 -12
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +785 -0
- package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +172 -0
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +261 -9
- package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +58 -3
- package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +151 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-auth-methods-api.md +579 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +8 -2
- package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +96 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +316 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-registration-config-api.md +221 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +121 -0
- package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
- package/dist/knowledge/skills/configure-billing/SKILL.md +27 -22
- package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +27 -15
- package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +41 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +36 -17
- package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +30 -28
- package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +169 -0
- package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +44 -11
- package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +187 -0
- package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +76 -0
- package/dist/knowledge/skills/configure-coding-agent/SKILL.md +280 -0
- package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +168 -0
- package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +504 -0
- package/dist/knowledge/skills/email-add-template/SKILL.md +41 -69
- package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +15 -7
- package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +120 -0
- package/dist/knowledge/skills/engine-component-registration/SKILL.md +19 -12
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +54 -31
- package/dist/knowledge/skills/engine-product-definitions/references/connected-feature-workflow.md +130 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +25 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-feature-builders-api.md +215 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +78 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +33 -24
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +121 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -8
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +5 -4
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +46 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +34 -7
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +151 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +6 -10
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +54 -5
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +75 -21
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +258 -0
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +480 -0
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +3983 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +211 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +165 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-elements-api.md +381 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-trigger-api.md +57 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-view-api.md +89 -0
- package/dist/knowledge/skills/i18n-label-generation/SKILL.md +13 -1
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +3 -1
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +237 -37
- package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +5 -2
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +174 -21
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +206 -14
- package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +95 -0
- package/dist/knowledge/skills/journey-approve/SKILL.md +28 -8
- package/dist/knowledge/skills/journey-approve/references/specification-family-map.md +88 -0
- package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +37 -2
- package/dist/knowledge/skills/journey-next/SKILL.md +41 -1
- package/dist/knowledge/skills/journey-report/SKILL.md +16 -3
- package/dist/knowledge/skills/journey-run/SKILL.md +92 -7
- package/dist/knowledge/skills/journey-run/references/expert-personas-and-deliberations.md +46 -0
- package/dist/knowledge/skills/journey-run/references/framework-playbook-approval-policy.md +108 -0
- package/dist/knowledge/skills/journey-status/SKILL.md +14 -4
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +153 -46
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +119 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +7 -4
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +253 -33
- package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +1 -1
- package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
- package/dist/knowledge/skills/market-alternatives/SKILL.md +1 -1
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
- package/dist/knowledge/skills/market-channels/SKILL.md +3 -3
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +226 -14
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +226 -14
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +56 -9
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +32 -9
- package/dist/knowledge/skills/market-icp/SKILL.md +2 -2
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +3 -3
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -2
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +17 -2
- package/dist/knowledge/skills/market-persona/SKILL.md +2 -2
- package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +2 -2
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -0
- package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +15 -0
- package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +1 -1
- package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +1 -1
- package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +198 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-celebration-overlay-contract.md +51 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-celebration-api.md +79 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-definition-api.md +220 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-progression-tracker-api.md +86 -0
- package/dist/knowledge/skills/minion-authoring/SKILL.md +140 -0
- package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +84 -0
- package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +91 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +38 -3
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +211 -14
- package/dist/knowledge/skills/module-registration/SKILL.md +50 -33
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +50 -1
- package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +142 -0
- package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
- package/dist/knowledge/skills/module-relationships/SKILL.md +62 -0
- package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +279 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +80 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +55 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +33 -6
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +99 -47
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +241 -9
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +196 -0
- package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +50 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +80 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +71 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +58 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +275 -0
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +64 -11
- package/dist/knowledge/skills/rate-limit-authoring/references/fixed-window-and-environment-multiplier.md +27 -0
- package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +19 -6
- package/dist/knowledge/skills/resource-add-field/SKILL.md +12 -5
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +373 -23
- package/dist/knowledge/skills/resource-add-module/SKILL.md +116 -265
- package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +133 -0
- package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +25 -0
- package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +12 -12
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +26 -3
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +122 -4
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +25 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +93 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +136 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +85 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +133 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +141 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-step-up-api.md +126 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +859 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +122 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +124 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +97 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +457 -15
- package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +197 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +162 -46
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +452 -0
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +5 -0
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +327 -11
- package/dist/knowledge/skills/resource-custom-view/references/framework-user-facing-error-message-api.md +50 -0
- package/dist/knowledge/skills/resource-external-data/SKILL.md +228 -15
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +54 -7
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +87 -113
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +13 -8
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +69 -26
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +246 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +7 -6
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +5 -3
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +43 -48
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +96 -14
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +47 -15
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +6 -2
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +32 -2
- package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +2 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +17 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +75 -4
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +182 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +35 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +46 -12
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +480 -15
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +67 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +74 -14
- package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +28 -5
- package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +25 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +34 -0
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +236 -18
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +54 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +35 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +327 -11
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +140 -4
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +155 -5
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +165 -0
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +9 -1
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
- package/dist/knowledge/skills/seeding-operations/SKILL.md +33 -29
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +13 -5
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +67 -74
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +97 -24
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +205 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +205 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +38 -3
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +211 -14
- package/dist/knowledge/skills/spec-component-update/SKILL.md +30 -11
- package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
- package/dist/knowledge/skills/spec-feature-update/SKILL.md +47 -9
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +3 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +32 -5
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +30 -0
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +1 -0
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +13 -2
- package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +24 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +1 -0
- package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +24 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +64 -0
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +3 -0
- package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +3 -3
- package/dist/knowledge/skills/views-execution-authoring/references/framework-user-facing-error-message-api.md +50 -0
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +43 -7
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +21 -1
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +21 -0
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +41 -1
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +735 -211
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +54 -7
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +67 -1
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -0
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +19 -5
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +94 -7
- package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
- package/dist/knowledge/skills/website-section-contact/SKILL.md +96 -146
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-cta/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-faq/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-hero/SKILL.md +37 -26
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +14 -1
- package/dist/knowledge/skills/worker-authoring/SKILL.md +164 -0
- package/dist/knowledge/skills/worker-authoring/examples/worker-route.example.md +98 -0
- package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +65 -0
- package/dist/knowledge/topic-index.json +5335 -1010
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/knowledge/references/example.provider.contribution.backend-billing.md +0 -12
- package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +0 -48
- /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
|
@@ -1,15 +1,15 @@
|
|
|
1
|
-
# Module Scaffold —
|
|
1
|
+
# Module Scaffold — Layout and Registration
|
|
2
2
|
|
|
3
|
-
|
|
4
|
-
align with existing modules in the same app.
|
|
3
|
+
Match the application's actual topology. The standard cross-package scaffold uses:
|
|
5
4
|
|
|
6
|
-
| Package |
|
|
7
|
-
|
|
8
|
-
| `shared-lib` |
|
|
9
|
-
| `
|
|
10
|
-
| `specifications` |
|
|
11
|
-
| `backend-api` |
|
|
5
|
+
| Package | Contribution | Registration |
|
|
6
|
+
|---|---|---|
|
|
7
|
+
| `shared-lib` | `src/modules/<module>/index.ts`, resources and enums | Default export imported into `src/modules-registry.shared.ts` → `applicationSharedModules`; public package export |
|
|
8
|
+
| `frontend` | `src/modules/<module>/index.ts`, UI behavior, views and app shell | Default `FrontendModule` imported into `src/modules/index.ts` → `applicationFrontendModules` |
|
|
9
|
+
| `specifications` | `src/modules/<module>/index.ts`, resource and view specifications | Named semantics export imported into `src/module-registry.specification.ts` → `applicationModuleBusinessSemantics`; public package export |
|
|
10
|
+
| `backend-api` | `src/modules/<module>/index.ts`, backend contribution and addons | Default `BackendOwnedModule` discovered by the existing immediate-directory scanner after compilation |
|
|
12
11
|
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
12
|
+
Declare the module's intended `services` in `wildo.saas.config.ts` as well. This declaration
|
|
13
|
+
supplies bootstrap topology; it does not insert identifiers into source registries.
|
|
14
|
+
Use `module-registration` for the canonical loader details. Omit layers that the chosen topology
|
|
15
|
+
does not need, and do not copy empty directories or invent a per-module label owner.
|
|
@@ -103,9 +103,12 @@ export const moduleResourcesConfigurationsFactoryMap: ResourceConfiguration_Init
|
|
|
103
103
|
[TasksManager_ResourceType.TEAM_GOALS]: teamGoals_ResourceConfiguration_InitializationFactory,
|
|
104
104
|
[TasksManager_ResourceType.ORGANIZATION_PARTNERSHIPS]: organizationPartnerships_ResourceConfiguration_InitializationFactory,
|
|
105
105
|
[TasksManager_ResourceType.ORGANIZATION_ESCALATION_CONTACTS]: organizationEscalationContacts_ResourceConfiguration_InitializationFactory,
|
|
106
|
+
[TasksManager_ResourceType.ORGANIZATION_ESCALATION_POLICIES]: organizationEscalationPolicies_ResourceConfiguration_InitializationFactory,
|
|
106
107
|
[TasksManager_ResourceType.EXTERNAL_CUSTOMERS]: externalCustomers_ResourceConfiguration_InitializationFactory,
|
|
108
|
+
[TasksManager_ResourceType.BILLABLE_SERVICES]: billableServices_ResourceConfiguration_InitializationFactory,
|
|
107
109
|
[TasksManager_ResourceType.ACCOUNT_ERASURE_REQUESTS]: accountErasureRequests_ResourceConfiguration_InitializationFactory,
|
|
108
110
|
[TasksManager_ResourceType.KNOWLEDGE_DOCUMENTS]: knowledgeDocuments_ResourceConfiguration_InitializationFactory,
|
|
111
|
+
[TasksManager_ResourceType.TODO_LIST_REMINDER_RULES]: todoListReminderRules_ResourceConfiguration_InitializationFactory,
|
|
109
112
|
}
|
|
110
113
|
```
|
|
111
114
|
|
|
@@ -130,6 +133,22 @@ and follow `resource-ui-behavior` — including a resource `icon` and an
|
|
|
130
133
|
`iconOverride` for every **custom** operation (custom ops have no default
|
|
131
134
|
action-button icon and otherwise render the placeholder).
|
|
132
135
|
|
|
136
|
+
Two declarations in that file are what make the resource REACHABLE, and a
|
|
137
|
+
scaffold that omits them compiles, registers, lists its rows through its parent
|
|
138
|
+
— and has no page of its own:
|
|
139
|
+
|
|
140
|
+
- **`views: [...]`** — one `[Op.X, { surface: ResourceOperationFrontendSurface.ADDRESSABLE }]`
|
|
141
|
+
entry per operation that gets a page. Without it there is no route for READ or
|
|
142
|
+
UPDATE (opening a row goes nowhere, a direct URL is a 404) and no Create button
|
|
143
|
+
in the list, because nothing declares that CREATE has a page to open.
|
|
144
|
+
- **`getFrontendResourceLabel`** — how one instance is named (`({ currentObject }) => currentObject.name`).
|
|
145
|
+
Without it the console reports `No getFrontendResourceLabel configured for "<resourceType>"`
|
|
146
|
+
and rows and breadcrumbs have nothing to call the record.
|
|
147
|
+
|
|
148
|
+
Both were missing when this skill was followed to add a resource to a live
|
|
149
|
+
application (2026-09-21); the list tab rendered, the rule rows rendered raw, and
|
|
150
|
+
every other surface was absent with no error except that console line.
|
|
151
|
+
|
|
133
152
|
### Step 5: Add specification and labels when the companion pipeline applies
|
|
134
153
|
|
|
135
154
|
When specifications exist for sibling resources, add
|
|
@@ -142,9 +161,10 @@ Add labels for user-visible fields and operations.
|
|
|
142
161
|
rg -n "applicationDatabase" infrastructure/*/wildo.infra.*.config.ts
|
|
143
162
|
```
|
|
144
163
|
|
|
145
|
-
|
|
146
|
-
|
|
147
|
-
|
|
164
|
+
`applicationDatabase: { engine: DatabaseEngine.MONGODB }` makes this step a
|
|
165
|
+
no-op — the collection appears on first write. PostgreSQL, whether declared or
|
|
166
|
+
selected because `applicationDatabase` is absent, means the new resource has
|
|
167
|
+
**no table until a migration creates one**, and the backend
|
|
148
168
|
will refuse to start with `postgresql_table_schema_mismatch`. Follow
|
|
149
169
|
`application-database-migrations`; the short form is `wildo db generate --name
|
|
150
170
|
add-<resource>`, then commit the migration folder together with
|
|
@@ -161,10 +181,13 @@ module barrel (`index.ts`) if siblings re-export theirs.
|
|
|
161
181
|
- `references/scaffold-surfaces-checklist.md` — surface checklist before "done"
|
|
162
182
|
- `references/framework-new-resource-core-config-api.md` — source-backed core operation / resource type / builder params
|
|
163
183
|
- `resource-config-wiring` → `references/framework-saas-models-resource-config-api.md` — typed config surface when authoring `resources-config`
|
|
184
|
+
- `resource-config-wiring` → `references/framework-personal-data-declaration-api.md` — **read once per new resource**: do its rows describe a person, and the four ways to answer
|
|
164
185
|
|
|
165
186
|
## Verification
|
|
166
187
|
|
|
188
|
+
- [ ] **The personal-data question is ANSWERED** — a `retentionPolicy` (`RETAIN_ONLY` says, checkably, that it holds none of its own), a `dataSubjectPolicy`, a `systemAccessPolicy.exportSubject`, or `.dataCategories()` on the fields that hold it. This is the cheapest moment; later means editing a shipped schema, and until it is answered the application's privacy notice can say nothing about this resource.
|
|
167
189
|
- [ ] New value added to the module's `<Module>_ResourceType` enum
|
|
190
|
+
- [ ] A user-facing resource's `ui-behavior` declares `views: [...]` (ADDRESSABLE per operation with a page) and `getFrontendResourceLabel` — without them it has no page and no Create button
|
|
168
191
|
- [ ] `<resource>.schemas.ts` exists and calls `initZodDecorators(z)` before schema definitions
|
|
169
192
|
- [ ] `<resource>.resources-config.ts` exists and matches the module's registration pattern
|
|
170
193
|
- [ ] **Module factory map (`<module>.resource-configs.ts`) includes a new entry keyed by the new enum value**
|
|
@@ -187,6 +187,101 @@ export enum ResourceSystemAccessMode {
|
|
|
187
187
|
* framework infrastructure does NOT imply that an ACL bypass is acceptable
|
|
188
188
|
* for its data. Keep the two concepts separate.
|
|
189
189
|
*/
|
|
190
|
+
/**
|
|
191
|
+
* Declares that THIS resource is the application's subject-erasure request lane, and how to read it.
|
|
192
|
+
*
|
|
193
|
+
* ## Why the application declares it rather than the framework knowing it
|
|
194
|
+
*
|
|
195
|
+
* The erasure lane is application-owned — four of the five marked sites for
|
|
196
|
+
* `WILDO.PRIVACY.SUBJECT_ERASURE` are in an application, not the engine — and its evidence demand
|
|
197
|
+
* (`evidence-requirement:subject-erasure-execution-record`) says so in terms: *"the row's schema and
|
|
198
|
+
* status vocabulary are the application's, so a collector queries it against that application's
|
|
199
|
+
* specification"*, and its verification step adds *"do NOT assert a specific channel vocabulary:
|
|
200
|
+
* that is one application's modelling choice"*.
|
|
201
|
+
*
|
|
202
|
+
* So a collector may not know that a request is raised through a field called `channel` carrying a
|
|
203
|
+
* value called `SUBJECT`. It has to be TOLD, by the application, in a form it can read. Before this
|
|
204
|
+
* existed, three clauses of that demand had a durable row holding every fact they wanted and no way
|
|
205
|
+
* to find it (#1209): not a missing control, a control nobody could point at.
|
|
206
|
+
*
|
|
207
|
+
* ## It binds FIELDS, never values the framework invents
|
|
208
|
+
*
|
|
209
|
+
* Every member below names something the application already authored. The one value the
|
|
210
|
+
* declaration carries — {@link ResourceSubjectErasureLane.raisedBy}`.subjectValue` — is the
|
|
211
|
+
* application's OWN enum member, quoted back so a reader can tell the two populations apart. The
|
|
212
|
+
* framework supplies no vocabulary here and must never grow one.
|
|
213
|
+
*
|
|
214
|
+
* ## What is deliberately NOT declared
|
|
215
|
+
*
|
|
216
|
+
* The SCHEDULE. C3 asks that requests be executed on the declared schedule, and that schedule is
|
|
217
|
+
* already on the executing operation's `CRON_JOB` variant (`cronExpression`) — declaring it again
|
|
218
|
+
* here would be a second copy that can only ever disagree with the one the scheduler reads.
|
|
219
|
+
* `executionOperationIdentifier` names the operation; the schedule is read from it.
|
|
220
|
+
*/
|
|
221
|
+
export type ResourceSubjectErasureLane = {
|
|
222
|
+
/**
|
|
223
|
+
* How a row says WHO raised the request — the subject exercising their own right, or the
|
|
224
|
+
* controller acting on their behalf. C1's whole obligation is that the two are distinguishable.
|
|
225
|
+
*/
|
|
226
|
+
raisedBy: {
|
|
227
|
+
/** The field carrying it. Must be a persisted field of this resource. */
|
|
228
|
+
fieldName: string,
|
|
229
|
+
/**
|
|
230
|
+
* The value of that field meaning the SUBJECT raised it themselves. Every other value is read as
|
|
231
|
+
* controller-raised — stated this way round because a lane may grow a second controller channel
|
|
232
|
+
* without the declaration going stale, whereas enumerating the controller values could not.
|
|
233
|
+
*/
|
|
234
|
+
subjectValue: string,
|
|
235
|
+
},
|
|
236
|
+
/**
|
|
237
|
+
* The field carrying WHICH user raised a controller-raised request.
|
|
238
|
+
*
|
|
239
|
+
* Omitting it is a positive claim, not a gap: it says this lane admits no controller-raised
|
|
240
|
+
* request at all. A collector reads it that way and a row carrying a non-subject value then
|
|
241
|
+
* contradicts the declaration, which is a finding about the application rather than about the
|
|
242
|
+
* evidence.
|
|
243
|
+
*/
|
|
244
|
+
requesterFieldName?: string,
|
|
245
|
+
/** The field carrying the justification a controller-raised request was made on, where the lane records one. */
|
|
246
|
+
justificationFieldName?: string,
|
|
247
|
+
/** The field carrying the instant the request was executed or failed. C3 judges execution against it. */
|
|
248
|
+
completedAtFieldName: string,
|
|
249
|
+
/** The field carrying what the execution did. Its vocabulary is the application's. */
|
|
250
|
+
outcomeFieldName: string,
|
|
251
|
+
/**
|
|
252
|
+
* The operation a SUBJECT uses to withdraw their own pending request (C2). Named rather than
|
|
253
|
+
* inferred: "the operation that cancels" is not derivable from an operation vocabulary, and
|
|
254
|
+
* guessing it would make the evidence depend on a naming convention no application agreed to.
|
|
255
|
+
*/
|
|
256
|
+
withdrawalOperationIdentifier: string,
|
|
257
|
+
/**
|
|
258
|
+
* How a WITHDRAWN row is recognisable afterwards — the same shape as {@link raisedBy}, and for the
|
|
259
|
+
* same reason: the vocabulary is the application's.
|
|
260
|
+
*
|
|
261
|
+
* C2 asks for the withdrawal door AND for "any cancelled rows", and those are two different
|
|
262
|
+
* questions. The door is answered from {@link withdrawalOperationIdentifier} — is the operation
|
|
263
|
+
* reachable to a subject while the request is pending — and needs no data at all. The rows need a
|
|
264
|
+
* marker, and there is nothing to derive one from: withdrawal and execution both leave a request in
|
|
265
|
+
* a terminal state, so a reader that knows only `completedAtFieldName` cannot tell "the subject
|
|
266
|
+
* changed their mind" from "the sweep ran".
|
|
267
|
+
*
|
|
268
|
+
* OPTIONAL, because an application may not model withdrawal as a value at all — it may delete the
|
|
269
|
+
* row, or move it. Omitting it says the count is unavailable, and a collector reports that rather
|
|
270
|
+
* than guessing; it never turns into a zero, which would read as "nobody withdrew anything".
|
|
271
|
+
*
|
|
272
|
+
* Note an EMPTY withdrawal set is explicitly not a deficiency in the demand — people do not have
|
|
273
|
+
* to change their minds — so this exists to make the number REPORTABLE, never to make it a target.
|
|
274
|
+
*/
|
|
275
|
+
withdrawnMarker?: {
|
|
276
|
+
/** The field carrying it. Must be a persisted field of this resource. */
|
|
277
|
+
fieldName: string,
|
|
278
|
+
/** The value of that field meaning the SUBJECT withdrew the request before it executed. */
|
|
279
|
+
withdrawnValue: string,
|
|
280
|
+
},
|
|
281
|
+
/** The scheduled operation that executes due requests. Its `cronExpression` IS the declared schedule. */
|
|
282
|
+
executionOperationIdentifier: string,
|
|
283
|
+
};
|
|
284
|
+
|
|
190
285
|
export type ResourceSystemAccessPolicy = {
|
|
191
286
|
/** Governs `readAsSystem`. Omitted ⇒ FORBIDDEN. */
|
|
192
287
|
read?: ResourceSystemAccessMode,
|
|
@@ -210,10 +305,22 @@ export type ResourceSystemAccessPolicy = {
|
|
|
210
305
|
* Auto-derived to `ALLOWED` by the factory when a resource opts into
|
|
211
306
|
* `retentionPolicy`; never authored by hand in the common case.
|
|
212
307
|
*
|
|
213
|
-
* **LIVE.** `readRetainedAsSystem` / `listRetainedAsSystem` exist and are enforced:
|
|
214
|
-
* asserted fail-closed, a privileged human role is required, and every reveal emits a
|
|
215
|
-
* human-attributed `RETAINED_DATA_ACCESS` audit event.
|
|
216
|
-
*
|
|
308
|
+
* **LIVE, and REACHABLE.** `readRetainedAsSystem` / `listRetainedAsSystem` exist and are enforced:
|
|
309
|
+
* the verb is asserted fail-closed, a privileged human role is required, and every reveal emits a
|
|
310
|
+
* human-attributed `RETAINED_DATA_ACCESS` audit event.
|
|
311
|
+
*
|
|
312
|
+
* "Reachable" is the half that was missing until #490, and the distinction is worth keeping. The
|
|
313
|
+
* primitives were correct and enforced from the day M5b landed — and had **no caller**, so the only
|
|
314
|
+
* route an operator actually had to a retained record was a database console: the unaudited path
|
|
315
|
+
* they were built to replace. `users | read_retained` is the operator surface that closes it, an
|
|
316
|
+
* authenticated `APP_ADMIN_SUPER_ADMIN` operation carrying a mandatory justification.
|
|
317
|
+
*
|
|
318
|
+
* A resource that derives this grant and exposes no such operation is reachable by nothing. That
|
|
319
|
+
* is a defensible state — not every retention resource needs an operator door — but it should be a
|
|
320
|
+
* decision rather than an oversight, and `retained-see-through-operator-surface.test.ts` is what
|
|
321
|
+
* makes it one.
|
|
322
|
+
*
|
|
323
|
+
* (This block previously said the primitives were "wired in a later phase" — false since M5b.)
|
|
217
324
|
*/
|
|
218
325
|
seeRetained?: ResourceSystemAccessMode,
|
|
219
326
|
|
|
@@ -417,6 +524,9 @@ export type ResourceConfiguration_BuilderParameters<
|
|
|
417
524
|
*/
|
|
418
525
|
httpApiBinding?: HttpApiResourceBindingAuthored,
|
|
419
526
|
|
|
527
|
+
/** REQUIRED when `persistenceAdapter` is INTROSPECTION; meaningless otherwise. */
|
|
528
|
+
introspectionBinding?: IntrospectionResourceBinding,
|
|
529
|
+
|
|
420
530
|
/**
|
|
421
531
|
* OPTIONAL inbound ETL pipeline on an ordinary LOCAL resource — "some resources local, some
|
|
422
532
|
* remote, ETL between them" (partial-resource coverage, model v3; PR-3). FORBIDDEN on an
|
|
@@ -475,6 +585,14 @@ export type ResourceConfiguration_BuilderParameters<
|
|
|
475
585
|
* explicit alternative authorization.
|
|
476
586
|
*/
|
|
477
587
|
systemAccessPolicy?: ResourceSystemAccessPolicy,
|
|
588
|
+
|
|
589
|
+
/**
|
|
590
|
+
* Declares this resource as the application's SUBJECT-ERASURE REQUEST LANE and binds the fields an
|
|
591
|
+
* evidence collector reads. Omitted ⇒ this resource is not that lane, which is the honest default:
|
|
592
|
+
* most resources are not, and an application that never built an erasure lane has declared none
|
|
593
|
+
* rather than failed a control. See {@link ResourceSubjectErasureLane}.
|
|
594
|
+
*/
|
|
595
|
+
subjectErasureLane?: ResourceSubjectErasureLane,
|
|
478
596
|
coreOperations: TCoreOperationEnum[],
|
|
479
597
|
customOperation?: TCustomOperationEnum, // default undefined
|
|
480
598
|
operationsConfiguration : { [K in ValidOperationKeys<TCustomOperationEnum, TCoreOperationEnum>]: OperationConfig_ForKey<K, TMainSchema> }
|
|
@@ -102,6 +102,17 @@ sending its email, or send an email without a usable token. Delivery is
|
|
|
102
102
|
best-effort—author an explicit product recovery operation such as RESEND when a
|
|
103
103
|
missing email must be recoverable.
|
|
104
104
|
|
|
105
|
+
For a variant whose synchronous round trip legitimately outlives the frontend's
|
|
106
|
+
30-second HTTP default — an operation that calls a model and waits, a blocking
|
|
107
|
+
generation, a long import — declare `clientRequestTimeoutMs` on that variant.
|
|
108
|
+
The frontend applies it as the per-request timeout on every dispatch shape.
|
|
109
|
+
Without it the request is aborted client-side while the server work succeeds:
|
|
110
|
+
the caller renders a network error and the operation-success refresh chain never
|
|
111
|
+
fires, so lists keep showing the pre-operation world. Do not hard-code timeouts
|
|
112
|
+
in consumer hooks instead — the variant is where the operation's own knowledge
|
|
113
|
+
of its duration belongs. Contract and a worked example:
|
|
114
|
+
`references/framework-saas-models-resource-config-api.md`.
|
|
115
|
+
|
|
105
116
|
### Step 5: Align with UI and spec
|
|
106
117
|
|
|
107
118
|
After config changes, `resource-ui-behavior` may need operation view updates;
|
|
@@ -292,14 +303,27 @@ fields (derived from the schema, never caller-supplied). Distinct from `isSystem
|
|
|
292
303
|
- `references/framework-saas-models-resource-config-api.md` — source-backed `resources-config` / registry types, including transactional token generation, relational `searchableFields`, and `forwardedLabel`
|
|
293
304
|
- `references/framework-saas-models-operation-scope-enums-api.md` — source-backed operation & scope enums
|
|
294
305
|
- `references/framework-system-access-reads-api.md` — source-backed `systemAccessPolicy` opt-in + the `SystemAccessBackendService` read AND trusted-write API (ACL-bypassing system-context reads + writes)
|
|
306
|
+
- `references/framework-role-ceiling-api.md` — **read if your resource has a caller-settable `roles` field**: wiring the grant ceiling, and why it takes the roles as the caller authored them
|
|
307
|
+
- `references/framework-administrative-continuity-codes-api.md` — the two 409 codes a last-administrator refusal carries, what actually counts as an administrator, and the two cases where the obvious remedy does not work
|
|
308
|
+
- `references/framework-scope-admissions-api.md` — the two per-variant admissions that relax whose row an operation may address, why each is on the variant rather than the resource, and why a crossing gets its own narrow verb
|
|
309
|
+
- `references/framework-user-notifications-api.md` — `userNotifications` on an operation: which channels actually send, how recipient preferences override, and why `condition` gates the message and not the call
|
|
310
|
+
- `references/framework-operation-audit-api.md` — what an operation leaves in the audit trail: the risk-driven baseline, `auditBelowRiskFloor`, and the three things the trail will not tell you
|
|
311
|
+
- `references/framework-authority-audit-interpretation.md` — membership and unit authority events, support-grant correlation, scoped queries, and the difference between actor, affected member and retained evidence
|
|
312
|
+
- `references/framework-required-features-api.md` — source-backed `requiredFeatures`: presence checks vs usage `limitChecks`, and why the SCREEN gate is not the security boundary
|
|
313
|
+
- `references/framework-collection-operation-declarations.md` — what a LIST/SEARCH variant declares (`filterFields`, `sortFields`, `isSearchable`, `maxPaginatedResultPerPageLimit`, `collectionExport`) and what each ABSENCE means — including why omitting `sortFields` is not "no sorting"
|
|
314
|
+
- `references/framework-operation-step-up-api.md` — source-backed `requiresStepUpAuthentication`: gating an irreversible operation behind a fresh proof of identity, why it is per-variant, and the read-shaped operations where it silently enforces nothing
|
|
315
|
+
- `references/framework-operation-idempotency-key-api.md` — source-backed `idempotencyKey`: making a provider-backed mutation safe to retry, `ACCEPTED` vs `REQUIRED`, and the half of the contract (remember, replay, refuse reuse) your implementation still owns
|
|
316
|
+
- `references/framework-personal-data-declaration-api.md` — **read once per resource**: does it hold data about a person, and the four ways to answer (including the checked way to say "no")
|
|
295
317
|
|
|
296
318
|
## Verification
|
|
297
319
|
|
|
320
|
+
- [ ] The resource has ANSWERED the personal-data question — a `retentionPolicy` (`RETAIN_ONLY` is the checked way to say it holds none of its own), a `dataSubjectPolicy`, a `systemAccessPolicy.exportSubject`, or a `.dataCategories()` declaration on the fields that hold it. Startup warns by name for every application resource that has said nothing.
|
|
298
321
|
- [ ] Every FK in the schema has a matching `createResourcesRelationship(...)` entry in the module relationships file
|
|
299
322
|
- [ ] Every relationship that resolves to multiple FKs to the same parent type sets `foreignKeyField` explicitly
|
|
300
323
|
- [ ] Operations referenced from `*.ui-behavior.tsx` exist in `*.resources-config.ts`
|
|
301
324
|
- [ ] Variants and discriminator wiring stays consistent with `createSchemaFamily` usage on the schema
|
|
302
325
|
- [ ] Role constraints (`roles: [...]`) match the product intent for each variant
|
|
326
|
+
- [ ] Any variant whose synchronous work can outlive ~30s declares `clientRequestTimeoutMs` (catch with the timeout grep below)
|
|
303
327
|
- [ ] `accessScopeStrategy` is set on every `REFERENCE` relationship (no implicit defaults relied upon)
|
|
304
328
|
- [ ] `contextPolicy` overrides for `LIST`/`SEARCH` are explicit when the relationship is high-cardinality
|
|
305
329
|
- [ ] Every relational `searchableFields` entry uses a `localField` that exists on this schema (and a `relatedJoinField` that exists on the related resource — defaults to `_id`)
|
|
@@ -317,6 +341,7 @@ Run from the app root and substitute the resource / FK field name:
|
|
|
317
341
|
| Relationship is co-located in the module-level relationships file (not inside config) | `rg -n "createResourcesRelationship" shared-lib/src/modules/*/resources/<resource>/<resource>.resources-config.ts` |
|
|
318
342
|
| Custom operation IDs in the UI exist in the resource config | `rg -n "operationLike:\\s*<Resource>_Operations\\." frontend/src/modules/*/resources/<resource>/<resource>.ui-behavior.tsx` |
|
|
319
343
|
| Same custom operation IDs are defined in the resource config | `rg -n "<Resource>_Operations\\." shared-lib/src/modules/*/resources/<resource>/<resource>.resources-config.ts` |
|
|
344
|
+
| Long-running variants declare their client timeout | `rg -n "clientRequestTimeoutMs" shared-lib/src/modules/*/resources/<resource>/<resource>.resources-config.ts` (expect a hit for any variant that generates/imports synchronously) |
|
|
320
345
|
| The two custom-operation lists agree | `comm -23 <(rg -oN "<Resource>_Operations\\.[A-Z_]+" frontend/src/modules/*/resources/<resource>/*.tsx \\| sort -u) <(rg -oN "<Resource>_Operations\\.[A-Z_]+" shared-lib/src/modules/*/resources/<resource>/*.ts \\| sort -u)` |
|
|
321
346
|
|
|
322
347
|
The third grep MUST return zero matches — relationship declarations in
|
|
@@ -0,0 +1,93 @@
|
|
|
1
|
+
# Administrative-continuity refusal codes
|
|
2
|
+
|
|
3
|
+
The stable, client-branchable identity of a **409 CONFLICT** raised because the write would remove
|
|
4
|
+
the last administrator a scope has.
|
|
5
|
+
|
|
6
|
+
Read this when:
|
|
7
|
+
|
|
8
|
+
- you are wiring an operation that can remove, demote, deactivate or erase an administrator — a
|
|
9
|
+
membership update or delete, a user suspension, a subject erasure;
|
|
10
|
+
- a client needs to tell "you would strip the last administrator" apart from any other conflict;
|
|
11
|
+
- the documented remedy — appoint another administrator, then retry — was followed and the refusal
|
|
12
|
+
came back anyway.
|
|
13
|
+
|
|
14
|
+
## Import Origins
|
|
15
|
+
|
|
16
|
+
- `@wildo-ai/saas-models`
|
|
17
|
+
|
|
18
|
+
## Source Excerpts
|
|
19
|
+
|
|
20
|
+
### Origin Package: `@wildo-ai/saas-models`
|
|
21
|
+
|
|
22
|
+
```typescript
|
|
23
|
+
/**
|
|
24
|
+
* Which administrative population a refusal was protecting.
|
|
25
|
+
*
|
|
26
|
+
* Imported from `@wildo-ai/saas-models`. A closed vocabulary with one named runtime source: schemas,
|
|
27
|
+
* comparisons and client branches all derive from this enum rather than re-typing the literals.
|
|
28
|
+
*
|
|
29
|
+
* ## Where you meet it
|
|
30
|
+
*
|
|
31
|
+
* A write that would strip the last accountable administrator is refused with HTTP **409 CONFLICT**,
|
|
32
|
+
* and this value rides under the response's stable `code` key. Branch on `code`, never on the
|
|
33
|
+
* message: the message is a human remedy and is free to be reworded, and every other field a backend
|
|
34
|
+
* might have used to carry the reason is stripped from a CONFLICT before it reaches a client.
|
|
35
|
+
*
|
|
36
|
+
* `409` and not `403`/`400` is deliberate and worth handling separately: the caller IS authorised and
|
|
37
|
+
* the payload IS valid. What forbids the write is the current state, so a generic "conflict, retry"
|
|
38
|
+
* branch loops forever — the remedy is to appoint another administrator at the named scope first.
|
|
39
|
+
*
|
|
40
|
+
* ## What counts as an administrator, when you are deciding whether the remedy will work
|
|
41
|
+
*
|
|
42
|
+
* Three conditions, all of which must hold, and each resolved toward the SMALLER count so an
|
|
43
|
+
* ambiguity produces an over-refusal (recoverable) rather than a lockout (not):
|
|
44
|
+
*
|
|
45
|
+
* 1. the roles must CONFER the anchor role — `APP_ADMIN_SUPER_ADMIN` at application scope,
|
|
46
|
+
* `ORG_OWNER` at organization scope — directly OR through an `inheritFrom` chain. The conferring
|
|
47
|
+
* set is resolved from your application's LIVE role table at the moment of the call, so a role you
|
|
48
|
+
* registered yourself that inherits from the anchor counts, and its holders are equally protected;
|
|
49
|
+
* 2. the membership must be `ACTIVE`. An `INVITED` row does not count even though accepting it would
|
|
50
|
+
* flip the same row — a recoverable administrator is not a usable one, and the invitee may never
|
|
51
|
+
* accept;
|
|
52
|
+
* 3. the linked user account must be `ACTIVE`. A suspended user cannot present the membership at all.
|
|
53
|
+
*
|
|
54
|
+
* ## Two traps
|
|
55
|
+
*
|
|
56
|
+
* **A UNIT-scoped grant does not satisfy the organization floor.** Granting the owner role inside one
|
|
57
|
+
* organization unit reaches that unit and nothing across the tenant, so the floor — which reads
|
|
58
|
+
* organization-wide membership roles and nothing else — refuses the retry exactly as before. Promote
|
|
59
|
+
* an organization-wide member instead.
|
|
60
|
+
*
|
|
61
|
+
* **Deactivating a user REPORTS rather than refuses.** Suspending an account is overwhelmingly
|
|
62
|
+
* incident response, and refusing it would mean an operator cannot lock out a hostile owner without
|
|
63
|
+
* first transferring ownership using the tenant the attacker controls. So the containment proceeds
|
|
64
|
+
* and every tenant it strands is recorded at critical severity — do not read this refusal as a
|
|
65
|
+
* guarantee that no suspension can leave a tenant ownerless.
|
|
66
|
+
*
|
|
67
|
+
* A tenant that is finished is exempt: a `CANCELLED` or `DELETED` organization, or one that has
|
|
68
|
+
* already requested deletion, may lose its last owner, so ordinary offboarding is never blocked.
|
|
69
|
+
*/
|
|
70
|
+
export enum AdministrativeContinuityErrorCode {
|
|
71
|
+
/**
|
|
72
|
+
* The write would leave the APPLICATION with no administratively usable super-administrator —
|
|
73
|
+
* a principal that confers `APP_ADMIN_SUPER_ADMIN` (directly or through an `inheritFrom` chain)
|
|
74
|
+
* and whose account status can still authenticate.
|
|
75
|
+
*
|
|
76
|
+
* Unrecoverable in-product once breached: every recovery door is itself gated on that role.
|
|
77
|
+
* Remedy: grant a super-administrator role to another active user, then retry.
|
|
78
|
+
*/
|
|
79
|
+
LAST_APPLICATION_SUPER_ADMIN = 'LAST_APPLICATION_SUPER_ADMIN',
|
|
80
|
+
|
|
81
|
+
/**
|
|
82
|
+
* The write would leave ONE organization with no administratively usable owner — an ACTIVE
|
|
83
|
+
* membership conferring `ORG_OWNER` (directly or by inheritance) whose linked user is also ACTIVE.
|
|
84
|
+
*
|
|
85
|
+
* Remedy before removing the last owner: grant an owner role to another active member, then retry.
|
|
86
|
+
* If external mutation or restored data already stranded the organization, the dedicated
|
|
87
|
+
* GRANT_OWNERSHIP operation provides a repair path to an eligible ACTIVE member with an ACTIVE
|
|
88
|
+
* linked user. A crossing platform administrator still needs its declared variant and a usable
|
|
89
|
+
* tenant-access grant; ownerless request auto-approval does not bypass the repair's checks.
|
|
90
|
+
*/
|
|
91
|
+
LAST_ORGANIZATION_OWNER = 'LAST_ORGANIZATION_OWNER',
|
|
92
|
+
}
|
|
93
|
+
```
|
|
@@ -0,0 +1,136 @@
|
|
|
1
|
+
# Interpret authority and support-access evidence
|
|
2
|
+
|
|
3
|
+
Read this when building an administrator investigation view, explaining who changed a member's
|
|
4
|
+
authority, or extending administrative operations. Keep the built-in lifecycle and its transaction
|
|
5
|
+
context; a custom `roles` field does not automatically inherit these specialized emitters.
|
|
6
|
+
|
|
7
|
+
## Identify which authority moved
|
|
8
|
+
|
|
9
|
+
| Built-in lifecycle | Evidence to interpret |
|
|
10
|
+
|---|---|
|
|
11
|
+
| Organization membership role change | `ORGANIZATION_MEMBER_ROLE_CHANGED` carries previous, resulting and requested role sets where supplied, plus the organization and membership. |
|
|
12
|
+
| Membership removal or invitation revocation | `ORGANIZATION_MEMBER_REMOVED` captures roles, previous status and revoked unit assignments before deletion removes that state. |
|
|
13
|
+
| Unit role assignment change | `ORGANIZATION_UNIT_MEMBER_ROLE_CHANGED` carries previous, new and requested **scalar** roles and the assignment/unit. It is narrower than organization-wide membership. |
|
|
14
|
+
| Unit assignment revocation | Its distinct removal event carries the revoked role; do not reconstruct that role from a row that has been deleted. |
|
|
15
|
+
| Ownership repair | Inspect `RESOURCE_OPERATION_PERFORMED` for the membership resource and `GRANT_OWNERSHIP`, including `fieldEvidence`. Do not expect a specialized role-change event's `requestedRoles` field here. |
|
|
16
|
+
|
|
17
|
+
The requested roles are what the caller authored; the resulting roles are what the operation stored.
|
|
18
|
+
Defaults and grant ceilings make that distinction meaningful. A unit assignment is one role in one
|
|
19
|
+
unit, not an organization-wide array with a different label.
|
|
20
|
+
|
|
21
|
+
The audit record's `userId` identifies the actor. The affected person and membership are separate
|
|
22
|
+
event data, such as `eventData.userId` and `eventData.memberId`; filtering by the record's `userId`
|
|
23
|
+
does not find every change **to** that person. For these authority events, `eventData.changedBy`
|
|
24
|
+
also describes the actor.
|
|
25
|
+
|
|
26
|
+
## Query first, then interpret the payload
|
|
27
|
+
|
|
28
|
+
Use the application's API base and a session authorized for the named customer organization.
|
|
29
|
+
For example:
|
|
30
|
+
|
|
31
|
+
```http
|
|
32
|
+
GET /organizations/{organizationId}/audit-logs?eventType=organization_member_role_changed
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
For a support crossing, use `eventType=cross_tenant_administrative_access` on the same organization
|
|
36
|
+
audit route. The route's scope and role checks still apply. A guessed organization identifier or a
|
|
37
|
+
role string does not grant access to another customer's history.
|
|
38
|
+
|
|
39
|
+
Use declared top-level query filters. Nested `eventData.resourceType` and
|
|
40
|
+
`eventData.operationIdentifier` are payload fields to inspect after retrieval, not LIST filters.
|
|
41
|
+
For ownership repair, select the operation-event family before inspecting those fields; a search
|
|
42
|
+
restricted to specialized member-role changes can miss it.
|
|
43
|
+
|
|
44
|
+
## Correlate support access without collapsing the records
|
|
45
|
+
|
|
46
|
+
| Record | Question it answers |
|
|
47
|
+
|---|---|
|
|
48
|
+
| Grant lifecycle | Who requested/approved/revoked access, with which justification and validity window? |
|
|
49
|
+
| Crossing observation | Which operator reached which identifiable tenant through which resource operation and variant? |
|
|
50
|
+
| Operation/change evidence | What was requested or changed by the business action? |
|
|
51
|
+
| Application-wide read event | Which broader read occurred without a single target organization? |
|
|
52
|
+
|
|
53
|
+
Resolve `authorizingGrantId` **together with** `authorizingGrantScope`. The row crossing observer uses
|
|
54
|
+
the tenant-grant scope when a tenant grant was resolved; application-wide read grants do not replace
|
|
55
|
+
row admission. Collection observations can identify the applicable tenant or application grant.
|
|
56
|
+
An absent grant identifier is not a request to invent one. `admissionDeclared` tells you the operation
|
|
57
|
+
opted into the crossing mechanism; it alone proves neither usable authorization nor successful work.
|
|
58
|
+
|
|
59
|
+
The row observer acts after the target row's tenant is identifiable; the crossing entry belongs to
|
|
60
|
+
that reached tenant's audit view. Declared READ/LIST/SEARCH outside organization-scoped resources
|
|
61
|
+
use a separate observer grouping the foreign tenants actually returned, including a single READ.
|
|
62
|
+
An empty result produces no returned-record crossing. That observer excludes internal/webhook
|
|
63
|
+
execution and the organization-scoped resources covered by the row observer; COUNT has no returned
|
|
64
|
+
records for it to inspect. A request
|
|
65
|
+
refused before reaching an observation point need not have a crossing entry. Correlate the available
|
|
66
|
+
actor, operation, affected record and request context with grant and operation evidence rather than
|
|
67
|
+
assuming one atomic evidence bundle.
|
|
68
|
+
|
|
69
|
+
## Preserve transaction and delivery meaning
|
|
70
|
+
|
|
71
|
+
Built-in authority writes stage their event data and emit after commit, so a rollback does not leave
|
|
72
|
+
an event asserting a change that never committed. The audit store is not part of that business
|
|
73
|
+
transaction. When extending the lifecycle, preserve its transaction options and supported
|
|
74
|
+
post-commit mechanism; emitting eagerly from an ordinary hook would change that guarantee.
|
|
75
|
+
|
|
76
|
+
Reasserting unchanged roles emits no new specialized role-change event. Cascade removal is explained
|
|
77
|
+
by the parent membership/account lifecycle, not fabricated as a separate revocation for every child.
|
|
78
|
+
System provisioning can produce stored evidence without an authenticated tenant routing context;
|
|
79
|
+
tenant SIEM routing uses that authenticated context, not merely an organization field in event data.
|
|
80
|
+
|
|
81
|
+
Crossing observation is best-effort and does not fail the observed request. An unavailable service or
|
|
82
|
+
failed emission can leave no retained entry. Inspect observation-drop and audit-store failure
|
|
83
|
+
diagnostics as well as configured log/metric retention. An empty query proves neither absence of
|
|
84
|
+
access nor healthy evidence delivery. Present a recorded action, a permission decision and the
|
|
85
|
+
availability of evidence as separate claims.
|
|
86
|
+
|
|
87
|
+
|
|
88
|
+
## Application audit read policy
|
|
89
|
+
|
|
90
|
+
`auditTrail.applicationReadAccess` defaults to `AuditApplicationReadAccess.ROLE_BASED` in every
|
|
91
|
+
environment. Holders of `CORE_APP_ROLES.APP_ADMIN_SUPER_ADMIN` or the read-only
|
|
92
|
+
`CORE_APP_ROLES.APP_AUDIT_EVIDENCE_READER` can read the application audit trail without a second approval;
|
|
93
|
+
scope filters and cross-tenant observations still apply. Give the evidence reader — not super-admin — to a
|
|
94
|
+
party that must read the trail and must not administer the application: an assurance collector's machine
|
|
95
|
+
credential or an external auditor. It inherits no other role. Opt into
|
|
96
|
+
`AuditApplicationReadAccess.INDEPENDENT_APPROVAL` when the application requires a time-bound
|
|
97
|
+
grant signed by a different administrator. Import the enum from `@wildo-ai/saas-models`.
|
|
98
|
+
|
|
99
|
+
A role-based audit read can therefore legitimately have no `authorizingGrantId`. Do not invent a
|
|
100
|
+
grant or infer refusal from that absence: correlate the operation, configured policy, actor roles
|
|
101
|
+
and response outcome.
|
|
102
|
+
|
|
103
|
+
A MACHINE reader has no user id. Its reads are attributed by credential instead: each
|
|
104
|
+
`cross_tenant_administrative_access` row carries `eventData.machineCredential`, and a machine read of the
|
|
105
|
+
application audit door also records `machine_access` (`resourceServer: api`, `operationIdentifier: api_list`,
|
|
106
|
+
`api_read` or `api_search`) even when it returned no tenant's rows. A collector counting audit rows should
|
|
107
|
+
exclude the rows its own credential wrote, or each run counts the previous run's reads.
|
|
108
|
+
|
|
109
|
+
Under `INDEPENDENT_APPROVAL` a machine reads only through an application access grant bound to its
|
|
110
|
+
credential: an administrator requests it with `grantedMachineCredential` (an active, unexpired API key or
|
|
111
|
+
OAuth client of this application), a DIFFERENT administrator approves it, and the grant admits that credential
|
|
112
|
+
and never the administrator who requested it. A machine credential can also ask the token endpoint for a
|
|
113
|
+
shorter token with `requested_expires_in` (seconds) on the `client_credentials` grant; the application's
|
|
114
|
+
access-token lifetime remains the ceiling. Other application-wide reads and tenant support grants keep their existing
|
|
115
|
+
requirements. Audit records are not automatically anonymized in production.
|
|
116
|
+
|
|
117
|
+
|
|
118
|
+
For an application requiring independent approval, configure the shared application configuration:
|
|
119
|
+
|
|
120
|
+
```typescript
|
|
121
|
+
import { AuditApplicationReadAccess, type AuditTrailConfig } from '@wildo-ai/saas-models';
|
|
122
|
+
|
|
123
|
+
const auditTrail: AuditTrailConfig = {
|
|
124
|
+
applicationReadAccess: AuditApplicationReadAccess.INDEPENDENT_APPROVAL,
|
|
125
|
+
};
|
|
126
|
+
```
|
|
127
|
+
|
|
128
|
+
Omitting `applicationReadAccess` selects role-based access. The stronger universal
|
|
129
|
+
`WILDO.ACCESS.SEGREGATION_OF_DUTIES@1` claim must not be accepted on the strength of a directory-only
|
|
130
|
+
elevation test when audit reads intentionally use the role-based policy.
|
|
131
|
+
|
|
132
|
+
|
|
133
|
+
The startup policy event also records `auditApplicationReadAccess.before` and `.after`. An absent
|
|
134
|
+
historical policy is represented as an unknown baseline, not assumed to have required approval.
|
|
135
|
+
Omitting the setting and explicitly selecting role-based access are the same effective policy.
|
|
136
|
+
This event observes the deployed configuration; deployment history identifies who authored it.
|
|
@@ -0,0 +1,85 @@
|
|
|
1
|
+
# Framework Collection-Operation Declarations
|
|
2
|
+
|
|
3
|
+
What a LIST or SEARCH operation variant declares so callers can filter, sort, search, page and
|
|
4
|
+
export it — and what each declaration's ABSENCE means, which is the half that surprises people.
|
|
5
|
+
|
|
6
|
+
Read this when authoring a collection operation, or when a list "works" but returns the wrong rows.
|
|
7
|
+
|
|
8
|
+
| declaration | what it does | absent ⇒ |
|
|
9
|
+
|---|---|---|
|
|
10
|
+
| `filterFields` | field name → schema; the fields a caller may filter on. A date-typed field automatically becomes a RANGE filter | no filtering offered |
|
|
11
|
+
| `sortFields` | the sortable allow-list | **no allow-list you chose** — see below |
|
|
12
|
+
| `isSearchable` + `searchableFields` + `searchableOptions` | free-text search over declared fields, own or relational | no text search |
|
|
13
|
+
| `maxPaginatedResultPerPageLimit` | the per-page ceiling a caller cannot exceed | 100 on a LIST, 50 on a SEARCH — see below |
|
|
14
|
+
| `collectionExport` | `formats` (`CSV` / `JSON`), `rowScopes`, `maximumExportedRows`; derives an export route beside the operation, under the same roles | no export route |
|
|
15
|
+
|
|
16
|
+
## ⚠️ Declare `sortFields`. Omitting it is not "no sorting"
|
|
17
|
+
|
|
18
|
+
With no `sortFields` there is nothing to validate a caller's `sort` against, and the two adapters
|
|
19
|
+
then do different things — neither of which is an allow-list you authored:
|
|
20
|
+
|
|
21
|
+
- **MongoDB returns the caller's sort VERBATIM.** Any field name they send is applied.
|
|
22
|
+
- **PostgreSQL falls back to the resource's planned COLUMNS** as the whitelist — it must name a real
|
|
23
|
+
column, because an unknown identifier there is both a SQL error and an injection surface.
|
|
24
|
+
|
|
25
|
+
So the behaviour is fail-closed on PostgreSQL and open on MongoDB, and on neither is it the set you
|
|
26
|
+
intended. Declare the fields you want sortable.
|
|
27
|
+
|
|
28
|
+
## What a filter is, and is not
|
|
29
|
+
|
|
30
|
+
A filter is an equality, a list of values, or a declared date range. There is no operator syntax on
|
|
31
|
+
the wire — anything richer is a custom operation with its own request shape.
|
|
32
|
+
|
|
33
|
+
**Filtering never widens visibility.** Whatever a caller asks for is intersected with the tenancy and
|
|
34
|
+
ownership filter their execution context carries, and with the retention hide. A filter can only ever
|
|
35
|
+
narrow.
|
|
36
|
+
|
|
37
|
+
## Free text is substring matching, not a search engine
|
|
38
|
+
|
|
39
|
+
Own-field search compiles to a case-insensitive substring match on both adapters. There is no
|
|
40
|
+
relevance ordering, no stemming and no typo tolerance — results come back in the declared sort order.
|
|
41
|
+
If the product needs ranked search, this declaration is not it.
|
|
42
|
+
|
|
43
|
+
## Export is not a snapshot
|
|
44
|
+
|
|
45
|
+
A whole-set export PAGES THROUGH the source operation, so rows written or deleted while the file is
|
|
46
|
+
produced can be missed or repeated; there is no consistent read across pages. Headers are sent before
|
|
47
|
+
the second page is read, so a fault mid-stream TRUNCATES the file rather than returning an error —
|
|
48
|
+
the row-count header is what lets a consumer notice a short file.
|
|
49
|
+
|
|
50
|
+
`maximumExportedRows` is optional, and omitting it means the export pages through whatever the
|
|
51
|
+
caller's filters match. Narrowing that is a decision you make deliberately.
|
|
52
|
+
|
|
53
|
+
CSV is lossy for nested values: an object or array is JSON-encoded into its cell to stay recoverable.
|
|
54
|
+
When a machine reads the result back, choose JSON.
|
|
55
|
+
|
|
56
|
+
## A page ceiling bounds what a CLIENT can ask for — and the two operations enforce it differently
|
|
57
|
+
|
|
58
|
+
Every paginated read is capped at the operation's `maxPaginatedResultPerPageLimit`, on every storage
|
|
59
|
+
adapter. What a caller who asks for more gets back depends on the operation:
|
|
60
|
+
|
|
61
|
+
| operation | a `limit` above the ceiling | undeclared ceiling |
|
|
62
|
+
|---|---|---|
|
|
63
|
+
| LIST | **clamped** — answered `200` with the ceiling applied, and the response's `pagination.limit` reports the limit actually used | 100 |
|
|
64
|
+
| SEARCH | **refused** — `400` validation failure before any query runs, because the request contract carries the same number | 50 |
|
|
65
|
+
|
|
66
|
+
So a client paging through a SEARCH must read the ceiling rather than guess high, and a client of a
|
|
67
|
+
LIST must read `pagination.limit` rather than assume its request was honoured.
|
|
68
|
+
|
|
69
|
+
Declare a ceiling when the default is wrong for the collection. The declaration is a contract, not a
|
|
70
|
+
policy limit: nothing stops an operation declaring a large one, and every page of that size is served
|
|
71
|
+
in full — so size it against the cost of the rows, not against what a caller would like.
|
|
72
|
+
|
|
73
|
+
**A ceiling does not bound an internal read.** Code in a custom implementation or service that asks a
|
|
74
|
+
repository for rows WITHOUT pagination gets every matching row, deliberately: framework enumerations
|
|
75
|
+
such as erasure cascades and subject exports rely on completeness. Over a large tenant that read holds
|
|
76
|
+
the whole result in memory, and nothing prevents it. When your code does not need every row, request
|
|
77
|
+
a page and iterate.
|
|
78
|
+
|
|
79
|
+
**A ceiling bounds the page, not the work.** An expensive filter is still expensive, and the count that
|
|
80
|
+
accompanies a paginated read runs whatever the page size.
|
|
81
|
+
|
|
82
|
+
## Related
|
|
83
|
+
|
|
84
|
+
- `references/framework-saas-models-resource-config-api.md` — the operation-variant type these are
|
|
85
|
+
declared on.
|