@wildo-ai/framework-knowledge 1.1.5 → 1.1.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/claude-marketplace/.claude-plugin/marketplace.json +14 -0
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +8 -0
- package/dist/claude-marketplace/plugins/wildo/agents/wildo-deriver.md +41 -0
- package/dist/claude-marketplace/plugins/wildo/hooks/hooks.json +18 -0
- package/dist/claude-marketplace/plugins/wildo/monitors/monitors.json +8 -0
- package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +38 -0
- package/dist/{knowledge/skills/journey-run/references/framework-playbook-approval-policy.md → claude-marketplace/plugins/wildo/references/approval-and-failure-policy.md} +10 -8
- package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +29 -0
- package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +61 -0
- package/dist/{knowledge/skills/journey-run → claude-marketplace/plugins/wildo}/references/expert-personas-and-deliberations.md +8 -8
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +67 -0
- package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +43 -0
- package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +70 -0
- package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +38 -0
- package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +23 -0
- package/dist/claude-marketplace/plugins/wildo/skills/next/SKILL.md +39 -0
- package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +39 -0
- package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +38 -0
- package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +38 -0
- package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +37 -0
- package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +320 -11
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +0 -3
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +12 -2
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +33 -2
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +8 -5
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +55 -10
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +1 -6
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -6
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +13 -4
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +10 -3
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +7 -3
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +8 -3
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +7 -3
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +9 -4
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +3 -2
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +4 -3
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +1 -3
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +10 -3
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +8 -3
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +12 -5
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +33 -5
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts +59 -0
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js +72 -0
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +66 -0
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +115 -0
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +50 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +54 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +36 -17
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +67 -17
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts +45 -0
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +46 -0
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +11 -3
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
- package/dist/knowledge/manifest.json +8 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +0 -3
- package/dist/knowledge/playbooks/bottom_up.build/method.md +4 -2
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +31 -7
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +134 -26
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +7 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +84 -29
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -7
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +12 -23
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -7
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +12 -14
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -2
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +20 -2
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +15 -7
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +8 -6
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +11 -4
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +2 -4
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +3 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +18 -2
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +1 -2
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +2 -4
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +8 -5
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +16 -2
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +3 -3
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +1 -3
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +1 -2
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +8 -7
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +11 -4
- package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +27 -5
- package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +1 -4
- package/dist/knowledge/playbooks/cross_cutting.feature-development/method.md +42 -0
- package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +73 -0
- package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +46 -0
- package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +108 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +112 -21
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +7 -2
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +2 -4
- package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +48 -0
- package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +66 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +6 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +0 -4
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +1 -2
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +1 -3
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +2 -4
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -2
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +1 -3
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +5 -3
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +2 -4
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +1 -3
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +0 -4
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +2 -4
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +1 -3
- package/dist/knowledge/playbooks/top_down.definition/method.md +7 -4
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +52 -7
- package/dist/knowledge/playbooks/top_down.expert-personas/method.md +1 -1
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +2 -4
- package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +72 -0
- package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +57 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +0 -1
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -1
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +2 -4
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +1 -2
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +2 -6
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +17 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +2 -5
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +1 -3
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +15 -7
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +2 -4
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +2 -4
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +1 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +12 -5
- package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +212 -0
- package/dist/knowledge/references/backend.inbound-handlers.agents.md +45 -0
- package/dist/knowledge/references/backend.inbound-handlers.definition.md +218 -0
- package/dist/knowledge/references/build-plan.task-graph.config.md +71 -6
- package/dist/knowledge/references/capability-composition.config.md +20 -1
- package/dist/knowledge/references/cli.market.generate-command.md +18 -2
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +7 -22
- package/dist/knowledge/references/engine.saas-technical-doc.provider-component.slot.md +83 -0
- package/dist/knowledge/references/example.authorization.service-provider-organization-wide-access.md +12 -0
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +5 -0
- package/dist/knowledge/references/example.backend.custom-operation.create-postfix.md +7 -3
- package/dist/knowledge/references/example.config.app-shell.command-menu-items.md +7 -0
- package/dist/knowledge/references/example.config.app-shell.full.md +11 -0
- package/dist/knowledge/references/example.config.backend.billing-enable.md +14 -0
- package/dist/knowledge/references/example.config.backend.inbound-email.md +14 -0
- package/dist/knowledge/references/example.config.backend.required-floors.md +7 -0
- package/dist/knowledge/references/example.config.navigation.full.md +45 -2
- package/dist/knowledge/references/example.config.provider-usage-pricing.md +36 -0
- package/dist/knowledge/references/example.config.provider.backend-scope-billing.md +5 -3
- package/dist/knowledge/references/example.config.provider.backend-scope-inbound-email.md +16 -0
- package/dist/knowledge/references/example.flows-actors.autonomous-agent.md +23 -0
- package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +36 -0
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +26 -3
- package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +1 -1
- package/dist/knowledge/references/example.inbound.application-endpoint-handler.md +72 -0
- package/dist/knowledge/references/example.inbound.email-channel-handler.md +47 -0
- package/dist/knowledge/references/example.inbound.email-to-todo.md +150 -0
- package/dist/knowledge/references/example.infra.environment-config.local.md +14 -30
- package/dist/knowledge/references/example.layout-3d.own-layout.md +16 -0
- package/dist/knowledge/references/example.layout-3d.registration.md +15 -0
- package/dist/knowledge/references/example.module.companion-exports.full.md +8 -13
- package/dist/knowledge/references/example.module.relationships.discriminator.md +2 -2
- package/dist/knowledge/references/example.organizations.serves-as-provider.md +12 -0
- package/dist/knowledge/references/example.provider.address-lookup.adapter.md +64 -0
- package/dist/knowledge/references/example.provider.backend-module-shape.md +3 -0
- package/dist/knowledge/references/example.provider.frontend-app.module.md +9 -0
- package/dist/knowledge/references/example.provider.frontend-facet.package-module.md +85 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +14 -13
- package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +18 -0
- package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +11 -11
- package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +5 -0
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +2 -0
- package/dist/knowledge/references/example.resource.retention-binding.closure-event.md +21 -0
- package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +1 -2
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +24 -6
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +36 -25
- package/dist/knowledge/references/example.resource.work-unit.declaration.md +13 -0
- package/dist/knowledge/references/example.spec.composite-view.workspace.md +0 -12
- package/dist/knowledge/references/example.views.app-level.composite-views-config.md +1 -1
- package/dist/knowledge/references/example.views.chart-view.resource-owned.md +27 -0
- package/dist/knowledge/references/example.views.composite-view.workspace.md +4 -1
- package/dist/knowledge/references/example.website.page.manifest.md +30 -0
- package/dist/knowledge/references/experience-plan.config.md +11 -4
- package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +20 -0
- package/dist/knowledge/references/external-connectors.backend.provider-augmentation.md +75 -0
- package/dist/knowledge/references/external-connectors.frontend-provider-component-declaration.md +85 -0
- package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +52 -0
- package/dist/knowledge/references/external-connectors.models.connection-rate-budgets.md +113 -0
- package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +165 -0
- package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +133 -0
- package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +44 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +21 -0
- package/dist/knowledge/references/external-connectors.provider-component-load-state.md +45 -0
- package/dist/knowledge/references/external-connectors.provider-component-loader-contribution.md +32 -0
- package/dist/knowledge/references/external-connectors.provider-component-registry.md +190 -0
- package/dist/knowledge/references/external-connectors.techdoc.frontend-provider-module.md +91 -0
- package/dist/knowledge/references/external-connectors.website.frontend-provider-module.md +91 -0
- package/dist/knowledge/references/integration-plan.config.md +34 -2
- package/dist/knowledge/references/market.alternative.config.md +1 -1
- package/dist/knowledge/references/market.buying-journey.config.md +1 -1
- package/dist/knowledge/references/market.category.config.md +1 -1
- package/dist/knowledge/references/market.channel.config.md +1 -1
- package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
- package/dist/knowledge/references/market.gain.config.md +1 -1
- package/dist/knowledge/references/market.icp.config.md +1 -1
- package/dist/knowledge/references/market.job.config.md +1 -1
- package/dist/knowledge/references/market.message-template.config.md +1 -1
- package/dist/knowledge/references/market.objection.config.md +1 -1
- package/dist/knowledge/references/market.pain.config.md +1 -1
- package/dist/knowledge/references/market.persona.config.md +1 -1
- package/dist/knowledge/references/market.positioning.config.md +1 -1
- package/dist/knowledge/references/market.proof.config.md +1 -1
- package/dist/knowledge/references/market.references.weighted-edges.md +7 -0
- package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
- package/dist/knowledge/references/market.trigger.config.md +1 -1
- package/dist/knowledge/references/placement-plan.config.md +7 -1
- package/dist/knowledge/references/platform.config.backing-services.md +15 -15
- package/dist/knowledge/references/platform.config.infra-provider-resolution.md +57 -57
- package/dist/knowledge/references/presets.3d.frame-style-overrides.md +134 -0
- package/dist/knowledge/references/presets.3d.layout-contract.md +213 -0
- package/dist/knowledge/references/presets.3d.register-layout.md +95 -0
- package/dist/knowledge/references/presets.models.labelling.sections.md +5 -0
- package/dist/knowledge/references/presets.models.shell-region.md +47 -0
- package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -0
- package/dist/knowledge/references/saas.backend.actor-execution-decision-record.md +41 -0
- package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
- package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +7 -6
- package/dist/knowledge/references/saas.backend.compliance.governed-documents-pdf-template.md +370 -0
- package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +7 -0
- package/dist/knowledge/references/saas.backend.domain-module.md +93 -15
- package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +66 -0
- package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +31 -0
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +200 -0
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +2 -0
- package/dist/knowledge/references/saas.backend.pdf-template.collection-definition.md +73 -0
- package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +33 -9
- package/dist/knowledge/references/saas.backend.submission-challenge.md +118 -0
- package/dist/knowledge/references/saas.backend.system-access-service.md +98 -0
- package/dist/knowledge/references/saas.backend.system-of-record-action-runner.md +73 -0
- package/dist/knowledge/references/saas.config.providers.augmentations.md +61 -0
- package/dist/knowledge/references/saas.config.providers.packages.md +59 -0
- package/dist/knowledge/references/saas.config.providers.shared-connections.md +84 -0
- package/dist/knowledge/references/saas.external-data.admin-endpoints.md +56 -2
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +2 -2
- package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +250 -0
- package/dist/knowledge/references/saas.frontend.billing-context.md +25 -2
- package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +92 -0
- package/dist/knowledge/references/saas.frontend.consent-based-provider-activation.md +22 -0
- package/dist/knowledge/references/saas.frontend.form-field-address.lookup-slot.md +74 -0
- package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +60 -0
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +7 -5
- package/dist/knowledge/references/saas.frontend.notifications.publish-badge-count.md +60 -0
- package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +17 -2
- package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +49 -0
- package/dist/knowledge/references/saas.frontend.related-resource-sections.md +8 -1
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +9 -0
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +100 -5
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +25 -1
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +61 -0
- package/dist/knowledge/references/saas.market.generation-agent.md +0 -1
- package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +34 -0
- package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +45 -0
- package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +107 -0
- package/dist/knowledge/references/saas.models.agent-work-output-review.md +36 -0
- package/dist/knowledge/references/saas.models.agent-work-override-rate.md +50 -0
- package/dist/knowledge/references/saas.models.agent-work-review-config.md +24 -0
- package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +97 -0
- package/dist/knowledge/references/saas.models.audit.trail-config.md +15 -9
- package/dist/knowledge/references/saas.models.auth.service-provider-client-authentication.md +169 -0
- package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +8 -0
- package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +54 -1
- package/dist/knowledge/references/saas.models.billing.referral-program.md +47 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +74 -0
- package/dist/knowledge/references/saas.models.config.tenant-teardown.md +31 -14
- package/dist/knowledge/references/saas.models.conversation-threads.md +242 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +4 -4
- package/dist/knowledge/references/saas.models.engine-capabilities.md +12 -0
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +5 -1
- package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +39 -0
- package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +38 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +667 -6
- package/dist/knowledge/references/saas.models.flows-actors.autonomous-agents-vocabulary.md +98 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-decision-vocabulary.md +52 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-calendar.md +42 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +84 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +69 -0
- package/dist/knowledge/references/saas.models.frontend-provider-public-config-contract.md +72 -0
- package/dist/knowledge/references/saas.models.http-api-binding.md +812 -29
- package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +81 -0
- package/dist/knowledge/references/saas.models.human-decision-review-marker.md +20 -0
- package/dist/knowledge/references/saas.models.inbound-channels.md +277 -0
- package/dist/knowledge/references/saas.models.inbound-email-domains.md +101 -0
- package/dist/knowledge/references/saas.models.inbound-email.md +111 -0
- package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +28 -0
- package/dist/knowledge/references/saas.models.model-cost-summary.md +87 -0
- package/dist/knowledge/references/saas.models.navigation.layout.md +11 -7
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +32 -23
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +8 -4
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +22 -20
- package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +14 -0
- package/dist/knowledge/references/saas.models.notifications.targets.md +20 -12
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +61 -34
- package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +9 -0
- package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +121 -0
- package/dist/knowledge/references/saas.models.organizations.service-provider-capability-grants.md +152 -0
- package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +49 -0
- package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +567 -0
- package/dist/knowledge/references/saas.models.privacy.legal-holds.md +172 -0
- package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +104 -0
- package/dist/knowledge/references/saas.models.privacy.retention-binding.md +103 -0
- package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +120 -0
- package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +147 -0
- package/dist/knowledge/references/saas.models.privacy.statutory-retention-ground.md +50 -0
- package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +388 -0
- package/dist/knowledge/references/saas.models.provider-address-lookup-contract.md +139 -0
- package/dist/knowledge/references/saas.models.provider-address-lookup-declaration.md +61 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +34 -0
- package/dist/knowledge/references/saas.models.provider-credential-identity.md +67 -0
- package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +139 -0
- package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +61 -0
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +98 -13
- package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +57 -0
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -28
- package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +54 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +6 -0
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +8 -0
- package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +82 -0
- package/dist/knowledge/references/saas.models.system-of-record-actions.md +226 -0
- package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +461 -0
- package/dist/knowledge/references/saas.models.systems-of-record.facet-augmentation.md +63 -0
- package/dist/knowledge/references/saas.models.systems-of-record.md +242 -7
- package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +109 -0
- package/dist/knowledge/references/saas.models.work-unit-ref.md +28 -0
- package/dist/knowledge/references/saas.public-runtime.contract.md +75 -7
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +20 -0
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +106 -13
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +14 -13
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.discriminated-union.md +36 -14
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-aggregate-offer.md +4 -3
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-product.md +4 -4
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-software-application.md +71 -0
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +6 -4
- package/dist/knowledge/references/saas.specifications.compliance.retention-enforcement-state.md +32 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +14 -2
- package/dist/knowledge/references/saas.specifications.processor-register.md +77 -0
- package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +71 -0
- package/dist/knowledge/references/saas.specifications.recipient-population.md +549 -0
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +112 -45
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +13 -1
- package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +17 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-frontend-prose.md +16 -0
- package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +98 -0
- package/dist/knowledge/references/saas.website.astro.bridge.md +32 -9
- package/dist/knowledge/references/saas.website.astro.head-renderer.md +1 -1
- package/dist/knowledge/references/saas.website.astro.label-loader.md +7 -4
- package/dist/knowledge/references/saas.website.astro.robots-renderer.md +15 -15
- package/dist/knowledge/references/saas.website.astro.site-context.md +5 -2
- package/dist/knowledge/references/saas.website.blog.bridge.md +17 -4
- package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +61 -0
- package/dist/knowledge/references/saas.website.config.site-context-loader.md +154 -0
- package/dist/knowledge/references/saas.website.consent.banner.md +10 -10
- package/dist/knowledge/references/saas.website.design-tokens.colors.md +7 -4
- package/dist/knowledge/references/saas.website.design-tokens.radius.md +1 -1
- package/dist/knowledge/references/saas.website.factories.define-section.md +3 -3
- package/dist/knowledge/references/saas.website.page-layout.component.md +5 -2
- package/dist/knowledge/references/saas.website.pricing-offer-structured-data.md +140 -0
- package/dist/knowledge/references/saas.website.provider-component.slot.md +99 -0
- package/dist/knowledge/references/saas.website.root-config.schema.md +6 -6
- package/dist/knowledge/references/saas.website.runtime.context.md +23 -4
- package/dist/knowledge/references/saas.website.sections.definition-schema.md +14 -7
- package/dist/knowledge/references/saas.website.seo.robots-config.md +4 -3
- package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +7 -5
- package/dist/knowledge/references/saas.website.submission-challenge.md +77 -0
- package/dist/knowledge/references/saas.website.use-pricing-catalog.hook.md +36 -0
- package/dist/knowledge/references/saas.website.use-runtime.hook.md +3 -2
- package/dist/knowledge/references/website-plan.config.md +39 -6
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +2 -1
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +21 -0
- package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +1 -2
- package/dist/knowledge/references/zod.decorators.file-schema.md +11 -10
- package/dist/knowledge/references/zod.decorators.file-vocabularies.md +7 -4
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +8 -2
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +5 -1
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +5 -1
- package/dist/knowledge/references/zod.factories.address.md +7 -7
- package/dist/knowledge/references/zod.factories.code.md +2 -2
- package/dist/knowledge/references/zod.factories.duration.md +4 -4
- package/dist/knowledge/references/zod.factories.money.md +3 -3
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +1238 -54
- package/dist/knowledge/registries/playbooks.json +81 -109
- package/dist/knowledge/registries/source-tags.json +3191 -1126
- package/dist/knowledge/rules/live-context-door.md +29 -0
- package/dist/knowledge/skills/INDEX.md +27 -24
- package/dist/knowledge/skills/agent-work-review/SKILL.md +141 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +38 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +40 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +54 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +28 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +108 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +111 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +43 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +42 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +31 -0
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +1 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +1 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +9 -0
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +94 -16
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +21 -8
- package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +7 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +13 -5
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +30 -6
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +160 -32
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +20 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +14 -2
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +88 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +112 -14
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +209 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +577 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +549 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +21 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +2 -2
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +276 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-shell-region-markers-api.md +66 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +1 -0
- package/dist/knowledge/skills/config-navigation/SKILL.md +114 -16
- package/dist/knowledge/skills/config-navigation/references/choosing-a-navigation-shape.md +314 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +11 -7
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +29 -5
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +40 -27
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +22 -20
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +112 -5
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +10 -10
- package/dist/knowledge/skills/config-navigation/references/navigation-zones.md +1 -1
- package/dist/knowledge/skills/config-saas/SKILL.md +3 -1
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +7 -0
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +21 -11
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +5 -1
- package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +59 -9
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +46 -0
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +251 -12
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +8 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +81 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +37 -15
- package/dist/knowledge/skills/configure-billing/SKILL.md +64 -24
- package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +35 -2
- package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +14 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +3 -0
- package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +25 -2
- package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +73 -1
- package/dist/knowledge/skills/configure-billing/references/framework-referral-program.md +110 -0
- package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +27 -12
- package/dist/knowledge/skills/configure-coding-agent/SKILL.md +11 -2
- package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +26 -2
- package/dist/knowledge/skills/email-add-template/SKILL.md +61 -24
- package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +5 -2
- package/dist/knowledge/skills/email-definition-wiring/SKILL.md +1 -0
- package/dist/knowledge/skills/email-labels-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/email-template-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/engine-component-registration/SKILL.md +1 -0
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +6 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +27 -3
- package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +180 -0
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +56 -0
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +208 -0
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +51 -0
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +27 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +31 -4
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +26 -3
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +148 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +287 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +202 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +93 -15
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +96 -11
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +2 -1
- package/dist/knowledge/skills/frontend-cdn-publish/SKILL.md +1 -0
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +1 -0
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -2
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +14 -9
- package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/i18n-label-generation/SKILL.md +1 -0
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +5 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +11 -9
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +5 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +8 -1
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +5 -0
- package/dist/knowledge/skills/i18n-translation-rerun/references/translation-workflow.md +5 -0
- package/dist/knowledge/skills/inbound-channels/SKILL.md +301 -0
- package/dist/knowledge/skills/inbound-channels/references/email-channel.md +133 -0
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +800 -0
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +222 -0
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +231 -0
- package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +135 -0
- package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +297 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +150 -44
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +83 -74
- package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +176 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +141 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +223 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +103 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +256 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-region-marker-api.md +52 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/layouts-and-transitions.md +29 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +25 -0
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +32 -1
- package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +2 -1
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +36 -4
- package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +2 -1
- package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
- package/dist/knowledge/skills/market-alternatives/SKILL.md +3 -2
- package/dist/knowledge/skills/market-authoring-overview/SKILL.md +1 -0
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +7 -0
- package/dist/knowledge/skills/market-category/SKILL.md +2 -1
- package/dist/knowledge/skills/market-channels/SKILL.md +2 -1
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +7 -4
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +6 -4
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +28 -13
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +18 -3
- package/dist/knowledge/skills/market-icp/SKILL.md +2 -1
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +4 -3
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
- package/dist/knowledge/skills/market-persona/SKILL.md +2 -1
- package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/market-positioning-authoring/references/framework-positioning-api.md +1 -1
- package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +3 -2
- package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +1 -0
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +1 -0
- package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +2 -1
- package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +3 -2
- package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +1 -0
- package/dist/knowledge/skills/minion-authoring/SKILL.md +5 -1
- package/dist/knowledge/skills/model-cost-attribution/SKILL.md +143 -0
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +211 -0
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +95 -0
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +117 -0
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +677 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +17 -16
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +6 -4
- package/dist/knowledge/skills/module-registration/SKILL.md +2 -1
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +93 -15
- package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +86 -1
- package/dist/knowledge/skills/module-relationships/SKILL.md +3 -2
- package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +34 -2
- package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +447 -0
- package/dist/knowledge/skills/provider-address-lookup/SKILL.md +207 -0
- package/dist/knowledge/skills/provider-address-lookup/references/framework-address-field-lookup-slot-api.md +82 -0
- package/dist/knowledge/skills/provider-address-lookup/references/framework-address-lookup-contract-api.md +214 -0
- package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +143 -0
- package/dist/knowledge/skills/provider-address-lookup/references/google-places-setup.md +73 -0
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +272 -33
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-augmentation-api.md +227 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-credential-identity-api.md +101 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +245 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +88 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-allow-list-api.md +111 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +309 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +132 -23
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +399 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +29 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-public-config-api.md +115 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-provider-component-registry-api.md +386 -0
- package/dist/knowledge/skills/provider-frontend-module/SKILL.md +258 -0
- package/dist/knowledge/skills/provider-frontend-module/references/framework-frontend-facet-contracts-api.md +463 -0
- package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +61 -0
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +75 -24
- package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +3 -3
- package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +61 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-connection-rate-budgets-api.md +176 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +17 -2
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +15 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +127 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +25 -0
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +6 -0
- package/dist/knowledge/skills/resource-add-field/SKILL.md +1 -0
- package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +1 -2
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +105 -6
- package/dist/knowledge/skills/resource-add-module/SKILL.md +1 -0
- package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +2 -1
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +3 -0
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +124 -30
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +1 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +8 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +9 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +17 -1
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +124 -30
- package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +7 -6
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +142 -34
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +98 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +86 -52
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +1 -0
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +100 -5
- package/dist/knowledge/skills/resource-external-data/SKILL.md +1026 -28
- package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +144 -0
- package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +68 -0
- package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +154 -0
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +686 -11
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +904 -31
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +166 -6
- package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +152 -0
- package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +60 -0
- package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +179 -0
- package/dist/knowledge/skills/resource-external-data/references/pipeline-destination-schema.md +1 -1
- package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +63 -0
- package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +122 -0
- package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +745 -0
- package/dist/knowledge/skills/resource-external-data/references/remote-references.md +85 -0
- package/dist/knowledge/skills/resource-external-data/references/rest-keyset-sources.md +85 -0
- package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +442 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +1 -0
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +1 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +12 -0
- package/dist/knowledge/skills/resource-retention-binding/SKILL.md +186 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +200 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +111 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +173 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +155 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +139 -0
- package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +55 -0
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +2 -2
- package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +1 -2
- package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +3 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +2 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +28 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +5 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +34 -30
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +5 -1
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +101 -42
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +21 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +1 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +125 -6
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +8 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +57 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +61 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +110 -9
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/seeding-operations/SKILL.md +1 -0
- package/dist/knowledge/skills/service-provider-relationships/SKILL.md +455 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +270 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +129 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +161 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +224 -0
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +576 -0
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +61 -0
- package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +43 -37
- package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +15 -14
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +14 -16
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +6 -4
- package/dist/knowledge/skills/spec-component-update/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +20 -21
- package/dist/knowledge/skills/spec-family-update/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-feature-update/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +13 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +158 -46
- package/dist/knowledge/skills/spec-update-after-change/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +17 -0
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +5 -1
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +1 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +2 -1
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +43 -1
- package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +102 -0
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +5 -1
- package/dist/knowledge/skills/views-composite-authoring/references/composite-embedding-checklist.md +3 -2
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +29 -6
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +3 -2
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +17 -4
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +23 -28
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +7 -22
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +167 -20
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +4 -3
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +63 -6
- package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +275 -0
- package/dist/knowledge/skills/website-label-pack/SKILL.md +13 -5
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +6 -2
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -2
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +117 -33
- package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +164 -0
- package/dist/knowledge/skills/website-page-variants/SKILL.md +1 -0
- package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +1 -0
- package/dist/knowledge/skills/website-section-contact/SKILL.md +65 -36
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-cta/SKILL.md +32 -22
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-faq/SKILL.md +99 -63
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +27 -18
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +33 -22
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +31 -20
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-hero/SKILL.md +65 -44
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +217 -200
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +248 -0
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +45 -34
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -11
- package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +8 -3
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +64 -34
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +30 -25
- package/dist/knowledge/skills/worker-authoring/SKILL.md +1 -0
- package/dist/knowledge/topic-index.json +5887 -1695
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/knowledge/skills/journey-approve/SKILL.md +0 -63
- package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +0 -77
- package/dist/knowledge/skills/journey-next/SKILL.md +0 -82
- package/dist/knowledge/skills/journey-report/SKILL.md +0 -56
- package/dist/knowledge/skills/journey-run/SKILL.md +0 -140
- package/dist/knowledge/skills/journey-status/SKILL.md +0 -60
- /package/dist/{knowledge/skills/journey-approve → claude-marketplace/plugins/wildo}/references/specification-family-map.md +0 -0
|
@@ -37,13 +37,15 @@
|
|
|
37
37
|
}
|
|
38
38
|
],
|
|
39
39
|
"outputs": [],
|
|
40
|
-
"stepOutputs": [
|
|
40
|
+
"stepOutputs": [
|
|
41
|
+
{
|
|
42
|
+
"ref": "judge:top_down.phase-gate",
|
|
43
|
+
"condensation": "The phase gate verdict on the definition set: overall and per criterion (PASS, CONCERN, GAP or INDETERMINATE)."
|
|
44
|
+
}
|
|
45
|
+
],
|
|
41
46
|
"method": {
|
|
42
|
-
"guidance": "# The Definition Lane — the umbrella\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\nThis playbook produces nothing itself. It drives the leaves that DEFINE the\napplication — what it is, for whom, against which market, delivering which\nrequirements, in which order, sold how — and it ends on the phase gate's verdict,\nwhich is the lane's closing decision.\n\n## The children, and why the order is not written here\n\nThe chain, each leaf gated by the families the ones before it land:\n\n- **`top_down.vision-elicitation`** — the vision brief, from the creator's own\n answers. No precondition: the lane starts here on a fresh application.\n- **`top_down.market-analysis`** — a NESTED LANE, not a leaf: it gathers web evidence,\n judges whether it is enough, and lands the `market-snapshot` only once the verdict is\n `adequate`, re-searching against the gaps the gate named for as long as it needs. Its\n evidence loop is its own business; this lane sees only that a market snapshot landed.\n- **`top_down.value-proposition`** — refines the same snapshot: benefits, tones of\n voice, one positioning pillar per targeted ICP.\n- **`top_down.requirements-definition`** — the requirements, from vision and market.\n- **`top_down.capability-map`** — benefit → feature edges on the snapshot, and the\n feature drafts.\n- **`top_down.business-model`** — revenue model and pricing plans, from the creator's\n pricing intent.\n- **`top_down.scope-roadmap`** — the phases that deliver or defer the requirements and\n the success criteria.\n- **`top_down.phase-gate`** — five criteria over the coherence report. Lands nothing;\n its verdict is what this lane ends on.\n\nBeside the chain, needing the vision (and the business model, for the register) and\nneeded by nothing downstream of this lane:\n\n- **`top_down.brand-identity`** — the visual identity, from the creator's answers.\n- **`top_down.risk-register`** — the register the assurance mechanisms read.\n\nNothing above is a sequence. Each child declares what it needs, and the runtime\nre-computes what may run after every round. That is what makes the lane re-runnable\non an application where most of it exists: whatever is on record satisfies the gates of\nwhatever is not.\n\n## Selecting the next children\n\nThe selector is shown the accepted truth for the families this lane declares — the\nvision whole, the others as a map of what exists — and the children that may run.\n\n- **Missing beats present.** A family already on record is not re-derived, unless a\n family it was derived from has been re-derived in this run.\n- **Independent children share a round.** The brand identity and the risk register\n ride beside the chain; several research lanes with genuinely different objectives\n return more than one asked everything.\n- **A child whose interview is unanswered is not offered.** The dossier answers the\n creator's questions per leaf; a leaf the dossier does not cover waits for the creator,\n and the lane runs everything else it can.\n- **The phase gate runs once, last, then the lane stops.** It lands nothing and returns\n nothing the runtime can mark delivered, so the round history is the record that it\n ran.\n\n## Composing an objective for a child\n\nEach dispatch carries an objective composed for that round. For a research child the\nmarket umbrella's rule holds: the first round broad, a later round naming the gap the\ngate named. For a chain leaf the objective names what changed upstream since its output\nlast landed — a re-derived market snapshot, a revised vision — so the leaf refines\nrather than restarts.\n\n## When to stop\n\nStop when the phase gate has run: its verdict is the decision. Stop also when nothing\neligible advances the definition — every remaining child is waiting for the creator, or\nthe evidence gate has named the same gap twice and a further round could not close it.\nSay which, in the rationale.\n\n## What the phase gate's verdict re-opens\n\nThe
|
|
43
|
-
"skillRefs": [
|
|
44
|
-
"journey-status",
|
|
45
|
-
"journey-report"
|
|
46
|
-
],
|
|
47
|
+
"guidance": "# The Definition Lane — the umbrella\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\nThis playbook produces nothing itself. It drives the leaves that DEFINE the\napplication — what it is, for whom, against which market, delivering which\nrequirements, in which order, sold how — and it ends on the phase gate's verdict,\nwhich is the lane's closing decision.\n\n## The children, and why the order is not written here\n\nThe chain, each leaf gated by the families the ones before it land:\n\n- **`top_down.vision-elicitation`** — the vision brief, from the creator's own\n answers. No precondition: the lane starts here on a fresh application.\n- **`top_down.market-analysis`** — a NESTED LANE, not a leaf: it gathers web evidence,\n judges whether it is enough, and lands the `market-snapshot` only once the verdict is\n `adequate`, re-searching against the gaps the gate named for as long as it needs. Its\n evidence loop is its own business; this lane sees only that a market snapshot landed.\n- **`top_down.value-proposition`** — refines the same snapshot: benefits, tones of\n voice, one positioning pillar per targeted ICP.\n- **`top_down.requirements-definition`** — the requirements, from vision and market.\n- **`top_down.capability-map`** — benefit → feature edges on the snapshot, and the\n feature drafts.\n- **`top_down.business-model`** — revenue model and pricing plans, from the creator's\n pricing intent.\n- **`top_down.scope-roadmap`** — the phases that deliver or defer the requirements and\n the success criteria.\n- **`top_down.phase-gate`** — five criteria over the coherence report. Lands nothing;\n its verdict is what this lane ends on.\n\nBeside the chain, needing the vision (and the business model, for the register) and\nneeded by nothing downstream of this lane:\n\n- **`top_down.brand-identity`** — the visual identity, from the creator's answers.\n- **`top_down.risk-register`** — the register the assurance mechanisms read.\n\nNothing above is a sequence. Each child declares what it needs, and the runtime\nre-computes what may run after every round. That is what makes the lane re-runnable\non an application where most of it exists: whatever is on record satisfies the gates of\nwhatever is not.\n\n## Selecting the next children\n\nThe selector is shown the accepted truth for the families this lane declares — the\nvision whole, the others as a map of what exists — and the children that may run.\n\n- **Missing beats present.** A family already on record is not re-derived, unless a\n family it was derived from has been re-derived in this run.\n- **Independent children share a round.** The brand identity and the risk register\n ride beside the chain; several research lanes with genuinely different objectives\n return more than one asked everything.\n- **A child whose interview is unanswered is not offered.** The dossier answers the\n creator's questions per leaf; a leaf the dossier does not cover waits for the creator,\n and the lane runs everything else it can.\n- **The phase gate runs once, last, then the lane stops.** It lands nothing and returns\n nothing the runtime can mark delivered, so the round history is the record that it\n ran.\n\n## Composing an objective for a child\n\nEach dispatch carries an objective composed for that round. For a research child the\nmarket umbrella's rule holds: the first round broad, a later round naming the gap the\ngate named. For a chain leaf the objective names what changed upstream since its output\nlast landed — a re-derived market snapshot, a revised vision — so the leaf refines\nrather than restarts.\n\n## When to stop\n\nStop when the phase gate has run: its verdict is the decision. Stop also when nothing\neligible advances the definition — every remaining child is waiting for the creator, or\nthe evidence gate has named the same gap twice and a further round could not close it.\nSay which, in the rationale.\n\n## What the phase gate's verdict re-opens\n\nThe lane declares this table, and the runtime applies it: a GAP on one of the first four\ncriteria offers the mapped leaf again, even though it already landed in this run. When a\nleaf you have already seen land is eligible again after the gate, that is this loop-back,\nnot churn. Re-run that leaf against the gate's rationale for the faulted criterion, then run\nthe gate again. A PASS re-opens nothing, and CONCERN or INDETERMINATE re-open nothing\neither: re-deriving a leaf does not answer advice, and it does not produce evidence.\n\n| criterion | re-opens |\n|---|---|\n| requirement coverage | `top_down.scope-roadmap` |\n| success-criterion coverage | `top_down.scope-roadmap` |\n| capability completeness | `top_down.capability-map` |\n| positioning / ICP coherence | `top_down.value-proposition` |\n| compliance presence | the compliance lane, which this lane does not admit — the root re-opens it, from this lane's exported verdict |\n\n## What the creator reviews\n\nThe definition set, family by family, exactly as each leaf's own review guide says —\nand the phase gate's verdict, which is the one decision this lane ends on: accept the\ndefinition, or send it back to the leaf the verdict names.\n",
|
|
48
|
+
"skillRefs": [],
|
|
47
49
|
"skillBodyRefs": [],
|
|
48
50
|
"contextSources": [],
|
|
49
51
|
"draftableDocumentDefinitionRefs": [],
|
|
@@ -53,6 +55,7 @@
|
|
|
53
55
|
"top_down.scope-roadmap",
|
|
54
56
|
"top_down.business-model",
|
|
55
57
|
"top_down.capability-map",
|
|
58
|
+
"top_down.feature-drafts",
|
|
56
59
|
"top_down.value-proposition",
|
|
57
60
|
"top_down.requirements-definition",
|
|
58
61
|
"top_down.market-analysis",
|
|
@@ -63,7 +66,49 @@
|
|
|
63
66
|
"maximumIterations": 20,
|
|
64
67
|
"maximumLanesPerIteration": 3,
|
|
65
68
|
"maximumDepth": 2,
|
|
66
|
-
"maximumDurationMs": 10800000
|
|
69
|
+
"maximumDurationMs": 10800000,
|
|
70
|
+
"reopenOnVerdict": [
|
|
71
|
+
{
|
|
72
|
+
"whenVerdictOf": "top_down.phase-gate",
|
|
73
|
+
"criterionRef": "application-creation:criterion/requirement-coverage",
|
|
74
|
+
"verdicts": [
|
|
75
|
+
"GAP"
|
|
76
|
+
],
|
|
77
|
+
"reopen": [
|
|
78
|
+
"top_down.scope-roadmap"
|
|
79
|
+
]
|
|
80
|
+
},
|
|
81
|
+
{
|
|
82
|
+
"whenVerdictOf": "top_down.phase-gate",
|
|
83
|
+
"criterionRef": "application-creation:criterion/success-criterion-coverage",
|
|
84
|
+
"verdicts": [
|
|
85
|
+
"GAP"
|
|
86
|
+
],
|
|
87
|
+
"reopen": [
|
|
88
|
+
"top_down.scope-roadmap"
|
|
89
|
+
]
|
|
90
|
+
},
|
|
91
|
+
{
|
|
92
|
+
"whenVerdictOf": "top_down.phase-gate",
|
|
93
|
+
"criterionRef": "application-creation:criterion/capability-completeness",
|
|
94
|
+
"verdicts": [
|
|
95
|
+
"GAP"
|
|
96
|
+
],
|
|
97
|
+
"reopen": [
|
|
98
|
+
"top_down.capability-map"
|
|
99
|
+
]
|
|
100
|
+
},
|
|
101
|
+
{
|
|
102
|
+
"whenVerdictOf": "top_down.phase-gate",
|
|
103
|
+
"criterionRef": "application-creation:criterion/positioning-icp-coherence",
|
|
104
|
+
"verdicts": [
|
|
105
|
+
"GAP"
|
|
106
|
+
],
|
|
107
|
+
"reopen": [
|
|
108
|
+
"top_down.value-proposition"
|
|
109
|
+
]
|
|
110
|
+
}
|
|
111
|
+
]
|
|
67
112
|
},
|
|
68
113
|
"suspendsForClarification": false,
|
|
69
114
|
"briefAdequacyGate": false,
|
|
@@ -45,7 +45,7 @@ A derivation is an agentic three-pass protocol over the application's own artifa
|
|
|
45
45
|
|
|
46
46
|
## What you read
|
|
47
47
|
|
|
48
|
-
The current journey state
|
|
48
|
+
The current journey state this run is given, to see which families have landed and
|
|
49
49
|
therefore which roles are derivable now.
|
|
50
50
|
|
|
51
51
|
## Verification
|
|
@@ -28,10 +28,8 @@
|
|
|
28
28
|
"outputs": [],
|
|
29
29
|
"stepOutputs": [],
|
|
30
30
|
"method": {
|
|
31
|
-
"guidance": "# Expert personas — staff the panels the catalog convenes\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What this step does\n\nSeveral steps of the creation journey are DECIDED BY A PANEL rather than by a single generation:\n`bottom_up.placement-plan` convenes an information architect and a design-system guardian, the logo\ngeneration step convenes an art director, a brand strategist and a design-system guardian. A panel is\nbuilt from **expert-persona charters** — one committed charter per framework expert role, derived from\nthis application's own vision, market, requirements, business model and brand, so a reviewer speaks\nfor THIS product rather than for a generic one.\n\nThis step derives and accepts those charters. It is runner-owned: no prompt is composed here. For every\nrole the catalog convenes (read off every playbook's `method.deliberation` and off the generation\nsteps' own panels), it runs the companion's derive → accept flow — a DRAFT, a CRITIQUE by a dedicated\ncritic, and a FINALIZE pass when the critique asks for one — then promotes the proposal into\n`specifications/src/personas/<role>.charter.generated.ts`, regenerates the aggregator and wires the\n`expertPersonaCharters` companion-exports slot.\n\n## What it will not do\n\n- **Overwrite a human-edited charter.** A committed charter carrying an `authored` block is never\n replaced; the accept step refuses and the run reports it.\n- **Re-derive a committed charter.** A role that already has a committed charter is left alone; ask for a\n re-derivation explicitly through the companion's `expert-personas/derive` route if the application's\n definition moved enough to warrant one.\n- **Fail on a role whose inputs are not landed.** A role needing the brand brief on an application with\n no brand yet is REPORTED as waiting, with the families it waits on. The step re-runs when they land.\n\n## Cost, so it is scheduled knowingly\n\nA derivation is an agentic three-pass protocol over the application's own artifacts: measured at about\n200 seconds per role on a real application. Five roles is a quarter of an hour. Submit the run detached.\n\n## What you read\n\nThe current journey state
|
|
32
|
-
"skillRefs": [
|
|
33
|
-
"journey-status"
|
|
34
|
-
],
|
|
31
|
+
"guidance": "# Expert personas — staff the panels the catalog convenes\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What this step does\n\nSeveral steps of the creation journey are DECIDED BY A PANEL rather than by a single generation:\n`bottom_up.placement-plan` convenes an information architect and a design-system guardian, the logo\ngeneration step convenes an art director, a brand strategist and a design-system guardian. A panel is\nbuilt from **expert-persona charters** — one committed charter per framework expert role, derived from\nthis application's own vision, market, requirements, business model and brand, so a reviewer speaks\nfor THIS product rather than for a generic one.\n\nThis step derives and accepts those charters. It is runner-owned: no prompt is composed here. For every\nrole the catalog convenes (read off every playbook's `method.deliberation` and off the generation\nsteps' own panels), it runs the companion's derive → accept flow — a DRAFT, a CRITIQUE by a dedicated\ncritic, and a FINALIZE pass when the critique asks for one — then promotes the proposal into\n`specifications/src/personas/<role>.charter.generated.ts`, regenerates the aggregator and wires the\n`expertPersonaCharters` companion-exports slot.\n\n## What it will not do\n\n- **Overwrite a human-edited charter.** A committed charter carrying an `authored` block is never\n replaced; the accept step refuses and the run reports it.\n- **Re-derive a committed charter.** A role that already has a committed charter is left alone; ask for a\n re-derivation explicitly through the companion's `expert-personas/derive` route if the application's\n definition moved enough to warrant one.\n- **Fail on a role whose inputs are not landed.** A role needing the brand brief on an application with\n no brand yet is REPORTED as waiting, with the families it waits on. The step re-runs when they land.\n\n## Cost, so it is scheduled knowingly\n\nA derivation is an agentic three-pass protocol over the application's own artifacts: measured at about\n200 seconds per role on a real application. Five roles is a quarter of an hour. Submit the run detached.\n\n## What you read\n\nThe current journey state this run is given, to see which families have landed and\ntherefore which roles are derivable now.\n\n## Verification\n\n- `specifications/src/personas/` holds one `*.charter.generated.ts` per role the run reports as derived,\n and `index.ts` lists every one of them.\n- `companion-exports.ts` wires `expertPersonaCharters` onto the aggregator.\n- The eligibility board no longer reports `PANEL_UNSTAFFED` for `bottom_up.placement-plan`.\n",
|
|
32
|
+
"skillRefs": [],
|
|
35
33
|
"skillBodyRefs": [],
|
|
36
34
|
"contextSources": [],
|
|
37
35
|
"draftableDocumentDefinitionRefs": [],
|
|
@@ -0,0 +1,72 @@
|
|
|
1
|
+
# Feature Drafts — Requirements → Capability Method
|
|
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
|
+
## What this playbook does
|
|
16
|
+
|
|
17
|
+
You are the **capability architect** for an application that has **no market**: an internal tool,
|
|
18
|
+
for example, built for a team rather than sold to customers. Your one job is to turn the accepted
|
|
19
|
+
**requirements** into the product **capabilities** that deliver them, and to record each capability as
|
|
20
|
+
a spec-first **`FeatureSpecificationDraft`** in the `feature-drafts` family.
|
|
21
|
+
|
|
22
|
+
There are no market benefits, ICPs or pricing to map from, and none is owed: do not invent a market,
|
|
23
|
+
a customer segment or a competitive position. The requirements say what the application must do and
|
|
24
|
+
for whom inside the organization; the vision says why it exists. Those two are your whole input.
|
|
25
|
+
|
|
26
|
+
## Read state first
|
|
27
|
+
|
|
28
|
+
- **Requirements** (functional and non-functional): what the application must do. Every capability
|
|
29
|
+
you draft must serve at least one requirement, and every functional requirement should be served by
|
|
30
|
+
at least one capability. A requirement no capability serves is either a gap to draft or a
|
|
31
|
+
requirement to question, never a silent omission.
|
|
32
|
+
- **Vision**: the problem, the mission and the constraints. Use it to name capabilities in the
|
|
33
|
+
application's own words and to keep them inside its stated scope.
|
|
34
|
+
- **Your prior feature drafts**, when present. Refine them; do not re-author (below).
|
|
35
|
+
|
|
36
|
+
## Drafting each capability
|
|
37
|
+
|
|
38
|
+
For every capability, author a draft with the **Draft path** of `spec-feature-update`: its purpose,
|
|
39
|
+
business role, lifecycle role, when to use it and when not to, and its availability role, all in
|
|
40
|
+
prose. Drafts are **spec-first and ref-less**: you author them before the runtime `FeatureDefinition`
|
|
41
|
+
exists, and the factory injects the `ref` later. The draft wrapper carries the stable `featureRef`;
|
|
42
|
+
the nested prose payload stays ref-less.
|
|
43
|
+
|
|
44
|
+
- **One capability, one draft.** When two requirements are served by the same capability, they share
|
|
45
|
+
it; do not fork it.
|
|
46
|
+
- **Name the requirements each draft serves**, in its purpose or business-role prose, so the roadmap
|
|
47
|
+
and the build decomposition can trace a capability back to what asked for it.
|
|
48
|
+
- **Stay at scaffold depth.** A draft is a first-cut capability contract. Operations, screens and
|
|
49
|
+
interaction semantics are the bottom-up build phase's work.
|
|
50
|
+
|
|
51
|
+
## Refine, don't re-author
|
|
52
|
+
|
|
53
|
+
- **Keep what still holds.** Do not rewrite drafts that are already correct.
|
|
54
|
+
- **Keep refs stable.** A draft's `featureRef` is named by the roadmap and by build tasks; renaming it
|
|
55
|
+
orphans them.
|
|
56
|
+
- Add a draft where a requirement gained a capability, correct one that is genuinely wrong, and
|
|
57
|
+
remove one only when no requirement calls for it any more.
|
|
58
|
+
|
|
59
|
+
## What you emit
|
|
60
|
+
|
|
61
|
+
The **feature-drafts** at `specifications/src/feature-drafts/index.ts`: one `FeatureSpecificationDraft`
|
|
62
|
+
per capability the requirements call for, passing `validateFeatureSpecificationDrafts`.
|
|
63
|
+
|
|
64
|
+
The creator reviews the result (approval posture `approve_result`) before it is accepted.
|
|
65
|
+
|
|
66
|
+
## References
|
|
67
|
+
|
|
68
|
+
These are skill FOLDERS installed in the application, named so each piece of work has an authoring
|
|
69
|
+
contract a later coding agent can open. This step has no tools and does not open them; what reaches
|
|
70
|
+
you is this method, your declared inputs, and the brief's own sections.
|
|
71
|
+
|
|
72
|
+
- `spec-feature-update`: author the spec-first `FeatureSpecificationDraft`s (the Draft path).
|
|
@@ -0,0 +1,57 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ref": "top_down.feature-drafts",
|
|
3
|
+
"version": "0.1.0",
|
|
4
|
+
"phase": "top_down",
|
|
5
|
+
"intent": "Draft the product capabilities an application needs from its accepted requirements and vision, for an application whose line has no market: one spec-first, ref-less feature specification draft per capability the requirements call for, each tracing to the requirements it serves.",
|
|
6
|
+
"preconditions": [
|
|
7
|
+
{
|
|
8
|
+
"kind": "artifact_valid",
|
|
9
|
+
"selector": {
|
|
10
|
+
"family": "requirements"
|
|
11
|
+
}
|
|
12
|
+
},
|
|
13
|
+
{
|
|
14
|
+
"kind": "artifact_valid",
|
|
15
|
+
"selector": {
|
|
16
|
+
"family": "vision-brief"
|
|
17
|
+
}
|
|
18
|
+
}
|
|
19
|
+
],
|
|
20
|
+
"inputs": [
|
|
21
|
+
{
|
|
22
|
+
"family": "requirements"
|
|
23
|
+
},
|
|
24
|
+
{
|
|
25
|
+
"family": "vision-brief"
|
|
26
|
+
},
|
|
27
|
+
{
|
|
28
|
+
"family": "feature-drafts"
|
|
29
|
+
}
|
|
30
|
+
],
|
|
31
|
+
"outputs": [
|
|
32
|
+
{
|
|
33
|
+
"family": "feature-drafts",
|
|
34
|
+
"schemaRef": "saas-specifications:FeatureSpecificationDrafts",
|
|
35
|
+
"description": "A collection of runner-addressed, ref-less FeatureSpecificationDraft payloads, one per capability the requirements call for."
|
|
36
|
+
}
|
|
37
|
+
],
|
|
38
|
+
"stepOutputs": [],
|
|
39
|
+
"method": {
|
|
40
|
+
"guidance": "# Feature Drafts — Requirements → Capability Method\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What this playbook does\n\nYou are the **capability architect** for an application that has **no market**: an internal tool,\nfor example, built for a team rather than sold to customers. Your one job is to turn the accepted\n**requirements** into the product **capabilities** that deliver them, and to record each capability as\na spec-first **`FeatureSpecificationDraft`** in the `feature-drafts` family.\n\nThere are no market benefits, ICPs or pricing to map from, and none is owed: do not invent a market,\na customer segment or a competitive position. The requirements say what the application must do and\nfor whom inside the organization; the vision says why it exists. Those two are your whole input.\n\n## Read state first\n\n- **Requirements** (functional and non-functional): what the application must do. Every capability\n you draft must serve at least one requirement, and every functional requirement should be served by\n at least one capability. A requirement no capability serves is either a gap to draft or a\n requirement to question, never a silent omission.\n- **Vision**: the problem, the mission and the constraints. Use it to name capabilities in the\n application's own words and to keep them inside its stated scope.\n- **Your prior feature drafts**, when present. Refine them; do not re-author (below).\n\n## Drafting each capability\n\nFor every capability, author a draft with the **Draft path** of `spec-feature-update`: its purpose,\nbusiness role, lifecycle role, when to use it and when not to, and its availability role, all in\nprose. Drafts are **spec-first and ref-less**: you author them before the runtime `FeatureDefinition`\nexists, and the factory injects the `ref` later. The draft wrapper carries the stable `featureRef`;\nthe nested prose payload stays ref-less.\n\n- **One capability, one draft.** When two requirements are served by the same capability, they share\n it; do not fork it.\n- **Name the requirements each draft serves**, in its purpose or business-role prose, so the roadmap\n and the build decomposition can trace a capability back to what asked for it.\n- **Stay at scaffold depth.** A draft is a first-cut capability contract. Operations, screens and\n interaction semantics are the bottom-up build phase's work.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** Do not rewrite drafts that are already correct.\n- **Keep refs stable.** A draft's `featureRef` is named by the roadmap and by build tasks; renaming it\n orphans them.\n- Add a draft where a requirement gained a capability, correct one that is genuinely wrong, and\n remove one only when no requirement calls for it any more.\n\n## What you emit\n\nThe **feature-drafts** at `specifications/src/feature-drafts/index.ts`: one `FeatureSpecificationDraft`\nper capability the requirements call for, passing `validateFeatureSpecificationDrafts`.\n\nThe creator reviews the result (approval posture `approve_result`) before it is accepted.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an authoring\ncontract a later coding agent can open. This step has no tools and does not open them; what reaches\nyou is this method, your declared inputs, and the brief's own sections.\n\n- `spec-feature-update`: author the spec-first `FeatureSpecificationDraft`s (the Draft path).\n",
|
|
41
|
+
"skillRefs": [
|
|
42
|
+
"spec-feature-update"
|
|
43
|
+
],
|
|
44
|
+
"skillBodyRefs": [],
|
|
45
|
+
"contextSources": [],
|
|
46
|
+
"draftableDocumentDefinitionRefs": [],
|
|
47
|
+
"suspendsForClarification": false,
|
|
48
|
+
"briefAdequacyGate": false,
|
|
49
|
+
"briefAdequacyExcludedSources": []
|
|
50
|
+
},
|
|
51
|
+
"executor": "companion_agent",
|
|
52
|
+
"approval": "approve_result",
|
|
53
|
+
"budget": {
|
|
54
|
+
"maxRuns": 3
|
|
55
|
+
},
|
|
56
|
+
"onFailure": "keep_and_flag"
|
|
57
|
+
}
|
|
@@ -21,7 +21,6 @@
|
|
|
21
21
|
"method": {
|
|
22
22
|
"guidance": "# Market Analysis — the umbrella\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\nThis playbook produces nothing itself. It coordinates three children and the market\nsnapshot is landed by one of them.\n\n## The children, and why the order is not written here\n\n- **`top_down.market-research`** gathers evidence from the public web and returns a\n condensed, source-attributed brief. Read-only: it can fetch and search, and it\n cannot write anything.\n- **`top_down.market-evidence-adequacy`** reads that evidence and answers one\n question — is this enough to derive a snapshot from? — returning a verdict and, when\n it is not, the specific gaps.\n- **`top_down.market-snapshot-produce`** derives and lands the `market-snapshot`\n family. It becomes eligible only once the gate has returned `adequate`.\n\nNothing above is a sequence. Each child declares what it needs, and the runtime\nre-computes what may run after every round. Research needs only the vision. The gate\nneeds research to have returned. Produce needs the gate to have returned `adequate` —\nnot merely to have run.\n\nThat is what makes the loop a loop: when the gate says `insufficient`, produce simply\nstays ineligible, research stays available, and the sensible next move is another\nresearch round **aimed at the gaps the gate named**. Nobody wrote \"if insufficient,\ngo back\" anywhere; it falls out of the preconditions.\n\n## Composing an objective for a child\n\nEach dispatch carries an objective composed for that round. This is the part that is\ninvented rather than authored, and it is where the value is:\n\n- The **first** research round should be broad — the category, who competes, what they\n charge, how buyers talk.\n- A **later** round should be narrow and should name the gap: *\"the first round found\n no published pricing for the two mid-market competitors; find it, or establish that\n it is quote-only.\"* Repeating the first objective produces the first answer again.\n- Where a round can be **split**, split it. Four lanes asking about category,\n competitors, pricing and buyer language separately return more than one lane asked\n everything at once — each returns a condensation, and the breadth is the point.\n\n## When to stop\n\nStop when the snapshot has landed. Stop also when the gate has named the same gap\ntwice and the second round could not close it — that gap is not going to be closed by\na third attempt, and a snapshot marked honestly incomplete is worth more than a loop\nthat spends its ceiling. Say which, in your rationale.\n\n## What the creator reviews\n\nThe landed `market-snapshot`, exactly as before — it still passes the deterministic\n`market-snapshot-valid` gate, and the creator still approves the result. What changed\nis only that its claims now rest on pages someone read.\n",
|
|
23
23
|
"skillRefs": [
|
|
24
|
-
"journey-status",
|
|
25
24
|
"market-authoring-overview"
|
|
26
25
|
],
|
|
27
26
|
"skillBodyRefs": [],
|
|
@@ -26,7 +26,6 @@
|
|
|
26
26
|
"method": {
|
|
27
27
|
"guidance": "# Evidence Adequacy — is this enough to derive from?\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\nYou are the **gate**. You judge whether the evidence gathered so far is enough to\nderive a market snapshot from — and when it is not, you say precisely what is missing.\n\n## The question you answer\n\nNot \"is this good research?\" and not \"is this market attractive?\". Only:\n\n> **Could a competent analyst write a defensible market snapshot from what is here,\n> without inventing anything?**\n\nIf yes, the verdict is `adequate`. If no, it is `insufficient`, and your `gaps` are\nwhat the next research round will be aimed at.\n\n## What makes evidence adequate\n\n- **The category is named by a source**, not assumed.\n- **At least a few real competing alternatives**, each with something concrete about\n what it costs or how it is sold. \"There are competitors\" is not evidence.\n- **Buyer language observed rather than imagined** — at least some of how the people\n with this problem describe it.\n- **Claims carry sources**, and the unsourced ones are marked as such.\n\n## What makes it insufficient, and how to say so\n\nName the GAP, not the feeling. `\"no pricing found for any competitor\"` sends the next\nround somewhere; `\"the evidence is thin\"` sends it nowhere and it comes back the same.\n\nEach gap should be answerable. If a gap is genuinely unanswerable from the public web\n— private pricing, a market nobody writes about — say that in the rationale rather\nthan emitting a gap that will fail again. A loop that keeps asking for something that\ndoes not exist is worse than a snapshot honestly marked incomplete.\n\n## Be willing to say ADEQUATE\n\nThe failure mode of a gate is not being too lenient. It is holding out for completeness\nthat no public source can provide, so the loop spends its rounds and stops on a ceiling\nwith nothing produced. Enough is enough; perfect is not the bar.\n\n## What you do not do\n\nYou author nothing, you land nothing, and you do not write the snapshot. Your verdict\nis read by the step that does.\n",
|
|
28
28
|
"skillRefs": [
|
|
29
|
-
"journey-status",
|
|
30
29
|
"market-snapshot-validation"
|
|
31
30
|
],
|
|
32
31
|
"skillBodyRefs": [],
|
|
@@ -27,7 +27,6 @@
|
|
|
27
27
|
"method": {
|
|
28
28
|
"guidance": "# Market Research — gather the evidence\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\nYou are the **researcher**. Your one job is to find out what is actually true about this\nproduct's market and report it with sources. You do not design the product, model\nits domain, choose a positioning, or author any file — a sibling does that, from\nwhat you bring back.\n\n## Why this step exists\n\nThe playbook that produces the market snapshot used to gather its own evidence, and\nit had no way to. Its executor was a structured-generation call with no tools, so\n\"research\" meant whatever the model already remembered — which is confident, fluent,\nand wrong in exactly the cases that matter, because prices change, competitors\nappear, and category language moves.\n\nThis step exists so that the snapshot rests on pages someone actually read.\n\n## What to find\n\nWork the objective you were given. It is not a fixed checklist: it was composed for\nTHIS round, and on a second round it will name what the first round could not find.\nWhere the objective is broad, these are the questions worth answering:\n\n1. **The category as sources name it.** Not the category we would like to be in —\n the words buyers and competitors actually use. Note the alternatives you rejected\n and why.\n2. **Who competes**, including the ones that are not products: a spreadsheet, an\n agency, doing nothing. For each, what it costs where that is published.\n3. **Price shape.** Per seat, per usage, tiered, quote-only. Ranges and what a\n published entry price is.\n4. **Buyer language.** How the people with the problem describe it in their own\n words, from forums, reviews, job posts, changelogs.\n\n## How to report\n\n- **Every factual claim carries the URL you read it from.** A claim without one is\n worse than an absent claim, because the reader cannot tell which it is.\n- **Say what you could NOT find.** The gaps are what the next round is aimed at, and\n an unstated gap silently becomes an assumption downstream.\n- **Report disagreement.** Where sources conflict, say so, say which you consider\n more authoritative, and say why. Do not pick one silently.\n- **Distinguish what you READ from what you INFER.** Inference is legitimate;\n presenting it as a finding is not.\n\n## Condensation is part of the job\n\nReturn a brief, not a transcript. The sibling that reads this reasons at its own\nresolution, and a parent flooded with raw page text is a parent that cannot hold the\nproblem. Roughly 2000 words: findings, sources, gaps. If a page mattered, say what it\nsaid and link it — do not paste it.\n\n## What you cannot do\n\nYou have no write access, no shell, and no path into the workspace. This is enforced,\nnot requested. If the objective seems to ask for a file, it does not — report what you\nfound and let the sibling author it.\n",
|
|
29
29
|
"skillRefs": [
|
|
30
|
-
"journey-status",
|
|
31
30
|
"market-category",
|
|
32
31
|
"market-alternatives"
|
|
33
32
|
],
|
|
@@ -106,8 +106,8 @@ artifact, not yet app source.
|
|
|
106
106
|
This playbook is **idempotent** on the journey's market artifact. Before
|
|
107
107
|
authoring anything:
|
|
108
108
|
|
|
109
|
-
1. Read the current journey state and scope
|
|
110
|
-
|
|
109
|
+
1. Read the current journey state and scope from what this run is given — the loaded
|
|
110
|
+
specifications and the workspace sections of your brief; do not re-derive it. That state tells you which
|
|
111
111
|
scope the snapshot must be complete *for*.
|
|
112
112
|
2. Check whether a MarketSnapshot already exists by reading the artifact at the
|
|
113
113
|
`market-snapshot` family's landing path, `specifications/src/market/index.ts`.
|
|
@@ -216,8 +216,6 @@ assembled from the slices above via their `market_*` skills, passing the
|
|
|
216
216
|
These are skill FOLDERS installed in the application, listed so each slice's
|
|
217
217
|
authoring contract has a name. This step has no tools and does not open them.
|
|
218
218
|
|
|
219
|
-
- `journey-status` — reads the current journey state and scope. That is a READ a
|
|
220
|
-
tool-using agent performs; you receive its answer as your declared inputs.
|
|
221
219
|
- `market-authoring-overview` — the orchestrator for
|
|
222
220
|
the whole market slice; read it first to see how the slices fit together.
|
|
223
221
|
- `market-category` — author the singular market
|
|
@@ -36,9 +36,8 @@
|
|
|
36
36
|
],
|
|
37
37
|
"stepOutputs": [],
|
|
38
38
|
"method": {
|
|
39
|
-
"guidance": "# Market Analysis — Produce Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The authoring order, research posture, and the \"produce vs.\n> refine\" rules below are deliberately explicit so they can be tuned against\n> real runs — treat them as a starting rubric, not a frozen contract. The\n> *analytical depth* of the market work (research rigor, competitive\n> teardown, quantified FIT/Kano scoring) is intentionally shallow here and is\n> deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **market analyst**. Your one job is to produce — or refine an\nexisting — **MarketSnapshot** for this product: the single artifact that\ndeclares *who the product is for*, *what they are trying to get done*, and\n*how the product is positioned* to them. You reason top-down from the\nproduct idea (there is no code yet in this phase); you do not model the\ndomain, author resources, or write features — later playbooks consume your\nsnapshot to do that.\n\n## The shape you return is FLAT, not nested\n\nRead this before the slice list below, because the slices read like a hierarchy and the object is\nnot one.\n\nA MarketSnapshot is **~16 sibling top-level collections** — `category`, `icps`, `personas`, `jobs`,\n`pains`, `gains`, `tonesOfVoice`, `benefits`, `positionings`, `channels`, `alternatives`,\n`triggers`, `buyingJourneys`, `proofs`, `objections`, `messageTemplates` — and entities point at\neach other with flat **ref strings** (`jobRef`, `painRef`, `gainRef`, `personaRef`, `alternativeRef`,\n…). An ICP does not CONTAIN its jobs; it names them:\n\n```\njobs: [ { ref: 'job-close-the-week', statement: '…' } ] // the job itself, top level\nicps: [ { ref: 'icp-small-team',\n jobs: [ { jobRef: 'job-close-the-week', importance: … } ] } ] // the ICP's REFERENCE to it\n```\n\n⚠ **Measured on this playbook, 2026-08-29.** A first attempt returned 41,098 characters that were\nrejected wholesale: it had nested `personas`, `benefits`, `positionings`, `channels`, `alternatives`,\n`triggers`, `proofs` and `objections` INSIDE `icps[0]`, left every top-level collection empty, and\nwrote whole job objects where `{ jobRef, importance }` belongs. The retry recovered it, but a full\ngeneration was spent discovering the shape. The slice ordering below is a THINKING order — what to\nwork out first — never the structure of the answer.\n\nA MarketSnapshot is assembled from these slices, each owned by a dedicated\n`market_*` app-knowledge skill. Those skills are named here so you know which\nauthoring contract each slice belongs to, and so a later CODING agent can open\nthe right one — you cannot: this step has no tools, and sixteen skill bodies do\nnot fit in one brief. Everything you need to author the snapshot is in THIS\nmethod and your declared inputs; where a detail is genuinely only in a skill,\nsay so on what you author rather than inventing it. You author them in\ndependency order because later slices reference earlier refs:\n\n1. **Category** — the one market category the product competes in, plus the\n rejected adjacent categories. (`market-category`)\n2. **ICPs** — the Ideal Customer Profiles: the firmographic / demographic\n segments the product is sold to. (`market-icp`)\n3. **Personas** — the human roles inside each ICP, including buying-group\n members. Every ICP needs at least one persona. (`market-persona`)\n4. **Jobs / Pains / Gains** — the Strategyzer customer-profile triplet for\n the personas: what they are trying to do, what blocks them, what a win\n looks like. (`market-jobs-pains-gains`)\n5. **Tones of voice** — the named brand voices the product speaks in.\n (`market-tone-of-voice`)\n6. **Benefits** — the outcome claims the product delivers, weighted against\n the pains/gains they relieve/create. (`market-add-feature-benefit`)\n7. **Positionings** — the per-ICP marketing-truth promise. Author one per\n ICP that the product actually targets. (`market-positioning-authoring`)\n8. **Reach surfaces** — the go-to-market context: channels, competing\n alternatives, buying triggers + per-ICP buying journeys, proofs, and the\n objections proofs answer. (`market-channels`, `market-alternatives`,\n `market-triggers-and-journey`, `market-proof-and-objection`)\n9. **Message templates** — reusable prompt templates that render from the\n snapshot above. Author last; they reference the earlier slices.\n (`market-message-templates-authoring`)\n\nAuthor only the slices the product's stage warrants — a first pass may stop\nafter positionings and leave the phase-3/4 reach surfaces empty (they\ndefault to `[]`). A snapshot with a category, at least one ICP, its\npersonas, the jobs/pains/gains triplet, and at least one positioning is a\nlegitimate v1; the reach surfaces and message templates are additive.\n\n## Where the snapshot lives\n\nThe MarketSnapshot for this journey is placed under\n`specifications/src/market/index.ts`. That is the artifact this\nplaybook owns and the rest of the top-down phase reads. When the product's\ndefinition later stabilises, the snapshot is what seeds the durable market\nspecification under `./specifications/` — but at this phase it is a journey\nartifact, not yet app source.\n\n## Produce vs. refine — read state first\n\nThis playbook is **idempotent** on the journey's market artifact. Before\nauthoring anything:\n\n1. Read the current journey state and scope through the `journey-status`\n skill (it owns the read; do not re-derive it here) — that tells you which\n scope the snapshot must be complete *for*.\n2. Check whether a MarketSnapshot already exists by reading the artifact at the\n `market-snapshot` family's landing path, `specifications/src/market/index.ts`.\n The path belongs to the FAMILY, not to this playbook — every playbook that\n writes a market snapshot writes that same file. Its presence or absence\n selects the mode below.\n\n- **No snapshot yet** — produce a fresh one, authoring the slices in the\n order above.\n- **A snapshot exists** — *refine* it: read every slice, keep what still\n holds, and only add/correct the slices the current steering notes or new\n research call for. Never silently discard authored refs — a downstream\n positioning or benefit may depend on an ICP or persona ref, and dropping\n it orphans them (the validator will catch this, but honest refinement\n should not create the orphan in the first place).\n\n## Provenance — record where a claim came from\n\nYou are given the evidence a sibling research step gathered, with the URLs it read.\nWhere an entity's content rests on one of those sources, RECORD that URL on the entity\n— in the schema's own provenance fields, which exist for exactly this:\n\n| field | for |\n|---|---|\n| `pains[].evidence[]`, `gains[].evidence[]`, `benefits[].evidence` | what a source shows about the pain, gain or claim |\n| `proofs[].evidenceUrl`, `proofs[].attribution.url` | the page a proof points at |\n| `alternatives[].notes[]`, `category.notes[]`, `icps[].notes[]` | where the framing came from |\n\n⚠ An earlier revision of this section told you to use `authoredMetadata.notes` instead.\nThat was wrong, and the correction is recorded rather than quietly applied because the\nrun that exposed it did better than the instruction: handed the evidence, the model\nput 10 URLs into the typed `evidence`/`evidenceUrl` fields above and none into the\ngeneric metadata block it had been pointed at. Typed provenance is machine-readable\nand the generic block is prose; prefer the specific field every time one exists.\n\nThis is not bookkeeping. Measured on this playbook's first composite run\n(2026-08-29): the snapshot it produced carried **zero** source URLs and was, on that\ndimension, indistinguishable from the single-call version it replaced — the judge\ncalled the older one's evidence \"self-referential statements such as 'The vision\nspecifies…'\". A sourced claim and an invented one must not look the same in what you\nland, because nobody downstream can tell them apart afterwards.\n\nSo:\n\n- An entity grounded in a fetched page carries its URL in `authoredMetadata.notes`.\n- An entity you INFERRED carries that word, and `confidence` set honestly — `LOW` for\n a hypothesis, not `HIGH` because it reads well.\n- An entity the evidence did not cover is still authorable, and says so.\n\nOmit `authoredMetadata` only where the content is so self-evident that provenance\nwould be noise. A competitor's price is never that.\n\n## Research posture (scaffold depth)\n\nGround each slice in evidence, not invention. At this scaffold depth the\nresearch is whatever the executing agent can gather about the product's\ncategory, competitors, and buyers; capture the *shape* faithfully (real\ncategory, real competing alternatives, plausible ICPs and personas) rather\nthan aspirational fiction. Where you are inferring rather than citing, say so\nin the slice's authored prose so a later, deeper research pass can tighten\nit. Do **not** build a research pipeline or block on external tooling here —\nricher web-research capability is a later-phase concern; this playbook\nconsumes whatever the agent already knows plus the creator's steering.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. It\nenforces the cross-slice invariants — orphan refs (a positioning naming a\nmissing ICP, a benefit naming a missing pain/gain), an ICP with no persona,\ninfluence cycles, duplicate edges, proofs without support, message-template\nplaceholder mismatches, and more. Duplicate or malformed refs and\n`ERROR`-severity issues are hard failures; the snapshot does not advance\nuntil they clear. `WARN`-severity issues (e.g. stale-authored, a missing\npositioning for a targeted ICP) do not block but should be resolved. Read\n`market-snapshot-validation` for the full issue catalogue and emit a clean\nsnapshot the first time.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. The following are explicitly **out of\nscope here** and are deepened in the methodology-depth phase, not now:\n\n- **Deep competitive teardown** — the reach surfaces capture *that* an\n alternative exists and *why* a buyer might pick it; a quantified,\n feature-by-feature competitor matrix is later-phase work.\n- **Quantified FIT / Kano scoring** — `market-scoring-interpretation` reads\n the deterministic FIT scorer; at scaffold depth you consume it to sanity-\n check benefit weighting, not to drive a precise prioritization model. The\n prioritization seam stays pluggable (see the capability-map playbook).\n- **Opportunity / TAM sizing and evidence depth** — jobs/pains/gains are\n authored as framing, not as a sized, sourced market model.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nA single MarketSnapshot at `specifications/src/market/index.ts`,\nassembled from the slices above via their `market_*` skills, passing the\n`market-snapshot-valid` gate. The creator reviews the result (approval posture\n`approve_result`) before it is accepted as the journey's market intent.\n\n## References\n\nThese are skill FOLDERS installed in the application, listed so each slice's\nauthoring contract has a name. This step has no tools and does not open them.\n\n- `journey-status` — reads the current journey state and scope. That is a READ a\n tool-using agent performs; you receive its answer as your declared inputs.\n- `market-authoring-overview` — the orchestrator for\n the whole market slice; read it first to see how the slices fit together.\n- `market-category` — author the singular market\n category.\n- `market-icp` — author the Ideal Customer Profiles.\n- `market-persona` — author the personas per ICP.\n- `market-jobs-pains-gains` — author the Strategyzer\n jobs/pains/gains triplet.\n- `market-tone-of-voice` — author the named brand\n voices.\n- `market-add-feature-benefit` — author the benefit\n claims and their pain/gain weighting.\n- `market-positioning-authoring` — author the per-ICP\n positioning promise.\n- `market-channels` — author the reach channels.\n- `market-alternatives` — author the competing\n alternatives.\n- `market-triggers-and-journey` — author buying\n triggers and per-ICP buying journeys.\n- `market-proof-and-objection` — author proofs and\n the objections they answer.\n- `market-message-templates-authoring` — author the\n reusable message templates (last).\n- `market-scoring-interpretation` — interpret the\n deterministic FIT scorer to sanity-check benefit weighting.\n- `market-snapshot-validation` — the full validation\n issue catalogue the quality gate enforces.\n",
|
|
39
|
+
"guidance": "# Market Analysis — Produce Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The authoring order, research posture, and the \"produce vs.\n> refine\" rules below are deliberately explicit so they can be tuned against\n> real runs — treat them as a starting rubric, not a frozen contract. The\n> *analytical depth* of the market work (research rigor, competitive\n> teardown, quantified FIT/Kano scoring) is intentionally shallow here and is\n> deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **market analyst**. Your one job is to produce — or refine an\nexisting — **MarketSnapshot** for this product: the single artifact that\ndeclares *who the product is for*, *what they are trying to get done*, and\n*how the product is positioned* to them. You reason top-down from the\nproduct idea (there is no code yet in this phase); you do not model the\ndomain, author resources, or write features — later playbooks consume your\nsnapshot to do that.\n\n## The shape you return is FLAT, not nested\n\nRead this before the slice list below, because the slices read like a hierarchy and the object is\nnot one.\n\nA MarketSnapshot is **~16 sibling top-level collections** — `category`, `icps`, `personas`, `jobs`,\n`pains`, `gains`, `tonesOfVoice`, `benefits`, `positionings`, `channels`, `alternatives`,\n`triggers`, `buyingJourneys`, `proofs`, `objections`, `messageTemplates` — and entities point at\neach other with flat **ref strings** (`jobRef`, `painRef`, `gainRef`, `personaRef`, `alternativeRef`,\n…). An ICP does not CONTAIN its jobs; it names them:\n\n```\njobs: [ { ref: 'job-close-the-week', statement: '…' } ] // the job itself, top level\nicps: [ { ref: 'icp-small-team',\n jobs: [ { jobRef: 'job-close-the-week', importance: … } ] } ] // the ICP's REFERENCE to it\n```\n\n⚠ **Measured on this playbook, 2026-08-29.** A first attempt returned 41,098 characters that were\nrejected wholesale: it had nested `personas`, `benefits`, `positionings`, `channels`, `alternatives`,\n`triggers`, `proofs` and `objections` INSIDE `icps[0]`, left every top-level collection empty, and\nwrote whole job objects where `{ jobRef, importance }` belongs. The retry recovered it, but a full\ngeneration was spent discovering the shape. The slice ordering below is a THINKING order — what to\nwork out first — never the structure of the answer.\n\nA MarketSnapshot is assembled from these slices, each owned by a dedicated\n`market_*` app-knowledge skill. Those skills are named here so you know which\nauthoring contract each slice belongs to, and so a later CODING agent can open\nthe right one — you cannot: this step has no tools, and sixteen skill bodies do\nnot fit in one brief. Everything you need to author the snapshot is in THIS\nmethod and your declared inputs; where a detail is genuinely only in a skill,\nsay so on what you author rather than inventing it. You author them in\ndependency order because later slices reference earlier refs:\n\n1. **Category** — the one market category the product competes in, plus the\n rejected adjacent categories. (`market-category`)\n2. **ICPs** — the Ideal Customer Profiles: the firmographic / demographic\n segments the product is sold to. (`market-icp`)\n3. **Personas** — the human roles inside each ICP, including buying-group\n members. Every ICP needs at least one persona. (`market-persona`)\n4. **Jobs / Pains / Gains** — the Strategyzer customer-profile triplet for\n the personas: what they are trying to do, what blocks them, what a win\n looks like. (`market-jobs-pains-gains`)\n5. **Tones of voice** — the named brand voices the product speaks in.\n (`market-tone-of-voice`)\n6. **Benefits** — the outcome claims the product delivers, weighted against\n the pains/gains they relieve/create. (`market-add-feature-benefit`)\n7. **Positionings** — the per-ICP marketing-truth promise. Author one per\n ICP that the product actually targets. (`market-positioning-authoring`)\n8. **Reach surfaces** — the go-to-market context: channels, competing\n alternatives, buying triggers + per-ICP buying journeys, proofs, and the\n objections proofs answer. (`market-channels`, `market-alternatives`,\n `market-triggers-and-journey`, `market-proof-and-objection`)\n9. **Message templates** — reusable prompt templates that render from the\n snapshot above. Author last; they reference the earlier slices.\n (`market-message-templates-authoring`)\n\nAuthor only the slices the product's stage warrants — a first pass may stop\nafter positionings and leave the phase-3/4 reach surfaces empty (they\ndefault to `[]`). A snapshot with a category, at least one ICP, its\npersonas, the jobs/pains/gains triplet, and at least one positioning is a\nlegitimate v1; the reach surfaces and message templates are additive.\n\n## Where the snapshot lives\n\nThe MarketSnapshot for this journey is placed under\n`specifications/src/market/index.ts`. That is the artifact this\nplaybook owns and the rest of the top-down phase reads. When the product's\ndefinition later stabilises, the snapshot is what seeds the durable market\nspecification under `./specifications/` — but at this phase it is a journey\nartifact, not yet app source.\n\n## Produce vs. refine — read state first\n\nThis playbook is **idempotent** on the journey's market artifact. Before\nauthoring anything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief; do not re-derive it. That state tells you which\n scope the snapshot must be complete *for*.\n2. Check whether a MarketSnapshot already exists by reading the artifact at the\n `market-snapshot` family's landing path, `specifications/src/market/index.ts`.\n The path belongs to the FAMILY, not to this playbook — every playbook that\n writes a market snapshot writes that same file. Its presence or absence\n selects the mode below.\n\n- **No snapshot yet** — produce a fresh one, authoring the slices in the\n order above.\n- **A snapshot exists** — *refine* it: read every slice, keep what still\n holds, and only add/correct the slices the current steering notes or new\n research call for. Never silently discard authored refs — a downstream\n positioning or benefit may depend on an ICP or persona ref, and dropping\n it orphans them (the validator will catch this, but honest refinement\n should not create the orphan in the first place).\n\n## Provenance — record where a claim came from\n\nYou are given the evidence a sibling research step gathered, with the URLs it read.\nWhere an entity's content rests on one of those sources, RECORD that URL on the entity\n— in the schema's own provenance fields, which exist for exactly this:\n\n| field | for |\n|---|---|\n| `pains[].evidence[]`, `gains[].evidence[]`, `benefits[].evidence` | what a source shows about the pain, gain or claim |\n| `proofs[].evidenceUrl`, `proofs[].attribution.url` | the page a proof points at |\n| `alternatives[].notes[]`, `category.notes[]`, `icps[].notes[]` | where the framing came from |\n\n⚠ An earlier revision of this section told you to use `authoredMetadata.notes` instead.\nThat was wrong, and the correction is recorded rather than quietly applied because the\nrun that exposed it did better than the instruction: handed the evidence, the model\nput 10 URLs into the typed `evidence`/`evidenceUrl` fields above and none into the\ngeneric metadata block it had been pointed at. Typed provenance is machine-readable\nand the generic block is prose; prefer the specific field every time one exists.\n\nThis is not bookkeeping. Measured on this playbook's first composite run\n(2026-08-29): the snapshot it produced carried **zero** source URLs and was, on that\ndimension, indistinguishable from the single-call version it replaced — the judge\ncalled the older one's evidence \"self-referential statements such as 'The vision\nspecifies…'\". A sourced claim and an invented one must not look the same in what you\nland, because nobody downstream can tell them apart afterwards.\n\nSo:\n\n- An entity grounded in a fetched page carries its URL in `authoredMetadata.notes`.\n- An entity you INFERRED carries that word, and `confidence` set honestly — `LOW` for\n a hypothesis, not `HIGH` because it reads well.\n- An entity the evidence did not cover is still authorable, and says so.\n\nOmit `authoredMetadata` only where the content is so self-evident that provenance\nwould be noise. A competitor's price is never that.\n\n## Research posture (scaffold depth)\n\nGround each slice in evidence, not invention. At this scaffold depth the\nresearch is whatever the executing agent can gather about the product's\ncategory, competitors, and buyers; capture the *shape* faithfully (real\ncategory, real competing alternatives, plausible ICPs and personas) rather\nthan aspirational fiction. Where you are inferring rather than citing, say so\nin the slice's authored prose so a later, deeper research pass can tighten\nit. Do **not** build a research pipeline or block on external tooling here —\nricher web-research capability is a later-phase concern; this playbook\nconsumes whatever the agent already knows plus the creator's steering.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. It\nenforces the cross-slice invariants — orphan refs (a positioning naming a\nmissing ICP, a benefit naming a missing pain/gain), an ICP with no persona,\ninfluence cycles, duplicate edges, proofs without support, message-template\nplaceholder mismatches, and more. Duplicate or malformed refs and\n`ERROR`-severity issues are hard failures; the snapshot does not advance\nuntil they clear. `WARN`-severity issues (e.g. stale-authored, a missing\npositioning for a targeted ICP) do not block but should be resolved. Read\n`market-snapshot-validation` for the full issue catalogue and emit a clean\nsnapshot the first time.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. The following are explicitly **out of\nscope here** and are deepened in the methodology-depth phase, not now:\n\n- **Deep competitive teardown** — the reach surfaces capture *that* an\n alternative exists and *why* a buyer might pick it; a quantified,\n feature-by-feature competitor matrix is later-phase work.\n- **Quantified FIT / Kano scoring** — `market-scoring-interpretation` reads\n the deterministic FIT scorer; at scaffold depth you consume it to sanity-\n check benefit weighting, not to drive a precise prioritization model. The\n prioritization seam stays pluggable (see the capability-map playbook).\n- **Opportunity / TAM sizing and evidence depth** — jobs/pains/gains are\n authored as framing, not as a sized, sourced market model.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nA single MarketSnapshot at `specifications/src/market/index.ts`,\nassembled from the slices above via their `market_*` skills, passing the\n`market-snapshot-valid` gate. The creator reviews the result (approval posture\n`approve_result`) before it is accepted as the journey's market intent.\n\n## References\n\nThese are skill FOLDERS installed in the application, listed so each slice's\nauthoring contract has a name. This step has no tools and does not open them.\n\n- `market-authoring-overview` — the orchestrator for\n the whole market slice; read it first to see how the slices fit together.\n- `market-category` — author the singular market\n category.\n- `market-icp` — author the Ideal Customer Profiles.\n- `market-persona` — author the personas per ICP.\n- `market-jobs-pains-gains` — author the Strategyzer\n jobs/pains/gains triplet.\n- `market-tone-of-voice` — author the named brand\n voices.\n- `market-add-feature-benefit` — author the benefit\n claims and their pain/gain weighting.\n- `market-positioning-authoring` — author the per-ICP\n positioning promise.\n- `market-channels` — author the reach channels.\n- `market-alternatives` — author the competing\n alternatives.\n- `market-triggers-and-journey` — author buying\n triggers and per-ICP buying journeys.\n- `market-proof-and-objection` — author proofs and\n the objections they answer.\n- `market-message-templates-authoring` — author the\n reusable message templates (last).\n- `market-scoring-interpretation` — interpret the\n deterministic FIT scorer to sanity-check benefit weighting.\n- `market-snapshot-validation` — the full validation\n issue catalogue the quality gate enforces.\n",
|
|
40
40
|
"skillRefs": [
|
|
41
|
-
"journey-status",
|
|
42
41
|
"market-authoring-overview",
|
|
43
42
|
"market-category",
|
|
44
43
|
"market-icp",
|
|
@@ -20,7 +20,7 @@ be rerun after the working definitions change.
|
|
|
20
20
|
|
|
21
21
|
## Readiness and inputs
|
|
22
22
|
|
|
23
|
-
|
|
23
|
+
Inspect the loaded specification values this run is given. `vision-brief`,
|
|
24
24
|
`market-snapshot`, `requirements` and `roadmap` must each pass their declared
|
|
25
25
|
family-validity precondition. A cross-family assessment cannot replace that validation.
|
|
26
26
|
|
|
@@ -52,12 +52,8 @@
|
|
|
52
52
|
"outputs": [],
|
|
53
53
|
"stepOutputs": [],
|
|
54
54
|
"method": {
|
|
55
|
-
"guidance": "# Top-Down Coherence Assessment\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## Purpose\n\nAssess whether the current top-down definitions agree well enough to guide the next\nwork. This playbook writes no application specification and accepts nothing. It can\nbe rerun after the working definitions change.\n\n## Readiness and inputs\n\
|
|
56
|
-
"skillRefs": [
|
|
57
|
-
"journey-status",
|
|
58
|
-
"journey-report",
|
|
59
|
-
"journey-approve"
|
|
60
|
-
],
|
|
55
|
+
"guidance": "# Top-Down Coherence Assessment\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## Purpose\n\nAssess whether the current top-down definitions agree well enough to guide the next\nwork. This playbook writes no application specification and accepts nothing. It can\nbe rerun after the working definitions change.\n\n## Readiness and inputs\n\nInspect the loaded specification values this run is given. `vision-brief`,\n`market-snapshot`, `requirements` and `roadmap` must each pass their declared\nfamily-validity precondition. A cross-family assessment cannot replace that validation.\n\nThe evaluator reads those families plus `feature-drafts` and `business-model` when\npresent. These optional inputs add implementation and commercial context; their\nabsence does not introduce another readiness gate. The runtime loads the exported\nworking-tree values. There is no evidence-sealing step or accepted-head projection.\n\nThe computed coherence report (the declared `coherence_report` context section of your brief) supplies the\nsupported dangling-reference and coverage checks. Interpret their consequences;\ndo not invent checks or recompute the arithmetic in prose.\n\n## Evaluation\n\nThe compiled evaluation treatment supplies the criteria and their guidance. For each\ncriterion, relate the verdict to the available evidence and explain what should change.\nUse `INDETERMINATE` when evidence does not support a semantic conclusion.\n\nThe current judge aggregates by worst severity:\n`GAP` → `INDETERMINATE` → `CONCERN` → `PASS`.\nDuplicate criterion results retain the worst verdict and all their rationales. Missing\ncriterion results remain indeterminate. The treatment's declarative policy fields do\nnot independently create another approval or continuation workflow in this runner.\n\nA failed model call or unusable treatment produces a skipped/unavailable judge result\n(`judged: false` with `skipped`), not a semantic pass. Check that status before using\nany verdict as evidence that assessment happened.\n\n## Read the result and decide what to do\n\nThe response reports `assessed: true`, the loaded `subjects`, a `reviewGuide`, the\njudge result when supplied, and `accepted: false`. The judge is advisory: this call\ndoes not automatically revise families, request authority, switch phases or block a\ntransition based on its verdict. Use the findings to choose the next work and review\nits outcome through the application's actual workflow.\n\nThis invocation performs one assessment. Do not infer enforced revision or\nadditional-evidence loops from the playbook's declared budget or continuation fields.\nWhen an input changes, reassess the new values rather than treating an old verdict as\nproof about the changed product.\n",
|
|
56
|
+
"skillRefs": [],
|
|
61
57
|
"skillBodyRefs": [],
|
|
62
58
|
"contextSources": [
|
|
63
59
|
"coherence_report"
|
|
@@ -25,10 +25,26 @@ override that protected consequence.
|
|
|
25
25
|
For every functional requirement:
|
|
26
26
|
|
|
27
27
|
- state one distinct product capability, not an implementation task;
|
|
28
|
-
- connect it to accepted vision or market evidence
|
|
28
|
+
- connect it to accepted vision or market evidence (when the brief says the
|
|
29
|
+
market does not apply to this application, the vision alone is the evidence:
|
|
30
|
+
cite its problem, its users and its success criteria, and declare no market
|
|
31
|
+
cross-references);
|
|
29
32
|
- keep current-horizon scope explicit; and
|
|
30
33
|
- provide observable acceptance language where meaningful.
|
|
31
34
|
|
|
35
|
+
## Refine, don't re-author
|
|
36
|
+
|
|
37
|
+
When requirements already exist, they arrive in your brief as the `requirements` input. Refine them:
|
|
38
|
+
|
|
39
|
+
- **Keep what still holds.** A requirement nothing asks you to change keeps its semantic slug, its statement
|
|
40
|
+
and its cross-references. Do not reword it for style.
|
|
41
|
+
- **Reuse slugs.** A requirement that changes keeps its slug; never mint a second slug for the same
|
|
42
|
+
capability, since every plan and task derived from the requirements cites it.
|
|
43
|
+
- **Change what you were asked to.** When the brief says what this run is for (a refinement of the
|
|
44
|
+
requirements, or a vision or market that moved), change that, and leave the rest as it is.
|
|
45
|
+
- **Leave a secondary line's requirements alone.** An element another line contributed is carried forward by
|
|
46
|
+
the runtime whether or not you restate it; do not rewrite it as your own.
|
|
47
|
+
|
|
32
48
|
For every non-functional requirement, preserve the declared quality axis and
|
|
33
49
|
measurement intent. Do not invent regulatory applicability. Missing or
|
|
34
50
|
contradictory accepted evidence yields a request for evidence or revision, not
|
|
@@ -38,11 +38,8 @@
|
|
|
38
38
|
],
|
|
39
39
|
"stepOutputs": [],
|
|
40
40
|
"method": {
|
|
41
|
-
"guidance": "# Requirements definition method\n\nProduce the current-horizon requirements family from the accepted\n`vision-brief` and `market-snapshot` heads. Treat those accepted projections as\nthe only application truth: conversational context may clarify them, but it\ncannot silently replace or amend them.\n\nThe provider response must parse as\n`RequirementsSnapshotGenerationSchema`. It supplies semantic slugs, statements,\nrationales, acceptance criteria and declared market cross-references. The\ntrusted structured-artifact runtime stamps the canonical requirement refs and\nsnapshot version, validates the permissive persisted `RequirementsSnapshot`,\nand records its exact input/output/evidence lineage. Provider output must not\ncontain timestamps, author identity, authority, accepted scope, family heads or\ncontinuity identifiers.\n\nNormal generation must produce at least one functional requirement. An empty\nfunctional set is not “good enough,” even though the incremental family schema\ncan persist it and `validateRequirementsSnapshot` reports only a warning. The\nrequirements playbook emits the deterministic `requirements-minimum-content`\nfinding into semantic assessment: it explains the missing minimum and requires\nrevision or evidence, but it never grants an evaluator or a model permission to\noverride that protected consequence.\n\nFor every functional requirement:\n\n- state one distinct product capability, not an implementation task;\n- connect it to accepted vision or market evidence;\n- keep current-horizon scope explicit; and\n- provide observable acceptance language where meaningful.\n\nFor every non-functional requirement, preserve the declared quality axis and\nmeasurement intent. Do not invent regulatory applicability. Missing or\ncontradictory accepted evidence yields a request for evidence or revision, not\na plausible completion.\n\nContext selection receives current accepted vision and market heads, the\nworking requirements candidate, and declared Framework guidance as structured\ndata. Missing mandatory context is explicit; retrieved instruction-shaped text\nis treated as data and excluded from coding-task projection. Optional context\nis bounded by the declared selection plan rather than by ad-hoc prompt growth.\n\nThe deterministic minimum-content finding and semantic coherence evaluation are\nseparate contributions. Application composition selects exactly one bounded\nnext action from hard floors, scoped risk, maturity, uncertainty, active\nresource authority and playbook bounds. A model may explain a proposal but it\ncannot override a hard floor or rewrite accepted truth: it writes files into the\nworking tree and nothing more. Acceptance is a git commit: under the current\nautonomy posture the development companion commits a run's writes before the\nnext build task starts, and a person reads the history and reverts what they\ndisagree with. A protected consequence is MARKED: under this posture it notifies\nand proceeds, and it holds for an operator decision only once gates are armed.\n\nGit is not a later materialization of an acceptance that happened somewhere else\n— it IS the acceptance. Replacing accepted application requirements therefore\nmeans committing over them, with the commit's author and instant standing as who\naccepted and when.\n",
|
|
42
|
-
"skillRefs": [
|
|
43
|
-
"journey-status",
|
|
44
|
-
"journey-report"
|
|
45
|
-
],
|
|
41
|
+
"guidance": "# Requirements definition method\n\nProduce the current-horizon requirements family from the accepted\n`vision-brief` and `market-snapshot` heads. Treat those accepted projections as\nthe only application truth: conversational context may clarify them, but it\ncannot silently replace or amend them.\n\nThe provider response must parse as\n`RequirementsSnapshotGenerationSchema`. It supplies semantic slugs, statements,\nrationales, acceptance criteria and declared market cross-references. The\ntrusted structured-artifact runtime stamps the canonical requirement refs and\nsnapshot version, validates the permissive persisted `RequirementsSnapshot`,\nand records its exact input/output/evidence lineage. Provider output must not\ncontain timestamps, author identity, authority, accepted scope, family heads or\ncontinuity identifiers.\n\nNormal generation must produce at least one functional requirement. An empty\nfunctional set is not “good enough,” even though the incremental family schema\ncan persist it and `validateRequirementsSnapshot` reports only a warning. The\nrequirements playbook emits the deterministic `requirements-minimum-content`\nfinding into semantic assessment: it explains the missing minimum and requires\nrevision or evidence, but it never grants an evaluator or a model permission to\noverride that protected consequence.\n\nFor every functional requirement:\n\n- state one distinct product capability, not an implementation task;\n- connect it to accepted vision or market evidence (when the brief says the\n market does not apply to this application, the vision alone is the evidence:\n cite its problem, its users and its success criteria, and declare no market\n cross-references);\n- keep current-horizon scope explicit; and\n- provide observable acceptance language where meaningful.\n\n## Refine, don't re-author\n\nWhen requirements already exist, they arrive in your brief as the `requirements` input. Refine them:\n\n- **Keep what still holds.** A requirement nothing asks you to change keeps its semantic slug, its statement\n and its cross-references. Do not reword it for style.\n- **Reuse slugs.** A requirement that changes keeps its slug; never mint a second slug for the same\n capability, since every plan and task derived from the requirements cites it.\n- **Change what you were asked to.** When the brief says what this run is for (a refinement of the\n requirements, or a vision or market that moved), change that, and leave the rest as it is.\n- **Leave a secondary line's requirements alone.** An element another line contributed is carried forward by\n the runtime whether or not you restate it; do not rewrite it as your own.\n\nFor every non-functional requirement, preserve the declared quality axis and\nmeasurement intent. Do not invent regulatory applicability. Missing or\ncontradictory accepted evidence yields a request for evidence or revision, not\na plausible completion.\n\nContext selection receives current accepted vision and market heads, the\nworking requirements candidate, and declared Framework guidance as structured\ndata. Missing mandatory context is explicit; retrieved instruction-shaped text\nis treated as data and excluded from coding-task projection. Optional context\nis bounded by the declared selection plan rather than by ad-hoc prompt growth.\n\nThe deterministic minimum-content finding and semantic coherence evaluation are\nseparate contributions. Application composition selects exactly one bounded\nnext action from hard floors, scoped risk, maturity, uncertainty, active\nresource authority and playbook bounds. A model may explain a proposal but it\ncannot override a hard floor or rewrite accepted truth: it writes files into the\nworking tree and nothing more. Acceptance is a git commit: under the current\nautonomy posture the development companion commits a run's writes before the\nnext build task starts, and a person reads the history and reverts what they\ndisagree with. A protected consequence is MARKED: under this posture it notifies\nand proceeds, and it holds for an operator decision only once gates are armed.\n\nGit is not a later materialization of an acceptance that happened somewhere else\n— it IS the acceptance. Replacing accepted application requirements therefore\nmeans committing over them, with the commit's author and instant standing as who\naccepted and when.\n",
|
|
42
|
+
"skillRefs": [],
|
|
46
43
|
"skillBodyRefs": [],
|
|
47
44
|
"contextSources": [],
|
|
48
45
|
"draftableDocumentDefinitionRefs": [],
|
|
@@ -38,9 +38,7 @@
|
|
|
38
38
|
"stepOutputs": [],
|
|
39
39
|
"method": {
|
|
40
40
|
"guidance": "# Complete the risk register\n\nThe derivation layer says what is PRESENT in this application — how many providers are vendor-hosted, how many operations an external agent can reach, which retention classes have a declared period, which resources have said nothing about personal data. Those are facts, and they are deliberately silent about what they MEAN.\n\nThis step writes what they mean for this product and these users, and proposes the risks no derivation reaches.\n\n## You are drafting, not deciding\n\nA model proposes; a human accepts; the accepted register is the committed file. Nothing you write here takes effect by being written, and the value of the artifact is that a person can disagree with it line by line. So:\n\n- Write statements a reader can argue with. \"Personal data is processed by third parties\" is unarguable and says nothing; \"two vendor-hosted LLM providers receive task titles and user names, which are the fields customers type freely\" is a claim someone can check and correct.\n- Never write a statement you cannot ground. If the evidence for a risk is that it sounds prudent, it is a PROPOSED entry and must be marked as one.\n- Do not soften a derived fact to make the register read better. The register is read by people deciding how deeply to audit something; a reassuring one is worse than none.\n\nAfter landing, the advisory judge reads the register against three criteria — honest entry origins, arguable statements with grounded bands, and the boundary with other mechanisms — and its verdicts reach the person accepting the register as notes. A verdict never refuses a landing.\n\n## Two kinds of entry, and the difference is what may be believed\n\n**SIGNAL_DERIVED** — completed from a derived signal, which the entry names. The measurement can be re-run, so the entry's premise is falsifiable: if the signal stops reporting the exposure, the statement resting on it is stale rather than merely old. One derived entry per signal.\n\n**PROPOSED** — a business risk nothing measures. This is why the step exists rather than the derivation being the whole answer: a register limited to what code can compute would omit most of what a product actually carries. Ground each one in the vision, the business model and the market snapshot, which this application has already authored, and never anchor it to a signal — a proposal pointing at a measurement is a derived entry wearing the wrong label.\n\n## Weighting is two qualitative bands and NOTHING is multiplied\n\nLikelihood and impact are each one of five bands. There is no score, no rating and no product of the two anywhere in the register, and this is not a stylistic preference: the derivation layer beneath this one asserts structurally that it emits no score, because a number is what a reader trusts without checking. Two judgements multiplied into a third judgement would put exactly that underneath a layer built to refuse it.\n\nGround the bands in what is IMPLEMENTED, not in how the risk sounds. \"Impact HIGH because the erasure path is manual\" is grounded. \"Impact HIGH because data breaches are serious\" is not — it would be equally true of every application ever built, which is the test for a weighting that carries no information.\n\nWhere the application has declared a posture for the signal, record it on the entry. A posture of AVOIDED that the measurement contradicts is not yours to resolve: state the risk as measured, note the contradiction in the weighting grounding, and let the person accepting the register decide whether the declaration or the product is wrong.\n\n## The signals, and what to do when they are not all there\n\nThe derived signals arrive in the declared `risk_signals` context section of your brief — measured facts about this application's own declarations, each with the inputs it came from and none with a score. Ground your weighting in them. Do not restate a signal as a risk, do not treat their order as a priority, and never re-derive or estimate one: they are computed, and a number you produced yourself would be indistinguishable on the page from one that was measured.\n\nFour of them are read from the application's configuration and always arrive. The two that need every resource materialized — the personal-data inventory and the MCP exposure — can be absent when the application cannot be introspected, and the section simply will not carry them.\n\nThe register does not require the derivation to have run. If signals were not supplied to this run, or only some were, produce the PROPOSED entries you can ground in the authored specification families, state plainly in the register which derived half is absent, and finish.\n\nDo not stop, do not ask for evidence to be collected first, and do not treat an absent measurement as an absent risk. A step that cannot proceed until evidence exists has made a measurement into a precondition, and a compliance workflow may never stand in front of the mechanism it describes.\n\n## What belongs to other mechanisms\n\n- **Which control objectives this application claims** — the compliance programme. A register entry may mention a control; it never binds one.\n- **Whether a control's evidence is adequate** — the evidence-adequacy step. The register says a risk exists, never that it has been discharged.\n- **How deeply to audit a demand** — a consumer of this register, not part of it. Write the risk; do not write the audit plan.\n- **Retention periods, provider deployment choices, jurisdictions** — configuration the application already declares. Read them; do not restate them as risks, and never contradict them here.\n",
|
|
41
|
-
"skillRefs": [
|
|
42
|
-
"journey-status"
|
|
43
|
-
],
|
|
41
|
+
"skillRefs": [],
|
|
44
42
|
"skillBodyRefs": [],
|
|
45
43
|
"contextSources": [
|
|
46
44
|
"risk_signals"
|
|
@@ -72,9 +72,10 @@ must already exist (the `artifact_exists` precondition enforces the capability m
|
|
|
72
72
|
is in place — you cannot plan releases before you know the capabilities). Before
|
|
73
73
|
planning anything:
|
|
74
74
|
|
|
75
|
-
1. Read the current journey state and scope
|
|
76
|
-
|
|
77
|
-
exists
|
|
75
|
+
1. Read the current journey state and scope from what this run is given — the loaded
|
|
76
|
+
specifications and the workspace sections of your brief — and do not re-derive it. Confirm a `market-snapshot`
|
|
77
|
+
exists (unless the market does not apply, below) and check whether a
|
|
78
|
+
`roadmap` already exists from an earlier run.
|
|
78
79
|
2. Read the capability-mapped **MarketSnapshot** (benefits + their
|
|
79
80
|
`deliveredByFeatureRefs`, and their authored Kano categories). The FIT half of
|
|
80
81
|
that signal is COMPUTED for you and arrives in
|
|
@@ -93,6 +94,17 @@ phases rather than re-cutting them blind.)
|
|
|
93
94
|
You **read** `market-snapshot` + `feature-drafts` + `requirements` +
|
|
94
95
|
`vision-brief`; you **write** the `roadmap` family.
|
|
95
96
|
|
|
97
|
+
### When the market does not apply
|
|
98
|
+
|
|
99
|
+
On an application whose line has no market (an internal tool), your brief says the
|
|
100
|
+
`market-snapshot` **does not apply**. That is an answer, not a missing input: do not
|
|
101
|
+
wait for one, and never invent ICPs, benefits or Kano categories. Cut the MVP from
|
|
102
|
+
the **requirements** and the **VisionSnapshot** instead: the first phase is the
|
|
103
|
+
smallest release that lets the operating team named in the vision do the job the
|
|
104
|
+
vision's success criteria describe, and a requirement is MVP-critical when a success
|
|
105
|
+
criterion cannot be met without it. The feature drafts still tell you how much of the
|
|
106
|
+
product each requirement pulls in.
|
|
107
|
+
|
|
96
108
|
## The phasing loop (build the ordered releases)
|
|
97
109
|
|
|
98
110
|
1. **Establish the MVP cut first.** The first phase is the smallest coherent
|
|
@@ -281,7 +293,3 @@ accepted as the journey's roadmap.
|
|
|
281
293
|
These are skill FOLDERS installed in the application, named so each piece of work has an
|
|
282
294
|
authoring contract a later coding agent can open. This step has no tools and does not open them;
|
|
283
295
|
what reaches you is this method, your declared inputs, and the brief's own sections.
|
|
284
|
-
|
|
285
|
-
- `journey-status` — read the current journey state and
|
|
286
|
-
scope, and confirm a `market-snapshot` (the capability map) already exists to
|
|
287
|
-
plan releases from.
|