@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 +1 @@
|
|
|
1
|
-
{"version":3,"file":"framework-knowledge.loader.d.ts","sourceRoot":"","sources":["
|
|
1
|
+
{"version":3,"file":"framework-knowledge.loader.d.ts","sourceRoot":"","sources":["../../src/framework-knowledge.loader.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EACV,yCAAyC,EAEzC,sDAAsD,EACtD,0BAA0B,EAC1B,8BAA8B,EAC9B,0BAA0B,EAE1B,uCAAuC,EACvC,oCAAoC,EACpC,6BAA6B,EAC7B,uBAAuB,EACvB,4BAA4B,EAC5B,iCAAiC,EAClC,MAAM,kCAAkC,CAAC;AAC1C,OAAO,EAAwC,8BAA8B,EAAE,MAAM,kCAAkC,CAAC;AAsFxH,wBAAgB,kCAAkC,CAAC,YAAY,EAAE,MAAM,GAAG,MAAM,CAE/E;AAED,wBAAgB,qCAAqC,IAAI,8BAA8B,CAAC,0BAA0B,CAAC,CAalH;AAED,wBAAgB,6BAA6B,IAAI,0BAA0B,CAE1E;AAED,wBAAgB,gCAAgC,IAAI,oCAAoC,EAAE,CAEzF;AAED,wBAAgB,+BAA+B,IAAI,4BAA4B,CAE9E;AAED,wBAAgB,4BAA4B,IAAI,iCAAiC,EAAE,CAElF;AAED,wBAAgB,0BAA0B,CAAC,OAAO,EAAE,MAAM,GAAG,uBAAuB,GAAG,IAAI,CAyB1F;AAED,wBAAgB,6BAA6B,CAAC,aAAa,SAAS,8BAA8B,EAChG,YAAY,EAAE,aAAa,GAC1B,6BAA6B,CAAC,aAAa,CAAC,CAE9C;AAED;;;GAGG;AACH,wBAAgB,+BAA+B,IAAI,uCAAuC,EAAE,CAK3F;AAED;;;;;;;;;GASG;AACH,wBAAgB,6BAA6B,CAAC,GAAG,EAAE,MAAM,GAAG,0BAA0B,GAAG,IAAI,CAmD5F;AAED,4EAA4E;AAC5E,wBAAgB,6CAA6C,IAAI,sDAAsD,EAAE,CAGxH;AAED;;;;;;GAMG;AACH,wBAAgB,4CAA4C,CAAC,GAAG,EAAE,MAAM,EAAE,OAAO,CAAC,EAAE,MAAM,GAAG,yCAAyC,GAAG,IAAI,CA0B5I;AAED;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAgB,sDAAsD,CACpE,GAAG,EAAE,MAAM,EACX,OAAO,CAAC,EAAE,MAAM,GACf,8BAA8B,CAAC,OAAO,CAAC,GAAG,IAAI,CAWhD;AAED;;;;;GAKG;AACH;;;;;;;GAOG;AACH,MAAM,WAAW,8BAA8B;IAC7C,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;CAC1B;AAED;;;;;;;;;;;;;;GAcG;AACH,wBAAgB,oCAAoC,IAAI,8BAA8B,EAAE,CAsBvF;AAED;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAgB,+BAA+B,CAAC,SAAS,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAQhF;AAED,wBAAgB,gCAAgC,IAAI,MAAM,GAAG,IAAI,CAQhE"}
|
package/dist/esm/index.d.ts.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["
|
|
1
|
+
{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA,cAAc,kCAAkC,CAAC;AACjD,cAAc,sCAAsC,CAAC;AACrD,cAAc,iCAAiC,CAAC"}
|
|
@@ -20,7 +20,7 @@ export declare const playbookDefinition: {
|
|
|
20
20
|
readonly ref: "bottom_up.assemble-verify";
|
|
21
21
|
readonly version: "0.4.0";
|
|
22
22
|
readonly phase: "bottom_up";
|
|
23
|
-
readonly intent: "Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over EVERY workspace package the application has (specifications, shared-lib, backend-api, frontend, and the website, technical documentation site, workers and minions it composed), derived from those packages rather than listed, OUTSIDE any coding agent, and reports a per-check outcome. It fixes NOTHING: a failure is surfaced for a refinement re-dispatch, which is a different playbook's job, and it authors no schemas and writes no code. Deliberately DISTINCT from the refinement phase's coverage audit, which also binds topic 7 but asks a SEMANTIC question (does the built app match the intent — specs diffed against introspected reality). This playbook never diffs intent against reality; if you are judging coverage you are in the refinement lane. Scope honesty: the check set is the whole-application TYPECHECK across every package — the question 'does it compile as one program', which no per-task check can answer because the dispatch lane typechecks only the package a task mutated — PLUS the schema-plan drift gate (`check:schema-plan-in-sync`), which asks whether the modelled resources have migrations behind them. The second is not a variant of the first: on a PostgreSQL-backed application a table exists only because a migration built it, so a resource whose migration was never generated compiles green in every package and then refuses to boot on `postgresql_table_schema_mismatch` — invisible to a typecheck, because no type in the program knows whether a table exists. It is safe on MongoDB applications and on unbuilt trees because it resolves three outcomes (not adopted / could-not-ask / decided) rather than reading an exit code. Since #2228 it also asks the two questions a typecheck cannot: does each optional site BUILD (the website's `astro build`, the documentation portal's `docusaurus build`; an absent package answers 'nothing to build'), and does the configuration pass `wildo config validate` (errors fail, warnings do not, a missing CLI is 'we could not ask')
|
|
23
|
+
readonly intent: "Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over EVERY workspace package the application has (specifications, shared-lib, backend-api, frontend, and the website, technical documentation site, workers and minions it composed), derived from those packages rather than listed, OUTSIDE any coding agent, and reports a per-check outcome. It fixes NOTHING: a failure is surfaced for a refinement re-dispatch, which is a different playbook's job, and it authors no schemas and writes no code. Deliberately DISTINCT from the refinement phase's coverage audit, which also binds topic 7 but asks a SEMANTIC question (does the built app match the intent — specs diffed against introspected reality). This playbook never diffs intent against reality; if you are judging coverage you are in the refinement lane. Scope honesty: the check set is the whole-application TYPECHECK across every package — the question 'does it compile as one program', which no per-task check can answer because the dispatch lane typechecks only the package a task mutated — PLUS the schema-plan drift gate (`check:schema-plan-in-sync`), which asks whether the modelled resources have migrations behind them. The second is not a variant of the first: on a PostgreSQL-backed application a table exists only because a migration built it, so a resource whose migration was never generated compiles green in every package and then refuses to boot on `postgresql_table_schema_mismatch` — invisible to a typecheck, because no type in the program knows whether a table exists. It is safe on MongoDB applications and on unbuilt trees because it resolves three outcomes (not adopted / could-not-ask / decided) rather than reading an exit code. Since #2228 it also asks the two questions a typecheck cannot: does each optional site BUILD (the website's `astro build`, the documentation portal's `docusaurus build`; an absent package answers 'nothing to build'), and does the configuration pass `wildo config validate` (errors fail, warnings do not, a missing CLI is 'we could not ask'); and it asks the RUNNING backend's readiness and renders the frontend in a browser, each reported unrun rather than passed when the stack is not up. Since #2404 it also builds the resources registry offline, as the backend's startup does (`check:resources-registry-init`), so a resource configuration the engine refuses at start is named before the running backend is asked. The whole test suite and OpenAPI/docs regeneration are NOT in this set.";
|
|
24
24
|
readonly preconditions: readonly [{
|
|
25
25
|
readonly kind: "artifact_exists";
|
|
26
26
|
readonly selector: {
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.assemble-verify/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;CAiCrB,CAAC"}
|
|
@@ -20,7 +20,7 @@ export const playbookDefinition = {
|
|
|
20
20
|
"ref": "bottom_up.assemble-verify",
|
|
21
21
|
"version": "0.4.0",
|
|
22
22
|
"phase": "bottom_up",
|
|
23
|
-
"intent": "Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over EVERY workspace package the application has (specifications, shared-lib, backend-api, frontend, and the website, technical documentation site, workers and minions it composed), derived from those packages rather than listed, OUTSIDE any coding agent, and reports a per-check outcome. It fixes NOTHING: a failure is surfaced for a refinement re-dispatch, which is a different playbook's job, and it authors no schemas and writes no code. Deliberately DISTINCT from the refinement phase's coverage audit, which also binds topic 7 but asks a SEMANTIC question (does the built app match the intent — specs diffed against introspected reality). This playbook never diffs intent against reality; if you are judging coverage you are in the refinement lane. Scope honesty: the check set is the whole-application TYPECHECK across every package — the question 'does it compile as one program', which no per-task check can answer because the dispatch lane typechecks only the package a task mutated — PLUS the schema-plan drift gate (`check:schema-plan-in-sync`), which asks whether the modelled resources have migrations behind them. The second is not a variant of the first: on a PostgreSQL-backed application a table exists only because a migration built it, so a resource whose migration was never generated compiles green in every package and then refuses to boot on `postgresql_table_schema_mismatch` — invisible to a typecheck, because no type in the program knows whether a table exists. It is safe on MongoDB applications and on unbuilt trees because it resolves three outcomes (not adopted / could-not-ask / decided) rather than reading an exit code. Since #2228 it also asks the two questions a typecheck cannot: does each optional site BUILD (the website's `astro build`, the documentation portal's `docusaurus build`; an absent package answers 'nothing to build'), and does the configuration pass `wildo config validate` (errors fail, warnings do not, a missing CLI is 'we could not ask')
|
|
23
|
+
"intent": "Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over EVERY workspace package the application has (specifications, shared-lib, backend-api, frontend, and the website, technical documentation site, workers and minions it composed), derived from those packages rather than listed, OUTSIDE any coding agent, and reports a per-check outcome. It fixes NOTHING: a failure is surfaced for a refinement re-dispatch, which is a different playbook's job, and it authors no schemas and writes no code. Deliberately DISTINCT from the refinement phase's coverage audit, which also binds topic 7 but asks a SEMANTIC question (does the built app match the intent — specs diffed against introspected reality). This playbook never diffs intent against reality; if you are judging coverage you are in the refinement lane. Scope honesty: the check set is the whole-application TYPECHECK across every package — the question 'does it compile as one program', which no per-task check can answer because the dispatch lane typechecks only the package a task mutated — PLUS the schema-plan drift gate (`check:schema-plan-in-sync`), which asks whether the modelled resources have migrations behind them. The second is not a variant of the first: on a PostgreSQL-backed application a table exists only because a migration built it, so a resource whose migration was never generated compiles green in every package and then refuses to boot on `postgresql_table_schema_mismatch` — invisible to a typecheck, because no type in the program knows whether a table exists. It is safe on MongoDB applications and on unbuilt trees because it resolves three outcomes (not adopted / could-not-ask / decided) rather than reading an exit code. Since #2228 it also asks the two questions a typecheck cannot: does each optional site BUILD (the website's `astro build`, the documentation portal's `docusaurus build`; an absent package answers 'nothing to build'), and does the configuration pass `wildo config validate` (errors fail, warnings do not, a missing CLI is 'we could not ask'); and it asks the RUNNING backend's readiness and renders the frontend in a browser, each reported unrun rather than passed when the stack is not up. Since #2404 it also builds the resources registry offline, as the backend's startup does (`check:resources-registry-init`), so a resource configuration the engine refuses at start is named before the running backend is asked. The whole test suite and OpenAPI/docs regeneration are NOT in this set.",
|
|
24
24
|
"preconditions": [
|
|
25
25
|
{ "kind": "artifact_exists", "selector": { "family": "build-plan" } }
|
|
26
26
|
],
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.assemble-verify/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,2BAA2B;IAClC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,suFAAsuF;IAChvF,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,YAAY,EAAE,EAAE;KACtE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,YAAY,EAAE;KAC3B;IACD,SAAS,EAAE,EAAE;IACb,QAAQ,EAAE;QACR,WAAW,EAAE;YACX,iCAAiC;SAClC;KACF;IACD,UAAU,EAAE,mBAAmB;IAC/B,UAAU,EAAE,gBAAgB;IAC5B;;;;;;;OAOG;IACH,QAAQ,EAAE;QACR,SAAS,EAAE,EAAE;QACb,eAAe,EAAE,OAAO;KACzB;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for topic 7 — the app-wide assemble/verify step.\n *\n * REBUILT rather than restored (issue #147). A playbook of this ref existed from\n * 2026-07-10 and was deleted on 2026-08-25 with the app-creation digest\n * demolition; the question it asked went with it, even though answering \"does\n * the built application assemble?\" needs no digests. Restoring it verbatim was\n * rejected: it declared the retired `COMPOSITE` executor, depended on two\n * families the demolition removed (`foundation-manifest`, `build-verification`),\n * and its method was explicit that NONE of its checks were actually run by the\n * runner — `// TODO CLI COMMAND:` placeholders and \"companion affordances that\n * do not exist yet\".\n *\n * What is different now is that the checks RUN. `DETERMINISTIC_CLI` is honoured\n * by the runtime as of #147, and the check refs below resolve through the same\n * closed `APPLICATION_CODING_TASK_VERIFICATION_CATALOG` a coding task uses, so\n * an unknown ref is refused rather than silently skipped.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.assemble-verify\",\n \"version\": \"0.4.0\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over EVERY workspace package the application has (specifications, shared-lib, backend-api, frontend, and the website, technical documentation site, workers and minions it composed), derived from those packages rather than listed, OUTSIDE any coding agent, and reports a per-check outcome. It fixes NOTHING: a failure is surfaced for a refinement re-dispatch, which is a different playbook's job, and it authors no schemas and writes no code. Deliberately DISTINCT from the refinement phase's coverage audit, which also binds topic 7 but asks a SEMANTIC question (does the built app match the intent — specs diffed against introspected reality). This playbook never diffs intent against reality; if you are judging coverage you are in the refinement lane. Scope honesty: the check set is the whole-application TYPECHECK across every package — the question 'does it compile as one program', which no per-task check can answer because the dispatch lane typechecks only the package a task mutated — PLUS the schema-plan drift gate (`check:schema-plan-in-sync`), which asks whether the modelled resources have migrations behind them. The second is not a variant of the first: on a PostgreSQL-backed application a table exists only because a migration built it, so a resource whose migration was never generated compiles green in every package and then refuses to boot on `postgresql_table_schema_mismatch` — invisible to a typecheck, because no type in the program knows whether a table exists. It is safe on MongoDB applications and on unbuilt trees because it resolves three outcomes (not adopted / could-not-ask / decided) rather than reading an exit code. Since #2228 it also asks the two questions a typecheck cannot: does each optional site BUILD (the website's `astro build`, the documentation portal's `docusaurus build`; an absent package answers 'nothing to build'), and does the configuration pass `wildo config validate` (errors fail, warnings do not, a missing CLI is 'we could not ask'); and it asks the RUNNING backend's readiness and renders the frontend in a browser, each reported unrun rather than passed when the stack is not up. Since #2404 it also builds the resources registry offline, as the backend's startup does (`check:resources-registry-init`), so a resource configuration the engine refuses at start is named before the running backend is asked. The whole test suite and OpenAPI/docs regeneration are NOT in this set.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"build-plan\" } }\n ],\n \"inputs\": [\n { \"family\": \"build-plan\" }\n ],\n \"outputs\": [],\n \"method\": {\n \"skillRefs\": [\n \"application-database-migrations\"\n ]\n },\n \"executor\": \"deterministic_cli\",\n \"approval\": \"approve_result\",\n /*\n * Token and model-call ceilings are OMITTED, not zeroed.\n *\n * Every field here is optional, and this tier makes no model calls at all — it runs typechecks in\n * a subprocess. Declaring `maxModelCalls: 0` is rejected by the schema (positive only), and\n * declaring `1` to satisfy it would state a ceiling nobody chose for a resource that is never\n * consumed. What IS bounded is wall-clock and how many times the step may run.\n */\n \"budget\": {\n \"maxRuns\": 40,\n \"maxDurationMs\": 3600000\n },\n \"onFailure\": \"keep_and_flag\",\n} as const;\n"]}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.build/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,8BAA8B,EAC9B,0BAA0B,EAC1B,0BAA0B,EAC3B,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,wBAAwB,EACxB,kBAAkB,EAEnB,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2FG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0H9B,CAAC"}
|
|
@@ -17,7 +17,7 @@ import { MetaWorkflow_AuthorityAssuranceClass, MetaWorkflow_AuthorityDecisionMod
|
|
|
17
17
|
*/
|
|
18
18
|
export declare const playbookDefinition: {
|
|
19
19
|
readonly ref: "bottom_up.build-decompose";
|
|
20
|
-
readonly version: "0.4.
|
|
20
|
+
readonly version: "0.4.6";
|
|
21
21
|
readonly phase: "bottom_up";
|
|
22
22
|
readonly intent: "Bottom-up build decomposition — the FIRST build-execution playbook, the pivot from planning the domain (the domain-plan) to decomposing the BUILD. Reads the approved domain-plan (the ModuleBusinessSemantics module drafts + per-module resource inventory), the relationship drafts inside it (the inter-resource relationship intents), and the definition set (roadmap for phasing, requirements + feature-drafts for task-brief context), and the PLACEMENT PLAN (where each settings destination, resource operation and view sits in the shell, decided upstream), and DECOMPOSES the build work into an ordered set of coding-agent tasks. Each task is bound onto (a) the 7-topic functional taxonomy (configure_application_foundation -> model_domain_graph -> define_interaction_semantics -> shape_user_experience -> extend_application -> connect_runtime_and_external_capabilities -> assemble_verify_and_iterate) and (b) the app-knowledge skill catalog (each task names the skill(s) that carry its technical HOW). The tasks follow the per-resource inner order (schema -> config -> ui-behavior -> spec, then operations / interaction semantics, then UX, then extensions, then integrations), with companion-owned generation steps (i18n-labels, email-templates, logo, and database-migrations for applications with an accepted PostgreSQL schema plan) interleaved at the points their inputs exist. This playbook PRODUCES the ordered task graph (a build-plan artifact); it does NOT dispatch tasks to coding agents (that is the dispatch-orchestration playbook downstream), does NOT capture change-sets / lock or schedule runs / verify, and does NOT solve multi-agent scale or interleaving. It authors no schemas and generates no code. The typed BuildPlanTaskGraph contract and deterministic validator already exist. Declare prerequisiteTaskRefs explicitly: the host derives readiness from those edges; functionalTopic provides context and skill routing, not an implicit execution order.";
|
|
23
23
|
readonly preconditions: readonly [{
|
|
@@ -31,6 +31,44 @@ export declare const playbookDefinition: {
|
|
|
31
31
|
readonly family: "placement-plan";
|
|
32
32
|
};
|
|
33
33
|
readonly "//": "SEQUENCING, not readiness — and the distinction is the whole point. `bottom_up.placement-plan` gates on the SAME `domain-plan` this does, so both become eligible at the same instant and decomposing first is legal. This method then says, at its placement section, 'No placement plan? Emit nothing here and say so' — which is honest per task and catastrophic per plan: the build proceeds with ZERO SHELL_PLACEMENT tasks and nothing refuses, so the finished application has no navigation and the cause is three playbooks upstream. `artifact_expected` is the kind written for exactly this (its own doc: use it whenever running early DEGRADES the output rather than invalidating it): the board reports `blocked only by sequencing`, a human may still run it deliberately, and `unmet` finally explains WHY the order matters instead of losing the signal.";
|
|
34
|
+
}, {
|
|
35
|
+
readonly kind: "artifact_expected";
|
|
36
|
+
readonly selector: {
|
|
37
|
+
readonly family: "experience-plan";
|
|
38
|
+
};
|
|
39
|
+
readonly "//": "The same shape for the experience plan (#2494): decomposing without it emits no view, no shell or design-system configuration, no milestone and no guidance, so the application ships with no home, the scaffold's colours and the default navigation. Inside the conception and build lanes every child is admitted past SEQUENCING, so this marks the board and a standalone run; what makes the LANE wait is the conception's stop condition, and what routes a plan decomposed without it back is the conception-buildable criterion.";
|
|
40
|
+
}, {
|
|
41
|
+
readonly kind: "artifact_expected";
|
|
42
|
+
readonly selector: {
|
|
43
|
+
readonly family: "integration-plan";
|
|
44
|
+
};
|
|
45
|
+
readonly "//": "Same reasoning: without it no worker, minion, provider binding or inbound-channel task is emitted. Its producer gates on the domain plan alone, so it is always producible and always expected.";
|
|
46
|
+
}, {
|
|
47
|
+
readonly kind: "artifact_expected";
|
|
48
|
+
readonly selector: {
|
|
49
|
+
readonly family: "website-plan";
|
|
50
|
+
};
|
|
51
|
+
readonly when: {
|
|
52
|
+
readonly selector: {
|
|
53
|
+
readonly family: "capability-composition";
|
|
54
|
+
};
|
|
55
|
+
readonly decision: "add-website";
|
|
56
|
+
readonly equals: "NEEDED";
|
|
57
|
+
};
|
|
58
|
+
readonly "//": "Expected only when the composition decided a website: an application without one has no website plan, and an unconditional expectation would wait for something its producer never runs.";
|
|
59
|
+
}, {
|
|
60
|
+
readonly kind: "artifact_expected";
|
|
61
|
+
readonly selector: {
|
|
62
|
+
readonly family: "documentation-plan";
|
|
63
|
+
};
|
|
64
|
+
readonly when: {
|
|
65
|
+
readonly selector: {
|
|
66
|
+
readonly family: "capability-composition";
|
|
67
|
+
};
|
|
68
|
+
readonly decision: "add-technical-doc";
|
|
69
|
+
readonly equals: "NEEDED";
|
|
70
|
+
};
|
|
71
|
+
readonly "//": "Expected only when the composition decided a documentation portal, for the same reason.";
|
|
34
72
|
}];
|
|
35
73
|
readonly inputs: readonly [{
|
|
36
74
|
readonly family: "domain-plan";
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.build-decompose/playbook.definition.ts"],"names":[],"mappings":"AACA,OAAO,EACL,oCAAoC,EACpC,kCAAkC,EAClC,wCAAwC,EACxC,+BAA+B,EAC/B,gCAAgC,EAChC,sCAAsC,EACtC,0CAA0C,EAC1C,6CAA6C,EAC7C,8BAA8B,EAC9B,oCAAoC,EACpC,6BAA6B,EAC9B,MAAM,sCAAsC,CAAC;AAE9C;;;;;;;;;;;;;;;GAeG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgFrB,CAAC;AAEX,eAAO,MAAM,yBAAyB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA4eW,CAAC"}
|
|
@@ -17,7 +17,7 @@ import { MetaWorkflow_AuthorityAssuranceClass, MetaWorkflow_AuthorityDecisionMod
|
|
|
17
17
|
*/
|
|
18
18
|
export const playbookDefinition = {
|
|
19
19
|
"ref": "bottom_up.build-decompose",
|
|
20
|
-
"version": "0.4.
|
|
20
|
+
"version": "0.4.6",
|
|
21
21
|
"phase": "bottom_up",
|
|
22
22
|
"intent": "Bottom-up build decomposition — the FIRST build-execution playbook, the pivot from planning the domain (the domain-plan) to decomposing the BUILD. Reads the approved domain-plan (the ModuleBusinessSemantics module drafts + per-module resource inventory), the relationship drafts inside it (the inter-resource relationship intents), and the definition set (roadmap for phasing, requirements + feature-drafts for task-brief context), and the PLACEMENT PLAN (where each settings destination, resource operation and view sits in the shell, decided upstream), and DECOMPOSES the build work into an ordered set of coding-agent tasks. Each task is bound onto (a) the 7-topic functional taxonomy (configure_application_foundation -> model_domain_graph -> define_interaction_semantics -> shape_user_experience -> extend_application -> connect_runtime_and_external_capabilities -> assemble_verify_and_iterate) and (b) the app-knowledge skill catalog (each task names the skill(s) that carry its technical HOW). The tasks follow the per-resource inner order (schema -> config -> ui-behavior -> spec, then operations / interaction semantics, then UX, then extensions, then integrations), with companion-owned generation steps (i18n-labels, email-templates, logo, and database-migrations for applications with an accepted PostgreSQL schema plan) interleaved at the points their inputs exist. This playbook PRODUCES the ordered task graph (a build-plan artifact); it does NOT dispatch tasks to coding agents (that is the dispatch-orchestration playbook downstream), does NOT capture change-sets / lock or schedule runs / verify, and does NOT solve multi-agent scale or interleaving. It authors no schemas and generates no code. The typed BuildPlanTaskGraph contract and deterministic validator already exist. Declare prerequisiteTaskRefs explicitly: the host derives readiness from those edges; functionalTopic provides context and skill routing, not an implicit execution order.",
|
|
23
23
|
"preconditions": [
|
|
@@ -26,6 +26,28 @@ export const playbookDefinition = {
|
|
|
26
26
|
"kind": "artifact_expected",
|
|
27
27
|
"selector": { "family": "placement-plan" },
|
|
28
28
|
"//": "SEQUENCING, not readiness — and the distinction is the whole point. `bottom_up.placement-plan` gates on the SAME `domain-plan` this does, so both become eligible at the same instant and decomposing first is legal. This method then says, at its placement section, 'No placement plan? Emit nothing here and say so' — which is honest per task and catastrophic per plan: the build proceeds with ZERO SHELL_PLACEMENT tasks and nothing refuses, so the finished application has no navigation and the cause is three playbooks upstream. `artifact_expected` is the kind written for exactly this (its own doc: use it whenever running early DEGRADES the output rather than invalidating it): the board reports `blocked only by sequencing`, a human may still run it deliberately, and `unmet` finally explains WHY the order matters instead of losing the signal."
|
|
29
|
+
},
|
|
30
|
+
{
|
|
31
|
+
"kind": "artifact_expected",
|
|
32
|
+
"selector": { "family": "experience-plan" },
|
|
33
|
+
"//": "The same shape for the experience plan (#2494): decomposing without it emits no view, no shell or design-system configuration, no milestone and no guidance, so the application ships with no home, the scaffold's colours and the default navigation. Inside the conception and build lanes every child is admitted past SEQUENCING, so this marks the board and a standalone run; what makes the LANE wait is the conception's stop condition, and what routes a plan decomposed without it back is the conception-buildable criterion."
|
|
34
|
+
},
|
|
35
|
+
{
|
|
36
|
+
"kind": "artifact_expected",
|
|
37
|
+
"selector": { "family": "integration-plan" },
|
|
38
|
+
"//": "Same reasoning: without it no worker, minion, provider binding or inbound-channel task is emitted. Its producer gates on the domain plan alone, so it is always producible and always expected."
|
|
39
|
+
},
|
|
40
|
+
{
|
|
41
|
+
"kind": "artifact_expected",
|
|
42
|
+
"selector": { "family": "website-plan" },
|
|
43
|
+
"when": { "selector": { "family": "capability-composition" }, "decision": "add-website", "equals": "NEEDED" },
|
|
44
|
+
"//": "Expected only when the composition decided a website: an application without one has no website plan, and an unconditional expectation would wait for something its producer never runs."
|
|
45
|
+
},
|
|
46
|
+
{
|
|
47
|
+
"kind": "artifact_expected",
|
|
48
|
+
"selector": { "family": "documentation-plan" },
|
|
49
|
+
"when": { "selector": { "family": "capability-composition" }, "decision": "add-technical-doc", "equals": "NEEDED" },
|
|
50
|
+
"//": "Expected only when the composition decided a documentation portal, for the same reason."
|
|
29
51
|
}
|
|
30
52
|
],
|
|
31
53
|
"inputs": [
|
|
@@ -81,7 +103,15 @@ export const evaluationTreatmentSource = {
|
|
|
81
103
|
// 4: experience coverage (#2235) — the experience plan's surfaces each have a task, and its absence is recorded.
|
|
82
104
|
// 5: module-and-resource coverage also asks for demonstration data (#2234), so a built application does not open empty.
|
|
83
105
|
// 6: experience coverage keys its absence case on the accepted-truth statement, not on a heading it did not see (#2235 review).
|
|
84
|
-
|
|
106
|
+
// 7: module-and-resource coverage orders a linked demo seed after the seed it references (#2392).
|
|
107
|
+
// 8: role coverage (#2490) — a requirement naming user groups is served by an APPLICATION_ROLES task.
|
|
108
|
+
// 9: interaction coverage (#2493) — a requirement verb beyond the default verbs is served by an interaction task.
|
|
109
|
+
// 10: interaction coverage also requires a task per lifecycle transition the domain plan declares (#2491).
|
|
110
|
+
// 11: interaction coverage also requires the UPDATE freeze of a lifecycle with final states (#2491 review F4).
|
|
111
|
+
// 12: that freeze lives in the objective of the transition into a final state, never in an `update` task (#2491 re-review).
|
|
112
|
+
// 13: locked states are frozen like final ones (#2491 re-review M1).
|
|
113
|
+
// 14: conception-buildable reports an absent experience plan as a conception gap (#2494).
|
|
114
|
+
definitionVersion: 14,
|
|
85
115
|
evaluationProtocol: {
|
|
86
116
|
schemaVersion: 1,
|
|
87
117
|
protocolRef: 'application-creation:evaluation-protocol/build-plan-coherent',
|
|
@@ -102,8 +132,9 @@ export const evaluationTreatmentSource = {
|
|
|
102
132
|
{
|
|
103
133
|
schemaVersion: 1,
|
|
104
134
|
criterionRef: 'application-creation:criterion/build-plan-module-and-resource-coverage',
|
|
105
|
-
|
|
106
|
-
|
|
135
|
+
// 3: a linked demo seed not ordered after the seed it references is a gap (#2392).
|
|
136
|
+
criterionVersion: 3,
|
|
137
|
+
instruction: "Determine whether every resource in every module's inventory (mainResources and supportingResources) of the domain plan has build tasks, and whether every task's moduleRef names a module the domain plan declares. A module whose resources have tasks but which carries no redundant scaffold task is NOT a finding: module slices are scaffolded by the foundation step. A module added after foundation with neither a foundation slice nor an ensure-module task IS a gap. The billing catalogue is covered the same way: every pricing plan the business model declares must be an APPLICATION_BILLING_PRODUCT of a BILLING_CATALOG task whose servesRefs name the plan; a declared plan with no billing product is a gap (the backend would have nothing to sell and the website would re-type its price). Seeding is covered the same way: a plan whose domain has main resources and no APPLICATION_DATA_SEED task of content DEMONSTRATION is a concern — the application would open empty, with nothing a creator can judge or show (#2234). A seed task whose rows point at rows another seed writes (a contact's customer, a quote's customer) and that is not ordered after that seed's task is a gap: the seed links them with referenceDataSeedRow and dependsOn, which resolve only against rows already written (#2392).",
|
|
107
138
|
assessesAspects: ['build-plan.task', 'domain-plan.module', 'domain-plan.resource'],
|
|
108
139
|
evidenceRequirements: [{
|
|
109
140
|
schemaVersion: 1,
|
|
@@ -310,21 +341,28 @@ export const evaluationTreatmentSource = {
|
|
|
310
341
|
* milestones. The method is right to emit no such task without a plan ("an improvised surface is the state
|
|
311
342
|
* this family replaced"), and the plan read as complete — no criterion here looked at the experience plan.
|
|
312
343
|
*
|
|
313
|
-
* Why an absent plan is PASS with a marked rationale, and not a weaker verdict:
|
|
314
|
-
*
|
|
315
|
-
* which ends in BLOCK)
|
|
316
|
-
*
|
|
317
|
-
* the
|
|
318
|
-
*
|
|
319
|
-
*
|
|
320
|
-
*
|
|
344
|
+
* Why an absent plan is PASS with a marked rationale, and not a weaker verdict: this treatment DECLARES every
|
|
345
|
+
* non-PASS verdict as routing back to the decomposer (CONCERN and GAP → REVISE, INDETERMINATE →
|
|
346
|
+
* REQUEST_EVIDENCE, which ends in BLOCK), and the decomposer cannot produce an upstream family by revising.
|
|
347
|
+
* Corrected 2026-10-05 (#2494 review G4): those consequences are declarations only — the treatment compiler
|
|
348
|
+
* copies the continuation policy and nothing acts on it, and the judge is advisory. What a verdict DOES today
|
|
349
|
+
* is what a composite's `reopenOnVerdict` table says, keyed on the criterion and the verdict; the build lane's
|
|
350
|
+
* table re-opens this decomposer for module and relationship coverage only. So the PASS rule keeps this
|
|
351
|
+
* criterion's verdict truthful against the declared treatment, not against a live routing.
|
|
352
|
+
*
|
|
353
|
+
* The absence is still not left at a marked PASS (#2494): it is a CONCEPTION fault, and `conception-buildable`
|
|
354
|
+
* reports it as a GAP. The root's `reopenOnVerdict` re-opens the conception and build lanes on exactly that GAP
|
|
355
|
+
* (exported by the build lane as `judge:bottom_up.build-decompose`), which is the routing that exists. The
|
|
356
|
+
* `artifact_expected` precondition on the family, rejected here before because every lane child is admitted
|
|
357
|
+
* past SEQUENCING, was added anyway for the board and standalone runs; what makes the lane wait is the
|
|
358
|
+
* conception's stop condition, which now names the experience plan.
|
|
321
359
|
*/
|
|
322
360
|
{
|
|
323
361
|
schemaVersion: 1,
|
|
324
362
|
criterionRef: 'application-creation:criterion/build-plan-experience-coverage',
|
|
325
|
-
criterionVersion:
|
|
326
|
-
instruction: "Determine whether every surface the experience plan decides has its build task: one task per VIEW (target MODULE_FRONTEND on the view's module, a product of the view's kind carrying the plan's viewRef verbatim), one APPLICATION_FRONTEND_CONFIG task per CONFIGURATION, one APPLICATION_MILESTONE task per planned MILESTONE, and one APPLICATION_GUIDANCE task per planned piece of GUIDANCE (an onboarding document's objective naming the hostViewRef that embeds it). A view, configuration, milestone or guidance entry with no task is a gap: the application would ship without it while the plan reads complete. Never conclude the plan is absent because this criterion's own slice does not show it: the accepted application truth either renders the experience plan or says it has none. When the accepted application truth STATES that `experience-plan` has no accepted content, the decomposer has rightly emitted none of these tasks and cannot repair the absence by revising: record PASS, and begin the rationale with the words 'NO EXPERIENCE PLAN:' followed by what the application will therefore lack (its app-level views, its shell and navigation configuration, its milestones and its onboarding), so the absence is on the record instead of silent.",
|
|
327
|
-
assessesAspects: ['build-plan.task', 'experience-plan.view', 'experience-plan.configuration', 'experience-plan.milestone', 'experience-plan.guidance'],
|
|
363
|
+
criterionVersion: 3,
|
|
364
|
+
instruction: "Determine whether every surface the experience plan decides has its build task: one task per VIEW (target MODULE_FRONTEND on the view's module, a product of the view's kind carrying the plan's viewRef verbatim), one APPLICATION_FRONTEND_CONFIG task per CONFIGURATION, one APPLICATION_MILESTONE task per planned MILESTONE, and one APPLICATION_GUIDANCE task per planned piece of GUIDANCE (an onboarding document's objective naming the hostViewRef that embeds it). When the plan decides a HOME, the GLOBAL_VIEWS configuration task's objective must set it: name `homeDefinitionFactory` and the home's view or resource operation. A view, configuration, milestone or guidance entry with no task, or a decided home no objective sets, is a gap: the application would ship without it (a missing home opens on the framework's welcome page) while the plan reads complete. Never conclude the plan is absent because this criterion's own slice does not show it: the accepted application truth either renders the experience plan or says it has none. When the accepted application truth STATES that `experience-plan` has no accepted content, the decomposer has rightly emitted none of these tasks and cannot repair the absence by revising: record PASS, and begin the rationale with the words 'NO EXPERIENCE PLAN:' followed by what the application will therefore lack (its app-level views, its shell and navigation configuration, its milestones and its onboarding), so the absence is on the record instead of silent.",
|
|
365
|
+
assessesAspects: ['build-plan.task', 'experience-plan.view', 'experience-plan.configuration', 'experience-plan.milestone', 'experience-plan.guidance', 'experience-plan.home'],
|
|
328
366
|
evidenceRequirements: [{
|
|
329
367
|
schemaVersion: 1,
|
|
330
368
|
requirementRef: 'application-creation:evidence-requirement/build-plan-experience-coverage',
|
|
@@ -343,10 +381,81 @@ export const evaluationTreatmentSource = {
|
|
|
343
381
|
verdictGuidance: {
|
|
344
382
|
[MetaWorkflow_EvaluationVerdict.PASS]: "Every view, configuration, milestone and guidance entry of the experience plan has its task — or no experience plan is in evidence, and the rationale begins 'NO EXPERIENCE PLAN:' and names what the application will lack.",
|
|
345
383
|
[MetaWorkflow_EvaluationVerdict.CONCERN]: "Every entry has a task, but a task's objective drops what the plan decided for it: a view's reusesComponentRefs, a milestone's moment, a guidance entry's gate, or an onboarding document's hostViewRef.",
|
|
346
|
-
[MetaWorkflow_EvaluationVerdict.GAP]: 'A view, configuration, milestone or guidance entry the experience plan declares has no task, or a view task carries a viewRef the plan does not declare.',
|
|
384
|
+
[MetaWorkflow_EvaluationVerdict.GAP]: 'A view, configuration, milestone or guidance entry the experience plan declares has no task, a decided home is set by no task\'s objective, or a view task carries a viewRef the plan does not declare.',
|
|
347
385
|
[MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The build plan is not in evidence, or the accepted application truth neither renders the experience plan nor states that it has none. (A STATED absence is not indeterminate: it is the PASS case above, marked.)',
|
|
348
386
|
},
|
|
349
387
|
},
|
|
388
|
+
/*
|
|
389
|
+
* #2490: app-creation-test-005's requirement "office and field users see different areas" was served by
|
|
390
|
+
* per-resource config tasks that all left every verb on ORG_MEMBER, plus an access-role RESOURCE nothing
|
|
391
|
+
* reads. No criterion asked whether the plan could enforce a role at all.
|
|
392
|
+
*/
|
|
393
|
+
{
|
|
394
|
+
schemaVersion: 1,
|
|
395
|
+
criterionRef: 'application-creation:criterion/build-plan-role-coverage',
|
|
396
|
+
criterionVersion: 1,
|
|
397
|
+
instruction: "Determine whether every requirement that names groups of users with different access (office and field staff, technicians, accountants, read-only reviewers, 'only administrators may …') is served by an APPLICATION_ROLES task producing one APPLICATION_ROLE per group that no core role already covers (ORG_OWNER, ORG_ADMIN, ORG_MANAGER, ORG_MEMBER, ORG_GUEST), ordered after the config tasks of the resources whose operations it narrows. A requirement satisfied by the core roles alone (only administrators may delete) needs no APPLICATION_ROLES task, but the config tasks of the resources it covers must say which operations are restricted. A task, product or resource that models roles, permissions or role assignments as DATA (an access-role or permission resource) is never a way to satisfy such a requirement.",
|
|
398
|
+
assessesAspects: ['build-plan.task', 'requirements.functional', 'requirements.non-functional'],
|
|
399
|
+
evidenceRequirements: [{
|
|
400
|
+
schemaVersion: 1,
|
|
401
|
+
requirementRef: 'application-creation:evidence-requirement/build-plan-role-coverage',
|
|
402
|
+
requirementVersion: 1,
|
|
403
|
+
kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,
|
|
404
|
+
subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',
|
|
405
|
+
minCount: 1,
|
|
406
|
+
maxCount: 8,
|
|
407
|
+
coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',
|
|
408
|
+
freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',
|
|
409
|
+
conditionRef: null,
|
|
410
|
+
independencePolicyRef: null,
|
|
411
|
+
diversityPolicyRef: null,
|
|
412
|
+
aggregationPolicyRef: null,
|
|
413
|
+
}],
|
|
414
|
+
verdictGuidance: {
|
|
415
|
+
[MetaWorkflow_EvaluationVerdict.PASS]: 'No requirement names user groups with different access, or every such group has an APPLICATION_ROLE product of an APPLICATION_ROLES task ordered after the config tasks it narrows, or is covered by a core role the relevant config tasks restrict to.',
|
|
416
|
+
[MetaWorkflow_EvaluationVerdict.CONCERN]: 'Each group has its role, but the APPLICATION_ROLES task is ordered before a config task of a resource it narrows, or its objective does not say which operations each role may call.',
|
|
417
|
+
[MetaWorkflow_EvaluationVerdict.GAP]: 'A requirement names a user group no core role covers and no APPLICATION_ROLE product declares, or the plan answers a role requirement with a task or resource that stores roles or permissions as data.',
|
|
418
|
+
[MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The build plan or the requirements are not in evidence.',
|
|
419
|
+
},
|
|
420
|
+
},
|
|
421
|
+
/*
|
|
422
|
+
* #2493: app-creation-test-004 (92 tasks) and -005 (86) planned no operation, document or email at all,
|
|
423
|
+
* and every lifecycle step shipped as a status users edit by hand. Each requirement was "served" by CRUD
|
|
424
|
+
* tasks citing it in servesRefs, and no criterion weighed whether those tasks could realise its verbs.
|
|
425
|
+
*/
|
|
426
|
+
{
|
|
427
|
+
schemaVersion: 1,
|
|
428
|
+
criterionRef: 'application-creation:criterion/build-plan-interaction-coverage',
|
|
429
|
+
// 2: every lifecycle transition the domain plan declares has its operation task (#2491).
|
|
430
|
+
// 3: every lifecycle with final states has its UPDATE freeze, as the method places it (#2491 review F4).
|
|
431
|
+
// 4: the freeze lives in the objective of the transition into a final state, never in an `update` task (#2491 re-review).
|
|
432
|
+
// 5: locked states (no edits, may still move on) are frozen the same way as final ones (#2491 re-review M1),
|
|
433
|
+
// in both its lifecycle clause and its requirement-verb clause.
|
|
434
|
+
criterionVersion: 5,
|
|
435
|
+
instruction: "Determine whether every transition the domain plan's lifecycles declare has a RESOURCE_OPERATION task on its resource (plus a MODULE_BACKEND task when the transition creates another resource), whether, for every lifecycle with locked or final states, the objective of a transition task moving into each of them restricts that resource's UPDATE to the states that are neither locked nor final (a separate RESOURCE_OPERATION named update is not a realisation: the scaffold already writes update, so it reads as built before it runs), and whether every functional acceptance criterion whose verb goes beyond the default resource verbs (create, read, update, list, delete) is served by a task able to realise it: a state change ('an accepted quote', 'issue the invoice', 'mark it paid') by a RESOURCE_OPERATION on the resource whose state changes; one record creating or filling another ('an accepted quote creates a job') by a RESOURCE_OPERATION on the source resource with a MODULE_BACKEND implementation; a record that must stop changing by the objective of the transition task into the locked or final state; a produced document by a PDF_TEMPLATE task; a sent message by the email generation step plus the triggering operation's task. A task citing the requirement in servesRefs does not realise a verb its kind cannot carry: a config or schema task leaves a status freely editable. A value derived from other records (a next action, an overdue flag) planned as a stored field is not a realisation either.",
|
|
436
|
+
assessesAspects: ['build-plan.task', 'requirements.functional', 'domain-plan.module', 'domain-plan.resource', 'domain-plan.lifecycle'],
|
|
437
|
+
evidenceRequirements: [{
|
|
438
|
+
schemaVersion: 1,
|
|
439
|
+
requirementRef: 'application-creation:evidence-requirement/build-plan-interaction-coverage',
|
|
440
|
+
requirementVersion: 1,
|
|
441
|
+
kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,
|
|
442
|
+
subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',
|
|
443
|
+
minCount: 1,
|
|
444
|
+
maxCount: 8,
|
|
445
|
+
coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',
|
|
446
|
+
freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',
|
|
447
|
+
conditionRef: null,
|
|
448
|
+
independencePolicyRef: null,
|
|
449
|
+
diversityPolicyRef: null,
|
|
450
|
+
aggregationPolicyRef: null,
|
|
451
|
+
}],
|
|
452
|
+
verdictGuidance: {
|
|
453
|
+
[MetaWorkflow_EvaluationVerdict.PASS]: 'No functional criterion names a verb beyond the default resource verbs, or each such verb is served by a task of a kind that can realise it, naming the requirement in servesRefs.',
|
|
454
|
+
[MetaWorkflow_EvaluationVerdict.CONCERN]: 'Every verb has a task, but a derived value (a next action, an overdue flag) is planned as a stored field, or an operation task does not say which states it moves between.',
|
|
455
|
+
[MetaWorkflow_EvaluationVerdict.GAP]: 'A declared lifecycle transition has no operation task, or no transition task into a locked or final state carries the UPDATE freeze (or it is planned as a separate update task); or a state change, a record creating another, a record that must stop changing, a produced document or a sent message named by a functional criterion has no task of a kind that can realise it — including a workflow-describing plan with no interaction task at all.',
|
|
456
|
+
[MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The build plan or the requirements are not in evidence.',
|
|
457
|
+
},
|
|
458
|
+
},
|
|
350
459
|
/*
|
|
351
460
|
* The one criterion that faults the CONCEPTION rather than the plan (#1638). Every other criterion
|
|
352
461
|
* here is the decomposer's own, and its GAP re-opens the decomposer. This one says the plan could not
|
|
@@ -358,9 +467,12 @@ export const evaluationTreatmentSource = {
|
|
|
358
467
|
{
|
|
359
468
|
schemaVersion: 1,
|
|
360
469
|
criterionRef: 'application-creation:criterion/conception-buildable',
|
|
361
|
-
|
|
362
|
-
|
|
363
|
-
|
|
470
|
+
// 2: an absent experience plan is a conception gap, routed back to the conception lane (#2494).
|
|
471
|
+
criterionVersion: 2,
|
|
472
|
+
instruction: "Determine whether the CONCEPTION this plan rests on can be built as declared. This criterion faults the domain plan, the capability composition or the surface plans — never the build plan. It is a GAP when (a) the domain plan declares a module, resource or relationship that no build task target can express, however it is decomposed, or (b) the computed coherence report shows a dangling reference or an 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, or (c) the accepted application truth STATES that `experience-plan` has no accepted content: every application with a frontend has an experience, and without its plan the build has no home, no design system from the brand, no navigation decision and no application views, which no revision of this plan can supply; the same when it STATES that `integration-plan` has none, since then nothing decided whether the application runs workers, minions, provider bindings or inbound channels (an integration plan that decides none is content, not an absence). A domain-plan element declared in an expressible shape that the build plan simply omits is NOT this criterion: that is module-and-resource coverage, the decomposer's own fault. Name the conception element in the rationale.",
|
|
473
|
+
// An aspect of each family clause (c) reads, so the slice states an ABSENT experience or integration plan and points at
|
|
474
|
+
// the accepted truth (#2494 review G1, G6); a criterion naming no aspect of a family is told nothing about it.
|
|
475
|
+
assessesAspects: ['build-plan.task', 'domain-plan.module', 'domain-plan.resource', 'domain-plan.relationship', 'experience-plan.view', 'integration-plan.worker'],
|
|
364
476
|
evidenceRequirements: [{
|
|
365
477
|
schemaVersion: 1,
|
|
366
478
|
requirementRef: 'application-creation:evidence-requirement/conception-buildable',
|
|
@@ -379,7 +491,7 @@ export const evaluationTreatmentSource = {
|
|
|
379
491
|
verdictGuidance: {
|
|
380
492
|
[MetaWorkflow_EvaluationVerdict.PASS]: 'Everything the conception declares has a build target, and the coherence report shows nothing in it the build would have to invent.',
|
|
381
493
|
[MetaWorkflow_EvaluationVerdict.CONCERN]: 'A conception element is expressible only awkwardly, or the coherence report shows an unrealised item that reads as a deliberate deferral.',
|
|
382
|
-
[MetaWorkflow_EvaluationVerdict.GAP]: 'The domain plan declares something no build target can express,
|
|
494
|
+
[MetaWorkflow_EvaluationVerdict.GAP]: 'The domain plan declares something no build target can express, the coherence report shows a dangling reference or unrealised decision in the conception that the build cannot proceed past without inventing it, or the accepted truth states the experience plan or the integration plan is absent.',
|
|
383
495
|
[MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The domain plan or the coherence report is not in evidence, so the conception cannot be read against the plan.',
|
|
384
496
|
},
|
|
385
497
|
},
|