@wildo-ai/framework-knowledge 1.1.0
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/LICENSE +34 -0
- package/dist/esm/.builder.pid +9 -0
- package/dist/esm/framework-knowledge.definitions.d.ts +51 -0
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -0
- package/dist/esm/framework-knowledge.definitions.js +1571 -0
- package/dist/esm/framework-knowledge.definitions.js.map +1 -0
- package/dist/esm/framework-knowledge.loader.d.ts +72 -0
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -0
- package/dist/esm/framework-knowledge.loader.js +258 -0
- package/dist/esm/framework-knowledge.loader.js.map +1 -0
- package/dist/esm/framework-knowledge.schemas.d.ts +236 -0
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -0
- package/dist/esm/framework-knowledge.schemas.js +23 -0
- package/dist/esm/framework-knowledge.schemas.js.map +1 -0
- package/dist/esm/index.d.ts +4 -0
- package/dist/esm/index.d.ts.map +1 -0
- package/dist/esm/index.js +4 -0
- package/dist/esm/index.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +53 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +56 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +200 -0
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +228 -0
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +39 -0
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +39 -0
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +261 -0
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +412 -0
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +61 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +65 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +53 -0
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +54 -0
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +43 -0
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +73 -0
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +53 -0
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +114 -0
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +95 -0
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +102 -0
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +258 -0
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +241 -0
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +241 -0
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +202 -0
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +82 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +89 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +56 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +76 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +30 -0
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +27 -0
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +31 -0
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +26 -0
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +254 -0
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +219 -0
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +180 -0
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +302 -0
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +249 -0
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +286 -0
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +248 -0
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +227 -0
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +45 -0
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +48 -0
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +250 -0
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +218 -0
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -0
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -0
- package/dist/knowledge/manifest.json +45 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +407 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +69 -0
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +556 -0
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +47 -0
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +344 -0
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +43 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +259 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +83 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/structured-artifact-action.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +321 -0
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +79 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +185 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +66 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +737 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +44 -0
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +261 -0
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +57 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +151 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +124 -0
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.business-model/method.md +128 -0
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +102 -0
- package/dist/knowledge/playbooks/top_down.business-model/structured-artifact-action.json +1 -0
- package/dist/knowledge/playbooks/top_down.capability-map/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.capability-map/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +239 -0
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +73 -0
- package/dist/knowledge/playbooks/top_down.capability-map/structured-artifact-action.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +177 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +95 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/method.md +64 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +49 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +40 -0
- package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +42 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +239 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +69 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/structured-artifact-action.json +1 -0
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +96 -0
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +77 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +53 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +61 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/structured-artifact-action.json +1 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +280 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +87 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/structured-artifact-action.json +1 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +204 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +54 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +146 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +120 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/structured-artifact-action.json +1 -0
- package/dist/knowledge/references/application.database.migration-change-risk.md +28 -0
- package/dist/knowledge/references/assertions.authored-metadata.config.md +90 -0
- package/dist/knowledge/references/assertions.behaviors.wire-contracts.md +223 -0
- package/dist/knowledge/references/assertions.references.conventions.md +92 -0
- package/dist/knowledge/references/assertions.snapshot.validation.md +317 -0
- package/dist/knowledge/references/assertions.specification.config.md +287 -0
- package/dist/knowledge/references/brand.asset.config.md +167 -0
- package/dist/knowledge/references/brand.authored-metadata.config.md +51 -0
- package/dist/knowledge/references/brand.logo-direction.config.md +88 -0
- package/dist/knowledge/references/brand.name.config.md +46 -0
- package/dist/knowledge/references/brand.snapshot.config.md +76 -0
- package/dist/knowledge/references/brand.snapshot.validation.md +446 -0
- package/dist/knowledge/references/brand.visual-tone.config.md +56 -0
- package/dist/knowledge/references/build-plan.task-graph.config.md +198 -0
- package/dist/knowledge/references/business-model.authored-metadata.config.md +65 -0
- package/dist/knowledge/references/business-model.pricing-plan.config.md +122 -0
- package/dist/knowledge/references/business-model.references.conventions.md +99 -0
- package/dist/knowledge/references/business-model.snapshot.config.md +121 -0
- package/dist/knowledge/references/business-model.snapshot.validation.md +325 -0
- package/dist/knowledge/references/cli.market.generate-command.md +230 -0
- package/dist/knowledge/references/cli.market.utils.md +147 -0
- package/dist/knowledge/references/companion.introspection.behaviors.market.md +90 -0
- package/dist/knowledge/references/companion.introspection.handlers.market.md +42 -0
- package/dist/knowledge/references/companion.market.generation-service.md +270 -0
- package/dist/knowledge/references/companion.market.prompt-renderer.md +244 -0
- package/dist/knowledge/references/companion.technical-doc.service.md +809 -0
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +125 -0
- package/dist/knowledge/references/engine.client-bundle.discipline.md +130 -0
- package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +55 -0
- package/dist/knowledge/references/engine.saas-technical-doc.config.md +215 -0
- package/dist/knowledge/references/engine.saas-website.config.md +331 -0
- package/dist/knowledge/references/example.authorization.unit-narrowing.declaration.md +24 -0
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +55 -0
- package/dist/knowledge/references/example.backend.custom-operation.create-postfix.md +35 -0
- package/dist/knowledge/references/example.backend.operation.error-throw.md +17 -0
- package/dist/knowledge/references/example.config.app-shell.command-menu-items.md +63 -0
- package/dist/knowledge/references/example.config.app-shell.full.md +147 -0
- package/dist/knowledge/references/example.config.app-shell.hosted-components.md +45 -0
- package/dist/knowledge/references/example.config.app-shell.quick-switcher-fields.md +37 -0
- package/dist/knowledge/references/example.config.backend.billing-enable.md +20 -0
- package/dist/knowledge/references/example.config.backend.required-floors.md +46 -0
- package/dist/knowledge/references/example.config.design-system.full.md +162 -0
- package/dist/knowledge/references/example.config.navigation.full.md +71 -0
- package/dist/knowledge/references/example.config.provider.backend-scope-billing.md +27 -0
- package/dist/knowledge/references/example.data-seeding.minimal.md +114 -0
- package/dist/knowledge/references/example.email.template.minimal.md +54 -0
- package/dist/knowledge/references/example.engine.component-registration.lazy-load.md +16 -0
- package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +146 -0
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +196 -0
- package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +174 -0
- package/dist/knowledge/references/example.i18n.label-generation.engine-barrel.md +15 -0
- package/dist/knowledge/references/example.infra.cdn.cloudflare.md +23 -0
- package/dist/knowledge/references/example.infra.cdn.generic.md +17 -0
- package/dist/knowledge/references/example.infra.environment-config.local.md +250 -0
- package/dist/knowledge/references/example.market.alternative.in-house-build.md +49 -0
- package/dist/knowledge/references/example.market.authored-metadata.md +32 -0
- package/dist/knowledge/references/example.market.buying-journey.core-icp.md +140 -0
- package/dist/knowledge/references/example.market.category.config.md +71 -0
- package/dist/knowledge/references/example.market.channel.community.md +39 -0
- package/dist/knowledge/references/example.market.feature-benefit.kano-threshold.md +67 -0
- package/dist/knowledge/references/example.market.feature-benefit.pain-reliever.md +65 -0
- package/dist/knowledge/references/example.market.icp.anti-target.md +47 -0
- package/dist/knowledge/references/example.market.icp.individual.md +82 -0
- package/dist/knowledge/references/example.market.icp.legal-entity-with-geographies.md +95 -0
- package/dist/knowledge/references/example.market.is-benefit-available.composition.md +40 -0
- package/dist/knowledge/references/example.market.job.emotional.md +27 -0
- package/dist/knowledge/references/example.market.job.functional.md +28 -0
- package/dist/knowledge/references/example.market.message-template.seeds.md +106 -0
- package/dist/knowledge/references/example.market.objection.pricing.md +39 -0
- package/dist/knowledge/references/example.market.persona.dmu-with-inheritance.md +62 -0
- package/dist/knowledge/references/example.market.persona.individual-self.md +51 -0
- package/dist/knowledge/references/example.market.positioning.per-icp.md +103 -0
- package/dist/knowledge/references/example.market.proof.metric.md +39 -0
- package/dist/knowledge/references/example.market.scoring.golden-case.md +46 -0
- package/dist/knowledge/references/example.market.scoring.no-coverage-zero.md +40 -0
- package/dist/knowledge/references/example.market.snapshot-validation.duplicate-journey-stage.md +36 -0
- package/dist/knowledge/references/example.market.snapshot-validation.errors-by-kind.md +55 -0
- package/dist/knowledge/references/example.market.snapshot-validation.objection-proof-benefit-mismatch.md +74 -0
- package/dist/knowledge/references/example.market.snapshot-validation.proof-without-support.md +32 -0
- package/dist/knowledge/references/example.market.snapshot-validation.threshold-without-job.md +44 -0
- package/dist/knowledge/references/example.market.snapshot.assembled.md +49 -0
- package/dist/knowledge/references/example.market.tone-of-voice.config.md +41 -0
- package/dist/knowledge/references/example.market.trigger.growth-milestone.md +43 -0
- package/dist/knowledge/references/example.module.companion-exports.full.md +142 -0
- package/dist/knowledge/references/example.module.registration.shared.md +16 -0
- package/dist/knowledge/references/example.module.relationships.actor-edge-back-to-scope-owner.md +47 -0
- package/dist/knowledge/references/example.module.relationships.discriminator.md +25 -0
- package/dist/knowledge/references/example.module.relationships.scope-membership-junction.md +25 -0
- package/dist/knowledge/references/example.provider.backend-module-shape.md +110 -0
- package/dist/knowledge/references/example.provider.contribution.backend-billing.md +12 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +30 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +21 -0
- package/dist/knowledge/references/example.rag.source-fields.declaration.md +83 -0
- package/dist/knowledge/references/example.rate-limit.custom-controller-surface.md +25 -0
- package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +24 -0
- package/dist/knowledge/references/example.resource.add-field.priority-enum.md +19 -0
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +21 -0
- package/dist/knowledge/references/example.resource.config-wiring.fk-relationship.md +33 -0
- package/dist/knowledge/references/example.resource.custom-view.read-host.md +28 -0
- package/dist/knowledge/references/example.resource.mcp-exposure.md +65 -0
- package/dist/knowledge/references/example.resource.reference-constraints.role-constrained.md +27 -0
- package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +22 -0
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +43 -0
- package/dist/knowledge/references/example.spec.composite-view.workspace.md +72 -0
- package/dist/knowledge/references/example.spec.feature.flag-with-codehandling.md +64 -0
- package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +88 -0
- package/dist/knowledge/references/example.spec.resource.semantic-field.md +23 -0
- package/dist/knowledge/references/example.views.app-level.composite-views-config.md +19 -0
- package/dist/knowledge/references/example.views.chart-view.resource-owned.md +69 -0
- package/dist/knowledge/references/example.views.composite-view.host-embeds.md +31 -0
- package/dist/knowledge/references/example.views.composite-view.workspace.md +65 -0
- package/dist/knowledge/references/example.views.custom-view.execution-host.md +41 -0
- package/dist/knowledge/references/example.views.execution-view.resource-owned.md +25 -0
- package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +42 -0
- package/dist/knowledge/references/market.alternative.config.md +68 -0
- package/dist/knowledge/references/market.alternative.kind.md +32 -0
- package/dist/knowledge/references/market.authored-metadata.config.md +64 -0
- package/dist/knowledge/references/market.buying-journey.config.md +43 -0
- package/dist/knowledge/references/market.buying-journey.stage.md +33 -0
- package/dist/knowledge/references/market.category.config.md +63 -0
- package/dist/knowledge/references/market.channel.config.md +59 -0
- package/dist/knowledge/references/market.channel.kind.md +49 -0
- package/dist/knowledge/references/market.context-block.builder.md +544 -0
- package/dist/knowledge/references/market.context-block.response.md +57 -0
- package/dist/knowledge/references/market.feature-benefit.config.md +84 -0
- package/dist/knowledge/references/market.feature-benefit.kano.md +41 -0
- package/dist/knowledge/references/market.gain.config.md +50 -0
- package/dist/knowledge/references/market.generation.response.md +108 -0
- package/dist/knowledge/references/market.icp.config.md +162 -0
- package/dist/knowledge/references/market.icp.geographic-targeting.md +57 -0
- package/dist/knowledge/references/market.inherit-from.md +74 -0
- package/dist/knowledge/references/market.is-benefit-available.md +58 -0
- package/dist/knowledge/references/market.job.config.md +48 -0
- package/dist/knowledge/references/market.message-template.config.md +86 -0
- package/dist/knowledge/references/market.objection.config.md +56 -0
- package/dist/knowledge/references/market.objection.kind.md +34 -0
- package/dist/knowledge/references/market.pain.config.md +50 -0
- package/dist/knowledge/references/market.persona.config.md +64 -0
- package/dist/knowledge/references/market.positioning.config.md +84 -0
- package/dist/knowledge/references/market.proof.config.md +48 -0
- package/dist/knowledge/references/market.proof.kind.md +34 -0
- package/dist/knowledge/references/market.references.weighted-edges.md +105 -0
- package/dist/knowledge/references/market.scoring.fit.md +215 -0
- package/dist/knowledge/references/market.snapshot.config.md +34 -0
- package/dist/knowledge/references/market.snapshot.validation.md +1171 -0
- package/dist/knowledge/references/market.tone-of-voice.config.md +80 -0
- package/dist/knowledge/references/market.trigger.config.md +45 -0
- package/dist/knowledge/references/market.trigger.kind.md +35 -0
- package/dist/knowledge/references/placement-plan.config.md +330 -0
- package/dist/knowledge/references/platform.config.application-database.md +74 -0
- package/dist/knowledge/references/platform.config.application-modules.md +30 -0
- package/dist/knowledge/references/platform.config.backing-services.md +266 -0
- package/dist/knowledge/references/platform.config.cdn.md +167 -0
- package/dist/knowledge/references/platform.config.environment.deployment.md +263 -0
- package/dist/knowledge/references/platform.config.saas.md +405 -0
- package/dist/knowledge/references/presets.models.design-system.configuration.md +59 -0
- package/dist/knowledge/references/presets.models.design-system.source-config.md +72 -0
- package/dist/knowledge/references/presets.models.labelling.sections.md +64 -0
- package/dist/knowledge/references/presets.models.material.profile-contract.md +192 -0
- package/dist/knowledge/references/presets.models.material.runtime-policy.md +60 -0
- package/dist/knowledge/references/presets.models.surface-policy.defaults.md +613 -0
- package/dist/knowledge/references/presets.models.surface-policy.md +534 -0
- package/dist/knowledge/references/presets.models.surface-variant.md +56 -0
- package/dist/knowledge/references/requirements.authored-metadata.config.md +64 -0
- package/dist/knowledge/references/requirements.functional-requirement.config.md +68 -0
- package/dist/knowledge/references/requirements.non-functional-requirement.config.md +100 -0
- package/dist/knowledge/references/requirements.references.conventions.md +125 -0
- package/dist/knowledge/references/requirements.snapshot.config.md +73 -0
- package/dist/knowledge/references/requirements.snapshot.validation.md +333 -0
- package/dist/knowledge/references/roadmap.authored-metadata.config.md +64 -0
- package/dist/knowledge/references/roadmap.phase.config.md +149 -0
- package/dist/knowledge/references/roadmap.references.conventions.md +89 -0
- package/dist/knowledge/references/roadmap.snapshot.config.md +65 -0
- package/dist/knowledge/references/roadmap.snapshot.validation.md +325 -0
- package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +32 -0
- package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +38 -0
- package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +45 -0
- package/dist/knowledge/references/saas.backend.custom-operation.authoritative-fields.md +53 -0
- package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +120 -0
- package/dist/knowledge/references/saas.backend.domain-module.md +237 -0
- package/dist/knowledge/references/saas.backend.email-template.definition.md +69 -0
- package/dist/knowledge/references/saas.backend.flows-actors.a2a-agent-card.md +89 -0
- package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +118 -0
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +82 -0
- package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +48 -0
- package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +39 -0
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +67 -0
- package/dist/knowledge/references/saas.backend.pdf-template.bindings.md +52 -0
- package/dist/knowledge/references/saas.backend.pdf-template.definition.md +113 -0
- package/dist/knowledge/references/saas.backend.rate-limit-service.check-policy.md +75 -0
- package/dist/knowledge/references/saas.backend.system-access-service.md +994 -0
- package/dist/knowledge/references/saas.data-seeding.admin-endpoints.md +59 -0
- package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +184 -0
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +95 -0
- package/dist/knowledge/references/saas.data-seeding.modes.md +72 -0
- package/dist/knowledge/references/saas.data-seeding.run-ledger.md +198 -0
- package/dist/knowledge/references/saas.data-seeding.run-status.md +35 -0
- package/dist/knowledge/references/saas.data-seeding.schedule.md +91 -0
- package/dist/knowledge/references/saas.data-seeding.scope-iteration-strategy.md +46 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +55 -0
- package/dist/knowledge/references/saas.external-providers.document-extraction.applicability.md +26 -0
- package/dist/knowledge/references/saas.external-providers.embeddings.applicability.md +30 -0
- package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +124 -0
- package/dist/knowledge/references/saas.external-providers.llm.operation-key.md +49 -0
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +265 -0
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +148 -0
- package/dist/knowledge/references/saas.frontend.app-shell.hosted-components.md +145 -0
- package/dist/knowledge/references/saas.frontend.chart-view.inserted-declaration.md +80 -0
- package/dist/knowledge/references/saas.frontend.command-menu.omnibox.md +88 -0
- package/dist/knowledge/references/saas.frontend.command-menu.search-resource.md +109 -0
- package/dist/knowledge/references/saas.frontend.component-registration.entry.md +21 -0
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +102 -0
- package/dist/knowledge/references/saas.frontend.composite-view.define-helper.md +31 -0
- package/dist/knowledge/references/saas.frontend.domain-module.md +31 -0
- package/dist/knowledge/references/saas.frontend.embedded-resource-descent.md +37 -0
- package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.md +172 -0
- package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +115 -0
- package/dist/knowledge/references/saas.frontend.execution-view.definition.md +172 -0
- package/dist/knowledge/references/saas.frontend.execution-view.dirty-bridge-contract.local-pane.md +109 -0
- package/dist/knowledge/references/saas.frontend.execution-view.dirty-bridge-contract.md +55 -0
- package/dist/knowledge/references/saas.frontend.execution-view.dirty-state-contract.md +151 -0
- package/dist/knowledge/references/saas.frontend.execution-view.failure-handling-contract.md +302 -0
- package/dist/knowledge/references/saas.frontend.execution-view.loading-aggregation.md +89 -0
- package/dist/knowledge/references/saas.frontend.execution-view.loading-aggregation.participation-prefetch.md +231 -0
- package/dist/knowledge/references/saas.frontend.execution-view.loading-aggregation.participation-prefetch.shell-data-hydrator.md +174 -0
- package/dist/knowledge/references/saas.frontend.execution-view.navigation-handling-and-embedding.md +96 -0
- package/dist/knowledge/references/saas.frontend.execution-view.navigation-handling-and-embedding.resolution.md +45 -0
- package/dist/knowledge/references/saas.frontend.execution-view.outcome-emission-contract.md +71 -0
- package/dist/knowledge/references/saas.frontend.execution-view.participation-and-anchor.md +80 -0
- package/dist/knowledge/references/saas.frontend.execution-view.three-zone-contract.md +147 -0
- package/dist/knowledge/references/saas.frontend.flows-actors-view.md +40 -0
- package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +80 -0
- package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +64 -0
- package/dist/knowledge/references/saas.frontend.inserted-view.identity-bindings-descriptor.md +149 -0
- package/dist/knowledge/references/saas.frontend.operation-key-and-resource-config-like.md +63 -0
- package/dist/knowledge/references/saas.frontend.quick-switcher.scope-field.md +102 -0
- package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +86 -0
- package/dist/knowledge/references/saas.frontend.related-resource-preview.md +23 -0
- package/dist/knowledge/references/saas.frontend.related-resource-sections.md +28 -0
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +43 -0
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +215 -0
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +531 -0
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +210 -0
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-preset-map.md +39 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +58 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +118 -0
- package/dist/knowledge/references/saas.frontend.view-definition-scope.md +42 -0
- package/dist/knowledge/references/saas.market.generation-agent.md +104 -0
- package/dist/knowledge/references/saas.models.core-resource-operation.md +86 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +395 -0
- package/dist/knowledge/references/saas.models.engine-capabilities.md +114 -0
- package/dist/knowledge/references/saas.models.error-type.md +45 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +162 -0
- package/dist/knowledge/references/saas.models.feature-limit-semantic.md +51 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-configuration.md +127 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +115 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-invocation.md +52 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-prompt-spec.md +188 -0
- package/dist/knowledge/references/saas.models.http-api-binding.md +237 -0
- package/dist/knowledge/references/saas.models.navigation.layout.md +149 -0
- package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +22 -0
- package/dist/knowledge/references/saas.models.organization-unit-narrowing-declaration.md +42 -0
- package/dist/knowledge/references/saas.models.polymorphism.optout-business-key.md +62 -0
- package/dist/knowledge/references/saas.models.polymorphism.variant-definition.md +74 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +97 -0
- package/dist/knowledge/references/saas.models.rate-limit-configuration.md +67 -0
- package/dist/knowledge/references/saas.models.relationship-handling-contract.md +30 -0
- package/dist/knowledge/references/saas.models.relationship-handling-settings.md +62 -0
- package/dist/knowledge/references/saas.models.relationship-nature-and-models.md +112 -0
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +431 -0
- package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +88 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +89 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-base.md +79 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +49 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-path.md +27 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-union.md +26 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +62 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +124 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-relationships-buckets.md +38 -0
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +69 -0
- package/dist/knowledge/references/saas.models.resource-config.searchable-relation.md +89 -0
- package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +121 -0
- package/dist/knowledge/references/saas.models.resource-config.token-generation.md +145 -0
- package/dist/knowledge/references/saas.models.resource-field-identifier.md +25 -0
- package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +77 -0
- package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +58 -0
- package/dist/knowledge/references/saas.models.resource-primary-scope.md +36 -0
- package/dist/knowledge/references/saas.models.resource-relationship-access-scope.md +26 -0
- package/dist/knowledge/references/saas.models.resource-relationship-builder-parameters.md +100 -0
- package/dist/knowledge/references/saas.models.resource-relationship-cardinality.md +57 -0
- package/dist/knowledge/references/saas.models.resource-relationship-declaration.md +69 -0
- package/dist/knowledge/references/saas.models.resource-relationship-resolved-semantics.md +60 -0
- package/dist/knowledge/references/saas.models.resource-relationship-schema.md +172 -0
- package/dist/knowledge/references/saas.models.resource-server-instance.md +109 -0
- package/dist/knowledge/references/saas.models.resource-type.md +24 -0
- package/dist/knowledge/references/saas.models.schema-family-builder.md +242 -0
- package/dist/knowledge/references/saas.models.scope-membership.md +143 -0
- package/dist/knowledge/references/saas.models.shared-domain-module.md +36 -0
- package/dist/knowledge/references/saas.models.shared-saas-module.md +36 -0
- package/dist/knowledge/references/saas.public-runtime.contract.md +229 -0
- package/dist/knowledge/references/saas.rag.retrieval-bounds.md +106 -0
- package/dist/knowledge/references/saas.rag.retrieval-refusals.md +89 -0
- package/dist/knowledge/references/saas.rag.retrieval-request.md +130 -0
- package/dist/knowledge/references/saas.rag.retrieval-result.md +147 -0
- package/dist/knowledge/references/saas.rag.retrieval-scores.md +54 -0
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +59 -0
- package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +74 -0
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +1158 -0
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +2602 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +180 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.discriminated-union.md +138 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-aggregate-offer.md +46 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-aggregate-rating.md +47 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-article.md +49 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-blog-posting.md +62 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-breadcrumb-list.md +46 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-faq-page.md +51 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-offer.md +46 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-organization.md +48 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-product.md +59 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-review.md +46 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-website.md +46 -0
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +530 -0
- package/dist/knowledge/references/saas.specifications.composite-view-specification.md +49 -0
- package/dist/knowledge/references/saas.specifications.error-message-specification.md +92 -0
- package/dist/knowledge/references/saas.specifications.family-specifications.md +109 -0
- package/dist/knowledge/references/saas.specifications.feature-specification.md +93 -0
- package/dist/knowledge/references/saas.specifications.frontend-component-spec-factory.md +113 -0
- package/dist/knowledge/references/saas.specifications.frontend-component-spec-model.md +366 -0
- package/dist/knowledge/references/saas.specifications.resource-frontend-configuration-aspect.md +41 -0
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +1978 -0
- package/dist/knowledge/references/saas.specifications.resource-pdf-template-spec.md +58 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-code-handling.md +49 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +156 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +171 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-frontend-config-type.md +54 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-frontend-prose.md +171 -0
- package/dist/knowledge/references/saas.website.astro.bridge.md +262 -0
- package/dist/knowledge/references/saas.website.astro.head-renderer.md +271 -0
- package/dist/knowledge/references/saas.website.astro.headers-renderer.md +41 -0
- package/dist/knowledge/references/saas.website.astro.i18n-helper.md +121 -0
- package/dist/knowledge/references/saas.website.astro.label-key-collector.md +117 -0
- package/dist/knowledge/references/saas.website.astro.label-loader.md +377 -0
- package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +46 -0
- package/dist/knowledge/references/saas.website.astro.pick-labels-for-page.md +90 -0
- package/dist/knowledge/references/saas.website.astro.robots-renderer.md +174 -0
- package/dist/knowledge/references/saas.website.astro.runtime-helper.md +187 -0
- package/dist/knowledge/references/saas.website.astro.site-context.md +141 -0
- package/dist/knowledge/references/saas.website.astro.sitemap-coverage.md +188 -0
- package/dist/knowledge/references/saas.website.astro.structured-data-renderer.md +174 -0
- package/dist/knowledge/references/saas.website.blog.bridge.md +396 -0
- package/dist/knowledge/references/saas.website.blog.collection-config.md +180 -0
- package/dist/knowledge/references/saas.website.blog.frontmatter.md +116 -0
- package/dist/knowledge/references/saas.website.blog.head-renderer.md +292 -0
- package/dist/knowledge/references/saas.website.blog.mdx-provider.md +100 -0
- package/dist/knowledge/references/saas.website.blog.post-renderer.md +291 -0
- package/dist/knowledge/references/saas.website.design-tokens.bundle.md +29 -0
- package/dist/knowledge/references/saas.website.design-tokens.colors.md +64 -0
- package/dist/knowledge/references/saas.website.design-tokens.radius.md +38 -0
- package/dist/knowledge/references/saas.website.factories.define-page-manifest.md +98 -0
- package/dist/knowledge/references/saas.website.factories.define-section.md +128 -0
- package/dist/knowledge/references/saas.website.label-keys.compose-helper.md +36 -0
- package/dist/knowledge/references/saas.website.label-keys.format.md +67 -0
- package/dist/knowledge/references/saas.website.label-pack.validator.md +206 -0
- package/dist/knowledge/references/saas.website.page-layout.component.md +217 -0
- package/dist/knowledge/references/saas.website.page-manifest.meta-label-keys.md +47 -0
- package/dist/knowledge/references/saas.website.page-manifest.route-path.md +49 -0
- package/dist/knowledge/references/saas.website.page-manifest.schema.md +186 -0
- package/dist/knowledge/references/saas.website.page-manifest.seo.md +46 -0
- package/dist/knowledge/references/saas.website.page.context.md +57 -0
- package/dist/knowledge/references/saas.website.primitives.button.md +123 -0
- package/dist/knowledge/references/saas.website.primitives.heading.md +103 -0
- package/dist/knowledge/references/saas.website.primitives.image.md +103 -0
- package/dist/knowledge/references/saas.website.primitives.internal-button.md +151 -0
- package/dist/knowledge/references/saas.website.primitives.internal-link.md +193 -0
- package/dist/knowledge/references/saas.website.primitives.link.md +78 -0
- package/dist/knowledge/references/saas.website.primitives.text.md +82 -0
- package/dist/knowledge/references/saas.website.refs.page.md +56 -0
- package/dist/knowledge/references/saas.website.refs.section.md +57 -0
- package/dist/knowledge/references/saas.website.root-config.navigation.md +37 -0
- package/dist/knowledge/references/saas.website.root-config.schema.md +192 -0
- package/dist/knowledge/references/saas.website.root-config.seo.md +98 -0
- package/dist/knowledge/references/saas.website.routing.localized-path.md +84 -0
- package/dist/knowledge/references/saas.website.runtime.context.md +174 -0
- package/dist/knowledge/references/saas.website.section.component.md +138 -0
- package/dist/knowledge/references/saas.website.section.context.md +63 -0
- package/dist/knowledge/references/saas.website.sections.category-enum.md +72 -0
- package/dist/knowledge/references/saas.website.sections.definition-schema.md +121 -0
- package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +37 -0
- package/dist/knowledge/references/saas.website.seo.robots-config.md +106 -0
- package/dist/knowledge/references/saas.website.seo.sitemap-config.md +73 -0
- package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +71 -0
- package/dist/knowledge/references/saas.website.use-label-by-key.hook.md +45 -0
- package/dist/knowledge/references/saas.website.use-label.hook.md +82 -0
- package/dist/knowledge/references/saas.website.use-page.hook.md +30 -0
- package/dist/knowledge/references/saas.website.use-runtime.hook.md +36 -0
- package/dist/knowledge/references/saas.website.use-section.hook.md +30 -0
- package/dist/knowledge/references/saas.website.use-tokens.hook.md +32 -0
- package/dist/knowledge/references/vision.authored-metadata.config.md +64 -0
- package/dist/knowledge/references/vision.constraint.config.md +66 -0
- package/dist/knowledge/references/vision.idea.config.md +45 -0
- package/dist/knowledge/references/vision.mission.config.md +46 -0
- package/dist/knowledge/references/vision.problem.config.md +51 -0
- package/dist/knowledge/references/vision.references.conventions.md +115 -0
- package/dist/knowledge/references/vision.snapshot.config.md +85 -0
- package/dist/knowledge/references/vision.snapshot.validation.md +226 -0
- package/dist/knowledge/references/vision.success-criterion.config.md +60 -0
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +550 -0
- package/dist/knowledge/references/zod.decorators.conditional-visibility.md +104 -0
- package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +436 -0
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +174 -0
- package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +101 -0
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +317 -0
- package/dist/knowledge/references/zod.decorators.file-generation.md +36 -0
- package/dist/knowledge/references/zod.decorators.file-rag-source.md +56 -0
- package/dist/knowledge/references/zod.decorators.file-schema.md +319 -0
- package/dist/knowledge/references/zod.decorators.foreign-key-display-mode.md +83 -0
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +459 -0
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +123 -0
- package/dist/knowledge/references/zod.decorators.rag-source.md +164 -0
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +122 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +152 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +314 -0
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +529 -0
- package/dist/knowledge/references/zod.factories.bigdecimal.md +155 -0
- package/dist/knowledge/references/zod.factories.code.md +127 -0
- package/dist/knowledge/references/zod.factories.duration.md +246 -0
- package/dist/knowledge/references/zod.factories.money.md +166 -0
- package/dist/knowledge/references/zod.factories.phone.md +88 -0
- package/dist/knowledge/references/zod.factories.range.md +174 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +15 -0
- package/dist/knowledge/registries/framework-topics.json +5212 -0
- package/dist/knowledge/registries/playbooks.json +488 -0
- package/dist/knowledge/registries/source-tags.json +7664 -0
- package/dist/knowledge/rules/resource-schema-awareness.md +77 -0
- package/dist/knowledge/skills/INDEX.md +349 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +415 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/examples/domain-use-case-and-admin-task.example.md +49 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +52 -0
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +218 -0
- package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +84 -0
- package/dist/knowledge/skills/application-database-migrations/references/framework-migration-change-risk-api.md +37 -0
- package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +64 -0
- package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +34 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +323 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +84 -0
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +324 -0
- package/dist/knowledge/skills/backend-addon-wiring/references/backend-di-routing.md +7 -0
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +276 -0
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +374 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-error-handling-api.md +118 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +107 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +134 -0
- package/dist/knowledge/skills/backend-custom-operation/references/operation-file-conventions.md +10 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +192 -0
- package/dist/knowledge/skills/brand-logo-authoring/references/brand-authoring-decisions.md +55 -0
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +184 -0
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +279 -0
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +346 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +160 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +518 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +158 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +95 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +100 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +1210 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +40 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +698 -0
- package/dist/knowledge/skills/config-app-shell/references/app-shell-surfaces.md +5 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +415 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-hosted-components-api.md +170 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-command-menu-omnibox-api.md +212 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-quick-switcher-scope-field-api.md +178 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +424 -0
- package/dist/knowledge/skills/config-design-system/references/design-system-file.md +10 -0
- package/dist/knowledge/skills/config-design-system/references/framework-design-system-configuration-api.md +77 -0
- package/dist/knowledge/skills/config-design-system/references/framework-material-profile-api.md +200 -0
- package/dist/knowledge/skills/config-design-system/references/framework-material-runtime-policy-api.md +68 -0
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +1212 -0
- package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +92 -0
- package/dist/knowledge/skills/config-navigation/SKILL.md +249 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +152 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-zones.md +5 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +209 -0
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +221 -0
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +408 -0
- package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +183 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +40 -0
- package/dist/knowledge/skills/configure-billing/SKILL.md +261 -0
- package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +90 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +122 -0
- package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +48 -0
- package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +69 -0
- package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +57 -0
- package/dist/knowledge/skills/email-add-template/SKILL.md +439 -0
- package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +9 -0
- package/dist/knowledge/skills/email-add-template/references/framework-email-template-api.md +72 -0
- package/dist/knowledge/skills/email-definition-wiring/SKILL.md +62 -0
- package/dist/knowledge/skills/email-labels-authoring/SKILL.md +64 -0
- package/dist/knowledge/skills/email-template-authoring/SKILL.md +62 -0
- package/dist/knowledge/skills/engine-component-registration/SKILL.md +257 -0
- package/dist/knowledge/skills/engine-component-registration/references/component-registration-file.md +7 -0
- package/dist/knowledge/skills/engine-component-registration/references/framework-component-registration-api.md +24 -0
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +429 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +287 -0
- package/dist/knowledge/skills/engine-product-definitions/references/product-registry-scope.md +5 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +491 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +227 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-named-a2a-agents-contract.md +143 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +368 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +226 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +208 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +286 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +376 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +262 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +130 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-prompt-spec-api.md +214 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +195 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/operation-key-selection.md +60 -0
- package/dist/knowledge/skills/frontend-cdn-publish/SKILL.md +237 -0
- package/dist/knowledge/skills/frontend-cdn-publish/references/cloudflare-and-operator-setup.md +56 -0
- package/dist/knowledge/skills/frontend-cdn-publish/references/framework-cdn-config-api.md +176 -0
- package/dist/knowledge/skills/i18n-label-generation/SKILL.md +261 -0
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +67 -0
- package/dist/knowledge/skills/i18n-label-generation/references/label-placement.md +7 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +269 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +67 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/i18n-routing.md +9 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +245 -0
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +67 -0
- package/dist/knowledge/skills/i18n-translation-rerun/references/translation-workflow.md +17 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +646 -0
- package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +77 -0
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +282 -0
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +265 -0
- package/dist/knowledge/skills/infra-environment-config/references/infra-config-files.md +7 -0
- package/dist/knowledge/skills/journey-approve/SKILL.md +43 -0
- package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +42 -0
- package/dist/knowledge/skills/journey-next/SKILL.md +42 -0
- package/dist/knowledge/skills/journey-report/SKILL.md +43 -0
- package/dist/knowledge/skills/journey-run/SKILL.md +55 -0
- package/dist/knowledge/skills/journey-status/SKILL.md +50 -0
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +370 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +50 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +409 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +247 -0
- package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +474 -0
- package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +139 -0
- package/dist/knowledge/skills/market-alternatives/SKILL.md +543 -0
- package/dist/knowledge/skills/market-authoring-overview/SKILL.md +354 -0
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +138 -0
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +129 -0
- package/dist/knowledge/skills/market-category/SKILL.md +290 -0
- package/dist/knowledge/skills/market-channels/SKILL.md +361 -0
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +2752 -0
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +2443 -0
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +1484 -0
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +1230 -0
- package/dist/knowledge/skills/market-icp/SKILL.md +625 -0
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +352 -0
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +415 -0
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1439 -0
- package/dist/knowledge/skills/market-persona/SKILL.md +407 -0
- package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +392 -0
- package/dist/knowledge/skills/market-positioning-authoring/references/framework-positioning-api.md +97 -0
- package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +665 -0
- package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +620 -0
- package/dist/knowledge/skills/market-scoring-interpretation/references/framework-scoring-api.md +291 -0
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +1706 -0
- package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1228 -0
- package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +260 -0
- package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +579 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +318 -0
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +544 -0
- package/dist/knowledge/skills/module-registration/SKILL.md +212 -0
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +366 -0
- package/dist/knowledge/skills/module-registration/references/registry-files.md +9 -0
- package/dist/knowledge/skills/module-relationships/SKILL.md +523 -0
- package/dist/knowledge/skills/module-relationships/references/cross-resource-fk-checklist.md +7 -0
- package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +738 -0
- package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +174 -0
- package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-template-api.md +203 -0
- package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-template-spec-api.md +62 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +239 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +90 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +50 -0
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +652 -0
- package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +182 -0
- package/dist/knowledge/skills/rate-limit-authoring/references/scope-key-and-bucket-conventions.md +137 -0
- package/dist/knowledge/skills/resource-add-field/SKILL.md +272 -0
- package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +153 -0
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +845 -0
- package/dist/knowledge/skills/resource-add-module/SKILL.md +322 -0
- package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +67 -0
- package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +15 -0
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +222 -0
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +540 -0
- package/dist/knowledge/skills/resource-add-resource/references/scaffold-surfaces-checklist.md +25 -0
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +370 -0
- package/dist/knowledge/skills/resource-config-wiring/references/config-change-routing.md +11 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +622 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +248 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +1769 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +1209 -0
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +228 -0
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +693 -0
- package/dist/knowledge/skills/resource-external-data/SKILL.md +349 -0
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +187 -0
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +261 -0
- package/dist/knowledge/skills/resource-external-data/references/lane-selection.md +49 -0
- package/dist/knowledge/skills/resource-external-data/references/pipeline-destination-schema.md +43 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +308 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-named-mcp-servers-contract.md +166 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +63 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +77 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-client-registration-postures.md +90 -0
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +424 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/corpus-field-selection.md +90 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +261 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-file-rag-source-api.md +117 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +597 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +181 -0
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +318 -0
- package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +132 -0
- package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +62 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +63 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +70 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +559 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-polymorphic-resources-api.md +147 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +247 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +164 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +327 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +1286 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +1080 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +75 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +62 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +69 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +45 -0
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +389 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-conditional-visibility-api.md +106 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +176 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +103 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-foreign-key-ui-api.md +97 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +839 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +461 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +125 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +245 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +302 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/ui-layer-boundaries.md +13 -0
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +569 -0
- package/dist/knowledge/skills/seeding-authoring/references/data-seeding-mode-picker.md +154 -0
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +176 -0
- package/dist/knowledge/skills/seeding-operations/SKILL.md +505 -0
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +337 -0
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +171 -0
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +662 -0
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +134 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +65 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +127 -0
- package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +726 -0
- package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +242 -0
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +362 -0
- package/dist/knowledge/skills/spec-companion-exports/references/companion-export-checklist.md +8 -0
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +533 -0
- package/dist/knowledge/skills/spec-component-update/SKILL.md +315 -0
- package/dist/knowledge/skills/spec-component-update/references/component-spec-props.md +8 -0
- package/dist/knowledge/skills/spec-component-update/references/framework-frontend-component-spec-api.md +481 -0
- package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +283 -0
- package/dist/knowledge/skills/spec-composite-view-update/references/composite-spec-sections.md +5 -0
- package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +51 -0
- package/dist/knowledge/skills/spec-family-update/SKILL.md +300 -0
- package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +13 -0
- package/dist/knowledge/skills/spec-family-update/references/framework-error-message-specifications-api.md +108 -0
- package/dist/knowledge/skills/spec-family-update/references/framework-family-specifications-api.md +111 -0
- package/dist/knowledge/skills/spec-feature-update/SKILL.md +306 -0
- package/dist/knowledge/skills/spec-feature-update/references/feature-spec-scope.md +5 -0
- package/dist/knowledge/skills/spec-feature-update/references/framework-feature-specification-api.md +95 -0
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +220 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +319 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +2610 -0
- package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +12 -0
- package/dist/knowledge/skills/spec-update-after-change/SKILL.md +195 -0
- package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +173 -0
- package/dist/knowledge/skills/spec-update-after-change/references/spec-maintenance-by-surface.md +33 -0
- package/dist/knowledge/skills/spec-update-after-change/references/surface-to-spec-routing.md +14 -0
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +259 -0
- package/dist/knowledge/skills/views-add-composite-view/references/composite-view-routing.md +10 -0
- package/dist/knowledge/skills/views-add-composite-view/references/framework-inserted-view-identity-api.md +151 -0
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +225 -0
- package/dist/knowledge/skills/views-add-custom-view/references/custom-view-routing.md +10 -0
- package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +107 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +201 -0
- package/dist/knowledge/skills/views-app-level/references/app-level-views-routing.md +9 -0
- package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +107 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +264 -0
- package/dist/knowledge/skills/views-chart-authoring/references/chart-view-checklist.md +7 -0
- package/dist/knowledge/skills/views-chart-authoring/references/framework-chart-view-contracts-api.md +82 -0
- package/dist/knowledge/skills/views-chart-authoring/references/framework-inserted-view-identity-api.md +152 -0
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +302 -0
- package/dist/knowledge/skills/views-composite-authoring/references/composite-embedding-checklist.md +23 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +133 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-inserted-view-identity-api.md +152 -0
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +209 -0
- package/dist/knowledge/skills/views-execution-authoring/references/execution-view-checklist.md +7 -0
- package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +389 -0
- package/dist/knowledge/skills/views-execution-authoring/references/framework-inserted-view-identity-api.md +152 -0
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +444 -0
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +587 -0
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +1426 -0
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +553 -0
- package/dist/knowledge/skills/website-bundle-discipline/references/example-website-button-override.md +52 -0
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +357 -0
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +511 -0
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +376 -0
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +304 -0
- package/dist/knowledge/skills/website-label-pack/SKILL.md +390 -0
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +461 -0
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +264 -0
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +414 -0
- package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +366 -0
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +420 -0
- package/dist/knowledge/skills/website-page-variants/SKILL.md +256 -0
- package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +302 -0
- package/dist/knowledge/skills/website-section-contact/SKILL.md +950 -0
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +579 -0
- package/dist/knowledge/skills/website-section-cta/SKILL.md +822 -0
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +579 -0
- package/dist/knowledge/skills/website-section-faq/SKILL.md +917 -0
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +579 -0
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +878 -0
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +579 -0
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +895 -0
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +579 -0
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +814 -0
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +579 -0
- package/dist/knowledge/skills/website-section-hero/SKILL.md +944 -0
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +583 -0
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +934 -0
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +579 -0
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +912 -0
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +579 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +624 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +633 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +193 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +790 -0
- package/dist/knowledge/topic-index.json +17510 -0
- package/dist/tsconfig.build.tsbuildinfo +1 -0
- package/dist/tsconfig.tsbuildinfo +1 -0
- package/package.json +49 -0
|
@@ -0,0 +1,280 @@
|
|
|
1
|
+
# Scope & Roadmap — Capability Map → Release Plan Method (v1 scaffold)
|
|
2
|
+
|
|
3
|
+
### Target Application Framing
|
|
4
|
+
|
|
5
|
+
This knowledge is for configuring behavior in the target application.
|
|
6
|
+
Wildo is the framework surface being used, not the product being built.
|
|
7
|
+
|
|
8
|
+
Read and apply these patterns from the application-developer point of view:
|
|
9
|
+
|
|
10
|
+
- how the application should configure the relevant app-level file
|
|
11
|
+
- how the application should use framework-provided factories, enums, and helpers
|
|
12
|
+
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
> **This is a v1 scaffold methodology.** It is a working first cut meant to be
|
|
16
|
+
> iterated. The phasing order, the MVP-first rubric, and the in/out-of-scope
|
|
17
|
+
> convention below are deliberately explicit so they can be tuned against real
|
|
18
|
+
> runs — treat them as a starting rubric, not a frozen contract. The
|
|
19
|
+
> *analytical depth* of release planning (typed schedules, dependency graphs,
|
|
20
|
+
> capacity/estimation, defended prioritization) is intentionally shallow here
|
|
21
|
+
> and is deepened in a later phase; do not perfect it in this playbook.
|
|
22
|
+
|
|
23
|
+
## What this playbook does
|
|
24
|
+
|
|
25
|
+
You are the **release planner**. This playbook turns *product capability* (the
|
|
26
|
+
features the capability map identified and the requirements behind them) into a
|
|
27
|
+
**release plan**: an ordered set of roadmap **phases** (MVP → Beta → GA →
|
|
28
|
+
Growth) that declare **what gets delivered when**. Capability mapping already
|
|
29
|
+
produced a **MarketSnapshot** whose benefits are wired to delivering features,
|
|
30
|
+
plus **feature-drafts** and a set of **requirements**. Your one job is to answer,
|
|
31
|
+
for the whole product: **in what order do we deliver this, and what is in vs out
|
|
32
|
+
of scope for each release?** — and record the answer as a `RoadmapSnapshot`.
|
|
33
|
+
|
|
34
|
+
You produce ONE artifact for this journey: the **roadmap** family
|
|
35
|
+
(`RoadmapSnapshot`), a single ordered `phases` collection.
|
|
36
|
+
|
|
37
|
+
This is a **focused planning pass**, distinct from the capability map (which
|
|
38
|
+
made each benefit deliverable and drafted the features) and from the phase-gate
|
|
39
|
+
(which decides whether the top-down phase is complete). Where the capability map
|
|
40
|
+
said *what the product must do*, you say *in what order it ships*.
|
|
41
|
+
|
|
42
|
+
## The roadmap is requirement/success-criterion-addressed, NOT feature-addressed
|
|
43
|
+
|
|
44
|
+
Read this before you start — it is the one structural fact that shapes the whole
|
|
45
|
+
method. A roadmap phase declares what it delivers through **two flat cross-ref
|
|
46
|
+
lists**:
|
|
47
|
+
|
|
48
|
+
- **`deliversRequirementRefs`** — the requirement refs (from the `requirements`
|
|
49
|
+
family) this phase delivers. Primarily **functional-requirement** refs
|
|
50
|
+
(`functional-requirement-…`) — the case the `_core` phase contract narrates —
|
|
51
|
+
but a phase that lands a quality attribute may also deliver a **non-functional**
|
|
52
|
+
ref (`nfr-…`); the catalog resolves both against one combined requirement-ref
|
|
53
|
+
pool, so an NFR ref is valid here (see the NFR-phasing boundary note).
|
|
54
|
+
- **`deliversSuccessCriterionRefs`** — the vision success-criterion refs (from
|
|
55
|
+
the `vision-brief` family) this phase is expected to satisfy.
|
|
56
|
+
|
|
57
|
+
A phase does **not** name feature refs. So the capability map's **features reach
|
|
58
|
+
the roadmap indirectly**: feature → benefit → requirement → phase. You slot
|
|
59
|
+
**requirements and success criteria** into phases; you use the capability map
|
|
60
|
+
(which feature delivers which benefit, and the FIT/Kano read on the feature set)
|
|
61
|
+
to **judge which requirements are MVP-critical vs later**. The feature →
|
|
62
|
+
requirement trace is **prose-only today** (a requirement cross-refs ICPs and jobs
|
|
63
|
+
but not market pains/gains, and there is no typed feature → requirement edge —
|
|
64
|
+
this is the filed depth-phase gap; see the scaffold-depth boundary). At scaffold
|
|
65
|
+
depth you bridge that trace by reading the capability map and the requirements
|
|
66
|
+
together and using judgement — do **not** try to make it deterministic here.
|
|
67
|
+
|
|
68
|
+
## Read state first — the four families you read, the one you write
|
|
69
|
+
|
|
70
|
+
This playbook is **idempotent** and, on a re-run, a *refinement*: a MarketSnapshot
|
|
71
|
+
must already exist (the `artifact_exists` precondition enforces the capability map
|
|
72
|
+
is in place — you cannot plan releases before you know the capabilities). Before
|
|
73
|
+
planning anything:
|
|
74
|
+
|
|
75
|
+
1. Read the current journey state and scope through the `journey-status` skill
|
|
76
|
+
(it owns the read; do not re-derive it here). Confirm a `market-snapshot`
|
|
77
|
+
exists and check whether a `roadmap` already exists from an earlier run.
|
|
78
|
+
2. Read the capability-mapped **MarketSnapshot** (benefits + their
|
|
79
|
+
`deliveredByFeatureRefs` + FIT/Kano signal), the **feature-drafts** (the prose
|
|
80
|
+
capability contracts — what each delivering feature actually is, so you can
|
|
81
|
+
weigh how much of the product a requirement pulls in and whether it is
|
|
82
|
+
MVP-critical), the **requirements** (`requirements` family — the
|
|
83
|
+
functional/non-functional requirements to slot into phases), and the
|
|
84
|
+
**VisionSnapshot** (`vision-brief` — the success criteria to deliver and the
|
|
85
|
+
differentiation that anchors what belongs in the MVP).
|
|
86
|
+
|
|
87
|
+
// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)
|
|
88
|
+
// TODO CLI COMMAND: wildo context roadmap (read any existing phases to refine)
|
|
89
|
+
|
|
90
|
+
You **read** `market-snapshot` + `feature-drafts` + `requirements` +
|
|
91
|
+
`vision-brief`; you **write** the `roadmap` family.
|
|
92
|
+
|
|
93
|
+
## The phasing loop (build the ordered releases)
|
|
94
|
+
|
|
95
|
+
1. **Establish the MVP cut first.** The first phase is the smallest coherent
|
|
96
|
+
release that makes the product's core promise true. Pull in the requirements
|
|
97
|
+
whose delivering features are **table-stakes** for the primary ICP — the
|
|
98
|
+
capability map's FIT/Kano read surfaces these (a `THRESHOLD` benefit for a
|
|
99
|
+
`CORE`/`EXPANSION` ICP is MVP-critical). A requirement whose benefit is a
|
|
100
|
+
`DELIGHTER`, or serves a non-primary segment, is a candidate for a later
|
|
101
|
+
phase, not the MVP. MVP-first is the scaffold rubric: deliver the differentiated
|
|
102
|
+
core early, defer the upside.
|
|
103
|
+
2. **Group the remaining work into ordered later phases.** Beta / GA / Growth
|
|
104
|
+
stages each pull in the next coherent slice of requirements and success
|
|
105
|
+
criteria. Group by *theme* (a phase has a narrative headline — "Trust &
|
|
106
|
+
safety", "Onboarding excellence"), not by arbitrary size.
|
|
107
|
+
3. **Assign each phase its ordering + coarse tags.**
|
|
108
|
+
- **`sequence`** — the authoritative ordering key (ascending integer).
|
|
109
|
+
Consumers sort by `sequence`, never by array position. Author with **gaps**
|
|
110
|
+
(10, 20, 30) so a later phase can be inserted without renumbering. Every
|
|
111
|
+
phase must have a **distinct** `sequence` (a shared sequence is a
|
|
112
|
+
`DUPLICATE_SEQUENCE` WARN — the order becomes ambiguous).
|
|
113
|
+
- **`horizon`** — coarse `NOW` / `NEXT` / `LATER` bucket (`RoadmapPhaseHorizon`).
|
|
114
|
+
- **`kind`** — coarse lifecycle stage `DISCOVERY` / `MVP` / `BETA` / `GA` /
|
|
115
|
+
`GROWTH` / `OTHER` (`RoadmapPhaseKind`).
|
|
116
|
+
- **`title`** (required), plus optional `theme` (narrative angle),
|
|
117
|
+
`objective` (the concrete outcome in prose), and `targetWindow` (WHEN, as
|
|
118
|
+
**free prose** — "Q3 2026", "first 3 months post-launch"; a typed schedule
|
|
119
|
+
is a later-phase concern).
|
|
120
|
+
4. **Wire what each phase delivers.** Populate `deliversRequirementRefs` with the
|
|
121
|
+
requirement refs (functional, and any non-functional quality the phase lands)
|
|
122
|
+
the phase delivers, and `deliversSuccessCriterionRefs` with the vision
|
|
123
|
+
success-criterion refs it satisfies. **Every requirement and every success
|
|
124
|
+
criterion should land in at most one phase** — the earliest that delivers it.
|
|
125
|
+
Two distinct duplication cases exist, and the gate catches only one:
|
|
126
|
+
- **Same ref twice on ONE phase's list** → a `DUPLICATE_CROSS_REF` WARN. The
|
|
127
|
+
gate catches this (each of the two lists is its own namespace, so the same
|
|
128
|
+
string appearing once in each list is NOT flagged).
|
|
129
|
+
- **Same ref on TWO different phases** → the gate does **NOT** catch this — the
|
|
130
|
+
validator's duplicate check is per-list, per-phase, never cross-phase. It is
|
|
131
|
+
silently wrong: coverage double-counts the ref and "which release first
|
|
132
|
+
delivers it" becomes ambiguous. Keeping a ref in exactly one phase is an
|
|
133
|
+
**authoring discipline**, not a gate-enforced invariant.
|
|
134
|
+
5. **Sanity-check coverage.** By the last phase, every requirement whose benefit
|
|
135
|
+
the product actually promises, and every vision success criterion, should be
|
|
136
|
+
delivered by some phase. A requirement no phase delivers is out-of-scope of the
|
|
137
|
+
*entire roadmap* — that is a real decision (it says "the product will not do
|
|
138
|
+
this"), so make it deliberately and narrate it, do not leave it by accident.
|
|
139
|
+
|
|
140
|
+
## In-scope vs out-of-scope per release (the scope decision)
|
|
141
|
+
|
|
142
|
+
The roadmap `_core` has **no typed out-of-scope axis** — a phase declares only
|
|
143
|
+
what it **delivers**. So scope is modelled as follows at scaffold depth:
|
|
144
|
+
|
|
145
|
+
- **In-scope of a release = its `delivers*` refs.** The `deliversRequirementRefs`
|
|
146
|
+
+ `deliversSuccessCriterionRefs` a phase carries ARE its declared, gate-checked
|
|
147
|
+
in-scope. This is explicit and typed.
|
|
148
|
+
- **Out-of-scope of a release is implicit + partly derivable.** Everything NOT
|
|
149
|
+
yet delivered by a phase at or before this one is out-of-scope of that release
|
|
150
|
+
(cumulative — a ref delivered by an earlier phase stays in-scope in every later
|
|
151
|
+
one). Within that out-of-scope set, two sub-cases ARE derivable from the roadmap
|
|
152
|
+
alone: *deferred* (some later phase delivers the ref → planned, just not yet)
|
|
153
|
+
vs *never* (NO phase anywhere delivers the ref → out of the product).
|
|
154
|
+
- **What is NOT derivable — and therefore needs prose.** The roadmap cannot
|
|
155
|
+
distinguish a *deliberately excluded* requirement ("we chose not to build SSO")
|
|
156
|
+
from an *accidentally dropped* one ("we forgot to slot it"): both surface
|
|
157
|
+
identically — a requirement authored in the `requirements` family that no phase
|
|
158
|
+
delivers. That single ambiguity is the entire cost of Option A. So record the
|
|
159
|
+
**rationale** for every deliberate "never" in the phase `objective` / `theme`
|
|
160
|
+
**prose** ("Out of scope for MVP: bulk import, SSO — deferred to GA"; "Not in
|
|
161
|
+
the product: on-prem hosting — SaaS-only by design"), and run the coverage
|
|
162
|
+
sanity-check (step 5 above) so an accidental drop is caught rather than shipped
|
|
163
|
+
as a phantom exclusion.
|
|
164
|
+
|
|
165
|
+
Rejected alternatives:
|
|
166
|
+
|
|
167
|
+
- A **typed out-of-scope / explicitly-deferred axis** on a phase (a
|
|
168
|
+
`defersRequirementRefs` list, or an `outOfScope` block). It is the real fix for
|
|
169
|
+
the ambiguity above — it makes "deliberately never" machine-readable — but it is
|
|
170
|
+
a `_core/roadmap` reshape, filed as a depth-phase item, NOT built here. Do
|
|
171
|
+
**not** reshape the roadmap contract to add it.
|
|
172
|
+
- A **phantom "out-of-scope" phase** — a phase whose `deliversRequirementRefs`
|
|
173
|
+
lists the *excluded* requirements to fake a machine-readable exclusion set. Do
|
|
174
|
+
**NOT** do this. A phase *delivers* its refs by definition; listing excluded
|
|
175
|
+
refs there inverts the semantics and **corrupts every downstream coverage
|
|
176
|
+
count** (those refs would read as delivered, and the phase-gate / refinement
|
|
177
|
+
playbooks would treat excluded work as shipped). This is exactly the kind of
|
|
178
|
+
"trick" the framework mindset forbids — the excluded set stays in prose until
|
|
179
|
+
the typed axis lands, never by abusing `delivers*`.
|
|
180
|
+
|
|
181
|
+
## Refine, don't re-author
|
|
182
|
+
|
|
183
|
+
- **Keep what still holds.** On a re-run, do not renumber or re-theme phases that
|
|
184
|
+
are already correct. Only add a phase, move a requirement to a different phase,
|
|
185
|
+
or correct a delivers-list where the plan genuinely changed.
|
|
186
|
+
- **Reuse existing phase refs.** A phase that already exists keeps its
|
|
187
|
+
`roadmap-phase-<slug>` ref — never mint a second ref for the same release. Refs
|
|
188
|
+
are unique (a `DUPLICATE_REF` is an ERROR that silently drops a phase).
|
|
189
|
+
- **Never orphan a deliver-ref.** A phase's `deliversRequirementRefs` /
|
|
190
|
+
`deliversSuccessCriterionRefs` must name refs that exist in the requirements /
|
|
191
|
+
vision families. These cross-family refs are resolution-checked **fail-soft**
|
|
192
|
+
(the check is skipped while the families are decoupled and no ref set is
|
|
193
|
+
supplied), so honest planning must not name a requirement or success criterion
|
|
194
|
+
that does not exist in the first place.
|
|
195
|
+
- **Each ref in at most one phase.** A requirement/success-criterion is delivered
|
|
196
|
+
by the earliest phase that delivers it; do not re-list it in later phases.
|
|
197
|
+
|
|
198
|
+
## Quality gate
|
|
199
|
+
|
|
200
|
+
The RoadmapSnapshot is checked by the deterministic `roadmap-valid` gate
|
|
201
|
+
(`validateRoadmapSnapshot`) before anything downstream consumes it. The invariants
|
|
202
|
+
it enforces (verified issue catalogue):
|
|
203
|
+
|
|
204
|
+
- **`INVALID_REF_FORMAT` (ERROR)** — a phase ref is not kebab-case with the
|
|
205
|
+
`roadmap-phase-` prefix.
|
|
206
|
+
- **`DUPLICATE_REF` (ERROR)** — two phases share a ref; the collection is
|
|
207
|
+
addressed by ref, so a duplicate silently drops a phase.
|
|
208
|
+
- **`DUPLICATE_SEQUENCE` (WARN)** — two phases share a `sequence`; the order
|
|
209
|
+
between them is ambiguous (no data lost, so a WARN). Give each phase a distinct
|
|
210
|
+
`sequence`.
|
|
211
|
+
- **`DUPLICATE_CROSS_REF` (WARN)** — the same deliver-ref is listed more than
|
|
212
|
+
once on ONE phase's deliver-list (each of the two lists is its own namespace, so
|
|
213
|
+
the same ref appearing once in each list is NOT a duplicate). Remove the repeat.
|
|
214
|
+
- **`NO_PHASES` (WARN)** — the roadmap plans no phases; it describes no delivery.
|
|
215
|
+
- **`STALE_AUTHORED` (WARN)** — a phase's `authored.lastAuthoredAt` is older than
|
|
216
|
+
its `reviewCadence`.
|
|
217
|
+
- **`UNKNOWN_REQUIREMENT_REF` / `UNKNOWN_SUCCESS_CRITERION_REF` (ERROR, fail-soft)**
|
|
218
|
+
— a `deliversRequirementRefs` / `deliversSuccessCriterionRefs` entry does not
|
|
219
|
+
resolve against a supplied ref set. These are **SKIPPED (fail-soft) when no ref
|
|
220
|
+
set is passed** — the roadmap family is decoupled from the requirements/vision
|
|
221
|
+
families and the catalog owns cross-family resolution, so authoring a roadmap
|
|
222
|
+
before those registries are fully wired does NOT crash-loop. Even so, only name
|
|
223
|
+
refs that really exist (see "Never orphan a deliver-ref").
|
|
224
|
+
|
|
225
|
+
## Scaffold-depth boundary (deferred to a later depth phase)
|
|
226
|
+
|
|
227
|
+
Keep this playbook at scaffold depth. Explicitly **out of scope here**:
|
|
228
|
+
|
|
229
|
+
- **Typed timeline / scheduling.** `targetWindow` is free prose and ordering is a
|
|
230
|
+
coarse `sequence` integer. Start/end dates, date math, and calendar alignment
|
|
231
|
+
are a later-phase concern — a phase says "first 3 months post-launch" as prose
|
|
232
|
+
today, not a typed interval. Do NOT build a schedule model.
|
|
233
|
+
- **Inter-phase dependency graph.** Phases are an ordered list, not a DAG. Edges
|
|
234
|
+
between phases (phase B needs phase A's delivery) are a later-phase concern.
|
|
235
|
+
- **Capacity / velocity / estimation and prioritization frameworks.** A phase is a
|
|
236
|
+
themed bucket of deliver-refs, not an estimated, capacity-fitted, RICE/WSJF/MoSCoW-
|
|
237
|
+
ranked plan. If you catch yourself estimating effort or building a prioritization
|
|
238
|
+
model, **stop** — that is depth-phase work.
|
|
239
|
+
- **A typed out-of-scope / explicitly-deferred axis** (see the scope decision
|
|
240
|
+
above) — a `_core/roadmap` reshape, filed as a depth-phase item, not built here.
|
|
241
|
+
- **Requirement priority + inter-requirement dependency.** A requirement has no
|
|
242
|
+
MoSCoW/priority axis and no "requirement A needs B" edge; only the roadmap
|
|
243
|
+
`sequence` approximates ordering. Do NOT reshape the requirements contract to add
|
|
244
|
+
them — it is a filed depth-phase question.
|
|
245
|
+
- **A dedicated non-functional-requirement delivery axis.** `deliversRequirementRefs`
|
|
246
|
+
today carries functional AND non-functional refs against one combined pool. Some
|
|
247
|
+
NFRs are cross-cutting quality attributes (accessibility, latency) that no single
|
|
248
|
+
phase "delivers" — whether NFRs deserve their own phase-delivery axis (or a
|
|
249
|
+
per-phase quality bar) rather than sharing `deliversRequirementRefs` is a
|
|
250
|
+
depth-phase question. At scaffold depth, slot a phase-specific NFR into
|
|
251
|
+
`deliversRequirementRefs` and leave universal NFRs unphased; do NOT reshape
|
|
252
|
+
`_core` for a separate axis here.
|
|
253
|
+
- **Per-phase ICP/segment targeting.** A phase cannot declare the primary
|
|
254
|
+
ICP/segment it serves; that is a filed depth-phase gap. Note it in prose if it
|
|
255
|
+
matters; do NOT reshape `_core` to add a typed edge.
|
|
256
|
+
- **Deterministic feature → phase traceability.** Because a requirement carries no
|
|
257
|
+
typed market pain/gain edge (and no typed feature → requirement edge), the
|
|
258
|
+
feature → benefit → requirement → phase trace is prose-only. Whether the
|
|
259
|
+
requirements family should gain a pain/gain edge is a filed depth-phase question —
|
|
260
|
+
do NOT reshape the requirements or roadmap contract here.
|
|
261
|
+
|
|
262
|
+
If you find yourself perfecting any of the above, stop and leave the slice at
|
|
263
|
+
scaffold depth — depth is a dedicated later pass done once, holistically.
|
|
264
|
+
|
|
265
|
+
## What you emit
|
|
266
|
+
|
|
267
|
+
One artifact for this journey: the **roadmap** at
|
|
268
|
+
`specifications/src/roadmap/index.ts` — a `RoadmapSnapshot` whose `phases`
|
|
269
|
+
are the ordered, MVP-first releases, each with a distinct `sequence`, a coarse
|
|
270
|
+
`horizon` + `kind`, and its `deliversRequirementRefs` / `deliversSuccessCriterionRefs`
|
|
271
|
+
wired — passing the `roadmap-valid` gate.
|
|
272
|
+
|
|
273
|
+
The creator reviews the result (approval posture `approve_result`) before it is
|
|
274
|
+
accepted as the journey's roadmap.
|
|
275
|
+
|
|
276
|
+
## References
|
|
277
|
+
|
|
278
|
+
- `.claude/skills/journey-status/SKILL.md` — read the current journey state and
|
|
279
|
+
scope, and confirm a `market-snapshot` (the capability map) already exists to
|
|
280
|
+
plan releases from.
|
|
@@ -0,0 +1,87 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ref": "top_down.scope-roadmap",
|
|
3
|
+
"version": "0.1.0",
|
|
4
|
+
"phase": "top_down",
|
|
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
|
+
"functionalTopics": [],
|
|
7
|
+
"preconditions": [
|
|
8
|
+
{
|
|
9
|
+
"kind": "phase_is",
|
|
10
|
+
"phase": "top_down"
|
|
11
|
+
},
|
|
12
|
+
{
|
|
13
|
+
"kind": "artifact_valid",
|
|
14
|
+
"selector": {
|
|
15
|
+
"family": "feature-drafts"
|
|
16
|
+
}
|
|
17
|
+
},
|
|
18
|
+
{
|
|
19
|
+
"kind": "artifact_valid",
|
|
20
|
+
"selector": {
|
|
21
|
+
"family": "market-snapshot"
|
|
22
|
+
}
|
|
23
|
+
},
|
|
24
|
+
{
|
|
25
|
+
"kind": "artifact_valid",
|
|
26
|
+
"selector": {
|
|
27
|
+
"family": "requirements"
|
|
28
|
+
}
|
|
29
|
+
},
|
|
30
|
+
{
|
|
31
|
+
"kind": "artifact_valid",
|
|
32
|
+
"selector": {
|
|
33
|
+
"family": "vision-brief"
|
|
34
|
+
}
|
|
35
|
+
}
|
|
36
|
+
],
|
|
37
|
+
"inputs": [
|
|
38
|
+
{
|
|
39
|
+
"family": "feature-drafts"
|
|
40
|
+
},
|
|
41
|
+
{
|
|
42
|
+
"family": "market-snapshot"
|
|
43
|
+
},
|
|
44
|
+
{
|
|
45
|
+
"family": "requirements"
|
|
46
|
+
},
|
|
47
|
+
{
|
|
48
|
+
"family": "vision-brief"
|
|
49
|
+
}
|
|
50
|
+
],
|
|
51
|
+
"outputs": [
|
|
52
|
+
{
|
|
53
|
+
"family": "roadmap",
|
|
54
|
+
"schemaRef": "saas-specifications:RoadmapSnapshot",
|
|
55
|
+
"description": "A validated ordered roadmap whose phases bind current-horizon requirements and success criteria."
|
|
56
|
+
}
|
|
57
|
+
],
|
|
58
|
+
"stepOutputs": [],
|
|
59
|
+
"method": {
|
|
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`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",
|
|
61
|
+
"skillRefs": [
|
|
62
|
+
"journey-status"
|
|
63
|
+
],
|
|
64
|
+
"elicitation": {
|
|
65
|
+
"questions": [
|
|
66
|
+
{
|
|
67
|
+
"ref": "mvp-cut",
|
|
68
|
+
"question": "What must be in the FIRST release for it to be worth shipping at all — and what are you happy to defer? Name the outcomes, not the features. Answer \"you decide\" if you would rather the plan propose a cut for you to react to.",
|
|
69
|
+
"kind": "free_text"
|
|
70
|
+
},
|
|
71
|
+
{
|
|
72
|
+
"ref": "delivery-pressure",
|
|
73
|
+
"question": "Is there a date, an event, or a commitment the first release has to meet? Answer \"none\" if the plan is shaped by scope rather than by a deadline.",
|
|
74
|
+
"kind": "free_text"
|
|
75
|
+
}
|
|
76
|
+
]
|
|
77
|
+
},
|
|
78
|
+
"contextSources": [],
|
|
79
|
+
"suspendsForClarification": false
|
|
80
|
+
},
|
|
81
|
+
"executor": "companion_agent",
|
|
82
|
+
"approval": "approve_result",
|
|
83
|
+
"budget": {
|
|
84
|
+
"maxRuns": 3
|
|
85
|
+
},
|
|
86
|
+
"onFailure": "keep_and_flag"
|
|
87
|
+
}
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"actionDefinition":{"actionRef":"application-creation:action/scope-roadmap","actionVersion":1,"allowedCapabilityClassRefs":["meta-workflow:capability-class/structured-artifact-generation"],"authorityRequirementRef":"application-creation:authority-requirement/scope-roadmap-result","budgetPolicyRef":"application-creation:budget-policy/scope-roadmap","continuationPolicyRef":"application-creation:continuation-policy/scope-roadmap","decisionPointDefinitionRefs":["application-creation:decision-point/scope-roadmap-result"],"effectSafetyPolicyRef":"application-creation:effect-safety/candidate-artifacts-before-acceptance","inputSelectorRefs":["application-creation:artifact-selector/accepted-feature-drafts","application-creation:artifact-selector/accepted-market-snapshot","application-creation:artifact-selector/accepted-requirements","application-creation:artifact-selector/accepted-vision-brief"],"intentRef":"application-creation:intent/derive-current-horizon-roadmap","outcomeContractRefs":["application-creation:output-contract/roadmap-snapshot"],"requiredCapabilityFacetRefs":["meta-workflow:capability-facet/atomic-output-set","meta-workflow:capability-facet/sealed-input-projection","meta-workflow:capability-facet/strict-provider-schema","meta-workflow:capability-facet/trusted-normalization"],"schemaVersion":1},"definitionRef":"application-creation:structured-artifact-action/scope-roadmap","definitionVersion":1,"driverDescriptor":{"descriptorRef":"meta-workflow:driver/structured-artifact-action","descriptorVersion":1},"inputProjectionContract":{"contractRef":"application-creation:input-projection/accepted-capability-map-definition-set","contractVersion":1},"normalizationContract":{"contractRef":"saas-specifications:normalizer/roadmap-snapshot-generation","contractVersion":1},"outputContract":{"acceptedArtifactClassificationRefs":["application-creation:artifact-classification/candidate-specification-family-snapshot"],"canonicalSerializationRef":"meta-workflow:canonicalization/wildo-json","canonicalSerializationVersion":1,"cardinality":"ONE","contentClass":"STRUCTURED_RECORD","invalidOutputDisposition":"FAIL_BINDING","outputContractRef":"application-creation:output-contract/roadmap-snapshot","outputContractVersion":1,"outputSchemaRef":"saas-specifications:schema/roadmap-snapshot","outputSchemaVersion":1,"schemaVersion":1,"validatorContractRef":"saas-specifications:validator/roadmap-snapshot","validatorContractVersion":1},"outputSetCommitment":"ATOMIC","providerOutputSchema":{"schemaRef":"saas-specifications:schema/roadmap-snapshot-generation","schemaVersion":1},"requiredFailureDispositions":["FAIL_BINDING","REQUEST_INPUT","RETRY_NEW_BINDING"],"requiredLifecycleFacets":[],"schemaVersion":1}
|
|
@@ -0,0 +1,204 @@
|
|
|
1
|
+
# Value Proposition & Positioning — Sharpen Method (v1 scaffold)
|
|
2
|
+
|
|
3
|
+
### Target Application Framing
|
|
4
|
+
|
|
5
|
+
This knowledge is for configuring behavior in the target application.
|
|
6
|
+
Wildo is the framework surface being used, not the product being built.
|
|
7
|
+
|
|
8
|
+
Read and apply these patterns from the application-developer point of view:
|
|
9
|
+
|
|
10
|
+
- how the application should configure the relevant app-level file
|
|
11
|
+
- how the application should use framework-provided factories, enums, and helpers
|
|
12
|
+
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
> **This is a v1 scaffold methodology.** It is a working first cut meant to
|
|
16
|
+
> be iterated. The refinement order, the benefit-weighting posture, and the
|
|
17
|
+
> "sharpen vs. leave" rules below are deliberately explicit so they can be
|
|
18
|
+
> tuned against real runs — treat them as a starting rubric, not a frozen
|
|
19
|
+
> contract. The *analytical depth* of the value-proposition work (quantified
|
|
20
|
+
> FIT / Kano scoring precision, positioning rigor) is intentionally shallow
|
|
21
|
+
> here and is deepened in a later phase; do not perfect it in this playbook.
|
|
22
|
+
|
|
23
|
+
## What this playbook does
|
|
24
|
+
|
|
25
|
+
You are the **positioning strategist**. Market-analysis already produced the
|
|
26
|
+
**MarketSnapshot** — the category, ICPs, personas, and jobs/pains/gains. Your
|
|
27
|
+
one job is to **sharpen the value-proposition slices of that same snapshot**:
|
|
28
|
+
the benefits, the tones of voice, and the per-ICP positioning pillars, framed
|
|
29
|
+
by the product's **VisionSnapshot** differentiation. You do not create a new
|
|
30
|
+
artifact family — benefits, tone-of-voice, and positioning all live *inside*
|
|
31
|
+
`MarketSnapshot`. You read the existing snapshot, tighten these three slices,
|
|
32
|
+
and re-emit the same snapshot.
|
|
33
|
+
|
|
34
|
+
This is a **focused refinement pass**, distinct from market-analysis (which
|
|
35
|
+
does the broad initial market sweep). Where market-analysis lays down the
|
|
36
|
+
whole snapshot at a first-pass depth, you come back over the value-proposition
|
|
37
|
+
slices specifically and make them sharp, consistent with each other, and true
|
|
38
|
+
to the vision.
|
|
39
|
+
|
|
40
|
+
The three slices you own, in dependency order (later slices reference earlier
|
|
41
|
+
refs, and all reference the jobs/pains/gains the market pass already authored):
|
|
42
|
+
|
|
43
|
+
1. **Benefits** — the outcome claims the product delivers (`FeatureBenefit`),
|
|
44
|
+
each a *weighted* set of edges: the pains it **relieves**, the gains it
|
|
45
|
+
**creates**, and the jobs it **advances**, every edge carrying a `degree`
|
|
46
|
+
(1..10) the FIT scorer multiplies by the ICP's own edge weight. Layer on
|
|
47
|
+
`importanceByICP`: a per-ICP `weight` plus a **Kano category** from the
|
|
48
|
+
`BenefitKanoCategory` enum — `THRESHOLD` (a must-have; its absence breaks
|
|
49
|
+
the deal), `PERFORMANCE` (more is better), `DELIGHTER` (unexpected upside),
|
|
50
|
+
plus `INDIFFERENT` / `REVERSE` for completeness — so the same benefit can
|
|
51
|
+
matter differently to different segments. Benefits reference the
|
|
52
|
+
pains/gains/jobs the market pass authored — never weight against a
|
|
53
|
+
pain/gain/job that does not exist. (`market-add-feature-benefit`)
|
|
54
|
+
- **Structural constraint (the U8 seam):** every benefit carries a
|
|
55
|
+
non-empty `deliveredByFeatureRefs[]` — a benefit must be *deliverable*.
|
|
56
|
+
At this top-down phase there is no feature registry yet, so these are
|
|
57
|
+
**forward-reference** feature refs; the `ORPHAN_REF` resolution check is
|
|
58
|
+
skipped until a feature set exists. **Wiring benefits to real spec-first
|
|
59
|
+
feature drafts is the capability-map playbook's job (U8), not yours** —
|
|
60
|
+
do not invent the feature registry here. Keep the refs you inherit;
|
|
61
|
+
leave a placeholder ref only where the market pass already did.
|
|
62
|
+
2. **Tones of voice** — the named brand voices the product speaks in
|
|
63
|
+
(`ToneOfVoice`, addressed by `ToneOfVoiceRef`). Keep them few and distinct;
|
|
64
|
+
each positioning and message template later speaks in one of them.
|
|
65
|
+
(`market-tone-of-voice`)
|
|
66
|
+
3. **Positioning** — the per-ICP marketing-truth promise (`MarketPositioning`):
|
|
67
|
+
author **one positioning entry per ICP the product actually targets**
|
|
68
|
+
(priority `CORE` or `EXPANSION`), each carrying **2–4 value pillars**
|
|
69
|
+
(`valuePillars`) — the sharp claims that separate the product from the
|
|
70
|
+
alternatives. Each pillar hangs off the weighted benefits above (it traces
|
|
71
|
+
back to `FeatureBenefitRef[]`) and is framed by the vision's
|
|
72
|
+
differentiation. (`market-positioning-authoring`)
|
|
73
|
+
|
|
74
|
+
Sharpen only the slices the product's stage warrants. A snapshot whose
|
|
75
|
+
benefits carry honest relieves/creates/advances weighting with per-ICP Kano
|
|
76
|
+
categories, at least one tone of voice, and one positioning entry (with its
|
|
77
|
+
value pillars) per `CORE`/`EXPANSION` ICP is a legitimate v1; the depth of the
|
|
78
|
+
weighting and the pillar prose is additive.
|
|
79
|
+
|
|
80
|
+
## Frame everything by the vision
|
|
81
|
+
|
|
82
|
+
The **VisionSnapshot** (`vision-brief` family) is your differentiation anchor.
|
|
83
|
+
Read its mission, its problem framing, and its success criteria before you
|
|
84
|
+
weight a single benefit. A benefit's weight, a Kano category, and a positioning
|
|
85
|
+
pillar are only *right* if they express the product's actual differentiation —
|
|
86
|
+
what the vision says makes this product worth building over the alternatives.
|
|
87
|
+
When a benefit or pillar cannot be traced back to the vision's differentiation,
|
|
88
|
+
that is a signal to either sharpen the vision link or drop the claim, not to
|
|
89
|
+
invent a promise the product does not stand behind.
|
|
90
|
+
|
|
91
|
+
## Where the snapshot lives
|
|
92
|
+
|
|
93
|
+
The MarketSnapshot for this journey is at
|
|
94
|
+
`specifications/src/market/index.ts`. That is the artifact this
|
|
95
|
+
playbook refines in place — you read it, sharpen the value-proposition slices,
|
|
96
|
+
and write the same artifact back. When the product's definition later
|
|
97
|
+
stabilises, the snapshot is what seeds the durable market specification under
|
|
98
|
+
`./specifications/` — but at this phase it is a journey artifact, not yet app
|
|
99
|
+
source.
|
|
100
|
+
|
|
101
|
+
## Refine, don't re-author — read state first
|
|
102
|
+
|
|
103
|
+
This playbook is **idempotent** and, by construction, a *refinement*: a
|
|
104
|
+
MarketSnapshot must already exist (the `artifact_exists` precondition enforces
|
|
105
|
+
it). Before sharpening anything:
|
|
106
|
+
|
|
107
|
+
1. Read the current journey state and scope through the `journey-status` skill
|
|
108
|
+
(it owns the read; do not re-derive it here) — that tells you which scope
|
|
109
|
+
the value proposition must hold *for*.
|
|
110
|
+
2. Read the existing MarketSnapshot at this playbook's placement path and the
|
|
111
|
+
VisionSnapshot at the `vision-brief` placement, so you sharpen against the
|
|
112
|
+
real market intent and the real differentiation, not from scratch.
|
|
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)
|
|
116
|
+
|
|
117
|
+
Then sharpen:
|
|
118
|
+
|
|
119
|
+
- **Keep what still holds.** Do not rewrite benefits, tones, or pillars that
|
|
120
|
+
are already sharp and vision-true. Only add/correct where the current
|
|
121
|
+
steering notes, the vision, or benefit-weight inconsistencies call for it.
|
|
122
|
+
- **Never orphan a ref.** A positioning names an ICP and its pillars name
|
|
123
|
+
benefits; a benefit names the pains/gains/jobs it relieves/creates/advances.
|
|
124
|
+
Dropping an ICP, pain, gain, job, or benefit that a positioning, pillar, or
|
|
125
|
+
benefit still points at orphans the downstream ref (the validator catches
|
|
126
|
+
this as `ORPHAN_REF`, but honest refinement should not create the orphan).
|
|
127
|
+
If a slice from the market pass is genuinely wrong, fix it at its source
|
|
128
|
+
slice, do not paper over it in the value-prop layer.
|
|
129
|
+
|
|
130
|
+
## Quality gate
|
|
131
|
+
|
|
132
|
+
Your re-emitted snapshot is checked by the deterministic `market-snapshot-valid`
|
|
133
|
+
gate (`validateMarketSnapshot`) before anything downstream consumes it. The
|
|
134
|
+
value-proposition invariants it enforces are mostly **`ERROR`-severity hard
|
|
135
|
+
failures** — the snapshot does not advance until they clear:
|
|
136
|
+
|
|
137
|
+
- **`MISSING_POSITIONING_FOR_ICP` (ERROR)** — a `CORE` or `EXPANSION` ICP has
|
|
138
|
+
no `MarketPositioning`. This is the headline gap this playbook closes: a
|
|
139
|
+
targeted ICP without a positioning is a *hard failure*, not a warning.
|
|
140
|
+
(`EXPLORATORY` / `DEFERRED` / `ANTI_TARGET` ICPs are exempt.)
|
|
141
|
+
- **`THRESHOLD_BENEFIT_WITHOUT_JOB` (ERROR)** — a benefit carries a
|
|
142
|
+
`kanoCategory: THRESHOLD` entry but its `advances[]` is empty; a must-have
|
|
143
|
+
claim needs a job to anchor against.
|
|
144
|
+
- **`MULTIPLE_THRESHOLDS_PER_ICP_JOB` (ERROR)** — two distinct benefits both
|
|
145
|
+
claim `THRESHOLD` for the same (icp, job); only one must-have per job.
|
|
146
|
+
- **`EMPTY_BENEFIT_DELIVERED_BY` (ERROR)** — a benefit's `deliveredByFeatureRefs[]`
|
|
147
|
+
is empty; every benefit must stay deliverable (see the U8 seam above).
|
|
148
|
+
- **`ORPHAN_REF` (ERROR)** — a positioning naming a missing ICP, a pillar or
|
|
149
|
+
benefit naming a missing pain/gain/job. (Feature-ref orphans are only
|
|
150
|
+
checked once a feature registry is passed — not at this phase.)
|
|
151
|
+
|
|
152
|
+
`WARN`-severity issues do not block but should be resolved: `DUPLICATE_EDGE_PER_ENTITY`
|
|
153
|
+
(a duplicate `(benefit, icp)` importance edge) and `STALE_AUTHORED` (a slice
|
|
154
|
+
past its review cadence). Read `market-snapshot-validation` for the full issue
|
|
155
|
+
catalogue and emit a clean snapshot the first time.
|
|
156
|
+
|
|
157
|
+
## Scaffold-depth boundary (deferred to a later depth phase)
|
|
158
|
+
|
|
159
|
+
Keep this playbook at scaffold depth. The following are explicitly **out of
|
|
160
|
+
scope here** and are deepened in the methodology-depth phase, not now:
|
|
161
|
+
|
|
162
|
+
- **Quantified FIT / Kano scoring precision** — `market-scoring-interpretation`
|
|
163
|
+
reads the deterministic FIT scorer; at scaffold depth you consume it to
|
|
164
|
+
sanity-check benefit weighting and Kano assignment, not to drive a precise
|
|
165
|
+
prioritization model. The prioritization seam stays pluggable (the
|
|
166
|
+
capability-map playbook owns wiring FIT scores into feature drafts). Do not
|
|
167
|
+
build a scoring model here.
|
|
168
|
+
- **Positioning rigor** — a pillar captures *the* sharp per-ICP promise; a
|
|
169
|
+
full competitive positioning matrix, message-market-fit testing, or
|
|
170
|
+
A/B-tested copy is later-phase work.
|
|
171
|
+
- **Message-template rendering** — this playbook stops at the value-proposition
|
|
172
|
+
slices (benefits / tone / pillars). Turning them into reusable message
|
|
173
|
+
templates stays with the market-analysis playbook's `market_message_templates`
|
|
174
|
+
slice.
|
|
175
|
+
|
|
176
|
+
If you find yourself perfecting any of the above, stop and leave the slice at
|
|
177
|
+
scaffold depth — depth is a dedicated later pass done once, holistically.
|
|
178
|
+
|
|
179
|
+
## What you emit
|
|
180
|
+
|
|
181
|
+
The SAME MarketSnapshot at `specifications/src/market/index.ts`,
|
|
182
|
+
with its value-proposition slices sharpened: weighted benefits with per-ICP
|
|
183
|
+
Kano categories, the tones of voice, and one positioning entry (with its 2–4
|
|
184
|
+
value pillars) per `CORE`/`EXPANSION` ICP — all framed by the vision's
|
|
185
|
+
differentiation — passing the
|
|
186
|
+
`market-snapshot-valid` gate. The creator reviews the result (approval posture
|
|
187
|
+
`approve_result`) before it is accepted as the journey's refined market intent.
|
|
188
|
+
|
|
189
|
+
## References
|
|
190
|
+
|
|
191
|
+
- `.claude/skills/journey-status/SKILL.md` — read the current journey state
|
|
192
|
+
and scope, and confirm a `market-snapshot` already exists to refine.
|
|
193
|
+
- `.claude/skills/market-add-feature-benefit/SKILL.md` — author the benefit
|
|
194
|
+
claims and their relieves/creates/advances weighting and per-ICP Kano
|
|
195
|
+
categories.
|
|
196
|
+
- `.claude/skills/market-tone-of-voice/SKILL.md` — author the named brand
|
|
197
|
+
voices.
|
|
198
|
+
- `.claude/skills/market-positioning-authoring/SKILL.md` — author the per-ICP
|
|
199
|
+
positioning entries and their 2–4 value pillars.
|
|
200
|
+
- `.claude/skills/market-scoring-interpretation/SKILL.md` — interpret the
|
|
201
|
+
deterministic FIT scorer to sanity-check benefit weighting and Kano
|
|
202
|
+
assignment (scaffold depth — sanity-check, not a scoring model).
|
|
203
|
+
- `.claude/skills/market-snapshot-validation/SKILL.md` — the full validation
|
|
204
|
+
issue catalogue the quality gate enforces.
|