@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
|
-
{"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-requirements-snapshot","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/requirements-horizon-readiness","application-creation:evidence-requirement/requirements-definition-coherence"],"requirementRef":"application-creation:authority-requirement/requirements-definition-result","requirementVersion":1,"riskClassRef":"application-creation:risk/requirements-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/requirements-definition","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/requirements-definition-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/requirements-definition","policyVersion":1},"decisionPointRef":"application-creation:decision-point/requirements-definition","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/requirements-definition","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/requirements-definition","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirements-definition-coherence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/requirements-horizon-readiness","requirementVersion":2}],"hardFloorRefs":["application-creation:hard-floor/requirements-horizon-readiness"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-definition","triggerRefs":["application-creation:trigger/requirements-snapshot-produced"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-requirements-definition-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/requirements-horizon-readiness"],"hardFloorRef":"application-creation:hard-floor/requirements-horizon-readiness"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/requirements-definition","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/requirements-definition","definitionVersion":2,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-requirements-definition-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/requirements-definition-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirements-definition-coherence","requirementVersion":1}],"instruction":"Assess whether each requirement is traceable to accepted vision or market evidence, states a distinct current-horizon obligation, and carries observable acceptance language where applicable. Do not invent missing requirements or silently turn implementation ideas into product obligations.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The set is usable, but one or more obligations are weakly traced or ambiguously testable.","GAP":"A material current-horizon obligation is missing, contradictory, or not testable enough to guide downstream scope.","INDETERMINATE":"Accepted vision/market evidence is insufficient to assess the requirements set.","PASS":"The requirements are distinct, traceable and sufficiently observable for the current horizon."}},{"criterionRef":"application-creation:criterion/requirements-horizon-readiness","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirements-horizon-readiness","requirementVersion":2}],"instruction":"Judge whether the requirements under judgment — the working-subject source when one is named, otherwise the accepted current-horizon requirements — give the current horizon a non-vacuous, implementable basis: at least one validated functional requirement with a testable acceptance criterion, or an exact settled exceptional disposition. The sealed hard-floor assessment for this criterion is the deterministic minimum-content finding on that same subject; treat it as the floor, not as the whole judgment. Never infer readiness from prose, model confidence or snapshot parse success, and never judge an empty collection ready.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The horizon has a basis, but it is thin or its acceptance language is weak enough that downstream scope would be guesswork.","GAP":"The requirements under judgment have no functional requirement and no exact settled exceptional disposition, or the sealed hard floor failed.","INDETERMINATE":"The current-horizon requirements evidence is absent, malformed, or does not bind the subject under judgment.","PASS":"The requirements under judgment carry at least one validated, testable current-horizon functional requirement (or an exact settled exceptional disposition) and the sealed hard floor is satisfied."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/requirements-definition","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.requirements-definition"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/requirements-definition","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-requirements","criterionRef":"application-creation:criterion/requirements-definition-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":1,"requirementRef":"application-creation:evidence-requirement/requirements-definition-coherence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/requirements-vision-market"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/current-horizon-requirements","criterionRef":"application-creation:criterion/requirements-horizon-readiness","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/requirements-horizon-readiness","requirementVersion":2,"schemaVersion":1,"subjectRef":"application-creation:definition-set/requirements-current-horizon"}],"schemaVersion":1}
|
|
1
|
+
{"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-requirements-snapshot","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/requirements-horizon-readiness","application-creation:evidence-requirement/requirements-definition-coherence"],"requirementRef":"application-creation:authority-requirement/requirements-definition-result","requirementVersion":1,"riskClassRef":"application-creation:risk/requirements-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/requirements-definition","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/requirements-definition-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/requirements-definition","policyVersion":1},"decisionPointRef":"application-creation:decision-point/requirements-definition","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/requirements-definition","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/requirements-definition","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirements-definition-coherence","requirementVersion":2},{"requirementRef":"application-creation:evidence-requirement/requirements-horizon-readiness","requirementVersion":2}],"hardFloorRefs":["application-creation:hard-floor/requirements-horizon-readiness"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-definition","triggerRefs":["application-creation:trigger/requirements-snapshot-produced"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-requirements-definition-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/requirements-horizon-readiness"],"hardFloorRef":"application-creation:hard-floor/requirements-horizon-readiness"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/requirements-definition","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/requirements-definition","definitionVersion":2,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-requirements-definition-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/requirements-definition-coherence","criterionVersion":3,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirements-definition-coherence","requirementVersion":2}],"instruction":"Assess whether each requirement is traceable to accepted vision or market evidence, or to a fact the creator stated in another interview; states a distinct current-horizon obligation; and carries observable acceptance language where applicable. Then check the creator's stated facts, when they are in your evidence: every data class, named regime, jurisdiction (with its languages), workflow stage, user group and scope boundary bearing on what the product must do is carried by a requirement or listed in excludedStatedFacts with a reason. A stated fact neither carried nor excluded is a GAP. Then check the market's pains: every pain a targeted ICP (CORE or EXPANSION) or one of its personas weighs at severity 7 or more is named in some requirement's painRefs or listed in excludedMarketPains with a reason; one that is neither is a GAP. The coherence report's high-severity-pains-unanswered finding lists them, computed over the accepted requirements. Then check the targeted personas' responsibilities: one the product exists to help with that no requirement carries is a GAP; one outside any product's scope needs nothing. A functional acceptance criterion that is a compliance guard (does not claim, is not presented as supported until) instead of a capability is a CONCERN: it belongs in a compliance non-functional requirement. Do not invent missing requirements or silently turn implementation ideas into product obligations.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The set is usable, but one or more obligations are weakly traced or ambiguously testable.","GAP":"A material current-horizon obligation is missing, contradictory, or not testable enough to guide downstream scope, or a fact the creator stated (or a high-severity market pain) is neither carried by a requirement nor explicitly excluded.","INDETERMINATE":"Accepted vision/market evidence is insufficient to assess the requirements set.","PASS":"The requirements are distinct, traceable and sufficiently observable for the current horizon."}},{"criterionRef":"application-creation:criterion/requirements-horizon-readiness","criterionVersion":3,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirements-horizon-readiness","requirementVersion":2}],"instruction":"Judge whether the requirements under judgment — the working-subject source when one is named, otherwise the accepted current-horizon requirements — give the current horizon a non-vacuous, implementable basis: at least one validated functional requirement with a testable acceptance criterion, or an exact settled exceptional disposition. The sealed hard-floor assessment for this criterion is the deterministic minimum-content finding on that same subject; treat it as the floor, not as the whole judgment. A requirement describing a workflow (quotes, jobs, invoices, orders, tickets) whose criteria only list what can be created, read and edited, naming no state, transition, document, total or number the workflow has, is a CONCERN: the horizon then reads as a database rather than a product. Never infer readiness from prose, model confidence or snapshot parse success, and never judge an empty collection ready.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The horizon has a basis, but it is thin or its acceptance language is weak enough that downstream scope would be guesswork.","GAP":"The requirements under judgment have no functional requirement and no exact settled exceptional disposition, or the sealed hard floor failed.","INDETERMINATE":"The current-horizon requirements evidence is absent, malformed, or does not bind the subject under judgment.","PASS":"The requirements under judgment carry at least one validated, testable current-horizon functional requirement (or an exact settled exceptional disposition) and the sealed hard floor is satisfied."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/requirements-definition","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.requirements-definition"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/requirements-definition","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-requirements","criterionRef":"application-creation:criterion/requirements-definition-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":1,"requirementRef":"application-creation:evidence-requirement/requirements-definition-coherence","requirementVersion":2,"schemaVersion":1,"subjectRef":"application-creation:definition-set/requirements-vision-market"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/current-horizon-requirements","criterionRef":"application-creation:criterion/requirements-horizon-readiness","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/requirements-horizon-readiness","requirementVersion":2,"schemaVersion":1,"subjectRef":"application-creation:definition-set/requirements-current-horizon"}],"schemaVersion":1}
|
|
@@ -1,9 +1,9 @@
|
|
|
1
1
|
# Requirements definition method
|
|
2
2
|
|
|
3
3
|
Produce the current-horizon requirements family from the accepted
|
|
4
|
-
`vision-brief` and `market-snapshot` heads
|
|
5
|
-
the
|
|
6
|
-
cannot silently replace or amend them.
|
|
4
|
+
`vision-brief` and `market-snapshot` heads, and from what the creator stated in
|
|
5
|
+
the other interviews. Treat those as the only application truth: conversational
|
|
6
|
+
context may clarify them, but it cannot silently replace or amend them.
|
|
7
7
|
|
|
8
8
|
The provider response must parse as
|
|
9
9
|
`RequirementsSnapshotGenerationSchema`. It supplies semantic slugs, statements,
|
|
@@ -25,13 +25,86 @@ override that protected consequence.
|
|
|
25
25
|
For every functional requirement:
|
|
26
26
|
|
|
27
27
|
- state one distinct product capability, not an implementation task;
|
|
28
|
-
- connect it to accepted vision or market evidence
|
|
29
|
-
market does not apply to this application,
|
|
30
|
-
|
|
31
|
-
cross-references);
|
|
28
|
+
- connect it to accepted vision or market evidence, or to a fact the creator
|
|
29
|
+
stated (when the brief says the market does not apply to this application,
|
|
30
|
+
the vision and the stated facts are the evidence: cite the vision's problem,
|
|
31
|
+
users and success criteria, and declare no market cross-references);
|
|
32
32
|
- keep current-horizon scope explicit; and
|
|
33
33
|
- provide observable acceptance language where meaningful.
|
|
34
34
|
|
|
35
|
+
## Acceptance criteria name states and transitions
|
|
36
|
+
|
|
37
|
+
A requirement for a workflow is a set of state changes, and its criteria say them: "a draft quote can be sent; a sent
|
|
38
|
+
quote can be accepted or declined; an accepted quote becomes a job carrying its customer, site and lines". Criteria that
|
|
39
|
+
only list what can be created, read and edited describe a database, not a product. An earlier run carried a whole
|
|
40
|
+
quote, job and invoice product in five such criteria, with no lifecycle, no documents, no totals and no numbering, and
|
|
41
|
+
every judge passed it. When the product numbers, totals, prints or sends documents, a criterion says so.
|
|
42
|
+
|
|
43
|
+
## Every high-severity market pain is relieved or left out
|
|
44
|
+
|
|
45
|
+
The `market-snapshot` input weighs each pain on the ICPs and personas that feel it (`pains[].severity`, 1 to 10). Every
|
|
46
|
+
pain a targeted ICP (`CORE` or `EXPANSION`) or one of its personas feels at 7 or more is owed an answer. The computed
|
|
47
|
+
coherence report (the declared `coherence_report` context section of your brief) lists those not answered yet in its
|
|
48
|
+
`high-severity-pains-unanswered` finding, each with its severity and who feels it; answer that list. Each pain is either:
|
|
49
|
+
|
|
50
|
+
- **relieved** by a requirement, which names it in `painRefs` (a functional requirement for what the product does about
|
|
51
|
+
it, a non-functional one for a quality); or
|
|
52
|
+
- **left out** in `excludedMarketPains`, with the pain's ref and why no requirement relieves it (a later horizon, served
|
|
53
|
+
by another tool, outside the product).
|
|
54
|
+
|
|
55
|
+
An earlier run's market weighed missed follow-ups and fragmented customer communications heavily, and no requirement
|
|
56
|
+
mentioned follow-ups, reminders, documents or mobile use. Name the pain on every requirement that relieves it, so the
|
|
57
|
+
coverage can be checked rather than read into the statements.
|
|
58
|
+
|
|
59
|
+
## The targeted personas' work is carried
|
|
60
|
+
|
|
61
|
+
Each persona of a targeted ICP lists its day-to-day `profile.responsibilities`. A responsibility the product exists to
|
|
62
|
+
help with (sending quotes, chasing follow-ups, scheduling jobs) is carried by a requirement, which names the persona's ICP
|
|
63
|
+
in `icpRefs`. A responsibility outside what any product does (reporting to the board, hiring) needs nothing. Read every
|
|
64
|
+
one: a responsibility at the centre of the product's job that no requirement carries is the same gap as an unanswered
|
|
65
|
+
pain, and the judge reports it.
|
|
66
|
+
|
|
67
|
+
## Compliance guards are non-functional requirements
|
|
68
|
+
|
|
69
|
+
A sentence such as "the product does not claim e-invoicing compliance" or "is not presented as supported until …" is a
|
|
70
|
+
constraint on the product, not a capability. Put it in a `compliance` non-functional requirement, never in a functional
|
|
71
|
+
requirement's acceptance criteria. An earlier run filled 14 of its 39 functional criteria with such guards, and the
|
|
72
|
+
functional requirements then said almost nothing about what the product does.
|
|
73
|
+
|
|
74
|
+
## Every stated fact becomes a requirement or an exclusion
|
|
75
|
+
|
|
76
|
+
The creator's answers to the other interviews arrive in
|
|
77
|
+
the declared `creator_stated_facts` context section of your brief. They are accepted truth beside the
|
|
78
|
+
vision and the market: statements about the product, not suggestions. On an
|
|
79
|
+
earlier run the creator named VAT identification numbers on quotes, job-site
|
|
80
|
+
addresses, Italy's SDI and Spain's VeriFactu e-invoicing, and four countries.
|
|
81
|
+
The requirements mentioned none of them, and the application shipped quotes
|
|
82
|
+
with no VAT, jobs with no site address, and one language for four countries.
|
|
83
|
+
|
|
84
|
+
Go through every answer that bears on what the product must do or be, and for each fact:
|
|
85
|
+
|
|
86
|
+
- **Carry it in a requirement.**
|
|
87
|
+
- A data class the product holds (a VAT number, a site address) belongs in the
|
|
88
|
+
statement or acceptance criteria of the functional requirement that captures
|
|
89
|
+
or shows it.
|
|
90
|
+
- A named regime (an e-invoicing mandate, a privacy law) becomes a
|
|
91
|
+
`compliance` non-functional requirement naming it.
|
|
92
|
+
- A jurisdiction implies its languages and formats: name them in a
|
|
93
|
+
`usability` or `compliance` non-functional requirement, and do not assume
|
|
94
|
+
English is enough.
|
|
95
|
+
- Each workflow stage and each user group (with the device they use) is served
|
|
96
|
+
by at least one functional requirement.
|
|
97
|
+
- **Or exclude it explicitly** in `excludedStatedFacts`, quoting the fact and
|
|
98
|
+
saying why no requirement carries it: out of this horizon, left to another
|
|
99
|
+
tool by the scope boundary, or contradicted by a later answer. Something the
|
|
100
|
+
creator put out of scope is excluded here, never quietly built.
|
|
101
|
+
|
|
102
|
+
Never drop a stated fact silently, and never write a requirement that
|
|
103
|
+
contradicts one. An answer marked ASSUMED was proposed for the creator, not
|
|
104
|
+
stated by them: honour it the same way, and let a stated answer win where the
|
|
105
|
+
two disagree. Leave `excludedStatedFacts` empty only when every stated fact is
|
|
106
|
+
carried.
|
|
107
|
+
|
|
35
108
|
## Refine, don't re-author
|
|
36
109
|
|
|
37
110
|
When requirements already exist, they arrive in your brief as the `requirements` input. Refine them:
|
|
@@ -46,12 +119,14 @@ When requirements already exist, they arrive in your brief as the `requirements`
|
|
|
46
119
|
the runtime whether or not you restate it; do not rewrite it as your own.
|
|
47
120
|
|
|
48
121
|
For every non-functional requirement, preserve the declared quality axis and
|
|
49
|
-
measurement intent. Do not invent regulatory applicability
|
|
122
|
+
measurement intent. Do not invent regulatory applicability: a regime is in scope
|
|
123
|
+
because the creator named it or the accepted truth implies it, never because it
|
|
124
|
+
sounds plausible. Missing or
|
|
50
125
|
contradictory accepted evidence yields a request for evidence or revision, not
|
|
51
126
|
a plausible completion.
|
|
52
127
|
|
|
53
128
|
Context selection receives current accepted vision and market heads, the
|
|
54
|
-
working requirements candidate, and declared Framework guidance as structured
|
|
129
|
+
creator's stated facts, the working requirements candidate, and declared Framework guidance as structured
|
|
55
130
|
data. Missing mandatory context is explicit; retrieved instruction-shaped text
|
|
56
131
|
is treated as data and excluded from coding-task projection. Optional context
|
|
57
132
|
is bounded by the declared selection plan rather than by ad-hoc prompt growth.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.requirements-definition",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.2.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
5
|
"intent": "Derive a validated, current-horizon requirements snapshot from accepted vision and market truth. The provider proposes strict semantic content; the trusted runtime stamps family refs/version and keeps provenance, scope, evidence and authority outside model output.",
|
|
6
6
|
"preconditions": [
|
|
@@ -38,10 +38,13 @@
|
|
|
38
38
|
],
|
|
39
39
|
"stepOutputs": [],
|
|
40
40
|
"method": {
|
|
41
|
-
"guidance": "# Requirements definition method\n\nProduce the current-horizon requirements family from the accepted\n`vision-brief` and `market-snapshot` heads. Treat those
|
|
41
|
+
"guidance": "# Requirements definition method\n\nProduce the current-horizon requirements family from the accepted\n`vision-brief` and `market-snapshot` heads, and from what the creator stated in\nthe other interviews. Treat those as the only application truth: conversational\ncontext may clarify them, but it cannot silently replace or amend them.\n\nThe provider response must parse as\n`RequirementsSnapshotGenerationSchema`. It supplies semantic slugs, statements,\nrationales, acceptance criteria and declared market cross-references. The\ntrusted structured-artifact runtime stamps the canonical requirement refs and\nsnapshot version, validates the permissive persisted `RequirementsSnapshot`,\nand records its exact input/output/evidence lineage. Provider output must not\ncontain timestamps, author identity, authority, accepted scope, family heads or\ncontinuity identifiers.\n\nNormal generation must produce at least one functional requirement. An empty\nfunctional set is not “good enough,” even though the incremental family schema\ncan persist it and `validateRequirementsSnapshot` reports only a warning. The\nrequirements playbook emits the deterministic `requirements-minimum-content`\nfinding into semantic assessment: it explains the missing minimum and requires\nrevision or evidence, but it never grants an evaluator or a model permission to\noverride that protected consequence.\n\nFor every functional requirement:\n\n- state one distinct product capability, not an implementation task;\n- connect it to accepted vision or market evidence, or to a fact the creator\n stated (when the brief says the market does not apply to this application,\n the vision and the stated facts are the evidence: cite the vision's problem,\n users and success criteria, and declare no market cross-references);\n- keep current-horizon scope explicit; and\n- provide observable acceptance language where meaningful.\n\n## Acceptance criteria name states and transitions\n\nA requirement for a workflow is a set of state changes, and its criteria say them: \"a draft quote can be sent; a sent\nquote can be accepted or declined; an accepted quote becomes a job carrying its customer, site and lines\". Criteria that\nonly list what can be created, read and edited describe a database, not a product. An earlier run carried a whole\nquote, job and invoice product in five such criteria, with no lifecycle, no documents, no totals and no numbering, and\nevery judge passed it. When the product numbers, totals, prints or sends documents, a criterion says so.\n\n## Every high-severity market pain is relieved or left out\n\nThe `market-snapshot` input weighs each pain on the ICPs and personas that feel it (`pains[].severity`, 1 to 10). Every\npain a targeted ICP (`CORE` or `EXPANSION`) or one of its personas feels at 7 or more is owed an answer. The computed\ncoherence report (the declared `coherence_report` context section of your brief) lists those not answered yet in its\n`high-severity-pains-unanswered` finding, each with its severity and who feels it; answer that list. Each pain is either:\n\n- **relieved** by a requirement, which names it in `painRefs` (a functional requirement for what the product does about\n it, a non-functional one for a quality); or\n- **left out** in `excludedMarketPains`, with the pain's ref and why no requirement relieves it (a later horizon, served\n by another tool, outside the product).\n\nAn earlier run's market weighed missed follow-ups and fragmented customer communications heavily, and no requirement\nmentioned follow-ups, reminders, documents or mobile use. Name the pain on every requirement that relieves it, so the\ncoverage can be checked rather than read into the statements.\n\n## The targeted personas' work is carried\n\nEach persona of a targeted ICP lists its day-to-day `profile.responsibilities`. A responsibility the product exists to\nhelp with (sending quotes, chasing follow-ups, scheduling jobs) is carried by a requirement, which names the persona's ICP\nin `icpRefs`. A responsibility outside what any product does (reporting to the board, hiring) needs nothing. Read every\none: a responsibility at the centre of the product's job that no requirement carries is the same gap as an unanswered\npain, and the judge reports it.\n\n## Compliance guards are non-functional requirements\n\nA sentence such as \"the product does not claim e-invoicing compliance\" or \"is not presented as supported until …\" is a\nconstraint on the product, not a capability. Put it in a `compliance` non-functional requirement, never in a functional\nrequirement's acceptance criteria. An earlier run filled 14 of its 39 functional criteria with such guards, and the\nfunctional requirements then said almost nothing about what the product does.\n\n## Every stated fact becomes a requirement or an exclusion\n\nThe creator's answers to the other interviews arrive in\nthe declared `creator_stated_facts` context section of your brief. They are accepted truth beside the\nvision and the market: statements about the product, not suggestions. On an\nearlier run the creator named VAT identification numbers on quotes, job-site\naddresses, Italy's SDI and Spain's VeriFactu e-invoicing, and four countries.\nThe requirements mentioned none of them, and the application shipped quotes\nwith no VAT, jobs with no site address, and one language for four countries.\n\nGo through every answer that bears on what the product must do or be, and for each fact:\n\n- **Carry it in a requirement.**\n - A data class the product holds (a VAT number, a site address) belongs in the\n statement or acceptance criteria of the functional requirement that captures\n or shows it.\n - A named regime (an e-invoicing mandate, a privacy law) becomes a\n `compliance` non-functional requirement naming it.\n - A jurisdiction implies its languages and formats: name them in a\n `usability` or `compliance` non-functional requirement, and do not assume\n English is enough.\n - Each workflow stage and each user group (with the device they use) is served\n by at least one functional requirement.\n- **Or exclude it explicitly** in `excludedStatedFacts`, quoting the fact and\n saying why no requirement carries it: out of this horizon, left to another\n tool by the scope boundary, or contradicted by a later answer. Something the\n creator put out of scope is excluded here, never quietly built.\n\nNever drop a stated fact silently, and never write a requirement that\ncontradicts one. An answer marked ASSUMED was proposed for the creator, not\nstated by them: honour it the same way, and let a stated answer win where the\ntwo disagree. Leave `excludedStatedFacts` empty only when every stated fact is\ncarried.\n\n## Refine, don't re-author\n\nWhen requirements already exist, they arrive in your brief as the `requirements` input. Refine them:\n\n- **Keep what still holds.** A requirement nothing asks you to change keeps its semantic slug, its statement\n and its cross-references. Do not reword it for style.\n- **Reuse slugs.** A requirement that changes keeps its slug; never mint a second slug for the same\n capability, since every plan and task derived from the requirements cites it.\n- **Change what you were asked to.** When the brief says what this run is for (a refinement of the\n requirements, or a vision or market that moved), change that, and leave the rest as it is.\n- **Leave a secondary line's requirements alone.** An element another line contributed is carried forward by\n the runtime whether or not you restate it; do not rewrite it as your own.\n\nFor every non-functional requirement, preserve the declared quality axis and\nmeasurement intent. Do not invent regulatory applicability: a regime is in scope\nbecause the creator named it or the accepted truth implies it, never because it\nsounds plausible. Missing or\ncontradictory accepted evidence yields a request for evidence or revision, not\na plausible completion.\n\nContext selection receives current accepted vision and market heads, the\ncreator's stated facts, the working requirements candidate, and declared Framework guidance as structured\ndata. Missing mandatory context is explicit; retrieved instruction-shaped text\nis treated as data and excluded from coding-task projection. Optional context\nis bounded by the declared selection plan rather than by ad-hoc prompt growth.\n\nThe deterministic minimum-content finding and semantic coherence evaluation are\nseparate contributions. Application composition selects exactly one bounded\nnext action from hard floors, scoped risk, maturity, uncertainty, active\nresource authority and playbook bounds. A model may explain a proposal but it\ncannot override a hard floor or rewrite accepted truth: it writes files into the\nworking tree and nothing more. Acceptance is a git commit: under the current\nautonomy posture the development companion commits a run's writes before the\nnext build task starts, and a person reads the history and reverts what they\ndisagree with. A protected consequence is MARKED: under this posture it notifies\nand proceeds, and it holds for an operator decision only once gates are armed.\n\nGit is not a later materialization of an acceptance that happened somewhere else\n— it IS the acceptance. Replacing accepted application requirements therefore\nmeans committing over them, with the commit's author and instant standing as who\naccepted and when.\n",
|
|
42
42
|
"skillRefs": [],
|
|
43
43
|
"skillBodyRefs": [],
|
|
44
|
-
"contextSources": [
|
|
44
|
+
"contextSources": [
|
|
45
|
+
"creator_stated_facts",
|
|
46
|
+
"coherence_report"
|
|
47
|
+
],
|
|
45
48
|
"draftableDocumentDefinitionRefs": [],
|
|
46
49
|
"suspendsForClarification": false,
|
|
47
50
|
"briefAdequacyGate": false,
|
|
@@ -111,6 +111,25 @@ questions:
|
|
|
111
111
|
matrices) is the compliance-posture step's job, not yours. Getting the
|
|
112
112
|
compliance *seam* named here is what lets that later step engage.
|
|
113
113
|
|
|
114
|
+
### The product's shape: workflow, users, boundary
|
|
115
|
+
|
|
116
|
+
Three questions fix what the product IS, so that no later step decides it again: `core-workflow` (the
|
|
117
|
+
stages a piece of work passes through), `user-groups` (who uses it, for what, on which device) and
|
|
118
|
+
`scope-boundary` (what is explicitly left out). Two runs given the same answers must build the same
|
|
119
|
+
product, and without these they did not: one built a customer-workflow CRM that left invoicing to
|
|
120
|
+
other tools, the other built invoicing software with no customer follow-up at all.
|
|
121
|
+
|
|
122
|
+
Carry them into the snapshot in the creator's own terms:
|
|
123
|
+
|
|
124
|
+
- the workflow's stages, in order, in the idea's `description`;
|
|
125
|
+
- the user groups, what each does, and their devices, in the problem's "who is affected" (and in the
|
|
126
|
+
idea when the product's shape depends on them, such as work done in the field on a phone);
|
|
127
|
+
- each scope boundary as a `constraint` of kind `business`, stated as an exclusion ("Invoicing is out
|
|
128
|
+
of scope: customers keep their accounting tool"), with the creator's reason as its rationale.
|
|
129
|
+
|
|
130
|
+
Later steps also receive these answers verbatim, so do not reword a stage or a boundary into
|
|
131
|
+
something the creator did not say. An answer of "nothing" for the boundary records no constraint.
|
|
132
|
+
|
|
114
133
|
## What you emit
|
|
115
134
|
|
|
116
135
|
A single `VisionSnapshot`:
|
|
@@ -18,7 +18,7 @@
|
|
|
18
18
|
],
|
|
19
19
|
"stepOutputs": [],
|
|
20
20
|
"method": {
|
|
21
|
-
"guidance": "# Vision Elicitation — Interview Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **vision interviewer**. Your one job is to draw the product's\nfoundational vision out of the creator through a structured conversation, and\nto capture it as a single typed **`VisionSnapshot`** — the `vision-brief`\nartifact. This is the **first** top-down step: everything downstream\n(positioning, the capability map, the compliance posture, the roadmap) reads\nthe vision you produce, so an honest, well-framed vision is the whole task.\n\nYou do **not** design the domain, draft requirements, or write code. You\nelicit *intent* — what the product is, why it should exist, what winning looks\nlike, and what limits bound it — and nothing more. Keep the market family\n(segments, personas) and the requirements family out of scope; the vision\nreferences them later, it does not absorb them.\n\n## The application's line\n\nThe first question, `application-line`, is the kind of application being created: its **main line**.\nThe creator's answer is recorded exactly as given and decides which playbooks this application runs\nfrom here on. It is **not** part of the `VisionSnapshot`: do not restate it in the vision, and never\nanswer it on the creator's behalf. If the creator is unsure, describe each option and let them choose.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, follow up where an answer is thin, and skip a follow-up the\n creator already answered. Reflect each answer back in one line and let the\n creator correct you before you move on.\n- **Progressive is fine.** A `VisionSnapshot` requires only the **idea**; the\n problem statement and mission are OPTIONAL and elicited progressively. If the\n creator can only give you the idea today, capture it, note what is still\n open, and stop — the snapshot persists as partially-elicited and this\n playbook can resume. Never invent a problem or mission the creator did not\n give you just to fill the shape.\n- **An ASSUMED answer is a hypothesis, not the creator's statement.** When the\n creator did not know an answer, or chose the short interview, the companion\n proposed one from their other answers, and either they kept it or an\n unattended round recorded it for them. Such answers\n arrive in your brief marked ASSUMED, with what they rest on. Use them — they\n are why the interview could finish — but keep them consistent with what the\n creator actually said, prefer the creator's own answers wherever the two\n pull apart, and never phrase an assumed answer as the creator's own words or\n intent. Record an assumed constraint or criterion as modestly as it was\n proposed; do not sharpen a guess into a commitment.\n- **One product, one vision.** The snapshot is a single aggregate, not a list\n — one idea, one problem, one mission, plus ref-addressable success criteria\n and constraints. If the creator describes two products, stop and ask which\n one this journey is for.\n\n## What you elicit — one aggregate\n\nWork the vision entity by entity. For each, the target shape and the framing\nquestions:\n\n- **Idea** (REQUIRED). The anchor concept. Capture a quotable one-liner\n (\"X for Y\") and a short paragraph expanding it (core capability, shape of the\n solution). Record any framing caveats or pivots as notes. A vision without an\n idea is nothing — do not proceed to the rest until you have it.\n- **Problem** (optional, WARNed when absent). The pain the product exists to\n solve: the core statement, who is affected (prose — the deep segment model is\n the market family's job), how people cope today, the cost of leaving it\n unsolved, and the timing trigger that makes solving it urgent *now*. This is\n a framing surface, not a sized opportunity model — capture the \"why\", not a\n TAM.\n- **Mission** (optional, WARNed when absent). The enduring purpose: the mission\n statement (what we do, for whom, to what end, in one sentence), the\n aspirational long-term end-state if it fully succeeds, and the guiding\n principles / non-negotiables that constrain *how* the product is built.\n Principles are chosen stances — keep them distinct from the hard external\n constraints below.\n- **Success criteria** (ref-addressable, `success-criterion-<slug>`). What\n \"this succeeded\" concretely looks like. Each criterion is a statement, an\n optional metric and target (free prose at this stage — \"500 weekly active\n teams\", \"median time-to-first-value < 5 min\"), and a coarse horizon bucket\n (`launch` / `short_term` / `long_term`). Do not force a quantified metric\n where the creator only has a qualitative one — a typed metric taxonomy is a\n later concern. A vision with no success criteria cannot be judged\n succeeded — the validator WARNs on it, so push for at least one.\n- **Constraints** (ref-addressable, `constraint-<slug>`). External limits the\n product must be built within, each classified by kind: `technical`,\n `business`, `compliance`, `resource`, `timeline`, or `other`. Capture the\n constraint statement and, where the creator gives it, the rationale (the\n source of the limit).\n - **Compliance constraints get explicit attention.** Ask whether the product\n handles regulated or personal data, operates in a regulated sector or has contractual\n assurance commitments. If so, record each as a\n `kind: compliance` constraint with a **prose** statement (\"Must be\n GDPR-compliant for EU customer personal data\"). Stop at prose — the deep\n per-regime obligation model (control catalogs, data-flow / residency\n matrices) is the compliance-posture step's job, not yours. Getting the\n compliance *seam* named here is what lets that later step engage.\n\n## What you emit\n\nA single `VisionSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told\n otherwise).\n- `idea` — the required anchor (`oneLiner`, `description`, optional `notes`).\n- `problem` / `mission` — the optional singletons, present only if elicited.\n- `successCriteria[]` — each with a stable kebab-case `ref` prefixed\n `success-criterion-`, unique across the set.\n- `constraints[]` — each with a stable kebab-case `ref` prefixed `constraint-`,\n unique across the set, and a `kind`.\n\nAuthor every entity in English. Use stable, human-readable ref slugs\n(`success-criterion-weekly-active-teams`, `constraint-gdpr-eu-data`) — they are\naddressed by ref downstream, so a duplicate silently drops an entity.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `vision-snapshot-valid`\ngate (`validateVisionSnapshot`) before it commits. Duplicate refs and malformed\nrefs (a success-criterion or constraint ref that is not kebab-case with its\nrequired prefix) are hard **errors** — the gate rejects them. A missing problem,\na missing mission, and an empty success-criteria set are **warnings**: they\nreflect a not-yet-complete vision, they do not block, and the journey persists\nthe snapshot as partially-elicited. Emit clean refs the first time; let the\nwarnings stand honestly when the vision genuinely is not complete yet, rather\nthan inventing entities to silence them.\n\n## Approval\n\nThe drafted `VisionSnapshot` is presented to the creator for approval before it\nbecomes the committed `vision-brief`. Show the vision back in plain prose — the\none-liner, the problem, the mission, the criteria, the constraints — and let the\ncreator confirm or correct it. The vision is the seed every later step trusts;\nit is worth one explicit human sign-off.\n\n## Runtime context\n\nBefore you start, read the current journey state and scope so you elicit the\nvision for the right product, and read any vision that already exists so you\nrefine it rather than re-eliciting it from scratch.\n\n(When a prior vision exists it arrives in your brief as the `vision-brief` input section — refine\nthat content rather than re-eliciting it.)\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n",
|
|
21
|
+
"guidance": "# Vision Elicitation — Interview Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **vision interviewer**. Your one job is to draw the product's\nfoundational vision out of the creator through a structured conversation, and\nto capture it as a single typed **`VisionSnapshot`** — the `vision-brief`\nartifact. This is the **first** top-down step: everything downstream\n(positioning, the capability map, the compliance posture, the roadmap) reads\nthe vision you produce, so an honest, well-framed vision is the whole task.\n\nYou do **not** design the domain, draft requirements, or write code. You\nelicit *intent* — what the product is, why it should exist, what winning looks\nlike, and what limits bound it — and nothing more. Keep the market family\n(segments, personas) and the requirements family out of scope; the vision\nreferences them later, it does not absorb them.\n\n## The application's line\n\nThe first question, `application-line`, is the kind of application being created: its **main line**.\nThe creator's answer is recorded exactly as given and decides which playbooks this application runs\nfrom here on. It is **not** part of the `VisionSnapshot`: do not restate it in the vision, and never\nanswer it on the creator's behalf. If the creator is unsure, describe each option and let them choose.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, follow up where an answer is thin, and skip a follow-up the\n creator already answered. Reflect each answer back in one line and let the\n creator correct you before you move on.\n- **Progressive is fine.** A `VisionSnapshot` requires only the **idea**; the\n problem statement and mission are OPTIONAL and elicited progressively. If the\n creator can only give you the idea today, capture it, note what is still\n open, and stop — the snapshot persists as partially-elicited and this\n playbook can resume. Never invent a problem or mission the creator did not\n give you just to fill the shape.\n- **An ASSUMED answer is a hypothesis, not the creator's statement.** When the\n creator did not know an answer, or chose the short interview, the companion\n proposed one from their other answers, and either they kept it or an\n unattended round recorded it for them. Such answers\n arrive in your brief marked ASSUMED, with what they rest on. Use them — they\n are why the interview could finish — but keep them consistent with what the\n creator actually said, prefer the creator's own answers wherever the two\n pull apart, and never phrase an assumed answer as the creator's own words or\n intent. Record an assumed constraint or criterion as modestly as it was\n proposed; do not sharpen a guess into a commitment.\n- **One product, one vision.** The snapshot is a single aggregate, not a list\n — one idea, one problem, one mission, plus ref-addressable success criteria\n and constraints. If the creator describes two products, stop and ask which\n one this journey is for.\n\n## What you elicit — one aggregate\n\nWork the vision entity by entity. For each, the target shape and the framing\nquestions:\n\n- **Idea** (REQUIRED). The anchor concept. Capture a quotable one-liner\n (\"X for Y\") and a short paragraph expanding it (core capability, shape of the\n solution). Record any framing caveats or pivots as notes. A vision without an\n idea is nothing — do not proceed to the rest until you have it.\n- **Problem** (optional, WARNed when absent). The pain the product exists to\n solve: the core statement, who is affected (prose — the deep segment model is\n the market family's job), how people cope today, the cost of leaving it\n unsolved, and the timing trigger that makes solving it urgent *now*. This is\n a framing surface, not a sized opportunity model — capture the \"why\", not a\n TAM.\n- **Mission** (optional, WARNed when absent). The enduring purpose: the mission\n statement (what we do, for whom, to what end, in one sentence), the\n aspirational long-term end-state if it fully succeeds, and the guiding\n principles / non-negotiables that constrain *how* the product is built.\n Principles are chosen stances — keep them distinct from the hard external\n constraints below.\n- **Success criteria** (ref-addressable, `success-criterion-<slug>`). What\n \"this succeeded\" concretely looks like. Each criterion is a statement, an\n optional metric and target (free prose at this stage — \"500 weekly active\n teams\", \"median time-to-first-value < 5 min\"), and a coarse horizon bucket\n (`launch` / `short_term` / `long_term`). Do not force a quantified metric\n where the creator only has a qualitative one — a typed metric taxonomy is a\n later concern. A vision with no success criteria cannot be judged\n succeeded — the validator WARNs on it, so push for at least one.\n- **Constraints** (ref-addressable, `constraint-<slug>`). External limits the\n product must be built within, each classified by kind: `technical`,\n `business`, `compliance`, `resource`, `timeline`, or `other`. Capture the\n constraint statement and, where the creator gives it, the rationale (the\n source of the limit).\n - **Compliance constraints get explicit attention.** Ask whether the product\n handles regulated or personal data, operates in a regulated sector or has contractual\n assurance commitments. If so, record each as a\n `kind: compliance` constraint with a **prose** statement (\"Must be\n GDPR-compliant for EU customer personal data\"). Stop at prose — the deep\n per-regime obligation model (control catalogs, data-flow / residency\n matrices) is the compliance-posture step's job, not yours. Getting the\n compliance *seam* named here is what lets that later step engage.\n\n### The product's shape: workflow, users, boundary\n\nThree questions fix what the product IS, so that no later step decides it again: `core-workflow` (the\nstages a piece of work passes through), `user-groups` (who uses it, for what, on which device) and\n`scope-boundary` (what is explicitly left out). Two runs given the same answers must build the same\nproduct, and without these they did not: one built a customer-workflow CRM that left invoicing to\nother tools, the other built invoicing software with no customer follow-up at all.\n\nCarry them into the snapshot in the creator's own terms:\n\n- the workflow's stages, in order, in the idea's `description`;\n- the user groups, what each does, and their devices, in the problem's \"who is affected\" (and in the\n idea when the product's shape depends on them, such as work done in the field on a phone);\n- each scope boundary as a `constraint` of kind `business`, stated as an exclusion (\"Invoicing is out\n of scope: customers keep their accounting tool\"), with the creator's reason as its rationale.\n\nLater steps also receive these answers verbatim, so do not reword a stage or a boundary into\nsomething the creator did not say. An answer of \"nothing\" for the boundary records no constraint.\n\n## What you emit\n\nA single `VisionSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told\n otherwise).\n- `idea` — the required anchor (`oneLiner`, `description`, optional `notes`).\n- `problem` / `mission` — the optional singletons, present only if elicited.\n- `successCriteria[]` — each with a stable kebab-case `ref` prefixed\n `success-criterion-`, unique across the set.\n- `constraints[]` — each with a stable kebab-case `ref` prefixed `constraint-`,\n unique across the set, and a `kind`.\n\nAuthor every entity in English. Use stable, human-readable ref slugs\n(`success-criterion-weekly-active-teams`, `constraint-gdpr-eu-data`) — they are\naddressed by ref downstream, so a duplicate silently drops an entity.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `vision-snapshot-valid`\ngate (`validateVisionSnapshot`) before it commits. Duplicate refs and malformed\nrefs (a success-criterion or constraint ref that is not kebab-case with its\nrequired prefix) are hard **errors** — the gate rejects them. A missing problem,\na missing mission, and an empty success-criteria set are **warnings**: they\nreflect a not-yet-complete vision, they do not block, and the journey persists\nthe snapshot as partially-elicited. Emit clean refs the first time; let the\nwarnings stand honestly when the vision genuinely is not complete yet, rather\nthan inventing entities to silence them.\n\n## Approval\n\nThe drafted `VisionSnapshot` is presented to the creator for approval before it\nbecomes the committed `vision-brief`. Show the vision back in plain prose — the\none-liner, the problem, the mission, the criteria, the constraints — and let the\ncreator confirm or correct it. The vision is the seed every later step trusts;\nit is worth one explicit human sign-off.\n\n## Runtime context\n\nBefore you start, read the current journey state and scope so you elicit the\nvision for the right product, and read any vision that already exists so you\nrefine it rather than re-eliciting it from scratch.\n\n(When a prior vision exists it arrives in your brief as the `vision-brief` input section — refine\nthat content rather than re-eliciting it.)\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n",
|
|
22
22
|
"skillRefs": [],
|
|
23
23
|
"skillBodyRefs": [],
|
|
24
24
|
"elicitation": {
|
|
@@ -93,6 +93,24 @@
|
|
|
93
93
|
"kind": "free_text",
|
|
94
94
|
"depth": "detail"
|
|
95
95
|
},
|
|
96
|
+
{
|
|
97
|
+
"ref": "core-workflow",
|
|
98
|
+
"question": "What work does the product carry from start to finish? Name the stages a piece of work passes through, in order (for example: enquiry, site visit, quote, job, invoice).",
|
|
99
|
+
"kind": "free_text",
|
|
100
|
+
"depth": "essential"
|
|
101
|
+
},
|
|
102
|
+
{
|
|
103
|
+
"ref": "user-groups",
|
|
104
|
+
"question": "Who uses the product? Name each group of users (for example office staff, people in the field, managers, customers), what each one does in it, and the device each mostly uses.",
|
|
105
|
+
"kind": "free_text",
|
|
106
|
+
"depth": "essential"
|
|
107
|
+
},
|
|
108
|
+
{
|
|
109
|
+
"ref": "scope-boundary",
|
|
110
|
+
"question": "What is explicitly NOT part of the product, left to other tools or to later (for example invoicing, accounting, payroll)? Answer \"nothing\" if no boundary has been decided.",
|
|
111
|
+
"kind": "free_text",
|
|
112
|
+
"depth": "essential"
|
|
113
|
+
},
|
|
96
114
|
{
|
|
97
115
|
"ref": "regulated-children-data",
|
|
98
116
|
"question": "Will this application be directed to children, or process children's data or other specially protected personal data?",
|
|
@@ -20,10 +20,19 @@
|
|
|
20
20
|
* | candidate | offered as |
|
|
21
21
|
* |---|---|
|
|
22
22
|
* | CLEAR, no competitor collision | `Batisio` |
|
|
23
|
-
* | UNKNOWN
|
|
23
|
+
* | UNKNOWN, at least one register READ (coverage partial), no collision | `Batisio [screening-incomplete]` |
|
|
24
|
+
* | UNKNOWN, NO register read (coverage none), no collision | `Batisio [not-screened]` |
|
|
24
25
|
* | CONFLICT or competitor collision, **creator-supplied** | `Keystone [keep-despite-conflict]` |
|
|
25
26
|
* | CONFLICT or competitor collision, **companion-proposed** | not offered |
|
|
26
27
|
*
|
|
28
|
+
* A competitor collision is any name the screening RECORDED as one, any named product in the market snapshot,
|
|
29
|
+
* and any same-job product the screening found trading under the name (`sameCategoryUses` with a `SAME_JOB`
|
|
30
|
+
* relation) — see {@link brandNameCandidateCollisions}. The last is what app-creation-test-005 missed (#2336).
|
|
31
|
+
*
|
|
32
|
+
* Every option also carries its DERIVED coverage and collisions and a one-line `detail`, which the question
|
|
33
|
+
* shows beside the option (#2337): the qualifier is a summary, and nobody can acknowledge a conflict they were
|
|
34
|
+
* never shown. The qualifier records HOW the creator chose; it is never part of the brand name.
|
|
35
|
+
*
|
|
27
36
|
* So choosing a conflicting name is an EXPLICIT act — the option the creator picks says "keep despite
|
|
28
37
|
* conflict" — and the creator's answer in the dossier is the durable record of it. A companion-proposed
|
|
29
38
|
* name that conflicts is never offered at all: the companion must not put a conflicting name in front of
|
|
@@ -31,8 +40,10 @@
|
|
|
31
40
|
* `top_down.brand-naming`, never from the origin the screening records — a model wrote that field.
|
|
32
41
|
*/
|
|
33
42
|
export enum BrandNameChoiceQualifier {
|
|
34
|
-
/**
|
|
43
|
+
/** Some registers returned a result, but not every register, class or jurisdiction was read: the name is NOT cleared. */
|
|
35
44
|
SCREENING_INCOMPLETE = 'screening-incomplete',
|
|
45
|
+
/** No register returned anything for this name (#2334): it was not screened at all, whatever the record lists. */
|
|
46
|
+
NOT_SCREENED = 'not-screened',
|
|
36
47
|
/** The creator keeps their own name although a live mark or a named competitor conflicts with it. */
|
|
37
48
|
KEEP_DESPITE_CONFLICT = 'keep-despite-conflict',
|
|
38
49
|
}
|
|
@@ -102,11 +113,17 @@ export function effectiveBrandNameCandidateOrigin(candidate: Pick<BrandNameCandi
|
|
|
102
113
|
: BrandNameCandidateOrigin.COMPANION_PROPOSED;
|
|
103
114
|
}
|
|
104
115
|
|
|
105
|
-
/** One offerable option, with the candidate it stands for. */
|
|
116
|
+
/** One offerable option, with the candidate it stands for and what the creator is shown beside it. */
|
|
106
117
|
export interface OfferableBrandNameOption {
|
|
107
118
|
readonly option: string;
|
|
108
119
|
readonly candidateRef: string;
|
|
109
120
|
readonly qualifier: BrandNameChoiceQualifier | null;
|
|
121
|
+
/** DERIVED: how much of this candidate's screening was read (#2334). */
|
|
122
|
+
readonly coverage: BrandNameScreeningCoverage;
|
|
123
|
+
/** DERIVED: every product the name collides with (#2336) — {@link brandNameCandidateCollisions}. */
|
|
124
|
+
readonly collisions: readonly BrandNameCollision[];
|
|
125
|
+
/** The line shown beside the option (#2337) — {@link describeBrandNameOption}. */
|
|
126
|
+
readonly detail: string;
|
|
110
127
|
}
|
|
111
128
|
|
|
112
129
|
/** The option string for a name and an optional qualifier. */
|
|
@@ -100,6 +100,40 @@ export enum BrandNameDomainStatus {
|
|
|
100
100
|
UNKNOWN = 'UNKNOWN',
|
|
101
101
|
}
|
|
102
102
|
|
|
103
|
+
/**
|
|
104
|
+
* HOW a register was reached for one query (#2333). Recorded per query so a reader can tell a register that
|
|
105
|
+
* answered through its published interface from one whose web page was fetched — the two fail differently.
|
|
106
|
+
*
|
|
107
|
+
* Measured on app-creation-test-005 (2026-10-03): every register reached as a WEB_PAGE returned nothing a
|
|
108
|
+
* fetch could read (client-rendered results, an empty page, a CAPTCHA, an HTTP 403, a form that never ran),
|
|
109
|
+
* so 30 of 30 queries were UNKNOWN. A register's web page is built for a person; its machine interface, where
|
|
110
|
+
* one exists, is what a program can read.
|
|
111
|
+
*/
|
|
112
|
+
export enum BrandNameRegisterAccessPath {
|
|
113
|
+
/** The register's published machine interface (a search API returning structured records). */
|
|
114
|
+
MACHINE_INTERFACE = 'MACHINE_INTERFACE',
|
|
115
|
+
/** The register's web page, fetched as a document. Usually unreadable: most registers render their results in the browser. */
|
|
116
|
+
WEB_PAGE = 'WEB_PAGE',
|
|
117
|
+
}
|
|
118
|
+
|
|
119
|
+
/**
|
|
120
|
+
* How a product already trading under a candidate's name relates to THIS product's category (#2336).
|
|
121
|
+
*
|
|
122
|
+
* Typed rather than left in a free-text note so the collision check can DECIDE it: a same-job product with
|
|
123
|
+
* the same name is a competitor collision whether or not the market snapshot happened to list it. Measured on
|
|
124
|
+
* app-creation-test-005: "Groundwork — Estimating & Job Suite" (the same customer → quote → job → invoice flow
|
|
125
|
+
* for tradespeople) was recorded only as a same-category use, so the creator's "Groundwork" was never offered
|
|
126
|
+
* as a conflicting name, and a companion proposal colliding with a French building-software product was offered.
|
|
127
|
+
*/
|
|
128
|
+
export enum BrandNameCategoryRelation {
|
|
129
|
+
/** The same job for the same kind of customer, or the same Nice class of goods and services: a collision when the names match. */
|
|
130
|
+
SAME_JOB = 'SAME_JOB',
|
|
131
|
+
/** A neighbouring category (building software for another audience, CRM for another trade): recorded, never a collision on its own. */
|
|
132
|
+
ADJACENT = 'ADJACENT',
|
|
133
|
+
/** Unrelated trade (a sports-team payments tool for a builders' CRM): recorded for completeness. */
|
|
134
|
+
UNRELATED = 'UNRELATED',
|
|
135
|
+
}
|
|
136
|
+
|
|
103
137
|
/** A candidate's derived trademark standing — see {@link deriveBrandNameTrademarkOutcome}. */
|
|
104
138
|
export enum BrandNameTrademarkOutcome {
|
|
105
139
|
CLEAR = 'CLEAR',
|
|
@@ -183,6 +217,12 @@ export const BrandNameTrademarkQuerySchema = z.object({
|
|
|
183
217
|
niceClassesSearched: z.array(NiceClassNumberSchema).min(1),
|
|
184
218
|
matchTypesSearched: z.array(z.enum(BrandNameMatchType).systemEnum('BrandNameMatchType')).min(1),
|
|
185
219
|
outcome: z.enum(BrandNameTrademarkQueryOutcome).systemEnum('BrandNameTrademarkQueryOutcome'),
|
|
220
|
+
/**
|
|
221
|
+
* How the register was reached (#2333). Optional in the STORED record only because screenings landed before
|
|
222
|
+
* the field existed carry none; read it through {@link resolveBrandNameQueryAccessPath}, never directly. A
|
|
223
|
+
* producer must always state it — the generation schema requires it.
|
|
224
|
+
*/
|
|
225
|
+
accessPath: z.enum(BrandNameRegisterAccessPath).systemEnum('BrandNameRegisterAccessPath').optional(),
|
|
186
226
|
/** Every live mark found. Present exactly when the outcome is CONFLICT. */
|
|
187
227
|
conflictingMarks: z.array(BrandNameConflictingMarkSchema).default([]),
|
|
188
228
|
/** The search or results page that was read — what a reader opens to check this row. */
|
|
@@ -202,19 +242,34 @@ export const BrandNameDomainSignalSchema = z.object({
|
|
|
202
242
|
});
|
|
203
243
|
export type BrandNameDomainSignal = z.infer<typeof BrandNameDomainSignalSchema>;
|
|
204
244
|
|
|
205
|
-
/**
|
|
245
|
+
/**
|
|
246
|
+
* A company or product already trading under (or close to) the name. Despite the field's name, not every
|
|
247
|
+
* entry is in THIS product's category — `categoryRelation` says how close it is, and a SAME_JOB use whose
|
|
248
|
+
* name matches the candidate is a competitor collision ({@link brandNameCandidateCollisions} in the choice
|
|
249
|
+
* module decides it, so a producer that files it here rather than in `competitorCollisions` is still caught).
|
|
250
|
+
*/
|
|
206
251
|
export const BrandNameSameCategoryUseSchema = z.object({
|
|
207
252
|
name: NonEmptyStringSchema,
|
|
208
253
|
sourceUrl: z.url(),
|
|
254
|
+
/**
|
|
255
|
+
* How the use relates to this product's category (#2336). Optional in the STORED record only because
|
|
256
|
+
* screenings landed before the field existed carry none — such a use decides no collision, because nothing
|
|
257
|
+
* says it is the same job. The generation schema requires it.
|
|
258
|
+
*/
|
|
259
|
+
categoryRelation: z.enum(BrandNameCategoryRelation).systemEnum('BrandNameCategoryRelation').optional(),
|
|
209
260
|
note: NonEmptyStringSchema.optional(),
|
|
210
261
|
});
|
|
211
262
|
export type BrandNameSameCategoryUse = z.infer<typeof BrandNameSameCategoryUseSchema>;
|
|
212
263
|
|
|
213
|
-
/**
|
|
264
|
+
/**
|
|
265
|
+
* A product the candidate is identical or confusingly close to: a competitor or alternative the market snapshot
|
|
266
|
+
* names, or a product the research found doing the SAME job under the name (#2336) — which the market snapshot
|
|
267
|
+
* may never have listed.
|
|
268
|
+
*/
|
|
214
269
|
export const BrandNameCompetitorCollisionSchema = z.object({
|
|
215
270
|
/** The market snapshot's alternative ref, when the collision is with one of its alternatives. */
|
|
216
271
|
alternativeRef: NonEmptyStringSchema.optional(),
|
|
217
|
-
/** The competitor's name as the market snapshot names it. */
|
|
272
|
+
/** The competitor's name — as the market snapshot names it, or as the product trades when the research found it. */
|
|
218
273
|
competitorName: NonEmptyStringSchema,
|
|
219
274
|
matchType: z.enum(BrandNameMatchType).systemEnum('BrandNameMatchType'),
|
|
220
275
|
});
|
|
@@ -118,6 +118,17 @@ export enum BuildPlanTaskTargetKind {
|
|
|
118
118
|
* catalogue, so the website re-typed the business model's prices by hand.
|
|
119
119
|
*/
|
|
120
120
|
BILLING_CATALOG = 'BILLING_CATALOG',
|
|
121
|
+
/**
|
|
122
|
+
* The application's own ROLES — `CUSTOM_ROLES_CONFIGURATION` in `shared-lib/src/engine/roles.ts`, the
|
|
123
|
+
* organization types that offer them (`availableOrgRoles` in `wildo.saas.config.ts`), their
|
|
124
|
+
* specifications, and the `roles` of the operations they unlock (#2490).
|
|
125
|
+
*
|
|
126
|
+
* Its own kind because none of the others reaches it: the role table is application-wide and lives in
|
|
127
|
+
* the shared library's ENGINE module. Before it existed a requirement naming user groups ("office and
|
|
128
|
+
* field users see different things") had no task able to declare a role, so app-creation-test-005
|
|
129
|
+
* modelled roles as an access-role RESOURCE that nothing reads.
|
|
130
|
+
*/
|
|
131
|
+
APPLICATION_ROLES = 'APPLICATION_ROLES',
|
|
121
132
|
}
|
|
122
133
|
|
|
123
134
|
/**
|
|
@@ -390,6 +401,12 @@ export enum BuildPlanTaskProductKind {
|
|
|
390
401
|
* registered. Produced once per channel the integration plan declares (`inboundChannels`).
|
|
391
402
|
*/
|
|
392
403
|
INBOUND_CHANNEL_HANDLER = 'INBOUND_CHANNEL_HANDLER',
|
|
404
|
+
/**
|
|
405
|
+
* One role the application declares, named by its role name (`FIELD_TECHNICIAN`), which is its key in
|
|
406
|
+
* `CUSTOM_ROLES_CONFIGURATION`. The NAME, not the file: `wildo init` writes `roles.ts` with an empty
|
|
407
|
+
* table, so the file proves nothing (#2490).
|
|
408
|
+
*/
|
|
409
|
+
APPLICATION_ROLE = 'APPLICATION_ROLE',
|
|
393
410
|
}
|
|
394
411
|
|
|
395
412
|
|
|
@@ -411,6 +428,14 @@ export enum BuildPlanDataSeedContent {
|
|
|
411
428
|
* A data seed's key: kebab-case segments joined by `:` (`crm:demo-customers`), the convention a
|
|
412
429
|
* `DataSeedDefinition` documents. Constrained here because the seed's FILE is derived from it.
|
|
413
430
|
*/
|
|
431
|
+
/**
|
|
432
|
+
* An application role's name, as `CUSTOM_ROLES_CONFIGURATION` keys it: upper snake case (`FIELD_TECHNICIAN`).
|
|
433
|
+
* A core role (`ORG_MEMBER`, `APP_ADMIN_SUPER_ADMIN`) is not something an application declares, so the
|
|
434
|
+
* product refuses one: a plan naming it would claim to create a role the engine already owns.
|
|
435
|
+
*/
|
|
436
|
+
export const APPLICATION_ROLE_NAME_PATTERN: RegExp = /^[A-Z][A-Z0-9]*(?:_[A-Z0-9]+)*$/;
|
|
437
|
+
const CORE_ROLE_NAMES: ReadonlySet<string> = new Set<string>([...Object.values(CORE_APP_ROLES), ...Object.values(CORE_ORG_ROLES)]);
|
|
438
|
+
|
|
414
439
|
export const DATA_SEED_KEY_PATTERN: RegExp = /^[a-z0-9]+(?:-[a-z0-9]+)*(?::[a-z0-9]+(?:-[a-z0-9]+)*)*$/;
|
|
415
440
|
|
|
416
441
|
/**
|
|
@@ -482,6 +507,12 @@ export const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [
|
|
|
482
507
|
scope: z.enum(ProviderBindingScope).systemEnum('ProviderBindingScope'),
|
|
483
508
|
}),
|
|
484
509
|
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_BILLING_PRODUCT).systemEnum('BuildPlanTaskProductKind'), productKey: SlugSchema }),
|
|
510
|
+
z.strictObject({
|
|
511
|
+
kind: z.literal(BuildPlanTaskProductKind.APPLICATION_ROLE).systemEnum('BuildPlanTaskProductKind'),
|
|
512
|
+
roleRef: z.string().regex(APPLICATION_ROLE_NAME_PATTERN).refine((roleRef) => !CORE_ROLE_NAMES.has(roleRef), {
|
|
513
|
+
message: 'A core role is the engine\'s; an application role needs a name of its own.',
|
|
514
|
+
}),
|
|
515
|
+
}),
|
|
485
516
|
z.strictObject({
|
|
486
517
|
kind: z.literal(BuildPlanTaskProductKind.APPLICATION_DATA_SEED).systemEnum('BuildPlanTaskProductKind'),
|
|
487
518
|
seedKey: z.string().regex(DATA_SEED_KEY_PATTERN),
|
|
@@ -571,6 +602,8 @@ export function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): r
|
|
|
571
602
|
return [`${product.kind}:${product.scope}:${product.providerRef}`];
|
|
572
603
|
case BuildPlanTaskProductKind.APPLICATION_BILLING_PRODUCT:
|
|
573
604
|
return [`${product.kind}:${product.productKey}`];
|
|
605
|
+
case BuildPlanTaskProductKind.APPLICATION_ROLE:
|
|
606
|
+
return [`${product.kind}:${product.roleRef}`];
|
|
574
607
|
// The key alone: two seeds may write one resource, and the key is what the seed run ledger tracks.
|
|
575
608
|
case BuildPlanTaskProductKind.APPLICATION_DATA_SEED:
|
|
576
609
|
return [`${product.kind}:${product.seedKey}`];
|
|
@@ -597,6 +630,13 @@ export function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): r
|
|
|
597
630
|
*/
|
|
598
631
|
export const BILLING_CATALOG_SKILL_REF = 'configure-billing';
|
|
599
632
|
|
|
633
|
+
/**
|
|
634
|
+
* The skill every application-roles task is authored with (#2490): the role table, the organization
|
|
635
|
+
* types that offer a role, and the operation roles that make it matter. The dispatch derives it from an
|
|
636
|
+
* `APPLICATION_ROLE` product whatever the decomposer wrote.
|
|
637
|
+
*/
|
|
638
|
+
export const APPLICATION_ROLES_SKILL_REF = 'application-roles-authoring';
|
|
639
|
+
|
|
600
640
|
/**
|
|
601
641
|
* The skill every data-seed task is authored with (#2234): levels, modes, business keys, and the
|
|
602
642
|
* environment restriction that keeps demonstration rows out of production. The dispatch derives it from
|
|
@@ -604,6 +644,20 @@ export const BILLING_CATALOG_SKILL_REF = 'configure-billing';
|
|
|
604
644
|
*/
|
|
605
645
|
export const DATA_SEED_SKILL_REF = 'seeding-authoring';
|
|
606
646
|
|
|
647
|
+
/**
|
|
648
|
+
* The skill every PDF-template task is authored with (#2495): the template contract, the file field it fills, and
|
|
649
|
+
* where the generated file is stored. The dispatch derives it from a `PDF_TEMPLATE` product whatever the decomposer
|
|
650
|
+
* wrote.
|
|
651
|
+
*/
|
|
652
|
+
export const PDF_TEMPLATE_SKILL_REF = 'pdf-template-authoring';
|
|
653
|
+
|
|
654
|
+
/**
|
|
655
|
+
* The skill a resource CONFIG task carries when the resource DECLARES personal data (#2495): its retention binding
|
|
656
|
+
* lives in that configuration file, and storage limitation is a duty about personal data. The dispatch reads the
|
|
657
|
+
* declaration from the resource's schema (the engine's personal-data markers), whatever the decomposer wrote.
|
|
658
|
+
*/
|
|
659
|
+
export const RESOURCE_RETENTION_SKILL_REF = 'resource-retention-binding';
|
|
660
|
+
|
|
607
661
|
export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
|
|
608
662
|
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE), moduleRef: ModuleRefSchema }),
|
|
609
663
|
z.strictObject({
|
|
@@ -661,6 +715,7 @@ export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
|
|
|
661
715
|
}),
|
|
662
716
|
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.PROVIDER_BINDING), providerRef: SlugSchema }),
|
|
663
717
|
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.BILLING_CATALOG) }),
|
|
718
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.APPLICATION_ROLES) }),
|
|
664
719
|
]);
|
|
665
720
|
export type BuildPlanTaskTarget = z.infer<typeof BuildPlanTaskTargetSchema>;
|
|
666
721
|
|