@wildo-ai/framework-knowledge 1.1.3 → 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 +349 -17
- 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/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +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.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.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
|
@@ -0,0 +1,158 @@
|
|
|
1
|
+
# saas.models.resource-config.operation-scope-admissions
|
|
2
|
+
|
|
3
|
+
## Import Origins
|
|
4
|
+
|
|
5
|
+
- `@wildo-ai/saas-models`
|
|
6
|
+
|
|
7
|
+
## Source Excerpts
|
|
8
|
+
|
|
9
|
+
### Origin Package: `@wildo-ai/saas-models`
|
|
10
|
+
|
|
11
|
+
```typescript
|
|
12
|
+
*
|
|
13
|
+
* The two per-variant admissions that relax WHOSE row an operation may address. Both are empty by
|
|
14
|
+
* default, both are declared on the VARIANT rather than the resource, and both are the seam a
|
|
15
|
+
* security reviewer should read first.
|
|
16
|
+
*
|
|
17
|
+
* Neither touches WHO may call: the operation's `roles` gate runs independently and unchanged, so
|
|
18
|
+
* an admitted variant is still reachable only by the roles it declares. Role decides who; these
|
|
19
|
+
* decide whose.
|
|
20
|
+
*
|
|
21
|
+
* The trap is the generic verb. Declaring an admission on a general UPDATE opens every field of
|
|
22
|
+
* every row it can reach — which is why the framework's own cross-tenant repair is authored as its
|
|
23
|
+
* own verb that writes one field in one direction and overwrites whatever else the payload carried.
|
|
24
|
+
* Give the crossing its own narrow operation.
|
|
25
|
+
*/
|
|
26
|
+
/**
|
|
27
|
+
* Admits an APPLICATION-scope platform super-administrator to a resource whose primary scope is a
|
|
28
|
+
* PER-INSTANCE tenant scope (today: `ORGANIZATIONS`) without requiring membership of that tenant.
|
|
29
|
+
*
|
|
30
|
+
* ## Why this exists, and why it is per-variant rather than global
|
|
31
|
+
*
|
|
32
|
+
* `validateParentScopeAccess` authorizes an organization-scoped operation by finding an
|
|
33
|
+
* organization-WIDE `initiatorRoles` entry whose `relatedResourceId` is the target organization. A
|
|
34
|
+
* platform super-administrator holds an APPLICATION-scope entry and therefore matches nothing — so
|
|
35
|
+
* they are denied on every org-scoped resource, INCLUDING the organization row itself. That is
|
|
36
|
+
* normally exactly right: it is what makes tenant isolation hold against the most privileged
|
|
37
|
+
* principal in the system, and it is pinned by
|
|
38
|
+
* `cross-tenant-super-admin-reach.integration.test.ts`.
|
|
39
|
+
*
|
|
40
|
+
* It also means a tenant that loses its last owner cannot be repaired by anyone, which is the other
|
|
41
|
+
* half of the administrative-continuity pattern: protect the tenant tier and
|
|
42
|
+
* repair it only from a higher authorized tier. This flag is that higher-tier
|
|
43
|
+
* exception and nothing else.
|
|
44
|
+
*
|
|
45
|
+
* **It is deliberately NOT a global super-admin bypass.** Adding one to the authorization layer
|
|
46
|
+
* would grant cross-tenant reach to EVERY org-scoped operation whose gate a super-admin's role
|
|
47
|
+
* chain satisfies — an enormous, silent widening of tenant isolation. Instead each variant opts in
|
|
48
|
+
* explicitly, so the admitted surface is enumerable by grep and empty by default.
|
|
49
|
+
*
|
|
50
|
+
* ## Conditions, all required
|
|
51
|
+
*
|
|
52
|
+
* - The caller must hold `APP_ADMIN_SUPER_ADMIN` at **APPLICATION** scope. An organization-scoped
|
|
53
|
+
* role string that merely spells the same name confers nothing: `getRoleHierarchy` partitions the
|
|
54
|
+
* two role tables, and membership `roles` is free-form (`OrgRolesSchema` admits any string), so
|
|
55
|
+
* without the scope qualifier a tenant admin could type their way into cross-tenant reach.
|
|
56
|
+
* - The variant must declare this flag. Absent, behaviour is unchanged and the caller is denied.
|
|
57
|
+
* - The caller must hold a usable platform-access grant for the target organization. Platform
|
|
58
|
+
* authority and this flag alone do not authorize ordinary cross-tenant operations.
|
|
59
|
+
* The REQUEST_ACCESS operation is the bootstrap exception: it asks for the grant and therefore
|
|
60
|
+
* cannot require one first. An ownerless-tenant recovery may auto-approve that request; recovery
|
|
61
|
+
* operations still require the resulting usable grant.
|
|
62
|
+
*
|
|
63
|
+
* Declare it only on operations whose PURPOSE is cross-tenant administration, and expect each one
|
|
64
|
+
* to justify itself: this is the seam a reviewer should look at first.
|
|
65
|
+
*
|
|
66
|
+
* assurance-control: WILDO.ACCESS.CROSS_TENANT_ADMINISTRATION — an explicitly enumerated,
|
|
67
|
+
* platform-tier admission across a tenant boundary that is otherwise absolute.
|
|
68
|
+
*/
|
|
69
|
+
admitsCrossTenantPlatformAdministration?: boolean;
|
|
70
|
+
|
|
71
|
+
/**
|
|
72
|
+
* Admits this variant to address a USER other than the caller — the USER_SELF-scope sibling of
|
|
73
|
+
* {@link admitsCrossTenantPlatformAdministration}, and it follows that flag's doctrine exactly:
|
|
74
|
+
* per-variant, empty by default, enumerable by grep.
|
|
75
|
+
*
|
|
76
|
+
* ## Why it is needed
|
|
77
|
+
*
|
|
78
|
+
* `authorizeUserSelf` authorizes a USER_SELF-scoped operation by requiring the addressed row to BE
|
|
79
|
+
* the caller. On `USERS` — whose `resourcePrimaryScope` IS `USER_SELF`, because the resource is a
|
|
80
|
+
* self-anchor scope root — that made the entire administrative surface self-only: `assign_roles`,
|
|
81
|
+
* `revoke_roles`, `suspend_user`, `unsuspend_user`, `reactivate_user`, `force_password_reset`, the admin READ and the
|
|
82
|
+
* core UPDATE/DELETE all refused `authorizations_access_denied` against another user, while the
|
|
83
|
+
* specification documents every one of them as acting on "another user's record" and the admin UI
|
|
84
|
+
* surfaces them as per-row actions.
|
|
85
|
+
*
|
|
86
|
+
* ## Why it is PER-VARIANT and not per-resource
|
|
87
|
+
*
|
|
88
|
+
* This is the whole reason a resource-level declaration cannot serve. Within `USERS` the two READ
|
|
89
|
+
* variants need OPPOSITE answers:
|
|
90
|
+
*
|
|
91
|
+
* - the DEFAULT read is gated `APP_USER`. Admitting cross-subject addressing there would let ANY
|
|
92
|
+
* authenticated user read ANY other user's row — `email`, `appRoles`, `status` — a privacy and
|
|
93
|
+
* enumeration regression far worse than the bug being fixed.
|
|
94
|
+
* - the `admin` read is gated `APP_ADMIN_VIEWER` and is precisely the surface that SHOULD address
|
|
95
|
+
* others.
|
|
96
|
+
*
|
|
97
|
+
* One resource, one field identifier, two required answers. Only the variant can carry it.
|
|
98
|
+
*
|
|
99
|
+
* ## What still protects the surface
|
|
100
|
+
*
|
|
101
|
+
* This flag relaxes WHOSE row may be addressed. It does not touch WHO may call: the operation's
|
|
102
|
+
* `roles` gate runs independently and unchanged, so an admitted variant is still reachable only by
|
|
103
|
+
* the roles it declares. Role decides who; this decides whose. Declare it only where the
|
|
104
|
+
* operation's PURPOSE is administering another person, and expect each one to justify itself.
|
|
105
|
+
*
|
|
106
|
+
* assurance-control: WILDO.ACCESS.LEAST_PRIVILEGE — an administrative action on another principal
|
|
107
|
+
* is authorized by the caller's ROLE, never by caller and subject being the same person.
|
|
108
|
+
*/
|
|
109
|
+
admitsCrossSubjectUserAdministration?: boolean;
|
|
110
|
+
|
|
111
|
+
/**
|
|
112
|
+
* Admits this variant to perform a COLLECTION-shaped write on a scope-ROOT resource that the
|
|
113
|
+
* caller's own execution context confines — the ANONYMOUS-scope sibling of
|
|
114
|
+
* {@link admitsCrossTenantPlatformAdministration} and {@link admitsCrossSubjectUserAdministration},
|
|
115
|
+
* following the same doctrine: per-variant, empty by default, enumerable by grep.
|
|
116
|
+
*
|
|
117
|
+
* ## Why it is needed
|
|
118
|
+
*
|
|
119
|
+
* A collection-shaped operation on a scope root is classified by
|
|
120
|
+
* `isUnconfinedScopeRootDirectoryRead` as an unconfined DIRECTORY write, and
|
|
121
|
+
* `enforceApplicationWideReadAdmission` then demands a two-person application access grant. That
|
|
122
|
+
* classification is right for the population it was written for — `SCOPE_ROOT_CONFINED_OPERATIONS`
|
|
123
|
+
* deliberately includes `UPDATE_MANY` so that "a set-shaped write on the tenant resource" cannot
|
|
124
|
+
* appear unconfined — and it is right because the gate reads the DECLARED shape and can know
|
|
125
|
+
* nothing about the row a custom implementation will actually select.
|
|
126
|
+
*
|
|
127
|
+
* But a collection shape is also the only shape in which a request CANNOT NAME A ROW, which is
|
|
128
|
+
* exactly what an anonymous self-write wants: `ANONYMOUS_USERS.record_consent` carries no entity id
|
|
129
|
+
* precisely so a visitor cannot address another visitor's session, and its implementation selects
|
|
130
|
+
* `{ uuidRef }` from the verified session JWT. Without this flag that operation answers 403 to the
|
|
131
|
+
* only caller it exists for (#1267).
|
|
132
|
+
*
|
|
133
|
+
* ## Why the confinement authority was NOT extended instead
|
|
134
|
+
*
|
|
135
|
+
* `assignScopeRootCollectionConfinementToFilter` states on its own disposition enum that
|
|
136
|
+
* `USER_SELF` / `ANONYMOUS` instances come from `initiatorIds`, *"which the request supplies about
|
|
137
|
+
* ITSELF and which therefore cannot be an authority set"*. Teaching it to confine by
|
|
138
|
+
* `anonymousUserId` would reverse that measured decision for every scope-root operation at once.
|
|
139
|
+
* This flag changes nothing there: the tenant derivation, its disposition vocabulary and every
|
|
140
|
+
* other operation are untouched.
|
|
141
|
+
*
|
|
142
|
+
* ## What the declaring operation owes
|
|
143
|
+
*
|
|
144
|
+
* The flag says "this write is confined by something the gate cannot see". The operation must
|
|
145
|
+
* therefore CONFINE IT — from the execution context, never from the request — and say where. A
|
|
146
|
+
* variant that declares this and then writes an unfiltered set has made the declaration a lie, and
|
|
147
|
+
* the gate will not catch it. Declare it only where the operation's PURPOSE is a principal acting
|
|
148
|
+
* on its own single row, and expect each one to justify itself: this is a seam a reviewer should
|
|
149
|
+
* look at first.
|
|
150
|
+
*
|
|
151
|
+
* It relaxes only the DIRECTORY classification. The operation's `roles` gate, the parent-scope
|
|
152
|
+
* check and the repository's own filters all run unchanged.
|
|
153
|
+
*
|
|
154
|
+
* assurance-control: WILDO.ACCESS.LEAST_PRIVILEGE — a collection-shaped write is admitted without a
|
|
155
|
+
* platform elevation only where the acting principal is confined to its own row by construction.
|
|
156
|
+
*/
|
|
157
|
+
admitsSelfConfinedScopeRootWrite?: boolean;
|
|
158
|
+
```
|
|
@@ -0,0 +1,77 @@
|
|
|
1
|
+
# saas.models.resource-config.operation-step-up
|
|
2
|
+
|
|
3
|
+
## Import Origins
|
|
4
|
+
|
|
5
|
+
- `@wildo-ai/saas-models`
|
|
6
|
+
|
|
7
|
+
## Source Excerpts
|
|
8
|
+
|
|
9
|
+
### Origin Package: `@wildo-ai/saas-models`
|
|
10
|
+
|
|
11
|
+
```typescript
|
|
12
|
+
*
|
|
13
|
+
* Demand a FRESH proof of identity for this specific operation, regardless of how recently the
|
|
14
|
+
* caller authenticated.
|
|
15
|
+
*
|
|
16
|
+
* The framework's baseline step-up is a per-USER-TYPE policy (`UserTypeAuthPolicy.stepUpAuth`):
|
|
17
|
+
* opt-in, defaulting to `enabled: false`, and *freshness*-based — it challenges only once the
|
|
18
|
+
* session's `lastAuthenticatedAt` is older than `maxAgeSeconds` (default 300). That is the right
|
|
19
|
+
* shape for "this tenant wants periodic re-proof across the board", and the wrong shape for a
|
|
20
|
+
* single irreversible action: a caller who signed in two minutes ago destroys the resource with
|
|
21
|
+
* no credential proof at all, and an application that never configures `stepUpAuth` is never
|
|
22
|
+
* challenged for anything.
|
|
23
|
+
*
|
|
24
|
+
* Setting this to `true` makes the challenge UNCONDITIONAL for this operation. The caller must
|
|
25
|
+
* present a valid single-use `REAUTH` consumable token (minted by `POST /auth/reauth`, carried in
|
|
26
|
+
* `X-Reauth-Token`); otherwise the request is refused with `STEP_UP_REQUIRED` (HTTP 403). The
|
|
27
|
+
* frontend HTTP client already completes this loop — it catches the 403, runs the registered
|
|
28
|
+
* step-up handler to obtain a token, and replays the request — so declaring the flag is the whole
|
|
29
|
+
* integration.
|
|
30
|
+
*
|
|
31
|
+
* FAIL-CLOSED by design: an operation that declares this is challenged even when the user type
|
|
32
|
+
* has NO `stepUpAuth` policy at all. Deriving the requirement from `riskLevel` was rejected —
|
|
33
|
+
* `riskLevel` is a UI/observability signal (danger-zone placement, typed confirmation, MCP
|
|
34
|
+
* destructive hints), read today by no authorization code, and silently promoting it to a security
|
|
35
|
+
* control would change the behaviour of every existing `CRITICAL` operation at once.
|
|
36
|
+
*
|
|
37
|
+
* Applies only to principals whose identity can be re-proved: user requests that are not
|
|
38
|
+
* sub-calls. Machine principals, internal calls and worker executions are exempt exactly as they
|
|
39
|
+
* are for the baseline policy — there is no interactive credential to re-present.
|
|
40
|
+
*
|
|
41
|
+
* ⚠️ **Check who can actually satisfy it before declaring it.**
|
|
42
|
+
* `AuthMethodManagementBackendService.reAuthenticate` accepts THREE factors — `PASSWORD`, `TOTP`
|
|
43
|
+
* (a code or a backup code, through the same anti-replay authority login uses) and `PASSKEY` (a
|
|
44
|
+
* WebAuthn assertion produced under {@link PasskeyAuthenticationCeremony.STEP_UP}, which pins user
|
|
45
|
+
* verification to REQUIRED and uses a challenge key a login assertion cannot redeem). A principal
|
|
46
|
+
* satisfies this gate only by proving an enrolled factor accepted by the effective policy.
|
|
47
|
+
* Holding a credential alone does not mean its method is currently permitted.
|
|
48
|
+
*
|
|
49
|
+
* A person who signs in through SSO can use an accepted local factor; a genuinely SSO-only
|
|
50
|
+
* account without one cannot satisfy this gate with its upstream SSO session. Passkey-only
|
|
51
|
+
* accounts can satisfy it when their passkey remains accepted by the effective policy.
|
|
52
|
+
*
|
|
53
|
+
* - **directory-managed (SCIM) users** in particular. The framework deliberately destroys their
|
|
54
|
+
* `passwordHash` AND passkeys as a compliance control
|
|
55
|
+
* (`_reconcileLocalCredentialsForDirectoryManaged` — a local first factor would survive IdP
|
|
56
|
+
* deprovisioning) and deliberately PRESERVES their TOTP, which sits on top of the IdP first
|
|
57
|
+
* factor. TOTP re-auth is what makes that preserved factor usable, and it is why an ORG_ADMIN
|
|
58
|
+
* of a directory-managed tenant can start a teardown when enrolled TOTP is accepted by policy.
|
|
59
|
+
*
|
|
60
|
+
* A principal holding NONE of the three still cannot satisfy the gate, and is still refused
|
|
61
|
+
* fail-closed with a diagnosable message. Check the effective `stepUpAuth` policy, including
|
|
62
|
+
* organization overrides and its accepted `methods` when enabled, before declaring this flag
|
|
63
|
+
* on an operation that population must perform. Login-method availability is a separate decision.
|
|
64
|
+
*
|
|
65
|
+
* This is also why the requirement is a per-operation flag rather than a hardcoded `password`
|
|
66
|
+
* field in a request DTO: the proof is negotiated by the auth policy, not frozen into the resource
|
|
67
|
+
* contract. A `{ password }` field cannot adapt to any of the above.
|
|
68
|
+
*
|
|
69
|
+
* assurance-control: WILDO.IDENTITY.STEP_UP_AUTHENTICATION — re-authentication before a high-impact action.
|
|
70
|
+
*
|
|
71
|
+
* ⚠️ **Read-shaped operations are SKIPPED, so the flag is inert on them.** `READ`, `LIST`,
|
|
72
|
+
* `SEARCH` and `COUNT` never reach the gate — declaring it there configures cleanly and enforces
|
|
73
|
+
* nothing. Step-up guards an ACT, not a look; to restrict who may read, use the operation's
|
|
74
|
+
* `roles`.
|
|
75
|
+
*/
|
|
76
|
+
requiresStepUpAuthentication?: boolean;
|
|
77
|
+
```
|
package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md
ADDED
|
@@ -0,0 +1,42 @@
|
|
|
1
|
+
# saas.models.resource-config.operation-variant-client-timeout
|
|
2
|
+
|
|
3
|
+
## Import Origins
|
|
4
|
+
|
|
5
|
+
- `@wildo-ai/saas-models`
|
|
6
|
+
|
|
7
|
+
## Source Excerpts
|
|
8
|
+
|
|
9
|
+
### Origin Package: `@wildo-ai/saas-models`
|
|
10
|
+
|
|
11
|
+
```typescript
|
|
12
|
+
*
|
|
13
|
+
* Frontend HTTP timeout for THIS variant, in milliseconds — declare it on any operation whose
|
|
14
|
+
* synchronous round trip legitimately outlives the frontend client's 30-second default (an
|
|
15
|
+
* operation that calls a model and waits for the answer, a long import, a blocking generation).
|
|
16
|
+
*
|
|
17
|
+
* The frontend resources client applies it as the per-request timeout on every dispatch shape
|
|
18
|
+
* (api-call, api-call-with-callback, search). An explicit caller-supplied
|
|
19
|
+
* `RequestOptions.timeout` still wins; omitting the field keeps the client default.
|
|
20
|
+
*
|
|
21
|
+
* Why it matters: without it, a long-running operation's request is aborted CLIENT-side while
|
|
22
|
+
* the server work succeeds — the caller renders a network error, and the operation-success
|
|
23
|
+
* refresh chain never fires, so lists keep showing the pre-operation world. Declare the
|
|
24
|
+
* expectation on the variant (the operation knows it is long-running); do not hard-code
|
|
25
|
+
* timeouts in consumer hooks, which duplicates that knowledge at every call site.
|
|
26
|
+
*
|
|
27
|
+
* This is a TRANSPORT expectation only — not a UI/observability signal (that is `riskLevel`)
|
|
28
|
+
* and not a server-side bound: the backend is free to answer sooner or be cut off by its own
|
|
29
|
+
* limits.
|
|
30
|
+
*
|
|
31
|
+
* @example a custom operation that generates a document before answering
|
|
32
|
+
* variants: [{
|
|
33
|
+
* variantType: ResourceOperationVariantType.API_CALL,
|
|
34
|
+
* roles: [CORE_ORG_ROLES.ORG_MEMBER],
|
|
35
|
+
* riskLevel: ResourceOperationRiskLevel.MEDIUM,
|
|
36
|
+
* clientRequestTimeoutMs: 300_000, // five minutes — the generation is synchronous
|
|
37
|
+
* requestDto: GenerateReportRequest_Schema,
|
|
38
|
+
* customResponseDto: GenerateReportOutcome_Schema,
|
|
39
|
+
* }]
|
|
40
|
+
*/
|
|
41
|
+
clientRequestTimeoutMs?: number;
|
|
42
|
+
```
|
|
@@ -53,10 +53,15 @@ export type OperationConfig_ForKey<
|
|
|
53
53
|
TMainSchema extends z.ZodTypeAny = z.ZodAny
|
|
54
54
|
> = {
|
|
55
55
|
variants: OperationVariant_ForKey<K, TMainSchema>[];
|
|
56
|
+
/** Reply deadline, initial routing priority and failure retry budget/backoff. Does not cancel execution. */
|
|
57
|
+
queueConfig?: ResourceConfiguration_QueueConfigAuthored;
|
|
56
58
|
serviceRuntimeMode?: ResourceOperation_ServiceRuntimeMode;
|
|
57
59
|
parentResourceAccessScopeStrategyOverrides?: { resourceType: ResourceType, accessScopeStrategy: ResourceRelationshipAccessScopeStrategy }[];
|
|
58
60
|
userNotifications?: UserNotificationDefinitionWithoutPrimaryScopeAndIdentifier[];
|
|
59
|
-
notificationBadgeOperations?: {
|
|
61
|
+
notificationBadgeOperations?: { badgeRef: NotificationBadgeKey, operation: NotificationBadgeOperation }[];
|
|
60
62
|
m2mNotifications?: M2MNotificationDefinitionWithoutIdentifier[];
|
|
63
|
+
recordsUsage?: MeteredUsageRecordingDefinition;
|
|
64
|
+
/** See {@link ResourceOperationConsentGateDeclaration} (#1258 Step 3). */
|
|
65
|
+
consentGate?: ResourceOperationConsentGateDeclaration;
|
|
61
66
|
};
|
|
62
67
|
```
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
# saas.models.resource-config.queue-policy
|
|
2
|
+
|
|
3
|
+
## Import Origins
|
|
4
|
+
|
|
5
|
+
- `@wildo-ai/saas-models`
|
|
6
|
+
|
|
7
|
+
## Source Excerpts
|
|
8
|
+
|
|
9
|
+
### Origin Package: `@wildo-ai/saas-models`
|
|
10
|
+
|
|
11
|
+
```typescript
|
|
12
|
+
*
|
|
13
|
+
* Queue policy for an operation declared with createResourceConfiguration_Initialization
|
|
14
|
+
* from @wildo-ai/saas-models. Set queueConfig beside serviceRuntimeMode, outside variants.
|
|
15
|
+
* Omitted fields take the schema defaults. timeoutMs limits caller waiting, not execution.
|
|
16
|
+
* Priority selects the initial queue lane; retries do not promise permanent priority ordering.
|
|
17
|
+
* maxRetries limits additional attempts after an actual failure, not duplicate broker deliveries.
|
|
18
|
+
*
|
|
19
|
+
* @example
|
|
20
|
+
* // Inside an operation configuration:
|
|
21
|
+
* // serviceRuntimeMode: ResourceOperation_ServiceRuntimeMode.QUEUED,
|
|
22
|
+
* // queueConfig: { timeoutMs: 30000, maxRetries: 0 },
|
|
23
|
+
*/
|
|
24
|
+
export const ResourceConfiguration_QueueConfigSchema = z.object({
|
|
25
|
+
/** Priority for queue routing (HIGH/CRITICAL → priority queue) */
|
|
26
|
+
priority: z.enum(JobPriority).default(JobPriority.NORMAL),
|
|
27
|
+
|
|
28
|
+
/** Maximum retry attempts before dead-letter */
|
|
29
|
+
maxRetries: z.number().int().min(0).default(3),
|
|
30
|
+
|
|
31
|
+
/** Caller reply-wait deadline in milliseconds (default: 5 minutes). Does not cancel worker execution. */
|
|
32
|
+
timeoutMs: z.number().int().min(1000).max(2147483647).default(300000),
|
|
33
|
+
|
|
34
|
+
/**
|
|
35
|
+
* Retry backoff timing (base delay, cap, curve). Controls how long a failed
|
|
36
|
+
* job of this operation waits before each re-attempt. Optional — unset fields
|
|
37
|
+
* fall back to `QUEUE_RETRY_DEFAULTS`. Honored by the queue worker via a
|
|
38
|
+
* durable broker delay queue (see `QueueRetryBackoffConfig`). Distinct from
|
|
39
|
+
* `maxRetries` (how many attempts) and `timeoutMs` (caller reply-wait deadline).
|
|
40
|
+
*/
|
|
41
|
+
retryConfig: QueueRetryBackoffConfigSchema.optional(),
|
|
42
|
+
|
|
43
|
+
}).strict().optional();
|
|
44
|
+
|
|
45
|
+
export type ResourceConfiguration_QueueConfig = z.infer<typeof ResourceConfiguration_QueueConfigSchema>;
|
|
46
|
+
|
|
47
|
+
/** Application input accepts omitted defaulted fields; the resource factory validates and resolves them. */
|
|
48
|
+
export type ResourceConfiguration_QueueConfigAuthored = z.input<typeof ResourceConfiguration_QueueConfigSchema>;
|
|
49
|
+
```
|
|
@@ -0,0 +1,84 @@
|
|
|
1
|
+
# saas.models.resource-config.required-features
|
|
2
|
+
|
|
3
|
+
## Import Origins
|
|
4
|
+
|
|
5
|
+
- `@wildo-ai/saas-models`
|
|
6
|
+
|
|
7
|
+
## Source Excerpts
|
|
8
|
+
|
|
9
|
+
### Origin Package: `@wildo-ai/saas-models`
|
|
10
|
+
|
|
11
|
+
```typescript
|
|
12
|
+
*
|
|
13
|
+
* Gating an operation or a view on a FEATURE the customer has — a plan entitlement, a boolean
|
|
14
|
+
* capability, or a usage limit.
|
|
15
|
+
*
|
|
16
|
+
* Declared as `requiredFeatures` on a resource operation variant or on a view. The shorthand form is
|
|
17
|
+
* a plain `string[]` of feature identifiers, auto-normalized to `{ features, mode: 'OR' }`; the full
|
|
18
|
+
* form adds `mode: 'AND'` and `limitChecks`.
|
|
19
|
+
*
|
|
20
|
+
* ## ⚠️ The screen gate is NOT the security boundary
|
|
21
|
+
*
|
|
22
|
+
* Declaring the requirement on a VIEW decides what a screen looks like. It does not stop the
|
|
23
|
+
* operation running. A capability that must not be REACHABLE needs the requirement declared on the
|
|
24
|
+
* OPERATION as well — the backend gate is what refuses, and it is the only thing that does.
|
|
25
|
+
*
|
|
26
|
+
* Two consequences of the interface half that follow from this, and are not defects:
|
|
27
|
+
*
|
|
28
|
+
* - **While the resolved feature set is still loading, everything is treated as AVAILABLE.** That
|
|
29
|
+
* avoids a flash of locked interface, and it means a gate can briefly show content the backend
|
|
30
|
+
* would refuse. Correct behaviour; not something to design around on the screen.
|
|
31
|
+
* - A hidden or prompted control is a presentation choice, so anyone who reaches the endpoint
|
|
32
|
+
* directly is decided by the operation's own declaration.
|
|
33
|
+
*
|
|
34
|
+
* ## Limit checks measure, they do not merely check presence
|
|
35
|
+
*
|
|
36
|
+
* `features` is a PRESENCE check on boolean capabilities. `limitChecks` is different: each entry
|
|
37
|
+
* names a LIMIT-type feature and an increment, and the gate measures current usage through that
|
|
38
|
+
* feature definition's own `counting` config before allowing the operation. Use `limitChecks` for
|
|
39
|
+
* "up to N of these", never a boolean feature.
|
|
40
|
+
*
|
|
41
|
+
* Limit check entry: references a LIMIT-type feature and specifies the increment.
|
|
42
|
+
* The gate uses the feature definition's `counting` config to measure current usage.
|
|
43
|
+
*/
|
|
44
|
+
export type RequiredFeaturesLimitCheck = {
|
|
45
|
+
/** Feature identifier (must reference a LIMIT-type feature) */
|
|
46
|
+
featureId: string;
|
|
47
|
+
/**
|
|
48
|
+
* How many units this operation would add.
|
|
49
|
+
* When omitted: auto-inferred from operation type:
|
|
50
|
+
* - CREATE → 1
|
|
51
|
+
* - CREATE_MANY → validatedData.length
|
|
52
|
+
* - All others → 0
|
|
53
|
+
*/
|
|
54
|
+
increment?: number;
|
|
55
|
+
/**
|
|
56
|
+
* Override counting config from feature definition (rare).
|
|
57
|
+
* Use when this specific operation needs different counting than the default.
|
|
58
|
+
*/
|
|
59
|
+
countingOverride?: LimitCountingConfig;
|
|
60
|
+
};
|
|
61
|
+
|
|
62
|
+
/**
|
|
63
|
+
* Full required features configuration for an operation variant.
|
|
64
|
+
*/
|
|
65
|
+
export type RequiredFeaturesFullConfig = {
|
|
66
|
+
/** Boolean feature identifiers that gate this operation (presence check) */
|
|
67
|
+
features?: string[];
|
|
68
|
+
/** Combination mode for boolean features: OR = any enables (default), AND = all required */
|
|
69
|
+
mode?: 'OR' | 'AND';
|
|
70
|
+
/** Limit checks to perform before this operation */
|
|
71
|
+
limitChecks?: RequiredFeaturesLimitCheck[];
|
|
72
|
+
};
|
|
73
|
+
|
|
74
|
+
/**
|
|
75
|
+
* Required features config: accepts either shorthand (string[]) or full config.
|
|
76
|
+
* Shorthand is auto-normalized by the factory to { features: [...], mode: 'OR' }.
|
|
77
|
+
*/
|
|
78
|
+
export type RequiredFeaturesConfig = string[] | RequiredFeaturesFullConfig;
|
|
79
|
+
|
|
80
|
+
/**
|
|
81
|
+
* Normalized required features (always the full form, after factory processing).
|
|
82
|
+
*/
|
|
83
|
+
export type RequiredFeaturesNormalized = RequiredFeaturesFullConfig;
|
|
84
|
+
```
|
|
@@ -60,6 +60,8 @@ export type ResourceConfiguration<
|
|
|
60
60
|
* (factory-enforced both ways). See the authoring-side declaration for the full contract.
|
|
61
61
|
*/
|
|
62
62
|
httpApiBinding?: HttpApiResourceBinding,
|
|
63
|
+
/** REQUIRED when `persistenceAdapter` is INTROSPECTION; meaningless otherwise. */
|
|
64
|
+
introspectionBinding?: IntrospectionResourceBinding,
|
|
63
65
|
|
|
64
66
|
/**
|
|
65
67
|
* The inbound ETL pipeline, when this LOCAL resource declared one — parsed + coherence-checked
|
|
@@ -89,6 +91,14 @@ export type ResourceConfiguration<
|
|
|
89
91
|
*/
|
|
90
92
|
systemAccessPolicy?: ResourceSystemAccessPolicy,
|
|
91
93
|
|
|
94
|
+
/**
|
|
95
|
+
* Declares this resource as the application's SUBJECT-ERASURE REQUEST LANE and binds the fields an
|
|
96
|
+
* evidence collector reads. Omitted ⇒ this resource is not that lane, which is the honest default:
|
|
97
|
+
* most resources are not, and an application that never built an erasure lane has declared none
|
|
98
|
+
* rather than failed a control. See {@link ResourceSubjectErasureLane}.
|
|
99
|
+
*/
|
|
100
|
+
subjectErasureLane?: ResourceSubjectErasureLane,
|
|
101
|
+
|
|
92
102
|
/**
|
|
93
103
|
* W7.3a: Marks this resource as accessible to anonymous sessions.
|
|
94
104
|
* When true, the engine generates dual URL paths and a STANDALONE relationship to ANONYMOUS_USERS.
|
|
@@ -19,6 +19,20 @@ export type ResourcesRegistry = {
|
|
|
19
19
|
resourceConfigurations: {
|
|
20
20
|
[key: ResourceType]: AnyResourceConfiguration ;
|
|
21
21
|
};
|
|
22
|
+
/**
|
|
23
|
+
* The resource types the APPLICATION registered — its own, never the engine's.
|
|
24
|
+
*
|
|
25
|
+
* The registry composes app and core factory maps into one `resourceConfigurations`, which is what
|
|
26
|
+
* every runtime consumer wants. This is the one place the two are still distinguishable, so the
|
|
27
|
+
* split is recorded HERE rather than re-derived by each consumer from a core key set — which would
|
|
28
|
+
* be a second enumeration of a population this file already knows.
|
|
29
|
+
*
|
|
30
|
+
* Its consumer today is the personal-data declaration report, which asks a question only an
|
|
31
|
+
* application author can act on: the engine declares its own posture on ~85 resources, and putting
|
|
32
|
+
* those in front of a reader of a report about THEIR application is how a diagnostic channel stops
|
|
33
|
+
* being read.
|
|
34
|
+
*/
|
|
35
|
+
applicationResourceTypes: ResourceType[];
|
|
22
36
|
/**
|
|
23
37
|
* Map of ResourceType to its standard field identifier (e.g., USERS -> userId).
|
|
24
38
|
* Used for FK field resolution without string manipulation.
|
|
@@ -67,6 +67,101 @@ export enum ResourceSystemAccessMode {
|
|
|
67
67
|
* framework infrastructure does NOT imply that an ACL bypass is acceptable
|
|
68
68
|
* for its data. Keep the two concepts separate.
|
|
69
69
|
*/
|
|
70
|
+
/**
|
|
71
|
+
* Declares that THIS resource is the application's subject-erasure request lane, and how to read it.
|
|
72
|
+
*
|
|
73
|
+
* ## Why the application declares it rather than the framework knowing it
|
|
74
|
+
*
|
|
75
|
+
* The erasure lane is application-owned — four of the five marked sites for
|
|
76
|
+
* `WILDO.PRIVACY.SUBJECT_ERASURE` are in an application, not the engine — and its evidence demand
|
|
77
|
+
* (`evidence-requirement:subject-erasure-execution-record`) says so in terms: *"the row's schema and
|
|
78
|
+
* status vocabulary are the application's, so a collector queries it against that application's
|
|
79
|
+
* specification"*, and its verification step adds *"do NOT assert a specific channel vocabulary:
|
|
80
|
+
* that is one application's modelling choice"*.
|
|
81
|
+
*
|
|
82
|
+
* So a collector may not know that a request is raised through a field called `channel` carrying a
|
|
83
|
+
* value called `SUBJECT`. It has to be TOLD, by the application, in a form it can read. Before this
|
|
84
|
+
* existed, three clauses of that demand had a durable row holding every fact they wanted and no way
|
|
85
|
+
* to find it (#1209): not a missing control, a control nobody could point at.
|
|
86
|
+
*
|
|
87
|
+
* ## It binds FIELDS, never values the framework invents
|
|
88
|
+
*
|
|
89
|
+
* Every member below names something the application already authored. The one value the
|
|
90
|
+
* declaration carries — {@link ResourceSubjectErasureLane.raisedBy}`.subjectValue` — is the
|
|
91
|
+
* application's OWN enum member, quoted back so a reader can tell the two populations apart. The
|
|
92
|
+
* framework supplies no vocabulary here and must never grow one.
|
|
93
|
+
*
|
|
94
|
+
* ## What is deliberately NOT declared
|
|
95
|
+
*
|
|
96
|
+
* The SCHEDULE. C3 asks that requests be executed on the declared schedule, and that schedule is
|
|
97
|
+
* already on the executing operation's `CRON_JOB` variant (`cronExpression`) — declaring it again
|
|
98
|
+
* here would be a second copy that can only ever disagree with the one the scheduler reads.
|
|
99
|
+
* `executionOperationIdentifier` names the operation; the schedule is read from it.
|
|
100
|
+
*/
|
|
101
|
+
export type ResourceSubjectErasureLane = {
|
|
102
|
+
/**
|
|
103
|
+
* How a row says WHO raised the request — the subject exercising their own right, or the
|
|
104
|
+
* controller acting on their behalf. C1's whole obligation is that the two are distinguishable.
|
|
105
|
+
*/
|
|
106
|
+
raisedBy: {
|
|
107
|
+
/** The field carrying it. Must be a persisted field of this resource. */
|
|
108
|
+
fieldName: string,
|
|
109
|
+
/**
|
|
110
|
+
* The value of that field meaning the SUBJECT raised it themselves. Every other value is read as
|
|
111
|
+
* controller-raised — stated this way round because a lane may grow a second controller channel
|
|
112
|
+
* without the declaration going stale, whereas enumerating the controller values could not.
|
|
113
|
+
*/
|
|
114
|
+
subjectValue: string,
|
|
115
|
+
},
|
|
116
|
+
/**
|
|
117
|
+
* The field carrying WHICH user raised a controller-raised request.
|
|
118
|
+
*
|
|
119
|
+
* Omitting it is a positive claim, not a gap: it says this lane admits no controller-raised
|
|
120
|
+
* request at all. A collector reads it that way and a row carrying a non-subject value then
|
|
121
|
+
* contradicts the declaration, which is a finding about the application rather than about the
|
|
122
|
+
* evidence.
|
|
123
|
+
*/
|
|
124
|
+
requesterFieldName?: string,
|
|
125
|
+
/** The field carrying the justification a controller-raised request was made on, where the lane records one. */
|
|
126
|
+
justificationFieldName?: string,
|
|
127
|
+
/** The field carrying the instant the request was executed or failed. C3 judges execution against it. */
|
|
128
|
+
completedAtFieldName: string,
|
|
129
|
+
/** The field carrying what the execution did. Its vocabulary is the application's. */
|
|
130
|
+
outcomeFieldName: string,
|
|
131
|
+
/**
|
|
132
|
+
* The operation a SUBJECT uses to withdraw their own pending request (C2). Named rather than
|
|
133
|
+
* inferred: "the operation that cancels" is not derivable from an operation vocabulary, and
|
|
134
|
+
* guessing it would make the evidence depend on a naming convention no application agreed to.
|
|
135
|
+
*/
|
|
136
|
+
withdrawalOperationIdentifier: string,
|
|
137
|
+
/**
|
|
138
|
+
* How a WITHDRAWN row is recognisable afterwards — the same shape as {@link raisedBy}, and for the
|
|
139
|
+
* same reason: the vocabulary is the application's.
|
|
140
|
+
*
|
|
141
|
+
* C2 asks for the withdrawal door AND for "any cancelled rows", and those are two different
|
|
142
|
+
* questions. The door is answered from {@link withdrawalOperationIdentifier} — is the operation
|
|
143
|
+
* reachable to a subject while the request is pending — and needs no data at all. The rows need a
|
|
144
|
+
* marker, and there is nothing to derive one from: withdrawal and execution both leave a request in
|
|
145
|
+
* a terminal state, so a reader that knows only `completedAtFieldName` cannot tell "the subject
|
|
146
|
+
* changed their mind" from "the sweep ran".
|
|
147
|
+
*
|
|
148
|
+
* OPTIONAL, because an application may not model withdrawal as a value at all — it may delete the
|
|
149
|
+
* row, or move it. Omitting it says the count is unavailable, and a collector reports that rather
|
|
150
|
+
* than guessing; it never turns into a zero, which would read as "nobody withdrew anything".
|
|
151
|
+
*
|
|
152
|
+
* Note an EMPTY withdrawal set is explicitly not a deficiency in the demand — people do not have
|
|
153
|
+
* to change their minds — so this exists to make the number REPORTABLE, never to make it a target.
|
|
154
|
+
*/
|
|
155
|
+
withdrawnMarker?: {
|
|
156
|
+
/** The field carrying it. Must be a persisted field of this resource. */
|
|
157
|
+
fieldName: string,
|
|
158
|
+
/** The value of that field meaning the SUBJECT withdrew the request before it executed. */
|
|
159
|
+
withdrawnValue: string,
|
|
160
|
+
},
|
|
161
|
+
/** The scheduled operation that executes due requests. Its `cronExpression` IS the declared schedule. */
|
|
162
|
+
executionOperationIdentifier: string,
|
|
163
|
+
};
|
|
164
|
+
|
|
70
165
|
export type ResourceSystemAccessPolicy = {
|
|
71
166
|
/** Governs `readAsSystem`. Omitted ⇒ FORBIDDEN. */
|
|
72
167
|
read?: ResourceSystemAccessMode,
|
|
@@ -90,10 +185,22 @@ export type ResourceSystemAccessPolicy = {
|
|
|
90
185
|
* Auto-derived to `ALLOWED` by the factory when a resource opts into
|
|
91
186
|
* `retentionPolicy`; never authored by hand in the common case.
|
|
92
187
|
*
|
|
93
|
-
* **LIVE.** `readRetainedAsSystem` / `listRetainedAsSystem` exist and are enforced:
|
|
94
|
-
* asserted fail-closed, a privileged human role is required, and every reveal emits a
|
|
95
|
-
* human-attributed `RETAINED_DATA_ACCESS` audit event.
|
|
96
|
-
*
|
|
188
|
+
* **LIVE, and REACHABLE.** `readRetainedAsSystem` / `listRetainedAsSystem` exist and are enforced:
|
|
189
|
+
* the verb is asserted fail-closed, a privileged human role is required, and every reveal emits a
|
|
190
|
+
* human-attributed `RETAINED_DATA_ACCESS` audit event.
|
|
191
|
+
*
|
|
192
|
+
* "Reachable" is the half that was missing until #490, and the distinction is worth keeping. The
|
|
193
|
+
* primitives were correct and enforced from the day M5b landed — and had **no caller**, so the only
|
|
194
|
+
* route an operator actually had to a retained record was a database console: the unaudited path
|
|
195
|
+
* they were built to replace. `users | read_retained` is the operator surface that closes it, an
|
|
196
|
+
* authenticated `APP_ADMIN_SUPER_ADMIN` operation carrying a mandatory justification.
|
|
197
|
+
*
|
|
198
|
+
* A resource that derives this grant and exposes no such operation is reachable by nothing. That
|
|
199
|
+
* is a defensible state — not every retention resource needs an operator door — but it should be a
|
|
200
|
+
* decision rather than an oversight, and `retained-see-through-operator-surface.test.ts` is what
|
|
201
|
+
* makes it one.
|
|
202
|
+
*
|
|
203
|
+
* (This block previously said the primitives were "wired in a later phase" — false since M5b.)
|
|
97
204
|
*/
|
|
98
205
|
seeRetained?: ResourceSystemAccessMode,
|
|
99
206
|
|
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
# saas.models.resource-config.system-managed-fields
|
|
2
|
+
|
|
3
|
+
## Import Origins
|
|
4
|
+
|
|
5
|
+
- `@wildo-ai/saas-models`
|
|
6
|
+
|
|
7
|
+
## Source Excerpts
|
|
8
|
+
|
|
9
|
+
### Origin Package: `@wildo-ai/saas-models`
|
|
10
|
+
|
|
11
|
+
```typescript
|
|
12
|
+
*
|
|
13
|
+
* The field names the framework owns. They are removed from every generated CREATE and UPDATE
|
|
14
|
+
* request contract, for every resource, whatever your schema declares and whatever a caller sends.
|
|
15
|
+
*
|
|
16
|
+
* Declaring one of these in a resource schema is fine and often necessary — the framework maintains
|
|
17
|
+
* the value. What you cannot do is accept it from a client, default it in a form, or require it on a
|
|
18
|
+
* create: the field is stripped before validation runs, so a form that collects it submits a value
|
|
19
|
+
* that is discarded, and a schema that requires it rejects every request.
|
|
20
|
+
*
|
|
21
|
+
* | field | who writes it |
|
|
22
|
+
* |---|---|
|
|
23
|
+
* | `_id` | the persistence layer (or your own `.isPrimaryKey()` field, stored beneath it) |
|
|
24
|
+
* | `createdAt` / `updatedAt` / `deletedAt` | the repository, on write |
|
|
25
|
+
* | `createdByUserId` | the repository, stamped from the execution context on CREATE, immutable afterwards |
|
|
26
|
+
* | `_version_db_doc` | the framework's optimistic-concurrency marker |
|
|
27
|
+
*
|
|
28
|
+
* The failure this prevents is quiet and was paid for once: a create form validating against a
|
|
29
|
+
* reserved field that no form collects fails every submit with `expected string, received undefined`,
|
|
30
|
+
* and the schema looks correct while it does. So the exclusion is unconditional and does not depend
|
|
31
|
+
* on the resource author remembering `.excludeFromCreate()`.
|
|
32
|
+
*
|
|
33
|
+
* ⚠️ A NARROWER set — `_id`, `createdAt`, `updatedAt`, `deletedAt`, `_version_db_doc` — is
|
|
34
|
+
* additionally *mandatory-discard*: even a trusted in-process system write cannot re-attach those
|
|
35
|
+
* through `preserveServerInjectedFields`. `createdByUserId` is deliberately not in that set, because
|
|
36
|
+
* an engine flow creating a row on somebody's behalf legitimately needs to stamp it.
|
|
37
|
+
*/
|
|
38
|
+
const SYSTEM_MANAGED_FIELDS = ['_id', 'createdAt', 'updatedAt', 'deletedAt', 'createdByUserId', '_version_db_doc'] as const;
|
|
39
|
+
```
|