@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
|
@@ -171,17 +171,18 @@ Keep this playbook at scaffold depth. Explicitly **out of scope here**:
|
|
|
171
171
|
The scoring seam stays pluggable — do NOT build or tune a scoring or
|
|
172
172
|
build-order model in this playbook.
|
|
173
173
|
- **Deep feature-spec drafts.** A draft here is a first-cut capability contract
|
|
174
|
-
(purpose / roles / use-when). Rich operation inventories
|
|
175
|
-
|
|
176
|
-
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
|
|
180
|
-
|
|
181
|
-
|
|
174
|
+
(purpose / roles / use-when). Rich operation inventories and UX are the
|
|
175
|
+
bottom-up build phase's job, not the capability map. The business verbs a
|
|
176
|
+
capability implies (accept, issue, close) are NOT deferred: the domain plan
|
|
177
|
+
declares them as lifecycles, so state them where a capability rests on them.
|
|
178
|
+
- **Requirement gain traceability.** A requirement cross-refs ICPs, jobs and the
|
|
179
|
+
market PAINS it relieves (`painRefs`), but not the gains it delivers, so a
|
|
180
|
+
"this requirement delivers `gain-X`" trace is expressible only in prose. Use
|
|
181
|
+
`painRefs` where a capability answers a pain; do NOT reshape the requirements
|
|
182
|
+
contract here to add a gain edge.
|
|
182
183
|
|
|
183
184
|
If you find yourself perfecting any of the above, stop and leave the slice at
|
|
184
|
-
scaffold depth
|
|
185
|
+
scaffold depth.
|
|
185
186
|
|
|
186
187
|
## What you emit
|
|
187
188
|
|
|
@@ -51,7 +51,7 @@
|
|
|
51
51
|
],
|
|
52
52
|
"stepOutputs": [],
|
|
53
53
|
"method": {
|
|
54
|
-
"guidance": "# Capability Map — Benefit → Feature Pivot 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 be\n> iterated. The mapping order, the draft-authoring posture, and the\n> prioritization rubric below are deliberately explicit so they can be tuned\n> against real runs — treat them as a starting rubric, not a frozen contract.\n> The *analytical depth* of the capability work (quantified FIT / Kano scoring\n> precision, a real prioritization model) is intentionally shallow here and is\n> deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **capability architect**. This playbook is the **pivot**: it turns\nthe *value proposition* (what the product promises the market) into *product\ncapability* (the features that actually deliver those promises). Value-proposition\nsharpening already produced a **MarketSnapshot** whose benefits carry weighted\nrelieves/creates/advances edges and per-ICP Kano categories. Your one job is to\nanswer, for every benefit: **which feature delivers this, and does that feature\nexist yet?** — and then record the answer in two places:\n\n1. **The benefit → feature edge** — on the SAME MarketSnapshot, wire every\n benefit's `deliveredByFeatureRefs[]` to the feature(s) that deliver it. This\n edge is the authoritative capability-mapping link (`FeatureBenefitConfig.\n deliveredByFeatureRefs`, required and non-empty): a benefit that is not\n deliverable by any feature is not a real capability. (`market-add-feature-benefit`)\n2. **The spec-first feature drafts** — for every feature the map introduces that\n has **no code registry entry yet**, author a `FeatureSpecificationDraft`\n (purpose, businessRole, lifecycleRole, useWhen/avoidWhen, availabilityRole —\n all in prose). These are **spec-first**: you author them BEFORE the runtime\n `FeatureDefinition` exists; the factory injects the `ref` later from the\n runtime identifier, so a draft is authored ref-less (`Omit<…, 'ref'>`). Use the **Draft path** in `spec-feature-update`; its runtime workflow is for a later implementation task. The draft wrapper carries `featureRef`, while the nested prose payload remains ref-less.\n\nThen you **assess fit** for the resulting feature set with a FIT-scoring + Kano\nstep — kept pluggable and versioned (see \"The scoring seam\" below). This does not set build priority.\n\nThis is a **focused pivot pass**, distinct from value-proposition sharpening\n(which weighted the benefits) and from scope/roadmap (which slots the features\ninto releases). Where value-proposition made the benefits sharp, you make each\nbenefit *deliverable* and give every new capability its first spec.\n\n## Read state first — the two families you read, the two you write\n\nThis playbook is **idempotent** and a *refinement*: a MarketSnapshot must\nalready exist (the `artifact_exists` precondition enforces it). Before mapping\nanything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it.\n2. Read the existing **MarketSnapshot** (the benefits and their weighting),\n the **requirements** (`requirements` family — the functional/non-functional\n requirements the features must satisfy), and the **VisionSnapshot**\n (`vision-brief` — the differentiation anchor). You map capability against the\n real market intent, the real requirements, and the real differentiation — not\n from scratch.\n\n\nYou **read** `market-snapshot` + `requirements` + `vision-brief`; you **write**\nthe refined `market-snapshot` (edge wired) and the `feature-drafts` family (the\nnew drafts).\n\n## The mapping loop (benefit by benefit)\n\nFor each benefit in the snapshot:\n\n1. **Identify the delivering feature(s).** Ask what capability the product must\n have for this benefit's claim to be true. Prefer *one clear feature per\n benefit*; a benefit may legitimately need more than one, and one feature may\n deliver several benefits.\n2. **Reuse before you create.** If a delivering feature already appears on\n another benefit's `deliveredByFeatureRefs`, or already has a draft from an\n earlier run, **reuse that same feature ref** — never mint a second ref for the\n same capability. Reusing refs is what keeps the map coherent and lets the\n downstream scope/roadmap playbook slot each feature exactly once.\n3. **Wire the edge.** Add the feature ref(s) to the benefit's\n `deliveredByFeatureRefs[]`. Every benefit must end with a non-empty edge —\n the gate fails a benefit with an empty `deliveredByFeatureRefs` as\n `EMPTY_BENEFIT_DELIVERED_BY` (ERROR).\n4. **Draft the new feature (spec-first).** If the feature is new (no code\n registry entry, no prior draft), author its `FeatureSpecificationDraft` into\n the `feature-drafts` family. A draft is the **prose subset** of a feature\n spec: a business-language `purpose`, its `businessRole` / optional\n `lifecycleRole`, `useWhen` / `avoidWhen`, optional `businessConstraints`, and\n the `availabilityRole` (how the feature gates / packages). **Author ONLY these\n prose fields.** Do NOT author a `ref` — the factory injects it later from the\n runtime feature identifier, which is why a draft is authored ref-less. Do NOT\n wire `codeHandling` (it links a spec back to a runtime enum member +\n collection entry that does not exist yet at this phase) — the code-handling\n provenance is added when the feature is actually built, not now.\n Use the **Draft path** in `spec-feature-update`, including its wrapper and export contract. Do not run its runtime-enum, definition, policy or profile steps. Keep this a capability contract, not an implementation.\n5. **Trace to requirements + vision.** A feature only earns its place if it\n delivers a benefit that traces to the vision's differentiation AND satisfies\n real requirements. When a benefit's delivering feature has no requirement\n behind it, that is a signal to either add the requirement upstream or drop the\n claim — not to invent a feature the product does not need.\n\n## The scoring seam — FIT + Kano, kept PLUGGABLE and VERSIONED\n\nAssess the mapped capability set with a **FIT-scoring + Kano** step, and let that\nassessment inform how the capabilities get prioritized.\n\n**FIT is a fit signal, NOT a priority ranking — do not conflate them.**\n`computeFeatureFitScoreForICP` answers one narrow question: *how well does this\nfeature serve this ICP* on a deterministic 0–100 scale (edge `degree` × the ICP's\nown edge weight). It deliberately does NOT answer \"which feature do we build\nfirst\" — that is prioritization, a separate, deferred concern. Combine the FIT\nscore with the per-ICP Kano category (`THRESHOLD` = table-stakes, `PERFORMANCE` =\nmore-is-better, `DELIGHTER` = upside) to read *table-stakes vs. upside per\nsegment* — a fit judgement, not a build-order. Bending the FIT score into a\nbuild-order ranking yields wrong answers (this is the locked FIT-vs-priority\nvocabulary the `market-scoring-interpretation` skill enforces).\n\n**This step is a pluggable, versioned interface — bind to it, never embed it.**\nThe scoring / prioritization methodology is expected to change substantially in a\nlater phase, so this playbook references the scoring *interface* (via the\n`market-scoring-interpretation` skill) and consumes its output; it does **not**\nre-implement the scoring math and does **not** hard-couple to any specific scoring\nfunction (`computeFeatureFitScoreForICP` today, a different scorer tomorrow). You do\nnot run the scorer and must not estimate its output: the per-ICP FIT scores are\ncomputed for you and arrive in the declared `market_fit_scores` context section of your brief, beside each\nbenefit's authored Kano category. Read them there and use them to sanity-check the\ncapability set — a `0` carrying a stated reason is structural (an anti-target, or no\nbenefit covering that ICP), not a measurement of poor fit. If\nyou find yourself hand-writing a scoring formula, tuning weights to hit a target\nresult, or building an actual build-order prioritization model, **stop** — that is\nthe depth phase's job, and hard-coding it here would break the pluggability\ncontract (OQ-6).\n\nAt scaffold depth this is a *fit sanity check on the capability set*, not a\ndefended prioritization. The headline gap it surfaces: a table-stakes capability\n(a `THRESHOLD` benefit for a `CORE`/`EXPANSION` ICP) whose delivering feature has\nno draft.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** Do not rewrite edges or drafts that are already\n correct. Only add/correct where a benefit lacks a delivering feature, a new\n benefit appeared, or a draft is genuinely wrong.\n- **Never orphan a ref.** A benefit points at feature refs; those refs must have\n a draft (for new features) or a real registry entry (once code exists).\n The combined output validator checks benefit references against existing feature identities plus the proposed draft wrappers. Supply `existingFeatureRefs` from the actual existing definitions when using `validateCapabilityMapOutputSet` directly; never invent references to make validation pass.\n- **One capability, one ref.** When two benefits are delivered by the same\n capability, they share the feature ref — do not fork it.\n\n## Quality gate\n\nValidate the connected output with `validateCapabilityMapOutputSet`. It parses the output shape, joins existing feature references with proposed draft identities, checks the market snapshot, and calls `validateFeatureSpecificationDrafts` for duplicate identities and each draft's prose contract. The result reports issues from both destinations.\n\nA draft payload is ref-less; its wrapper still supplies the stable `featureRef` needed for these checks. Missing feature links are not exempt merely because runtime definitions have not been created. Market pain/gain/job references and positioning/threshold checks still apply; read `market-snapshot-validation` for their detailed meanings.\n\nValidation is not product review or evidence that the capability has been implemented. Inspect the proposed benefit links and draft intent together before accepting the proposal.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. Explicitly **out of scope here**:\n\n- **A real prioritization model.** The FIT/Kano step here is a *fit* sanity\n check, not a defended, weighted, capacity-fitted *prioritization* (RICE/WSJF\n and the like are later-phase — and FIT is not priority, see the scoring seam).\n The scoring seam stays pluggable — do NOT build or tune a scoring or\n build-order model in this playbook.\n- **Deep feature-spec drafts.** A draft here is a first-cut capability contract\n (purpose / roles / use-when). Rich operation inventories, interaction\n semantics, and UX are the bottom-up build phase's job, not the capability map.\n- **Requirement pain/gain traceability.** A requirement today cross-refs ICPs and\n jobs but NOT market pains/gains, so the \"this requirement delivers\n `gain-X`\" trace that would let capability mapping run benefit → requirement →\n feature *deterministically* is lossy (expressible only in prose). Whether the\n requirements family should gain a pain/gain edge is a filed depth-phase\n question — do NOT reshape the requirements contract here.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nTwo artifacts for this journey:\n\n1. The SAME **MarketSnapshot** at `specifications/src/market/index.ts`,\n with every benefit's `deliveredByFeatureRefs` edge wired to its delivering\n feature(s), passing the `market-snapshot-valid` gate.\n2. The **feature-drafts** at `specifications/src/feature-drafts/index.ts` —\n one spec-first `FeatureSpecificationDraft` per new delivering feature.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's capability map.\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\n- `market-add-feature-benefit` — author/adjust the benefit\n claims and wire their `deliveredByFeatureRefs` edges.\n- `spec-feature-update` — author the spec-first\n `FeatureSpecificationDraft`(s) for the new delivering features.\n- `market-scoring-interpretation` — the FIT/Kano scoring\n interface: interpret the deterministic scorer's ranking to sanity-check the\n capability set (pluggable seam — consume it, do not re-implement it).\n- `market-snapshot-validation` — the full validation issue\n catalogue the quality gate enforces.\n",
|
|
54
|
+
"guidance": "# Capability Map — Benefit → Feature Pivot 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 be\n> iterated. The mapping order, the draft-authoring posture, and the\n> prioritization rubric below are deliberately explicit so they can be tuned\n> against real runs — treat them as a starting rubric, not a frozen contract.\n> The *analytical depth* of the capability work (quantified FIT / Kano scoring\n> precision, a real prioritization model) is intentionally shallow here and is\n> deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **capability architect**. This playbook is the **pivot**: it turns\nthe *value proposition* (what the product promises the market) into *product\ncapability* (the features that actually deliver those promises). Value-proposition\nsharpening already produced a **MarketSnapshot** whose benefits carry weighted\nrelieves/creates/advances edges and per-ICP Kano categories. Your one job is to\nanswer, for every benefit: **which feature delivers this, and does that feature\nexist yet?** — and then record the answer in two places:\n\n1. **The benefit → feature edge** — on the SAME MarketSnapshot, wire every\n benefit's `deliveredByFeatureRefs[]` to the feature(s) that deliver it. This\n edge is the authoritative capability-mapping link (`FeatureBenefitConfig.\n deliveredByFeatureRefs`, required and non-empty): a benefit that is not\n deliverable by any feature is not a real capability. (`market-add-feature-benefit`)\n2. **The spec-first feature drafts** — for every feature the map introduces that\n has **no code registry entry yet**, author a `FeatureSpecificationDraft`\n (purpose, businessRole, lifecycleRole, useWhen/avoidWhen, availabilityRole —\n all in prose). These are **spec-first**: you author them BEFORE the runtime\n `FeatureDefinition` exists; the factory injects the `ref` later from the\n runtime identifier, so a draft is authored ref-less (`Omit<…, 'ref'>`). Use the **Draft path** in `spec-feature-update`; its runtime workflow is for a later implementation task. The draft wrapper carries `featureRef`, while the nested prose payload remains ref-less.\n\nThen you **assess fit** for the resulting feature set with a FIT-scoring + Kano\nstep — kept pluggable and versioned (see \"The scoring seam\" below). This does not set build priority.\n\nThis is a **focused pivot pass**, distinct from value-proposition sharpening\n(which weighted the benefits) and from scope/roadmap (which slots the features\ninto releases). Where value-proposition made the benefits sharp, you make each\nbenefit *deliverable* and give every new capability its first spec.\n\n## Read state first — the two families you read, the two you write\n\nThis playbook is **idempotent** and a *refinement*: a MarketSnapshot must\nalready exist (the `artifact_exists` precondition enforces it). Before mapping\nanything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it.\n2. Read the existing **MarketSnapshot** (the benefits and their weighting),\n the **requirements** (`requirements` family — the functional/non-functional\n requirements the features must satisfy), and the **VisionSnapshot**\n (`vision-brief` — the differentiation anchor). You map capability against the\n real market intent, the real requirements, and the real differentiation — not\n from scratch.\n\n\nYou **read** `market-snapshot` + `requirements` + `vision-brief`; you **write**\nthe refined `market-snapshot` (edge wired) and the `feature-drafts` family (the\nnew drafts).\n\n## The mapping loop (benefit by benefit)\n\nFor each benefit in the snapshot:\n\n1. **Identify the delivering feature(s).** Ask what capability the product must\n have for this benefit's claim to be true. Prefer *one clear feature per\n benefit*; a benefit may legitimately need more than one, and one feature may\n deliver several benefits.\n2. **Reuse before you create.** If a delivering feature already appears on\n another benefit's `deliveredByFeatureRefs`, or already has a draft from an\n earlier run, **reuse that same feature ref** — never mint a second ref for the\n same capability. Reusing refs is what keeps the map coherent and lets the\n downstream scope/roadmap playbook slot each feature exactly once.\n3. **Wire the edge.** Add the feature ref(s) to the benefit's\n `deliveredByFeatureRefs[]`. Every benefit must end with a non-empty edge —\n the gate fails a benefit with an empty `deliveredByFeatureRefs` as\n `EMPTY_BENEFIT_DELIVERED_BY` (ERROR).\n4. **Draft the new feature (spec-first).** If the feature is new (no code\n registry entry, no prior draft), author its `FeatureSpecificationDraft` into\n the `feature-drafts` family. A draft is the **prose subset** of a feature\n spec: a business-language `purpose`, its `businessRole` / optional\n `lifecycleRole`, `useWhen` / `avoidWhen`, optional `businessConstraints`, and\n the `availabilityRole` (how the feature gates / packages). **Author ONLY these\n prose fields.** Do NOT author a `ref` — the factory injects it later from the\n runtime feature identifier, which is why a draft is authored ref-less. Do NOT\n wire `codeHandling` (it links a spec back to a runtime enum member +\n collection entry that does not exist yet at this phase) — the code-handling\n provenance is added when the feature is actually built, not now.\n Use the **Draft path** in `spec-feature-update`, including its wrapper and export contract. Do not run its runtime-enum, definition, policy or profile steps. Keep this a capability contract, not an implementation.\n5. **Trace to requirements + vision.** A feature only earns its place if it\n delivers a benefit that traces to the vision's differentiation AND satisfies\n real requirements. When a benefit's delivering feature has no requirement\n behind it, that is a signal to either add the requirement upstream or drop the\n claim — not to invent a feature the product does not need.\n\n## The scoring seam — FIT + Kano, kept PLUGGABLE and VERSIONED\n\nAssess the mapped capability set with a **FIT-scoring + Kano** step, and let that\nassessment inform how the capabilities get prioritized.\n\n**FIT is a fit signal, NOT a priority ranking — do not conflate them.**\n`computeFeatureFitScoreForICP` answers one narrow question: *how well does this\nfeature serve this ICP* on a deterministic 0–100 scale (edge `degree` × the ICP's\nown edge weight). It deliberately does NOT answer \"which feature do we build\nfirst\" — that is prioritization, a separate, deferred concern. Combine the FIT\nscore with the per-ICP Kano category (`THRESHOLD` = table-stakes, `PERFORMANCE` =\nmore-is-better, `DELIGHTER` = upside) to read *table-stakes vs. upside per\nsegment* — a fit judgement, not a build-order. Bending the FIT score into a\nbuild-order ranking yields wrong answers (this is the locked FIT-vs-priority\nvocabulary the `market-scoring-interpretation` skill enforces).\n\n**This step is a pluggable, versioned interface — bind to it, never embed it.**\nThe scoring / prioritization methodology is expected to change substantially in a\nlater phase, so this playbook references the scoring *interface* (via the\n`market-scoring-interpretation` skill) and consumes its output; it does **not**\nre-implement the scoring math and does **not** hard-couple to any specific scoring\nfunction (`computeFeatureFitScoreForICP` today, a different scorer tomorrow). You do\nnot run the scorer and must not estimate its output: the per-ICP FIT scores are\ncomputed for you and arrive in the declared `market_fit_scores` context section of your brief, beside each\nbenefit's authored Kano category. Read them there and use them to sanity-check the\ncapability set — a `0` carrying a stated reason is structural (an anti-target, or no\nbenefit covering that ICP), not a measurement of poor fit. If\nyou find yourself hand-writing a scoring formula, tuning weights to hit a target\nresult, or building an actual build-order prioritization model, **stop** — that is\nthe depth phase's job, and hard-coding it here would break the pluggability\ncontract (OQ-6).\n\nAt scaffold depth this is a *fit sanity check on the capability set*, not a\ndefended prioritization. The headline gap it surfaces: a table-stakes capability\n(a `THRESHOLD` benefit for a `CORE`/`EXPANSION` ICP) whose delivering feature has\nno draft.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** Do not rewrite edges or drafts that are already\n correct. Only add/correct where a benefit lacks a delivering feature, a new\n benefit appeared, or a draft is genuinely wrong.\n- **Never orphan a ref.** A benefit points at feature refs; those refs must have\n a draft (for new features) or a real registry entry (once code exists).\n The combined output validator checks benefit references against existing feature identities plus the proposed draft wrappers. Supply `existingFeatureRefs` from the actual existing definitions when using `validateCapabilityMapOutputSet` directly; never invent references to make validation pass.\n- **One capability, one ref.** When two benefits are delivered by the same\n capability, they share the feature ref — do not fork it.\n\n## Quality gate\n\nValidate the connected output with `validateCapabilityMapOutputSet`. It parses the output shape, joins existing feature references with proposed draft identities, checks the market snapshot, and calls `validateFeatureSpecificationDrafts` for duplicate identities and each draft's prose contract. The result reports issues from both destinations.\n\nA draft payload is ref-less; its wrapper still supplies the stable `featureRef` needed for these checks. Missing feature links are not exempt merely because runtime definitions have not been created. Market pain/gain/job references and positioning/threshold checks still apply; read `market-snapshot-validation` for their detailed meanings.\n\nValidation is not product review or evidence that the capability has been implemented. Inspect the proposed benefit links and draft intent together before accepting the proposal.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. Explicitly **out of scope here**:\n\n- **A real prioritization model.** The FIT/Kano step here is a *fit* sanity\n check, not a defended, weighted, capacity-fitted *prioritization* (RICE/WSJF\n and the like are later-phase — and FIT is not priority, see the scoring seam).\n The scoring seam stays pluggable — do NOT build or tune a scoring or\n build-order model in this playbook.\n- **Deep feature-spec drafts.** A draft here is a first-cut capability contract\n (purpose / roles / use-when). Rich operation inventories and UX are the\n bottom-up build phase's job, not the capability map. The business verbs a\n capability implies (accept, issue, close) are NOT deferred: the domain plan\n declares them as lifecycles, so state them where a capability rests on them.\n- **Requirement gain traceability.** A requirement cross-refs ICPs, jobs and the\n market PAINS it relieves (`painRefs`), but not the gains it delivers, so a\n \"this requirement delivers `gain-X`\" trace is expressible only in prose. Use\n `painRefs` where a capability answers a pain; do NOT reshape the requirements\n contract here to add a gain edge.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth.\n\n## What you emit\n\nTwo artifacts for this journey:\n\n1. The SAME **MarketSnapshot** at `specifications/src/market/index.ts`,\n with every benefit's `deliveredByFeatureRefs` edge wired to its delivering\n feature(s), passing the `market-snapshot-valid` gate.\n2. The **feature-drafts** at `specifications/src/feature-drafts/index.ts` —\n one spec-first `FeatureSpecificationDraft` per new delivering feature.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's capability map.\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\n- `market-add-feature-benefit` — author/adjust the benefit\n claims and wire their `deliveredByFeatureRefs` edges.\n- `spec-feature-update` — author the spec-first\n `FeatureSpecificationDraft`(s) for the new delivering features.\n- `market-scoring-interpretation` — the FIT/Kano scoring\n interface: interpret the deterministic scorer's ranking to sanity-check the\n capability set (pluggable seam — consume it, do not re-implement it).\n- `market-snapshot-validation` — the full validation issue\n catalogue the quality gate enforces.\n",
|
|
55
55
|
"skillRefs": [
|
|
56
56
|
"market-add-feature-benefit",
|
|
57
57
|
"market-scoring-interpretation",
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.expert-personas",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.2.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
5
|
"intent": "Staff every expert panel the catalog convenes: derive and accept an application-specific charter for each framework expert role that a deliberated playbook (`method.deliberation`) or a companion generation step (the logo panel) seats, grounded in the application's own vision, market, requirements, business model and brand. Idempotent: a role whose charter is committed is left alone (a human-edited charter is never overwritten), and a role whose shaping inputs have not landed yet is REPORTED as waiting rather than failing the run. Before this step existed the panel's staffing was not a journey step at all — every deliberated playbook failed closed at bind time on an application whose charters nobody had curled in by hand (#572).",
|
|
6
6
|
"preconditions": [
|
|
@@ -23,9 +23,23 @@
|
|
|
23
23
|
},
|
|
24
24
|
{
|
|
25
25
|
"family": "market-snapshot"
|
|
26
|
+
},
|
|
27
|
+
{
|
|
28
|
+
"family": "requirements"
|
|
29
|
+
},
|
|
30
|
+
{
|
|
31
|
+
"family": "business-model"
|
|
32
|
+
},
|
|
33
|
+
{
|
|
34
|
+
"family": "brand-brief"
|
|
35
|
+
}
|
|
36
|
+
],
|
|
37
|
+
"outputs": [
|
|
38
|
+
{
|
|
39
|
+
"family": "expert-personas",
|
|
40
|
+
"description": "One accepted charter per expert role a convened panel seats (written by the companion's expert-persona accept as a charter module per role plus the personas aggregator, never by the generic landing renderer). A role whose shaping inputs have not landed is reported as waiting and staffed by a later run."
|
|
26
41
|
}
|
|
27
42
|
],
|
|
28
|
-
"outputs": [],
|
|
29
43
|
"stepOutputs": [],
|
|
30
44
|
"method": {
|
|
31
45
|
"guidance": "# Expert personas — staff the panels the catalog convenes\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## What this step does\n\nSeveral steps of the creation journey are DECIDED BY A PANEL rather than by a single generation:\n`bottom_up.placement-plan` convenes an information architect and a design-system guardian, the logo\ngeneration step convenes an art director, a brand strategist and a design-system guardian. A panel is\nbuilt from **expert-persona charters** — one committed charter per framework expert role, derived from\nthis application's own vision, market, requirements, business model and brand, so a reviewer speaks\nfor THIS product rather than for a generic one.\n\nThis step derives and accepts those charters. It is runner-owned: no prompt is composed here. For every\nrole the catalog convenes (read off every playbook's `method.deliberation` and off the generation\nsteps' own panels), it runs the companion's derive → accept flow — a DRAFT, a CRITIQUE by a dedicated\ncritic, and a FINALIZE pass when the critique asks for one — then promotes the proposal into\n`specifications/src/personas/<role>.charter.generated.ts`, regenerates the aggregator and wires the\n`expertPersonaCharters` companion-exports slot.\n\n## What it will not do\n\n- **Overwrite a human-edited charter.** A committed charter carrying an `authored` block is never\n replaced; the accept step refuses and the run reports it.\n- **Re-derive a committed charter.** A role that already has a committed charter is left alone; ask for a\n re-derivation explicitly through the companion's `expert-personas/derive` route if the application's\n definition moved enough to warrant one.\n- **Fail on a role whose inputs are not landed.** A role needing the brand brief on an application with\n no brand yet is REPORTED as waiting, with the families it waits on. The step re-runs when they land.\n\n## Cost, so it is scheduled knowingly\n\nA derivation is an agentic three-pass protocol over the application's own artifacts: measured at about\n200 seconds per role on a real application. Five roles is a quarter of an hour. Submit the run detached.\n\n## What you read\n\nThe current journey state this run is given, to see which families have landed and\ntherefore which roles are derivable now.\n\n## Verification\n\n- `specifications/src/personas/` holds one `*.charter.generated.ts` per role the run reports as derived,\n and `index.ts` lists every one of them.\n- `companion-exports.ts` wires `expertPersonaCharters` onto the aggregator.\n- The eligibility board no longer reports `PANEL_UNSTAFFED` for `bottom_up.placement-plan`.\n",
|
|
@@ -45,8 +45,11 @@ the nested prose payload stays ref-less.
|
|
|
45
45
|
it; do not fork it.
|
|
46
46
|
- **Name the requirements each draft serves**, in its purpose or business-role prose, so the roadmap
|
|
47
47
|
and the build decomposition can trace a capability back to what asked for it.
|
|
48
|
-
- **Stay at scaffold depth.** A draft is a first-cut capability contract.
|
|
49
|
-
|
|
48
|
+
- **Stay at scaffold depth.** A draft is a first-cut capability contract. Screens and the
|
|
49
|
+
operations that implement it are the bottom-up build phase's work. But say what the capability
|
|
50
|
+
DOES in the business's verbs ("a sent quote can be accepted, and accepting it creates a job"):
|
|
51
|
+
the domain plan turns those verbs into lifecycles, and a draft that names none leaves it nothing
|
|
52
|
+
to read.
|
|
50
53
|
|
|
51
54
|
## Refine, don't re-author
|
|
52
55
|
|
|
@@ -37,7 +37,7 @@
|
|
|
37
37
|
],
|
|
38
38
|
"stepOutputs": [],
|
|
39
39
|
"method": {
|
|
40
|
-
"guidance": "# Feature Drafts — Requirements → Capability Method\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## What this playbook does\n\nYou are the **capability architect** for an application that has **no market**: an internal tool,\nfor example, built for a team rather than sold to customers. Your one job is to turn the accepted\n**requirements** into the product **capabilities** that deliver them, and to record each capability as\na spec-first **`FeatureSpecificationDraft`** in the `feature-drafts` family.\n\nThere are no market benefits, ICPs or pricing to map from, and none is owed: do not invent a market,\na customer segment or a competitive position. The requirements say what the application must do and\nfor whom inside the organization; the vision says why it exists. Those two are your whole input.\n\n## Read state first\n\n- **Requirements** (functional and non-functional): what the application must do. Every capability\n you draft must serve at least one requirement, and every functional requirement should be served by\n at least one capability. A requirement no capability serves is either a gap to draft or a\n requirement to question, never a silent omission.\n- **Vision**: the problem, the mission and the constraints. Use it to name capabilities in the\n application's own words and to keep them inside its stated scope.\n- **Your prior feature drafts**, when present. Refine them; do not re-author (below).\n\n## Drafting each capability\n\nFor every capability, author a draft with the **Draft path** of `spec-feature-update`: its purpose,\nbusiness role, lifecycle role, when to use it and when not to, and its availability role, all in\nprose. Drafts are **spec-first and ref-less**: you author them before the runtime `FeatureDefinition`\nexists, and the factory injects the `ref` later. The draft wrapper carries the stable `featureRef`;\nthe nested prose payload stays ref-less.\n\n- **One capability, one draft.** When two requirements are served by the same capability, they share\n it; do not fork it.\n- **Name the requirements each draft serves**, in its purpose or business-role prose, so the roadmap\n and the build decomposition can trace a capability back to what asked for it.\n- **Stay at scaffold depth.** A draft is a first-cut capability contract.
|
|
40
|
+
"guidance": "# Feature Drafts — Requirements → Capability Method\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## What this playbook does\n\nYou are the **capability architect** for an application that has **no market**: an internal tool,\nfor example, built for a team rather than sold to customers. Your one job is to turn the accepted\n**requirements** into the product **capabilities** that deliver them, and to record each capability as\na spec-first **`FeatureSpecificationDraft`** in the `feature-drafts` family.\n\nThere are no market benefits, ICPs or pricing to map from, and none is owed: do not invent a market,\na customer segment or a competitive position. The requirements say what the application must do and\nfor whom inside the organization; the vision says why it exists. Those two are your whole input.\n\n## Read state first\n\n- **Requirements** (functional and non-functional): what the application must do. Every capability\n you draft must serve at least one requirement, and every functional requirement should be served by\n at least one capability. A requirement no capability serves is either a gap to draft or a\n requirement to question, never a silent omission.\n- **Vision**: the problem, the mission and the constraints. Use it to name capabilities in the\n application's own words and to keep them inside its stated scope.\n- **Your prior feature drafts**, when present. Refine them; do not re-author (below).\n\n## Drafting each capability\n\nFor every capability, author a draft with the **Draft path** of `spec-feature-update`: its purpose,\nbusiness role, lifecycle role, when to use it and when not to, and its availability role, all in\nprose. Drafts are **spec-first and ref-less**: you author them before the runtime `FeatureDefinition`\nexists, and the factory injects the `ref` later. The draft wrapper carries the stable `featureRef`;\nthe nested prose payload stays ref-less.\n\n- **One capability, one draft.** When two requirements are served by the same capability, they share\n it; do not fork it.\n- **Name the requirements each draft serves**, in its purpose or business-role prose, so the roadmap\n and the build decomposition can trace a capability back to what asked for it.\n- **Stay at scaffold depth.** A draft is a first-cut capability contract. Screens and the\n operations that implement it are the bottom-up build phase's work. But say what the capability\n DOES in the business's verbs (\"a sent quote can be accepted, and accepting it creates a job\"):\n the domain plan turns those verbs into lifecycles, and a draft that names none leaves it nothing\n to read.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** Do not rewrite drafts that are already correct.\n- **Keep refs stable.** A draft's `featureRef` is named by the roadmap and by build tasks; renaming it\n orphans them.\n- Add a draft where a requirement gained a capability, correct one that is genuinely wrong, and\n remove one only when no requirement calls for it any more.\n\n## What you emit\n\nThe **feature-drafts** at `specifications/src/feature-drafts/index.ts`: one `FeatureSpecificationDraft`\nper capability the requirements call for, passing `validateFeatureSpecificationDrafts`.\n\nThe creator reviews the result (approval posture `approve_result`) before it is accepted.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an authoring\ncontract a later coding agent can open. This step has no tools and does not open them; what reaches\nyou is this method, your declared inputs, and the brief's own sections.\n\n- `spec-feature-update`: author the spec-first `FeatureSpecificationDraft`s (the Draft path).\n",
|
|
41
41
|
"skillRefs": [
|
|
42
42
|
"spec-feature-update"
|
|
43
43
|
],
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"aggregationPolicyRef":"application-creation:aggregation/worst-market-analysis-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","criterionVersion":
|
|
1
|
+
{"aggregationPolicyRef":"application-creation:aggregation/worst-market-analysis-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":2}],"instruction":"Assess whether the validated market graph is meaningfully grounded in accepted vision and sealed research evidence, distinguishes facts from hypotheses, and is coherent enough for current-horizon requirements and capability work. Then check the category against what the creator stated, when it is in your evidence: it keeps every workflow stage they named, puts nothing they excluded at its centre, and a category naming a different kind of product from theirs carries a category note starting \"Reframe:\". A dropped stage, a centred exclusion, or an unmarked reframe is a GAP. Do not reward exhaustive taxonomy when the targeting or evidence basis is weak.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The graph is usable but material targeting or evidence uncertainty is explicitly unresolved.","GAP":"The market graph materially contradicts the vision, lacks a usable target, presents unsupported claims as truth, or reframes the product the creator stated without marking it.","INDETERMINATE":"Accepted vision, research evidence or candidate output is absent, stale or insufficient.","PASS":"The market graph is valid, evidence-aware and coherent with the accepted vision."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/market-analysis","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.market-snapshot-produce"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
|
|
@@ -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-market-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/market-evidence-and-vision-coherence"],"requirementRef":"application-creation:authority-requirement/market-analysis-result","requirementVersion":1,"riskClassRef":"application-creation:risk/market-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/market-analysis","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/market-analysis-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/market-analysis","policyVersion":1},"decisionPointRef":"application-creation:decision-point/market-analysis-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/market-analysis-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/market-analysis","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":
|
|
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-market-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/market-evidence-and-vision-coherence"],"requirementRef":"application-creation:authority-requirement/market-analysis-result","requirementVersion":1,"riskClassRef":"application-creation:risk/market-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/market-analysis","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/market-analysis-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/market-analysis","policyVersion":1},"decisionPointRef":"application-creation:decision-point/market-analysis-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/market-analysis-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/market-analysis","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":2}],"hardFloorRefs":["application-creation:hard-floor/market-snapshot-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/market-definition-change","triggerRefs":["application-creation:trigger/market-snapshot-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-market-analysis-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/market-evidence-and-vision-coherence"],"hardFloorRef":"application-creation:hard-floor/market-snapshot-valid"}],"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/market-analysis-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/market-analysis","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-market-analysis-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":2}],"instruction":"Assess whether the validated market graph is meaningfully grounded in accepted vision and sealed research evidence, distinguishes facts from hypotheses, and is coherent enough for current-horizon requirements and capability work. Then check the category against what the creator stated, when it is in your evidence: it keeps every workflow stage they named, puts nothing they excluded at its centre, and a category naming a different kind of product from theirs carries a category note starting \"Reframe:\". A dropped stage, a centred exclusion, or an unmarked reframe is a GAP. Do not reward exhaustive taxonomy when the targeting or evidence basis is weak.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The graph is usable but material targeting or evidence uncertainty is explicitly unresolved.","GAP":"The market graph materially contradicts the vision, lacks a usable target, presents unsupported claims as truth, or reframes the product the creator stated without marking it.","INDETERMINATE":"Accepted vision, research evidence or candidate output is absent, stale or insufficient.","PASS":"The market graph is valid, evidence-aware and coherent with the accepted vision."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/market-analysis","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.market-snapshot-produce"},"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/market-analysis","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/exact-market-input-and-candidate","criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":2,"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":2,"schemaVersion":1,"subjectRef":"application-creation:definition-set/accepted-vision-research-and-market-candidate"}],"schemaVersion":1}
|
|
@@ -160,6 +160,32 @@ So:
|
|
|
160
160
|
Omit `authoredMetadata` only where the content is so self-evident that provenance
|
|
161
161
|
would be noise. A competitor's price is never that.
|
|
162
162
|
|
|
163
|
+
## The creator's framing binds the category
|
|
164
|
+
|
|
165
|
+
The creator has already said what the product is. Their answers arrive in
|
|
166
|
+
the declared `creator_stated_facts` context section of your brief: the one-liner, the workflow the product
|
|
167
|
+
carries (`core-workflow`), who uses it (`user-groups`) and what is left out
|
|
168
|
+
(`scope-boundary`). Given identical answers, two earlier runs chose two different
|
|
169
|
+
products: one a customer-workflow CRM that left invoicing to other tools, the
|
|
170
|
+
other trade-workflow software with invoicing at its centre and no customer
|
|
171
|
+
follow-up. That choice was never the market step's to make.
|
|
172
|
+
|
|
173
|
+
- **Every stage the creator named stays in the product.** A category under which
|
|
174
|
+
a stated stage disappears (follow-up, say) is the wrong category, not a sharper one.
|
|
175
|
+
- **Nothing the creator left out becomes central.** A category that puts an
|
|
176
|
+
excluded capability (invoicing, say) at its heart contradicts the scope
|
|
177
|
+
boundary. Pick another.
|
|
178
|
+
- **A reframe is MARKED, never silent.** You may name the category in better
|
|
179
|
+
market language than the creator's ("trade-operations CRM" for "a CRM for
|
|
180
|
+
building firms"), as long as the workflow and the boundary still hold. When
|
|
181
|
+
your category's NAME differs from the kind of product the creator named, add
|
|
182
|
+
a `category.notes[]` entry that starts with `Reframe:`. It quotes the creator's
|
|
183
|
+
own framing, names yours, and says why. That note is how the creator sees the
|
|
184
|
+
decision and overturns it. Never list the creator's own framing among
|
|
185
|
+
`rejectedCategories`.
|
|
186
|
+
- When the creator gave no workflow or boundary, frame from the one-liner and the
|
|
187
|
+
problem, and say in the category notes that the shape was inferred.
|
|
188
|
+
|
|
163
189
|
## Research posture (scaffold depth)
|
|
164
190
|
|
|
165
191
|
Ground each slice in evidence, not invention. At this scaffold depth the
|
|
@@ -36,7 +36,7 @@
|
|
|
36
36
|
],
|
|
37
37
|
"stepOutputs": [],
|
|
38
38
|
"method": {
|
|
39
|
-
"guidance": "# Market Analysis — Produce 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 authoring order, research posture, and the \"produce vs.\n> refine\" rules below are deliberately explicit so they can be tuned against\n> real runs — treat them as a starting rubric, not a frozen contract. The\n> *analytical depth* of the market work (research rigor, competitive\n> teardown, quantified FIT/Kano scoring) is intentionally shallow here and is\n> deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **market analyst**. Your one job is to produce — or refine an\nexisting — **MarketSnapshot** for this product: the single artifact that\ndeclares *who the product is for*, *what they are trying to get done*, and\n*how the product is positioned* to them. You reason top-down from the\nproduct idea (there is no code yet in this phase); you do not model the\ndomain, author resources, or write features — later playbooks consume your\nsnapshot to do that.\n\n## The shape you return is FLAT, not nested\n\nRead this before the slice list below, because the slices read like a hierarchy and the object is\nnot one.\n\nA MarketSnapshot is **~16 sibling top-level collections** — `category`, `icps`, `personas`, `jobs`,\n`pains`, `gains`, `tonesOfVoice`, `benefits`, `positionings`, `channels`, `alternatives`,\n`triggers`, `buyingJourneys`, `proofs`, `objections`, `messageTemplates` — and entities point at\neach other with flat **ref strings** (`jobRef`, `painRef`, `gainRef`, `personaRef`, `alternativeRef`,\n…). An ICP does not CONTAIN its jobs; it names them:\n\n```\njobs: [ { ref: 'job-close-the-week', statement: '…' } ] // the job itself, top level\nicps: [ { ref: 'icp-small-team',\n jobs: [ { jobRef: 'job-close-the-week', importance: … } ] } ] // the ICP's REFERENCE to it\n```\n\n⚠ **Measured on this playbook, 2026-08-29.** A first attempt returned 41,098 characters that were\nrejected wholesale: it had nested `personas`, `benefits`, `positionings`, `channels`, `alternatives`,\n`triggers`, `proofs` and `objections` INSIDE `icps[0]`, left every top-level collection empty, and\nwrote whole job objects where `{ jobRef, importance }` belongs. The retry recovered it, but a full\ngeneration was spent discovering the shape. The slice ordering below is a THINKING order — what to\nwork out first — never the structure of the answer.\n\nA MarketSnapshot is assembled from these slices, each owned by a dedicated\n`market_*` app-knowledge skill. Those skills are named here so you know which\nauthoring contract each slice belongs to, and so a later CODING agent can open\nthe right one — you cannot: this step has no tools, and sixteen skill bodies do\nnot fit in one brief. Everything you need to author the snapshot is in THIS\nmethod and your declared inputs; where a detail is genuinely only in a skill,\nsay so on what you author rather than inventing it. You author them in\ndependency order because later slices reference earlier refs:\n\n1. **Category** — the one market category the product competes in, plus the\n rejected adjacent categories. (`market-category`)\n2. **ICPs** — the Ideal Customer Profiles: the firmographic / demographic\n segments the product is sold to. (`market-icp`)\n3. **Personas** — the human roles inside each ICP, including buying-group\n members. Every ICP needs at least one persona. (`market-persona`)\n4. **Jobs / Pains / Gains** — the Strategyzer customer-profile triplet for\n the personas: what they are trying to do, what blocks them, what a win\n looks like. (`market-jobs-pains-gains`)\n5. **Tones of voice** — the named brand voices the product speaks in.\n (`market-tone-of-voice`)\n6. **Benefits** — the outcome claims the product delivers, weighted against\n the pains/gains they relieve/create. (`market-add-feature-benefit`)\n7. **Positionings** — the per-ICP marketing-truth promise. Author one per\n ICP that the product actually targets. (`market-positioning-authoring`)\n8. **Reach surfaces** — the go-to-market context: channels, competing\n alternatives, buying triggers + per-ICP buying journeys, proofs, and the\n objections proofs answer. (`market-channels`, `market-alternatives`,\n `market-triggers-and-journey`, `market-proof-and-objection`)\n9. **Message templates** — reusable prompt templates that render from the\n snapshot above. Author last; they reference the earlier slices.\n (`market-message-templates-authoring`)\n\nAuthor only the slices the product's stage warrants — a first pass may stop\nafter positionings and leave the phase-3/4 reach surfaces empty (they\ndefault to `[]`). A snapshot with a category, at least one ICP, its\npersonas, the jobs/pains/gains triplet, and at least one positioning is a\nlegitimate v1; the reach surfaces and message templates are additive.\n\n## Where the snapshot lives\n\nThe MarketSnapshot for this journey is placed under\n`specifications/src/market/index.ts`. That is the artifact this\nplaybook owns and the rest of the top-down phase reads. When the product's\ndefinition later stabilises, the snapshot is what seeds the durable market\nspecification under `./specifications/` — but at this phase it is a journey\nartifact, not yet app source.\n\n## Produce vs. refine — read state first\n\nThis playbook is **idempotent** on the journey's market artifact. Before\nauthoring anything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief; do not re-derive it. That state tells you which\n scope the snapshot must be complete *for*.\n2. Check whether a MarketSnapshot already exists by reading the artifact at the\n `market-snapshot` family's landing path, `specifications/src/market/index.ts`.\n The path belongs to the FAMILY, not to this playbook — every playbook that\n writes a market snapshot writes that same file. Its presence or absence\n selects the mode below.\n\n- **No snapshot yet** — produce a fresh one, authoring the slices in the\n order above.\n- **A snapshot exists** — *refine* it: read every slice, keep what still\n holds, and only add/correct the slices the current steering notes or new\n research call for. Never silently discard authored refs — a downstream\n positioning or benefit may depend on an ICP or persona ref, and dropping\n it orphans them (the validator will catch this, but honest refinement\n should not create the orphan in the first place).\n\n## Provenance — record where a claim came from\n\nYou are given the evidence a sibling research step gathered, with the URLs it read.\nWhere an entity's content rests on one of those sources, RECORD that URL on the entity\n— in the schema's own provenance fields, which exist for exactly this:\n\n| field | for |\n|---|---|\n| `pains[].evidence[]`, `gains[].evidence[]`, `benefits[].evidence` | what a source shows about the pain, gain or claim |\n| `proofs[].evidenceUrl`, `proofs[].attribution.url` | the page a proof points at |\n| `alternatives[].notes[]`, `category.notes[]`, `icps[].notes[]` | where the framing came from |\n\n⚠ An earlier revision of this section told you to use `authoredMetadata.notes` instead.\nThat was wrong, and the correction is recorded rather than quietly applied because the\nrun that exposed it did better than the instruction: handed the evidence, the model\nput 10 URLs into the typed `evidence`/`evidenceUrl` fields above and none into the\ngeneric metadata block it had been pointed at. Typed provenance is machine-readable\nand the generic block is prose; prefer the specific field every time one exists.\n\nThis is not bookkeeping. Measured on this playbook's first composite run\n(2026-08-29): the snapshot it produced carried **zero** source URLs and was, on that\ndimension, indistinguishable from the single-call version it replaced — the judge\ncalled the older one's evidence \"self-referential statements such as 'The vision\nspecifies…'\". A sourced claim and an invented one must not look the same in what you\nland, because nobody downstream can tell them apart afterwards.\n\nSo:\n\n- An entity grounded in a fetched page carries its URL in `authoredMetadata.notes`.\n- An entity you INFERRED carries that word, and `confidence` set honestly — `LOW` for\n a hypothesis, not `HIGH` because it reads well.\n- An entity the evidence did not cover is still authorable, and says so.\n\nOmit `authoredMetadata` only where the content is so self-evident that provenance\nwould be noise. A competitor's price is never that.\n\n## Research posture (scaffold depth)\n\nGround each slice in evidence, not invention. At this scaffold depth the\nresearch is whatever the executing agent can gather about the product's\ncategory, competitors, and buyers; capture the *shape* faithfully (real\ncategory, real competing alternatives, plausible ICPs and personas) rather\nthan aspirational fiction. Where you are inferring rather than citing, say so\nin the slice's authored prose so a later, deeper research pass can tighten\nit. Do **not** build a research pipeline or block on external tooling here —\nricher web-research capability is a later-phase concern; this playbook\nconsumes whatever the agent already knows plus the creator's steering.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. It\nenforces the cross-slice invariants — orphan refs (a positioning naming a\nmissing ICP, a benefit naming a missing pain/gain), an ICP with no persona,\ninfluence cycles, duplicate edges, proofs without support, message-template\nplaceholder mismatches, and more. Duplicate or malformed refs and\n`ERROR`-severity issues are hard failures; the snapshot does not advance\nuntil they clear. `WARN`-severity issues (e.g. stale-authored, a missing\npositioning for a targeted ICP) do not block but should be resolved. Read\n`market-snapshot-validation` for the full issue catalogue and emit a clean\nsnapshot the first time.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. The following are explicitly **out of\nscope here** and are deepened in the methodology-depth phase, not now:\n\n- **Deep competitive teardown** — the reach surfaces capture *that* an\n alternative exists and *why* a buyer might pick it; a quantified,\n feature-by-feature competitor matrix is later-phase work.\n- **Quantified FIT / Kano scoring** — `market-scoring-interpretation` reads\n the deterministic FIT scorer; at scaffold depth you consume it to sanity-\n check benefit weighting, not to drive a precise prioritization model. The\n prioritization seam stays pluggable (see the capability-map playbook).\n- **Opportunity / TAM sizing and evidence depth** — jobs/pains/gains are\n authored as framing, not as a sized, sourced market model.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nA single MarketSnapshot at `specifications/src/market/index.ts`,\nassembled from the slices above via their `market_*` skills, passing the\n`market-snapshot-valid` gate. The creator reviews the result (approval posture\n`approve_result`) before it is accepted as the journey's market intent.\n\n## References\n\nThese are skill FOLDERS installed in the application, listed so each slice's\nauthoring contract has a name. This step has no tools and does not open them.\n\n- `market-authoring-overview` — the orchestrator for\n the whole market slice; read it first to see how the slices fit together.\n- `market-category` — author the singular market\n category.\n- `market-icp` — author the Ideal Customer Profiles.\n- `market-persona` — author the personas per ICP.\n- `market-jobs-pains-gains` — author the Strategyzer\n jobs/pains/gains triplet.\n- `market-tone-of-voice` — author the named brand\n voices.\n- `market-add-feature-benefit` — author the benefit\n claims and their pain/gain weighting.\n- `market-positioning-authoring` — author the per-ICP\n positioning promise.\n- `market-channels` — author the reach channels.\n- `market-alternatives` — author the competing\n alternatives.\n- `market-triggers-and-journey` — author buying\n triggers and per-ICP buying journeys.\n- `market-proof-and-objection` — author proofs and\n the objections they answer.\n- `market-message-templates-authoring` — author the\n reusable message templates (last).\n- `market-scoring-interpretation` — interpret the\n deterministic FIT scorer to sanity-check benefit weighting.\n- `market-snapshot-validation` — the full validation\n issue catalogue the quality gate enforces.\n",
|
|
39
|
+
"guidance": "# Market Analysis — Produce 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 authoring order, research posture, and the \"produce vs.\n> refine\" rules below are deliberately explicit so they can be tuned against\n> real runs — treat them as a starting rubric, not a frozen contract. The\n> *analytical depth* of the market work (research rigor, competitive\n> teardown, quantified FIT/Kano scoring) is intentionally shallow here and is\n> deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **market analyst**. Your one job is to produce — or refine an\nexisting — **MarketSnapshot** for this product: the single artifact that\ndeclares *who the product is for*, *what they are trying to get done*, and\n*how the product is positioned* to them. You reason top-down from the\nproduct idea (there is no code yet in this phase); you do not model the\ndomain, author resources, or write features — later playbooks consume your\nsnapshot to do that.\n\n## The shape you return is FLAT, not nested\n\nRead this before the slice list below, because the slices read like a hierarchy and the object is\nnot one.\n\nA MarketSnapshot is **~16 sibling top-level collections** — `category`, `icps`, `personas`, `jobs`,\n`pains`, `gains`, `tonesOfVoice`, `benefits`, `positionings`, `channels`, `alternatives`,\n`triggers`, `buyingJourneys`, `proofs`, `objections`, `messageTemplates` — and entities point at\neach other with flat **ref strings** (`jobRef`, `painRef`, `gainRef`, `personaRef`, `alternativeRef`,\n…). An ICP does not CONTAIN its jobs; it names them:\n\n```\njobs: [ { ref: 'job-close-the-week', statement: '…' } ] // the job itself, top level\nicps: [ { ref: 'icp-small-team',\n jobs: [ { jobRef: 'job-close-the-week', importance: … } ] } ] // the ICP's REFERENCE to it\n```\n\n⚠ **Measured on this playbook, 2026-08-29.** A first attempt returned 41,098 characters that were\nrejected wholesale: it had nested `personas`, `benefits`, `positionings`, `channels`, `alternatives`,\n`triggers`, `proofs` and `objections` INSIDE `icps[0]`, left every top-level collection empty, and\nwrote whole job objects where `{ jobRef, importance }` belongs. The retry recovered it, but a full\ngeneration was spent discovering the shape. The slice ordering below is a THINKING order — what to\nwork out first — never the structure of the answer.\n\nA MarketSnapshot is assembled from these slices, each owned by a dedicated\n`market_*` app-knowledge skill. Those skills are named here so you know which\nauthoring contract each slice belongs to, and so a later CODING agent can open\nthe right one — you cannot: this step has no tools, and sixteen skill bodies do\nnot fit in one brief. Everything you need to author the snapshot is in THIS\nmethod and your declared inputs; where a detail is genuinely only in a skill,\nsay so on what you author rather than inventing it. You author them in\ndependency order because later slices reference earlier refs:\n\n1. **Category** — the one market category the product competes in, plus the\n rejected adjacent categories. (`market-category`)\n2. **ICPs** — the Ideal Customer Profiles: the firmographic / demographic\n segments the product is sold to. (`market-icp`)\n3. **Personas** — the human roles inside each ICP, including buying-group\n members. Every ICP needs at least one persona. (`market-persona`)\n4. **Jobs / Pains / Gains** — the Strategyzer customer-profile triplet for\n the personas: what they are trying to do, what blocks them, what a win\n looks like. (`market-jobs-pains-gains`)\n5. **Tones of voice** — the named brand voices the product speaks in.\n (`market-tone-of-voice`)\n6. **Benefits** — the outcome claims the product delivers, weighted against\n the pains/gains they relieve/create. (`market-add-feature-benefit`)\n7. **Positionings** — the per-ICP marketing-truth promise. Author one per\n ICP that the product actually targets. (`market-positioning-authoring`)\n8. **Reach surfaces** — the go-to-market context: channels, competing\n alternatives, buying triggers + per-ICP buying journeys, proofs, and the\n objections proofs answer. (`market-channels`, `market-alternatives`,\n `market-triggers-and-journey`, `market-proof-and-objection`)\n9. **Message templates** — reusable prompt templates that render from the\n snapshot above. Author last; they reference the earlier slices.\n (`market-message-templates-authoring`)\n\nAuthor only the slices the product's stage warrants — a first pass may stop\nafter positionings and leave the phase-3/4 reach surfaces empty (they\ndefault to `[]`). A snapshot with a category, at least one ICP, its\npersonas, the jobs/pains/gains triplet, and at least one positioning is a\nlegitimate v1; the reach surfaces and message templates are additive.\n\n## Where the snapshot lives\n\nThe MarketSnapshot for this journey is placed under\n`specifications/src/market/index.ts`. That is the artifact this\nplaybook owns and the rest of the top-down phase reads. When the product's\ndefinition later stabilises, the snapshot is what seeds the durable market\nspecification under `./specifications/` — but at this phase it is a journey\nartifact, not yet app source.\n\n## Produce vs. refine — read state first\n\nThis playbook is **idempotent** on the journey's market artifact. Before\nauthoring anything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief; do not re-derive it. That state tells you which\n scope the snapshot must be complete *for*.\n2. Check whether a MarketSnapshot already exists by reading the artifact at the\n `market-snapshot` family's landing path, `specifications/src/market/index.ts`.\n The path belongs to the FAMILY, not to this playbook — every playbook that\n writes a market snapshot writes that same file. Its presence or absence\n selects the mode below.\n\n- **No snapshot yet** — produce a fresh one, authoring the slices in the\n order above.\n- **A snapshot exists** — *refine* it: read every slice, keep what still\n holds, and only add/correct the slices the current steering notes or new\n research call for. Never silently discard authored refs — a downstream\n positioning or benefit may depend on an ICP or persona ref, and dropping\n it orphans them (the validator will catch this, but honest refinement\n should not create the orphan in the first place).\n\n## Provenance — record where a claim came from\n\nYou are given the evidence a sibling research step gathered, with the URLs it read.\nWhere an entity's content rests on one of those sources, RECORD that URL on the entity\n— in the schema's own provenance fields, which exist for exactly this:\n\n| field | for |\n|---|---|\n| `pains[].evidence[]`, `gains[].evidence[]`, `benefits[].evidence` | what a source shows about the pain, gain or claim |\n| `proofs[].evidenceUrl`, `proofs[].attribution.url` | the page a proof points at |\n| `alternatives[].notes[]`, `category.notes[]`, `icps[].notes[]` | where the framing came from |\n\n⚠ An earlier revision of this section told you to use `authoredMetadata.notes` instead.\nThat was wrong, and the correction is recorded rather than quietly applied because the\nrun that exposed it did better than the instruction: handed the evidence, the model\nput 10 URLs into the typed `evidence`/`evidenceUrl` fields above and none into the\ngeneric metadata block it had been pointed at. Typed provenance is machine-readable\nand the generic block is prose; prefer the specific field every time one exists.\n\nThis is not bookkeeping. Measured on this playbook's first composite run\n(2026-08-29): the snapshot it produced carried **zero** source URLs and was, on that\ndimension, indistinguishable from the single-call version it replaced — the judge\ncalled the older one's evidence \"self-referential statements such as 'The vision\nspecifies…'\". A sourced claim and an invented one must not look the same in what you\nland, because nobody downstream can tell them apart afterwards.\n\nSo:\n\n- An entity grounded in a fetched page carries its URL in `authoredMetadata.notes`.\n- An entity you INFERRED carries that word, and `confidence` set honestly — `LOW` for\n a hypothesis, not `HIGH` because it reads well.\n- An entity the evidence did not cover is still authorable, and says so.\n\nOmit `authoredMetadata` only where the content is so self-evident that provenance\nwould be noise. A competitor's price is never that.\n\n## The creator's framing binds the category\n\nThe creator has already said what the product is. Their answers arrive in\nthe declared `creator_stated_facts` context section of your brief: the one-liner, the workflow the product\ncarries (`core-workflow`), who uses it (`user-groups`) and what is left out\n(`scope-boundary`). Given identical answers, two earlier runs chose two different\nproducts: one a customer-workflow CRM that left invoicing to other tools, the\nother trade-workflow software with invoicing at its centre and no customer\nfollow-up. That choice was never the market step's to make.\n\n- **Every stage the creator named stays in the product.** A category under which\n a stated stage disappears (follow-up, say) is the wrong category, not a sharper one.\n- **Nothing the creator left out becomes central.** A category that puts an\n excluded capability (invoicing, say) at its heart contradicts the scope\n boundary. Pick another.\n- **A reframe is MARKED, never silent.** You may name the category in better\n market language than the creator's (\"trade-operations CRM\" for \"a CRM for\n building firms\"), as long as the workflow and the boundary still hold. When\n your category's NAME differs from the kind of product the creator named, add\n a `category.notes[]` entry that starts with `Reframe:`. It quotes the creator's\n own framing, names yours, and says why. That note is how the creator sees the\n decision and overturns it. Never list the creator's own framing among\n `rejectedCategories`.\n- When the creator gave no workflow or boundary, frame from the one-liner and the\n problem, and say in the category notes that the shape was inferred.\n\n## Research posture (scaffold depth)\n\nGround each slice in evidence, not invention. At this scaffold depth the\nresearch is whatever the executing agent can gather about the product's\ncategory, competitors, and buyers; capture the *shape* faithfully (real\ncategory, real competing alternatives, plausible ICPs and personas) rather\nthan aspirational fiction. Where you are inferring rather than citing, say so\nin the slice's authored prose so a later, deeper research pass can tighten\nit. Do **not** build a research pipeline or block on external tooling here —\nricher web-research capability is a later-phase concern; this playbook\nconsumes whatever the agent already knows plus the creator's steering.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. It\nenforces the cross-slice invariants — orphan refs (a positioning naming a\nmissing ICP, a benefit naming a missing pain/gain), an ICP with no persona,\ninfluence cycles, duplicate edges, proofs without support, message-template\nplaceholder mismatches, and more. Duplicate or malformed refs and\n`ERROR`-severity issues are hard failures; the snapshot does not advance\nuntil they clear. `WARN`-severity issues (e.g. stale-authored, a missing\npositioning for a targeted ICP) do not block but should be resolved. Read\n`market-snapshot-validation` for the full issue catalogue and emit a clean\nsnapshot the first time.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. The following are explicitly **out of\nscope here** and are deepened in the methodology-depth phase, not now:\n\n- **Deep competitive teardown** — the reach surfaces capture *that* an\n alternative exists and *why* a buyer might pick it; a quantified,\n feature-by-feature competitor matrix is later-phase work.\n- **Quantified FIT / Kano scoring** — `market-scoring-interpretation` reads\n the deterministic FIT scorer; at scaffold depth you consume it to sanity-\n check benefit weighting, not to drive a precise prioritization model. The\n prioritization seam stays pluggable (see the capability-map playbook).\n- **Opportunity / TAM sizing and evidence depth** — jobs/pains/gains are\n authored as framing, not as a sized, sourced market model.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nA single MarketSnapshot at `specifications/src/market/index.ts`,\nassembled from the slices above via their `market_*` skills, passing the\n`market-snapshot-valid` gate. The creator reviews the result (approval posture\n`approve_result`) before it is accepted as the journey's market intent.\n\n## References\n\nThese are skill FOLDERS installed in the application, listed so each slice's\nauthoring contract has a name. This step has no tools and does not open them.\n\n- `market-authoring-overview` — the orchestrator for\n the whole market slice; read it first to see how the slices fit together.\n- `market-category` — author the singular market\n category.\n- `market-icp` — author the Ideal Customer Profiles.\n- `market-persona` — author the personas per ICP.\n- `market-jobs-pains-gains` — author the Strategyzer\n jobs/pains/gains triplet.\n- `market-tone-of-voice` — author the named brand\n voices.\n- `market-add-feature-benefit` — author the benefit\n claims and their pain/gain weighting.\n- `market-positioning-authoring` — author the per-ICP\n positioning promise.\n- `market-channels` — author the reach channels.\n- `market-alternatives` — author the competing\n alternatives.\n- `market-triggers-and-journey` — author buying\n triggers and per-ICP buying journeys.\n- `market-proof-and-objection` — author proofs and\n the objections they answer.\n- `market-message-templates-authoring` — author the\n reusable message templates (last).\n- `market-scoring-interpretation` — interpret the\n deterministic FIT scorer to sanity-check benefit weighting.\n- `market-snapshot-validation` — the full validation\n issue catalogue the quality gate enforces.\n",
|
|
40
40
|
"skillRefs": [
|
|
41
41
|
"market-authoring-overview",
|
|
42
42
|
"market-category",
|
|
@@ -55,7 +55,9 @@
|
|
|
55
55
|
"market-snapshot-validation"
|
|
56
56
|
],
|
|
57
57
|
"skillBodyRefs": [],
|
|
58
|
-
"contextSources": [
|
|
58
|
+
"contextSources": [
|
|
59
|
+
"creator_stated_facts"
|
|
60
|
+
],
|
|
59
61
|
"draftableDocumentDefinitionRefs": [],
|
|
60
62
|
"suspendsForClarification": false,
|
|
61
63
|
"briefAdequacyGate": false,
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"aggregationPolicyRef":"application-creation:aggregation/worst-top-down-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.name","brand-name-screening.candidate"],"criterionRef":"application-creation:criterion/brand-name-screening-standing","criterionVersion":
|
|
1
|
+
{"aggregationPolicyRef":"application-creation:aggregation/worst-top-down-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.name","brand-name-screening.candidate"],"criterionRef":"application-creation:criterion/brand-name-screening-standing","criterionVersion":3,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-standing","requirementVersion":1}],"instruction":"Determine where the product's NAME stands, reading the coherence report's brand-name findings first — they are computed, not judged. On a line that carries a brand, a missing brand-name screening (brand-name-screening-missing) or a brand name no screening covers (brand-name-not-screened), or a conflict nobody chose to keep (brand-name-conflict-unacknowledged), is a gap in the definition: the brand identity's name question cannot be answered, or the name was never checked. A name chosen with the screening incomplete, with no register read at all (brand-name-no-register-read), or kept despite a conflict is a deliberate, recorded decision that must be visible — in the risk register, as an entry derived from the brand-name-trademark-standing signal, and in the launch list as a brand name not cleared — not a failure. Fewer than three offerable proposals, a creator-listed name the screening does not carry, a screening that read no register for any name (brand-name-screening-read-nothing), or a place the application declares it operates in that the screening does not list (brand-name-operating-jurisdiction-not-screened), is a concern. A line with no brand (no brand-name finding and no definition-brand-brief-missing finding is reported for it) has nothing to assess; a line that carries a brand whose brief has not landed (definition-brand-brief-missing) is assessed by the definition-completeness criterion, never passed here as a line with no brand.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The brand name was chosen with the screening incomplete or kept despite a conflict and the risk register carries it, or the screening offers fewer than three proposals or misses a name the creator listed.","GAP":"On a line with a brand, no screening is on record or the brand name was never screened; or a name kept despite a conflict is recorded nowhere, the risk register included.","INDETERMINATE":"The coherence report is not in evidence, so the brand name's standing cannot be read.","PASS":"The line carries no brand, or the brand name is a screened candidate whose screening is complete and clear."}},{"assessesAspects":["market.benefit","feature-drafts.draft"],"criterionRef":"application-creation:criterion/capability-completeness","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1}],"instruction":"Determine whether every current-horizon market benefit is connected to at least one resolvable delivering feature. Treat an unwired benefit as a material gap; do not infer a connection from thematic similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All benefits are wired, but one or more connections are weak, indirect, or insufficiently explained.","GAP":"At least one current-horizon benefit has no resolvable delivering feature.","INDETERMINATE":"The accepted evidence cannot establish the benefit-to-feature wiring completely.","PASS":"Every current-horizon benefit has at least one resolvable delivering feature."}},{"criterionRef":"application-creation:criterion/compliance-presence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1}],"instruction":"Determine whether a product handling regulated or sensitive data declares at least one applicable compliance constraint. Do not invent regulation applicability; report indeterminate when the accepted evidence does not establish the data or sector posture.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A compliance constraint exists, but its applicability or coverage is weakly established.","GAP":"A regulated-data trigger is established and no applicable compliance constraint is declared.","INDETERMINATE":"The evidence cannot establish the regulated-data trigger or the applicable constraint posture.","PASS":"The evidence establishes either no regulated-data trigger or an applicable declared compliance constraint."}},{"criterionRef":"application-creation:criterion/definition-completeness","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/definition-completeness","requirementVersion":1}],"instruction":"Determine whether the definition holds every family the application's declared line carries, reading the coherence report's definition findings — they are computed, not judged. A business model (definition-business-model-missing) or a brand brief (definition-brand-brief-missing) the line carries that has not landed is a gap: the definition is not finished, whatever the other families say, and the finding names the step to run (or the interview to answer). A family the line declares not applicable is never reported and is not a gap. Do not infer a missing family from anything other than these findings.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Not used: a family the line carries is either on record or missing.","GAP":"The coherence report names a business model or a brand brief the declared line carries that has not landed.","INDETERMINATE":"The coherence report is not in evidence, so which families have landed cannot be read.","PASS":"The coherence report carries no definition-*-missing finding: every family the declared line carries has landed or is declared not applicable."}},{"assessesAspects":["market.icp","market.positioning"],"criterionRef":"application-creation:criterion/positioning-icp-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1}],"instruction":"Determine whether positioning pillars address the declared core ICPs without centring an anti-target segment. Preserve the authored ICP classifications and do not silently reclassify a segment.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Positioning is broadly coherent but under-serves a core ICP or approaches an anti-target boundary.","GAP":"Positioning ignores the core ICPs or explicitly centres an anti-target segment.","INDETERMINATE":"The accepted evidence cannot connect positioning pillars to the classified ICP set.","PASS":"Positioning addresses the core ICPs and does not centre an anti-target segment."}},{"assessesAspects":["requirements.functional","roadmap.phase"],"criterionRef":"application-creation:criterion/requirement-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is delivered by a roadmap phase or explicitly deferred in accepted roadmap intent. Do not treat absence as deliberate deferral.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but one or more deferrals are weakly justified or difficult to trace.","GAP":"At least one functional requirement is neither delivered nor explicitly deferred.","INDETERMINATE":"The accepted evidence cannot establish complete requirement-to-roadmap accounting.","PASS":"Every current-horizon functional requirement is delivered or explicitly deferred."}},{"assessesAspects":["vision.success-criterion","roadmap.phase"],"criterionRef":"application-creation:criterion/success-criterion-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon vision success criterion is delivered by at least one roadmap phase. Keep success criteria distinct from implementation tasks or generic aspirations.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All criteria are covered, but one or more delivery links are weak or overly indirect.","GAP":"At least one current-horizon success criterion is not delivered by any roadmap phase.","INDETERMINATE":"The accepted evidence cannot establish complete success-criterion-to-roadmap coverage.","PASS":"Every current-horizon success criterion is delivered by at least one roadmap phase."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/top-down-phase-gate","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.phase-gate"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
|
|
@@ -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/journey-phase-transition","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/capability-completeness","application-creation:evidence-requirement/compliance-presence","application-creation:evidence-requirement/positioning-icp-coherence","application-creation:evidence-requirement/requirement-coverage","application-creation:evidence-requirement/success-criterion-coverage"],"requirementRef":"application-creation:authority-requirement/top-down-to-bottom-up-transition","requirementVersion":1,"riskClassRef":"application-creation:risk/bootstrap-non-regulated-phase-transition","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/top-down-phase-gate","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/top-down-to-bottom-up-transition","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/top-down-phase-gate","policyVersion":1},"decisionPointRef":"application-creation:decision-point/top-down-phase-gate","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/top-down-phase-gate","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/top-down-phase-gate","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-standing","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/required-family-validity"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-transition","triggerRefs":["application-creation:trigger/top-down-definition-set-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-top-down-coherence-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/capability-completeness","application-creation:evidence-requirement/compliance-presence","application-creation:evidence-requirement/positioning-icp-coherence","application-creation:evidence-requirement/requirement-coverage","application-creation:evidence-requirement/success-criterion-coverage"],"hardFloorRef":"application-creation:hard-floor/required-family-validity"}],"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/top-down-phase-gate","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/top-down-phase-gate","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-top-down-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.name","brand-name-screening.candidate"],"criterionRef":"application-creation:criterion/brand-name-screening-standing","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-standing","requirementVersion":1}],"instruction":"Determine where the product's NAME stands, reading the coherence report's brand-name findings first — they are computed, not judged. On a line that carries a brand, a missing brand-name screening (brand-name-screening-missing) or a brand name no screening covers (brand-name-not-screened), or a conflict nobody chose to keep (brand-name-conflict-unacknowledged), is a gap in the definition: the brand identity's name question cannot be answered, or the name was never checked. A name chosen with the screening incomplete or kept despite a conflict is a deliberate, recorded decision that must be visible — in the risk register, as an entry derived from the brand-name-trademark-standing signal — not a failure. Fewer than three offerable proposals, or a creator-listed name the screening does not carry, is a concern. A line with no brand (no brand-name finding is reported for it) has nothing to assess.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The brand name was chosen with the screening incomplete or kept despite a conflict and the risk register carries it, or the screening offers fewer than three proposals or misses a name the creator listed.","GAP":"On a line with a brand, no screening is on record or the brand name was never screened; or a name kept despite a conflict is recorded nowhere, the risk register included.","INDETERMINATE":"The coherence report is not in evidence, so the brand name's standing cannot be read.","PASS":"The line carries no brand, or the brand name is a screened candidate whose screening is complete and clear."}},{"assessesAspects":["market.benefit","feature-drafts.draft"],"criterionRef":"application-creation:criterion/capability-completeness","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1}],"instruction":"Determine whether every current-horizon market benefit is connected to at least one resolvable delivering feature. Treat an unwired benefit as a material gap; do not infer a connection from thematic similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All benefits are wired, but one or more connections are weak, indirect, or insufficiently explained.","GAP":"At least one current-horizon benefit has no resolvable delivering feature.","INDETERMINATE":"The accepted evidence cannot establish the benefit-to-feature wiring completely.","PASS":"Every current-horizon benefit has at least one resolvable delivering feature."}},{"criterionRef":"application-creation:criterion/compliance-presence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1}],"instruction":"Determine whether a product handling regulated or sensitive data declares at least one applicable compliance constraint. Do not invent regulation applicability; report indeterminate when the accepted evidence does not establish the data or sector posture.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A compliance constraint exists, but its applicability or coverage is weakly established.","GAP":"A regulated-data trigger is established and no applicable compliance constraint is declared.","INDETERMINATE":"The evidence cannot establish the regulated-data trigger or the applicable constraint posture.","PASS":"The evidence establishes either no regulated-data trigger or an applicable declared compliance constraint."}},{"assessesAspects":["market.icp","market.positioning"],"criterionRef":"application-creation:criterion/positioning-icp-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1}],"instruction":"Determine whether positioning pillars address the declared core ICPs without centring an anti-target segment. Preserve the authored ICP classifications and do not silently reclassify a segment.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Positioning is broadly coherent but under-serves a core ICP or approaches an anti-target boundary.","GAP":"Positioning ignores the core ICPs or explicitly centres an anti-target segment.","INDETERMINATE":"The accepted evidence cannot connect positioning pillars to the classified ICP set.","PASS":"Positioning addresses the core ICPs and does not centre an anti-target segment."}},{"assessesAspects":["requirements.functional","roadmap.phase"],"criterionRef":"application-creation:criterion/requirement-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is delivered by a roadmap phase or explicitly deferred in accepted roadmap intent. Do not treat absence as deliberate deferral.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but one or more deferrals are weakly justified or difficult to trace.","GAP":"At least one functional requirement is neither delivered nor explicitly deferred.","INDETERMINATE":"The accepted evidence cannot establish complete requirement-to-roadmap accounting.","PASS":"Every current-horizon functional requirement is delivered or explicitly deferred."}},{"assessesAspects":["vision.success-criterion","roadmap.phase"],"criterionRef":"application-creation:criterion/success-criterion-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon vision success criterion is delivered by at least one roadmap phase. Keep success criteria distinct from implementation tasks or generic aspirations.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All criteria are covered, but one or more delivery links are weak or overly indirect.","GAP":"At least one current-horizon success criterion is not delivered by any roadmap phase.","INDETERMINATE":"The accepted evidence cannot establish complete success-criterion-to-roadmap coverage.","PASS":"Every current-horizon success criterion is delivered by at least one roadmap phase."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/top-down-phase-gate","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.phase-gate"},"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/top-down-phase-gate","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/brand-name-and-its-screening","criterionRef":"application-creation:criterion/brand-name-screening-standing","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":1,"requirementRef":"application-creation:evidence-requirement/brand-name-screening-standing","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/brand-and-name-screening"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-benefits","criterionRef":"application-creation:criterion/capability-completeness","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-capability-wiring"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/regulated-data-and-compliance-constraints","criterionRef":"application-creation:criterion/compliance-presence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-compliance"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/core-and-anti-target-icps","criterionRef":"application-creation:criterion/positioning-icp-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-positioning"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-functional-requirements","criterionRef":"application-creation:criterion/requirement-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/requirements-roadmap"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-success-criteria","criterionRef":"application-creation:criterion/success-criterion-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-roadmap"}],"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/journey-phase-transition","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/capability-completeness","application-creation:evidence-requirement/compliance-presence","application-creation:evidence-requirement/positioning-icp-coherence","application-creation:evidence-requirement/requirement-coverage","application-creation:evidence-requirement/success-criterion-coverage"],"requirementRef":"application-creation:authority-requirement/top-down-to-bottom-up-transition","requirementVersion":1,"riskClassRef":"application-creation:risk/bootstrap-non-regulated-phase-transition","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/top-down-phase-gate","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/top-down-to-bottom-up-transition","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/top-down-phase-gate","policyVersion":1},"decisionPointRef":"application-creation:decision-point/top-down-phase-gate","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/top-down-phase-gate","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/top-down-phase-gate","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-standing","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/definition-completeness","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/required-family-validity"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-transition","triggerRefs":["application-creation:trigger/top-down-definition-set-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-top-down-coherence-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/capability-completeness","application-creation:evidence-requirement/compliance-presence","application-creation:evidence-requirement/positioning-icp-coherence","application-creation:evidence-requirement/requirement-coverage","application-creation:evidence-requirement/success-criterion-coverage"],"hardFloorRef":"application-creation:hard-floor/required-family-validity"}],"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/top-down-phase-gate","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/top-down-phase-gate","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-top-down-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.name","brand-name-screening.candidate"],"criterionRef":"application-creation:criterion/brand-name-screening-standing","criterionVersion":3,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-standing","requirementVersion":1}],"instruction":"Determine where the product's NAME stands, reading the coherence report's brand-name findings first — they are computed, not judged. On a line that carries a brand, a missing brand-name screening (brand-name-screening-missing) or a brand name no screening covers (brand-name-not-screened), or a conflict nobody chose to keep (brand-name-conflict-unacknowledged), is a gap in the definition: the brand identity's name question cannot be answered, or the name was never checked. A name chosen with the screening incomplete, with no register read at all (brand-name-no-register-read), or kept despite a conflict is a deliberate, recorded decision that must be visible — in the risk register, as an entry derived from the brand-name-trademark-standing signal, and in the launch list as a brand name not cleared — not a failure. Fewer than three offerable proposals, a creator-listed name the screening does not carry, a screening that read no register for any name (brand-name-screening-read-nothing), or a place the application declares it operates in that the screening does not list (brand-name-operating-jurisdiction-not-screened), is a concern. A line with no brand (no brand-name finding and no definition-brand-brief-missing finding is reported for it) has nothing to assess; a line that carries a brand whose brief has not landed (definition-brand-brief-missing) is assessed by the definition-completeness criterion, never passed here as a line with no brand.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The brand name was chosen with the screening incomplete or kept despite a conflict and the risk register carries it, or the screening offers fewer than three proposals or misses a name the creator listed.","GAP":"On a line with a brand, no screening is on record or the brand name was never screened; or a name kept despite a conflict is recorded nowhere, the risk register included.","INDETERMINATE":"The coherence report is not in evidence, so the brand name's standing cannot be read.","PASS":"The line carries no brand, or the brand name is a screened candidate whose screening is complete and clear."}},{"assessesAspects":["market.benefit","feature-drafts.draft"],"criterionRef":"application-creation:criterion/capability-completeness","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1}],"instruction":"Determine whether every current-horizon market benefit is connected to at least one resolvable delivering feature. Treat an unwired benefit as a material gap; do not infer a connection from thematic similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All benefits are wired, but one or more connections are weak, indirect, or insufficiently explained.","GAP":"At least one current-horizon benefit has no resolvable delivering feature.","INDETERMINATE":"The accepted evidence cannot establish the benefit-to-feature wiring completely.","PASS":"Every current-horizon benefit has at least one resolvable delivering feature."}},{"criterionRef":"application-creation:criterion/compliance-presence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1}],"instruction":"Determine whether a product handling regulated or sensitive data declares at least one applicable compliance constraint. Do not invent regulation applicability; report indeterminate when the accepted evidence does not establish the data or sector posture.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A compliance constraint exists, but its applicability or coverage is weakly established.","GAP":"A regulated-data trigger is established and no applicable compliance constraint is declared.","INDETERMINATE":"The evidence cannot establish the regulated-data trigger or the applicable constraint posture.","PASS":"The evidence establishes either no regulated-data trigger or an applicable declared compliance constraint."}},{"criterionRef":"application-creation:criterion/definition-completeness","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/definition-completeness","requirementVersion":1}],"instruction":"Determine whether the definition holds every family the application's declared line carries, reading the coherence report's definition findings — they are computed, not judged. A business model (definition-business-model-missing) or a brand brief (definition-brand-brief-missing) the line carries that has not landed is a gap: the definition is not finished, whatever the other families say, and the finding names the step to run (or the interview to answer). A family the line declares not applicable is never reported and is not a gap. Do not infer a missing family from anything other than these findings.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Not used: a family the line carries is either on record or missing.","GAP":"The coherence report names a business model or a brand brief the declared line carries that has not landed.","INDETERMINATE":"The coherence report is not in evidence, so which families have landed cannot be read.","PASS":"The coherence report carries no definition-*-missing finding: every family the declared line carries has landed or is declared not applicable."}},{"assessesAspects":["market.icp","market.positioning"],"criterionRef":"application-creation:criterion/positioning-icp-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1}],"instruction":"Determine whether positioning pillars address the declared core ICPs without centring an anti-target segment. Preserve the authored ICP classifications and do not silently reclassify a segment.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Positioning is broadly coherent but under-serves a core ICP or approaches an anti-target boundary.","GAP":"Positioning ignores the core ICPs or explicitly centres an anti-target segment.","INDETERMINATE":"The accepted evidence cannot connect positioning pillars to the classified ICP set.","PASS":"Positioning addresses the core ICPs and does not centre an anti-target segment."}},{"assessesAspects":["requirements.functional","roadmap.phase"],"criterionRef":"application-creation:criterion/requirement-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is delivered by a roadmap phase or explicitly deferred in accepted roadmap intent. Do not treat absence as deliberate deferral.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but one or more deferrals are weakly justified or difficult to trace.","GAP":"At least one functional requirement is neither delivered nor explicitly deferred.","INDETERMINATE":"The accepted evidence cannot establish complete requirement-to-roadmap accounting.","PASS":"Every current-horizon functional requirement is delivered or explicitly deferred."}},{"assessesAspects":["vision.success-criterion","roadmap.phase"],"criterionRef":"application-creation:criterion/success-criterion-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon vision success criterion is delivered by at least one roadmap phase. Keep success criteria distinct from implementation tasks or generic aspirations.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All criteria are covered, but one or more delivery links are weak or overly indirect.","GAP":"At least one current-horizon success criterion is not delivered by any roadmap phase.","INDETERMINATE":"The accepted evidence cannot establish complete success-criterion-to-roadmap coverage.","PASS":"Every current-horizon success criterion is delivered by at least one roadmap phase."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/top-down-phase-gate","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.phase-gate"},"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/top-down-phase-gate","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/brand-name-and-its-screening","criterionRef":"application-creation:criterion/brand-name-screening-standing","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":1,"requirementRef":"application-creation:evidence-requirement/brand-name-screening-standing","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/brand-and-name-screening"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-benefits","criterionRef":"application-creation:criterion/capability-completeness","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-capability-wiring"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/regulated-data-and-compliance-constraints","criterionRef":"application-creation:criterion/compliance-presence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-compliance"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/coherence-report-definition-findings","criterionRef":"application-creation:criterion/definition-completeness","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/definition-completeness","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/line-carried-families"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/core-and-anti-target-icps","criterionRef":"application-creation:criterion/positioning-icp-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-positioning"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-functional-requirements","criterionRef":"application-creation:criterion/requirement-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/requirements-roadmap"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/all-current-horizon-success-criteria","criterionRef":"application-creation:criterion/success-criterion-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-family-heads","independencePolicyRef":null,"kind":"MANDATORY","maxCount":1,"minCount":1,"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-roadmap"}],"schemaVersion":1}
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.phase-gate",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.3.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
5
|
"intent": "Assess whether the validated top-down definition set is cross-artifact coherent enough for the current horizon. Deterministic family validation remains a non-bypassable eligibility floor; this playbook contributes an advisory semantic evaluation and never mutates application truth.",
|
|
6
6
|
"preconditions": [
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"aggregationPolicyRef":"application-creation:aggregation/worst-requirements-definition-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/requirements-definition-coherence","criterionVersion":
|
|
1
|
+
{"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"]}
|