@wildo-ai/framework-knowledge 1.1.8 → 1.1.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +11 -0
- package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +9 -2
- package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +21 -0
- package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +121 -0
- package/dist/claude-marketplace/plugins/wildo/references/expert-personas-and-deliberations.md +26 -7
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +31 -5
- package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +4 -2
- package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +29 -2
- package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +69 -24
- package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +10 -0
- package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +21 -5
- package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +31 -5
- package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +2 -0
- package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +20 -4
- 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 +95 -5
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/index.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
- 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 +11 -11
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +29 -22
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +41 -3
- 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 +175 -14
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -3
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +8 -4
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +13 -6
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +4 -2
- 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 +90 -13
- 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 +4 -3
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +4 -3
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +8 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +12 -4
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +12 -3
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +8 -4
- 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 +4 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +2 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +25 -27
- 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 +91 -43
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +41 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +43 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +200 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +203 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +81 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +93 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +3 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +27 -18
- 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.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +11 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +11 -11
- 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 +2 -0
- 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 +3 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +2 -0
- 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 +3 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +5 -2
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -4
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +27 -6
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +32 -12
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +13 -5
- 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 +7 -3
- 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 +71 -2
- 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 -1
- 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 +23 -8
- 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 +7 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +4 -2
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +9 -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 +3 -3
- 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.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +35 -2
- 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 +41 -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 -1
- package/dist/knowledge/manifest.json +8 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +22 -7
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
- package/dist/knowledge/playbooks/bottom_up.build/method.md +17 -15
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +261 -34
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +42 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +188 -59
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +169 -276
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +8 -1
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +3 -2
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +11 -3
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +129 -17
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +7 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +28 -6
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +5 -4
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +13 -5
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +50 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +16 -4
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +19 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +5 -2
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +7 -3
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +8 -0
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +3 -2
- package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +5 -2
- package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +75 -37
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +35 -38
- package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +145 -0
- package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +57 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +99 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +65 -0
- package/dist/knowledge/playbooks/top_down.brand-naming/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +76 -0
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/method.md +60 -6
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +15 -10
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +10 -9
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +30 -10
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +3 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +4 -1
- package/dist/knowledge/playbooks/top_down.definition/method.md +8 -3
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +6 -4
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +16 -2
- package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +5 -2
- package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +26 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +4 -2
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +11 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +84 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +6 -3
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +21 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +8 -2
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +4 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +29 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +58 -17
- package/dist/knowledge/references/brand.name-choice.config.md +144 -0
- package/dist/knowledge/references/brand.name-screening.config.md +308 -0
- package/dist/knowledge/references/build-plan.task-graph.config.md +119 -11
- package/dist/knowledge/references/business-model.pricing-plan.config.md +16 -0
- package/dist/knowledge/references/business-model.snapshot.config.md +64 -0
- package/dist/knowledge/references/business-model.snapshot.validation.md +68 -4
- package/dist/knowledge/references/capability-composition.config.md +67 -4
- package/dist/knowledge/references/companion.market.prompt-renderer.md +11 -6
- package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +44 -0
- package/dist/knowledge/references/example.backend.custom-operation.audit-event.md +81 -0
- package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +258 -0
- package/dist/knowledge/references/example.backend.custom-operation.computed-total.md +153 -0
- package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +107 -0
- package/dist/knowledge/references/example.data-seeding.minimal.md +39 -10
- package/dist/knowledge/references/example.data-seeding.row-reference.md +80 -0
- package/dist/knowledge/references/example.email.template.minimal.md +1 -1
- package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +74 -0
- package/dist/knowledge/references/example.resource.personal-data.free-text-field.md +19 -0
- package/dist/knowledge/references/example.resource.personal-data.person-without-account.md +27 -0
- package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +152 -0
- package/dist/knowledge/references/example.resource.ui-behavior.filter-presets.md +15 -0
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +8 -0
- package/dist/knowledge/references/example.views.app-level.home-definition.md +13 -0
- package/dist/knowledge/references/example.views.chart-definition.shared.md +83 -0
- package/dist/knowledge/references/experience-plan.config.md +60 -7
- package/dist/knowledge/references/market.context-block.builder.md +1 -1
- package/dist/knowledge/references/market.snapshot.validation.md +1 -1
- package/dist/knowledge/references/placement-plan.config.md +43 -0
- package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -2
- package/dist/knowledge/references/requirements.non-functional-requirement.config.md +2 -0
- package/dist/knowledge/references/requirements.references.conventions.md +1 -1
- package/dist/knowledge/references/requirements.snapshot.config.md +57 -1
- package/dist/knowledge/references/requirements.snapshot.validation.md +35 -1
- package/dist/knowledge/references/saas.backend.audit-logs.log-event.md +63 -0
- package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +60 -0
- package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +156 -0
- package/dist/knowledge/references/saas.backend.email.send.md +77 -0
- package/dist/knowledge/references/saas.backend.notifications.operation-email-template-ref.md +60 -0
- package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +7 -1
- package/dist/knowledge/references/saas.data-seeding.computed-entry.md +43 -0
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +14 -2
- package/dist/knowledge/references/saas.data-seeding.row-reference.md +93 -0
- package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +124 -0
- package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +316 -0
- package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +106 -0
- package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +60 -0
- package/dist/knowledge/references/saas.frontend.resource-label-params.md +52 -0
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +47 -18
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -1
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destination-roles.md +25 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +2 -2
- package/dist/knowledge/references/saas.models.audit.trail-config.md +45 -0
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +5 -3
- package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +81 -2
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +26 -0
- package/dist/knowledge/references/saas.models.roles.definition.md +61 -0
- package/dist/knowledge/references/saas.models.roles.organization-defaults.md +97 -0
- package/dist/knowledge/references/saas.public-runtime.contract.md +26 -0
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +10 -0
- package/dist/knowledge/references/saas.website.astro.bridge.md +10 -0
- package/dist/knowledge/references/saas.website.astro.label-loader.md +12 -0
- package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +14 -1
- package/dist/knowledge/references/saas.website.astro.site-context.md +13 -0
- package/dist/knowledge/references/saas.website.blog.bridge.md +4 -0
- package/dist/knowledge/references/saas.website.config.site-context-loader.md +3 -0
- package/dist/knowledge/references/saas.website.factories.define-section.md +4 -0
- package/dist/knowledge/references/saas.website.legal.public-document-links.md +76 -0
- package/dist/knowledge/references/saas.website.page-manifest.schema.md +12 -3
- package/dist/knowledge/references/saas.website.page-sections.component.md +72 -0
- package/dist/knowledge/references/saas.website.root-config.seo.md +2 -1
- package/dist/knowledge/references/saas.website.runtime.context.md +7 -0
- package/dist/knowledge/references/saas.website.sections.definition-schema.md +11 -0
- package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +2 -0
- package/dist/knowledge/references/website-plan.config.md +26 -0
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +13 -0
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +7 -0
- package/dist/knowledge/references/zod.decorators.document-sequence.md +65 -0
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +1 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +21 -0
- package/dist/knowledge/references/zod.factories.bigdecimal.md +1 -0
- package/dist/knowledge/references/zod.factories.code.md +1 -0
- package/dist/knowledge/references/zod.factories.duration.md +1 -0
- package/dist/knowledge/references/zod.factories.money.md +1 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +374 -1
- package/dist/knowledge/registries/playbooks.json +76 -28
- package/dist/knowledge/registries/source-tags.json +1513 -898
- package/dist/knowledge/rules/live-context-door.md +5 -2
- package/dist/knowledge/skills/INDEX.md +5 -2
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +16 -3
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +14 -3
- package/dist/knowledge/skills/application-roles-authoring/SKILL.md +158 -0
- package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +169 -0
- package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +63 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +6 -1
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +256 -9
- package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +42 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +220 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +5 -0
- package/dist/knowledge/skills/brand-name-screening/SKILL.md +178 -0
- package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +466 -0
- package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +87 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +7 -3
- package/dist/knowledge/skills/config-app-shell/SKILL.md +58 -5
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +461 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +80 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +28 -6
- package/dist/knowledge/skills/config-navigation/SKILL.md +14 -3
- package/dist/knowledge/skills/config-saas/SKILL.md +56 -15
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +65 -2
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +62 -2
- package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +81 -2
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +6 -1
- package/dist/knowledge/skills/configure-billing/SKILL.md +18 -4
- package/dist/knowledge/skills/email-add-template/SKILL.md +28 -6
- package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +1 -1
- package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +128 -0
- package/dist/knowledge/skills/email-add-template/references/framework-operation-email-template-ref-api.md +99 -0
- package/dist/knowledge/skills/engine-component-registration/SKILL.md +6 -1
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +21 -8
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -2
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +18 -4
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +11 -3
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -1
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +8 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +19 -5
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +10 -2
- package/dist/knowledge/skills/inbound-channels/SKILL.md +2 -2
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +6 -1
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +17 -2
- package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +122 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +11 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +9 -2
- package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +10 -2
- package/dist/knowledge/skills/market-alternatives/SKILL.md +10 -2
- package/dist/knowledge/skills/market-authoring-overview/SKILL.md +10 -2
- package/dist/knowledge/skills/market-category/SKILL.md +21 -7
- package/dist/knowledge/skills/market-channels/SKILL.md +6 -1
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +22 -4
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +12 -2
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +21 -11
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +11 -6
- package/dist/knowledge/skills/market-icp/SKILL.md +10 -2
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +6 -1
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +6 -1
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
- package/dist/knowledge/skills/market-persona/SKILL.md +14 -3
- package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +6 -1
- package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +10 -2
- package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +6 -1
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -4
- package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1 -1
- package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +6 -1
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +26 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +7 -1
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +10 -0
- package/dist/knowledge/skills/module-relationships/SKILL.md +37 -8
- package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +4 -2
- package/dist/knowledge/skills/provider-address-lookup/SKILL.md +14 -3
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +6 -1
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +14 -3
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +10 -2
- package/dist/knowledge/skills/resource-add-field/SKILL.md +10 -2
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +46 -17
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +14 -2
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +26 -0
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +29 -3
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +19 -4
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +5 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +103 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +135 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +26 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +26 -7
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +10 -2
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +46 -17
- package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +2 -2
- package/dist/knowledge/skills/resource-retention-binding/SKILL.md +5 -1
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +15 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +569 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +358 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +8 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +21 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +7 -2
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +13 -0
- package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +153 -0
- package/dist/knowledge/skills/resource-status-lifecycle/references/commercial-documents.md +46 -0
- package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +198 -0
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +30 -4
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +157 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +101 -19
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +202 -39
- package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +67 -0
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +154 -4
- package/dist/knowledge/skills/seeding-authoring/references/seed-row-overlay.md +22 -0
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +7 -1
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +43 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +2 -2
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +6 -1
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +10 -0
- package/dist/knowledge/skills/spec-component-update/SKILL.md +10 -2
- package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +2 -2
- package/dist/knowledge/skills/spec-family-update/SKILL.md +71 -66
- package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +1 -1
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +30 -10
- package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +28 -0
- package/dist/knowledge/skills/spec-update-after-change/SKILL.md +22 -5
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +6 -1
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -2
- package/dist/knowledge/skills/views-app-level/SKILL.md +13 -3
- package/dist/knowledge/skills/views-app-level/references/application-home.md +56 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +221 -37
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +22 -5
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -1
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +32 -2
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +16 -3
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +4 -0
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +7 -1
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +13 -1
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +14 -2
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +13 -1
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +6 -1
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +19 -1
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +55 -18
- package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +98 -0
- package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +8 -11
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +100 -8
- package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +3 -0
- package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +6 -1
- package/dist/knowledge/skills/website-section-contact/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-cta/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-faq/SKILL.md +21 -1
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +21 -1
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +25 -2
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-hero/SKILL.md +33 -10
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +21 -1
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +27 -2
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +16 -4
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +11 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +16 -1
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +2 -1
- package/dist/knowledge/topic-index.json +1590 -292
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
|
@@ -25,6 +25,7 @@ empty or fails.
|
|
|
25
25
|
| `wildo context workspace map\|get\|related` | the application's own code, by resource — its fields, operations and relationships — instead of the whole registry |
|
|
26
26
|
| `wildo context journey` | where the application's creation stands: what is eligible, what is unmet, and what each run took and spent — per round and per child for a composite, with the rounds that began from a state an earlier round had already begun from |
|
|
27
27
|
| `wildo context coherence` | what disagrees across the landed specification families |
|
|
28
|
+
| `wildo context launch-blockers` | what still stands between the application and a real user — each open compliance decision (an undeclared part of `operatorComplianceIdentity`, an unanswered governance question, an undeclared retention class, undeclared subject-data recipients, sign-up acceptance) and a brand name its trademark screening has not cleared, where it is decided and what settles it. It marks and never blocks; a settled item is gone on the next read |
|
|
28
29
|
| `wildo context health` | whether the companion is answering at all |
|
|
29
30
|
|
|
30
31
|
## Commands that ask the running application backend
|
|
@@ -83,8 +84,10 @@ prompt, and from a background monitor); the detail is always read with these ver
|
|
|
83
84
|
|---|---|
|
|
84
85
|
| `wildo creation feed` | what happened (a run completed or was refused, a dispatch settled), what is asked of you, what could come next |
|
|
85
86
|
| `wildo creation feed --follow --exit-on-change` | waits, and returns at the first new event — the loop to run after starting work |
|
|
86
|
-
| `wildo creation questions` | every question waiting on an answer, each with the exact command that answers it |
|
|
87
|
-
| `wildo creation answer <id> --revision <r> …` | answers, declines or cancels one of them. Every answer records who gave it: `--person` for the person's, `--derived <ref>=<value> --derived-by agent:<name>` for one the application's own files settle — the verb refuses an unattributed answer from inside an agent session |
|
|
87
|
+
| `wildo creation questions` | every question waiting on an answer, each with the exact command that answers it — and, apart and not counted, the assumed answers the person may revisit |
|
|
88
|
+
| `wildo creation answer <id> --revision <r> …` | answers, declines or cancels one of them. Every answer records who gave it: `--person` for the person's, `--derived <ref>=<value> --derived-by agent:<name>` for one the application's own files settle, `--assumed "<value>" --rationale "<why>"` for a proposal the person kept because they did not know — the verb refuses an unattributed answer from inside an agent session |
|
|
89
|
+
| `wildo creation propose <playbookRef> [--question <ref>]` | proposes answers to interview questions the person does not know; writes nothing |
|
|
90
|
+
| `wildo creation depth [simple\|detailed]` | reads or records how detailed this application's interviews are |
|
|
88
91
|
|
|
89
92
|
Check `wildo creation questions` whenever work you started through the companion seems not to move:
|
|
90
93
|
a run waiting on an answer looks exactly like a slow one. The `/wildo:run` and `/wildo:build` commands carry the loop.
|
|
@@ -38,6 +38,7 @@ describes adding or changing its capabilities.
|
|
|
38
38
|
| **`resource-add-resource`** **(orchestrator)** — scaffold a new resource across shared-lib, app, specs | "scaffold a new resource", "add a reviews resource", "create a projects entity", "new persisted resource type" |
|
|
39
39
|
| **`resource-add-module`** **(orchestrator)** — scaffold a new module folder across shared-lib, app, specifications, backend-api | "add a new module", "scaffold a billing module folder", "new bounded context", "create a feature area" |
|
|
40
40
|
| **`resource-schema-authoring`** — edit Zod schemas with structural decorators | "edit the Zod schema for tasks", "change the shape of a field", "use schema family for variants", "tweak lifecycle flags on a field" |
|
|
41
|
+
| **`resource-status-lifecycle`** — give a resource states the engine enforces: one operation per transition (`enabledCondition` + `basicPrefixOperation` + `authoritativeFields`), the status excluded from UPDATE, the record frozen once final, and a conversion's write in one transaction; for a quote, order or invoice, the parts that make it a trustworthy commercial document | "accept a quote", "issue the invoice", "mark it paid", "lock it after it is sent", "only allow X when Y", "convert the quote into a job" |
|
|
41
42
|
| **`resource-config-wiring`** — edit `*.resources-config.ts` for operations, variants, relationships, roles | "wire a new operation variant", "add a custom operation to a resource", "configure resource relationships in registry", "change operation roles" |
|
|
42
43
|
| **`resource-retention-binding`** — bind a resource to a retention class and start point so expired rows are deleted on schedule | "delete closed tickets after 90 days", "how long do we keep X", "keep invoices ten years", "purge old logs", "retention period for this resource" |
|
|
43
44
|
| **`resource-ui-behavior`** — edit `*.ui-behavior.tsx` for layouts, display/edit modes, enum UI | "change how the priority field renders", "tweak the tasks list UI behavior", "add display-mode badge-with-colors", "conditional visibility on a field" |
|
|
@@ -124,7 +125,7 @@ registrations).
|
|
|
124
125
|
| **`module-relationships`** — wire cross-resource relationships and FK fields | "wire an FK between tasks and users", "add cross-resource relationship", "define assignee on tasks", "relate two resources" |
|
|
125
126
|
| **`module-companion-exports`** — update companion export entrypoints for cross-package specs and registries | "expose module specs to companion", "fix companion introspection after moving specs", "add module companion export", "companion missing registry" |
|
|
126
127
|
| **`engine-component-registration`** — register custom frontend components in the component registration map | "register a custom React component", "expose a component to ui-behavior", "add component to registration map", "custom component key for spec" |
|
|
127
|
-
| **`engine-product-definitions`** — maintain application product,
|
|
128
|
+
| **`engine-product-definitions`** — maintain application product, feature, and milestone registries (roles: `application-roles-authoring`) | "update milestone registry", "change features registry", "product taxonomy edit" |
|
|
128
129
|
| **`milestones-and-celebrations`** — declare milestones, choose how each celebrates (level vs mode), show progress with the tracker's variants, and replace the celebration's look with your own component | "add a milestone", "celebrate the first X", "the celebration blocks the user", "use confetti instead of the popup", "show progress on the dashboard", "brand the celebration", "different animation per milestone" |
|
|
129
130
|
| **`guidance-onboarding-authoring`** — embedded onboarding documents (`EmbedOnboarding`) and triggered guidance flows: banners, tours, checklists, and surveys whose answer is saved to a resource field | "add onboarding", "welcome message on the dashboard", "getting-started checklist", "show a tip after the first X", "add a product tour", "ask the user a question and save the answer", "the onboarding never appears" |
|
|
130
131
|
|
|
@@ -225,6 +226,7 @@ design-system color TOKENS (`config-design-system`).
|
|
|
225
226
|
| Skill | Trigger phrases |
|
|
226
227
|
| ------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
227
228
|
| **`brand-logo-authoring`** — author the `BrandSnapshot` brief (brand name, logo direction, visual tone) that drives logo + brand-image generation | "give the app a logo", "design our logo", "author the brand identity", "set the logo direction", "we need a brand mark", "generate the app logo", "what should our logo look like", "define the visual identity / visual tone" |
|
|
229
|
+
| **`brand-name-screening`** — propose brand names and run a minimal trademark screening of each (registers, Nice classes, jurisdictions, competitor collisions) into the `BrandNameScreening` the creator chooses the name from | "suggest names for the app", "propose a brand name", "is this name trademarked", "check the name against EUIPO", "screen our name", "can we use the name X", "the name conflicts with a trademark" |
|
|
228
230
|
|
|
229
231
|
### Backend — DI, controllers, custom operations
|
|
230
232
|
|
|
@@ -244,6 +246,7 @@ Anything that changes **backend-api code** beyond schema-driven CRUD.
|
|
|
244
246
|
| **`backend-custom-operation`** — implement or modify default/custom resource operations server-side | "change server-side create logic for tasks", "add custom operation handler", "override default update behavior", "custom backend logic for an operation" |
|
|
245
247
|
| **`inbound-channels`** — declare an inbound handler (`BackendDomainModule.inboundHandlers`): a webhook handler, engine-verified (Svix / HMAC header), or an EMAIL channel handler gated on the sender's assurance, answering on the thread; receiving email (shared domain, organization domains proven by a DNS TXT record, client mailboxes); stored once, scope-pinned with declared roles, retried, replayable | "receive a webhook from X", "add an inbound webhook endpoint", "handle Svix / Resend webhooks", "a client's system should create records in our app", "verify an HMAC-signed callback", "replay a failed webhook", "clients should email documents to a case", "turn incoming email into tickets", "reply to the sender automatically", "let each organization receive mail at its own domain", "give each client a mailbox on our domain" |
|
|
246
248
|
| **`rate-limit-authoring`** — author per-endpoint rate limits via the declarative `rateLimit?` policy on resource-operation variants, or call `RateLimitBackendService.checkPolicy(...)` from a custom controller | "rate-limit this endpoint", "add a per-IP cap", "throttle the magic-link / OTP / password-reset / register flow", "the endpoint is being abused", "tune the OAuth / SCIM token quota", "the headers don't show the right `X-RateLimit-Reset`" |
|
|
249
|
+
| **`application-roles-authoring`** — declare the application's own user roles (`shared-lib/src/engine/roles.ts`), offer each on its organization types (`availableOrgRoles`) and name it in the `roles` of every operation it unlocks; roles are configuration, never a resource of role names or permissions | "office and field users see different things", "add a technician role", "only admins can issue invoices", "permissions per role", "different user roles see different screens", "who can do what" |
|
|
247
250
|
| **`authorization-unit-narrowing`** — declare a resource confined to the organization UNIT (department / region / team) a member holds a role in, via the `organizationUnitNarrowing` startup opt-in; confines reads and writes without touching the organization scope | "scope this resource to a department", "each team should only see their own records", "regional managers should only manage their region's data", "restrict projects to the user's business unit", "add unit-level permissions", "why can a unit manager see every record" |
|
|
248
251
|
| **`service-provider-relationships`** — let one organization's people work inside other organizations (an agency, a practice) under a relationship each client proposes or accepts, can confine to some of its teams, and can end on the next request; `servesAsProvider` on an organization type | "let an agency work in our customers' workspaces", "our consultants need access to client accounts", "managed service provider access", "limit the agency to one department", "how does a client revoke an outside firm" |
|
|
249
252
|
|
|
@@ -292,7 +295,7 @@ surprises you.
|
|
|
292
295
|
| Skill | Trigger phrases |
|
|
293
296
|
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
294
297
|
| **`infra-environment-config`** — edit infra/environment configuration (URLs, secret refs, endpoints) | "change local environment config", "add deployed environment target", "wire secret reference in infra", "update dev stack URLs" |
|
|
295
|
-
| **`local-environment-bootstrap`** — drive `wildo setup` / `wildo local init/reinit/dev/up/down/reset` / `wildo config sync` to initialize, repair, verify, start, and reset the complete local project generation | "initialize my project", "repair broken platform or Mongo state", "my Mongo volume was reset", "reinitialize from empty data", "set up my local stack", "regenerate runtime env files", "reset my local data" |
|
|
298
|
+
| **`local-environment-bootstrap`** — drive `wildo setup` / `wildo local init/reinit/dev/up/down/reset` / `wildo config sync` to initialize, repair, verify, start, and reset the complete local project generation | "initialize my project", "repair broken platform or Mongo state", "my Mongo volume was reset", "reinitialize from empty data", "set up my local stack", "regenerate runtime env files", "reset my local data", "a dev server says a generated file must be regenerated", "is this generated file stale" |
|
|
296
299
|
| **`frontend-cdn-publish`** — configure the OPT-IN `cdn?[serviceKey]` block + `wildo frontend publish` to serve a frontend from object storage + a CDN (Cloudflare live adapter or GENERIC) instead of its nginx pod | "put the website on a CDN", "serve docs from a CDN instead of nginx", "configure CDN publishing", "set up Cloudflare for the app", "wildo frontend publish", "upload the frontend dist to S3 + CDN", "re-home CSP to the edge" |
|
|
297
300
|
| **`application-database-migrations`** — generate, review and apply PostgreSQL migrations so the database matches the resource model (PostgreSQL-backed applications only) | "I added a resource and the backend won't start", "table does not exist", "postgresql_table_schema_mismatch", "generate a migration", "wildo db generate", "the schema plan is out of sync", "do I need a migration for this field", "my migration was refused" |
|
|
298
301
|
|
|
@@ -443,14 +443,27 @@ source-backed in `references/framework-documentation-chapters-api.md`.
|
|
|
443
443
|
|
|
444
444
|
| Invariant | Command |
|
|
445
445
|
|---|---|
|
|
446
|
-
| No framework/internal vocabulary in consumer prose |
|
|
446
|
+
| No framework/internal vocabulary in consumer prose | see the commands below the table |
|
|
447
447
|
| No generic related labels | `rg -n "Related documentation" specifications/src/technical-documentation/index.ts` |
|
|
448
|
-
| No endpoint inventory disguised as a guide |
|
|
448
|
+
| No endpoint inventory disguised as a guide | see the commands below the table |
|
|
449
449
|
| No hand-typed API-reference URL in a body | `rg -n "\]\(/api" specifications/src/technical-documentation/index.ts` prints nothing |
|
|
450
|
-
| Every chapter key is planned |
|
|
450
|
+
| Every chapter key is planned | run the command below the table; it prints nothing |
|
|
451
451
|
| No hand-authored generated output | `git diff --name-only -- technical-doc/src/generated` changes only after `wildo docs publish` |
|
|
452
452
|
| Every chapter materialized | `ls technical-doc/src/generated/consumer-documentation/docusaurus/docs/guides/` |
|
|
453
453
|
|
|
454
|
+
```bash
|
|
455
|
+
# No framework/internal vocabulary in consumer prose
|
|
456
|
+
rg -n "Wildo|framework-capabilit|projectionRef|app-creator" specifications/src/technical-documentation/index.ts
|
|
457
|
+
|
|
458
|
+
# No endpoint inventory disguised as a guide
|
|
459
|
+
rg -n "^(GET|POST|PUT|PATCH|DELETE) /" specifications/src/technical-documentation/index.ts
|
|
460
|
+
```
|
|
461
|
+
|
|
462
|
+
```bash
|
|
463
|
+
# Every chapter key is planned
|
|
464
|
+
comm -23 <(rg -o -N "chapter-[a-z0-9-]+" specifications/src/technical-documentation/index.ts | sort -u) <(rg -o -N "chapter-[a-z0-9-]+" specifications/src/documentation-plan/index.ts | sort -u)
|
|
465
|
+
```
|
|
466
|
+
|
|
454
467
|
## Common rationalizations
|
|
455
468
|
|
|
456
469
|
| Rationalization | Reality |
|
|
@@ -194,9 +194,20 @@ narrow, and both limits are worth knowing:
|
|
|
194
194
|
|---|---|
|
|
195
195
|
| The plan and the model agree (exits 0) | `wildo db diff --check` |
|
|
196
196
|
| A lockfile exists at all — without one, no migration has ever been accepted | `ls backend-api/migrations/schema-plan.lock.json` |
|
|
197
|
-
| Every migration folder actually contains SQL (an empty folder applies nothing) |
|
|
198
|
-
| No destructive statement is missing its acknowledgement |
|
|
199
|
-
| The lockfile moved in the same commit as a new migration |
|
|
197
|
+
| Every migration folder actually contains SQL (an empty folder applies nothing) | see the commands below the table |
|
|
198
|
+
| No destructive statement is missing its acknowledgement | see the commands below the table |
|
|
199
|
+
| The lockfile moved in the same commit as a new migration | see the commands below the table |
|
|
200
|
+
|
|
201
|
+
```bash
|
|
202
|
+
# Every migration folder actually contains SQL (an empty folder applies nothing)
|
|
203
|
+
comm -23 <(ls -d backend-api/migrations/*/ | xargs -n1 basename | sort) <(rg -l --no-messages "" backend-api/migrations/*/migration.sql | xargs -n1 dirname | xargs -n1 basename | sort)
|
|
204
|
+
|
|
205
|
+
# No destructive statement is missing its acknowledgement
|
|
206
|
+
rg -l "^drop table|drop column" backend-api/migrations/*/migration.sql | xargs -r rg --files-without-match "wildo:acknowledge-destructive"
|
|
207
|
+
|
|
208
|
+
# The lockfile moved in the same commit as a new migration
|
|
209
|
+
git show --name-only HEAD | rg "schema-plan.lock.json"
|
|
210
|
+
```
|
|
200
211
|
|
|
201
212
|
## Common Rationalizations
|
|
202
213
|
|
|
@@ -0,0 +1,158 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: application-roles-authoring
|
|
3
|
+
description: Declare the application's own user roles (office staff, field technicians, accountants, read-only reviewers) and make them decide who may do what — the role table, the organization types that offer each role, and the role list of every operation. Use when the user says "office and field users see different things", "add a technician role", "only admins can issue invoices", "different user roles see different screens", "permissions per role", "who can do what", "a role that can only read", or when a requirement names groups of users with different access.
|
|
4
|
+
user-invocable: false
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Application Roles
|
|
8
|
+
|
|
9
|
+
### Target Application Framing
|
|
10
|
+
|
|
11
|
+
This knowledge is for configuring behavior in the target application.
|
|
12
|
+
Wildo is the framework surface being used, not the product being built.
|
|
13
|
+
|
|
14
|
+
Read and apply these patterns from the application-developer point of view:
|
|
15
|
+
|
|
16
|
+
- how the application should configure the relevant app-level file
|
|
17
|
+
- how the application should use framework-provided factories, enums, and helpers
|
|
18
|
+
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
19
|
+
|
|
20
|
+
|
|
21
|
+
## Overview
|
|
22
|
+
|
|
23
|
+
An application controls who may do what with **roles**. The engine ships the core organization roles
|
|
24
|
+
(`ORG_OWNER`, `ORG_ADMIN`, `ORG_MANAGER`, `ORG_MEMBER`, `ORG_GUEST`) and the application adds its own.
|
|
25
|
+
Every operation variant of every resource names the roles allowed to call it, and the engine refuses
|
|
26
|
+
everyone else before the operation runs.
|
|
27
|
+
|
|
28
|
+
A role does something only when it appears in three places: the role table, the organization type
|
|
29
|
+
that offers it, and the operations it unlocks. This skill is those three edits. The boundary it keeps:
|
|
30
|
+
**roles are configuration, never data.** A resource holding role names, permission lists or
|
|
31
|
+
"user ↔ role" assignments is read by nothing in the engine — it looks like access control and enforces
|
|
32
|
+
none of it.
|
|
33
|
+
|
|
34
|
+
## App Paths
|
|
35
|
+
|
|
36
|
+
| Surface | Glob (relative to app root) |
|
|
37
|
+
|---|---|
|
|
38
|
+
| The application's role table | `shared-lib/src/engine/roles.ts` (`CUSTOM_ROLES_CONFIGURATION`) |
|
|
39
|
+
| Which roles an organization offers | `wildo.saas.config.ts` → `organizationTypes.<type>.availableOrgRoles` / `defaultMemberRole` |
|
|
40
|
+
| Who may call each operation | `shared-lib/src/modules/<module>/resources/<resource>/<resource>.resources-config.ts` (`roles` on each variant) |
|
|
41
|
+
| Role specifications (purpose, labels) | `specifications/src/engine/roles/<role>.role.specification.ts`, spread into `roleSpecifications` in `specifications/src/companion-exports.ts` |
|
|
42
|
+
|
|
43
|
+
## When to Use
|
|
44
|
+
|
|
45
|
+
- A requirement or a person names groups of users with different access ("office" and "field",
|
|
46
|
+
"accountant", "viewer", "dispatcher").
|
|
47
|
+
- An operation must be refused to some members ("only admins can delete", "technicians cannot see
|
|
48
|
+
invoices").
|
|
49
|
+
- Someone proposes an `access-role`, `permission` or `user-role-assignment` resource. Stop and use this
|
|
50
|
+
skill instead.
|
|
51
|
+
|
|
52
|
+
## When NOT to Use
|
|
53
|
+
|
|
54
|
+
- **Separating tenants from each other** — the organization scope already does that for every
|
|
55
|
+
resource.
|
|
56
|
+
- **Confining a member to their department's or region's rows** — that is row scope within a role:
|
|
57
|
+
`authorization-unit-narrowing`.
|
|
58
|
+
- **Granting a role from your own code path** (a custom resource whose `roles` field a caller sets) —
|
|
59
|
+
the role-ceiling gate in `resource-config-wiring` → `references/framework-role-ceiling-api.md`.
|
|
60
|
+
- **Labelling and describing a role** once it exists — `spec-family-update`.
|
|
61
|
+
|
|
62
|
+
## Workflow
|
|
63
|
+
|
|
64
|
+
### Step 1 — Decide the roles from the user groups, reusing the core ones
|
|
65
|
+
|
|
66
|
+
For each group the requirements name, decide which existing role already fits before declaring one.
|
|
67
|
+
The usual answer: the broadest internal group holds `ORG_MEMBER`; a narrower group gets a custom role.
|
|
68
|
+
Read `references/framework-application-roles-api.md` for the chain. A custom role inherits from the
|
|
69
|
+
role whose access it should start from — `ORG_GUEST` for "almost nothing", `ORG_MEMBER` for
|
|
70
|
+
"everything a member has, plus".
|
|
71
|
+
|
|
72
|
+
### Step 2 — Declare each custom role in `shared-lib/src/engine/roles.ts`
|
|
73
|
+
|
|
74
|
+
One entry per role, keyed by its name, with `relatedPrimaryScope` `ORGANIZATIONS` (a role inside one
|
|
75
|
+
organization) or `APPLICATION` (application-wide). Any other scope is ignored at startup and the role
|
|
76
|
+
grants nothing.
|
|
77
|
+
|
|
78
|
+
### Step 3 — Offer it on the organization type
|
|
79
|
+
|
|
80
|
+
Add the role to `organizationTypes.<type>.availableOrgRoles` in `wildo.saas.config.ts`. Omitted, the
|
|
81
|
+
list defaults to owner, admin and member only, and nobody can be given the new role. Set
|
|
82
|
+
`defaultMemberRole` if new members should start in it. Apply the change with
|
|
83
|
+
`wildo config reapply-declaration`, or restart with `wildo local dev`.
|
|
84
|
+
|
|
85
|
+
### Step 4 — Name it on every operation it unlocks
|
|
86
|
+
|
|
87
|
+
In each affected `*.resources-config.ts`, set `roles` on the operation variants (`resource-config-wiring`).
|
|
88
|
+
A caller holding a role OR any role down its inheritance qualifies, so `ORG_MEMBER` admits members,
|
|
89
|
+
managers, admins and owners. Name the custom role explicitly wherever its holders are admitted, and
|
|
90
|
+
name both when administrators must also qualify for a custom role's operation. When a group may change
|
|
91
|
+
only part of a record (technicians record progress, the office edits everything), give that group its
|
|
92
|
+
own custom operation over those fields (`backend-custom-operation`) instead of admitting it to the full
|
|
93
|
+
UPDATE.
|
|
94
|
+
|
|
95
|
+
### Step 5 — Specify and label it
|
|
96
|
+
|
|
97
|
+
Author a role specification (`spec-family-update`) so the purpose grounds the role's labels, and make
|
|
98
|
+
sure `roleSpecifications` in `specifications/src/companion-exports.ts` spreads the application's role
|
|
99
|
+
specifications beside `engineRoleSpecifications`. Then regenerate labels (`i18n-label-generation`).
|
|
100
|
+
People receive the role on the engine's members screen and through invitations: there is nothing to
|
|
101
|
+
build for assignment.
|
|
102
|
+
|
|
103
|
+
## Worked Example
|
|
104
|
+
|
|
105
|
+
The complete office/field wiring — role table, organization type, operation role sets — is in
|
|
106
|
+
`references/office-and-field-worked-example.md`, with what each line earns.
|
|
107
|
+
|
|
108
|
+
## References
|
|
109
|
+
|
|
110
|
+
- `references/framework-application-roles-api.md` — source-backed role definition and the engine's organization roles with their inheritance chain.
|
|
111
|
+
- `references/office-and-field-worked-example.md` — the three places a role must appear, for office staff and field technicians.
|
|
112
|
+
|
|
113
|
+
## Verification
|
|
114
|
+
|
|
115
|
+
- [ ] Every custom role in `roles.ts` has `relatedPrimaryScope` `ORGANIZATIONS` or `APPLICATION`.
|
|
116
|
+
- [ ] Every custom organization role is in `availableOrgRoles` of each organization type that should offer it.
|
|
117
|
+
- [ ] Every custom role is named in at least one operation's `roles`.
|
|
118
|
+
- [ ] No resource stores roles, permissions or role assignments.
|
|
119
|
+
- [ ] Each role has a specification and labels.
|
|
120
|
+
|
|
121
|
+
### Grep invariants
|
|
122
|
+
|
|
123
|
+
```bash
|
|
124
|
+
# the declared roles
|
|
125
|
+
rg -n "role: '" shared-lib/src/engine/roles.ts
|
|
126
|
+
# each declared role is offered (repeat per role name)
|
|
127
|
+
rg -n "'FIELD_TECHNICIAN'" wildo.saas.config.ts
|
|
128
|
+
# each declared role is named on an operation (repeat per role name)
|
|
129
|
+
rg -l "'FIELD_TECHNICIAN'" shared-lib/src/modules
|
|
130
|
+
# a resource modelling roles or permissions as data (must return empty)
|
|
131
|
+
rg -li "permission|roleassignment|accessrole" shared-lib/src/modules --glob '*.schemas.ts'
|
|
132
|
+
```
|
|
133
|
+
|
|
134
|
+
## Common Rationalizations
|
|
135
|
+
|
|
136
|
+
| Rationalization | Reality |
|
|
137
|
+
|---|---|
|
|
138
|
+
| "Let the organization define its own roles in a settings screen" | The engine has no runtime role table: roles are declared in `roles.ts` at build time. A role resource edited at runtime is read by no authorization check. |
|
|
139
|
+
| "I'll add a permissions enum and check it later" | Nothing checks it later. The engine gates operations on `roles` alone, so the enum ships as a control that enforces nothing. |
|
|
140
|
+
| "The field role should inherit ORG_MEMBER so technicians can work" | Then technicians hold everything office staff hold. Inherit `ORG_GUEST` and name the field role on the operations it needs. |
|
|
141
|
+
| "ORG_ADMIN inherits everything, so admins pass my custom role's operations" | The chain is linear and a custom role is not on it. Name `ORG_MEMBER` (or `ORG_ADMIN`) beside the custom role where administrators must qualify. |
|
|
142
|
+
| "Hiding the menu entry is enough" | Hiding is not refusing. The operation's `roles` is what the engine enforces; navigation only follows it. |
|
|
143
|
+
|
|
144
|
+
## Red Flags
|
|
145
|
+
|
|
146
|
+
- A custom role in `roles.ts` that no operation names (catch with the **named on an operation** grep).
|
|
147
|
+
- A custom organization role missing from `availableOrgRoles` (catch with the **offered** grep).
|
|
148
|
+
- A resource whose schema stores roles, permissions or assignments (catch with the **modelling roles as data** grep — must return empty).
|
|
149
|
+
- A custom role inheriting `ORG_MEMBER` or higher when the requirement narrows access (catch by reading `roles.ts` against Step 1).
|
|
150
|
+
- Every operation of a resource on the same single role while the requirements name several groups (catch by reading each `*.resources-config.ts` touched in Step 4).
|
|
151
|
+
|
|
152
|
+
## Related Skills
|
|
153
|
+
|
|
154
|
+
- `resource-config-wiring` — where each operation variant's `roles` is written.
|
|
155
|
+
- `authorization-unit-narrowing` — confine a role's holders to their unit's rows.
|
|
156
|
+
- `spec-family-update` — role specifications and their wording.
|
|
157
|
+
- `i18n-label-generation` — generate the role labels.
|
|
158
|
+
- `config-saas` — the rest of `wildo.saas.config.ts`, including organization types.
|
|
@@ -0,0 +1,169 @@
|
|
|
1
|
+
# Framework — Application Roles
|
|
2
|
+
|
|
3
|
+
The contracts an application's own roles are declared with, and the organization roles the engine
|
|
4
|
+
ships. Read this before declaring a role, choosing what it inherits, or naming roles on an operation.
|
|
5
|
+
|
|
6
|
+
- `RoleDefinition` / `RolesConfiguration` — the shape of `CUSTOM_ROLES_CONFIGURATION`, and the three
|
|
7
|
+
places a role must appear before it does anything.
|
|
8
|
+
- `DEFAULT_ORGANIZATION_ROLES` — the core organization roles and their linear inheritance chain, plus
|
|
9
|
+
the handler-only and delegated roles you never assign.
|
|
10
|
+
|
|
11
|
+
## The role definition
|
|
12
|
+
|
|
13
|
+
## Import Origins
|
|
14
|
+
|
|
15
|
+
- `@wildo-ai/saas-models`
|
|
16
|
+
|
|
17
|
+
## Source Excerpts
|
|
18
|
+
|
|
19
|
+
### Origin Package: `@wildo-ai/saas-models`
|
|
20
|
+
|
|
21
|
+
```typescript
|
|
22
|
+
*
|
|
23
|
+
* One role an application declares, and the table of them. Import from `@wildo-ai/saas-models`
|
|
24
|
+
* (`RolesConfiguration`, `CORE_ORG_ROLES`, `CORE_APP_ROLES`, `ResourcePrimaryScope`).
|
|
25
|
+
*
|
|
26
|
+
* An application's own roles live in ONE place: `CUSTOM_ROLES_CONFIGURATION` in
|
|
27
|
+
* `shared-lib/src/engine/roles.ts`, a `RolesConfiguration` keyed by the role's name. Nothing else
|
|
28
|
+
* declares a role — never a resource holding role names or permission lists, which the engine does not
|
|
29
|
+
* read.
|
|
30
|
+
*
|
|
31
|
+
* - `role` — the role's name, equal to its key. Any string; prefer a stable upper-snake name
|
|
32
|
+
* (`FIELD_TECHNICIAN`).
|
|
33
|
+
* - `inheritFrom` — the role whose access this one also receives. A holder of a role satisfies every
|
|
34
|
+
* operation naming that role OR any role up its `inheritFrom` chain. The core organization chain is
|
|
35
|
+
* linear: `ORG_OWNER → ORG_ADMIN → ORG_MANAGER → ORG_MEMBER → ORG_GUEST`. So a custom role inheriting
|
|
36
|
+
* `ORG_MEMBER` is NOT held by an `ORG_ADMIN`: to let administrators do what the custom role does,
|
|
37
|
+
* name both roles on the operation.
|
|
38
|
+
* - `isSystemRole` — `false` for every role an application declares.
|
|
39
|
+
* - `relatedPrimaryScope` — `ResourcePrimaryScope.ORGANIZATIONS` for a role a member holds inside one
|
|
40
|
+
* organization, `ResourcePrimaryScope.APPLICATION` for an application-wide role. Any other scope is
|
|
41
|
+
* ignored at startup with a warning, and the role grants nothing.
|
|
42
|
+
*
|
|
43
|
+
* Declaring a role is one of three steps. An organization role must also be listed in
|
|
44
|
+
* `organizationTypes.<type>.availableOrgRoles` of `wildo.saas.config.ts` (or no member can be given
|
|
45
|
+
* it), and it must be named in the `roles` of the operation variants it unlocks (or holding it changes
|
|
46
|
+
* nothing). People receive it through the engine's members screen and invitations.
|
|
47
|
+
*/
|
|
48
|
+
export const RoleDefinitionSchema = z.object({
|
|
49
|
+
role: RolesSchema,
|
|
50
|
+
inheritFrom: RolesSchema.optional(),
|
|
51
|
+
isSystemRole: z.boolean().default(false),
|
|
52
|
+
relatedPrimaryScope : z.enum(ResourcePrimaryScope),
|
|
53
|
+
});
|
|
54
|
+
|
|
55
|
+
|
|
56
|
+
export type RoleDefinition = z.infer<typeof RoleDefinitionSchema>;
|
|
57
|
+
|
|
58
|
+
export const RolesConfigurationSchema = z.record(z.string(), RoleDefinitionSchema).refine(
|
|
59
|
+
(record) => {
|
|
60
|
+
// Validate that all keys are valid roles
|
|
61
|
+
return Object.keys(record).every(key => {
|
|
62
|
+
try {
|
|
63
|
+
RolesSchema.parse(key);
|
|
64
|
+
return true;
|
|
65
|
+
} catch {
|
|
66
|
+
return false;
|
|
67
|
+
}
|
|
68
|
+
});
|
|
69
|
+
}
|
|
70
|
+
);
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
## The engine's organization roles
|
|
74
|
+
|
|
75
|
+
## Import Origins
|
|
76
|
+
|
|
77
|
+
- `@wildo-ai/saas-models`
|
|
78
|
+
|
|
79
|
+
## Source Excerpts
|
|
80
|
+
|
|
81
|
+
### Origin Package: `@wildo-ai/saas-models`
|
|
82
|
+
|
|
83
|
+
```typescript
|
|
84
|
+
*
|
|
85
|
+
* The organization roles the engine ships, and how they inherit. Read it to choose what a custom role
|
|
86
|
+
* should `inheritFrom` and which roles an operation must name.
|
|
87
|
+
*
|
|
88
|
+
* The person-holdable chain is linear: `ORG_OWNER → ORG_ADMIN → ORG_MANAGER → ORG_MEMBER → ORG_GUEST`
|
|
89
|
+
* (each holds everything to its right). `ORG_SERVICE_PROVIDER` hangs off `ORG_MEMBER` for experts of a
|
|
90
|
+
* service firm. The entries after `ORG_OWNER` are handler-only or delegated-capability roles: the
|
|
91
|
+
* engine confers them (an inbound handler, a live capability grant), they are never stored on a
|
|
92
|
+
* membership, and a membership naming one is refused. Never inherit from them or assign them.
|
|
93
|
+
*/
|
|
94
|
+
export const DEFAULT_ORGANIZATION_ROLES: RolesConfiguration = {
|
|
95
|
+
[CORE_ORG_ROLES.ORG_GUEST]: {
|
|
96
|
+
role: CORE_ORG_ROLES.ORG_GUEST,
|
|
97
|
+
isSystemRole: true,
|
|
98
|
+
relatedPrimaryScope: ResourcePrimaryScope.ORGANIZATIONS
|
|
99
|
+
},
|
|
100
|
+
[CORE_ORG_ROLES.ORG_MEMBER]: {
|
|
101
|
+
role: CORE_ORG_ROLES.ORG_MEMBER,
|
|
102
|
+
inheritFrom: CORE_ORG_ROLES.ORG_GUEST,
|
|
103
|
+
isSystemRole: true,
|
|
104
|
+
relatedPrimaryScope: ResourcePrimaryScope.ORGANIZATIONS
|
|
105
|
+
},
|
|
106
|
+
[CORE_ORG_ROLES.ORG_SERVICE_PROVIDER]: {
|
|
107
|
+
role: CORE_ORG_ROLES.ORG_SERVICE_PROVIDER,
|
|
108
|
+
inheritFrom: CORE_ORG_ROLES.ORG_MEMBER,
|
|
109
|
+
isSystemRole: true,
|
|
110
|
+
relatedPrimaryScope: ResourcePrimaryScope.ORGANIZATIONS
|
|
111
|
+
},
|
|
112
|
+
[CORE_ORG_ROLES.ORG_MANAGER]: {
|
|
113
|
+
role: CORE_ORG_ROLES.ORG_MANAGER,
|
|
114
|
+
inheritFrom: CORE_ORG_ROLES.ORG_MEMBER,
|
|
115
|
+
isSystemRole: true,
|
|
116
|
+
relatedPrimaryScope: ResourcePrimaryScope.ORGANIZATIONS
|
|
117
|
+
},
|
|
118
|
+
[CORE_ORG_ROLES.ORG_ADMIN]: {
|
|
119
|
+
role: CORE_ORG_ROLES.ORG_ADMIN,
|
|
120
|
+
inheritFrom: CORE_ORG_ROLES.ORG_MANAGER,
|
|
121
|
+
isSystemRole: true,
|
|
122
|
+
relatedPrimaryScope: ResourcePrimaryScope.ORGANIZATIONS
|
|
123
|
+
},
|
|
124
|
+
[CORE_ORG_ROLES.ORG_OWNER]: {
|
|
125
|
+
role: CORE_ORG_ROLES.ORG_OWNER,
|
|
126
|
+
inheritFrom: CORE_ORG_ROLES.ORG_ADMIN,
|
|
127
|
+
isSystemRole: true,
|
|
128
|
+
relatedPrimaryScope: ResourcePrimaryScope.ORGANIZATIONS
|
|
129
|
+
},
|
|
130
|
+
// No `inheritFrom`: handler-only, confers exactly the billing operations that name it (#1629).
|
|
131
|
+
[CORE_ORG_ROLES.ORG_BILLING_PROVIDER_EVENTS]: {
|
|
132
|
+
role: CORE_ORG_ROLES.ORG_BILLING_PROVIDER_EVENTS,
|
|
133
|
+
isSystemRole: true,
|
|
134
|
+
relatedPrimaryScope: ResourcePrimaryScope.ORGANIZATIONS
|
|
135
|
+
},
|
|
136
|
+
// No `inheritFrom` on any delegated capability (#1631): each confers exactly the operations that name it, and
|
|
137
|
+
// inheriting anything would make a lent capability's reach a function of what that role grows into later.
|
|
138
|
+
[CORE_ORG_ROLES.ORG_DELEGATED_INVITE_MEMBERS]: {
|
|
139
|
+
role: CORE_ORG_ROLES.ORG_DELEGATED_INVITE_MEMBERS,
|
|
140
|
+
isSystemRole: true,
|
|
141
|
+
relatedPrimaryScope: ResourcePrimaryScope.ORGANIZATIONS
|
|
142
|
+
},
|
|
143
|
+
[CORE_ORG_ROLES.ORG_DELEGATED_MANAGE_RELATIONSHIP_EXPERTS]: {
|
|
144
|
+
role: CORE_ORG_ROLES.ORG_DELEGATED_MANAGE_RELATIONSHIP_EXPERTS,
|
|
145
|
+
isSystemRole: true,
|
|
146
|
+
relatedPrimaryScope: ResourcePrimaryScope.ORGANIZATIONS
|
|
147
|
+
},
|
|
148
|
+
[CORE_ORG_ROLES.ORG_DELEGATED_READ_AUDIT_TRAIL]: {
|
|
149
|
+
role: CORE_ORG_ROLES.ORG_DELEGATED_READ_AUDIT_TRAIL,
|
|
150
|
+
isSystemRole: true,
|
|
151
|
+
relatedPrimaryScope: ResourcePrimaryScope.ORGANIZATIONS
|
|
152
|
+
},
|
|
153
|
+
[CORE_ORG_ROLES.ORG_DELEGATED_MANAGE_SSO_SCIM]: {
|
|
154
|
+
role: CORE_ORG_ROLES.ORG_DELEGATED_MANAGE_SSO_SCIM,
|
|
155
|
+
isSystemRole: true,
|
|
156
|
+
relatedPrimaryScope: ResourcePrimaryScope.ORGANIZATIONS
|
|
157
|
+
},
|
|
158
|
+
[CORE_ORG_ROLES.ORG_DELEGATED_MANAGE_API_KEYS]: {
|
|
159
|
+
role: CORE_ORG_ROLES.ORG_DELEGATED_MANAGE_API_KEYS,
|
|
160
|
+
isSystemRole: true,
|
|
161
|
+
relatedPrimaryScope: ResourcePrimaryScope.ORGANIZATIONS
|
|
162
|
+
},
|
|
163
|
+
[CORE_ORG_ROLES.ORG_DELEGATED_APPROVE_ACCESS_GRANTS]: {
|
|
164
|
+
role: CORE_ORG_ROLES.ORG_DELEGATED_APPROVE_ACCESS_GRANTS,
|
|
165
|
+
isSystemRole: true,
|
|
166
|
+
relatedPrimaryScope: ResourcePrimaryScope.ORGANIZATIONS
|
|
167
|
+
}
|
|
168
|
+
};
|
|
169
|
+
```
|
|
@@ -0,0 +1,63 @@
|
|
|
1
|
+
# Worked Example — Office Staff and Field Technicians
|
|
2
|
+
|
|
3
|
+
The complete wiring for two groups of users who must see different parts of the product: the role
|
|
4
|
+
declaration, the organization type that offers it, and the operation role sets that make it matter.
|
|
5
|
+
|
|
6
|
+
Read it when a requirement names user groups ("office", "field", "technicians", "accountants",
|
|
7
|
+
"read-only reviewers") and you are about to decide what each may do.
|
|
8
|
+
|
|
9
|
+
|
|
10
|
+
## Usage Example
|
|
11
|
+
|
|
12
|
+
```typescript
|
|
13
|
+
*
|
|
14
|
+
* A trade business with office staff and field technicians. Everything below imports from
|
|
15
|
+
* `@wildo-ai/saas-models`.
|
|
16
|
+
*
|
|
17
|
+
* 1. `shared-lib/src/engine/roles.ts` declares the field role. Office staff need no new role: they hold
|
|
18
|
+
* the core `ORG_MEMBER`, so administrators and owners keep everything office staff can do. The field
|
|
19
|
+
* role inherits `ORG_GUEST`, the bottom of the chain, so it starts from almost nothing.
|
|
20
|
+
*/
|
|
21
|
+
export const CUSTOM_ROLES_CONFIGURATION: RolesConfiguration = {
|
|
22
|
+
FIELD_TECHNICIAN: {
|
|
23
|
+
role: 'FIELD_TECHNICIAN',
|
|
24
|
+
inheritFrom: CORE_ORG_ROLES.ORG_GUEST,
|
|
25
|
+
isSystemRole: false,
|
|
26
|
+
relatedPrimaryScope: ResourcePrimaryScope.ORGANIZATIONS,
|
|
27
|
+
},
|
|
28
|
+
};
|
|
29
|
+
|
|
30
|
+
/**
|
|
31
|
+
* 2. `wildo.saas.config.ts` → `organizationTypes.<type>.availableOrgRoles` offers it. Omitted, the list
|
|
32
|
+
* defaults to owner, admin and member only, so the field role could never be given to anyone.
|
|
33
|
+
*/
|
|
34
|
+
export const workspaceAvailableOrgRoles: Roles[] = [
|
|
35
|
+
CORE_ORG_ROLES.ORG_OWNER,
|
|
36
|
+
CORE_ORG_ROLES.ORG_ADMIN,
|
|
37
|
+
CORE_ORG_ROLES.ORG_MEMBER,
|
|
38
|
+
'FIELD_TECHNICIAN',
|
|
39
|
+
];
|
|
40
|
+
|
|
41
|
+
/**
|
|
42
|
+
* 3. Each operation variant's `roles` names who may call it. A holder satisfies a role it holds OR one
|
|
43
|
+
* up its `inheritFrom` chain, so `ORG_MEMBER` here admits office staff, managers, admins and owners,
|
|
44
|
+
* and the field role must be named explicitly wherever technicians are admitted.
|
|
45
|
+
*/
|
|
46
|
+
/** Jobs: technicians read the jobs and record progress on them. */
|
|
47
|
+
export const jobReadAndProgressRoles: Roles[] = ['FIELD_TECHNICIAN', CORE_ORG_ROLES.ORG_MEMBER];
|
|
48
|
+
/** Quotes and invoices: office only. A technician holding only the field role is refused. */
|
|
49
|
+
export const quoteAndInvoiceRoles: Roles[] = [CORE_ORG_ROLES.ORG_MEMBER];
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
What each part earns:
|
|
53
|
+
|
|
54
|
+
- **No role for office staff.** They hold the core `ORG_MEMBER`, so administrators and owners keep
|
|
55
|
+
every office capability through the chain. Declaring a custom "office" role would force every
|
|
56
|
+
operation to name it AND the core roles.
|
|
57
|
+
- **The field role inherits `ORG_GUEST`.** It starts from the bottom, so a technician reaches only the
|
|
58
|
+
operations that name the field role explicitly. Inheriting `ORG_MEMBER` instead would give
|
|
59
|
+
technicians everything office staff have, which is the opposite of the requirement.
|
|
60
|
+
- **`availableOrgRoles` lists it.** Without the entry, the members screen cannot give the role to
|
|
61
|
+
anyone: the default list is owner, admin and member.
|
|
62
|
+
- **Operations name it where technicians are admitted, and only there.** Invoices name `ORG_MEMBER`
|
|
63
|
+
alone, so a technician is refused by the engine, not merely hidden from in the UI.
|
|
@@ -356,9 +356,14 @@ Run from the app root, substituting `<resource>` and `<field>`:
|
|
|
356
356
|
|---|---|
|
|
357
357
|
| The declaration exists | `rg -n "organizationUnitNarrowing" backend-api/src` |
|
|
358
358
|
| The declared field exists on the schema | `rg -n "<field>" shared-lib/src/modules/*/**/<resource>*.schemas.ts` |
|
|
359
|
-
| **No authorization-plane resource is declared** (must be empty) |
|
|
359
|
+
| **No authorization-plane resource is declared** (must be empty) | see the commands below the table |
|
|
360
360
|
| The specification mentions the confinement | `rg -n -i "organization unit" specifications/src/modules/*/resources/<resource>.resource.specification.ts` |
|
|
361
361
|
|
|
362
|
+
```bash
|
|
363
|
+
# No authorization-plane resource is declared (must be empty)
|
|
364
|
+
rg -n "organizationUnitNarrowing" -A 20 backend-api/src | rg -n "ORGANIZATION_MEMBERS|ORGANIZATION_UNIT_MEMBERS|ORGANIZATION_UNITS|ORGANIZATIONS|ORG_API_KEYS|OAUTH_CLIENTS_ORGANIZATION"
|
|
365
|
+
```
|
|
366
|
+
|
|
362
367
|
The high-signal invariant is the **field-name match**: everything else fails
|
|
363
368
|
loudly, while a misspelled field name is the one mistake that fails quietly.
|
|
364
369
|
|