@wildo-ai/framework-knowledge 1.1.2 → 1.1.3
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/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 +228 -6
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts +1 -2
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +3 -4
- 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 +4 -4
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +3 -4
- 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 +4 -4
- 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 +0 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +1 -2
- 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 +1 -2
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +2 -3
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +3 -3
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -2
- 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 +1 -2
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +0 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +0 -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 +0 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +0 -1
- 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 +0 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +0 -2
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +2 -2
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +0 -2
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +9 -4
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +0 -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 +0 -1
- 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 +0 -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 +0 -1
- 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 +0 -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 +0 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +0 -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 +0 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/manifest.json +8 -9
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +13 -70
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +11 -19
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +5 -88
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +15 -8
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +4 -5
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +15 -8
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +4 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -7
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +22 -49
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +8 -17
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +15 -780
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +11 -11
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +20 -141
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +15 -10
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +3 -2
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +16 -11
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +14 -6
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +4 -2
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +16 -7
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +4 -21
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +65 -16
- package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-analysis/method.md +165 -51
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +43 -23
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +4 -8
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +7 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +7 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +15 -7
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +3 -3
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +16 -11
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +4 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +15 -7
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +16 -11
- package/dist/knowledge/references/build-plan.task-graph.config.md +1 -45
- package/dist/knowledge/references/companion.technical-doc.service.md +2 -102
- package/dist/knowledge/references/example.config.app-shell.full.md +5 -0
- package/dist/knowledge/references/example.module.companion-exports.full.md +0 -1
- package/dist/knowledge/references/example.provider.backend-module-shape.md +0 -7
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +1 -0
- package/dist/knowledge/references/platform.config.saas.md +0 -51
- package/dist/knowledge/references/presets.models.surface-policy.md +10 -19
- package/dist/knowledge/references/saas.external-data.admin-endpoints.md +48 -0
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +11 -31
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +1 -0
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +0 -45
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +0 -198
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -164
- package/dist/knowledge/references/saas.models.engine-capabilities.md +6 -26
- package/dist/knowledge/references/saas.models.http-api-binding.md +29 -3
- package/dist/knowledge/references/saas.models.provider-capabilities.md +3 -4
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +2 -4
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +0 -2
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +0 -14
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +31 -11
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +2 -32
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +6 -29
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +0 -56
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +0 -22
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +0 -26
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +0 -45
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +1 -7
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +5 -31
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +1 -44
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +0 -3
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +0 -1
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +0 -15
- package/dist/knowledge/registries/assurance-authority-bases.json +2 -3
- package/dist/knowledge/registries/framework-topics.json +11 -146
- package/dist/knowledge/registries/playbooks.json +18 -154
- package/dist/knowledge/registries/source-tags.json +630 -883
- package/dist/knowledge/skills/INDEX.md +3 -4
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +1 -2
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -16
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +9 -31
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +74 -252
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +8 -26
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +53 -97
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +21 -84
- package/dist/knowledge/skills/config-app-shell/SKILL.md +9 -31
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +12 -31
- package/dist/knowledge/skills/config-design-system/SKILL.md +1 -23
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +10 -19
- package/dist/knowledge/skills/config-navigation/SKILL.md +2 -75
- package/dist/knowledge/skills/config-saas/SKILL.md +2 -19
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +9 -30
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +0 -51
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +0 -7
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +1 -2
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +3 -4
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +0 -56
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +0 -56
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +0 -1
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +0 -56
- package/dist/knowledge/skills/resource-add-field/SKILL.md +3 -3
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +0 -213
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +1 -2
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +2 -4
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +0 -15
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +2 -224
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +0 -198
- package/dist/knowledge/skills/resource-external-data/SKILL.md +2 -0
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +29 -3
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +70 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +1 -22
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +8 -28
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +0 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +0 -17
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +0 -46
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +0 -15
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +0 -26
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +1 -7
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +0 -198
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +1 -44
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +0 -3
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +0 -1
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +0 -56
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +5 -31
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +0 -22
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +0 -45
- package/dist/knowledge/topic-index.json +220 -725
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +0 -1
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +0 -51
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +0 -43
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +0 -185
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +0 -64
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +0 -41
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +0 -100
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +0 -117
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +0 -86
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +0 -61
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +0 -41
- package/dist/knowledge/playbooks/top_down.compliance-research/method.md +0 -76
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +0 -42
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +0 -56
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -42
- package/dist/knowledge/playbooks/top_down.market-research/method.md +0 -68
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -44
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +0 -239
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +0 -67
- package/dist/knowledge/references/placement-plan.config.md +0 -330
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +0 -34
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +0 -45
- package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +0 -65
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +0 -58
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +0 -118
- package/dist/knowledge/references/saas.models.file-upload-grant.md +0 -179
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +0 -124
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +0 -99
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +0 -127
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +0 -42
- package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +0 -29
- package/dist/knowledge/references/zod.decorators.data-categories.md +0 -197
- package/dist/knowledge/rules/resource-schema-awareness.md +0 -77
- package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +0 -124
- package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +0 -47
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +0 -98
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +0 -54
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +0 -232
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +0 -149
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +0 -114
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +0 -133
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +0 -111
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +0 -622
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +0 -192
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +0 -245
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +0 -134
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +0 -65
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +0 -127
- /package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/structured-artifact-action.json +0 -0
|
@@ -5,6 +5,10 @@
|
|
|
5
5
|
"intent": "Turn the accepted market and requirements truth, plus the creator's own pricing intent, into a non-vacuous BusinessModelLiteSnapshot: the product-level revenue model and a sketch of pricing plans, each cross-linked to the market ICPs it is sold to and the requirements it unlocks. A PLANNING artifact carrying commercial INTENT — never the billing runtime, and never a price the creator did not state.",
|
|
6
6
|
"functionalTopics": [],
|
|
7
7
|
"preconditions": [
|
|
8
|
+
{
|
|
9
|
+
"kind": "phase_is",
|
|
10
|
+
"phase": "top_down"
|
|
11
|
+
},
|
|
8
12
|
{
|
|
9
13
|
"kind": "artifact_valid",
|
|
10
14
|
"selector": {
|
|
@@ -40,10 +44,10 @@
|
|
|
40
44
|
{
|
|
41
45
|
"family": "business-model",
|
|
42
46
|
"schemaRef": "saas-specifications:BusinessModelLiteSnapshot",
|
|
47
|
+
"placement": "specifications/src/business-model/",
|
|
43
48
|
"description": "A validated revenue-model classification plus at least one pricing plan, each cross-linked to the market ICPs it targets and the requirements it unlocks."
|
|
44
49
|
}
|
|
45
50
|
],
|
|
46
|
-
"stepOutputs": [],
|
|
47
51
|
"method": {
|
|
48
52
|
"guidance": "# Business Model — Commercial Intent 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.** Pricing sketch depth only — no unit\n> economics, no cohort modelling, no competitive price positioning. Those are a\n> later phase; do not perfect them here.\n\n## What this playbook does\n\nYou are recording the product's **commercial intent**: how it makes money, and\nwhat it sells. The output is one `BusinessModelLiteSnapshot` — a revenue-model\nclassification plus a sketch of pricing plans, each cross-linked to the market\nsegments it is sold to and the requirements it unlocks.\n\nIt is a **PLANNING artifact**, in exactly the sense the vision and the roadmap\nare. It is not the billing runtime, not a Stripe catalogue, and not a price list\nanyone is held to. Nothing reads it to charge a customer.\n\n## The one rule that governs everything below\n\n**You do not decide how this product charges. The creator does.**\n\nEvery other top-down family is DERIVED — the market snapshot follows from the\nvision, requirements follow from both, the roadmap follows from the capability\nmap. This one is not, and the difference is not a matter of degree. The same\nproduct is a fair freemium tool, a per-seat B2B subscription, or a\nusage-metered API, and **nothing in the vision, the market or the requirements\ndecides which**. It is a business decision, and only the creator holds it.\n\nSo this playbook interviews. Your job is to take what the creator said and make\nit *structured and cross-linked* — never to fill a gap they left.\n\nConcretely:\n\n- **Never invent a price.** If the creator said \"not decided yet\", omit\n `pricePoint`. A tier with no price is a real, useful plan; a tier with a price\n nobody chose is a fabrication that then propagates — the foundation playbook\n derives the billing capability from this artifact.\n- **Never invent a tier.** Three tiers is the industry default and that is\n exactly why it is a trap. If they described one, produce one.\n- **Never invent a scaling axis.** If they did not say what the price scales\n with, omit `pricingModel` rather than guessing `per_seat`.\n- **\"Not decided yet\" is an answer.** Record what they *did* decide and leave\n the rest absent. Absence is legible; an invention is not.\n\n## What you DO derive\n\nTwo things, and both are cross-links rather than content:\n\n### `targetIcpRefs` — who each plan is sold to\n\nThe creator described tiers in prose (\"a free one for solo people, a paid one\nfor teams\"). The market snapshot holds the ICP refs. Your job is to resolve one\nagainst the other: match each described audience to the ICP that means it, and\nput its ref on the plan.\n\nEvery ref you write must EXIST in the market snapshot. A dangling ICP ref is a\nvalidator ERROR, and it is also the more interesting failure — it usually means\nthe creator described an audience the market analysis never identified, which is\nworth surfacing rather than papering over. If a described audience matches no\nICP, omit the ref and say so in `targetSummary` prose instead.\n\nWatch for **anti-targets**: a vision constraint may explicitly rule out a\nsegment (an enterprise procurement motion, say). Do not target an ICP the vision\nexcludes, even if a tier looks like it fits.\n\n### `includesRequirementRefs` — what each plan unlocks\n\nThis is the traceability that makes the artifact load-bearing rather than\ndecorative: it is what `bottom_up.foundation` reads to decide whether the\napplication needs a billing capability at all.\n\nResolve the creator's description of what each tier includes against the\n`requirements` family, and list the refs. Every ref must exist there. A paid\ntier that unlocks no nameable requirement is a signal worth leaving visible —\neither the requirement is missing, or the tier is not really differentiated.\n\n## The free tier is the one to get right\n\nIf the creator described a free tier or trial, two things matter and both come\nfrom what they said:\n\n- what it **includes** — the requirements it unlocks;\n- what is **deliberately held back** — which is usually the sharper statement of\n the paid tiers' value, and belongs in the paid plan's `includes` prose.\n\nIf they said there is no free tier, say nothing about one. Freemium is a\n*revenue model*, not a default.\n\n## Producing the artifact\n\nOne output, the `business-model` family. The contract is strict:\n\n- **`revenueModel` is required.** Pick the enum member closest to what the\n creator described. If they described something genuinely outside the set, pick\n the nearest and explain the mismatch in the plans' prose — do not stretch a\n member past its meaning.\n- **At least one plan.** A business model with no plans carries no information a\n reader could act on. If the creator sells exactly one thing, that is one plan,\n fully described.\n- **`slug`, not `ref`.** You author a kebab-case slug per plan; the trusted\n runtime stamps the `pricing-plan-` prefix. Never write a ref yourself.\n- **Every optional field is nullable and required.** Send `null` where the\n creator gave you nothing. An omitted key and a considered \"there is none\" must\n not look the same.\n\n## Verification before you answer\n\n- [ ] Every `pricePoint` traces to something the creator actually wrote.\n- [ ] Every plan traces to a tier they described. No tier count was rounded up.\n- [ ] Every `targetIcpRefs` entry exists in the market snapshot.\n- [ ] Every `includesRequirementRefs` entry exists in the requirements snapshot.\n- [ ] No ICP the vision constraints exclude is targeted.\n- [ ] `revenueModel` is consistent with the plans beneath it — a `freemium`\n classification with no free plan, or a `subscription` with only a one-off\n purchase, is incoherent.\n- [ ] Nothing in the artifact answers a question the creator left open.\n",
|
|
49
53
|
"skillRefs": [
|
|
@@ -85,13 +89,17 @@
|
|
|
85
89
|
"kind": "free_text"
|
|
86
90
|
}
|
|
87
91
|
]
|
|
88
|
-
}
|
|
89
|
-
"contextSources": [],
|
|
90
|
-
"suspendsForClarification": false,
|
|
91
|
-
"briefAdequacyGate": false,
|
|
92
|
-
"briefAdequacyExcludedSources": []
|
|
92
|
+
}
|
|
93
93
|
},
|
|
94
94
|
"executor": "companion_agent",
|
|
95
|
+
"qualityGates": [
|
|
96
|
+
{
|
|
97
|
+
"ref": "business-model-valid",
|
|
98
|
+
"kind": "deterministic_validator",
|
|
99
|
+
"validatorRef": "saas-specifications:validateBusinessModelLiteSnapshot",
|
|
100
|
+
"required": true
|
|
101
|
+
}
|
|
102
|
+
],
|
|
95
103
|
"approval": "approve_result",
|
|
96
104
|
"budget": {
|
|
97
105
|
"maxRuns": 3
|
|
@@ -68,6 +68,8 @@ anything:
|
|
|
68
68
|
real market intent, the real requirements, and the real differentiation — not
|
|
69
69
|
from scratch.
|
|
70
70
|
|
|
71
|
+
// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)
|
|
72
|
+
// TODO CLI COMMAND: wildo context market-snapshot (read the benefits to map + any existing feature edges)
|
|
71
73
|
|
|
72
74
|
You **read** `market-snapshot` + `requirements` + `vision-brief`; you **write**
|
|
73
75
|
the refined `market-snapshot` (edge wired) and the `feature-drafts` family (the
|
|
@@ -213,10 +215,10 @@ scaffold depth — depth is a dedicated later pass done once, holistically.
|
|
|
213
215
|
|
|
214
216
|
Two artifacts for this journey:
|
|
215
217
|
|
|
216
|
-
1. The SAME **MarketSnapshot** at
|
|
218
|
+
1. The SAME **MarketSnapshot** at `.wildo-saas/journey/<journeyId>/market-snapshot/`,
|
|
217
219
|
with every benefit's `deliveredByFeatureRefs` edge wired to its delivering
|
|
218
220
|
feature(s), passing the `market-snapshot-valid` gate.
|
|
219
|
-
2. The **feature-drafts** at
|
|
221
|
+
2. The **feature-drafts** at `.wildo-saas/journey/<journeyId>/feature-drafts/` —
|
|
220
222
|
one spec-first `FeatureSpecificationDraft` per new delivering feature.
|
|
221
223
|
|
|
222
224
|
The creator reviews the result (approval posture `approve_result`) before it is
|
|
@@ -5,6 +5,10 @@
|
|
|
5
5
|
"intent": "Map accepted market benefits and requirements to coherent product capabilities, atomically refining the market benefit-to-feature edges and producing ref-less feature specification drafts. FIT/Kano remains a pluggable fit signal, never an implicit build-order ranking.",
|
|
6
6
|
"functionalTopics": [],
|
|
7
7
|
"preconditions": [
|
|
8
|
+
{
|
|
9
|
+
"kind": "phase_is",
|
|
10
|
+
"phase": "top_down"
|
|
11
|
+
},
|
|
8
12
|
{
|
|
9
13
|
"kind": "artifact_valid",
|
|
10
14
|
"selector": {
|
|
@@ -39,30 +43,35 @@
|
|
|
39
43
|
{
|
|
40
44
|
"family": "market-snapshot",
|
|
41
45
|
"schemaRef": "saas-specifications:MarketSnapshot",
|
|
46
|
+
"placement": ".wildo-saas/journey/<journeyId>/market-snapshot/",
|
|
42
47
|
"description": "The same market snapshot, refined so every benefit names its delivering feature refs."
|
|
43
48
|
},
|
|
44
49
|
{
|
|
45
50
|
"family": "feature-drafts",
|
|
46
51
|
"schemaRef": "saas-specifications:FeatureSpecificationDrafts",
|
|
52
|
+
"placement": ".wildo-saas/journey/<journeyId>/feature-drafts/",
|
|
47
53
|
"description": "A collection of runner-addressed, ref-less FeatureSpecificationDraft payloads for capabilities without runtime definitions."
|
|
48
54
|
}
|
|
49
55
|
],
|
|
50
|
-
"stepOutputs": [],
|
|
51
56
|
"method": {
|
|
52
|
-
"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'>`). The\n cross-registry validators are deliberately **fail-soft while the feature\n registry is empty** — so authoring the spec before the code does NOT\n crash-loop the app. (`spec-feature-update`)\n\nThen you **prioritize** the resulting feature set with a FIT-scoring + Kano\nstep — kept pluggable and versioned (see \"The scoring seam\" below).\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 through the `journey-status` skill\n (it owns the read; do not re-derive it here).\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 `spec-feature-update` is the field-shape authority for a feature spec; here\n you use its prose surface only. Keep it a *capability contract*, not an\n implementation. (`spec-feature-update`)\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). Treat\nthe scorer as a swappable black box: feed it the snapshot, read back the per-ICP\nFIT scores + Kano categories, and use them to sanity-check the capability set. 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 Removing a feature that a benefit still delivers, or a draft a benefit still\n points at, orphans the edge. Feature-ref orphans are only resolution-checked\n once a feature registry is passed to the validator (not at this phase — the\n registry is empty and the check is fail-soft), so honest refinement must not\n create the orphan in the first place.\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\nThe refined MarketSnapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. The\ncapability-mapping invariants it enforces:\n\n- **`EMPTY_BENEFIT_DELIVERED_BY` (ERROR)** — a benefit's `deliveredByFeatureRefs[]`\n is empty; every benefit must be deliverable. This is the headline check this\n playbook clears.\n- **`ORPHAN_REF` (ERROR)** — a benefit naming a missing pain/gain/job (feature-ref\n orphans are only checked once a feature registry is passed — not at this phase).\n- The value-proposition invariants inherited from the prior pass\n (`MISSING_POSITIONING_FOR_ICP`, `THRESHOLD_BENEFIT_WITHOUT_JOB`,\n `MULTIPLE_THRESHOLDS_PER_ICP_JOB`) still apply — do not regress them.\n\nRead `market-snapshot-validation` for the full issue catalogue.\n\nThe `feature-drafts` family has **no snapshot-level deterministic gate at this\nphase** — the only feature-spec validator is per-item and needs a ref-bearing\nconfig, which a spec-first draft deliberately omits. Author each draft to the\n`spec-feature-update` skill's contract (which carries the per-draft validity\ncheck); the collection-level gate is a filed depth-phase item (see below).\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- **A snapshot-level `feature-drafts` validator.** No deterministic validator\n exists yet for a *collection* of spec-first drafts (the per-item\n `validateFeatureSpecification` needs a ref, which drafts omit). Authoring the\n collection-level gate — and deciding whether draft prioritization output is\n itself a gated artifact — is depth-phase work.\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\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and\n scope, and confirm a `market-snapshot` already exists to map from.\n- `.claude/skills/market-add-feature-benefit/SKILL.md` — author/adjust the benefit\n claims and wire their `deliveredByFeatureRefs` edges.\n- `.claude/skills/spec-feature-update/SKILL.md` — author the spec-first\n `FeatureSpecificationDraft`(s) for the new delivering features.\n- `.claude/skills/market-scoring-interpretation/SKILL.md` — 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- `.claude/skills/market-snapshot-validation/SKILL.md` — the full validation issue\n catalogue the quality gate enforces.\n",
|
|
57
|
+
"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'>`). The\n cross-registry validators are deliberately **fail-soft while the feature\n registry is empty** — so authoring the spec before the code does NOT\n crash-loop the app. (`spec-feature-update`)\n\nThen you **prioritize** the resulting feature set with a FIT-scoring + Kano\nstep — kept pluggable and versioned (see \"The scoring seam\" below).\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 through the `journey-status` skill\n (it owns the read; do not re-derive it here).\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// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)\n// TODO CLI COMMAND: wildo context market-snapshot (read the benefits to map + any existing feature edges)\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 `spec-feature-update` is the field-shape authority for a feature spec; here\n you use its prose surface only. Keep it a *capability contract*, not an\n implementation. (`spec-feature-update`)\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). Treat\nthe scorer as a swappable black box: feed it the snapshot, read back the per-ICP\nFIT scores + Kano categories, and use them to sanity-check the capability set. 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 Removing a feature that a benefit still delivers, or a draft a benefit still\n points at, orphans the edge. Feature-ref orphans are only resolution-checked\n once a feature registry is passed to the validator (not at this phase — the\n registry is empty and the check is fail-soft), so honest refinement must not\n create the orphan in the first place.\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\nThe refined MarketSnapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. The\ncapability-mapping invariants it enforces:\n\n- **`EMPTY_BENEFIT_DELIVERED_BY` (ERROR)** — a benefit's `deliveredByFeatureRefs[]`\n is empty; every benefit must be deliverable. This is the headline check this\n playbook clears.\n- **`ORPHAN_REF` (ERROR)** — a benefit naming a missing pain/gain/job (feature-ref\n orphans are only checked once a feature registry is passed — not at this phase).\n- The value-proposition invariants inherited from the prior pass\n (`MISSING_POSITIONING_FOR_ICP`, `THRESHOLD_BENEFIT_WITHOUT_JOB`,\n `MULTIPLE_THRESHOLDS_PER_ICP_JOB`) still apply — do not regress them.\n\nRead `market-snapshot-validation` for the full issue catalogue.\n\nThe `feature-drafts` family has **no snapshot-level deterministic gate at this\nphase** — the only feature-spec validator is per-item and needs a ref-bearing\nconfig, which a spec-first draft deliberately omits. Author each draft to the\n`spec-feature-update` skill's contract (which carries the per-draft validity\ncheck); the collection-level gate is a filed depth-phase item (see below).\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- **A snapshot-level `feature-drafts` validator.** No deterministic validator\n exists yet for a *collection* of spec-first drafts (the per-item\n `validateFeatureSpecification` needs a ref, which drafts omit). Authoring the\n collection-level gate — and deciding whether draft prioritization output is\n itself a gated artifact — is depth-phase work.\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 `.wildo-saas/journey/<journeyId>/market-snapshot/`,\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 `.wildo-saas/journey/<journeyId>/feature-drafts/` —\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\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and\n scope, and confirm a `market-snapshot` already exists to map from.\n- `.claude/skills/market-add-feature-benefit/SKILL.md` — author/adjust the benefit\n claims and wire their `deliveredByFeatureRefs` edges.\n- `.claude/skills/spec-feature-update/SKILL.md` — author the spec-first\n `FeatureSpecificationDraft`(s) for the new delivering features.\n- `.claude/skills/market-scoring-interpretation/SKILL.md` — 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- `.claude/skills/market-snapshot-validation/SKILL.md` — the full validation issue\n catalogue the quality gate enforces.\n",
|
|
53
58
|
"skillRefs": [
|
|
54
59
|
"journey-status",
|
|
55
60
|
"market-add-feature-benefit",
|
|
56
61
|
"market-scoring-interpretation",
|
|
57
62
|
"market-snapshot-validation",
|
|
58
63
|
"spec-feature-update"
|
|
59
|
-
]
|
|
60
|
-
"contextSources": [],
|
|
61
|
-
"suspendsForClarification": false,
|
|
62
|
-
"briefAdequacyGate": false,
|
|
63
|
-
"briefAdequacyExcludedSources": []
|
|
64
|
+
]
|
|
64
65
|
},
|
|
65
66
|
"executor": "companion_agent",
|
|
67
|
+
"qualityGates": [
|
|
68
|
+
{
|
|
69
|
+
"ref": "capability-map-output-set-valid",
|
|
70
|
+
"kind": "deterministic_validator",
|
|
71
|
+
"validatorRef": "saas-specifications:validateCapabilityMapOutputSet",
|
|
72
|
+
"required": true
|
|
73
|
+
}
|
|
74
|
+
],
|
|
66
75
|
"approval": "approve_result",
|
|
67
76
|
"budget": {
|
|
68
77
|
"maxRuns": 3
|
|
@@ -69,9 +69,8 @@ requirements and explicit gaps.
|
|
|
69
69
|
The transition is not an automatic conversion and must not reinterpret a
|
|
70
70
|
vision sentence as a control mapping or positive compliance claim. Preserve
|
|
71
71
|
the vision constraint as product intent, record any missing detail as
|
|
72
|
-
`UNDETERMINED` or an explicit gap, and
|
|
73
|
-
|
|
74
|
-
and a human commit is the only acceptance there is. Runtime organizations, assignees, evidence,
|
|
72
|
+
`UNDETERMINED` or an explicit gap, and accept the structured family through the
|
|
73
|
+
normal semantic-delta authority. Runtime organizations, assignees, evidence,
|
|
75
74
|
control occurrences and assessments remain outside both artifacts.
|
|
76
75
|
|
|
77
76
|
## The derivation posture
|
|
@@ -168,24 +167,8 @@ Before you start, read the current journey state and scope, and read the
|
|
|
168
167
|
existing vision so you refine its compliance constraints rather than writing a
|
|
169
168
|
fresh, disconnected set.
|
|
170
169
|
|
|
171
|
-
|
|
172
|
-
|
|
173
|
-
|
|
174
|
-
## The evidence, and how to use it
|
|
175
|
-
|
|
176
|
-
Your run carries what sibling steps gathered — source-attributed regime evidence and the adequacy
|
|
177
|
-
verdict that admitted this step. Derive each constraint from the creator's answers AND that
|
|
178
|
-
evidence, never from recollection:
|
|
179
|
-
|
|
180
|
-
- A regime the evidence establishes as APPLICABLE becomes a `compliance` constraint whose statement
|
|
181
|
-
names the regime, the trigger (jurisdiction / data class / sector / commitment), and what it
|
|
182
|
-
governs — in the evidence's terms.
|
|
183
|
-
- A regime the evidence EXCLUDES is not written as a constraint, and is not silently dropped either:
|
|
184
|
-
where the creator's answers suggested it, the statement of a neighbouring constraint may note the
|
|
185
|
-
exclusion so the decision is legible.
|
|
186
|
-
- A trigger the evidence could NOT establish becomes a constraint stating the OPEN QUESTION, never a
|
|
187
|
-
guessed answer — an unestablished regime stated as settled is the defect this composite exists to
|
|
188
|
-
end.
|
|
170
|
+
// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)
|
|
171
|
+
// TODO CLI COMMAND: wildo context vision-brief (read the existing vision + its current constraints)
|
|
189
172
|
|
|
190
173
|
## References
|
|
191
174
|
|
|
@@ -1,23 +1,19 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.compliance-posture",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.1.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
|
-
"intent": "Compliance-posture pass: a focused elicitation that determines which legal, regulatory, contractual and external-assurance regimes the product operates under by reasoning over its jurisdictions, the classes of data it handles, its sector and customer commitments — and records each applicable regime as a `compliance`-kind constraint (prose statement) on the product's VisionSnapshot (the `vision-brief` artifact family). This SHARPENS the compliance seam the vision-elicitation step named in passing; it does NOT re-elicit the whole vision. SCAFFOLD depth: compliance stays PROSE constraints here — the deep per-regime obligation model (control catalogs, data-residency matrices, obligation graphs) is a deferred later concern, not built here. v1 scaffold methodology — iterate the regime-derivation rubric.
|
|
5
|
+
"intent": "Compliance-posture pass: a focused elicitation that determines which legal, regulatory, contractual and external-assurance regimes the product operates under by reasoning over its jurisdictions, the classes of data it handles, its sector and customer commitments — and records each applicable regime as a `compliance`-kind constraint (prose statement) on the product's VisionSnapshot (the `vision-brief` artifact family). This SHARPENS the compliance seam the vision-elicitation step named in passing; it does NOT re-elicit the whole vision. SCAFFOLD depth: compliance stays PROSE constraints here — the deep per-regime obligation model (control catalogs, data-residency matrices, obligation graphs) is a deferred later concern, not built here. v1 scaffold methodology — iterate the regime-derivation rubric.",
|
|
6
6
|
"functionalTopics": [],
|
|
7
7
|
"preconditions": [
|
|
8
|
+
{
|
|
9
|
+
"kind": "phase_is",
|
|
10
|
+
"phase": "top_down"
|
|
11
|
+
},
|
|
8
12
|
{
|
|
9
13
|
"kind": "artifact_exists",
|
|
10
14
|
"selector": {
|
|
11
15
|
"family": "vision-brief"
|
|
12
16
|
}
|
|
13
|
-
},
|
|
14
|
-
{
|
|
15
|
-
"kind": "step_available",
|
|
16
|
-
"ref": "compliance-adequacy",
|
|
17
|
-
"requires": {
|
|
18
|
-
"path": "verdict",
|
|
19
|
-
"equals": "adequate"
|
|
20
|
-
}
|
|
21
17
|
}
|
|
22
18
|
],
|
|
23
19
|
"inputs": [
|
|
@@ -29,21 +25,74 @@
|
|
|
29
25
|
{
|
|
30
26
|
"family": "vision-brief",
|
|
31
27
|
"schemaRef": "saas-specifications:VisionSnapshot",
|
|
28
|
+
"placement": ".wildo-saas/journey/<journeyId>/vision-brief/",
|
|
32
29
|
"description": "The same VisionSnapshot the vision-elicitation step seeded, refined in place: this playbook adds/updates the `constraints[]` entries whose `kind` is `compliance`, each a prose `statement` naming an applicable regime and the data / jurisdiction it governs. Other vision entities (idea, problem, mission, success criteria, non-compliance constraints) are left untouched. Validated by validateVisionSnapshot."
|
|
33
30
|
}
|
|
34
31
|
],
|
|
35
|
-
"stepOutputs": [],
|
|
36
32
|
"method": {
|
|
37
|
-
"guidance": "# Compliance Posture — Derivation 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.** The regime-derivation rubric below\n> (which triggers imply which regime, how much to capture) is a deliberately\n> explicit first cut meant to be tuned against real runs. Treat it as a\n> starting rubric, not a frozen contract. Crucially, it derives compliance\n> **posture at scaffold depth** — prose constraints, not a per-regime\n> obligation model.\n\n## What this playbook does\n\nYou determine the product's **compliance posture** — which regulatory regimes\nit must be built to satisfy — and record each as a `compliance`-kind constraint\non the existing vision. The vision-elicitation step already named the\ncompliance _seam_ in passing (a single \"we handle EU personal data\" line). Your\njob is the focused, deliberate pass over that seam: reason from the product's\njurisdictions, the classes of data it handles, and its sector to the concrete\nset of regimes, and write each one down as its own constraint with a clear\nprose statement.\n\nYou do **not** re-elicit the whole vision, design the domain, or draft\nrequirements. You touch exactly one slice of the `VisionSnapshot`: its\n`constraints[]` entries of `kind: compliance`. Everything else on the snapshot\n— the idea, the problem, the mission, the success criteria, the\nnon-compliance constraints — you leave exactly as you found it.\n\n## The scaffold-depth boundary (read this before you start)\n\nAt this stage compliance is captured as **prose constraints only**. Each\napplicable regime becomes one constraint entry whose `statement` names the\nregime and the data / jurisdiction it governs — e.g. _\"Must be GDPR-compliant\nfor EU/EEA customer personal data.\"_ That is the whole deliverable.\n\nDo **not** build, and do not try to author into the snapshot:\n\n- per-regime control catalogs or obligation graphs (legal-article mappings,\n sector safeguards, external-assurance criteria),\n- data-flow / residency matrices,\n- retention schedules, DPA registries, or audit-config derivations.\n\nThat deep per-regime obligation model is a deliberately deferred later concern.\nIf you catch yourself modelling controls or obligations, **stop** — you have\nleft scaffold depth. Naming the regime seam accurately here is exactly what\nlets that later, deeper step engage. Getting the _set of applicable regimes_\nright, in prose, is the win.\n\n### Transition to structured compliance conception\n\nThis playbook does not write the dedicated `compliance-program` family. Its\naccepted vision constraints are precursor facts for a later, separately\napproved compliance-conception step. That step may initialize or revise the\noptional structured family only after it resolves exact source versions and\nrights records, declarative application scope, applicability authority, Wildo\nobjective bindings, implementation choices, responsibilities, documentation\nrequirements and explicit gaps.\n\nThe transition is not an automatic conversion and must not reinterpret a\nvision sentence as a control mapping or positive compliance claim. Preserve\nthe vision constraint as product intent, record any missing detail as\n`UNDETERMINED` or an explicit gap, and land the structured family as files in the\nspecifications package. Landing is not accepting: the run leaves working edits,\nand a human commit is the only acceptance there is. Runtime organizations, assignees, evidence,\ncontrol occurrences and assessments remain outside both artifacts.\n\n## The derivation posture\n\n- **Derive, then confirm — do not just transcribe.** The typed questions on\n this playbook (`method.elicitation`) gather the raw triggers: jurisdictions,\n data classes, sector, and direct yes/no reads on the common regimes. Your\n value is reasoning from those triggers to the regime set, then reflecting\n each derived regime back to the creator for confirmation. If EU users +\n personal data are present, GDPR applies whether or not the creator named it;\n surface that, don't wait to be told.\n- **Regime derivation rubric (v1).** Use these as the starting triggers, and\n follow up where an answer is thin:\n - **GDPR / UK GDPR** — serving EU/EEA (or UK) individuals, or processing\n their personal data. Triggered by jurisdiction (EU/EEA/UK) + any personal\n data.\n - **HIPAA** — handling US protected health information as, or on behalf of, a\n covered entity or business associate. Triggered by health data + US\n healthcare context.\n - **External assurance commitments** — enterprise customers or the product's own security posture\n require an independent attestation or certification over security / availability /\n confidentiality. Often contractual rather than statutory — capture the requested target as\n externally supplied source metadata when the go-to-market depends on it.\n - **Data residency / sovereignty** — a requirement that certain data stay\n within a region or country. Triggered by residency answers or sector rules;\n record as its own compliance constraint even when it rides alongside GDPR.\n - **Sector & additional regimes** — payment-card, consumer-privacy, children's-data,\n government-security, contractual-assurance and sector-code obligations. Add each that\n the triggers imply; preserve the exact named source only in the later source registry.\n - When the triggers are genuinely absent (no personal data, no regulated\n sector), the honest posture is _no compliance constraints_ — say so and add\n none. Do not invent a regime to look thorough.\n- **One regime, one constraint.** Keep regimes as separate constraint entries\n rather than one omnibus \"must be compliant\" line — the set is read\n downstream, and a merged statement loses which regimes are actually in play.\n\n## What you emit\n\nYou refine the **existing** `VisionSnapshot` in place. Concretely, you\nadd or update entries in `constraints[]`:\n\n- Each applicable regime is one entry with `kind: compliance`.\n- Each entry has a stable kebab-case `ref` prefixed `constraint-`\n (e.g. `constraint-gdpr-eu-personal-data`,\n `constraint-hipaa-us-phi`, `constraint-external-assurance-security`,\n `constraint-data-residency-eu`), unique across the whole `constraints[]` set.\n- Each entry's `statement` is a prose sentence naming the regime and the data /\n jurisdiction it governs. Where the creator gave the source of the limit\n (a customer contract, a specific law), capture it as the constraint's\n rationale.\n\nLeave every non-`compliance` constraint, and every other vision entity,\nuntouched.\n\n**Idempotent — refine, do not duplicate.** Read the vision first. If compliance\nconstraints already exist (the vision-elicitation step, or a prior run of this\nplaybook, may have written some), reconcile against them: update a statement\nthat is now sharper, add a regime that was missed, and remove one only if the\ncreator confirms it never applied. **Match existing constraints by the REGIME\ntheir `statement` names, not by their `ref` slug** — the vision-elicitation step\nwrites compliance prose without following this playbook's ref convention, so a\nGDPR line it left may sit under any slug (`constraint-gdpr`,\n`constraint-eu-data`, …). When you refine a regime that is already present,\n**reuse that entry's existing `ref`** so it updates in place rather than\nforking; only mint a fresh `constraint-<regime>-<scope>` slug for a regime that\nis genuinely new. Re-running this playbook on an already-posture'd vision must\nconverge to one entry per regime, never accumulate near-duplicate\n`constraint-gdpr-*` entries.\n\n## Quality gate\n\nYour refined snapshot is checked by the deterministic `vision-snapshot-valid`\ngate (`validateVisionSnapshot`) before it commits — the same gate the\nvision-elicitation step uses, because you write to the same family. Duplicate\nrefs and malformed refs (a constraint ref that is not kebab-case with the\n`constraint-` prefix) are hard **errors**; the gate rejects them. Emit clean,\nunique refs the first time. Note that a vision with no compliance constraints\nis perfectly valid — an honestly unregulated product should pass the gate with\nnone.\n\n## Approval\n\nThe refined `VisionSnapshot` is presented to the creator for approval before it\nbecomes the committed `vision-brief`. Show the derived compliance posture back\nin plain prose — the list of regimes, each with the data / jurisdiction it\ngoverns and why it applies — and let the creator confirm or correct it.\nCompliance drives real downstream engine capability, audit, and retention\nchoices, so it is worth one explicit human sign-off that the regime set is\nright.\n\n## Runtime context\n\nBefore you start, read the current journey state and scope, and read the\nexisting vision so you refine its compliance constraints rather than writing a\nfresh, disconnected set.\n\n(The existing vision and its current constraints are already in your brief as the `vision-brief`\ninput section.)\n\n## The evidence, and how to use it\n\nYour run carries what sibling steps gathered — source-attributed regime evidence and the adequacy\nverdict that admitted this step. Derive each constraint from the creator's answers AND that\nevidence, never from recollection:\n\n- A regime the evidence establishes as APPLICABLE becomes a `compliance` constraint whose statement\n names the regime, the trigger (jurisdiction / data class / sector / commitment), and what it\n governs — in the evidence's terms.\n- A regime the evidence EXCLUDES is not written as a constraint, and is not silently dropped either:\n where the creator's answers suggested it, the statement of a neighbouring constraint may note the\n exclusion so the decision is legible.\n- A trigger the evidence could NOT establish becomes a constraint stating the OPEN QUESTION, never a\n guessed answer — an unestablished regime stated as settled is the defect this composite exists to\n end.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read current journey state and\n scope before deriving, and to see the `vision-brief` (and its existing\n compliance constraints) you refine.\n",
|
|
33
|
+
"guidance": "# Compliance Posture — Derivation 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.** The regime-derivation rubric below\n> (which triggers imply which regime, how much to capture) is a deliberately\n> explicit first cut meant to be tuned against real runs. Treat it as a\n> starting rubric, not a frozen contract. Crucially, it derives compliance\n> **posture at scaffold depth** — prose constraints, not a per-regime\n> obligation model.\n\n## What this playbook does\n\nYou determine the product's **compliance posture** — which regulatory regimes\nit must be built to satisfy — and record each as a `compliance`-kind constraint\non the existing vision. The vision-elicitation step already named the\ncompliance _seam_ in passing (a single \"we handle EU personal data\" line). Your\njob is the focused, deliberate pass over that seam: reason from the product's\njurisdictions, the classes of data it handles, and its sector to the concrete\nset of regimes, and write each one down as its own constraint with a clear\nprose statement.\n\nYou do **not** re-elicit the whole vision, design the domain, or draft\nrequirements. You touch exactly one slice of the `VisionSnapshot`: its\n`constraints[]` entries of `kind: compliance`. Everything else on the snapshot\n— the idea, the problem, the mission, the success criteria, the\nnon-compliance constraints — you leave exactly as you found it.\n\n## The scaffold-depth boundary (read this before you start)\n\nAt this stage compliance is captured as **prose constraints only**. Each\napplicable regime becomes one constraint entry whose `statement` names the\nregime and the data / jurisdiction it governs — e.g. _\"Must be GDPR-compliant\nfor EU/EEA customer personal data.\"_ That is the whole deliverable.\n\nDo **not** build, and do not try to author into the snapshot:\n\n- per-regime control catalogs or obligation graphs (legal-article mappings,\n sector safeguards, external-assurance criteria),\n- data-flow / residency matrices,\n- retention schedules, DPA registries, or audit-config derivations.\n\nThat deep per-regime obligation model is a deliberately deferred later concern.\nIf you catch yourself modelling controls or obligations, **stop** — you have\nleft scaffold depth. Naming the regime seam accurately here is exactly what\nlets that later, deeper step engage. Getting the _set of applicable regimes_\nright, in prose, is the win.\n\n### Transition to structured compliance conception\n\nThis playbook does not write the dedicated `compliance-program` family. Its\naccepted vision constraints are precursor facts for a later, separately\napproved compliance-conception step. That step may initialize or revise the\noptional structured family only after it resolves exact source versions and\nrights records, declarative application scope, applicability authority, Wildo\nobjective bindings, implementation choices, responsibilities, documentation\nrequirements and explicit gaps.\n\nThe transition is not an automatic conversion and must not reinterpret a\nvision sentence as a control mapping or positive compliance claim. Preserve\nthe vision constraint as product intent, record any missing detail as\n`UNDETERMINED` or an explicit gap, and accept the structured family through the\nnormal semantic-delta authority. Runtime organizations, assignees, evidence,\ncontrol occurrences and assessments remain outside both artifacts.\n\n## The derivation posture\n\n- **Derive, then confirm — do not just transcribe.** The typed questions on\n this playbook (`method.elicitation`) gather the raw triggers: jurisdictions,\n data classes, sector, and direct yes/no reads on the common regimes. Your\n value is reasoning from those triggers to the regime set, then reflecting\n each derived regime back to the creator for confirmation. If EU users +\n personal data are present, GDPR applies whether or not the creator named it;\n surface that, don't wait to be told.\n- **Regime derivation rubric (v1).** Use these as the starting triggers, and\n follow up where an answer is thin:\n - **GDPR / UK GDPR** — serving EU/EEA (or UK) individuals, or processing\n their personal data. Triggered by jurisdiction (EU/EEA/UK) + any personal\n data.\n - **HIPAA** — handling US protected health information as, or on behalf of, a\n covered entity or business associate. Triggered by health data + US\n healthcare context.\n - **External assurance commitments** — enterprise customers or the product's own security posture\n require an independent attestation or certification over security / availability /\n confidentiality. Often contractual rather than statutory — capture the requested target as\n externally supplied source metadata when the go-to-market depends on it.\n - **Data residency / sovereignty** — a requirement that certain data stay\n within a region or country. Triggered by residency answers or sector rules;\n record as its own compliance constraint even when it rides alongside GDPR.\n - **Sector & additional regimes** — payment-card, consumer-privacy, children's-data,\n government-security, contractual-assurance and sector-code obligations. Add each that\n the triggers imply; preserve the exact named source only in the later source registry.\n - When the triggers are genuinely absent (no personal data, no regulated\n sector), the honest posture is _no compliance constraints_ — say so and add\n none. Do not invent a regime to look thorough.\n- **One regime, one constraint.** Keep regimes as separate constraint entries\n rather than one omnibus \"must be compliant\" line — the set is read\n downstream, and a merged statement loses which regimes are actually in play.\n\n## What you emit\n\nYou refine the **existing** `VisionSnapshot` in place. Concretely, you\nadd or update entries in `constraints[]`:\n\n- Each applicable regime is one entry with `kind: compliance`.\n- Each entry has a stable kebab-case `ref` prefixed `constraint-`\n (e.g. `constraint-gdpr-eu-personal-data`,\n `constraint-hipaa-us-phi`, `constraint-external-assurance-security`,\n `constraint-data-residency-eu`), unique across the whole `constraints[]` set.\n- Each entry's `statement` is a prose sentence naming the regime and the data /\n jurisdiction it governs. Where the creator gave the source of the limit\n (a customer contract, a specific law), capture it as the constraint's\n rationale.\n\nLeave every non-`compliance` constraint, and every other vision entity,\nuntouched.\n\n**Idempotent — refine, do not duplicate.** Read the vision first. If compliance\nconstraints already exist (the vision-elicitation step, or a prior run of this\nplaybook, may have written some), reconcile against them: update a statement\nthat is now sharper, add a regime that was missed, and remove one only if the\ncreator confirms it never applied. **Match existing constraints by the REGIME\ntheir `statement` names, not by their `ref` slug** — the vision-elicitation step\nwrites compliance prose without following this playbook's ref convention, so a\nGDPR line it left may sit under any slug (`constraint-gdpr`,\n`constraint-eu-data`, …). When you refine a regime that is already present,\n**reuse that entry's existing `ref`** so it updates in place rather than\nforking; only mint a fresh `constraint-<regime>-<scope>` slug for a regime that\nis genuinely new. Re-running this playbook on an already-posture'd vision must\nconverge to one entry per regime, never accumulate near-duplicate\n`constraint-gdpr-*` entries.\n\n## Quality gate\n\nYour refined snapshot is checked by the deterministic `vision-snapshot-valid`\ngate (`validateVisionSnapshot`) before it commits — the same gate the\nvision-elicitation step uses, because you write to the same family. Duplicate\nrefs and malformed refs (a constraint ref that is not kebab-case with the\n`constraint-` prefix) are hard **errors**; the gate rejects them. Emit clean,\nunique refs the first time. Note that a vision with no compliance constraints\nis perfectly valid — an honestly unregulated product should pass the gate with\nnone.\n\n## Approval\n\nThe refined `VisionSnapshot` is presented to the creator for approval before it\nbecomes the committed `vision-brief`. Show the derived compliance posture back\nin plain prose — the list of regimes, each with the data / jurisdiction it\ngoverns and why it applies — and let the creator confirm or correct it.\nCompliance drives real downstream engine capability, audit, and retention\nchoices, so it is worth one explicit human sign-off that the regime set is\nright.\n\n## Runtime context\n\nBefore you start, read the current journey state and scope, and read the\nexisting vision so you refine its compliance constraints rather than writing a\nfresh, disconnected set.\n\n// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)\n// TODO CLI COMMAND: wildo context vision-brief (read the existing vision + its current constraints)\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read current journey state and\n scope before deriving, and to see the `vision-brief` (and its existing\n compliance constraints) you refine.\n",
|
|
38
34
|
"skillRefs": [
|
|
39
35
|
"journey-status"
|
|
40
36
|
],
|
|
41
|
-
"
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
37
|
+
"elicitation": {
|
|
38
|
+
"questions": [
|
|
39
|
+
{
|
|
40
|
+
"ref": "handles-regulated-data",
|
|
41
|
+
"question": "Does the product store, process, or transmit personal data or otherwise regulated data (health, financial, biometric, children's, government) — either from end users or on behalf of customers?",
|
|
42
|
+
"kind": "confirm"
|
|
43
|
+
},
|
|
44
|
+
{
|
|
45
|
+
"ref": "data-classes",
|
|
46
|
+
"question": "Which classes of sensitive data does the product touch? List them (e.g. names/emails, health records, payment card data, government IDs, precise location, employee data). Answer \"none\" if it handles no personal or sensitive data.",
|
|
47
|
+
"kind": "free_text"
|
|
48
|
+
},
|
|
49
|
+
{
|
|
50
|
+
"ref": "jurisdictions",
|
|
51
|
+
"question": "In which jurisdictions do your users live and your data reside or transit (e.g. EU/EEA, UK, US, California, Canada, specific countries)? This is what drives which privacy regimes apply.",
|
|
52
|
+
"kind": "free_text"
|
|
53
|
+
},
|
|
54
|
+
{
|
|
55
|
+
"ref": "sector",
|
|
56
|
+
"question": "Does the product operate in a regulated sector with its own rules (healthcare, finance/banking, insurance, education, government, telecoms)? Name the sector, or answer \"none\".",
|
|
57
|
+
"kind": "free_text"
|
|
58
|
+
},
|
|
59
|
+
{
|
|
60
|
+
"ref": "gdpr-applies",
|
|
61
|
+
"question": "Do you serve EU/EEA (or UK) individuals or process their personal data? (This is the primary trigger for GDPR / UK GDPR.)",
|
|
62
|
+
"kind": "confirm"
|
|
63
|
+
},
|
|
64
|
+
{
|
|
65
|
+
"ref": "hipaa-applies",
|
|
66
|
+
"question": "Do you handle US protected health information as, or on behalf of, a covered entity or business associate? (This is the primary trigger for HIPAA.)",
|
|
67
|
+
"kind": "confirm"
|
|
68
|
+
},
|
|
69
|
+
{
|
|
70
|
+
"ref": "external-assurance-applies",
|
|
71
|
+
"question": "Do enterprise customers (or your own security posture) require an independent attestation or certification covering security / availability / confidentiality of the service? Name the requested target only as an external source requirement.",
|
|
72
|
+
"kind": "confirm"
|
|
73
|
+
},
|
|
74
|
+
{
|
|
75
|
+
"ref": "data-residency",
|
|
76
|
+
"question": "Are there data-residency or sovereignty requirements — must certain data stay within a region or country (e.g. EU-only hosting, in-country storage)? Describe them, or answer \"none\".",
|
|
77
|
+
"kind": "free_text"
|
|
78
|
+
},
|
|
79
|
+
{
|
|
80
|
+
"ref": "additional-regimes",
|
|
81
|
+
"question": "Any other legal regimes, sector frameworks, government programs, or contractual security commitments that apply? List the externally named sources, or answer \"none\".",
|
|
82
|
+
"kind": "free_text"
|
|
83
|
+
}
|
|
84
|
+
]
|
|
85
|
+
}
|
|
45
86
|
},
|
|
46
87
|
"executor": "companion_agent",
|
|
88
|
+
"qualityGates": [
|
|
89
|
+
{
|
|
90
|
+
"ref": "vision-snapshot-valid",
|
|
91
|
+
"kind": "deterministic_validator",
|
|
92
|
+
"validatorRef": "saas-specifications:validateVisionSnapshot",
|
|
93
|
+
"required": true
|
|
94
|
+
}
|
|
95
|
+
],
|
|
47
96
|
"approval": "approve_result",
|
|
48
97
|
"budget": {
|
|
49
98
|
"maxRuns": 3
|
|
@@ -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,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1}],"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. 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, or presents unsupported claims as truth.","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-
|
|
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,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1}],"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. 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, or presents unsupported claims as truth.","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-analysis"},"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}],"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":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1}],"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. 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, or presents unsupported claims as truth.","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-
|
|
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}],"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":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1}],"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. 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, or presents unsupported claims as truth.","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-analysis"},"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":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/accepted-vision-research-and-market-candidate"}],"schemaVersion":1}
|