@wildo-ai/framework-knowledge 1.1.9 → 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/expert-personas-and-deliberations.md +26 -7
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +4 -2
- package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +4 -2
- package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +9 -3
- 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 +84 -4
- 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 +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +39 -1
- 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 +132 -20
- 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.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 +2 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +85 -8
- 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.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 +2 -2
- 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 +10 -4
- 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 +2 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +5 -3
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +11 -9
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +17 -3
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +19 -2
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.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.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.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.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.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.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +38 -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 -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.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.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.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +11 -0
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
- package/dist/knowledge/manifest.json +7 -7
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +1 -1
- 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 +149 -11
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +40 -2
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +55 -0
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +10 -2
- 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 +107 -11
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +4 -2
- 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.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 +2 -1
- 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 +7 -3
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +3 -3
- package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +56 -16
- package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +6 -4
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +30 -9
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +5 -3
- package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +12 -1
- 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.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 +1 -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.vision-elicitation/method.md +19 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +19 -1
- package/dist/knowledge/references/brand.name-choice.config.md +20 -3
- package/dist/knowledge/references/brand.name-screening.config.md +58 -3
- package/dist/knowledge/references/build-plan.task-graph.config.md +55 -0
- 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 +10 -9
- 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/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.computed-entry.md +43 -0
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +8 -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.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.website.astro.bridge.md +10 -0
- package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -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.legal.public-document-links.md +76 -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.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 +337 -1
- package/dist/knowledge/registries/playbooks.json +18 -18
- package/dist/knowledge/registries/source-tags.json +1435 -873
- package/dist/knowledge/rules/live-context-door.md +1 -1
- package/dist/knowledge/skills/INDEX.md +3 -1
- 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 +33 -9
- package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +78 -6
- package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +30 -8
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +2 -1
- 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 +25 -11
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +51 -1
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +62 -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 +27 -5
- 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 +18 -4
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +10 -2
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +6 -1
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +6 -1
- 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 +11 -3
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +1 -1
- 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-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 +14 -3
- 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-relationships/SKILL.md +31 -4
- 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 +155 -40
- 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 +148 -4
- package/dist/knowledge/skills/seeding-authoring/references/seed-row-overlay.md +22 -0
- 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-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 +10 -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 +16 -5
- 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-faq/SKILL.md +6 -1
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +6 -1
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +10 -2
- package/dist/knowledge/skills/website-section-hero/SKILL.md +6 -1
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +6 -1
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +12 -2
- package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +15 -3
- 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 +1441 -269
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/package.json +4 -4
|
@@ -1,12 +1,14 @@
|
|
|
1
1
|
# Data seeding — authoring contract (source)
|
|
2
2
|
|
|
3
|
-
The
|
|
3
|
+
The source-anchored surfaces an app developer touches when
|
|
4
4
|
authoring a `DataSeedDefinition`:
|
|
5
5
|
|
|
6
6
|
- **`DataSeedMode`** — the four modes (`LAZY` / `ADDITIVE` / `UPGRADE` / `SYNC`); the JSDoc on each variant captures its write semantics, re-run safety, and required-field invariants.
|
|
7
7
|
- **`DataSeedDefinitionInput`** — the input contract for `createDataSeedDefinition(...)`, with the cross-mode required-vs-optional summary.
|
|
8
|
+
- **`referenceDataSeedRow`** — the value an entry uses for a foreign key to a row ANOTHER seed writes. The engine
|
|
9
|
+
resolves it to that row's `_id` when the seed runs; the referenced seed must be in `dependsOn`.
|
|
8
10
|
|
|
9
|
-
|
|
11
|
+
All three live under the focused
|
|
10
12
|
`@wildo-ai/saas-backend-lib/data-seeding-models` subpath barrel —
|
|
11
13
|
import from there in seed files (NOT the package root).
|
|
12
14
|
|
|
@@ -127,8 +129,14 @@ export enum DataSeedMode {
|
|
|
127
129
|
* dispatcher walks `fromVersion` from the persisted row's
|
|
128
130
|
* `seedVersion` up to `version - 1`, then re-applies
|
|
129
131
|
* `managedFields` from the declared entries.
|
|
130
|
-
* - `dependsOn` —
|
|
131
|
-
*
|
|
132
|
+
* - `dependsOn` — seeds that run before this one. It orders and passes no
|
|
133
|
+
* data; to point an entry's foreign key at a row a dependency wrote, put
|
|
134
|
+
* `referenceDataSeedRow(dependencySeed, { …businessKey })` where the value
|
|
135
|
+
* goes, and the engine resolves it to that row's `_id` when this seed runs.
|
|
136
|
+
* Every referenced seed MUST be listed here.
|
|
137
|
+
* - `anchorEntriesToScopeForeignKey` — inject the scope's foreign key
|
|
138
|
+
* (`organizationId`, …) into every entry's business key, so static entries
|
|
139
|
+
* can be written once and seeded per scope row.
|
|
132
140
|
* - `schedule` — optional cron-driven re-run binding; presence is the
|
|
133
141
|
* sole opt-in signal for the engine cron batch. FORBIDDEN for
|
|
134
142
|
* `mode === LAZY`.
|
|
@@ -184,3 +192,139 @@ export interface DataSeedDefinition extends DataSeedDefinitionParsed, DataSeedDe
|
|
|
184
192
|
triggers: DataSeedTrigger[];
|
|
185
193
|
}
|
|
186
194
|
```
|
|
195
|
+
|
|
196
|
+
A computed `entry()` receives the triggering row and returns exactly one entry; it cannot skip a row:
|
|
197
|
+
|
|
198
|
+
## Import Origins
|
|
199
|
+
|
|
200
|
+
- `@wildo-ai/saas-backend-lib`
|
|
201
|
+
|
|
202
|
+
## Source Excerpts
|
|
203
|
+
|
|
204
|
+
### Origin Package: `@wildo-ai/saas-backend-lib`
|
|
205
|
+
|
|
206
|
+
```typescript
|
|
207
|
+
*
|
|
208
|
+
* Function shape of a **computed** seed entry — used by a seed whose payload depends on the row that triggered it
|
|
209
|
+
* (an `afterCreate` seed needs that row's `_id`). Declared as a type rather than in the Zod schema, because Zod cannot
|
|
210
|
+
* validate what a function returns.
|
|
211
|
+
*
|
|
212
|
+
* `triggeringRow` is that row as stored, untyped (`Record<string, unknown>` with its `_id`), or `null` for a
|
|
213
|
+
* lazy-access seed. Narrow the fields you read yourself.
|
|
214
|
+
*
|
|
215
|
+
* The context deliberately offers no way to READ other rows. A foreign key to a
|
|
216
|
+
* row another seed writes is returned as `referenceDataSeedRow(targetSeed, key)`
|
|
217
|
+
* and resolved by the engine (the target seed must be in `dependsOn`).
|
|
218
|
+
*
|
|
219
|
+
* It returns exactly ONE entry, every time it is called: there is no "skip this row" value. A seed that should
|
|
220
|
+
* apply to only some triggering rows is the wrong shape; put the condition in an operation (a postfix that creates
|
|
221
|
+
* the row when the condition holds) instead.
|
|
222
|
+
*/
|
|
223
|
+
export type DataSeedComputedEntryFn = (context: {
|
|
224
|
+
/**
|
|
225
|
+
* The resource row whose lifecycle event fired the seed (Level B only).
|
|
226
|
+
* Always present for `triggerKind: 'resourceLifecycle'`. `null` for lazy
|
|
227
|
+
* access seeds where there is no triggering row.
|
|
228
|
+
*/
|
|
229
|
+
triggeringRow: { _id: string } & Record<string, unknown> | null;
|
|
230
|
+
/**
|
|
231
|
+
* Who caused the run, for attribution only: the seed itself always runs as an internal request, whoever triggered
|
|
232
|
+
* it. `triggeredByUserId` is recorded in the row's `__seed` metadata and in the `DataSeedRun` ledger.
|
|
233
|
+
*/
|
|
234
|
+
executionContext: {
|
|
235
|
+
triggeredByUserId: string | null;
|
|
236
|
+
};
|
|
237
|
+
}) => DataSeedStaticEntry | Promise<DataSeedStaticEntry>;
|
|
238
|
+
```
|
|
239
|
+
|
|
240
|
+
## Import Origins
|
|
241
|
+
|
|
242
|
+
- `@wildo-ai/saas-backend-lib`
|
|
243
|
+
|
|
244
|
+
## Source Excerpts
|
|
245
|
+
|
|
246
|
+
### Origin Package: `@wildo-ai/saas-backend-lib`
|
|
247
|
+
|
|
248
|
+
```typescript
|
|
249
|
+
/**
|
|
250
|
+
* What a reference needs to know about the seed whose row it names. A whole `DataSeedDefinition` satisfies it — pass
|
|
251
|
+
* the target seed's definition, imported from the module that declares it.
|
|
252
|
+
*/
|
|
253
|
+
export type DataSeedRowReferenceTarget = Pick<DataSeedDefinition, 'seedKey' | 'resourceType' | 'scope' | 'allowedApplicationEnvironments'>;
|
|
254
|
+
|
|
255
|
+
/**
|
|
256
|
+
* A reference to a row another seed writes, placed where a foreign-key VALUE goes in an entry's `businessKey` or
|
|
257
|
+
* `data` (directly, or inside a nested object or array). The engine replaces it with the row's `_id` before writing.
|
|
258
|
+
*
|
|
259
|
+
* Build it with {@link referenceDataSeedRow}; never construct one by hand.
|
|
260
|
+
*/
|
|
261
|
+
export class DataSeedRowReference {
|
|
262
|
+
/** Brand read by {@link isDataSeedRowReference}. */
|
|
263
|
+
public readonly [DATA_SEED_ROW_REFERENCE_BRAND]: true = true;
|
|
264
|
+
|
|
265
|
+
/** @internal — use {@link referenceDataSeedRow}. */
|
|
266
|
+
public constructor(
|
|
267
|
+
/** The seed that writes the referenced row. Must be in the referring seed's `dependsOn`. */
|
|
268
|
+
public readonly target: DataSeedRowReferenceTarget,
|
|
269
|
+
/**
|
|
270
|
+
* The referenced row's business key, as the target resource declares it. The scope's own foreign key may be left
|
|
271
|
+
* out when both seeds share a scope kind; the engine fills it in from the scope being seeded.
|
|
272
|
+
*/
|
|
273
|
+
public readonly businessKey: Readonly<Record<string, unknown>>,
|
|
274
|
+
) {
|
|
275
|
+
Object.freeze(this);
|
|
276
|
+
}
|
|
277
|
+
|
|
278
|
+
/** What a log line or a JSON dump shows instead of an empty object (the brand is a symbol, which JSON drops). */
|
|
279
|
+
public toJSON(): string {
|
|
280
|
+
return describeDataSeedRowReference(this);
|
|
281
|
+
}
|
|
282
|
+
}
|
|
283
|
+
|
|
284
|
+
/**
|
|
285
|
+
* Reference the row a `dependsOn` seed writes, by that row's business key.
|
|
286
|
+
*
|
|
287
|
+
* @param target The seed that writes the row — its definition, as returned by `createDataSeedDefinition`.
|
|
288
|
+
* @param businessKey The row's business key. Leave out the scope foreign key (`organizationId`, `userId`, …) when the
|
|
289
|
+
* target seed has the same scope kind as the referring seed: the engine fills it from the scope being seeded.
|
|
290
|
+
* @throws Error when `target` has no `seedKey`, when `businessKey` is not a plain object, or when a business-key value
|
|
291
|
+
* is `undefined` or is itself a reference.
|
|
292
|
+
*
|
|
293
|
+
* @example
|
|
294
|
+
* ```ts
|
|
295
|
+
* import { referenceDataSeedRow } from '@wildo-ai/saas-backend-lib/data-seeding-models';
|
|
296
|
+
* import demoCustomersSeed from './crm.demo-customers.seed';
|
|
297
|
+
*
|
|
298
|
+
* // In a seed declaring dependsOn: [{ seedKey: demoCustomersSeed.seedKey }]
|
|
299
|
+
* data: { customerId: referenceDataSeedRow(demoCustomersSeed, { email: 'ana.martin@example.com' }) }
|
|
300
|
+
* ```
|
|
301
|
+
*/
|
|
302
|
+
export function referenceDataSeedRow(
|
|
303
|
+
target: DataSeedRowReferenceTarget,
|
|
304
|
+
businessKey: Record<string, unknown>,
|
|
305
|
+
): DataSeedRowReference {
|
|
306
|
+
if (target === null || typeof target !== 'object' || typeof target.seedKey !== 'string' || target.seedKey.length === 0) {
|
|
307
|
+
throw new Error('referenceDataSeedRow: `target` must be the referenced seed\'s definition (a value carrying its `seedKey`, `resourceType` and `scope`).');
|
|
308
|
+
}
|
|
309
|
+
if (!isPlainObject(businessKey)) {
|
|
310
|
+
throw new Error(`referenceDataSeedRow: the business key of a reference to seed '${target.seedKey}' must be a plain object.`);
|
|
311
|
+
}
|
|
312
|
+
for (const [field, value] of Object.entries(businessKey)) {
|
|
313
|
+
if (value === undefined) {
|
|
314
|
+
throw new Error(`referenceDataSeedRow: business-key field '${field}' of a reference to seed '${target.seedKey}' is undefined — a business key is identity; use null for a genuinely-nullable field.`);
|
|
315
|
+
}
|
|
316
|
+
if (containsDataSeedRowReference(value)) {
|
|
317
|
+
throw new Error(`referenceDataSeedRow: business-key field '${field}' of a reference to seed '${target.seedKey}' is itself a reference — a reference names its row by literal values.`);
|
|
318
|
+
}
|
|
319
|
+
}
|
|
320
|
+
return new DataSeedRowReference(
|
|
321
|
+
{
|
|
322
|
+
seedKey: target.seedKey,
|
|
323
|
+
resourceType: target.resourceType,
|
|
324
|
+
scope: target.scope,
|
|
325
|
+
...(target.allowedApplicationEnvironments !== undefined ? { allowedApplicationEnvironments: target.allowedApplicationEnvironments } : {}),
|
|
326
|
+
},
|
|
327
|
+
Object.freeze({ ...businessKey }),
|
|
328
|
+
);
|
|
329
|
+
}
|
|
330
|
+
```
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
# The `__seed` overlay — field names
|
|
2
|
+
|
|
3
|
+
Read this when a test, a log or a stored row shows a seeded row's `__seed` block. Authors never read
|
|
4
|
+
or write the overlay; the engine owns it.
|
|
5
|
+
|
|
6
|
+
**Note on overlay field names** (audit L1-7, post-Phase-7
|
|
7
|
+
close-out): the `__seed` overlay tracks **`managedSince`**
|
|
8
|
+
(the wall-clock `Date` at which the framework first stamped
|
|
9
|
+
the row — preserved across subsequent passes by
|
|
10
|
+
`buildDataSeedRowMetadataForUpsert`, and only re-set when the
|
|
11
|
+
row is created). It does NOT carry `mode`, `runId`, or
|
|
12
|
+
`seededAt` — earlier drafts
|
|
13
|
+
of this guide and some forum discussions referenced those
|
|
14
|
+
names as if they were persisted on the row. They are NOT:
|
|
15
|
+
`mode` lives on the seed definition (not the row), `runId`
|
|
16
|
+
lives on `DataSeedRun` (one row per pass, not per seeded
|
|
17
|
+
document), and `seededAt` was renamed to `managedSince`
|
|
18
|
+
early in the design to clarify the "first-stamp wall-clock"
|
|
19
|
+
semantic. Authors should never need to read or write any of
|
|
20
|
+
these — the overlay is dispatcher-private — but the naming
|
|
21
|
+
matters for tests and for the `data-seed-row-metadata.shared.schemas.ts`
|
|
22
|
+
source file.
|
|
@@ -264,3 +264,46 @@ export enum EngineSettingsDestinationRef {
|
|
|
264
264
|
* grant and says so. Neither becomes placeable by widening the operation that is already there.
|
|
265
265
|
*/
|
|
266
266
|
```
|
|
267
|
+
|
|
268
|
+
## Who sees an engine destination
|
|
269
|
+
|
|
270
|
+
The engine decides, through the destination's own `requiredRoles`; your placement cannot widen or narrow it. Three
|
|
271
|
+
tiers, from these two role sets:
|
|
272
|
+
|
|
273
|
+
## Import Origins
|
|
274
|
+
|
|
275
|
+
- `@wildo-ai/saas-frontend-lib`
|
|
276
|
+
|
|
277
|
+
## Source Excerpts
|
|
278
|
+
|
|
279
|
+
### Origin Package: `@wildo-ai/saas-frontend-lib`
|
|
280
|
+
|
|
281
|
+
```typescript
|
|
282
|
+
/** Org-management destinations are visible to organization owners and admins. */
|
|
283
|
+
const ORG_MANAGEMENT_ROLES: string[] = [CORE_ORG_ROLES.ORG_OWNER, CORE_ORG_ROLES.ORG_ADMIN];
|
|
284
|
+
|
|
285
|
+
/**
|
|
286
|
+
* Application-administration destinations are visible to the application's own super-administrator.
|
|
287
|
+
*
|
|
288
|
+
* ONE role, deliberately, and not the wider `APP_ADMIN_*` family: every destination gated with this
|
|
289
|
+
* is a surface whose resource ALSO requires `APP_ADMIN_SUPER_ADMIN` server-side, so admitting
|
|
290
|
+
* `APP_ADMIN_VIEWER` or `APP_ADMIN_BILLING_MANAGER` here would render a rail entry that answers 403
|
|
291
|
+
* on open — worse than absent, because it reads as a permission the operator has and a bug they hit.
|
|
292
|
+
* Widen this only alongside the operation roles it would then have to match.
|
|
293
|
+
*/
|
|
294
|
+
const APPLICATION_ADMINISTRATION_ROLES: string[] = [CORE_APP_ROLES.APP_ADMIN_SUPER_ADMIN];
|
|
295
|
+
```
|
|
296
|
+
|
|
297
|
+
- **Personal destinations** (`profile`, `security`, `preferences`, `appearance`, your invitations, your own provider
|
|
298
|
+
credentials) have no `requiredRoles`: every signed-in user sees them.
|
|
299
|
+
- **Organization destinations** (general, members, billing, SSO, webhooks, API keys, audit logs, …) are for the
|
|
300
|
+
organization's owners and admins. A few are narrower, owner-only (legal holds, referrals), and one is wider: the
|
|
301
|
+
organization's entitlements, which every member sees.
|
|
302
|
+
- **Application destinations** (`application-*`, and `billing-catalog`) are for the application's super-administrator;
|
|
303
|
+
the application audit and retention-enforcement destinations also admit the audit-evidence reader.
|
|
304
|
+
|
|
305
|
+
The role match is exact: a custom role that inherits `ORG_ADMIN` does not see an organization destination unless it is
|
|
306
|
+
listed itself.
|
|
307
|
+
|
|
308
|
+
So placing an organization destination on a rail that ordinary members open shows them nothing there. That is
|
|
309
|
+
expected, not a misplacement.
|
|
@@ -128,8 +128,8 @@ export interface SettingsDestination {
|
|
|
128
128
|
ref: string;
|
|
129
129
|
/** What the destination renders in its content panel. */
|
|
130
130
|
target: SettingsSectionTarget;
|
|
131
|
-
/** Declarative runtime capability gating (
|
|
132
|
-
runtimeAvailability?:
|
|
131
|
+
/** Declarative runtime capability gating (launcher items' `requiredCapabilities`; roles are `requiredRoles`). */
|
|
132
|
+
runtimeAvailability?: SettingsRuntimeAvailabilityConfig;
|
|
133
133
|
/** Feature flags required to surface this destination (plan/subscription gating). */
|
|
134
134
|
requiredFeatures?: RequiredFeaturesConfig;
|
|
135
135
|
/** RBAC roles required to surface this destination (OR semantics). */
|
|
@@ -360,7 +360,12 @@ Run from the repo root, substituting `<spec-export>` and `<slug>`:
|
|
|
360
360
|
| Companion exports uses the typed contract | `rg -n "SpecificationsCompanionExports<" specifications/src/companion-exports.ts` |
|
|
361
361
|
| **No deep package-internal imports** (must be empty) | `rg -n "from\s+'\.\.\/\.\.\/\.\.\/" specifications/src/companion-exports.ts` |
|
|
362
362
|
| **No hand-built spec maps** (every slot is a single barrel import) | `rg -n "Specifications:\s+\{" specifications/src/companion-exports.ts` (must be 0 — every slot reads from a barrel name, not an inline literal) |
|
|
363
|
-
| Each spec family barrel has an `index.ts` |
|
|
363
|
+
| Each spec family barrel has an `index.ts` | see the commands below the table |
|
|
364
|
+
|
|
365
|
+
```bash
|
|
366
|
+
# Each spec family barrel has an `index.ts`
|
|
367
|
+
rg --files specifications/src/modules/<slug>/ | rg "index\.ts$"
|
|
368
|
+
```
|
|
364
369
|
|
|
365
370
|
The high-signal invariant is **"spec is exported from its family
|
|
366
371
|
barrel AND lands in `companion-exports.ts`"** — a spec that shows up
|
|
@@ -300,10 +300,18 @@ Run from the repo root, substituting `<componentRef>`:
|
|
|
300
300
|
| Spec uses the typed factory | `rg -n "frontendComponentSpecification\(" specifications/src/modules/<slug>/frontend-components/` |
|
|
301
301
|
| `componentRef` uses the typed enum | `rg -n "componentRef:\s+FrontendComponentType\." specifications/src/modules/<slug>/frontend-components/<componentRef>.frontend-component.specification.ts` |
|
|
302
302
|
| **No string-literal componentRef** (must be empty) | `rg -n "componentRef:\s+'" specifications/src/modules/<slug>/frontend-components/` |
|
|
303
|
-
| Every prop has a `valueKind` |
|
|
304
|
-
| Every ENUM prop has an `enumerationSource` |
|
|
303
|
+
| Every prop has a `valueKind` | see the commands below the table |
|
|
304
|
+
| Every ENUM prop has an `enumerationSource` | see the commands below the table |
|
|
305
305
|
| Spec re-exported from companion bundle | `rg -n "<componentRef>FrontendComponentSpecification" specifications/src/companion-exports.ts` |
|
|
306
306
|
|
|
307
|
+
```bash
|
|
308
|
+
# Every prop has a `valueKind`
|
|
309
|
+
rg -n "propName:\s+'" specifications/src/modules/<slug>/frontend-components/<componentRef>.frontend-component.specification.ts -A 3 | rg "valueKind:"
|
|
310
|
+
|
|
311
|
+
# Every ENUM prop has an `enumerationSource`
|
|
312
|
+
rg -n "valueKind:\s+FrontendComponentPropValueKind\.ENUM" specifications/src/modules/<slug>/frontend-components/<componentRef>.frontend-component.specification.ts -A 8 | rg "enumerationSource:"
|
|
313
|
+
```
|
|
314
|
+
|
|
307
315
|
The high-signal invariant is **"every ENUM prop has an
|
|
308
316
|
`enumerationSource`"** — a typed enum reference is what lets
|
|
309
317
|
companion / codegen follow the prop vocabulary back to its declaration
|
|
@@ -248,8 +248,8 @@ Run from the app root, substituting `<slug>` and `<view-ref>`:
|
|
|
248
248
|
| Spec uses the typed factory (no raw object) | `rg -n "compositeViewSpecificationFromDefinition\(" specifications/src/modules/<slug>/composite-views/` |
|
|
249
249
|
| `translationRef` uses the typed builder | `rg -n "translationRef:\s+build\w+CompositeViewTranslationRef\(" specifications/src/modules/<slug>/composite-views/<view-ref>.composite-view.specification.ts` |
|
|
250
250
|
| **No hand-written translation ref** (must be empty) | `rg -n "translationRef:\s+'" specifications/src/modules/<slug>/composite-views/` |
|
|
251
|
-
| `sectionRefs` declared in spec | `rg -oN "sectionRefs:\s+\[\K[^\]]+" specifications/src/modules/<slug>/composite-views/<view-ref>.composite-view.specification.ts` |
|
|
252
|
-
| `<Section name>` declared in JSX (must be the same set as `sectionRefs`) | `rg -oN "<Section\s+name=\"\K[^\"]+" frontend/src/modules/<slug>/**/*CompositeView.tsx` |
|
|
251
|
+
| `sectionRefs` declared in spec | `rg -P -oN "sectionRefs:\s+\[\K[^\]]+" specifications/src/modules/<slug>/composite-views/<view-ref>.composite-view.specification.ts` |
|
|
252
|
+
| `<Section name>` declared in JSX (must be the same set as `sectionRefs`) | `rg -P -oN "<Section\s+name=\"\K[^\"]+" frontend/src/modules/<slug>/**/*CompositeView.tsx` |
|
|
253
253
|
| Spec re-exported from companion bundle | `rg -n "<view-ref>CompositeViewSpecification" specifications/src/companion-exports.ts` |
|
|
254
254
|
|
|
255
255
|
The high-signal invariant is the **`sectionRefs` ↔ `<Section name>` set
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: spec-family-update
|
|
3
|
-
description: Author or update product, role, and milestone family specifications with stable ids, cross-links, and `codeHandling` wiring. Use when the user says "spec out a new product tier", "rename a role spec", "update the milestone narrative", "add a new product/role/milestone spec", "the family spec ids drifted from the runtime
|
|
3
|
+
description: Author or update product, role, and milestone family specifications with stable ids, cross-links, and `codeHandling` wiring. Use when the user says "spec out a new product tier", "rename a role spec", "update the milestone narrative", "add a new product/role/milestone spec", "the family spec ids drifted from the runtime record", or any change to product / role / milestone definition family records.
|
|
4
4
|
user-invocable: false
|
|
5
5
|
---
|
|
6
6
|
|
|
@@ -31,24 +31,27 @@ serve three consumers:
|
|
|
31
31
|
2. The **definition lookup** — `codeHandling.definitionOwner`,
|
|
32
32
|
`definitionSymbol`, `definitionCollectionEntry`, and
|
|
33
33
|
`identifierDeclaration` let companion follow the spec back to the
|
|
34
|
-
runtime
|
|
34
|
+
runtime record it describes.
|
|
35
35
|
3. The **packaging / commerce / org structure layers** — product
|
|
36
36
|
specs feed pricing tables; role specs feed permission narratives;
|
|
37
37
|
milestone specs feed onboarding and progression UIs.
|
|
38
38
|
|
|
39
39
|
These three families are spec'd through the **same shape** as feature
|
|
40
|
-
specs
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
follows
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
>
|
|
40
|
+
specs — each built with its `appLevel<Family>SpecificationFromDefinition(...)`
|
|
41
|
+
helper and aggregated with `build<Family>SpecificationMap(...)`, both from
|
|
42
|
+
`@wildo-ai/saas-specifications`. What differs is the runtime record each
|
|
43
|
+
spec follows:
|
|
44
|
+
|
|
45
|
+
| Family | Runtime record (shared-lib) | Shape |
|
|
46
|
+
|---|---|---|
|
|
47
|
+
| Role | `CUSTOM_ROLES_CONFIGURATION` in `shared-lib/src/engine/roles.ts` | a record keyed by the role name — no enum; declare the role itself with `application-roles-authoring` |
|
|
48
|
+
| Product | `CUSTOM_PRODUCT_CATALOG` in `shared-lib/src/engine/product.ts` | an array of product definitions |
|
|
49
|
+
| Milestone | `CUSTOM_MILESTONE_DEFINITIONS` in `shared-lib/src/engine/milestones.ts`, or a module's `moduleMilestonesDefinitions` in `shared-lib/src/modules/<module>/milestones.ts` | an array of milestone definitions |
|
|
50
|
+
|
|
51
|
+
> **Where they live**: role specifications under `specifications/src/engine/roles/`,
|
|
52
|
+
> product specifications under `specifications/src/engine/products/`, milestone
|
|
53
|
+
> specifications under `specifications/src/modules/<module>/milestones/`. Mirror a
|
|
54
|
+
> sibling in the same folder; with none yet, mirror `spec-feature-update`.
|
|
52
55
|
|
|
53
56
|
### A fourth definition family: error-message specs
|
|
54
57
|
|
|
@@ -72,18 +75,16 @@ two ways that change how you treat it:
|
|
|
72
75
|
|
|
73
76
|
| Surface | Glob (relative to repo root) |
|
|
74
77
|
|--------------------------------------|---------------------------------------------------------------------------------------------------------------|
|
|
75
|
-
|
|
|
76
|
-
|
|
|
77
|
-
| Milestone spec | `specifications/src/milestones/<
|
|
78
|
-
|
|
|
79
|
-
|
|
|
80
|
-
| Family enums (parity) | `shared-lib/src/products/custom-products.ts`, `shared-lib/src/roles/custom-roles.ts`, `shared-lib/src/milestones/custom-milestones.ts` |
|
|
81
|
-
| Family definition collections | `shared-lib/src/products/custom-product-definitions.ts`, `shared-lib/src/roles/custom-role-definitions.ts`, `shared-lib/src/milestones/custom-milestone-definitions.ts` |
|
|
78
|
+
| Role spec | `specifications/src/engine/roles/<role>.role.specification.ts` (aggregated in `specifications/src/engine/roles/index.ts`) |
|
|
79
|
+
| Product spec | `specifications/src/engine/products/<product>.product.specification.ts` |
|
|
80
|
+
| Milestone spec | `specifications/src/modules/<slug>/milestones/<group>.milestone.specifications.ts` (aggregated in that folder's `index.ts`) |
|
|
81
|
+
| Companion exports | `specifications/src/companion-exports.ts` (`productSpecifications`, `roleSpecifications`, `milestoneSpecifications` slots) — spread the application's map beside the engine's, or the companion reads only the engine's |
|
|
82
|
+
| Runtime records | `shared-lib/src/engine/roles.ts` (`CUSTOM_ROLES_CONFIGURATION`), `shared-lib/src/engine/product.ts` (`CUSTOM_PRODUCT_CATALOG`), `shared-lib/src/engine/milestones.ts` / `shared-lib/src/modules/<slug>/milestones.ts` |
|
|
82
83
|
|
|
83
84
|
## When to Use
|
|
84
85
|
|
|
85
86
|
- Adding a new product tier, role, or milestone — author the spec
|
|
86
|
-
alongside the
|
|
87
|
+
alongside the runtime record
|
|
87
88
|
- Renaming a family record — update the spec's
|
|
88
89
|
`identifierDeclaration` + collection entry + cross-references
|
|
89
90
|
- Updating tier pricing narrative, role permissions narrative, or
|
|
@@ -103,15 +104,17 @@ two ways that change how you treat it:
|
|
|
103
104
|
|
|
104
105
|
## Workflow
|
|
105
106
|
|
|
106
|
-
### Step 1: Pick the family + locate the
|
|
107
|
+
### Step 1: Pick the family + locate the runtime record
|
|
107
108
|
|
|
108
109
|
Use `references/family-spec-routing.md` to pick the file pattern.
|
|
109
110
|
Whichever family (product / role / milestone), the spec must follow
|
|
110
111
|
its runtime backbone:
|
|
111
112
|
|
|
112
|
-
1.
|
|
113
|
-
|
|
114
|
-
|
|
113
|
+
1. Find (or add) the runtime record the spec describes: the role's entry
|
|
114
|
+
in `CUSTOM_ROLES_CONFIGURATION` (declared with `application-roles-authoring`),
|
|
115
|
+
the product in `CUSTOM_PRODUCT_CATALOG`, the milestone in its definitions array
|
|
116
|
+
2. Author the spec with the family's `appLevel<Family>SpecificationFromDefinition(...)`,
|
|
117
|
+
naming the record (`{ role: 'FIELD_TECHNICIAN' }` for a role)
|
|
115
118
|
3. Add cross-links if the family interacts with another (e.g. a
|
|
116
119
|
role spec that requires a product tier)
|
|
117
120
|
|
|
@@ -134,13 +137,15 @@ signal.
|
|
|
134
137
|
Same shape as the feature spec:
|
|
135
138
|
|
|
136
139
|
- `definitionOwner: { ownerId, ownerKind: SpecificationOwnerKind.* }`
|
|
137
|
-
- `definitionSymbol` — the
|
|
138
|
-
(`
|
|
139
|
-
|
|
140
|
-
|
|
141
|
-
|
|
142
|
-
|
|
143
|
-
|
|
140
|
+
- `definitionSymbol` — the runtime record's symbol
|
|
141
|
+
(`CUSTOM_ROLES_CONFIGURATION`, `CUSTOM_PRODUCT_CATALOG`,
|
|
142
|
+
`CUSTOM_MILESTONE_DEFINITIONS` or the module's `moduleMilestonesDefinitions`)
|
|
143
|
+
- `definitionCollectionEntry` — the field that identifies the entry and its
|
|
144
|
+
value; for a role, `identifierField: 'role'` and the role name (a small
|
|
145
|
+
helper beside the role specs, taking the role name, keeps the symbol in one
|
|
146
|
+
place)
|
|
147
|
+
- `identifierDeclaration` — a typed enum reference when the family's
|
|
148
|
+
identifiers ARE an enum; roles are plain strings, so a role spec has none
|
|
144
149
|
- `supportingSymbols: [...]` — related runtime symbols (e.g. for a
|
|
145
150
|
product spec, the pricing-table symbol; for a role spec, the
|
|
146
151
|
permission-set symbol)
|
|
@@ -149,16 +154,16 @@ Same shape as the feature spec:
|
|
|
149
154
|
|
|
150
155
|
### Step 5: Register
|
|
151
156
|
|
|
152
|
-
1. Add the spec to the family map
|
|
157
|
+
1. Add the spec to the family map (`build<Family>SpecificationMap`)
|
|
153
158
|
2. Re-export from the family spec barrel
|
|
154
159
|
3. Verify it lands in `specificationsCompanionExports.<family>Specifications`
|
|
155
160
|
|
|
156
161
|
## Worked Example
|
|
157
162
|
|
|
158
|
-
|
|
159
|
-
`spec-feature-update` worked example for the spec shape — the
|
|
160
|
-
`codeHandling` wiring pattern is identical, only the
|
|
161
|
-
|
|
163
|
+
Mirror a sibling family spec in the same folder when one exists; otherwise
|
|
164
|
+
mirror the `spec-feature-update` worked example for the spec shape — the
|
|
165
|
+
`codeHandling` wiring pattern is identical, only the runtime record
|
|
166
|
+
changes. The framework feature anchor
|
|
162
167
|
demonstrates the canonical typed `codeHandling` wiring you should
|
|
163
168
|
copy:
|
|
164
169
|
|
|
@@ -227,10 +232,10 @@ export const aiAssistantFeatureSpecification: FeatureSpecificationConfig = {
|
|
|
227
232
|
|
|
228
233
|
When porting to a family spec, swap:
|
|
229
234
|
|
|
230
|
-
- `CUSTOM_FEATURE_DEFINITIONS` → `
|
|
231
|
-
`
|
|
232
|
-
- `ApplicationFeature` →
|
|
233
|
-
|
|
235
|
+
- `CUSTOM_FEATURE_DEFINITIONS` → `CUSTOM_PRODUCT_CATALOG` /
|
|
236
|
+
`CUSTOM_ROLES_CONFIGURATION` / `CUSTOM_MILESTONE_DEFINITIONS`
|
|
237
|
+
- `ApplicationFeature` (an enum) → the product's or milestone's identifier,
|
|
238
|
+
or the role's plain name
|
|
234
239
|
- `featureSpecifications` map → `productSpecifications` /
|
|
235
240
|
`roleSpecifications` / `milestoneSpecifications`
|
|
236
241
|
- `availabilityRole` (feature-only) → drop in family specs (use
|
|
@@ -246,33 +251,34 @@ When porting to a family spec, swap:
|
|
|
246
251
|
|
|
247
252
|
## Verification
|
|
248
253
|
|
|
249
|
-
- [ ]
|
|
250
|
-
- [ ]
|
|
251
|
-
- [ ] Spec uses the family-specific typed contract (`ProductSpecificationConfig` / `RoleSpecificationConfig` / `MilestoneSpecificationConfig`)
|
|
254
|
+
- [ ] The runtime record the spec describes exists (the role in `CUSTOM_ROLES_CONFIGURATION`, the product in `CUSTOM_PRODUCT_CATALOG`, the milestone in its definitions array)
|
|
255
|
+
- [ ] Spec uses the family-specific typed contract (`ProductSpecificationConfig` / `RoleSpecificationConfig` / `MilestoneSpecificationConfig`) through its `appLevel<Family>SpecificationFromDefinition` helper
|
|
252
256
|
- [ ] `codeHandling.definitionOwner.ownerKind` uses `SpecificationOwnerKind.*`
|
|
253
|
-
- [ ] `codeHandling.definitionCollectionEntry
|
|
254
|
-
- [ ]
|
|
255
|
-
- [ ] Spec
|
|
256
|
-
- [ ] Spec lands in `specificationsCompanionExports.<family>Specifications`
|
|
257
|
+
- [ ] `codeHandling.definitionSymbol` names the runtime record, and `definitionCollectionEntry` names the entry (`identifierField: 'role'` + the role name, for a role)
|
|
258
|
+
- [ ] Spec registered in the family map through `build<Family>SpecificationMap`
|
|
259
|
+
- [ ] Spec lands in `specificationsCompanionExports.<family>Specifications`, spread beside the engine's map
|
|
257
260
|
|
|
258
261
|
### Grep invariants
|
|
259
262
|
|
|
260
|
-
Run from the
|
|
261
|
-
/ `milestone`), `<FamilyEnum>` (`CustomProduct` / `CustomRole` /
|
|
262
|
-
`CustomMilestone`), and `<MEMBER>`:
|
|
263
|
+
Run from the app root, substituting `<NAME>` (the role name, product or milestone identifier):
|
|
263
264
|
|
|
264
265
|
| Invariant | Command |
|
|
265
266
|
|---------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
266
|
-
|
|
|
267
|
-
|
|
|
268
|
-
|
|
|
269
|
-
|
|
|
270
|
-
|
|
271
|
-
|
|
272
|
-
|
|
267
|
+
| The runtime record exists | `rg -n "<NAME>" shared-lib/src/engine/roles.ts shared-lib/src/engine/product.ts shared-lib/src/engine/milestones.ts shared-lib/src/modules/*/milestones.ts` |
|
|
268
|
+
| A spec names it | `rg -ln "<NAME>" specifications/src/engine specifications/src/modules` |
|
|
269
|
+
| The companion reads the application's family map, not only the engine's | see the commands below the table |
|
|
270
|
+
| **Unique ids across a family** (must return no duplicates) | see the commands below the table |
|
|
271
|
+
|
|
272
|
+
```bash
|
|
273
|
+
# The companion reads the application's family map, not only the engine's
|
|
274
|
+
rg -n "roleSpecifications|productSpecifications|milestoneSpecifications" specifications/src/companion-exports.ts
|
|
275
|
+
|
|
276
|
+
# Unique ids across a family (must return no duplicates)
|
|
277
|
+
rg -P -oN "FromDefinition\(\s*\{\s*\w+:\s*'\K[^']+" specifications/src | sort | uniq -d
|
|
278
|
+
```
|
|
273
279
|
|
|
274
280
|
The high-signal invariant is **"unique ids across the family"** —
|
|
275
|
-
two specs that
|
|
281
|
+
two specs that name the same record mean one silently
|
|
276
282
|
shadows the other in the family map; companion will lose half the
|
|
277
283
|
narrative.
|
|
278
284
|
|
|
@@ -281,17 +287,16 @@ narrative.
|
|
|
281
287
|
| Rationalization | Reality |
|
|
282
288
|
|-----------------|---------|
|
|
283
289
|
| "Rename id casually" | Analytics, billing, permission systems, and companion all cache by id; renaming without a migration record breaks all four. |
|
|
284
|
-
| "Two families can share the same id namespace" | Each family has its own
|
|
290
|
+
| "Two families can share the same id namespace" | Each family has its own runtime record and map; cross-family id sharing breaks runtime resolution. |
|
|
285
291
|
| "I'll skip cross-family `supportingSymbols`" | When a role spec depends on a product tier, omitting the supporting symbol drops the cross-family link from companion / AI authoring. |
|
|
286
292
|
| "Schema families and definition families are the same thing" | They are not. Schema families (money, range, duration) are Zod factories under `resource-schema-authoring`; definition families (product, role, milestone) are this skill. |
|
|
287
293
|
|
|
288
294
|
## Red Flags
|
|
289
295
|
|
|
290
|
-
-
|
|
291
|
-
- Spec exists but
|
|
292
|
-
-
|
|
293
|
-
-
|
|
294
|
-
- Family record renamed in the enum but the spec's `memberName` still references the old name
|
|
296
|
+
- Two specs naming the same record in one family (catch with the **Unique ids across a family** grep — must return no lines)
|
|
297
|
+
- Spec exists but its runtime record does not (catch with the **runtime record exists** grep)
|
|
298
|
+
- `roleSpecifications` / `productSpecifications` / `milestoneSpecifications` in companion exports holding only the engine's map, so the application's specs are read by nothing (catch with the **companion reads the application's family map** grep)
|
|
299
|
+
- Record renamed in shared-lib but the spec still names the old one (catch with the **runtime record exists** grep on the spec's name)
|
|
295
300
|
|
|
296
301
|
## Related Skills
|
|
297
302
|
|
|
@@ -4,7 +4,7 @@
|
|
|
4
4
|
|--------|-------------------|
|
|
5
5
|
| Product | `*.product.specification.ts` |
|
|
6
6
|
| Role | `*.role.specification.ts` |
|
|
7
|
-
| Milestone | `*.milestone.
|
|
7
|
+
| Milestone | `*.milestone.specifications.ts` (one file per group of milestones) |
|
|
8
8
|
|
|
9
9
|
Shared rules:
|
|
10
10
|
|