@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
|
@@ -147,6 +147,7 @@ product, and `TASK_DECLARES_NO_PRODUCT` is the honest answer rather than a place
|
|
|
147
147
|
| `WEBSITE_SECTION` | `pageRef` + `sectionRef` | one section of one page, declared in `<pageRef>.sections.tsx` |
|
|
148
148
|
| `DOCUMENTATION_CHAPTER` | `chapterRef` | the chapter's authored body, keyed by its `chapterRef` in `specifications/src/technical-documentation/index.ts`, which `wildo docs publish` joins to the documentation plan and publishes under `/guides/<slug>` |
|
|
149
149
|
| `APPLICATION_BILLING_PRODUCT` | `productKey` | one product of the application's billing catalogue, named by its catalogue `key` (a slug, e.g. `team`) — declared in `shared-lib/src/engine/product.ts` under the `BILLING_CATALOG` target. The KEY, never the file: `wildo init` writes the file with an empty catalogue |
|
|
150
|
+
| `APPLICATION_ROLE` | `roleRef` | one role the application declares, named by its key in `CUSTOM_ROLES_CONFIGURATION` (upper snake case, e.g. `FIELD_TECHNICIAN`; never a core role such as `ORG_MEMBER`) — declared in `shared-lib/src/engine/roles.ts` under the `APPLICATION_ROLES` target. The NAME, never the file: `wildo init` writes the file with an empty table |
|
|
150
151
|
| `APPLICATION_DATA_SEED` | `seedKey` + `resourceRef` + `content` (`REFERENCE` or `DEMONSTRATION`) | one data seed a module declares, named by its key (`<moduleRef>:<purpose>`, e.g. `crm:demo-customers`) — the file `backend-api/src/modules/<moduleRef>/seeds/<seedKey with : as .>.seed.ts`, registered by the module. A `DEMONSTRATION` seed lands only once it declares the environments it runs in, without production |
|
|
151
152
|
| `INBOUND_CHANNEL_HANDLER` | `channel` + the handler's `handlerRef` (`<moduleRef>.<purpose>`, e.g. `matters.mail-intake`) | the handler that decides what a message arriving on a channel the integration plan declared causes. Its file is `backend-api/src/modules/<moduleRef>/inbound/<handlerRef>.inbound-channel-handler.ts`, and it lands when the module's backend `index.ts` imports that file — which is how it is registered on `inboundHandlers` |
|
|
152
153
|
|
|
@@ -321,6 +322,17 @@ export enum BuildPlanTaskTargetKind {
|
|
|
321
322
|
* catalogue, so the website re-typed the business model's prices by hand.
|
|
322
323
|
*/
|
|
323
324
|
BILLING_CATALOG = 'BILLING_CATALOG',
|
|
325
|
+
/**
|
|
326
|
+
* The application's own ROLES — `CUSTOM_ROLES_CONFIGURATION` in `shared-lib/src/engine/roles.ts`, the
|
|
327
|
+
* organization types that offer them (`availableOrgRoles` in `wildo.saas.config.ts`), their
|
|
328
|
+
* specifications, and the `roles` of the operations they unlock (#2490).
|
|
329
|
+
*
|
|
330
|
+
* Its own kind because none of the others reaches it: the role table is application-wide and lives in
|
|
331
|
+
* the shared library's ENGINE module. Before it existed a requirement naming user groups ("office and
|
|
332
|
+
* field users see different things") had no task able to declare a role, so app-creation-test-005
|
|
333
|
+
* modelled roles as an access-role RESOURCE that nothing reads.
|
|
334
|
+
*/
|
|
335
|
+
APPLICATION_ROLES = 'APPLICATION_ROLES',
|
|
324
336
|
}
|
|
325
337
|
|
|
326
338
|
/**
|
|
@@ -593,6 +605,12 @@ export enum BuildPlanTaskProductKind {
|
|
|
593
605
|
* registered. Produced once per channel the integration plan declares (`inboundChannels`).
|
|
594
606
|
*/
|
|
595
607
|
INBOUND_CHANNEL_HANDLER = 'INBOUND_CHANNEL_HANDLER',
|
|
608
|
+
/**
|
|
609
|
+
* One role the application declares, named by its role name (`FIELD_TECHNICIAN`), which is its key in
|
|
610
|
+
* `CUSTOM_ROLES_CONFIGURATION`. The NAME, not the file: `wildo init` writes `roles.ts` with an empty
|
|
611
|
+
* table, so the file proves nothing (#2490).
|
|
612
|
+
*/
|
|
613
|
+
APPLICATION_ROLE = 'APPLICATION_ROLE',
|
|
596
614
|
}
|
|
597
615
|
|
|
598
616
|
|
|
@@ -614,6 +632,14 @@ export enum BuildPlanDataSeedContent {
|
|
|
614
632
|
* A data seed's key: kebab-case segments joined by `:` (`crm:demo-customers`), the convention a
|
|
615
633
|
* `DataSeedDefinition` documents. Constrained here because the seed's FILE is derived from it.
|
|
616
634
|
*/
|
|
635
|
+
/**
|
|
636
|
+
* An application role's name, as `CUSTOM_ROLES_CONFIGURATION` keys it: upper snake case (`FIELD_TECHNICIAN`).
|
|
637
|
+
* A core role (`ORG_MEMBER`, `APP_ADMIN_SUPER_ADMIN`) is not something an application declares, so the
|
|
638
|
+
* product refuses one: a plan naming it would claim to create a role the engine already owns.
|
|
639
|
+
*/
|
|
640
|
+
export const APPLICATION_ROLE_NAME_PATTERN: RegExp = /^[A-Z][A-Z0-9]*(?:_[A-Z0-9]+)*$/;
|
|
641
|
+
const CORE_ROLE_NAMES: ReadonlySet<string> = new Set<string>([...Object.values(CORE_APP_ROLES), ...Object.values(CORE_ORG_ROLES)]);
|
|
642
|
+
|
|
617
643
|
export const DATA_SEED_KEY_PATTERN: RegExp = /^[a-z0-9]+(?:-[a-z0-9]+)*(?::[a-z0-9]+(?:-[a-z0-9]+)*)*$/;
|
|
618
644
|
|
|
619
645
|
/**
|
|
@@ -685,6 +711,12 @@ export const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [
|
|
|
685
711
|
scope: z.enum(ProviderBindingScope).systemEnum('ProviderBindingScope'),
|
|
686
712
|
}),
|
|
687
713
|
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_BILLING_PRODUCT).systemEnum('BuildPlanTaskProductKind'), productKey: SlugSchema }),
|
|
714
|
+
z.strictObject({
|
|
715
|
+
kind: z.literal(BuildPlanTaskProductKind.APPLICATION_ROLE).systemEnum('BuildPlanTaskProductKind'),
|
|
716
|
+
roleRef: z.string().regex(APPLICATION_ROLE_NAME_PATTERN).refine((roleRef) => !CORE_ROLE_NAMES.has(roleRef), {
|
|
717
|
+
message: 'A core role is the engine\'s; an application role needs a name of its own.',
|
|
718
|
+
}),
|
|
719
|
+
}),
|
|
688
720
|
z.strictObject({
|
|
689
721
|
kind: z.literal(BuildPlanTaskProductKind.APPLICATION_DATA_SEED).systemEnum('BuildPlanTaskProductKind'),
|
|
690
722
|
seedKey: z.string().regex(DATA_SEED_KEY_PATTERN),
|
|
@@ -774,6 +806,8 @@ export function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): r
|
|
|
774
806
|
return [`${product.kind}:${product.scope}:${product.providerRef}`];
|
|
775
807
|
case BuildPlanTaskProductKind.APPLICATION_BILLING_PRODUCT:
|
|
776
808
|
return [`${product.kind}:${product.productKey}`];
|
|
809
|
+
case BuildPlanTaskProductKind.APPLICATION_ROLE:
|
|
810
|
+
return [`${product.kind}:${product.roleRef}`];
|
|
777
811
|
// The key alone: two seeds may write one resource, and the key is what the seed run ledger tracks.
|
|
778
812
|
case BuildPlanTaskProductKind.APPLICATION_DATA_SEED:
|
|
779
813
|
return [`${product.kind}:${product.seedKey}`];
|
|
@@ -800,6 +834,13 @@ export function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): r
|
|
|
800
834
|
*/
|
|
801
835
|
export const BILLING_CATALOG_SKILL_REF = 'configure-billing';
|
|
802
836
|
|
|
837
|
+
/**
|
|
838
|
+
* The skill every application-roles task is authored with (#2490): the role table, the organization
|
|
839
|
+
* types that offer a role, and the operation roles that make it matter. The dispatch derives it from an
|
|
840
|
+
* `APPLICATION_ROLE` product whatever the decomposer wrote.
|
|
841
|
+
*/
|
|
842
|
+
export const APPLICATION_ROLES_SKILL_REF = 'application-roles-authoring';
|
|
843
|
+
|
|
803
844
|
/**
|
|
804
845
|
* The skill every data-seed task is authored with (#2234): levels, modes, business keys, and the
|
|
805
846
|
* environment restriction that keeps demonstration rows out of production. The dispatch derives it from
|
|
@@ -807,6 +848,20 @@ export const BILLING_CATALOG_SKILL_REF = 'configure-billing';
|
|
|
807
848
|
*/
|
|
808
849
|
export const DATA_SEED_SKILL_REF = 'seeding-authoring';
|
|
809
850
|
|
|
851
|
+
/**
|
|
852
|
+
* The skill every PDF-template task is authored with (#2495): the template contract, the file field it fills, and
|
|
853
|
+
* where the generated file is stored. The dispatch derives it from a `PDF_TEMPLATE` product whatever the decomposer
|
|
854
|
+
* wrote.
|
|
855
|
+
*/
|
|
856
|
+
export const PDF_TEMPLATE_SKILL_REF = 'pdf-template-authoring';
|
|
857
|
+
|
|
858
|
+
/**
|
|
859
|
+
* The skill a resource CONFIG task carries when the resource DECLARES personal data (#2495): its retention binding
|
|
860
|
+
* lives in that configuration file, and storage limitation is a duty about personal data. The dispatch reads the
|
|
861
|
+
* declaration from the resource's schema (the engine's personal-data markers), whatever the decomposer wrote.
|
|
862
|
+
*/
|
|
863
|
+
export const RESOURCE_RETENTION_SKILL_REF = 'resource-retention-binding';
|
|
864
|
+
|
|
810
865
|
export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
|
|
811
866
|
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE), moduleRef: ModuleRefSchema }),
|
|
812
867
|
z.strictObject({
|
|
@@ -864,6 +919,7 @@ export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
|
|
|
864
919
|
}),
|
|
865
920
|
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.PROVIDER_BINDING), providerRef: SlugSchema }),
|
|
866
921
|
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.BILLING_CATALOG) }),
|
|
922
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.APPLICATION_ROLES) }),
|
|
867
923
|
]);
|
|
868
924
|
export type BuildPlanTaskTarget = z.infer<typeof BuildPlanTaskTargetSchema>;
|
|
869
925
|
|
|
@@ -1106,7 +1162,7 @@ emit the ordered per-resource stage tasks:
|
|
|
1106
1162
|
|---|---|---|
|
|
1107
1163
|
| **(only when needed)** Ensure module `<id>` slice exists + is registered across runtimes — **normally already done by the foundation step**; emit this only for a module the foundation step did NOT establish (e.g. one added to the plan after foundation ran). Idempotent, never a blind re-scaffold | `model_domain_graph` | `resource-add-module` + `module-registration` |
|
|
1108
1164
|
| Resource `<name>` — domain schema (fields, enums, structural decorators). **Workspace-aware**: when the resource already exists as a compose-born starter (see the workspace section), the objective names the DOMAIN content to add to it; only a resource the workspace does not list gets a skeleton-creation objective | `model_domain_graph` | `resource-add-resource` (skeleton, only when the resource does not exist yet) + `resource-schema-authoring` (the persisted shape) + `application-database-migrations` (**PostgreSQL applications only** — see below) |
|
|
1109
|
-
| Resource `<name>` — config (registry presence, core operation verbs, access / role scope — but NOT cross-resource relationships, which are the dedicated Step 2 tasks) | `model_domain_graph` | `resource-config-wiring` |
|
|
1165
|
+
| Resource `<name>` — config (registry presence, core operation verbs, access / role scope — but NOT cross-resource relationships, which are the dedicated Step 2 tasks) | `model_domain_graph` | `resource-config-wiring` (plus `resource-retention-binding` when the resource declares personal data — the dispatch adds it whatever you write) |
|
|
1110
1166
|
| Resource `<name>` — ui-behavior (its read, form, summary and header surfaces and field chrome, each decided and stated — the resource's own UX) | `shape_user_experience` | `resource-ui-behavior` |
|
|
1111
1167
|
| Resource `<name>` — spec (canonical business semantics — the per-resource documentation capstone) | `model_domain_graph` | `spec-resource-update` |
|
|
1112
1168
|
|
|
@@ -1187,7 +1243,14 @@ tasks editing one file:
|
|
|
1187
1243
|
|
|
1188
1244
|
| Task | Functional topic | Skill (the HOW) |
|
|
1189
1245
|
|---|---|---|
|
|
1190
|
-
| Author the
|
|
1246
|
+
| Author the settings rail placement config from the accepted placement plan | `shape_user_experience` | `settings-placement-authoring` |
|
|
1247
|
+
| Author the sidebar, command palette or user menu placement config from the accepted placement plan | `shape_user_experience` | `config-app-shell` |
|
|
1248
|
+
|
|
1249
|
+
Bind by the FILE the surface is configured in. The settings rail is `settings-hub.config.ts`. The sidebar, the palette
|
|
1250
|
+
and the user menu (its `settingsEntries`) are `app-shell.config.ts`, and `settings-placement-authoring` itself sends
|
|
1251
|
+
work on them to `config-app-shell`: binding it there hands the agent a skill that tells it to go elsewhere. Only
|
|
1252
|
+
`config-app-shell` teaches `runtimeAvailability.visibleToRoles`, which a sidebar group or entry the plan restricts to
|
|
1253
|
+
some roles needs.
|
|
1191
1254
|
|
|
1192
1255
|
Any task whose HOW includes **writing JSX for a bespoke surface** — a ui-behavior
|
|
1193
1256
|
stage, a custom or composite view, an app-level screen — binds
|
|
@@ -1227,7 +1290,9 @@ Rules:
|
|
|
1227
1290
|
|
|
1228
1291
|
- **This is the single home for cross-resource relationships.** A relationship is wired
|
|
1229
1292
|
ONCE, here, by the `module-relationships` skill (which coordinates the FK across the
|
|
1230
|
-
owner's schema + config, the target's relationship map,
|
|
1293
|
+
owner's schema + config, the target's relationship map, the owner's read and edit pages,
|
|
1294
|
+
and both specs coherently). The owner's UI task runs before the FK exists, so showing the
|
|
1295
|
+
reference on its pages is THIS task's work; say so in the objective. Do
|
|
1231
1296
|
NOT also wire it inside the per-resource config task in Step 1 — that config task
|
|
1232
1297
|
establishes the resource's registry presence and core verbs, not its cross-resource
|
|
1233
1298
|
FKs. Emitting the relationship in both places double-counts the work.
|
|
@@ -1259,6 +1324,42 @@ skills". Every skill name you emit MUST appear there, spelled exactly. Do **not*
|
|
|
1259
1324
|
skill name and do not recall one: a name that is not in that list addresses no skill
|
|
1260
1325
|
folder, and the task bound to it cannot be dispatched.
|
|
1261
1326
|
|
|
1327
|
+
### Every requirement verb becomes a task
|
|
1328
|
+
|
|
1329
|
+
Default verbs (create, read, update, list, delete) are what Step 1 already gives every resource.
|
|
1330
|
+
Everything a requirement says the product DOES beyond them is work this step must emit.
|
|
1331
|
+
|
|
1332
|
+
**Start with the domain plan's `lifecycles`.** Each declared transition is one `RESOURCE_OPERATION`
|
|
1333
|
+
task on its resource (target `RESOURCE_STAGE` CONFIG, `operationRef` = the `transitionRef`), skill
|
|
1334
|
+
`resource-status-lifecycle`, ordered after that resource's config task; its objective names the
|
|
1335
|
+
states it moves between and who performs it. A transition with `createsResourceRef` adds a
|
|
1336
|
+
`MODULE_BACKEND` task for the write that creates the target, skill `backend-custom-operation`,
|
|
1337
|
+
ordered after both resources' config tasks. The resource's SCHEMA task objective names the status
|
|
1338
|
+
enum with every declared state, the `initialState` as its default, and each transition's `stampsField`,
|
|
1339
|
+
all excluded from create and update: a transition is the only way to move them.
|
|
1340
|
+
For a resource with `lockedStates` or `finalStates`, the objective of each transition task that moves INTO
|
|
1341
|
+
one of them also restricts the resource's UPDATE to the states that are neither locked nor final. Never plan
|
|
1342
|
+
that freeze as its own `update` operation task: the scaffold already writes `update`, so such a task reads
|
|
1343
|
+
as built before it runs.
|
|
1344
|
+
|
|
1345
|
+
Then read every functional requirement's acceptance criteria for verbs no lifecycle carries, and
|
|
1346
|
+
classify each:
|
|
1347
|
+
|
|
1348
|
+
| The criterion says… | Emit | Skill |
|
|
1349
|
+
|---|---|---|
|
|
1350
|
+
| a record CHANGES STATE ("an accepted quote", "issue the invoice", "mark it paid", "close the case", "a submitted request can be approved") | one `RESOURCE_OPERATION` per transition, on the resource whose state changes, target `RESOURCE_STAGE` (CONFIG). Its objective names the states it moves between and who may call it | `resource-status-lifecycle` |
|
|
1351
|
+
| one record CREATES or FILLS another ("an accepted quote creates a job", "invoice the job") | a `RESOURCE_OPERATION` on the SOURCE resource, plus a `MODULE_BACKEND` task carrying the implementation that writes the target; ordered after both resources' config tasks | `backend-custom-operation` |
|
|
1352
|
+
| a record must not change any more ("an issued invoice cannot be edited") | the objective of the `RESOURCE_OPERATION` task for the transition into that locked or final state also restricts its UPDATE to the open states (never a separate `update` task, which the scaffold already writes) | `resource-status-lifecycle` |
|
|
1353
|
+
| a user group may or may not do something ("technicians cannot see invoices") | an `APPLICATION_ROLES` task (see below), or, for core roles alone, the config tasks' objectives | `application-roles-authoring` / `resource-config-wiring` |
|
|
1354
|
+
| the product PRODUCES a document ("send the quote as a PDF", "print the invoice") | a `PDF_TEMPLATE` task bound to a generated-file field of that resource | `pdf-template-authoring` |
|
|
1355
|
+
| the product SENDS a message ("email the customer", "remind the office") | the `email-templates` generation step, and a `RESOURCE_OPERATION` task whose objective declares the notification on the operation that triggers it | `email-add-template` |
|
|
1356
|
+
| something is shown or computed from other records ("the next action", "what is overdue") | NOT a stored field: a view task from the experience plan, or a computed value in the owning resource's config task objective | — |
|
|
1357
|
+
|
|
1358
|
+
A task emitted from a requirement verb is justified by that requirement: name it in `servesRefs`.
|
|
1359
|
+
It is never the "justified by nothing" speculative work the rule further down warns about. A plan
|
|
1360
|
+
whose requirements describe a workflow and which carries no `define_interaction_semantics` task is
|
|
1361
|
+
not a lighter plan — it is a CRUD shell, and the reviewer reports it as a gap.
|
|
1362
|
+
|
|
1262
1363
|
**Every surface below has its own target kind and its own product kind. Use them.**
|
|
1263
1364
|
Until 2026-09-22 only resources had a vocabulary, so a task for any of these surfaces
|
|
1264
1365
|
either declared no product (and could never be proven landed) or borrowed `MODULE`
|
|
@@ -1270,7 +1371,8 @@ replaced — the judge reports it as a gap.
|
|
|
1270
1371
|
role / scope rules, rate limits — interaction beyond the default resource verbs.
|
|
1271
1372
|
Target `RESOURCE_STAGE` (CONFIG), product `RESOURCE_OPERATION`. Skills: the Backend and
|
|
1272
1373
|
Resources domains of the router (`backend-custom-operation`, `rate-limit-authoring`,
|
|
1273
|
-
`authorization-unit-narrowing`).
|
|
1374
|
+
`authorization-unit-narrowing`). **Derive these from the requirements' VERBS** — read
|
|
1375
|
+
"Every requirement verb becomes a task" below before emitting anything else in this step.
|
|
1274
1376
|
- **`shape_user_experience`** — the cross-resource UX, and you do NOT decide it here. The
|
|
1275
1377
|
**experience plan** (`bottom_up.experience-plan`) already did: which surfaces exist, what
|
|
1276
1378
|
each is for, which presets it reuses, and how the shell, navigation, design system and
|
|
@@ -1289,6 +1391,15 @@ replaced — the judge reports it as a gap.
|
|
|
1289
1391
|
product `APPLICATION_FRONTEND_CONFIG` naming the surface's own `declarationRefs`, and
|
|
1290
1392
|
its skill the one the surface names (`config-navigation`, `config-design-system`,
|
|
1291
1393
|
`config-app-shell`; `views-app-level` for global views — derived at dispatch too).
|
|
1394
|
+
When the plan decides a `home`, the `GLOBAL_VIEWS` task sets it: its objective says to make
|
|
1395
|
+
`homeDefinitionFactory` in `frontend/src/config/global-views.config.ts` return that home, carrying
|
|
1396
|
+
the home's rationale. A `VIEW` home is an application view: `{ compositeViewReference: <the view's
|
|
1397
|
+
ref constant> }`, and the task depends on the task that builds that view. A `RESOURCE_OPERATION`
|
|
1398
|
+
home is `{ resourceOperationPath: … }` naming the resource's registered type (camelCase, not the
|
|
1399
|
+
slug), the operation, `isOperationDefault: true`, `isBulkOperation: false` and the default variant's
|
|
1400
|
+
`variantKey`: the root matches all of them exactly and silently shows the welcome page on a
|
|
1401
|
+
mismatch. That task depends on the resource's config task. Without the home the application opens
|
|
1402
|
+
on the framework's welcome page whatever the plan says.
|
|
1292
1403
|
- one task per planned MILESTONE, target `MODULE_BACKEND` on the milestone's module,
|
|
1293
1404
|
product `APPLICATION_MILESTONE` naming its `milestoneRef`, skill
|
|
1294
1405
|
`milestones-and-celebrations` (`EXPERIENCE_MILESTONE_SKILL_REF`). It depends on the config stage of its
|
|
@@ -1318,7 +1429,7 @@ replaced — the judge reports it as a gap.
|
|
|
1318
1429
|
- a custom UI component / widget → target `MODULE_FRONTEND`, product `CUSTOM_COMPONENT`;
|
|
1319
1430
|
skills `engine-component-registration`, `frontend-component-catalog`;
|
|
1320
1431
|
- a PDF template / renderer → target `MODULE_BACKEND`, product `PDF_TEMPLATE`; skill
|
|
1321
|
-
`pdf-template-authoring
|
|
1432
|
+
`pdf-template-authoring` (the dispatch adds it whatever you write);
|
|
1322
1433
|
- custom backend implementation logic → target `MODULE_BACKEND`, product the
|
|
1323
1434
|
`RESOURCE_OPERATION` it serves; skill `backend-addon-wiring`;
|
|
1324
1435
|
- workers and minions → you do NOT decide them here. The **integration plan**
|
|
@@ -1352,6 +1463,26 @@ replaced — the judge reports it as a gap.
|
|
|
1352
1463
|
`provider-operation-calls` and `configure-billing` as the task's further reading when the
|
|
1353
1464
|
binding is one an application then CALLS. Environment and infra config are the
|
|
1354
1465
|
foundation's, not a build task's.
|
|
1466
|
+
- **What the domain plan left to the engine** — its `engineRealizedRequirements` name the
|
|
1467
|
+
requirements met by configuration rather than a module. Each still owes configuration work:
|
|
1468
|
+
`APPLICATION_ROLES` → the roles task below; `NOTIFICATIONS` → the triggering operation's task
|
|
1469
|
+
(the verb table above); `PERSONAL_DATA` and `AUDIT_TRAIL` → the declarations in the resource
|
|
1470
|
+
config tasks' objectives; `BILLING` → the billing catalogue task; `GUIDANCE` → the experience
|
|
1471
|
+
plan's guidance tasks; `GOVERNED_DOCUMENT` → no build task (the compliance lane composes it);
|
|
1472
|
+
`ORGANIZATION_MEMBERSHIP` and `LOCALIZATION` → no task beyond the foundation's capabilities.
|
|
1473
|
+
Never emit a task that builds one of these as a resource.
|
|
1474
|
+
- **The application roles** — target `APPLICATION_ROLES`, when a requirement names groups of
|
|
1475
|
+
users with different access ("office and field staff", "technicians cannot see invoices",
|
|
1476
|
+
"read-only reviewers"). Emit ONE task (the role table is one file) producing one
|
|
1477
|
+
`APPLICATION_ROLE` per group that no core role covers, skill `application-roles-authoring`
|
|
1478
|
+
(the dispatch adds it whatever you write), and `servesRefs` naming the requirement. Reuse the
|
|
1479
|
+
core roles first: the broadest internal group usually holds `ORG_MEMBER`, and a requirement met by
|
|
1480
|
+
them alone ("only administrators may delete") needs no roles task, only config tasks that say which
|
|
1481
|
+
operations are restricted. The task declares the roles, offers them on the organization types,
|
|
1482
|
+
and narrows the `roles` of the operations they govern, so order it AFTER the config tasks of every
|
|
1483
|
+
resource it narrows, and say in its objective which operations each role may call. Never answer a
|
|
1484
|
+
role requirement with a resource holding roles, permissions or role assignments: nothing in the
|
|
1485
|
+
engine reads it.
|
|
1355
1486
|
- **The billing catalogue** — target `BILLING_CATALOG`, and the **business model** decided it:
|
|
1356
1487
|
its pricing plans are the products the application sells. Emit ONE task (the catalogue is one
|
|
1357
1488
|
file, so two tasks would write over each other) producing one `APPLICATION_BILLING_PRODUCT` per
|
|
@@ -1378,9 +1509,15 @@ replaced — the judge reports it as a gap.
|
|
|
1378
1509
|
plausible records (three to eight) for each main resource a person meets first, in the market's
|
|
1379
1510
|
own language and examples, consistent with each other (an enquiry names a customer that exists).
|
|
1380
1511
|
One seed per resource. The seed declares `allowedApplicationEnvironments` without production,
|
|
1381
|
-
and the task lands only once it does, so these rows can never sit beside real ones.
|
|
1382
|
-
|
|
1383
|
-
|
|
1512
|
+
and the task lands only once it does, so these rows can never sit beside real ones. A resource
|
|
1513
|
+
that belongs to an organization is seeded per organization, on organization creation.
|
|
1514
|
+
A seed whose rows point at rows ANOTHER seed writes (a contact's customer, a quote's customer, an
|
|
1515
|
+
invoice's job) links them with `referenceDataSeedRow` and lists that seed in `dependsOn` — the
|
|
1516
|
+
engine resolves each reference to the row's `_id`, and nothing else can, because the id is
|
|
1517
|
+
generated. Say so in the task's objective: name the seed it references and the field each
|
|
1518
|
+
reference fills, so the worker does not have to discover the mechanism. Order a seed after its
|
|
1519
|
+
resource's schema and config tasks, after the relationship tasks for the links its rows carry,
|
|
1520
|
+
and after the task of every seed whose rows it references. Name each `seedKey`
|
|
1384
1521
|
`<moduleRef>:<purpose>` (`crm:demo-customers`): the namespace keeps one module's seeds apart from
|
|
1385
1522
|
another's. Never a seed for a resource the engine owns (users, organizations, memberships).
|
|
1386
1523
|
- **The website** — target `WEBSITE`, and you do NOT decide its content here. The
|
|
@@ -1439,7 +1576,8 @@ Rules:
|
|
|
1439
1576
|
in Step 1 and needs only that resource's schema/config — see the ordering axes.)
|
|
1440
1577
|
- **Draw tasks from the definition set, not a blank page.** A UX or operation task
|
|
1441
1578
|
earns its existence from a requirement or feature-draft; a task justified by nothing
|
|
1442
|
-
in the definition set is a CONCERN (speculative work).
|
|
1579
|
+
in the definition set is a CONCERN (speculative work). A task serving a requirement verb
|
|
1580
|
+
(the table above) always earns it, even when no feature-draft mentions the operation.
|
|
1443
1581
|
|
|
1444
1582
|
## Step 4 — Interleave the companion-owned generation steps
|
|
1445
1583
|
|
|
@@ -1605,6 +1743,6 @@ what reaches you is this method, your declared inputs, and the brief's own secti
|
|
|
1605
1743
|
|
|
1606
1744
|
## Reviewer checklist — `build-plan-coherent`
|
|
1607
1745
|
|
|
1608
|
-
These
|
|
1746
|
+
These twelve invariants are the criteria of this playbook's compiled evaluation treatment (`application-creation:evaluation-treatment/build-plan-coherent`, one criterion per invariant, invariants 2 and 2b sharing one), which the advisory judge runs after every landing. They are kept here as creator-facing review guidance too, so a reviewer and the judge read the same words:
|
|
1609
1747
|
|
|
1610
|
-
Judge whether the drafted build plan is a coherent, complete, correctly-ordered decomposition of the approved domain plan into coding-agent tasks — WITHOUT straying into how those tasks execute. Assess ten invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) MODULE + RESOURCE COVERAGE — every resource in every module's inventory (mainResources + supportingResources) has build tasks; a resource with no task is a GAP (the build would not produce it). Task `moduleRef` values must be module ids the workspace section lists (an invented module id is a GAP — the dispatcher cannot route it), and a task whose objective CREATES a resource the workspace section shows already exists — instead of enriching it — is a CONCERN (it dispatches a no-op). Module slices are scaffolded by the foundation step (a sibling playbook), so a module needs a dedicated ensure-module task ONLY where foundation did not establish it — a module whose resources have tasks but which carries no redundant scaffold task is NOT a GAP (do not flag the absence of a module-scaffold task foundation already owns); a module added to the plan after foundation with neither a foundation slice nor an ensure-module task IS a GAP. Every pricing plan the business model declares must be an `APPLICATION_BILLING_PRODUCT` of a `BILLING_CATALOG` task whose `servesRefs` name it; a declared plan with no billing product is a GAP. A plan with main resources and no `DEMONSTRATION` `APPLICATION_DATA_SEED` task is a CONCERN: the application would open empty. (2) TASK WELL-FORMEDNESS — every task names exactly ONE functional topic that is a real MetaWorkflow_FunctionalTopic value (configure_application_foundation / model_domain_graph / define_interaction_semantics / shape_user_experience / extend_application / connect_runtime_and_external_capabilities / assemble_verify_and_iterate) and at least one skill that is a real folder in the app-knowledge skill catalog; a task with an invented topic or a dangling skill is a GAP. (2b) PRODUCT DECLARATION — every task except a COMPANION_GENERATION_STEP declares at least one product in `produces`, and a generation step declares none; a coding task with an empty `produces` is a GAP, because it has no declared output to probe. The host can advance after a COMPLETED durable run, but carries the task in `unverifiableLandedTaskRefs`; that means ran, not proven. Repair the product declaration rather than treating this fallback as evidence of correct output. A product must name something COMPOSITION DOES NOT ALREADY WRITE — the fields a schema gains rather than its file, the verbs a config gains rather than its file, both endpoints of a relationship rather than one — so a product naming only a scaffolded artifact is a GAP wearing a declaration. Two tasks claiming the SAME artifact is a GAP as well (landing becomes undecidable); two tasks enriching one resource with DIFFERENT fields is correct and not a finding. A cross-resource FOREIGN KEY declared on a schema task's `produces` is a GAP — the relationship task is its single home (Step 2), and declaring it twice attributes one artifact to two tasks; a schema task's products are the resource's OWN domain fields. (3) PER-RESOURCE STAGE ORDER — for each resource, its tasks respect the inner order schema -> config -> ui-behavior -> spec; a config task ordered before that resource's schema task, or a spec task before its ui-behavior task, is a GAP (the build stage would run against a missing prerequisite). A supportingResource (e.g. a pure junction / lookup entity) may legitimately OMIT stages it does not need — a junction with schema + config and no ui-behavior is fine; only an out-of-ORDER stage (or a mainResource missing schema/config) is a GAP, not an intentionally-omitted stage on a supporting resource. (4) TOPIC DEPENDENCY ORDER — tasks respect the topic dependency edges (model_domain_graph before define_interaction_semantics; app-level shape_user_experience [views / navigation composing multiple resources or operations] after the interaction semantics and resources it composes; extend_application after the UX it extends; connect_runtime_and_external_capabilities after the resources it connects). Note the deliberate exception: a resource's OWN ui-behavior (its field displays / forms, a shape_user_experience task) depends only on that resource's own schema + config and MAY precede cross-resource operations — that is NOT a violation. What IS a GAP: an app-level view composing resources/operations placed before they exist, an integration task before the resources it connects, or any user-experience task before that resource's schema task. The per-resource spec task is a documentation capstone (topic model_domain_graph) and must be ordered after the schema / config / ui-behavior stages it documents; a spec task before its ui-behavior stage is a GAP. (5) RELATIONSHIP COVERAGE — every relationship-draft whose two endpoints are resources the domain plan declares has a wiring task (bound to the module-relationships skill) ordered AFTER both endpoint resources' schema tasks; a relationship with no wiring task, or one ordered before its endpoints exist, is a GAP. A relationship to a resource no module declares is NOT this invariant: no task can wire it, so it is invariant (8)'s. (6) COMPANION-GENERATION INTERLEAVE — the executable companion-owned generation steps (`i18n-labels`, `email-templates`, `logo`, plus `database-migrations` for a PostgreSQL-backed application) are present and placed AFTER the resources / modules whose output they consume; a labels-generation task ordered before the resources it labels, or a missing executable generation step for authored surfaces, is a CONCERN. `logo` is the exception to the ordering half — it consumes the brand brief rather than any code surface, so it is unordered with respect to resource work and only its ABSENCE (on an application with a brand brief) is a CONCERN. The migration step follows the schema stages whose drift it migrates and is not authored for MongoDB. Do NOT flag the absence of an `i18n-translations` step — the dispatch host derives it after `i18n-labels`. Do NOT flag the absence of a seeds GENERATION step — none exists; seeding is an `APPLICATION_DATA_SEED` coding task, judged under invariant (1). (7) BOUNDARY DISCIPLINE — the plan stays at DECOMPOSITION depth: it names tasks, their topic, their skill(s), their target, and their ordering intent; it does NOT specify how a task is DISPATCHED (dispatch locking and concurrency, change-set capture, git baseline, verify/quality-gate mechanics = the dispatch-orchestration playbook) and does NOT solve multi-agent SCALE or interleaving concurrency (= the scale playbook). Any task that describes how a task EXECUTES rather than WHAT it builds, or that authors a schema / resolves a cardinality into a concrete FK / generates code, is a CONCERN (scope creep out of the decomposition phase). (8) CONCEPTION BUILDABLE — this one faults the CONCEPTION, never the plan: a GAP when the domain plan declares a module, resource or relationship no build target can express however it is decomposed, or when the computed coherence report shows a dangling reference or unrealised decision in the conception (a domain-plan resource another family names that does not exist, a composition surface no plan realises) that the build would have to invent to proceed. An element the plan merely FORGOT is invariant (1), not this one — only a conception GAP sends the application back to its conception lane, which is the most expensive way to fix an omission. Name the conception element. (9) EXPERIENCE COVERAGE — every view, configuration, milestone and piece of guidance the experience plan declares has its task (a view task carrying the plan's viewRef verbatim, an onboarding document's objective naming its hostViewRef); an entry with no task is a GAP, and an objective that drops what the plan decided for its entry (reused components, the moment, the gate) is a CONCERN. With NO experience plan the plan rightly carries none of these tasks: mark PASS and begin the note with 'NO EXPERIENCE PLAN:' naming what the application will lack — never a CONCERN or GAP, because the decomposer cannot produce an upstream family by revising. (The deterministic gates and the creator's approval remain the floors; the judge's verdicts are advisory notes beside them.)
|
|
1748
|
+
Judge whether the drafted build plan is a coherent, complete, correctly-ordered decomposition of the approved domain plan into coding-agent tasks — WITHOUT straying into how those tasks execute. Assess twelve invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) MODULE + RESOURCE COVERAGE — every resource in every module's inventory (mainResources + supportingResources) has build tasks; a resource with no task is a GAP (the build would not produce it). Task `moduleRef` values must be module ids the workspace section lists (an invented module id is a GAP — the dispatcher cannot route it), and a task whose objective CREATES a resource the workspace section shows already exists — instead of enriching it — is a CONCERN (it dispatches a no-op). Module slices are scaffolded by the foundation step (a sibling playbook), so a module needs a dedicated ensure-module task ONLY where foundation did not establish it — a module whose resources have tasks but which carries no redundant scaffold task is NOT a GAP (do not flag the absence of a module-scaffold task foundation already owns); a module added to the plan after foundation with neither a foundation slice nor an ensure-module task IS a GAP. Every pricing plan the business model declares must be an `APPLICATION_BILLING_PRODUCT` of a `BILLING_CATALOG` task whose `servesRefs` name it; a declared plan with no billing product is a GAP. A plan with main resources and no `DEMONSTRATION` `APPLICATION_DATA_SEED` task is a CONCERN: the application would open empty. A seed task whose rows reference another seed's rows (a contact's customer) that is not ordered after that seed's task is a GAP — the reference resolves only against rows already written. (2) TASK WELL-FORMEDNESS — every task names exactly ONE functional topic that is a real MetaWorkflow_FunctionalTopic value (configure_application_foundation / model_domain_graph / define_interaction_semantics / shape_user_experience / extend_application / connect_runtime_and_external_capabilities / assemble_verify_and_iterate) and at least one skill that is a real folder in the app-knowledge skill catalog; a task with an invented topic or a dangling skill is a GAP. (2b) PRODUCT DECLARATION — every task except a COMPANION_GENERATION_STEP declares at least one product in `produces`, and a generation step declares none; a coding task with an empty `produces` is a GAP, because it has no declared output to probe. The host can advance after a COMPLETED durable run, but carries the task in `unverifiableLandedTaskRefs`; that means ran, not proven. Repair the product declaration rather than treating this fallback as evidence of correct output. A product must name something COMPOSITION DOES NOT ALREADY WRITE — the fields a schema gains rather than its file, the verbs a config gains rather than its file, both endpoints of a relationship rather than one — so a product naming only a scaffolded artifact is a GAP wearing a declaration. Two tasks claiming the SAME artifact is a GAP as well (landing becomes undecidable); two tasks enriching one resource with DIFFERENT fields is correct and not a finding. A cross-resource FOREIGN KEY declared on a schema task's `produces` is a GAP — the relationship task is its single home (Step 2), and declaring it twice attributes one artifact to two tasks; a schema task's products are the resource's OWN domain fields. (3) PER-RESOURCE STAGE ORDER — for each resource, its tasks respect the inner order schema -> config -> ui-behavior -> spec; a config task ordered before that resource's schema task, or a spec task before its ui-behavior task, is a GAP (the build stage would run against a missing prerequisite). A supportingResource (e.g. a pure junction / lookup entity) may legitimately OMIT stages it does not need — a junction with schema + config and no ui-behavior is fine; only an out-of-ORDER stage (or a mainResource missing schema/config) is a GAP, not an intentionally-omitted stage on a supporting resource. (4) TOPIC DEPENDENCY ORDER — tasks respect the topic dependency edges (model_domain_graph before define_interaction_semantics; app-level shape_user_experience [views / navigation composing multiple resources or operations] after the interaction semantics and resources it composes; extend_application after the UX it extends; connect_runtime_and_external_capabilities after the resources it connects). Note the deliberate exception: a resource's OWN ui-behavior (its field displays / forms, a shape_user_experience task) depends only on that resource's own schema + config and MAY precede cross-resource operations — that is NOT a violation. What IS a GAP: an app-level view composing resources/operations placed before they exist, an integration task before the resources it connects, or any user-experience task before that resource's schema task. The per-resource spec task is a documentation capstone (topic model_domain_graph) and must be ordered after the schema / config / ui-behavior stages it documents; a spec task before its ui-behavior stage is a GAP. (5) RELATIONSHIP COVERAGE — every relationship-draft whose two endpoints are resources the domain plan declares has a wiring task (bound to the module-relationships skill) ordered AFTER both endpoint resources' schema tasks; a relationship with no wiring task, or one ordered before its endpoints exist, is a GAP. A relationship to a resource no module declares is NOT this invariant: no task can wire it, so it is invariant (8)'s. (6) COMPANION-GENERATION INTERLEAVE — the executable companion-owned generation steps (`i18n-labels`, `email-templates`, `logo`, plus `database-migrations` for a PostgreSQL-backed application) are present and placed AFTER the resources / modules whose output they consume; a labels-generation task ordered before the resources it labels, or a missing executable generation step for authored surfaces, is a CONCERN. `logo` is the exception to the ordering half — it consumes the brand brief rather than any code surface, so it is unordered with respect to resource work and only its ABSENCE (on an application with a brand brief) is a CONCERN. The migration step follows the schema stages whose drift it migrates and is not authored for MongoDB. Do NOT flag the absence of an `i18n-translations` step — the dispatch host derives it after `i18n-labels`. Do NOT flag the absence of a seeds GENERATION step — none exists; seeding is an `APPLICATION_DATA_SEED` coding task, judged under invariant (1). (7) BOUNDARY DISCIPLINE — the plan stays at DECOMPOSITION depth: it names tasks, their topic, their skill(s), their target, and their ordering intent; it does NOT specify how a task is DISPATCHED (dispatch locking and concurrency, change-set capture, git baseline, verify/quality-gate mechanics = the dispatch-orchestration playbook) and does NOT solve multi-agent SCALE or interleaving concurrency (= the scale playbook). Any task that describes how a task EXECUTES rather than WHAT it builds, or that authors a schema / resolves a cardinality into a concrete FK / generates code, is a CONCERN (scope creep out of the decomposition phase). (8) CONCEPTION BUILDABLE — this one faults the CONCEPTION, never the plan: a GAP when the domain plan declares a module, resource or relationship no build target can express however it is decomposed, or when the computed coherence report shows a dangling reference or unrealised decision in the conception (a domain-plan resource another family names that does not exist, a composition surface no plan realises) that the build would have to invent to proceed. An element the plan merely FORGOT is invariant (1), not this one — only a conception GAP sends the application back to its conception lane, which is the most expensive way to fix an omission. Name the conception element. (9) EXPERIENCE COVERAGE — every view, configuration, milestone and piece of guidance the experience plan declares has its task (a view task carrying the plan's viewRef verbatim, an onboarding document's objective naming its hostViewRef), and a decided `home` is set by the `GLOBAL_VIEWS` task's objective (it names `homeDefinitionFactory` and the home); an entry with no task, or a decided home no objective sets, is a GAP, and an objective that drops what the plan decided for its entry (reused components, the moment, the gate) is a CONCERN. With NO experience plan the plan rightly carries none of these tasks: mark PASS and begin the note with 'NO EXPERIENCE PLAN:' naming what the application will lack — never a CONCERN or GAP, because the decomposer cannot produce an upstream family by revising. (10) ROLE COVERAGE — every requirement that names groups of users with different access is served by an `APPLICATION_ROLES` task producing one `APPLICATION_ROLE` per group no core role covers, ordered after the config tasks of the resources it narrows; a group with no role, or a role requirement answered by a task or resource that stores roles or permissions as data, is a GAP; a roles task ordered before a config task it narrows, or whose objective does not say which operations each role may call, is a CONCERN. (11) INTERACTION COVERAGE — every transition the domain plan's lifecycles declare has its `RESOURCE_OPERATION` task (and a `MODULE_BACKEND` task when it creates a resource), and every functional acceptance criterion whose verb goes beyond the default resource verbs (a state change, one record creating or filling another, a record that must stop changing, a produced document, a sent message) is served by a task of the matching kind (`RESOURCE_OPERATION`, a `MODULE_BACKEND` implementation, `PDF_TEMPLATE`, the email generation step) whose `servesRefs` name the requirement; a plan whose requirements describe a workflow and which carries no interaction task, or a state change served only by a config task that leaves the status freely editable, is a GAP; a derived value (a next action, an overdue flag) planned as a stored field is a CONCERN. (The deterministic gates and the creator's approval remain the floors; the judge's verdicts are advisory notes beside them.)
|