@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
|
@@ -1,10 +1,14 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.scope-roadmap",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
5
|
"intent": "Turn the accepted capability map into a non-vacuous current-horizon RoadmapSnapshot. Phases explicitly sequence and group accepted requirements and vision success criteria without pretending that FIT is build-order authority or inventing unsupported delivery commitments.",
|
|
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,9 +44,6 @@
|
|
|
40
44
|
{
|
|
41
45
|
"family": "requirements"
|
|
42
46
|
},
|
|
43
|
-
{
|
|
44
|
-
"family": "roadmap"
|
|
45
|
-
},
|
|
46
47
|
{
|
|
47
48
|
"family": "vision-brief"
|
|
48
49
|
}
|
|
@@ -51,12 +52,12 @@
|
|
|
51
52
|
{
|
|
52
53
|
"family": "roadmap",
|
|
53
54
|
"schemaRef": "saas-specifications:RoadmapSnapshot",
|
|
55
|
+
"placement": ".wildo-saas/journey/<journeyId>/roadmap/",
|
|
54
56
|
"description": "A validated ordered roadmap whose phases bind current-horizon requirements and success criteria."
|
|
55
57
|
}
|
|
56
58
|
],
|
|
57
|
-
"stepOutputs": [],
|
|
58
59
|
"method": {
|
|
59
|
-
"guidance": "# Scope & Roadmap — Capability Map → Release Plan 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 phasing order, the MVP-first rubric, and the in/out-of-scope\n> convention below are deliberately explicit so they can be tuned against real\n> runs — treat them as a starting rubric, not a frozen contract. The\n> *analytical depth* of release planning (typed schedules, dependency graphs,\n> capacity/estimation, defended prioritization) is intentionally shallow here\n> and is deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **release planner**. This playbook turns *product capability* (the\nfeatures the capability map identified and the requirements behind them) into a\n**release plan**: an ordered set of roadmap **phases** (MVP → Beta → GA →\nGrowth) that declare **what gets delivered when**. Capability mapping already\nproduced a **MarketSnapshot** whose benefits are wired to delivering features,\nplus **feature-drafts** and a set of **requirements**. Your one job is to answer,\nfor the whole product: **in what order do we deliver this, and what is in vs out\nof scope for each release?** — and record the answer as a `RoadmapSnapshot`.\n\nYou produce ONE artifact for this journey: the **roadmap** family\n(`RoadmapSnapshot`), a single ordered `phases` collection.\n\nThis is a **focused planning pass**, distinct from the capability map (which\nmade each benefit deliverable and drafted the features) and from the phase-gate\n(which decides whether the top-down phase is complete). Where the capability map\nsaid *what the product must do*, you say *in what order it ships*.\n\n## The roadmap is requirement/success-criterion-addressed, NOT feature-addressed\n\nRead this before you start — it is the one structural fact that shapes the whole\nmethod. A roadmap phase declares what it delivers through **two flat cross-ref\nlists**:\n\n- **`deliversRequirementRefs`** — the requirement refs (from the `requirements`\n family) this phase delivers. Primarily **functional-requirement** refs\n (`functional-requirement-…`) — the case the `_core` phase contract narrates —\n but a phase that lands a quality attribute may also deliver a **non-functional**\n ref (`nfr-…`); the catalog resolves both against one combined requirement-ref\n pool, so an NFR ref is valid here (see the NFR-phasing boundary note).\n- **`deliversSuccessCriterionRefs`** — the vision success-criterion refs (from\n the `vision-brief` family) this phase is expected to satisfy.\n\nA phase does **not** name feature refs. So the capability map's **features reach\nthe roadmap indirectly**: feature → benefit → requirement → phase. You slot\n**requirements and success criteria** into phases; you use the capability map\n(which feature delivers which benefit, and the FIT/Kano read on the feature set)\nto **judge which requirements are MVP-critical vs later**. The feature →\nrequirement trace is **prose-only today** (a requirement cross-refs ICPs and jobs\nbut not market pains/gains, and there is no typed feature → requirement edge —\nthis is the filed depth-phase gap; see the scaffold-depth boundary). At scaffold\ndepth you bridge that trace by reading the capability map and the requirements\ntogether and using judgement — do **not** try to make it deterministic here.\n\n## Read state first — the four families you read, the one you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*: a MarketSnapshot\nmust already exist (the `artifact_exists` precondition enforces the capability map\nis in place — you cannot plan releases before you know the capabilities). Before\nplanning anything:\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). Confirm a `market-snapshot`\n exists and check whether a `roadmap` already exists from an earlier run.\n2. Read the capability-mapped **MarketSnapshot** (benefits + their\n `deliveredByFeatureRefs` + FIT/Kano signal), the **feature-drafts** (the prose\n capability contracts — what each delivering feature actually is, so you can\n weigh how much of the product a requirement pulls in and whether it is\n MVP-critical), the **requirements** (`requirements` family — the\n functional/non-functional requirements to slot into phases), and the\n **VisionSnapshot** (`vision-brief` — the success criteria to deliver and the\n differentiation that anchors what belongs in the MVP).\n\n(A previously landed roadmap arrives in your brief as the `roadmap` input section — refine those\nphases rather than re-cutting them blind.)\n\nYou **read** `market-snapshot` + `feature-drafts` + `requirements` +\n`vision-brief`; you **write** the `roadmap` family.\n\n## The phasing loop (build the ordered releases)\n\n1. **Establish the MVP cut first.** The first phase is the smallest coherent\n release that makes the product's core promise true. Pull in the requirements\n whose delivering features are **table-stakes** for the primary ICP — the\n capability map's FIT/Kano read surfaces these (a `THRESHOLD` benefit for a\n `CORE`/`EXPANSION` ICP is MVP-critical). A requirement whose benefit is a\n `DELIGHTER`, or serves a non-primary segment, is a candidate for a later\n phase, not the MVP. MVP-first is the scaffold rubric: deliver the differentiated\n core early, defer the upside.\n2. **Group the remaining work into ordered later phases.** Beta / GA / Growth\n stages each pull in the next coherent slice of requirements and success\n criteria. Group by *theme* (a phase has a narrative headline — \"Trust &\n safety\", \"Onboarding excellence\"), not by arbitrary size.\n3. **Assign each phase its ordering + coarse tags.**\n - **`sequence`** — the authoritative ordering key (ascending integer).\n Consumers sort by `sequence`, never by array position. Author with **gaps**\n (10, 20, 30) so a later phase can be inserted without renumbering. Every\n phase must have a **distinct** `sequence` (a shared sequence is a\n `DUPLICATE_SEQUENCE` WARN — the order becomes ambiguous).\n - **`horizon`** — coarse `NOW` / `NEXT` / `LATER` bucket (`RoadmapPhaseHorizon`).\n - **`kind`** — coarse lifecycle stage `DISCOVERY` / `MVP` / `BETA` / `GA` /\n `GROWTH` / `OTHER` (`RoadmapPhaseKind`).\n - **`title`** (required), plus optional `theme` (narrative angle),\n `objective` (the concrete outcome in prose), and `targetWindow` (WHEN, as\n **free prose** — \"Q3 2026\", \"first 3 months post-launch\"; a typed schedule\n is a later-phase concern).\n4. **Wire what each phase delivers.** Populate `deliversRequirementRefs` with the\n requirement refs (functional, and any non-functional quality the phase lands)\n the phase delivers, and `deliversSuccessCriterionRefs` with the vision\n success-criterion refs it satisfies. **Every requirement and every success\n criterion should land in at most one phase** — the earliest that delivers it.\n Two distinct duplication cases exist, and the gate catches only one:\n - **Same ref twice on ONE phase's list** → a `DUPLICATE_CROSS_REF` WARN. The\n gate catches this (each of the two lists is its own namespace, so the same\n string appearing once in each list is NOT flagged).\n - **Same ref on TWO different phases** → the gate does **NOT** catch this — the\n validator's duplicate check is per-list, per-phase, never cross-phase. It is\n silently wrong: coverage double-counts the ref and \"which release first\n delivers it\" becomes ambiguous. Keeping a ref in exactly one phase is an\n **authoring discipline**, not a gate-enforced invariant.\n5. **Sanity-check coverage.** By the last phase, every requirement whose benefit\n the product actually promises, and every vision success criterion, should be\n delivered by some phase. A requirement no phase delivers is out-of-scope of the\n *entire roadmap* — that is a real decision (it says \"the product will not do\n this\"), so make it deliberately and narrate it, do not leave it by accident.\n\n## In-scope vs out-of-scope per release (the scope decision)\n\nThe roadmap `_core` has **no typed out-of-scope axis** — a phase declares only\nwhat it **delivers**. So scope is modelled as follows at scaffold depth:\n\n- **In-scope of a release = its `delivers*` refs.** The `deliversRequirementRefs`\n + `deliversSuccessCriterionRefs` a phase carries ARE its declared, gate-checked\n in-scope. This is explicit and typed.\n- **Out-of-scope of a release is implicit + partly derivable.** Everything NOT\n yet delivered by a phase at or before this one is out-of-scope of that release\n (cumulative — a ref delivered by an earlier phase stays in-scope in every later\n one). Within that out-of-scope set, two sub-cases ARE derivable from the roadmap\n alone: *deferred* (some later phase delivers the ref → planned, just not yet)\n vs *never* (NO phase anywhere delivers the ref → out of the product).\n- **What is NOT derivable — and therefore needs prose.** The roadmap cannot\n distinguish a *deliberately excluded* requirement (\"we chose not to build SSO\")\n from an *accidentally dropped* one (\"we forgot to slot it\"): both surface\n identically — a requirement authored in the `requirements` family that no phase\n delivers. That single ambiguity is the entire cost of Option A. So record the\n **rationale** for every deliberate \"never\" in the phase `objective` / `theme`\n **prose** (\"Out of scope for MVP: bulk import, SSO — deferred to GA\"; \"Not in\n the product: on-prem hosting — SaaS-only by design\"), and run the coverage\n sanity-check (step 5 above) so an accidental drop is caught rather than shipped\n as a phantom exclusion.\n\nRejected alternatives:\n\n- A **typed out-of-scope / explicitly-deferred axis** on a phase (a\n `defersRequirementRefs` list, or an `outOfScope` block). It is the real fix for\n the ambiguity above — it makes \"deliberately never\" machine-readable — but it is\n a `_core/roadmap` reshape, filed as a depth-phase item, NOT built here. Do\n **not** reshape the roadmap contract to add it.\n- A **phantom \"out-of-scope\" phase** — a phase whose `deliversRequirementRefs`\n lists the *excluded* requirements to fake a machine-readable exclusion set. Do\n **NOT** do this. A phase *delivers* its refs by definition; listing excluded\n refs there inverts the semantics and **corrupts every downstream coverage\n count** (those refs would read as delivered, and the phase-gate / refinement\n playbooks would treat excluded work as shipped). This is exactly the kind of\n \"trick\" the framework mindset forbids — the excluded set stays in prose until\n the typed axis lands, never by abusing `delivers*`.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not renumber or re-theme phases that\n are already correct. Only add a phase, move a requirement to a different phase,\n or correct a delivers-list where the plan genuinely changed.\n- **Reuse existing phase refs.** A phase that already exists keeps its\n `roadmap-phase-<slug>` ref — never mint a second ref for the same release. Refs\n are unique (a `DUPLICATE_REF` is an ERROR that silently drops a phase).\n- **Never orphan a deliver-ref.** A phase's `deliversRequirementRefs` /\n `deliversSuccessCriterionRefs` must name refs that exist in the requirements /\n vision families. These cross-family refs are resolution-checked **fail-soft**\n (the check is skipped while the families are decoupled and no ref set is\n supplied), so honest planning must not name a requirement or success criterion\n that does not exist in the first place.\n- **Each ref in at most one phase.** A requirement/success-criterion is delivered\n by the earliest phase that delivers it; do not re-list it in later phases.\n\n## Quality gate\n\nThe RoadmapSnapshot is checked by the deterministic `roadmap-valid` gate\n(`validateRoadmapSnapshot`) before anything downstream consumes it. The invariants\nit enforces (verified issue catalogue):\n\n- **`INVALID_REF_FORMAT` (ERROR)** — a phase ref is not kebab-case with the\n `roadmap-phase-` prefix.\n- **`DUPLICATE_REF` (ERROR)** — two phases share a ref; the collection is\n addressed by ref, so a duplicate silently drops a phase.\n- **`DUPLICATE_SEQUENCE` (WARN)** — two phases share a `sequence`; the order\n between them is ambiguous (no data lost, so a WARN). Give each phase a distinct\n `sequence`.\n- **`DUPLICATE_CROSS_REF` (WARN)** — the same deliver-ref is listed more than\n once on ONE phase's deliver-list (each of the two lists is its own namespace, so\n the same ref appearing once in each list is NOT a duplicate). Remove the repeat.\n- **`NO_PHASES` (WARN)** — the roadmap plans no phases; it describes no delivery.\n- **`STALE_AUTHORED` (WARN)** — a phase's `authored.lastAuthoredAt` is older than\n its `reviewCadence`.\n- **`UNKNOWN_REQUIREMENT_REF` / `UNKNOWN_SUCCESS_CRITERION_REF` (ERROR, fail-soft)**\n — a `deliversRequirementRefs` / `deliversSuccessCriterionRefs` entry does not\n resolve against a supplied ref set. These are **SKIPPED (fail-soft) when no ref\n set is passed** — the roadmap family is decoupled from the requirements/vision\n families and the catalog owns cross-family resolution, so authoring a roadmap\n before those registries are fully wired does NOT crash-loop. Even so, only name\n refs that really exist (see \"Never orphan a deliver-ref\").\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- **Typed timeline / scheduling.** `targetWindow` is free prose and ordering is a\n coarse `sequence` integer. Start/end dates, date math, and calendar alignment\n are a later-phase concern — a phase says \"first 3 months post-launch\" as prose\n today, not a typed interval. Do NOT build a schedule model.\n- **Inter-phase dependency graph.** Phases are an ordered list, not a DAG. Edges\n between phases (phase B needs phase A's delivery) are a later-phase concern.\n- **Capacity / velocity / estimation and prioritization frameworks.** A phase is a\n themed bucket of deliver-refs, not an estimated, capacity-fitted, RICE/WSJF/MoSCoW-\n ranked plan. If you catch yourself estimating effort or building a prioritization\n model, **stop** — that is depth-phase work.\n- **A typed out-of-scope / explicitly-deferred axis** (see the scope decision\n above) — a `_core/roadmap` reshape, filed as a depth-phase item, not built here.\n- **Requirement priority + inter-requirement dependency.** A requirement has no\n MoSCoW/priority axis and no \"requirement A needs B\" edge; only the roadmap\n `sequence` approximates ordering. Do NOT reshape the requirements contract to add\n them — it is a filed depth-phase question.\n- **A dedicated non-functional-requirement delivery axis.** `deliversRequirementRefs`\n today carries functional AND non-functional refs against one combined pool. Some\n NFRs are cross-cutting quality attributes (accessibility, latency) that no single\n phase \"delivers\" — whether NFRs deserve their own phase-delivery axis (or a\n per-phase quality bar) rather than sharing `deliversRequirementRefs` is a\n depth-phase question. At scaffold depth, slot a phase-specific NFR into\n `deliversRequirementRefs` and leave universal NFRs unphased; do NOT reshape\n `_core` for a separate axis here.\n- **Per-phase ICP/segment targeting.** A phase cannot declare the primary\n ICP/segment it serves; that is a filed depth-phase gap. Note it in prose if it\n matters; do NOT reshape `_core` to add a typed edge.\n- **Deterministic feature → phase traceability.** Because a requirement carries no\n typed market pain/gain edge (and no typed feature → requirement edge), the\n feature → benefit → requirement → phase trace is prose-only. Whether the\n requirements family should gain a pain/gain edge is a filed depth-phase question —\n do NOT reshape the requirements or roadmap 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\nOne artifact for this journey: the **roadmap** at\n`specifications/src/roadmap/index.ts` — a `RoadmapSnapshot` whose `phases`\nare the ordered, MVP-first releases, each with a distinct `sequence`, a coarse\n`horizon` + `kind`, and its `deliversRequirementRefs` / `deliversSuccessCriterionRefs`\nwired — passing the `roadmap-valid` gate.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's roadmap.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and\n scope, and confirm a `market-snapshot` (the capability map) already exists to\n plan releases from.\n",
|
|
60
|
+
"guidance": "# Scope & Roadmap — Capability Map → Release Plan 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 phasing order, the MVP-first rubric, and the in/out-of-scope\n> convention below are deliberately explicit so they can be tuned against real\n> runs — treat them as a starting rubric, not a frozen contract. The\n> *analytical depth* of release planning (typed schedules, dependency graphs,\n> capacity/estimation, defended prioritization) is intentionally shallow here\n> and is deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **release planner**. This playbook turns *product capability* (the\nfeatures the capability map identified and the requirements behind them) into a\n**release plan**: an ordered set of roadmap **phases** (MVP → Beta → GA →\nGrowth) that declare **what gets delivered when**. Capability mapping already\nproduced a **MarketSnapshot** whose benefits are wired to delivering features,\nplus **feature-drafts** and a set of **requirements**. Your one job is to answer,\nfor the whole product: **in what order do we deliver this, and what is in vs out\nof scope for each release?** — and record the answer as a `RoadmapSnapshot`.\n\nYou produce ONE artifact for this journey: the **roadmap** family\n(`RoadmapSnapshot`), a single ordered `phases` collection.\n\nThis is a **focused planning pass**, distinct from the capability map (which\nmade each benefit deliverable and drafted the features) and from the phase-gate\n(which decides whether the top-down phase is complete). Where the capability map\nsaid *what the product must do*, you say *in what order it ships*.\n\n## The roadmap is requirement/success-criterion-addressed, NOT feature-addressed\n\nRead this before you start — it is the one structural fact that shapes the whole\nmethod. A roadmap phase declares what it delivers through **two flat cross-ref\nlists**:\n\n- **`deliversRequirementRefs`** — the requirement refs (from the `requirements`\n family) this phase delivers. Primarily **functional-requirement** refs\n (`functional-requirement-…`) — the case the `_core` phase contract narrates —\n but a phase that lands a quality attribute may also deliver a **non-functional**\n ref (`nfr-…`); the catalog resolves both against one combined requirement-ref\n pool, so an NFR ref is valid here (see the NFR-phasing boundary note).\n- **`deliversSuccessCriterionRefs`** — the vision success-criterion refs (from\n the `vision-brief` family) this phase is expected to satisfy.\n\nA phase does **not** name feature refs. So the capability map's **features reach\nthe roadmap indirectly**: feature → benefit → requirement → phase. You slot\n**requirements and success criteria** into phases; you use the capability map\n(which feature delivers which benefit, and the FIT/Kano read on the feature set)\nto **judge which requirements are MVP-critical vs later**. The feature →\nrequirement trace is **prose-only today** (a requirement cross-refs ICPs and jobs\nbut not market pains/gains, and there is no typed feature → requirement edge —\nthis is the filed depth-phase gap; see the scaffold-depth boundary). At scaffold\ndepth you bridge that trace by reading the capability map and the requirements\ntogether and using judgement — do **not** try to make it deterministic here.\n\n## Read state first — the four families you read, the one you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*: a MarketSnapshot\nmust already exist (the `artifact_exists` precondition enforces the capability map\nis in place — you cannot plan releases before you know the capabilities). Before\nplanning anything:\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). Confirm a `market-snapshot`\n exists and check whether a `roadmap` already exists from an earlier run.\n2. Read the capability-mapped **MarketSnapshot** (benefits + their\n `deliveredByFeatureRefs` + FIT/Kano signal), the **feature-drafts** (the prose\n capability contracts — what each delivering feature actually is, so you can\n weigh how much of the product a requirement pulls in and whether it is\n MVP-critical), the **requirements** (`requirements` family — the\n functional/non-functional requirements to slot into phases), and the\n **VisionSnapshot** (`vision-brief` — the success criteria to deliver and the\n differentiation that anchors what belongs in the MVP).\n\n// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)\n// TODO CLI COMMAND: wildo context roadmap (read any existing phases to refine)\n\nYou **read** `market-snapshot` + `feature-drafts` + `requirements` +\n`vision-brief`; you **write** the `roadmap` family.\n\n## The phasing loop (build the ordered releases)\n\n1. **Establish the MVP cut first.** The first phase is the smallest coherent\n release that makes the product's core promise true. Pull in the requirements\n whose delivering features are **table-stakes** for the primary ICP — the\n capability map's FIT/Kano read surfaces these (a `THRESHOLD` benefit for a\n `CORE`/`EXPANSION` ICP is MVP-critical). A requirement whose benefit is a\n `DELIGHTER`, or serves a non-primary segment, is a candidate for a later\n phase, not the MVP. MVP-first is the scaffold rubric: deliver the differentiated\n core early, defer the upside.\n2. **Group the remaining work into ordered later phases.** Beta / GA / Growth\n stages each pull in the next coherent slice of requirements and success\n criteria. Group by *theme* (a phase has a narrative headline — \"Trust &\n safety\", \"Onboarding excellence\"), not by arbitrary size.\n3. **Assign each phase its ordering + coarse tags.**\n - **`sequence`** — the authoritative ordering key (ascending integer).\n Consumers sort by `sequence`, never by array position. Author with **gaps**\n (10, 20, 30) so a later phase can be inserted without renumbering. Every\n phase must have a **distinct** `sequence` (a shared sequence is a\n `DUPLICATE_SEQUENCE` WARN — the order becomes ambiguous).\n - **`horizon`** — coarse `NOW` / `NEXT` / `LATER` bucket (`RoadmapPhaseHorizon`).\n - **`kind`** — coarse lifecycle stage `DISCOVERY` / `MVP` / `BETA` / `GA` /\n `GROWTH` / `OTHER` (`RoadmapPhaseKind`).\n - **`title`** (required), plus optional `theme` (narrative angle),\n `objective` (the concrete outcome in prose), and `targetWindow` (WHEN, as\n **free prose** — \"Q3 2026\", \"first 3 months post-launch\"; a typed schedule\n is a later-phase concern).\n4. **Wire what each phase delivers.** Populate `deliversRequirementRefs` with the\n requirement refs (functional, and any non-functional quality the phase lands)\n the phase delivers, and `deliversSuccessCriterionRefs` with the vision\n success-criterion refs it satisfies. **Every requirement and every success\n criterion should land in at most one phase** — the earliest that delivers it.\n Two distinct duplication cases exist, and the gate catches only one:\n - **Same ref twice on ONE phase's list** → a `DUPLICATE_CROSS_REF` WARN. The\n gate catches this (each of the two lists is its own namespace, so the same\n string appearing once in each list is NOT flagged).\n - **Same ref on TWO different phases** → the gate does **NOT** catch this — the\n validator's duplicate check is per-list, per-phase, never cross-phase. It is\n silently wrong: coverage double-counts the ref and \"which release first\n delivers it\" becomes ambiguous. Keeping a ref in exactly one phase is an\n **authoring discipline**, not a gate-enforced invariant.\n5. **Sanity-check coverage.** By the last phase, every requirement whose benefit\n the product actually promises, and every vision success criterion, should be\n delivered by some phase. A requirement no phase delivers is out-of-scope of the\n *entire roadmap* — that is a real decision (it says \"the product will not do\n this\"), so make it deliberately and narrate it, do not leave it by accident.\n\n## In-scope vs out-of-scope per release (the scope decision)\n\nThe roadmap `_core` has **no typed out-of-scope axis** — a phase declares only\nwhat it **delivers**. So scope is modelled as follows at scaffold depth:\n\n- **In-scope of a release = its `delivers*` refs.** The `deliversRequirementRefs`\n + `deliversSuccessCriterionRefs` a phase carries ARE its declared, gate-checked\n in-scope. This is explicit and typed.\n- **Out-of-scope of a release is implicit + partly derivable.** Everything NOT\n yet delivered by a phase at or before this one is out-of-scope of that release\n (cumulative — a ref delivered by an earlier phase stays in-scope in every later\n one). Within that out-of-scope set, two sub-cases ARE derivable from the roadmap\n alone: *deferred* (some later phase delivers the ref → planned, just not yet)\n vs *never* (NO phase anywhere delivers the ref → out of the product).\n- **What is NOT derivable — and therefore needs prose.** The roadmap cannot\n distinguish a *deliberately excluded* requirement (\"we chose not to build SSO\")\n from an *accidentally dropped* one (\"we forgot to slot it\"): both surface\n identically — a requirement authored in the `requirements` family that no phase\n delivers. That single ambiguity is the entire cost of Option A. So record the\n **rationale** for every deliberate \"never\" in the phase `objective` / `theme`\n **prose** (\"Out of scope for MVP: bulk import, SSO — deferred to GA\"; \"Not in\n the product: on-prem hosting — SaaS-only by design\"), and run the coverage\n sanity-check (step 5 above) so an accidental drop is caught rather than shipped\n as a phantom exclusion.\n\nRejected alternatives:\n\n- A **typed out-of-scope / explicitly-deferred axis** on a phase (a\n `defersRequirementRefs` list, or an `outOfScope` block). It is the real fix for\n the ambiguity above — it makes \"deliberately never\" machine-readable — but it is\n a `_core/roadmap` reshape, filed as a depth-phase item, NOT built here. Do\n **not** reshape the roadmap contract to add it.\n- A **phantom \"out-of-scope\" phase** — a phase whose `deliversRequirementRefs`\n lists the *excluded* requirements to fake a machine-readable exclusion set. Do\n **NOT** do this. A phase *delivers* its refs by definition; listing excluded\n refs there inverts the semantics and **corrupts every downstream coverage\n count** (those refs would read as delivered, and the phase-gate / refinement\n playbooks would treat excluded work as shipped). This is exactly the kind of\n \"trick\" the framework mindset forbids — the excluded set stays in prose until\n the typed axis lands, never by abusing `delivers*`.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not renumber or re-theme phases that\n are already correct. Only add a phase, move a requirement to a different phase,\n or correct a delivers-list where the plan genuinely changed.\n- **Reuse existing phase refs.** A phase that already exists keeps its\n `roadmap-phase-<slug>` ref — never mint a second ref for the same release. Refs\n are unique (a `DUPLICATE_REF` is an ERROR that silently drops a phase).\n- **Never orphan a deliver-ref.** A phase's `deliversRequirementRefs` /\n `deliversSuccessCriterionRefs` must name refs that exist in the requirements /\n vision families. These cross-family refs are resolution-checked **fail-soft**\n (the check is skipped while the families are decoupled and no ref set is\n supplied), so honest planning must not name a requirement or success criterion\n that does not exist in the first place.\n- **Each ref in at most one phase.** A requirement/success-criterion is delivered\n by the earliest phase that delivers it; do not re-list it in later phases.\n\n## Quality gate\n\nThe RoadmapSnapshot is checked by the deterministic `roadmap-valid` gate\n(`validateRoadmapSnapshot`) before anything downstream consumes it. The invariants\nit enforces (verified issue catalogue):\n\n- **`INVALID_REF_FORMAT` (ERROR)** — a phase ref is not kebab-case with the\n `roadmap-phase-` prefix.\n- **`DUPLICATE_REF` (ERROR)** — two phases share a ref; the collection is\n addressed by ref, so a duplicate silently drops a phase.\n- **`DUPLICATE_SEQUENCE` (WARN)** — two phases share a `sequence`; the order\n between them is ambiguous (no data lost, so a WARN). Give each phase a distinct\n `sequence`.\n- **`DUPLICATE_CROSS_REF` (WARN)** — the same deliver-ref is listed more than\n once on ONE phase's deliver-list (each of the two lists is its own namespace, so\n the same ref appearing once in each list is NOT a duplicate). Remove the repeat.\n- **`NO_PHASES` (WARN)** — the roadmap plans no phases; it describes no delivery.\n- **`STALE_AUTHORED` (WARN)** — a phase's `authored.lastAuthoredAt` is older than\n its `reviewCadence`.\n- **`UNKNOWN_REQUIREMENT_REF` / `UNKNOWN_SUCCESS_CRITERION_REF` (ERROR, fail-soft)**\n — a `deliversRequirementRefs` / `deliversSuccessCriterionRefs` entry does not\n resolve against a supplied ref set. These are **SKIPPED (fail-soft) when no ref\n set is passed** — the roadmap family is decoupled from the requirements/vision\n families and the catalog owns cross-family resolution, so authoring a roadmap\n before those registries are fully wired does NOT crash-loop. Even so, only name\n refs that really exist (see \"Never orphan a deliver-ref\").\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- **Typed timeline / scheduling.** `targetWindow` is free prose and ordering is a\n coarse `sequence` integer. Start/end dates, date math, and calendar alignment\n are a later-phase concern — a phase says \"first 3 months post-launch\" as prose\n today, not a typed interval. Do NOT build a schedule model.\n- **Inter-phase dependency graph.** Phases are an ordered list, not a DAG. Edges\n between phases (phase B needs phase A's delivery) are a later-phase concern.\n- **Capacity / velocity / estimation and prioritization frameworks.** A phase is a\n themed bucket of deliver-refs, not an estimated, capacity-fitted, RICE/WSJF/MoSCoW-\n ranked plan. If you catch yourself estimating effort or building a prioritization\n model, **stop** — that is depth-phase work.\n- **A typed out-of-scope / explicitly-deferred axis** (see the scope decision\n above) — a `_core/roadmap` reshape, filed as a depth-phase item, not built here.\n- **Requirement priority + inter-requirement dependency.** A requirement has no\n MoSCoW/priority axis and no \"requirement A needs B\" edge; only the roadmap\n `sequence` approximates ordering. Do NOT reshape the requirements contract to add\n them — it is a filed depth-phase question.\n- **A dedicated non-functional-requirement delivery axis.** `deliversRequirementRefs`\n today carries functional AND non-functional refs against one combined pool. Some\n NFRs are cross-cutting quality attributes (accessibility, latency) that no single\n phase \"delivers\" — whether NFRs deserve their own phase-delivery axis (or a\n per-phase quality bar) rather than sharing `deliversRequirementRefs` is a\n depth-phase question. At scaffold depth, slot a phase-specific NFR into\n `deliversRequirementRefs` and leave universal NFRs unphased; do NOT reshape\n `_core` for a separate axis here.\n- **Per-phase ICP/segment targeting.** A phase cannot declare the primary\n ICP/segment it serves; that is a filed depth-phase gap. Note it in prose if it\n matters; do NOT reshape `_core` to add a typed edge.\n- **Deterministic feature → phase traceability.** Because a requirement carries no\n typed market pain/gain edge (and no typed feature → requirement edge), the\n feature → benefit → requirement → phase trace is prose-only. Whether the\n requirements family should gain a pain/gain edge is a filed depth-phase question —\n do NOT reshape the requirements or roadmap 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\nOne artifact for this journey: the **roadmap** at\n`.wildo-saas/journey/<journeyId>/roadmap/` — a `RoadmapSnapshot` whose `phases`\nare the ordered, MVP-first releases, each with a distinct `sequence`, a coarse\n`horizon` + `kind`, and its `deliversRequirementRefs` / `deliversSuccessCriterionRefs`\nwired — passing the `roadmap-valid` gate.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's roadmap.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and\n scope, and confirm a `market-snapshot` (the capability map) already exists to\n plan releases from.\n",
|
|
60
61
|
"skillRefs": [
|
|
61
62
|
"journey-status"
|
|
62
63
|
],
|
|
@@ -73,13 +74,17 @@
|
|
|
73
74
|
"kind": "free_text"
|
|
74
75
|
}
|
|
75
76
|
]
|
|
76
|
-
}
|
|
77
|
-
"contextSources": [],
|
|
78
|
-
"suspendsForClarification": false,
|
|
79
|
-
"briefAdequacyGate": false,
|
|
80
|
-
"briefAdequacyExcludedSources": []
|
|
77
|
+
}
|
|
81
78
|
},
|
|
82
79
|
"executor": "companion_agent",
|
|
80
|
+
"qualityGates": [
|
|
81
|
+
{
|
|
82
|
+
"ref": "roadmap-valid",
|
|
83
|
+
"kind": "deterministic_validator",
|
|
84
|
+
"validatorRef": "saas-specifications:validateRoadmapSnapshot",
|
|
85
|
+
"required": true
|
|
86
|
+
}
|
|
87
|
+
],
|
|
83
88
|
"approval": "approve_result",
|
|
84
89
|
"budget": {
|
|
85
90
|
"maxRuns": 3
|
|
@@ -91,7 +91,7 @@ invent a promise the product does not stand behind.
|
|
|
91
91
|
## Where the snapshot lives
|
|
92
92
|
|
|
93
93
|
The MarketSnapshot for this journey is at
|
|
94
|
-
|
|
94
|
+
`.wildo-saas/journey/<journeyId>/market-snapshot/`. That is the artifact this
|
|
95
95
|
playbook refines in place — you read it, sharpen the value-proposition slices,
|
|
96
96
|
and write the same artifact back. When the product's definition later
|
|
97
97
|
stabilises, the snapshot is what seeds the durable market specification under
|
|
@@ -111,6 +111,8 @@ it). Before sharpening anything:
|
|
|
111
111
|
VisionSnapshot at the `vision-brief` placement, so you sharpen against the
|
|
112
112
|
real market intent and the real differentiation, not from scratch.
|
|
113
113
|
|
|
114
|
+
// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)
|
|
115
|
+
// TODO CLI COMMAND: wildo context market-snapshot (read the existing snapshot to refine its value-prop slices)
|
|
114
116
|
|
|
115
117
|
Then sharpen:
|
|
116
118
|
|
|
@@ -176,7 +178,7 @@ scaffold depth — depth is a dedicated later pass done once, holistically.
|
|
|
176
178
|
|
|
177
179
|
## What you emit
|
|
178
180
|
|
|
179
|
-
The SAME MarketSnapshot at
|
|
181
|
+
The SAME MarketSnapshot at `.wildo-saas/journey/<journeyId>/market-snapshot/`,
|
|
180
182
|
with its value-proposition slices sharpened: weighted benefits with per-ICP
|
|
181
183
|
Kano categories, the tones of voice, and one positioning entry (with its 2–4
|
|
182
184
|
value pillars) per `CORE`/`EXPANSION` ICP — all framed by the vision's
|
|
@@ -5,6 +5,10 @@
|
|
|
5
5
|
"intent": "Top-down value-proposition / positioning: sharpen the product's value proposition on an EXISTING MarketSnapshot — the weighted benefits (relieves/creates/advances edges, Kano category per ICP), the tones of voice, and the per-ICP positioning pillars — framed by the product VisionSnapshot's differentiation. Runs after market-analysis (which produced the broad snapshot) and refines the same market-snapshot artifact; it does NOT create a new family (benefits, tone-of-voice, and positioning all live inside MarketSnapshot). Emits the refined MarketSnapshot validated by validateMarketSnapshot, consumed downstream by capability-map (benefits -> deliveredByFeatureRefs) and the refinement/coverage playbooks. v1 scaffold methodology — the FIT/Kano scoring precision and positioning rigor are iterated in a later depth phase, not here.",
|
|
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": {
|
|
@@ -24,12 +28,12 @@
|
|
|
24
28
|
{
|
|
25
29
|
"family": "market-snapshot",
|
|
26
30
|
"schemaRef": "saas-specifications:MarketSnapshot",
|
|
31
|
+
"placement": ".wildo-saas/journey/<journeyId>/market-snapshot/",
|
|
27
32
|
"description": "The SAME MarketSnapshot, refined so its value-proposition slices are sharp: benefits with weighted relieves/creates/advances edges and per-ICP Kano categories, the tones of voice, and one positioning pillar per targeted ICP. Validated by validateMarketSnapshot; feeds capability-map and refinement."
|
|
28
33
|
}
|
|
29
34
|
],
|
|
30
|
-
"stepOutputs": [],
|
|
31
35
|
"method": {
|
|
32
|
-
"guidance": "# Value Proposition & Positioning — Sharpen Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The refinement order, the benefit-weighting posture, and the\n> \"sharpen vs. leave\" rules below are deliberately explicit so they can be\n> tuned against real runs — treat them as a starting rubric, not a frozen\n> contract. The *analytical depth* of the value-proposition work (quantified\n> FIT / Kano scoring precision, positioning rigor) is intentionally shallow\n> here and is deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **positioning strategist**. Market-analysis already produced the\n**MarketSnapshot** — the category, ICPs, personas, and jobs/pains/gains. Your\none job is to **sharpen the value-proposition slices of that same snapshot**:\nthe benefits, the tones of voice, and the per-ICP positioning pillars, framed\nby the product's **VisionSnapshot** differentiation. You do not create a new\nartifact family — benefits, tone-of-voice, and positioning all live *inside*\n`MarketSnapshot`. You read the existing snapshot, tighten these three slices,\nand re-emit the same snapshot.\n\nThis is a **focused refinement pass**, distinct from market-analysis (which\ndoes the broad initial market sweep). Where market-analysis lays down the\nwhole snapshot at a first-pass depth, you come back over the value-proposition\nslices specifically and make them sharp, consistent with each other, and true\nto the vision.\n\nThe three slices you own, in dependency order (later slices reference earlier\nrefs, and all reference the jobs/pains/gains the market pass already authored):\n\n1. **Benefits** — the outcome claims the product delivers (`FeatureBenefit`),\n each a *weighted* set of edges: the pains it **relieves**, the gains it\n **creates**, and the jobs it **advances**, every edge carrying a `degree`\n (1..10) the FIT scorer multiplies by the ICP's own edge weight. Layer on\n `importanceByICP`: a per-ICP `weight` plus a **Kano category** from the\n `BenefitKanoCategory` enum — `THRESHOLD` (a must-have; its absence breaks\n the deal), `PERFORMANCE` (more is better), `DELIGHTER` (unexpected upside),\n plus `INDIFFERENT` / `REVERSE` for completeness — so the same benefit can\n matter differently to different segments. Benefits reference the\n pains/gains/jobs the market pass authored — never weight against a\n pain/gain/job that does not exist. (`market-add-feature-benefit`)\n - **Structural constraint (the U8 seam):** every benefit carries a\n non-empty `deliveredByFeatureRefs[]` — a benefit must be *deliverable*.\n At this top-down phase there is no feature registry yet, so these are\n **forward-reference** feature refs; the `ORPHAN_REF` resolution check is\n skipped until a feature set exists. **Wiring benefits to real spec-first\n feature drafts is the capability-map playbook's job (U8), not yours** —\n do not invent the feature registry here. Keep the refs you inherit;\n leave a placeholder ref only where the market pass already did.\n2. **Tones of voice** — the named brand voices the product speaks in\n (`ToneOfVoice`, addressed by `ToneOfVoiceRef`). Keep them few and distinct;\n each positioning and message template later speaks in one of them.\n (`market-tone-of-voice`)\n3. **Positioning** — the per-ICP marketing-truth promise (`MarketPositioning`):\n author **one positioning entry per ICP the product actually targets**\n (priority `CORE` or `EXPANSION`), each carrying **2–4 value pillars**\n (`valuePillars`) — the sharp claims that separate the product from the\n alternatives. Each pillar hangs off the weighted benefits above (it traces\n back to `FeatureBenefitRef[]`) and is framed by the vision's\n differentiation. (`market-positioning-authoring`)\n\nSharpen only the slices the product's stage warrants. A snapshot whose\nbenefits carry honest relieves/creates/advances weighting with per-ICP Kano\ncategories, at least one tone of voice, and one positioning entry (with its\nvalue pillars) per `CORE`/`EXPANSION` ICP is a legitimate v1; the depth of the\nweighting and the pillar prose is additive.\n\n## Frame everything by the vision\n\nThe **VisionSnapshot** (`vision-brief` family) is your differentiation anchor.\nRead its mission, its problem framing, and its success criteria before you\nweight a single benefit. A benefit's weight, a Kano category, and a positioning\npillar are only *right* if they express the product's actual differentiation —\nwhat the vision says makes this product worth building over the alternatives.\nWhen a benefit or pillar cannot be traced back to the vision's differentiation,\nthat is a signal to either sharpen the vision link or drop the claim, not to\ninvent a promise the product does not stand behind.\n\n## Where the snapshot lives\n\nThe MarketSnapshot for this journey is at\n`specifications/src/market/index.ts`. That is the artifact this\nplaybook refines in place — you read it, sharpen the value-proposition slices,\nand write the same artifact back. When the product's definition later\nstabilises, the snapshot is what seeds the durable market specification under\n`./specifications/` — but at this phase it is a journey artifact, not yet app\nsource.\n\n## Refine, don't re-author — read state first\n\nThis playbook is **idempotent** and, by construction, a *refinement*: a\nMarketSnapshot must already exist (the `artifact_exists` precondition enforces\nit). Before sharpening anything:\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) — that tells you which scope\n the value proposition must hold *for*.\n2. Read the existing MarketSnapshot at this playbook's placement path and the\n VisionSnapshot at the `vision-brief` placement, so you sharpen against the\n real market intent and the real differentiation, not from scratch.\n\n\nThen sharpen:\n\n- **Keep what still holds.** Do not rewrite benefits, tones, or pillars that\n are already sharp and vision-true. Only add/correct where the current\n steering notes, the vision, or benefit-weight inconsistencies call for it.\n- **Never orphan a ref.** A positioning names an ICP and its pillars name\n benefits; a benefit names the pains/gains/jobs it relieves/creates/advances.\n Dropping an ICP, pain, gain, job, or benefit that a positioning, pillar, or\n benefit still points at orphans the downstream ref (the validator catches\n this as `ORPHAN_REF`, but honest refinement should not create the orphan).\n If a slice from the market pass is genuinely wrong, fix it at its source\n slice, do not paper over it in the value-prop layer.\n\n## Quality gate\n\nYour re-emitted snapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. The\nvalue-proposition invariants it enforces are mostly **`ERROR`-severity hard\nfailures** — the snapshot does not advance until they clear:\n\n- **`MISSING_POSITIONING_FOR_ICP` (ERROR)** — a `CORE` or `EXPANSION` ICP has\n no `MarketPositioning`. This is the headline gap this playbook closes: a\n targeted ICP without a positioning is a *hard failure*, not a warning.\n (`EXPLORATORY` / `DEFERRED` / `ANTI_TARGET` ICPs are exempt.)\n- **`THRESHOLD_BENEFIT_WITHOUT_JOB` (ERROR)** — a benefit carries a\n `kanoCategory: THRESHOLD` entry but its `advances[]` is empty; a must-have\n claim needs a job to anchor against.\n- **`MULTIPLE_THRESHOLDS_PER_ICP_JOB` (ERROR)** — two distinct benefits both\n claim `THRESHOLD` for the same (icp, job); only one must-have per job.\n- **`EMPTY_BENEFIT_DELIVERED_BY` (ERROR)** — a benefit's `deliveredByFeatureRefs[]`\n is empty; every benefit must stay deliverable (see the U8 seam above).\n- **`ORPHAN_REF` (ERROR)** — a positioning naming a missing ICP, a pillar or\n benefit naming a missing pain/gain/job. (Feature-ref orphans are only\n checked once a feature registry is passed — not at this phase.)\n\n`WARN`-severity issues do not block but should be resolved: `DUPLICATE_EDGE_PER_ENTITY`\n(a duplicate `(benefit, icp)` importance edge) and `STALE_AUTHORED` (a slice\npast its review cadence). Read `market-snapshot-validation` for the full issue\ncatalogue and emit a clean snapshot the first time.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. The following are explicitly **out of\nscope here** and are deepened in the methodology-depth phase, not now:\n\n- **Quantified FIT / Kano scoring precision** — `market-scoring-interpretation`\n reads the deterministic FIT scorer; at scaffold depth you consume it to\n sanity-check benefit weighting and Kano assignment, not to drive a precise\n prioritization model. The prioritization seam stays pluggable (the\n capability-map playbook owns wiring FIT scores into feature drafts). Do not\n build a scoring model here.\n- **Positioning rigor** — a pillar captures *the* sharp per-ICP promise; a\n full competitive positioning matrix, message-market-fit testing, or\n A/B-tested copy is later-phase work.\n- **Message-template rendering** — this playbook stops at the value-proposition\n slices (benefits / tone / pillars). Turning them into reusable message\n templates stays with the market-analysis playbook's `market_message_templates`\n slice.\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\nThe SAME MarketSnapshot at `specifications/src/market/index.ts`,\nwith its value-proposition slices sharpened: weighted benefits with per-ICP\nKano categories, the tones of voice, and one positioning entry (with its 2–4\nvalue pillars) per `CORE`/`EXPANSION` ICP — all framed by the vision's\ndifferentiation — passing the\n`market-snapshot-valid` gate. The creator reviews the result (approval posture\n`approve_result`) before it is accepted as the journey's refined market intent.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state\n and scope, and confirm a `market-snapshot` already exists to refine.\n- `.claude/skills/market-add-feature-benefit/SKILL.md` — author the benefit\n claims and their relieves/creates/advances weighting and per-ICP Kano\n categories.\n- `.claude/skills/market-tone-of-voice/SKILL.md` — author the named brand\n voices.\n- `.claude/skills/market-positioning-authoring/SKILL.md` — author the per-ICP\n positioning entries and their 2–4 value pillars.\n- `.claude/skills/market-scoring-interpretation/SKILL.md` — interpret the\n deterministic FIT scorer to sanity-check benefit weighting and Kano\n assignment (scaffold depth — sanity-check, not a scoring model).\n- `.claude/skills/market-snapshot-validation/SKILL.md` — the full validation\n issue catalogue the quality gate enforces.\n",
|
|
36
|
+
"guidance": "# Value Proposition & Positioning — Sharpen Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The refinement order, the benefit-weighting posture, and the\n> \"sharpen vs. leave\" rules below are deliberately explicit so they can be\n> tuned against real runs — treat them as a starting rubric, not a frozen\n> contract. The *analytical depth* of the value-proposition work (quantified\n> FIT / Kano scoring precision, positioning rigor) is intentionally shallow\n> here and is deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **positioning strategist**. Market-analysis already produced the\n**MarketSnapshot** — the category, ICPs, personas, and jobs/pains/gains. Your\none job is to **sharpen the value-proposition slices of that same snapshot**:\nthe benefits, the tones of voice, and the per-ICP positioning pillars, framed\nby the product's **VisionSnapshot** differentiation. You do not create a new\nartifact family — benefits, tone-of-voice, and positioning all live *inside*\n`MarketSnapshot`. You read the existing snapshot, tighten these three slices,\nand re-emit the same snapshot.\n\nThis is a **focused refinement pass**, distinct from market-analysis (which\ndoes the broad initial market sweep). Where market-analysis lays down the\nwhole snapshot at a first-pass depth, you come back over the value-proposition\nslices specifically and make them sharp, consistent with each other, and true\nto the vision.\n\nThe three slices you own, in dependency order (later slices reference earlier\nrefs, and all reference the jobs/pains/gains the market pass already authored):\n\n1. **Benefits** — the outcome claims the product delivers (`FeatureBenefit`),\n each a *weighted* set of edges: the pains it **relieves**, the gains it\n **creates**, and the jobs it **advances**, every edge carrying a `degree`\n (1..10) the FIT scorer multiplies by the ICP's own edge weight. Layer on\n `importanceByICP`: a per-ICP `weight` plus a **Kano category** from the\n `BenefitKanoCategory` enum — `THRESHOLD` (a must-have; its absence breaks\n the deal), `PERFORMANCE` (more is better), `DELIGHTER` (unexpected upside),\n plus `INDIFFERENT` / `REVERSE` for completeness — so the same benefit can\n matter differently to different segments. Benefits reference the\n pains/gains/jobs the market pass authored — never weight against a\n pain/gain/job that does not exist. (`market-add-feature-benefit`)\n - **Structural constraint (the U8 seam):** every benefit carries a\n non-empty `deliveredByFeatureRefs[]` — a benefit must be *deliverable*.\n At this top-down phase there is no feature registry yet, so these are\n **forward-reference** feature refs; the `ORPHAN_REF` resolution check is\n skipped until a feature set exists. **Wiring benefits to real spec-first\n feature drafts is the capability-map playbook's job (U8), not yours** —\n do not invent the feature registry here. Keep the refs you inherit;\n leave a placeholder ref only where the market pass already did.\n2. **Tones of voice** — the named brand voices the product speaks in\n (`ToneOfVoice`, addressed by `ToneOfVoiceRef`). Keep them few and distinct;\n each positioning and message template later speaks in one of them.\n (`market-tone-of-voice`)\n3. **Positioning** — the per-ICP marketing-truth promise (`MarketPositioning`):\n author **one positioning entry per ICP the product actually targets**\n (priority `CORE` or `EXPANSION`), each carrying **2–4 value pillars**\n (`valuePillars`) — the sharp claims that separate the product from the\n alternatives. Each pillar hangs off the weighted benefits above (it traces\n back to `FeatureBenefitRef[]`) and is framed by the vision's\n differentiation. (`market-positioning-authoring`)\n\nSharpen only the slices the product's stage warrants. A snapshot whose\nbenefits carry honest relieves/creates/advances weighting with per-ICP Kano\ncategories, at least one tone of voice, and one positioning entry (with its\nvalue pillars) per `CORE`/`EXPANSION` ICP is a legitimate v1; the depth of the\nweighting and the pillar prose is additive.\n\n## Frame everything by the vision\n\nThe **VisionSnapshot** (`vision-brief` family) is your differentiation anchor.\nRead its mission, its problem framing, and its success criteria before you\nweight a single benefit. A benefit's weight, a Kano category, and a positioning\npillar are only *right* if they express the product's actual differentiation —\nwhat the vision says makes this product worth building over the alternatives.\nWhen a benefit or pillar cannot be traced back to the vision's differentiation,\nthat is a signal to either sharpen the vision link or drop the claim, not to\ninvent a promise the product does not stand behind.\n\n## Where the snapshot lives\n\nThe MarketSnapshot for this journey is at\n`.wildo-saas/journey/<journeyId>/market-snapshot/`. That is the artifact this\nplaybook refines in place — you read it, sharpen the value-proposition slices,\nand write the same artifact back. When the product's definition later\nstabilises, the snapshot is what seeds the durable market specification under\n`./specifications/` — but at this phase it is a journey artifact, not yet app\nsource.\n\n## Refine, don't re-author — read state first\n\nThis playbook is **idempotent** and, by construction, a *refinement*: a\nMarketSnapshot must already exist (the `artifact_exists` precondition enforces\nit). Before sharpening anything:\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) — that tells you which scope\n the value proposition must hold *for*.\n2. Read the existing MarketSnapshot at this playbook's placement path and the\n VisionSnapshot at the `vision-brief` placement, so you sharpen against the\n real market intent and the real differentiation, not 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 existing snapshot to refine its value-prop slices)\n\nThen sharpen:\n\n- **Keep what still holds.** Do not rewrite benefits, tones, or pillars that\n are already sharp and vision-true. Only add/correct where the current\n steering notes, the vision, or benefit-weight inconsistencies call for it.\n- **Never orphan a ref.** A positioning names an ICP and its pillars name\n benefits; a benefit names the pains/gains/jobs it relieves/creates/advances.\n Dropping an ICP, pain, gain, job, or benefit that a positioning, pillar, or\n benefit still points at orphans the downstream ref (the validator catches\n this as `ORPHAN_REF`, but honest refinement should not create the orphan).\n If a slice from the market pass is genuinely wrong, fix it at its source\n slice, do not paper over it in the value-prop layer.\n\n## Quality gate\n\nYour re-emitted snapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. The\nvalue-proposition invariants it enforces are mostly **`ERROR`-severity hard\nfailures** — the snapshot does not advance until they clear:\n\n- **`MISSING_POSITIONING_FOR_ICP` (ERROR)** — a `CORE` or `EXPANSION` ICP has\n no `MarketPositioning`. This is the headline gap this playbook closes: a\n targeted ICP without a positioning is a *hard failure*, not a warning.\n (`EXPLORATORY` / `DEFERRED` / `ANTI_TARGET` ICPs are exempt.)\n- **`THRESHOLD_BENEFIT_WITHOUT_JOB` (ERROR)** — a benefit carries a\n `kanoCategory: THRESHOLD` entry but its `advances[]` is empty; a must-have\n claim needs a job to anchor against.\n- **`MULTIPLE_THRESHOLDS_PER_ICP_JOB` (ERROR)** — two distinct benefits both\n claim `THRESHOLD` for the same (icp, job); only one must-have per job.\n- **`EMPTY_BENEFIT_DELIVERED_BY` (ERROR)** — a benefit's `deliveredByFeatureRefs[]`\n is empty; every benefit must stay deliverable (see the U8 seam above).\n- **`ORPHAN_REF` (ERROR)** — a positioning naming a missing ICP, a pillar or\n benefit naming a missing pain/gain/job. (Feature-ref orphans are only\n checked once a feature registry is passed — not at this phase.)\n\n`WARN`-severity issues do not block but should be resolved: `DUPLICATE_EDGE_PER_ENTITY`\n(a duplicate `(benefit, icp)` importance edge) and `STALE_AUTHORED` (a slice\npast its review cadence). Read `market-snapshot-validation` for the full issue\ncatalogue and emit a clean snapshot the first time.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. The following are explicitly **out of\nscope here** and are deepened in the methodology-depth phase, not now:\n\n- **Quantified FIT / Kano scoring precision** — `market-scoring-interpretation`\n reads the deterministic FIT scorer; at scaffold depth you consume it to\n sanity-check benefit weighting and Kano assignment, not to drive a precise\n prioritization model. The prioritization seam stays pluggable (the\n capability-map playbook owns wiring FIT scores into feature drafts). Do not\n build a scoring model here.\n- **Positioning rigor** — a pillar captures *the* sharp per-ICP promise; a\n full competitive positioning matrix, message-market-fit testing, or\n A/B-tested copy is later-phase work.\n- **Message-template rendering** — this playbook stops at the value-proposition\n slices (benefits / tone / pillars). Turning them into reusable message\n templates stays with the market-analysis playbook's `market_message_templates`\n slice.\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\nThe SAME MarketSnapshot at `.wildo-saas/journey/<journeyId>/market-snapshot/`,\nwith its value-proposition slices sharpened: weighted benefits with per-ICP\nKano categories, the tones of voice, and one positioning entry (with its 2–4\nvalue pillars) per `CORE`/`EXPANSION` ICP — all framed by the vision's\ndifferentiation — passing the\n`market-snapshot-valid` gate. The creator reviews the result (approval posture\n`approve_result`) before it is accepted as the journey's refined market intent.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state\n and scope, and confirm a `market-snapshot` already exists to refine.\n- `.claude/skills/market-add-feature-benefit/SKILL.md` — author the benefit\n claims and their relieves/creates/advances weighting and per-ICP Kano\n categories.\n- `.claude/skills/market-tone-of-voice/SKILL.md` — author the named brand\n voices.\n- `.claude/skills/market-positioning-authoring/SKILL.md` — author the per-ICP\n positioning entries and their 2–4 value pillars.\n- `.claude/skills/market-scoring-interpretation/SKILL.md` — interpret the\n deterministic FIT scorer to sanity-check benefit weighting and Kano\n assignment (scaffold depth — sanity-check, not a scoring model).\n- `.claude/skills/market-snapshot-validation/SKILL.md` — the full validation\n issue catalogue the quality gate enforces.\n",
|
|
33
37
|
"skillRefs": [
|
|
34
38
|
"journey-status",
|
|
35
39
|
"market-add-feature-benefit",
|
|
@@ -37,13 +41,17 @@
|
|
|
37
41
|
"market-tone-of-voice",
|
|
38
42
|
"market-scoring-interpretation",
|
|
39
43
|
"market-snapshot-validation"
|
|
40
|
-
]
|
|
41
|
-
"contextSources": [],
|
|
42
|
-
"suspendsForClarification": false,
|
|
43
|
-
"briefAdequacyGate": false,
|
|
44
|
-
"briefAdequacyExcludedSources": []
|
|
44
|
+
]
|
|
45
45
|
},
|
|
46
46
|
"executor": "companion_agent",
|
|
47
|
+
"qualityGates": [
|
|
48
|
+
{
|
|
49
|
+
"ref": "market-snapshot-valid",
|
|
50
|
+
"kind": "deterministic_validator",
|
|
51
|
+
"validatorRef": "saas-specifications:validateMarketSnapshot",
|
|
52
|
+
"required": true
|
|
53
|
+
}
|
|
54
|
+
],
|
|
47
55
|
"approval": "approve_result",
|
|
48
56
|
"budget": {
|
|
49
57
|
"maxRuns": 3
|
|
@@ -137,8 +137,8 @@ Before you start, read the current journey state and scope so you elicit the
|
|
|
137
137
|
vision for the right product, and read any vision that already exists so you
|
|
138
138
|
refine it rather than re-eliciting it from scratch.
|
|
139
139
|
|
|
140
|
-
|
|
141
|
-
|
|
140
|
+
// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)
|
|
141
|
+
// TODO CLI COMMAND: wildo context vision-brief (read the existing vision, if any, to refine it)
|
|
142
142
|
|
|
143
143
|
## References
|
|
144
144
|
|
|
@@ -1,25 +1,26 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.vision-elicitation",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
5
|
"intent": "Elicit a complete current-horizon product vision from sealed creator input and application context. The provider proposes semantic content; the trusted runtime stamps refs/version and keeps provenance, authority and accepted-family mutation outside model output.",
|
|
6
6
|
"functionalTopics": [],
|
|
7
|
-
"preconditions": [
|
|
8
|
-
"inputs": [
|
|
7
|
+
"preconditions": [
|
|
9
8
|
{
|
|
10
|
-
"
|
|
9
|
+
"kind": "phase_is",
|
|
10
|
+
"phase": "top_down"
|
|
11
11
|
}
|
|
12
12
|
],
|
|
13
|
+
"inputs": [],
|
|
13
14
|
"outputs": [
|
|
14
15
|
{
|
|
15
16
|
"family": "vision-brief",
|
|
16
17
|
"schemaRef": "saas-specifications:VisionSnapshot",
|
|
18
|
+
"placement": ".wildo-saas/journey/<journeyId>/vision-brief/",
|
|
17
19
|
"description": "One validated VisionSnapshot containing the product idea, problem, mission, success criteria and constraints."
|
|
18
20
|
}
|
|
19
21
|
],
|
|
20
|
-
"stepOutputs": [],
|
|
21
22
|
"method": {
|
|
22
|
-
"guidance": "# Vision Elicitation — Interview Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **vision interviewer**. Your one job is to draw the product's\nfoundational vision out of the creator through a structured conversation, and\nto capture it as a single typed **`VisionSnapshot`** — the `vision-brief`\nartifact. This is the **first** top-down step: everything downstream\n(positioning, the capability map, the compliance posture, the roadmap) reads\nthe vision you produce, so an honest, well-framed vision is the whole task.\n\nYou do **not** design the domain, draft requirements, or write code. You\nelicit *intent* — what the product is, why it should exist, what winning looks\nlike, and what limits bound it — and nothing more. Keep the market family\n(segments, personas) and the requirements family out of scope; the vision\nreferences them later, it does not absorb them.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, follow up where an answer is thin, and skip a follow-up the\n creator already answered. Reflect each answer back in one line and let the\n creator correct you before you move on.\n- **Progressive is fine.** A `VisionSnapshot` requires only the **idea**; the\n problem statement and mission are OPTIONAL and elicited progressively. If the\n creator can only give you the idea today, capture it, note what is still\n open, and stop — the snapshot persists as partially-elicited and this\n playbook can resume. Never invent a problem or mission the creator did not\n give you just to fill the shape.\n- **One product, one vision.** The snapshot is a single aggregate, not a list\n — one idea, one problem, one mission, plus ref-addressable success criteria\n and constraints. If the creator describes two products, stop and ask which\n one this journey is for.\n\n## What you elicit — one aggregate\n\nWork the vision entity by entity. For each, the target shape and the framing\nquestions:\n\n- **Idea** (REQUIRED). The anchor concept. Capture a quotable one-liner\n (\"X for Y\") and a short paragraph expanding it (core capability, shape of the\n solution). Record any framing caveats or pivots as notes. A vision without an\n idea is nothing — do not proceed to the rest until you have it.\n- **Problem** (optional, WARNed when absent). The pain the product exists to\n solve: the core statement, who is affected (prose — the deep segment model is\n the market family's job), how people cope today, the cost of leaving it\n unsolved, and the timing trigger that makes solving it urgent *now*. This is\n a framing surface, not a sized opportunity model — capture the \"why\", not a\n TAM.\n- **Mission** (optional, WARNed when absent). The enduring purpose: the mission\n statement (what we do, for whom, to what end, in one sentence), the\n aspirational long-term end-state if it fully succeeds, and the guiding\n principles / non-negotiables that constrain *how* the product is built.\n Principles are chosen stances — keep them distinct from the hard external\n constraints below.\n- **Success criteria** (ref-addressable, `success-criterion-<slug>`). What\n \"this succeeded\" concretely looks like. Each criterion is a statement, an\n optional metric and target (free prose at this stage — \"500 weekly active\n teams\", \"median time-to-first-value < 5 min\"), and a coarse horizon bucket\n (`launch` / `short_term` / `long_term`). Do not force a quantified metric\n where the creator only has a qualitative one — a typed metric taxonomy is a\n later concern. A vision with no success criteria cannot be judged\n succeeded — the validator WARNs on it, so push for at least one.\n- **Constraints** (ref-addressable, `constraint-<slug>`). External limits the\n product must be built within, each classified by kind: `technical`,\n `business`, `compliance`, `resource`, `timeline`, or `other`. Capture the\n constraint statement and, where the creator gives it, the rationale (the\n source of the limit).\n - **Compliance constraints get explicit attention.** Ask whether the product\n handles regulated or personal data, operates in a regulated sector or has contractual\n assurance commitments. If so, record each as a\n `kind: compliance` constraint with a **prose** statement (\"Must be\n GDPR-compliant for EU customer personal data\"). Stop at prose — the deep\n per-regime obligation model (control catalogs, data-flow / residency\n matrices) is the compliance-posture step's job, not yours. Getting the\n compliance *seam* named here is what lets that later step engage.\n\n## What you emit\n\nA single `VisionSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told\n otherwise).\n- `idea` — the required anchor (`oneLiner`, `description`, optional `notes`).\n- `problem` / `mission` — the optional singletons, present only if elicited.\n- `successCriteria[]` — each with a stable kebab-case `ref` prefixed\n `success-criterion-`, unique across the set.\n- `constraints[]` — each with a stable kebab-case `ref` prefixed `constraint-`,\n unique across the set, and a `kind`.\n\nAuthor every entity in English. Use stable, human-readable ref slugs\n(`success-criterion-weekly-active-teams`, `constraint-gdpr-eu-data`) — they are\naddressed by ref downstream, so a duplicate silently drops an entity.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `vision-snapshot-valid`\ngate (`validateVisionSnapshot`) before it commits. Duplicate refs and malformed\nrefs (a success-criterion or constraint ref that is not kebab-case with its\nrequired prefix) are hard **errors** — the gate rejects them. A missing problem,\na missing mission, and an empty success-criteria set are **warnings**: they\nreflect a not-yet-complete vision, they do not block, and the journey persists\nthe snapshot as partially-elicited. Emit clean refs the first time; let the\nwarnings stand honestly when the vision genuinely is not complete yet, rather\nthan inventing entities to silence them.\n\n## Approval\n\nThe drafted `VisionSnapshot` is presented to the creator for approval before it\nbecomes the committed `vision-brief`. Show the vision back in plain prose — the\none-liner, the problem, the mission, the criteria, the constraints — and let the\ncreator confirm or correct it. The vision is the seed every later step trusts;\nit is worth one explicit human sign-off.\n\n## Runtime context\n\nBefore you start, read the current journey state and scope so you elicit the\nvision for the right product, and read any vision that already exists so you\nrefine it rather than re-eliciting it from scratch.\n\n(
|
|
23
|
+
"guidance": "# Vision Elicitation — Interview Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **vision interviewer**. Your one job is to draw the product's\nfoundational vision out of the creator through a structured conversation, and\nto capture it as a single typed **`VisionSnapshot`** — the `vision-brief`\nartifact. This is the **first** top-down step: everything downstream\n(positioning, the capability map, the compliance posture, the roadmap) reads\nthe vision you produce, so an honest, well-framed vision is the whole task.\n\nYou do **not** design the domain, draft requirements, or write code. You\nelicit *intent* — what the product is, why it should exist, what winning looks\nlike, and what limits bound it — and nothing more. Keep the market family\n(segments, personas) and the requirements family out of scope; the vision\nreferences them later, it does not absorb them.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, follow up where an answer is thin, and skip a follow-up the\n creator already answered. Reflect each answer back in one line and let the\n creator correct you before you move on.\n- **Progressive is fine.** A `VisionSnapshot` requires only the **idea**; the\n problem statement and mission are OPTIONAL and elicited progressively. If the\n creator can only give you the idea today, capture it, note what is still\n open, and stop — the snapshot persists as partially-elicited and this\n playbook can resume. Never invent a problem or mission the creator did not\n give you just to fill the shape.\n- **One product, one vision.** The snapshot is a single aggregate, not a list\n — one idea, one problem, one mission, plus ref-addressable success criteria\n and constraints. If the creator describes two products, stop and ask which\n one this journey is for.\n\n## What you elicit — one aggregate\n\nWork the vision entity by entity. For each, the target shape and the framing\nquestions:\n\n- **Idea** (REQUIRED). The anchor concept. Capture a quotable one-liner\n (\"X for Y\") and a short paragraph expanding it (core capability, shape of the\n solution). Record any framing caveats or pivots as notes. A vision without an\n idea is nothing — do not proceed to the rest until you have it.\n- **Problem** (optional, WARNed when absent). The pain the product exists to\n solve: the core statement, who is affected (prose — the deep segment model is\n the market family's job), how people cope today, the cost of leaving it\n unsolved, and the timing trigger that makes solving it urgent *now*. This is\n a framing surface, not a sized opportunity model — capture the \"why\", not a\n TAM.\n- **Mission** (optional, WARNed when absent). The enduring purpose: the mission\n statement (what we do, for whom, to what end, in one sentence), the\n aspirational long-term end-state if it fully succeeds, and the guiding\n principles / non-negotiables that constrain *how* the product is built.\n Principles are chosen stances — keep them distinct from the hard external\n constraints below.\n- **Success criteria** (ref-addressable, `success-criterion-<slug>`). What\n \"this succeeded\" concretely looks like. Each criterion is a statement, an\n optional metric and target (free prose at this stage — \"500 weekly active\n teams\", \"median time-to-first-value < 5 min\"), and a coarse horizon bucket\n (`launch` / `short_term` / `long_term`). Do not force a quantified metric\n where the creator only has a qualitative one — a typed metric taxonomy is a\n later concern. A vision with no success criteria cannot be judged\n succeeded — the validator WARNs on it, so push for at least one.\n- **Constraints** (ref-addressable, `constraint-<slug>`). External limits the\n product must be built within, each classified by kind: `technical`,\n `business`, `compliance`, `resource`, `timeline`, or `other`. Capture the\n constraint statement and, where the creator gives it, the rationale (the\n source of the limit).\n - **Compliance constraints get explicit attention.** Ask whether the product\n handles regulated or personal data, operates in a regulated sector or has contractual\n assurance commitments. If so, record each as a\n `kind: compliance` constraint with a **prose** statement (\"Must be\n GDPR-compliant for EU customer personal data\"). Stop at prose — the deep\n per-regime obligation model (control catalogs, data-flow / residency\n matrices) is the compliance-posture step's job, not yours. Getting the\n compliance *seam* named here is what lets that later step engage.\n\n## What you emit\n\nA single `VisionSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told\n otherwise).\n- `idea` — the required anchor (`oneLiner`, `description`, optional `notes`).\n- `problem` / `mission` — the optional singletons, present only if elicited.\n- `successCriteria[]` — each with a stable kebab-case `ref` prefixed\n `success-criterion-`, unique across the set.\n- `constraints[]` — each with a stable kebab-case `ref` prefixed `constraint-`,\n unique across the set, and a `kind`.\n\nAuthor every entity in English. Use stable, human-readable ref slugs\n(`success-criterion-weekly-active-teams`, `constraint-gdpr-eu-data`) — they are\naddressed by ref downstream, so a duplicate silently drops an entity.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `vision-snapshot-valid`\ngate (`validateVisionSnapshot`) before it commits. Duplicate refs and malformed\nrefs (a success-criterion or constraint ref that is not kebab-case with its\nrequired prefix) are hard **errors** — the gate rejects them. A missing problem,\na missing mission, and an empty success-criteria set are **warnings**: they\nreflect a not-yet-complete vision, they do not block, and the journey persists\nthe snapshot as partially-elicited. Emit clean refs the first time; let the\nwarnings stand honestly when the vision genuinely is not complete yet, rather\nthan inventing entities to silence them.\n\n## Approval\n\nThe drafted `VisionSnapshot` is presented to the creator for approval before it\nbecomes the committed `vision-brief`. Show the vision back in plain prose — the\none-liner, the problem, the mission, the criteria, the constraints — and let the\ncreator confirm or correct it. The vision is the seed every later step trusts;\nit is worth one explicit human sign-off.\n\n## Runtime context\n\nBefore you start, read the current journey state and scope so you elicit the\nvision for the right product, and read any vision that already exists so you\nrefine it rather than re-eliciting it from scratch.\n\n// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)\n// TODO CLI COMMAND: wildo context vision-brief (read the existing vision, if any, to refine it)\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read current journey state and\n scope before eliciting, and to see whether a `vision-brief` already exists.\n",
|
|
23
24
|
"skillRefs": [
|
|
24
25
|
"journey-status"
|
|
25
26
|
],
|
|
@@ -106,13 +107,17 @@
|
|
|
106
107
|
"kind": "free_text"
|
|
107
108
|
}
|
|
108
109
|
]
|
|
109
|
-
}
|
|
110
|
-
"contextSources": [],
|
|
111
|
-
"suspendsForClarification": false,
|
|
112
|
-
"briefAdequacyGate": false,
|
|
113
|
-
"briefAdequacyExcludedSources": []
|
|
110
|
+
}
|
|
114
111
|
},
|
|
115
112
|
"executor": "companion_agent",
|
|
113
|
+
"qualityGates": [
|
|
114
|
+
{
|
|
115
|
+
"ref": "vision-snapshot-valid",
|
|
116
|
+
"kind": "deterministic_validator",
|
|
117
|
+
"validatorRef": "saas-specifications:validateVisionSnapshot",
|
|
118
|
+
"required": true
|
|
119
|
+
}
|
|
120
|
+
],
|
|
116
121
|
"approval": "approve_result",
|
|
117
122
|
"budget": {
|
|
118
123
|
"maxRuns": 3
|
|
@@ -36,20 +36,6 @@ export enum BuildPlanTaskTargetKind {
|
|
|
36
36
|
RELATIONSHIP = 'RELATIONSHIP',
|
|
37
37
|
/** A companion-owned deterministic generation step (labels, seeds, emails…) interleaved by the build loop, never a coding-agent run. */
|
|
38
38
|
COMPANION_GENERATION_STEP = 'COMPANION_GENERATION_STEP',
|
|
39
|
-
/**
|
|
40
|
-
* Authoring one SHELL SURFACE's placement configuration from the accepted
|
|
41
|
-
* placement plan — the settings rail, the sidebar, the user menu or the
|
|
42
|
-
* command palette.
|
|
43
|
-
*
|
|
44
|
-
* Its own kind rather than a reuse of the neighbours, because none of them is
|
|
45
|
-
* true of it: it is not a MODULE or a RESOURCE_STAGE (it is application-wide
|
|
46
|
-
* and belongs to no resource), not a RELATIONSHIP, and emphatically not a
|
|
47
|
-
* COMPANION_GENERATION_STEP — that kind is documented as "never a coding-agent
|
|
48
|
-
* run" and writing `settings-hub.config.ts` is exactly a coding-agent run.
|
|
49
|
-
* Borrowing one would hand the host the wrong mutation scope and the wrong
|
|
50
|
-
* verification, which is what the closed vocabulary exists to prevent.
|
|
51
|
-
*/
|
|
52
|
-
SHELL_PLACEMENT = 'SHELL_PLACEMENT',
|
|
53
39
|
}
|
|
54
40
|
|
|
55
41
|
/** The per-resource build stages, in their fixed order. */
|
|
@@ -88,24 +74,6 @@ export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
|
|
|
88
74
|
/** The companion generation step this task runs (e.g. labels, seeds); resolved by the companion, never by a coding agent. */
|
|
89
75
|
generationStepRef: SlugSchema,
|
|
90
76
|
}),
|
|
91
|
-
z.strictObject({
|
|
92
|
-
kind: z.literal(BuildPlanTaskTargetKind.SHELL_PLACEMENT),
|
|
93
|
-
/**
|
|
94
|
-
* Which shell surface this task authors — the placement family's OWN
|
|
95
|
-
* `PlacementSurface`, deliberately not a build-plan copy of it.
|
|
96
|
-
*
|
|
97
|
-
* A copy was written first and was a defect, caught by probing the landing
|
|
98
|
-
* renderer rather than by any test: `PlacementAddress` discriminates on
|
|
99
|
-
* `surface` with `z.literal(...)` per option, so only the VALUES survive into
|
|
100
|
-
* the schema, and the renderer resolves a discriminator by matching that value
|
|
101
|
-
* SET against the exported enums. Two enums with identical values made the
|
|
102
|
-
* match ambiguous, the renderer correctly refused to guess an owner, and the
|
|
103
|
-
* address discriminator became unnameable — a landed placement plan would have
|
|
104
|
-
* emitted `surface: "SETTINGS_HUB"` as a bare string instead of
|
|
105
|
-
* `PlacementSurface.SETTINGS_HUB`. One concept, one named source.
|
|
106
|
-
*/
|
|
107
|
-
surface: z.enum(PlacementSurface),
|
|
108
|
-
}),
|
|
109
77
|
]);
|
|
110
78
|
export type BuildPlanTaskTarget = z.infer<typeof BuildPlanTaskTargetSchema>;
|
|
111
79
|
|
|
@@ -126,19 +94,7 @@ export const BuildPlanTaskSchema = z.strictObject({
|
|
|
126
94
|
/** One sentence of intent: what this task delivers. */
|
|
127
95
|
objective: NonEmptyStringSchema,
|
|
128
96
|
target: BuildPlanTaskTargetSchema,
|
|
129
|
-
/**
|
|
130
|
-
* Exactly ONE functional topic this task belongs to.
|
|
131
|
-
*
|
|
132
|
-
* **It does NOT drive ordering** — this said "drives cross-app ordering" until 2026-08-30 and
|
|
133
|
-
* nothing ever ordered by it. Sequencing is `prerequisiteTaskRefs`, resolved by the host, and it
|
|
134
|
-
* is the only thing that decides what may run next.
|
|
135
|
-
*
|
|
136
|
-
* What it DOES: the dispatch host stamps it into the coding-agent's task payload beside
|
|
137
|
-
* `skillRefs`, so the agent is told which phase of building the application this task belongs to.
|
|
138
|
-
* That is context an LLM reads, not a value the runtime branches on — the distinction matters,
|
|
139
|
-
* because a reader who believes it orders will look here for a scheduling bug that lives in the
|
|
140
|
-
* prerequisite graph. See issue #124.
|
|
141
|
-
*/
|
|
97
|
+
/** Exactly ONE functional topic this task belongs to (drives cross-app ordering). */
|
|
142
98
|
functionalTopic: z.enum(MetaWorkflow_FunctionalTopic),
|
|
143
99
|
/** Installed app-knowledge skill folders that carry the technical HOW; resolved via the skills router at dispatch. */
|
|
144
100
|
skillRefs: z.array(SkillRefSchema).min(1),
|
|
@@ -22,7 +22,7 @@ import {
|
|
|
22
22
|
resolveFeatureGatedCoreResourceExclusions,
|
|
23
23
|
describeCaughtError,
|
|
24
24
|
} from '@wildo-ai/saas-backend-lib';
|
|
25
|
-
import {
|
|
25
|
+
import { CoreResourceType, ErrorCustomMessageReference, ErrorType } from '@wildo-ai/saas-models';
|
|
26
26
|
import { AppFrontendType, loadConfig } from '@wildo-ai/platform-config-lib';
|
|
27
27
|
import {
|
|
28
28
|
generateOpenApiDocuments,
|
|
@@ -37,10 +37,6 @@ import {
|
|
|
37
37
|
type OperationProjection,
|
|
38
38
|
type ResourceTag,
|
|
39
39
|
type TechnicalDocGenerateOpenApiResult,
|
|
40
|
-
type ApplicationConnectionServer,
|
|
41
|
-
type ApplicationAuthenticationDocumentationSource,
|
|
42
|
-
type ApplicationMcpToolSource,
|
|
43
|
-
type ApplicationWebhookEventSource,
|
|
44
40
|
} from '@wildo-ai/saas-technical-doc/companion';
|
|
45
41
|
import {
|
|
46
42
|
createApiReferenceLinkIndex,
|
|
@@ -108,13 +104,6 @@ interface OpenApiGenerationInputSubprocessOutput {
|
|
|
108
104
|
/** Source-derived application activation facts; independent from the API-reference selection. */
|
|
109
105
|
readonly hasConfiguredMcpToolOperations: boolean;
|
|
110
106
|
readonly hasConfiguredA2aSkills: boolean;
|
|
111
|
-
/**
|
|
112
|
-
* The two integration inventories the same walk collects. Row types come from the ENGINE, not
|
|
113
|
-
* from the subprocess module, so this mirror cannot drift on their shape while the parent still
|
|
114
|
-
* never loads subprocess code.
|
|
115
|
-
*/
|
|
116
|
-
readonly mcpTools: readonly ApplicationMcpToolSource[];
|
|
117
|
-
readonly webhookEvents: readonly ApplicationWebhookEventSource[];
|
|
118
107
|
/**
|
|
119
108
|
* Source-derived role semantics cross the subprocess boundary unchanged.
|
|
120
109
|
* The parent then joins the application's primary-locale labels before a
|
|
@@ -183,90 +172,9 @@ export class TechnicalDocCompanionService {
|
|
|
183
172
|
hasConfiguredA2aSkills: subprocessOutput.hasConfiguredA2aSkills,
|
|
184
173
|
organizationRoles,
|
|
185
174
|
organizationUnitAwareResources: subprocessOutput.organizationUnitAwareResources,
|
|
186
|
-
...this.resolveApplicationConnectionInputs(technicalDocConfig),
|
|
187
|
-
authentication: this.resolveApplicationAuthenticationInputs(),
|
|
188
|
-
integration: { mcpTools: subprocessOutput.mcpTools, webhookEvents: subprocessOutput.webhookEvents },
|
|
189
175
|
});
|
|
190
176
|
}
|
|
191
177
|
|
|
192
|
-
/**
|
|
193
|
-
* The application facts the documentation names instead of hedging: the product's own name and
|
|
194
|
-
* the base URLs it publishes.
|
|
195
|
-
*
|
|
196
|
-
* The name is what a customer calls the product — `displayName` from `wildo.saas.config.ts`,
|
|
197
|
-
* falling back to the application's `name`. Deliberately NOT `publicMarketingTitle`: that is the documentation SITE's
|
|
198
|
-
* title ("Your Application — Technical Documentation") and reads wrong inside a sentence.
|
|
199
|
-
*
|
|
200
|
-
* The base URLs are the ones the application already authors for its API reference, so the
|
|
201
|
-
* guides and the reference name the same origins by construction.
|
|
202
|
-
*/
|
|
203
|
-
private resolveApplicationConnectionInputs(technicalDocConfig: WildoTechnicalDocConfig): {
|
|
204
|
-
applicationName: string;
|
|
205
|
-
apiServers: readonly ApplicationConnectionServer[];
|
|
206
|
-
} {
|
|
207
|
-
const saasConfig = this.companionContext.saasConfig;
|
|
208
|
-
const applicationName = saasConfig.displayName?.trim() || saasConfig.name.trim();
|
|
209
|
-
if (applicationName.length === 0) {
|
|
210
|
-
throw new Error('technical-documentation requires the application to declare a name (displayName or name in wildo.saas.config.ts)');
|
|
211
|
-
}
|
|
212
|
-
return {
|
|
213
|
-
applicationName,
|
|
214
|
-
apiServers: (technicalDocConfig.apiServers ?? []).map((server) => ({
|
|
215
|
-
url: server.url,
|
|
216
|
-
...(server.description === undefined ? {} : { description: server.description }),
|
|
217
|
-
})),
|
|
218
|
-
};
|
|
219
|
-
}
|
|
220
|
-
|
|
221
|
-
/**
|
|
222
|
-
* The sign-in policy this application actually applies, per user type.
|
|
223
|
-
*
|
|
224
|
-
* Read from `userTypes[<key>].auth`, which is where all authentication policy lives — there are
|
|
225
|
-
* no global defaults. Enabled methods go through `getEnabledMethods`, the same helper the runtime
|
|
226
|
-
* uses, rather than re-reading the boolean-or-object shorthand here; and they are ordered by the
|
|
227
|
-
* engine's own enum so two applications list the same methods in the same order.
|
|
228
|
-
*/
|
|
229
|
-
private resolveApplicationAuthenticationInputs(): ApplicationAuthenticationDocumentationSource {
|
|
230
|
-
const userTypes = Object.entries(this.appConfigService.config.userTypes ?? {}).map(([userTypeKey, definition]) => {
|
|
231
|
-
const auth = definition.auth;
|
|
232
|
-
const enabled = getEnabledMethods(auth.authMethodsEnabled);
|
|
233
|
-
return {
|
|
234
|
-
userTypeKey,
|
|
235
|
-
enabledMethods: Object.values(AuthMethod).filter((method) => enabled.has(method)),
|
|
236
|
-
multifactor: {
|
|
237
|
-
required: auth.mfaPolicy.requireMFA,
|
|
238
|
-
strongRequired: auth.mfaPolicy.requireStrongMFA,
|
|
239
|
-
enrollmentGracePeriodDays: auth.mfaPolicy.enrollmentGracePeriodDays,
|
|
240
|
-
passkeyExemptFromMultifactor: auth.mfaPolicy.passkeyExemptFromMFA,
|
|
241
|
-
...(auth.mfaPolicy.acceptableMFAMethods === undefined ? {} : { acceptableMethods: auth.mfaPolicy.acceptableMFAMethods }),
|
|
242
|
-
},
|
|
243
|
-
password: {
|
|
244
|
-
minLength: auth.passwordPolicy.minLength,
|
|
245
|
-
maxLength: auth.passwordPolicy.maxLength,
|
|
246
|
-
requireUppercase: auth.passwordPolicy.requireUppercase,
|
|
247
|
-
requireLowercase: auth.passwordPolicy.requireLowercase,
|
|
248
|
-
requireNumbers: auth.passwordPolicy.requireNumbers,
|
|
249
|
-
requireSpecialChars: auth.passwordPolicy.requireSpecialChars,
|
|
250
|
-
expiryDays: auth.passwordPolicy.expiryDays,
|
|
251
|
-
},
|
|
252
|
-
session: {
|
|
253
|
-
durationMinutes: auth.sessionDurationMinutes,
|
|
254
|
-
...(auth.maxConcurrentSessions === undefined ? {} : { maxConcurrentSessions: auth.maxConcurrentSessions }),
|
|
255
|
-
},
|
|
256
|
-
lockout: {
|
|
257
|
-
maxLoginAttempts: auth.lockoutPolicy.maxLoginAttempts,
|
|
258
|
-
lockoutDurationMinutes: auth.lockoutPolicy.lockoutDurationMinutes,
|
|
259
|
-
progressive: auth.lockoutPolicy.progressiveLockout,
|
|
260
|
-
maxProgressiveLockoutHours: auth.lockoutPolicy.maxProgressiveLockoutHours,
|
|
261
|
-
},
|
|
262
|
-
};
|
|
263
|
-
});
|
|
264
|
-
if (userTypes.length === 0) {
|
|
265
|
-
throw new Error('technical-documentation requires the application to declare at least one user type');
|
|
266
|
-
}
|
|
267
|
-
return { userTypes };
|
|
268
|
-
}
|
|
269
|
-
|
|
270
178
|
/**
|
|
271
179
|
* Publishes the complete managed documentation tree at stable generated paths.
|
|
272
180
|
* This operation synchronizes the framework-owned consumer documentation into
|
|
@@ -347,9 +255,6 @@ export class TechnicalDocCompanionService {
|
|
|
347
255
|
hasConfiguredA2aSkills: subprocessOutput.hasConfiguredA2aSkills,
|
|
348
256
|
organizationRoles,
|
|
349
257
|
organizationUnitAwareResources: subprocessOutput.organizationUnitAwareResources,
|
|
350
|
-
...this.resolveApplicationConnectionInputs(technicalDocConfig),
|
|
351
|
-
authentication: this.resolveApplicationAuthenticationInputs(),
|
|
352
|
-
integration: { mcpTools: subprocessOutput.mcpTools, webhookEvents: subprocessOutput.webhookEvents },
|
|
353
258
|
});
|
|
354
259
|
const generationInput = this.assembleGenerationInput(subprocessOutput, technicalDocConfig);
|
|
355
260
|
|
|
@@ -643,12 +548,7 @@ export class TechnicalDocCompanionService {
|
|
|
643
548
|
|
|
644
549
|
let loaded: WildoTechnicalDocConfig;
|
|
645
550
|
try {
|
|
646
|
-
|
|
647
|
-
// `loadConfig` again is NOT enough on its own: jiti's module cache is process-global, so
|
|
648
|
-
// without this the second evaluation returns the first one's result and a valid taxonomy,
|
|
649
|
-
// server or overview edit stays invisible until an unrelated restart — precisely the outcome
|
|
650
|
-
// the contract above rejects. Same defect as issue #170, different read site.
|
|
651
|
-
loaded = await loadConfig<WildoTechnicalDocConfig>(techDocConfigPath, { freshModuleCache: true });
|
|
551
|
+
loaded = await loadConfig<WildoTechnicalDocConfig>(techDocConfigPath);
|
|
652
552
|
} catch (e) {
|
|
653
553
|
throw this.errorBuilder.buildError(ErrorType.CONFIGURATION, undefined, {
|
|
654
554
|
customMessageReference: ErrorCustomMessageReference.CONFIGURATION,
|
|
@@ -64,6 +64,7 @@ export const appShellConfig : AppConfiguration_Frontend['appComponentsConfigurat
|
|
|
64
64
|
responsiveBreakpoint: ViewportBreakpoint.MOBILE,
|
|
65
65
|
responsivePolicy: SidebarResponsivePolicy.BURGER,
|
|
66
66
|
defaultSection: 'main',
|
|
67
|
+
showUncategorized: true,
|
|
67
68
|
// HOME as the app's BRAND HEADER: the generated Your Application symbol + the
|
|
68
69
|
// application display name, pinned above the search trigger and doubling as
|
|
69
70
|
// the home button (so no separate "Home" row renders). The alternatives are
|
|
@@ -134,8 +135,12 @@ export const appShellConfig : AppConfiguration_Frontend['appComponentsConfigurat
|
|
|
134
135
|
],
|
|
135
136
|
showOrgSwitcher: true,
|
|
136
137
|
showLogout: true,
|
|
138
|
+
mergeSettings: false,
|
|
137
139
|
},
|
|
138
140
|
|
|
141
|
+
[ApplicationLevelComponentType.SETTINGS_DROPDOWN]: {
|
|
142
|
+
mergedWith: ApplicationLevelComponentType.USER_DROPDOWN,
|
|
143
|
+
},
|
|
139
144
|
|
|
140
145
|
[ApplicationLevelComponentType.NAVIGATION_CONTROL]: true,
|
|
141
146
|
|
|
@@ -129,7 +129,6 @@ export const specificationsCompanionExports: SpecificationsCompanionExports<
|
|
|
129
129
|
* decisions remain private runtime state.
|
|
130
130
|
*/
|
|
131
131
|
documentFactSpecification: applicationDocumentFactSpecification,
|
|
132
|
-
authoredDocumentFactSpecification: applicationAuthoredDocumentFactSpecification,
|
|
133
132
|
/**
|
|
134
133
|
* The accepted typed build plan (`build-plan` family, `BuildPlanTaskGraph`).
|
|
135
134
|
* The bottom-up dispatch playbook's coding owner reads it from the verified
|