@wildo-ai/framework-knowledge 1.1.9 → 1.1.11
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +11 -0
- package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +4 -2
- package/dist/claude-marketplace/plugins/wildo/references/expert-personas-and-deliberations.md +26 -7
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +4 -2
- package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +4 -2
- package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +9 -3
- package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +543 -80
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.research-provenance.d.ts +88 -0
- package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -0
- package/dist/esm/framework-knowledge.research-provenance.js +140 -0
- package/dist/esm/framework-knowledge.research-provenance.js.map +1 -0
- package/dist/esm/index.d.ts +2 -0
- package/dist/esm/index.d.ts.map +1 -1
- package/dist/esm/index.js +2 -0
- package/dist/esm/index.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +43 -2
- 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 +138 -21
- 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.js +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/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.js +1 -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 +17 -9
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +22 -11
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +89 -9
- 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 +6 -5
- 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 +6 -4
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +2 -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 +7 -2
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +12 -3
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +8 -4
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +28 -6
- 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 +23 -5
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +9 -3
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +14 -2
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +14 -6
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +5 -3
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +11 -9
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +17 -3
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +19 -2
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.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-conception/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +2 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +9 -3
- 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 +34 -7
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +39 -13
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +14 -6
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +38 -3
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +23 -8
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts +95 -0
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +111 -0
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -0
- 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 +15 -3
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/esm/source-anchor-grammar.d.ts +70 -0
- package/dist/esm/source-anchor-grammar.d.ts.map +1 -0
- package/dist/esm/source-anchor-grammar.js +114 -0
- package/dist/esm/source-anchor-grammar.js.map +1 -0
- 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/method.md +6 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
- 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 +497 -32
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +44 -3
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +302 -8
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +2 -2
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +12 -7
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +11 -3
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +118 -11
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -3
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +41 -10
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +7 -5
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +5 -0
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +12 -0
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +79 -1
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +16 -4
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +187 -14
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +23 -3
- package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +3 -2
- package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +6 -2
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +99 -24
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +38 -3
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +4 -3
- package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +5 -2
- package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +2 -2
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +8 -6
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +16 -5
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +3 -3
- package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +56 -16
- package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +6 -4
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +30 -9
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +5 -3
- package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +12 -1
- package/dist/knowledge/playbooks/top_down.business-model/method.md +6 -0
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +2 -2
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +10 -9
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +2 -2
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +12 -2
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.definition/method.md +7 -2
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +5 -4
- package/dist/knowledge/playbooks/top_down.expert-personas/method.md +10 -3
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +18 -4
- package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +5 -2
- package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +2 -2
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +26 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +5 -3
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +84 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +6 -3
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +1 -1
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.service-method/method.md +198 -0
- package/dist/knowledge/playbooks/top_down.service-method/playbook.json +96 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +23 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +23 -4
- package/dist/knowledge/references/acp.execution-profile.md +9 -1
- package/dist/knowledge/references/application-maturity.config.md +1 -1
- package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +55 -0
- package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +13 -2
- package/dist/knowledge/references/backend.inbound-handlers.agents.md +10 -3
- package/dist/knowledge/references/backend.inbound-handlers.definition.md +426 -5
- package/dist/knowledge/references/backend.inbound-handlers.pipelines.md +62 -0
- package/dist/knowledge/references/blueprint.definition-contract.md +483 -0
- package/dist/knowledge/references/brand.name-choice.config.md +20 -3
- package/dist/knowledge/references/brand.name-screening.config.md +58 -3
- package/dist/knowledge/references/brand.visual-tone.config.md +26 -8
- package/dist/knowledge/references/build-plan.task-graph.config.md +292 -7
- package/dist/knowledge/references/business-model.pricing-plan.config.md +7 -0
- package/dist/knowledge/references/business-model.snapshot.validation.md +18 -0
- package/dist/knowledge/references/capability-composition.config.md +4 -3
- package/dist/knowledge/references/cli.market.generate-command.md +2 -1
- package/dist/knowledge/references/companion.market.prompt-renderer.md +11 -6
- package/dist/knowledge/references/companion.technical-doc.service.md +166 -32
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +14 -0
- package/dist/knowledge/references/engine.saas-technical-doc.config.md +1 -1
- package/dist/knowledge/references/engine.saas-website.config.md +16 -44
- package/dist/knowledge/references/example.ai-use-declaration.agent.md +37 -0
- package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +44 -0
- package/dist/knowledge/references/{example.authorization.service-provider-organization-wide-access.md → example.authorization.relationship-organization-wide-access.md} +2 -2
- package/dist/knowledge/references/example.backend.custom-operation.audit-event.md +81 -0
- package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +259 -0
- package/dist/knowledge/references/example.backend.custom-operation.computed-total.md +153 -0
- package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +129 -0
- package/dist/knowledge/references/example.blueprint.definition.internal-tool.md +45 -0
- package/dist/knowledge/references/example.config.app-shell.full.md +6 -3
- package/dist/knowledge/references/example.config.app-shell.hosted-components.md +4 -1
- package/dist/knowledge/references/example.config.backend.inbound-email.md +4 -2
- package/dist/knowledge/references/example.config.backend.required-floors.md +4 -2
- package/dist/knowledge/references/example.config.design-system.full.md +40 -116
- package/dist/knowledge/references/example.data-seeding.minimal.md +10 -9
- package/dist/knowledge/references/example.data-seeding.row-reference.md +80 -0
- package/dist/knowledge/references/example.email.template.minimal.md +1 -1
- package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +10 -0
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +70 -14
- package/dist/knowledge/references/example.flows-actors.declared-flow.md +115 -0
- package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +12 -0
- package/dist/knowledge/references/example.inbound.email-channel-handler.md +10 -1
- package/dist/knowledge/references/example.infra.environment-config.local.md +24 -0
- package/dist/knowledge/references/example.layout-2d.registration.md +11 -0
- package/dist/knowledge/references/example.minion.contained-tick.md +1 -1
- package/dist/knowledge/references/example.module.relationships.scope-membership-junction.md +8 -10
- package/dist/knowledge/references/example.organizations.relationship-kinds.md +26 -0
- package/dist/knowledge/references/example.professional-qualifications.declaration.md +10 -0
- package/dist/knowledge/references/example.professional-qualifications.gate.md +25 -0
- package/dist/knowledge/references/example.provider.backend-module-shape.md +10 -0
- package/dist/knowledge/references/example.provider.frontend-facet.on-demand-sdk.md +41 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +4 -5
- package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +7 -5
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -1
- package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +74 -0
- package/dist/knowledge/references/example.resource.personal-data.free-text-field.md +19 -0
- package/dist/knowledge/references/example.resource.personal-data.person-without-account.md +27 -0
- package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +152 -0
- package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +23 -7
- package/dist/knowledge/references/example.resource.ui-behavior.filter-presets.md +15 -0
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +60 -22
- package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +81 -0
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +19 -20
- package/dist/knowledge/references/example.spec.composite-view.workspace.md +10 -2
- package/dist/knowledge/references/example.views.app-level.home-definition.md +13 -0
- package/dist/knowledge/references/example.views.chart-definition.shared.md +83 -0
- package/dist/knowledge/references/example.views.composite-view.workspace.md +10 -3
- package/dist/knowledge/references/example.website.blocks.section.md +20 -0
- package/dist/knowledge/references/example.website.blocks.site-choices.md +78 -0
- package/dist/knowledge/references/example.website.blocks.site-configs.md +155 -0
- package/dist/knowledge/references/example.website.demo.append.md +57 -0
- package/dist/knowledge/references/example.website.demo.approval.md +47 -0
- package/dist/knowledge/references/example.website.demo.celebrate.md +39 -0
- package/dist/knowledge/references/example.website.demo.complete-items.md +103 -0
- package/dist/knowledge/references/example.website.demo.connect.md +45 -0
- package/dist/knowledge/references/example.website.demo.dashboard.md +74 -0
- package/dist/knowledge/references/example.website.demo.query-answer.md +77 -0
- package/dist/knowledge/references/example.website.demo.status-lifecycle.md +71 -0
- package/dist/knowledge/references/example.website.demo.transform.md +43 -0
- package/dist/knowledge/references/example.website.page.manifest.md +2 -6
- package/dist/knowledge/references/example.website.section.bento.md +27 -0
- package/dist/knowledge/references/example.website.section.contact-form.md +15 -0
- package/dist/knowledge/references/example.website.section.factories.md +82 -0
- package/dist/knowledge/references/example.website.section.faq.md +17 -0
- package/dist/knowledge/references/example.website.section.footer-cta.md +13 -0
- package/dist/knowledge/references/example.website.section.hero.md +16 -0
- package/dist/knowledge/references/example.website.section.latest-posts.md +15 -0
- package/dist/knowledge/references/example.website.section.marquee.md +26 -0
- package/dist/knowledge/references/example.website.section.roadmap.md +25 -0
- package/dist/knowledge/references/example.website.section.site-block.md +43 -0
- package/dist/knowledge/references/example.website.section.solution-paths.md +17 -0
- package/dist/knowledge/references/example.website.section.stats.md +23 -0
- package/dist/knowledge/references/example.website.section.steps.md +15 -0
- package/dist/knowledge/references/example.website.showcase.tour.md +49 -0
- package/dist/knowledge/references/example.website.theme.composed.md +69 -0
- package/dist/knowledge/references/experience-plan.config.md +76 -7
- package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +6 -0
- package/dist/knowledge/references/external-connectors.frontend-provider-sdk-activation-mode.md +27 -0
- package/dist/knowledge/references/external-connectors.models.connection-target.md +99 -0
- package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +6 -0
- package/dist/knowledge/references/external-connectors.models.hook-inbound-endpoint.md +352 -0
- package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +64 -0
- package/dist/knowledge/references/external-connectors.models.hook-trigger-strategy.md +97 -0
- package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +61 -2
- package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +70 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +253 -0
- package/dist/knowledge/references/external-connectors.models.subject-erasure-effect.md +105 -0
- package/dist/knowledge/references/integration-plan.config.md +21 -1
- package/dist/knowledge/references/market.context-block.builder.md +1 -1
- package/dist/knowledge/references/market.references.weighted-edges.md +14 -1
- package/dist/knowledge/references/minions.tick-contract.md +2 -2
- package/dist/knowledge/references/placement-plan.config.md +107 -2
- package/dist/knowledge/references/platform.config.environment.deployment.md +9 -1
- package/dist/knowledge/references/platform.config.infrastructure-host.md +2 -0
- package/dist/knowledge/references/platform.config.platform-key-management.md +206 -0
- package/dist/knowledge/references/platform.config.saas.md +106 -14
- package/dist/knowledge/references/platform.key-management.vault-custody.md +78 -0
- package/dist/knowledge/references/presets.3d.layout-contract.md +4 -30
- package/dist/knowledge/references/presets.3d.register-layout.md +14 -36
- package/dist/knowledge/references/presets.layouts-2d.authoring.md +157 -0
- package/dist/knowledge/references/presets.layouts-2d.register-layout.md +53 -0
- package/dist/knowledge/references/presets.layouts-2d.settings.md +53 -0
- package/dist/knowledge/references/presets.layouts-2d.vocabulary.md +41 -0
- package/dist/knowledge/references/presets.models.palette-contrast.md +183 -0
- package/dist/knowledge/references/presets.models.palette-derivation.md +93 -0
- package/dist/knowledge/references/presets.models.surface-policy.defaults.md +27 -0
- package/dist/knowledge/references/presets.models.surface-variant.md +10 -0
- package/dist/knowledge/references/presets.models.theme-contract.md +136 -0
- package/dist/knowledge/references/presets.models.theme-personality-lexicon.md +81 -0
- package/dist/knowledge/references/presets.models.theme-personality.md +159 -0
- package/dist/knowledge/references/presets.themes.compose-theme.md +46 -0
- package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -2
- package/dist/knowledge/references/requirements.non-functional-requirement.config.md +2 -0
- package/dist/knowledge/references/requirements.references.conventions.md +1 -1
- package/dist/knowledge/references/requirements.snapshot.config.md +57 -1
- package/dist/knowledge/references/requirements.snapshot.validation.md +35 -1
- package/dist/knowledge/references/roadmap.phase.config.md +2 -16
- package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +131 -0
- package/dist/knowledge/references/saas.backend.a2a.token-budget.md +77 -11
- package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +158 -0
- package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +3 -1
- package/dist/knowledge/references/saas.backend.audit-logs.log-event.md +63 -0
- package/dist/knowledge/references/saas.backend.crypto-keys.application-keys.md +100 -0
- package/dist/knowledge/references/saas.backend.custom-operation.commit-outcome-read-back.md +208 -0
- package/dist/knowledge/references/saas.backend.custom-operation.target-authority.md +33 -0
- package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +131 -1
- package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +60 -0
- package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +156 -0
- package/dist/knowledge/references/saas.backend.domain-module.md +76 -1
- package/dist/knowledge/references/saas.backend.email-template.definition.md +34 -0
- package/dist/knowledge/references/saas.backend.email-template.words.md +98 -0
- package/dist/knowledge/references/saas.backend.email.send.md +84 -0
- package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +9 -1
- package/dist/knowledge/references/saas.backend.flows-actors.ask-person-tool.md +79 -0
- package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-case-selector.md +71 -0
- package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +21 -10
- package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +11 -5
- package/dist/knowledge/references/saas.backend.flows-actors.chat-agent-declaration.md +51 -0
- package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +207 -0
- package/dist/knowledge/references/saas.backend.flows-actors.decision-notice-handler.md +239 -0
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +300 -3
- package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +13 -2
- package/dist/knowledge/references/saas.backend.flows-actors.operation-approval-resolvers.md +50 -0
- package/dist/knowledge/references/saas.backend.flows-actors.present-records-tool.md +106 -0
- package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +14 -1
- package/dist/knowledge/references/saas.backend.flows-actors.retrieval-tool.md +205 -0
- package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +21 -5
- package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +27 -0
- package/dist/knowledge/references/saas.backend.flows.start-flow.md +47 -0
- package/dist/knowledge/references/saas.backend.notifications.operation-email-template-ref.md +60 -0
- package/dist/knowledge/references/saas.backend.pdf-template.collection-definition.md +5 -3
- package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +15 -25
- package/dist/knowledge/references/saas.backend.rate-limit-service.check-policy.md +3 -2
- package/dist/knowledge/references/saas.backend.submission-challenge.md +4 -0
- package/dist/knowledge/references/saas.backend.system-access-service.md +242 -107
- package/dist/knowledge/references/saas.config.content-security-policy.md +1 -2
- package/dist/knowledge/references/saas.data-seeding.computed-entry.md +43 -0
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +8 -2
- package/dist/knowledge/references/saas.data-seeding.row-reference.md +93 -0
- package/dist/knowledge/references/saas.data-seeding.run-ledger.md +3 -0
- package/dist/knowledge/references/saas.external-data.admin-endpoints.md +70 -3
- package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +3 -0
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +10 -2
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +10 -16
- package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +7 -3
- package/dist/knowledge/references/saas.frontend.app-shell.register-shell-layout.md +97 -0
- package/dist/knowledge/references/saas.frontend.app-shell.shell-layout-contract.md +60 -0
- package/dist/knowledge/references/saas.frontend.app-shell.shell-motion-contract.md +274 -0
- package/dist/knowledge/references/saas.frontend.app-shell.use-shell-motion.md +73 -0
- package/dist/knowledge/references/saas.frontend.brand-identity.md +6 -0
- package/dist/knowledge/references/saas.frontend.chart-view.inserted-declaration.md +13 -0
- package/dist/knowledge/references/saas.frontend.chat-sign-in-completion.md +99 -0
- package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +126 -0
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +9 -3
- package/dist/knowledge/references/saas.frontend.domain-module.md +5 -0
- package/dist/knowledge/references/saas.frontend.embedded-resource-descent.md +2 -1
- package/dist/knowledge/references/saas.frontend.execution-view.definition.md +17 -3
- package/dist/knowledge/references/saas.frontend.field-tiles.md +76 -0
- package/dist/knowledge/references/saas.frontend.flows-actors-view.md +10 -2
- package/dist/knowledge/references/saas.frontend.focus-indicator.md +119 -0
- package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +324 -0
- package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +109 -0
- package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +61 -0
- package/dist/knowledge/references/saas.frontend.operation-key-and-resource-config-like.md +68 -1
- package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +14 -24
- package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +149 -0
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +98 -34
- package/dist/knowledge/references/saas.frontend.resource-label-params.md +54 -0
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +17 -11
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +125 -58
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +13 -7
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destination-roles.md +25 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +141 -32
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +64 -2
- package/dist/knowledge/references/saas.models.agent-suspension.md +75 -0
- package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +2 -2
- package/dist/knowledge/references/saas.models.agent-work-decision-contents-read.md +69 -0
- package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +11 -2
- package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +20 -3
- package/dist/knowledge/references/saas.models.agent-work-output-review.md +3 -3
- package/dist/knowledge/references/saas.models.agent-work-override-rate.md +6 -5
- package/dist/knowledge/references/saas.models.agent-work-review-config.md +22 -4
- package/dist/knowledge/references/saas.models.analytics.value-moments.md +22 -0
- package/dist/knowledge/references/saas.models.application-agent-policy.md +28 -0
- package/dist/knowledge/references/saas.models.application-entry-points.md +45 -0
- package/dist/knowledge/references/saas.models.audit.trail-config.md +63 -5
- package/dist/knowledge/references/{saas.models.auth.service-provider-client-authentication.md → saas.models.auth.relationship-grantor-authentication.md} +54 -48
- package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +4 -4
- package/dist/knowledge/references/saas.models.chat-identity-link-host.md +38 -0
- package/dist/knowledge/references/saas.models.compliance.ai-use-classification.md +179 -0
- package/dist/knowledge/references/saas.models.compliance.ai-use-posture.md +121 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +42 -82
- package/dist/knowledge/references/saas.models.conversation-threads.md +4 -3
- package/dist/knowledge/references/saas.models.crypto-keys.floors.md +22 -0
- package/dist/knowledge/references/saas.models.crypto-keys.key-management-config.md +130 -0
- package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +27 -0
- package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +403 -0
- package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +84 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +24 -1
- package/dist/knowledge/references/saas.models.engine-capabilities.md +28 -0
- package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +16 -9
- package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +23 -6
- package/dist/knowledge/references/saas.models.external-data-conflict-vocabulary.md +53 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +81 -18
- package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report-config.md +28 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +317 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-content-guardrails.md +150 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +45 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +147 -0
- package/dist/knowledge/references/saas.models.flows-actors.autonomous-agents-vocabulary.md +49 -7
- package/dist/knowledge/references/saas.models.flows-actors.chat-agents-vocabulary.md +26 -0
- package/dist/knowledge/references/saas.models.flows-actors.decision-card-wording.md +284 -0
- package/dist/knowledge/references/saas.models.flows-actors.decision-notice-recorded-cards.md +93 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +62 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +314 -0
- package/dist/knowledge/references/saas.models.flows-actors.operation-approval-pending.md +55 -0
- package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +62 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +6 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +1 -0
- package/dist/knowledge/references/saas.models.flows.run-state.md +49 -0
- package/dist/knowledge/references/saas.models.flows.runnable-model.md +255 -0
- package/dist/knowledge/references/saas.models.frontend-on-demand-capability-contract.md +54 -0
- package/dist/knowledge/references/saas.models.http-api-binding.md +157 -42
- package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +3 -3
- package/dist/knowledge/references/saas.models.http-api-population-filter.md +51 -0
- package/dist/knowledge/references/saas.models.inbound-channels.md +4 -1
- package/dist/knowledge/references/saas.models.inbound-email-domains.md +5 -5
- package/dist/knowledge/references/saas.models.inbound-email.md +2 -2
- package/dist/knowledge/references/saas.models.m2m-webhook-events.md +73 -0
- package/dist/knowledge/references/saas.models.model-cost-summary.md +56 -20
- package/dist/knowledge/references/saas.models.notifications.targets.md +25 -2
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +63 -9
- package/dist/knowledge/references/saas.models.on-demand-provider-capabilities.md +28 -0
- package/dist/knowledge/references/saas.models.organization-agent-policy.md +43 -0
- package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +73 -0
- package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +48 -0
- package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +6 -6
- package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +9 -10
- package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +911 -0
- package/dist/knowledge/references/saas.models.organizations.professional-qualification-kinds.md +46 -0
- package/dist/knowledge/references/saas.models.organizations.professional-qualifications.md +168 -0
- package/dist/knowledge/references/{saas.models.organizations.service-provider-capability-grants.md → saas.models.organizations.relationship-capability-grants.md} +56 -35
- package/dist/knowledge/references/saas.models.organizations.relationship-grantor-controls.md +62 -0
- package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +224 -0
- package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +277 -0
- package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +113 -0
- package/dist/knowledge/references/saas.models.privacy.legal-holds.md +68 -5
- package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +67 -2
- package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +13 -14
- package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +278 -40
- package/dist/knowledge/references/saas.models.provider-capabilities.md +33 -0
- package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +50 -1
- package/dist/knowledge/references/saas.models.providers.capability-activation-policy.md +28 -0
- package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +8 -0
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +37 -0
- package/dist/knowledge/references/saas.models.providers.execute-operation-request.md +25 -0
- package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +1 -1
- package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +13 -1
- package/dist/knowledge/references/saas.models.rate-limit-configuration.md +4 -4
- package/dist/knowledge/references/saas.models.representative-activity.md +65 -0
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +84 -2
- package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +24 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +57 -11
- package/dist/knowledge/references/saas.models.resource-config.operation-base.md +20 -3
- package/dist/knowledge/references/saas.models.resource-config.operation-bulk.md +37 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-chat-command.md +39 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +1 -1
- package/dist/knowledge/references/saas.models.resource-config.operation-required-qualifications.md +30 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +99 -2
- package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +1 -1
- package/dist/knowledge/references/saas.models.resource-config.operation-union.md +0 -1
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +1 -1
- package/dist/knowledge/references/saas.models.resource-config.record-label-fields.md +23 -0
- package/dist/knowledge/references/saas.models.resource-config.request-field-offers.md +104 -0
- package/dist/knowledge/references/saas.models.resource-config.required-features.md +20 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +9 -0
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +25 -3
- package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +25 -0
- package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +2 -1
- package/dist/knowledge/references/saas.models.resource-config.token-generation.md +1 -1
- package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +3 -2
- package/dist/knowledge/references/saas.models.resource-relationship-builder-parameters.md +6 -2
- package/dist/knowledge/references/saas.models.roadmap.phase-horizon.md +31 -0
- package/dist/knowledge/references/saas.models.roles.definition.md +61 -0
- package/dist/knowledge/references/saas.models.roles.organization-defaults.md +97 -0
- package/dist/knowledge/references/saas.models.schema-family-builder.md +17 -4
- package/dist/knowledge/references/saas.models.scope-membership.md +2 -2
- package/dist/knowledge/references/saas.models.system-of-record-capabilities.md +121 -0
- package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +3 -2
- package/dist/knowledge/references/saas.models.systems-of-record.md +36 -1
- package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +7 -3
- package/dist/knowledge/references/saas.models.work-unit-ref.md +17 -2
- package/dist/knowledge/references/saas.public-runtime.contract.md +60 -2
- package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +3 -2
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +13 -0
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +275 -13
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +5 -4
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +9 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +16 -2
- package/dist/knowledge/references/saas.specifications.processor-register.md +10 -1
- package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +111 -2
- package/dist/knowledge/references/saas.specifications.recipient-population.md +46 -0
- package/dist/knowledge/references/saas.specifications.resource-frontend-configuration-aspect.md +7 -0
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +24 -2
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +21 -7
- package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +19 -5
- package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +136 -6
- package/dist/knowledge/references/saas.website.astro.bridge.md +61 -14
- package/dist/knowledge/references/saas.website.astro.head-renderer.md +63 -27
- package/dist/knowledge/references/saas.website.astro.i18n-helper.md +39 -10
- package/dist/knowledge/references/saas.website.astro.label-key-collector.md +12 -11
- package/dist/knowledge/references/saas.website.astro.label-loader.md +41 -9
- package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +14 -1
- package/dist/knowledge/references/saas.website.astro.pick-labels-for-page.md +1 -2
- package/dist/knowledge/references/saas.website.astro.runtime-helper.md +48 -17
- package/dist/knowledge/references/saas.website.astro.site-context.md +30 -8
- package/dist/knowledge/references/saas.website.astro.structured-data-renderer.md +29 -8
- package/dist/knowledge/references/saas.website.blocks.actions.md +91 -0
- package/dist/knowledge/references/saas.website.blocks.band.md +41 -0
- package/dist/knowledge/references/saas.website.blocks.bento.md +70 -0
- package/dist/knowledge/references/saas.website.blocks.card-grid.md +115 -0
- package/dist/knowledge/references/saas.website.blocks.card.md +77 -0
- package/dist/knowledge/references/saas.website.blocks.cta-band.md +94 -0
- package/dist/knowledge/references/saas.website.blocks.define-block.md +123 -0
- package/dist/knowledge/references/saas.website.blocks.definitions.md +132 -0
- package/dist/knowledge/references/saas.website.blocks.faq.md +89 -0
- package/dist/knowledge/references/saas.website.blocks.feature-row.md +109 -0
- package/dist/knowledge/references/saas.website.blocks.hero.md +140 -0
- package/dist/knowledge/references/saas.website.blocks.intro.md +68 -0
- package/dist/knowledge/references/saas.website.blocks.latest-posts.md +104 -0
- package/dist/knowledge/references/saas.website.blocks.marquee.md +76 -0
- package/dist/knowledge/references/saas.website.blocks.pricing.md +395 -0
- package/dist/knowledge/references/saas.website.blocks.product-tour.md +158 -0
- package/dist/knowledge/references/saas.website.blocks.quote-cards.md +64 -0
- package/dist/knowledge/references/saas.website.blocks.roadmap.md +108 -0
- package/dist/knowledge/references/saas.website.blocks.section-slots.md +64 -0
- package/dist/knowledge/references/saas.website.blocks.solution-paths.md +71 -0
- package/dist/knowledge/references/saas.website.blocks.stats.md +183 -0
- package/dist/knowledge/references/saas.website.blocks.steps.md +69 -0
- package/dist/knowledge/references/saas.website.blocks.stylesheet.md +68 -0
- package/dist/knowledge/references/saas.website.blocks.tables.md +153 -0
- package/dist/knowledge/references/saas.website.blocks.vocabulary.md +227 -0
- package/dist/knowledge/references/saas.website.blog.bridge.md +102 -53
- package/dist/knowledge/references/saas.website.blog.collection-config.md +76 -24
- package/dist/knowledge/references/saas.website.blog.cover-resolver.md +93 -0
- package/dist/knowledge/references/saas.website.blog.frontmatter.md +104 -7
- package/dist/knowledge/references/saas.website.blog.head-renderer.md +37 -19
- package/dist/knowledge/references/saas.website.blog.index-builder.md +63 -0
- package/dist/knowledge/references/saas.website.blog.index.md +43 -0
- package/dist/knowledge/references/saas.website.blog.post-cover.md +38 -0
- package/dist/knowledge/references/saas.website.blog.post-renderer.md +113 -85
- package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +181 -0
- package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +26 -0
- package/dist/knowledge/references/saas.website.blog.vocabulary-labels.md +113 -0
- package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +2 -1
- package/dist/knowledge/references/saas.website.config.site-context-loader.md +24 -1
- package/dist/knowledge/references/saas.website.consent.banner.md +1 -1
- package/dist/knowledge/references/saas.website.consent.context.md +1 -1
- package/dist/knowledge/references/saas.website.design-tokens.bundle.md +28 -6
- package/dist/knowledge/references/saas.website.design-tokens.colors.md +7 -6
- package/dist/knowledge/references/saas.website.design-tokens.compose-function.md +35 -0
- package/dist/knowledge/references/saas.website.design-tokens.compose.md +76 -0
- package/dist/knowledge/references/saas.website.design-tokens.personality-derivation.md +22 -0
- package/dist/knowledge/references/saas.website.design-tokens.personality-lexicon.md +31 -0
- package/dist/knowledge/references/saas.website.design-tokens.personality.md +82 -0
- package/dist/knowledge/references/saas.website.design-tokens.product.md +122 -0
- package/dist/knowledge/references/saas.website.design-tokens.radius.md +12 -1
- package/dist/knowledge/references/saas.website.design-tokens.readers.md +58 -0
- package/dist/knowledge/references/saas.website.design-tokens.spacing.md +61 -0
- package/dist/knowledge/references/saas.website.design-tokens.surface-depth.md +60 -0
- package/dist/knowledge/references/saas.website.design-tokens.tones.md +75 -0
- package/dist/knowledge/references/saas.website.design-tokens.typography.md +115 -0
- package/dist/knowledge/references/saas.website.factories.define-page-manifest.md +23 -21
- package/dist/knowledge/references/saas.website.factories.define-section.md +36 -38
- package/dist/knowledge/references/saas.website.format.publication-date.md +26 -0
- package/dist/knowledge/references/saas.website.label-keys.compose-helper.md +1 -1
- package/dist/knowledge/references/saas.website.label-keys.format.md +2 -2
- package/dist/knowledge/references/saas.website.label-pack.validator.md +7 -8
- package/dist/knowledge/references/saas.website.labels.section-labels.md +34 -0
- package/dist/knowledge/references/saas.website.legal.public-document-links.md +91 -0
- package/dist/knowledge/references/saas.website.locale-switcher.label-keys.md +35 -0
- package/dist/knowledge/references/saas.website.menu.icons.md +123 -0
- package/dist/knowledge/references/saas.website.menu.label-keys.md +112 -0
- package/dist/knowledge/references/saas.website.menu.schema.md +92 -0
- package/dist/knowledge/references/saas.website.menu.vocabulary.md +79 -0
- package/dist/knowledge/references/saas.website.motion.demo-player.md +105 -0
- package/dist/knowledge/references/saas.website.motion.demo-scenario.md +460 -0
- package/dist/knowledge/references/saas.website.motion.demo.md +324 -0
- package/dist/knowledge/references/saas.website.motion.element-attributes.md +115 -0
- package/dist/knowledge/references/saas.website.motion.reveal-renditions.md +67 -0
- package/dist/knowledge/references/saas.website.motion.stylesheet.md +82 -0
- package/dist/knowledge/references/saas.website.motion.tempo-table.md +99 -0
- package/dist/knowledge/references/saas.website.motion.tokens.md +46 -0
- package/dist/knowledge/references/saas.website.motion.vocabulary.md +85 -0
- package/dist/knowledge/references/saas.website.page-layout.component.md +34 -8
- package/dist/knowledge/references/saas.website.page-manifest.meta-label-keys.md +4 -4
- package/dist/knowledge/references/saas.website.page-manifest.route-path.md +1 -1
- package/dist/knowledge/references/saas.website.page-manifest.schema.md +25 -29
- package/dist/knowledge/references/saas.website.page-manifest.seo.md +1 -1
- package/dist/knowledge/references/saas.website.page-navigation.md +44 -0
- package/dist/knowledge/references/saas.website.page.context.md +9 -2
- package/dist/knowledge/references/saas.website.primitives.button.md +6 -6
- package/dist/knowledge/references/saas.website.primitives.heading.md +17 -18
- package/dist/knowledge/references/saas.website.primitives.image.md +18 -15
- package/dist/knowledge/references/saas.website.primitives.internal-button.md +11 -12
- package/dist/knowledge/references/saas.website.primitives.internal-link.md +11 -35
- package/dist/knowledge/references/saas.website.primitives.link.md +22 -11
- package/dist/knowledge/references/saas.website.primitives.text.md +10 -8
- package/dist/knowledge/references/saas.website.product.atoms.md +366 -0
- package/dist/knowledge/references/saas.website.product.figures.md +320 -0
- package/dist/knowledge/references/saas.website.product.hooks.md +278 -0
- package/dist/knowledge/references/saas.website.product.panels.md +324 -0
- package/dist/knowledge/references/saas.website.product.stylesheet.md +1086 -0
- package/dist/knowledge/references/saas.website.refs.section.md +2 -2
- package/dist/knowledge/references/saas.website.root-config.schema.md +34 -17
- package/dist/knowledge/references/saas.website.root-config.seo.md +2 -1
- package/dist/knowledge/references/saas.website.routing.link-target.md +70 -0
- package/dist/knowledge/references/saas.website.routing.localized-path.md +15 -8
- package/dist/knowledge/references/saas.website.runtime.context.md +51 -17
- package/dist/knowledge/references/saas.website.section.component.md +21 -19
- package/dist/knowledge/references/saas.website.sections.category-enum.md +21 -2
- package/dist/knowledge/references/saas.website.sections.definition-schema.md +47 -39
- package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +2 -0
- package/dist/knowledge/references/saas.website.site-footer.menu.md +47 -0
- package/dist/knowledge/references/saas.website.site-header.component.md +100 -0
- package/dist/knowledge/references/saas.website.site-header.scroll-behavior.md +26 -0
- package/dist/knowledge/references/saas.website.stacking.md +86 -0
- package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +162 -0
- package/dist/knowledge/references/saas.website.use-blog-index.hook.md +27 -0
- package/dist/knowledge/references/saas.website.use-label.hook.md +6 -4
- package/dist/knowledge/references/service-method.config.md +270 -0
- package/dist/knowledge/references/website-plan.config.md +561 -23
- package/dist/knowledge/references/website-plan.menu-placement.md +118 -0
- package/dist/knowledge/references/website-plan.page-kind-essentials.md +42 -0
- package/dist/knowledge/references/website-plan.page-routes.md +39 -0
- package/dist/knowledge/references/workers.node.worker-init-contract.md +4 -2
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +86 -9
- package/dist/knowledge/references/zod.decorators.chrome-modes.md +92 -0
- package/dist/knowledge/references/zod.decorators.data-categories.md +101 -11
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +82 -6
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +23 -1
- package/dist/knowledge/references/zod.decorators.document-sequence.md +65 -0
- package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +41 -7
- package/dist/knowledge/references/zod.decorators.file-schema.md +6 -5
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +25 -9
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +15 -3
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +5 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +50 -1
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +44 -5
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +130 -9
- package/dist/knowledge/references/zod.factories.bigdecimal.md +17 -7
- package/dist/knowledge/references/zod.factories.code.md +18 -8
- package/dist/knowledge/references/zod.factories.duration.md +23 -13
- package/dist/knowledge/references/zod.factories.money.md +24 -14
- package/dist/knowledge/references/zod.factories.phone.md +23 -14
- package/dist/knowledge/references/zod.factories.range.md +5 -1
- package/dist/knowledge/registries/assurance-authority-bases.json +3 -3
- package/dist/knowledge/registries/framework-topics.json +2854 -246
- package/dist/knowledge/registries/playbooks.json +57 -36
- package/dist/knowledge/registries/source-tags.json +8863 -4569
- package/dist/knowledge/rules/database-migration-obligation.md +11 -5
- package/dist/knowledge/rules/live-context-door.md +1 -1
- package/dist/knowledge/skills/INDEX.md +63 -34
- package/dist/knowledge/skills/agent-work-review/SKILL.md +86 -23
- package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +203 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +2 -2
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-decision-contents-api.md +79 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +4 -4
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +6 -5
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +22 -4
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +15 -3
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +20 -3
- package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +16 -9
- package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +24 -7
- package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +341 -0
- package/dist/knowledge/skills/ai-use-declaration/SKILL.md +192 -0
- package/dist/knowledge/skills/ai-use-declaration/references/choosing-the-domain-and-class.md +73 -0
- package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-classification-api.md +194 -0
- package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-posture-api.md +136 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +16 -3
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +41 -12
- package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +34 -0
- package/dist/knowledge/skills/application-roles-authoring/SKILL.md +158 -0
- package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +169 -0
- package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +63 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +130 -4
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +90 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-own-rows-declaration-api.md +59 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +6 -6
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +79 -2
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +291 -10
- package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +42 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +3 -2
- package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +223 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +20 -3
- package/dist/knowledge/skills/backend-custom-operation/references/framework-target-authority-api.md +61 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +368 -1
- package/dist/knowledge/skills/blueprint-authoring/SKILL.md +189 -0
- package/dist/knowledge/skills/blueprint-authoring/references/blueprint-content-kinds.md +29 -0
- package/dist/knowledge/skills/blueprint-authoring/references/framework-blueprint-definition-api.md +490 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +132 -2
- package/dist/knowledge/skills/brand-logo-authoring/references/brand-authoring-decisions.md +15 -3
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +26 -8
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-style-word-lexicon-api.md +126 -0
- package/dist/knowledge/skills/brand-name-screening/SKILL.md +33 -9
- package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +78 -6
- package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +30 -8
- package/dist/knowledge/skills/chat-agent-conversations/SKILL.md +163 -0
- package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +295 -0
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +8 -6
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +136 -34
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +4 -3
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +13 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +34 -7
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +10 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +37 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +178 -4
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +46 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +485 -61
- package/dist/knowledge/skills/config-app-shell/SKILL.md +101 -19
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +20 -18
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +7 -3
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-hosted-components-api.md +13 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +20 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +472 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +82 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-shell-layout-api.md +528 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +271 -166
- package/dist/knowledge/skills/config-design-system/references/design-system-file.md +5 -1
- package/dist/knowledge/skills/config-design-system/references/framework-focus-indicator-api.md +182 -0
- package/dist/knowledge/skills/config-design-system/references/framework-palette-contrast-api.md +195 -0
- package/dist/knowledge/skills/config-design-system/references/framework-palette-derivation-api.md +108 -0
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +37 -0
- package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +235 -0
- package/dist/knowledge/skills/config-design-system/references/theme-design-principles.md +202 -0
- package/dist/knowledge/skills/config-navigation/SKILL.md +14 -3
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +16 -5
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +1 -1
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +7 -1
- package/dist/knowledge/skills/config-saas/SKILL.md +27 -11
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +62 -4
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +80 -7
- package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +314 -0
- package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +29 -1
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +8 -0
- package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +1 -2
- package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +1182 -0
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +61 -0
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +56 -11
- package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +22 -0
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +106 -14
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +11 -4
- package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +9 -10
- package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +6 -4
- package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +155 -92
- package/dist/knowledge/skills/configure-billing/SKILL.md +32 -4
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +10 -0
- package/dist/knowledge/skills/configure-billing/references/framework-metered-usage-recording-api.md +109 -0
- package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +18 -2
- package/dist/knowledge/skills/email-add-template/SKILL.md +72 -9
- package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +1 -1
- package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +135 -0
- package/dist/knowledge/skills/email-add-template/references/framework-email-template-api.md +134 -0
- package/dist/knowledge/skills/email-add-template/references/framework-operation-email-template-ref-api.md +99 -0
- package/dist/knowledge/skills/engine-component-registration/SKILL.md +6 -1
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +21 -8
- package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +28 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +71 -14
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +95 -13
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +9 -1
- package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +98 -9
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +44 -16
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +160 -23
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +10 -3
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +14 -2
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +291 -22
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +70 -14
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +451 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +406 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +201 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +172 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-ask-person-tool-api.md +121 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +7 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +63 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +324 -7
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +95 -6
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +255 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-present-records-tool-api.md +150 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-retrieval-tool-api.md +251 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +112 -16
- package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +339 -0
- package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +264 -0
- package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +133 -0
- package/dist/knowledge/skills/flows-actors-declared-flow/references/step-kinds.md +16 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +109 -9
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +45 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +14 -3
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +13 -6
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +16 -7
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +29 -18
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +144 -14
- package/dist/knowledge/skills/human-decision-notices/SKILL.md +150 -0
- package/dist/knowledge/skills/human-decision-notices/references/framework-decision-card-wording-api.md +292 -0
- package/dist/knowledge/skills/human-decision-notices/references/framework-decision-notice-handler-api.md +340 -0
- package/dist/knowledge/skills/i18n-label-generation/SKILL.md +17 -1
- package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +19 -5
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +14 -3
- package/dist/knowledge/skills/inbound-channels/SKILL.md +66 -8
- package/dist/knowledge/skills/inbound-channels/references/email-channel.md +34 -1
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +78 -6
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +8 -8
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +434 -6
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-pipelines-api.md +73 -0
- package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +1 -1
- package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +24 -13
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +113 -3
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +9 -1
- package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +2 -0
- package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +294 -0
- package/dist/knowledge/skills/layout-2d-adoption/SKILL.md +158 -0
- package/dist/knowledge/skills/layout-2d-adoption/references/choosing-a-layout.md +43 -0
- package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +167 -0
- package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-registration-api.md +101 -0
- package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-settings-api.md +59 -0
- package/dist/knowledge/skills/layout-2d-adoption/references/framework-shell-motion-api.md +415 -0
- package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +1 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +65 -32
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +14 -36
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +7 -3
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +6 -1
- package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +4 -2
- package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +10 -2
- package/dist/knowledge/skills/market-alternatives/SKILL.md +10 -2
- package/dist/knowledge/skills/market-authoring-overview/SKILL.md +10 -2
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +14 -1
- package/dist/knowledge/skills/market-category/SKILL.md +21 -7
- package/dist/knowledge/skills/market-channels/SKILL.md +6 -1
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +20 -3
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +10 -1
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +23 -12
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +13 -7
- package/dist/knowledge/skills/market-icp/SKILL.md +10 -2
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +6 -1
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +6 -1
- package/dist/knowledge/skills/market-persona/SKILL.md +14 -3
- package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +6 -1
- package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +10 -2
- package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +6 -1
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +14 -3
- package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +6 -1
- package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +1 -1
- package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +2 -2
- package/dist/knowledge/skills/model-cost-attribution/SKILL.md +40 -10
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +57 -2
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +57 -21
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +7 -3
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +176 -4
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +7 -1
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +9 -0
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +81 -1
- package/dist/knowledge/skills/module-relationships/SKILL.md +81 -31
- package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +8 -4
- package/dist/knowledge/skills/organization-relationships/SKILL.md +668 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +1233 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-capability-grants-api.md +243 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +284 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +521 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +162 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +145 -0
- package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +4 -2
- package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +5 -3
- package/dist/knowledge/skills/professional-qualifications/SKILL.md +173 -0
- package/dist/knowledge/skills/professional-qualifications/references/choosing-who-may-decide.md +53 -0
- package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +67 -0
- package/dist/knowledge/skills/professional-qualifications/references/framework-operation-required-qualifications-api.md +39 -0
- package/dist/knowledge/skills/professional-qualifications/references/framework-professional-qualifications-api.md +223 -0
- package/dist/knowledge/skills/provider-address-lookup/SKILL.md +15 -4
- package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +3 -3
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +138 -4
- package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +32 -28
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-augmentation-api.md +16 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +6 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +634 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +70 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +61 -2
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-subject-erasure-effect-api.md +222 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +15 -6
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +9 -2
- package/dist/knowledge/skills/provider-frontend-module/SKILL.md +47 -5
- package/dist/knowledge/skills/provider-frontend-module/references/framework-on-demand-capabilities-api.md +306 -0
- package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +11 -3
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +37 -14
- package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +56 -18
- package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +1 -1
- package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +143 -25
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +6 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +9 -6
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +256 -1
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +81 -37
- package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +27 -13
- package/dist/knowledge/skills/resource-add-field/SKILL.md +10 -2
- package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +32 -12
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +167 -61
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +63 -6
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +84 -2
- package/dist/knowledge/skills/resource-chat-commands/SKILL.md +137 -0
- package/dist/knowledge/skills/resource-chat-commands/references/framework-resource-chat-command-contract.md +72 -0
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +131 -7
- package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +4 -4
- package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +17 -8
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +25 -4
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +323 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +23 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +159 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +162 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-request-field-offers-api.md +168 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +20 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +135 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +3 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +221 -23
- package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +108 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +242 -107
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +202 -17
- package/dist/knowledge/skills/resource-config-wiring/references/framework-webhook-events-api.md +116 -0
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +10 -2
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +123 -56
- package/dist/knowledge/skills/resource-external-data/SKILL.md +280 -64
- package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +335 -0
- package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +18 -6
- package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +73 -14
- package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +6 -0
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +81 -18
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +238 -49
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +111 -11
- package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +145 -0
- package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +30 -4
- package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +21 -9
- package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +61 -14
- package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +18 -2
- package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +3 -1
- package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +39 -13
- package/dist/knowledge/skills/resource-external-data/references/remote-references.md +17 -7
- package/dist/knowledge/skills/resource-external-data/references/requested-keys.md +104 -0
- package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +1 -1
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +17 -4
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +2 -2
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +1 -1
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +6 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +31 -1
- package/dist/knowledge/skills/resource-retention-binding/SKILL.md +8 -2
- package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +68 -5
- package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +25 -0
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +39 -9
- package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +23 -7
- package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +571 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +358 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +2 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +87 -6
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +19 -22
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +127 -12
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +17 -4
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +50 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +44 -5
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +119 -64
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +2 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +216 -18
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +6 -0
- package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +153 -0
- package/dist/knowledge/skills/resource-status-lifecycle/references/commercial-documents.md +46 -0
- package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +198 -0
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +185 -80
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +159 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +120 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +41 -7
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-field-tiles-api.md +114 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +257 -65
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +25 -9
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +15 -3
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +151 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +144 -57
- package/dist/knowledge/skills/resource-ui-behavior/references/record-page-anatomy.md +131 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +57 -31
- package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +56 -0
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +155 -40
- package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +67 -0
- package/dist/knowledge/skills/seeding-authoring/references/data-seeding-mode-picker.md +16 -1
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +148 -4
- package/dist/knowledge/skills/seeding-authoring/references/seed-row-overlay.md +22 -0
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +15 -8
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +3 -0
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +42 -11
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +183 -31
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +64 -2
- package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +5 -4
- package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +5 -4
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +6 -1
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +9 -0
- package/dist/knowledge/skills/spec-component-update/SKILL.md +10 -2
- package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +17 -9
- package/dist/knowledge/skills/spec-family-update/SKILL.md +71 -66
- package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +1 -1
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +30 -10
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +71 -14
- package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +28 -0
- package/dist/knowledge/skills/spec-update-after-change/SKILL.md +22 -5
- package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +19 -5
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +20 -6
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +20 -3
- package/dist/knowledge/skills/views-add-custom-view/references/framework-focus-indicator-api.md +145 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +13 -3
- package/dist/knowledge/skills/views-app-level/references/application-home.md +56 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +226 -37
- package/dist/knowledge/skills/views-chart-authoring/references/framework-chart-view-contracts-api.md +13 -0
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +33 -9
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +12 -3
- package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +17 -3
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +93 -27
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +264 -78
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +1068 -192
- package/dist/knowledge/skills/website-building-blocks/SKILL.md +337 -0
- package/dist/knowledge/skills/website-building-blocks/references/framework-website-blocks-api.md +3050 -0
- package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +627 -0
- package/dist/knowledge/skills/website-building-blocks/references/framework-website-product-kit-api.md +3309 -0
- package/dist/knowledge/skills/website-building-blocks/references/website-visual-quality-rubric.md +75 -0
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +46 -19
- package/dist/knowledge/skills/website-bundle-discipline/references/example-website-button-override.md +8 -12
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +18 -5
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +97 -29
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +77 -66
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +71 -24
- package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +5 -1
- package/dist/knowledge/skills/website-label-pack/SKILL.md +24 -17
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +116 -76
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +43 -14
- package/dist/knowledge/skills/website-motion-design/SKILL.md +277 -0
- package/dist/knowledge/skills/website-motion-design/references/framework-motion-api.md +1562 -0
- package/dist/knowledge/skills/website-motion-design/references/industry-practice.md +28 -0
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +266 -371
- package/dist/knowledge/skills/website-navigation-authoring/references/framework-menu-api.md +712 -0
- package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +120 -0
- package/dist/knowledge/skills/website-navigation-authoring/references/menu-keys-and-styling.md +151 -0
- package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +131 -329
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +170 -66
- package/dist/knowledge/skills/website-page-authoring/references/framework-page-kinds-api.md +982 -0
- package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +27 -3
- package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +19 -0
- package/dist/knowledge/skills/website-page-authoring/references/page-kinds.md +118 -0
- package/dist/knowledge/skills/website-page-variants/SKILL.md +70 -69
- package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +54 -29
- package/dist/knowledge/skills/website-section-comparison/SKILL.md +1171 -0
- package/dist/knowledge/skills/website-section-comparison/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-comparison/references/framework-website-tables-api.md +487 -0
- package/dist/knowledge/skills/website-section-contact/SKILL.md +408 -185
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +197 -119
- package/dist/knowledge/skills/website-section-cta/SKILL.md +398 -234
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +197 -119
- package/dist/knowledge/skills/website-section-faq/SKILL.md +564 -300
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +197 -119
- package/dist/knowledge/skills/website-section-faq/references/framework-website-faq-api.md +489 -0
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +650 -272
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +197 -119
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +577 -261
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +197 -119
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +532 -233
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +197 -119
- package/dist/knowledge/skills/website-section-hero/SKILL.md +606 -330
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +198 -120
- package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1150 -0
- package/dist/knowledge/skills/website-section-how-it-works/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-how-it-works/references/framework-website-steps-api.md +337 -0
- package/dist/knowledge/skills/website-section-integrations/SKILL.md +974 -0
- package/dist/knowledge/skills/website-section-integrations/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-integrations/references/framework-website-marquee-api.md +825 -0
- package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +928 -0
- package/dist/knowledge/skills/website-section-latest-posts/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-latest-posts/references/framework-website-latest-posts-api.md +465 -0
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +552 -376
- package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +77 -0
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +197 -119
- package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +2 -1
- package/dist/knowledge/skills/website-section-pricing/references/framework-website-pricing-api.md +670 -0
- package/dist/knowledge/skills/website-section-problem/SKILL.md +1150 -0
- package/dist/knowledge/skills/website-section-problem/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-problem/references/framework-website-card-grid-api.md +664 -0
- package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1322 -0
- package/dist/knowledge/skills/website-section-product-showcase/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-card-grid-api.md +533 -0
- package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-product-tour-api.md +917 -0
- package/dist/knowledge/skills/website-section-roadmap/SKILL.md +1133 -0
- package/dist/knowledge/skills/website-section-roadmap/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-roadmap/references/framework-website-roadmap-api.md +475 -0
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +743 -309
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +197 -119
- package/dist/knowledge/skills/website-section-social-proof/references/framework-website-quote-cards-api.md +623 -0
- package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +1057 -0
- package/dist/knowledge/skills/website-section-solution-paths/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-solution-paths/references/framework-website-solution-paths-api.md +477 -0
- package/dist/knowledge/skills/website-section-stats/SKILL.md +1086 -0
- package/dist/knowledge/skills/website-section-stats/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-stats/references/framework-website-stats-api.md +517 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +198 -70
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +575 -57
- package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +17 -2
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +8 -95
- package/dist/knowledge/skills/website-theme-authoring/SKILL.md +226 -0
- package/dist/knowledge/skills/website-theme-authoring/references/framework-website-theme-api.md +893 -0
- package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +4 -2
- package/dist/knowledge/topic-index.json +17305 -8263
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/knowledge/references/example.organizations.serves-as-provider.md +0 -12
- package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +0 -121
- package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +0 -49
- package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +0 -567
- package/dist/knowledge/references/saas.website.root-config.navigation.md +0 -37
- package/dist/knowledge/skills/service-provider-relationships/SKILL.md +0 -455
- package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +0 -270
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +0 -129
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +0 -161
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +0 -224
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +0 -576
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "bottom_up.conception",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.4",
|
|
4
4
|
"phase": "bottom_up",
|
|
5
|
-
"intent": "Drive the CONCEPTION of the application as one lane: the domain plan from the requirements and the market, the expert personas that staff the panels, the capability composition the application needs, the foundation composed from the plan and that composition, the surface plans for whatever the composition says this application presents — its experience, its website, its documentation — and the placement plan the panel decides — ending on one decision: the conception is accepted, or returned to the domain plan. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. Select what is MISSING from the accepted truth shown to you. A child already on record whose inputs have not changed since it landed is not offered at all; every option is marked FIRST RUN, or REFRESH with the input that moved. The foundation
|
|
5
|
+
"intent": "Drive the CONCEPTION of the application as one lane: the domain plan from the requirements and the market, the expert personas that staff the panels, the capability composition the application needs, the foundation composed from the plan and that composition, the surface plans for whatever the composition says this application presents — its experience, its website, its documentation — and the placement plan the panel decides — ending on one decision: the conception is accepted, or returned to the domain plan. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. Select what is MISSING from the accepted truth shown to you. A child already on record whose inputs have not changed since it landed is not offered at all; every option is marked FIRST RUN, or REFRESH with the input that moved. The foundation is a runner-owned step that lands no family: run it ONCE, when its inputs are on record, and do not spend a round on it again — the round history shows it ran. The expert personas are runner-owned too but land the panels' charters: they are offered only while a role can be staffed now, so run them whenever they are offered; a second run staffs a role that waited on a family which has since landed. Run independent children in the same round. STOP when the placement plan is on record, the EXPERIENCE plan and the INTEGRATION plan are on record (an integration plan that decides nothing runs in the background is a plan on record), AND every surface the capability composition decided NEEDED (a website, a documentation portal) has its plan on record: the placement plan is this lane's closing decision, but it needs only the domain plan, so it can land before a surface plan — and a surface decided and never planned is one the build decomposition emits no task for. The experience plan is not a composition decision because every application with a frontend has an experience: without it the build has no home, no design system from the brand, no navigation decision and no application views (#2494, both creation runs that closed this lane without it). The integration plan is the same kind of decision: without it the build emits no worker, minion, provider binding or inbound channel, and nothing says whether that was decided. A child whose interview the creator has not answered, or whose run suspended on a clarification, is not offered; run everything else and stop when nothing eligible advances the conception.",
|
|
6
6
|
"preconditions": [
|
|
7
7
|
{
|
|
8
8
|
"kind": "artifact_valid",
|
|
@@ -61,12 +61,20 @@
|
|
|
61
61
|
{
|
|
62
62
|
"family": "documentation-plan",
|
|
63
63
|
"render": "map"
|
|
64
|
+
},
|
|
65
|
+
{
|
|
66
|
+
"family": "experience-plan",
|
|
67
|
+
"render": "map"
|
|
68
|
+
},
|
|
69
|
+
{
|
|
70
|
+
"family": "integration-plan",
|
|
71
|
+
"render": "map"
|
|
64
72
|
}
|
|
65
73
|
],
|
|
66
74
|
"outputs": [],
|
|
67
75
|
"stepOutputs": [],
|
|
68
76
|
"method": {
|
|
69
|
-
"guidance": "# The Conception 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 steps that CONCEIVE the\napplication's structure — the domain plan, the panels' staffing, the foundation, the\nplacement plan — and it ends on the placement plan, which is the lane's closing decision.\n\n## The children, and why the order is not written here\n\n- **`bottom_up.domain-plan`** — modules, resources and relationships, from the\n requirements and the market. Asks the creator one question (tenancy) and may suspend\n mid-run on a clarification.\n- **`top_down.expert-personas`** — derives and accepts the expert charters the panels\n convene. Runner-owned
|
|
77
|
+
"guidance": "# The Conception 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 steps that CONCEIVE the\napplication's structure — the domain plan, the panels' staffing, the foundation, the\nplacement plan — and it ends on the placement plan, which is the lane's closing decision.\n\n## The children, and why the order is not written here\n\n- **`bottom_up.domain-plan`** — modules, resources and relationships, from the\n requirements and the market. Asks the creator one question (tenancy) and may suspend\n mid-run on a clarification.\n- **`top_down.expert-personas`** — derives and accepts the expert charters the panels\n convene. Runner-owned; lands the charters (`expert-personas`), never re-derives a\n committed charter, reports a role whose inputs have not landed as waiting, and is\n offered again once such a role can be staffed.\n- **`bottom_up.capability-composition`** — which composition scenarios the\n application needs (a website, a technical-doc portal, workers, minions). Its record\n is what the foundation applies.\n- **`bottom_up.foundation`** — composes the application from the domain plan: the\n configuration, the module and resource slices, the environments. Runner-owned,\n idempotent (a byte-identical target is a skip; a collision refuses), asks the creator\n three questions.\n- **`bottom_up.experience-plan`**, **`bottom_up.website-plan`**,\n **`bottom_up.documentation-plan`** — what each surface the composition declared\n CONTAINS. Conception rather than build: the decomposer reads all three, so a surface\n planned after decomposition is one the build plan has no task for. An application that\n declared no website simply has no website plan, and nothing waits for one.\n- **`bottom_up.placement-plan`** — where every module lands in the application shell,\n decided by a panel (an information architect and a design-system guardian) over three\n candidates.\n\nNothing above is a sequence. Each child declares what it needs, and the runtime\nre-computes what may run after every round. The plan needs the requirements and the\nmarket; the personas need the vision and the market; the foundation and the placement\nneed the plan. Re-run the lane on an application whose plan exists and the first round\nalready offers the three that follow it.\n\n## Selecting the next children\n\n- **Missing beats present.** A plan or a placement already on record whose inputs\n have not changed since it landed is not offered at all. Every option is marked\n FIRST RUN, or REFRESH with the input that moved.\n- **The foundation runs once.** It lands nothing the runtime marks delivered, so it\n stays eligible; the round history is the record that it ran. Do not spend a round on\n it a second time.\n- **The personas run when they are offered.** They are offered (FIRST RUN or REFRESH)\n only while a role can be staffed now, and marked current otherwise. A second run is\n how a role that waited on the brand or the business model gets its charter once that\n family has landed.\n- **Independent children share a round.** The personas and the foundation do not wait on\n each other and can run beside each other.\n- **A child waiting on the creator is not offered** — an unanswered interview, or a\n suspended clarification. Run everything else, and stop when nothing eligible advances\n the conception.\n\n## Composing an objective for a child\n\nFor the domain plan, name the requirements the plan must route and the market ICPs it\nserves. For a re-derivation, name what placement or the build reported the plan could\nnot route — that is the whole objective. For placement, name the modules the plan\ndeclares and the audiences that reach them.\n\n## When the build sends the application back\n\nThe root re-opens this lane when the build lane's decomposer finds the conception unbuildable\n(`conception-buildable` GAP, #1638). The round history names the criterion, and the objective you\nare given carries the decomposer's reason. Revise the leaf that owns the faulted element, which is\nusually the domain plan: a module, resource or relationship no build target can express, or a\nreference another family makes to something the plan does not declare. A composition surface no\nplan realises belongs to the surface plan it names. Do not re-derive the whole conception: the\nleaves the fault does not touch are still right, and re-deriving them makes the build re-plan work\nthat was sound.\n\n## When to stop\n\nStop when the placement plan is on record AND every surface the capability composition\ndecided is planned: the placement plan is the decision this lane ends on, but it depends\nonly on the domain plan, so it can land while the composition's surfaces are still\nunplanned. A website or documentation portal the composition marks NEEDED, with no\nwebsite plan or documentation plan on record, is a surface the build decomposition will\nemit no task for — and nothing downstream says so. Offer its plan before stopping. The\ncoherence report names the gap as `composition-surface-not-planned`.\n\nStop also when nothing eligible advances the conception — the plan suspended on a\nclarification, or an interview is unanswered — and say which.\n\n## What the creator reviews\n\nThe domain plan and the placement plan, exactly as each leaf's own review guide says;\nthe composed application in the working tree, through `git status`; and the accepted\ncharters. The decision this lane ends on: the conception is accepted, or returned to\nthe domain plan with what could not be routed.\n",
|
|
70
78
|
"skillRefs": [],
|
|
71
79
|
"skillBodyRefs": [],
|
|
72
80
|
"contextSources": [],
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"aggregationPolicyRef":"application-creation:aggregation/worst-domain-plan-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/domain-plan-boundary-discipline","criterionVersion":
|
|
1
|
+
{"aggregationPolicyRef":"application-creation:aggregation/worst-domain-plan-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/domain-plan-boundary-discipline","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-boundary-discipline","requirementVersion":1}],"instruction":"Determine whether the output remains at planning depth: modules, resource inventories, relationship intents and resource lifecycles (states, transitions, conversions, locked and final states) only. Treat schema fields, concrete foreign-key placement or generated implementation code as scope leakage.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The output is usable but contains limited premature implementation detail.","GAP":"The output materially crosses into schema, foreign-key or implementation authoring.","INDETERMINATE":"The staged evidence cannot establish the output depth boundary.","PASS":"The output remains within the declared planning-depth boundary."}},{"criterionRef":"application-creation:criterion/domain-plan-engine-concern-discipline","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-engine-concern-discipline","requirementVersion":1}],"instruction":"Determine whether any module or resource stands in for a concern the engine already provides or that is not data a user maintains: roles, permissions or role assignments (the engine roles); members, invitations or teams; an audit history; processing purposes, legal bases, compliance or country declarations typed in by users (a governed document); a next action, stage or status copied from other records (derived, shown in a view). Such a requirement belongs in engineRealizedRequirements, or is derived. A product resource that merely mentions one of these words (an invoice with a status, a job with a stage the user sets as part of the work) is not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A resource may duplicate an engine concern or derived state, but the definition context leaves room for a genuine product reading; name it and the reading.","GAP":"A module or resource models roles or permissions, a compliance or country declaration users type in, or state copied from other records, while the requirement it serves is the engine's or derivable.","INDETERMINATE":"The staged evidence cannot establish what the resources hold.","PASS":"No module or resource models an engine-provided concern, a disclaimer, or state derived from other records."}},{"criterionRef":"application-creation:criterion/domain-plan-feature-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-feature-coverage","requirementVersion":1}],"instruction":"Determine whether every feature draft and benefit-delivering feature is realizable by the proposed module capabilities and resource inventories. Do not infer a home from naming similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All features have homes, but one or more mappings are weak or insufficiently explained.","GAP":"At least one feature or benefit-delivering capability has no resolvable domain home.","INDETERMINATE":"The staged evidence cannot establish complete feature coverage.","PASS":"Every feature and benefit-delivering capability has a resolvable domain home."}},{"criterionRef":"application-creation:criterion/domain-plan-inventory-plausibility","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-inventory-plausibility","requirementVersion":1}],"instruction":"Assess whether main resources form each module semantic center, supporting resources remain genuinely supporting, and ownership boundaries are plausible. Deterministic uniqueness has already passed and must not be reinterpreted.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The inventories are usable but one or more main/supporting classifications are questionable.","GAP":"At least one inventory materially contradicts its declared module capability.","INDETERMINATE":"The staged evidence cannot establish plausible module inventories.","PASS":"Each module inventory has a plausible semantic center and supporting boundary."}},{"criterionRef":"application-creation:criterion/domain-plan-lifecycle-coverage","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-lifecycle-coverage","requirementVersion":1}],"instruction":"Determine whether every resource a current-horizon requirement describes moving through states (sent, accepted, issued, paid, approved, closed) has a lifecycle whose transitions carry the requirement's verbs, whose conversions name the resource they create when one record creates another (\"an accepted quote creates a job\"), and whose locked and final states together cover what the requirements say must stop changing (locked when the record still moves on, final when nothing moves it again). A state change expressed only as a relationship, a status the requirements never move, or a lifecycle for a value derived from other records is not coverage.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Each such record has a lifecycle, but a verb, a conversion target, or a locked or final state the requirements imply is missing from it.","GAP":"A requirement moves a record through states and the plan has no lifecycle for it, or expresses the move only as a relationship.","INDETERMINATE":"The staged evidence cannot establish which requirements move records through states.","PASS":"No requirement moves a record through states, or every such record has a lifecycle carrying the requirement's verbs, its conversions and its final states."}},{"criterionRef":"application-creation:criterion/domain-plan-module-justification","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-module-justification","requirementVersion":1}],"instruction":"Determine whether every proposed module is justified by accepted requirements or features and represents one coherent business capability. Flag speculative or mixed-purpose modules.","schemaVersion":1,"verdictGuidance":{"CONCERN":"One or more modules are weakly justified or combine boundaries that should be reconsidered.","GAP":"At least one module is speculative or materially incoherent with the definition set.","INDETERMINATE":"The staged evidence cannot establish why every module exists.","PASS":"Every proposed module is justified and capability-coherent."}},{"criterionRef":"application-creation:criterion/domain-plan-relationship-integrity","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-relationship-integrity","requirementVersion":1}],"instruction":"Assess whether the typed relationship intents are semantically necessary and coherent with the inventoried resources, conceptual cardinality and ownership direction. Read every cardinality from the source resource to the target resource (how many sources to how many targets): an edge from the resource holding the reference to the resource it references, where many holders share one referenced row, is many-to-one and is correct. Deterministic validation has already refused a one-sided cardinality whose \"one\" end holds the reference; do not re-report that. Do not resolve the intents into physical foreign keys.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The relationships are structurally valid but one or more semantic intents need refinement.","GAP":"At least one necessary relationship is missing or one declared relationship is materially incoherent.","INDETERMINATE":"The staged evidence cannot establish semantic relationship integrity.","PASS":"The relationship intents coherently connect the proposed resource inventory."}},{"criterionRef":"application-creation:criterion/domain-plan-requirement-coverage","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is served by at least one module capability and resource inventory, OR is recorded in engineRealizedRequirements because the engine already provides it (roles, membership, audit, personal data, governed documents, billing, guidance, notifications, localization). Treat a requirement with neither a resolvable module home nor an engine realization as a material gap.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete but one or more requirement-to-module links are weak or indirect.","GAP":"At least one current-horizon functional requirement has neither a resolvable module home nor an engine realization.","INDETERMINATE":"The staged evidence cannot establish complete requirement coverage.","PASS":"Every current-horizon functional requirement has a coherent module and resource home, or an engine realization naming the concern that meets it."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/domain-plan-output-set-result","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:bottom_up.domain-plan"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-domain-plan-output-set","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/domain-plan-boundary-discipline","application-creation:evidence-requirement/domain-plan-feature-coverage","application-creation:evidence-requirement/domain-plan-inventory-plausibility","application-creation:evidence-requirement/domain-plan-module-justification","application-creation:evidence-requirement/domain-plan-relationship-integrity","application-creation:evidence-requirement/domain-plan-requirement-coverage"],"requirementRef":"application-creation:authority-requirement/domain-plan-output-set-result","requirementVersion":1,"riskClassRef":"application-creation:risk/domain-plan-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/domain-plan-output-set-result","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/domain-plan-output-set-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/domain-plan-output-set-result","policyVersion":1},"decisionPointRef":"application-creation:decision-point/domain-plan-output-set-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/domain-plan-output-set-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/domain-plan-output-set-result","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-boundary-discipline","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-feature-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-inventory-plausibility","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-module-justification","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-relationship-integrity","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-requirement-coverage","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/domain-plan-output-set-structurally-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/domain-plan-accepted-landing","triggerRefs":["application-creation:trigger/domain-plan-output-set-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-domain-plan-coherence-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/domain-plan-boundary-discipline","application-creation:evidence-requirement/domain-plan-feature-coverage","application-creation:evidence-requirement/domain-plan-inventory-plausibility","application-creation:evidence-requirement/domain-plan-module-justification","application-creation:evidence-requirement/domain-plan-relationship-integrity","application-creation:evidence-requirement/domain-plan-requirement-coverage"],"hardFloorRef":"application-creation:hard-floor/domain-plan-output-set-structurally-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/domain-plan-output-set-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/domain-plan-output-set-result","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-domain-plan-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/domain-plan-boundary-discipline","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-boundary-discipline","requirementVersion":1}],"instruction":"Determine whether the output remains at planning depth: modules, resource inventories and relationship intents only. Treat schema fields, concrete foreign-key placement or generated implementation code as scope leakage.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The output is usable but contains limited premature implementation detail.","GAP":"The output materially crosses into schema, foreign-key or implementation authoring.","INDETERMINATE":"The staged evidence cannot establish the output depth boundary.","PASS":"The output remains within the declared planning-depth boundary."}},{"criterionRef":"application-creation:criterion/domain-plan-feature-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-feature-coverage","requirementVersion":1}],"instruction":"Determine whether every feature draft and benefit-delivering feature is realizable by the proposed module capabilities and resource inventories. Do not infer a home from naming similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All features have homes, but one or more mappings are weak or insufficiently explained.","GAP":"At least one feature or benefit-delivering capability has no resolvable domain home.","INDETERMINATE":"The staged evidence cannot establish complete feature coverage.","PASS":"Every feature and benefit-delivering capability has a resolvable domain home."}},{"criterionRef":"application-creation:criterion/domain-plan-inventory-plausibility","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-inventory-plausibility","requirementVersion":1}],"instruction":"Assess whether main resources form each module semantic center, supporting resources remain genuinely supporting, and ownership boundaries are plausible. Deterministic uniqueness has already passed and must not be reinterpreted.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The inventories are usable but one or more main/supporting classifications are questionable.","GAP":"At least one inventory materially contradicts its declared module capability.","INDETERMINATE":"The staged evidence cannot establish plausible module inventories.","PASS":"Each module inventory has a plausible semantic center and supporting boundary."}},{"criterionRef":"application-creation:criterion/domain-plan-module-justification","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-module-justification","requirementVersion":1}],"instruction":"Determine whether every proposed module is justified by accepted requirements or features and represents one coherent business capability. Flag speculative or mixed-purpose modules.","schemaVersion":1,"verdictGuidance":{"CONCERN":"One or more modules are weakly justified or combine boundaries that should be reconsidered.","GAP":"At least one module is speculative or materially incoherent with the definition set.","INDETERMINATE":"The staged evidence cannot establish why every module exists.","PASS":"Every proposed module is justified and capability-coherent."}},{"criterionRef":"application-creation:criterion/domain-plan-relationship-integrity","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-relationship-integrity","requirementVersion":1}],"instruction":"Assess whether the typed relationship intents are semantically necessary and coherent with the inventoried resources, conceptual cardinality and ownership direction. Read every cardinality from the source resource to the target resource (how many sources to how many targets): an edge from the resource holding the reference to the resource it references, where many holders share one referenced row, is many-to-one and is correct. Deterministic validation has already refused a one-sided cardinality whose \"one\" end holds the reference; do not re-report that. Do not resolve the intents into physical foreign keys.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The relationships are structurally valid but one or more semantic intents need refinement.","GAP":"At least one necessary relationship is missing or one declared relationship is materially incoherent.","INDETERMINATE":"The staged evidence cannot establish semantic relationship integrity.","PASS":"The relationship intents coherently connect the proposed resource inventory."}},{"criterionRef":"application-creation:criterion/domain-plan-requirement-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is served by at least one module capability and resource inventory. Treat a requirement without a resolvable module home as a material gap.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete but one or more requirement-to-module links are weak or indirect.","GAP":"At least one current-horizon functional requirement has no resolvable module home.","INDETERMINATE":"The staged evidence cannot establish complete requirement coverage.","PASS":"Every current-horizon functional requirement has a coherent module and resource home."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/domain-plan-output-set-result","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:bottom_up.domain-plan"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/domain-plan-output-set-result","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-boundary-discipline","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-boundary-discipline","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-feature-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-feature-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-inventory-plausibility","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-inventory-plausibility","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-module-justification","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-module-justification","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-relationship-integrity","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-relationship-integrity","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-requirement-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-requirement-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"}],"schemaVersion":1}
|
|
1
|
+
{"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-domain-plan-output-set","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/domain-plan-boundary-discipline","application-creation:evidence-requirement/domain-plan-feature-coverage","application-creation:evidence-requirement/domain-plan-inventory-plausibility","application-creation:evidence-requirement/domain-plan-module-justification","application-creation:evidence-requirement/domain-plan-relationship-integrity","application-creation:evidence-requirement/domain-plan-requirement-coverage"],"requirementRef":"application-creation:authority-requirement/domain-plan-output-set-result","requirementVersion":1,"riskClassRef":"application-creation:risk/domain-plan-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/domain-plan-output-set-result","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/domain-plan-output-set-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/domain-plan-output-set-result","policyVersion":1},"decisionPointRef":"application-creation:decision-point/domain-plan-output-set-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/domain-plan-output-set-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/domain-plan-output-set-result","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-boundary-discipline","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-engine-concern-discipline","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-feature-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-inventory-plausibility","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-lifecycle-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-module-justification","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-relationship-integrity","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-requirement-coverage","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/domain-plan-output-set-structurally-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/domain-plan-accepted-landing","triggerRefs":["application-creation:trigger/domain-plan-output-set-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-domain-plan-coherence-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/domain-plan-boundary-discipline","application-creation:evidence-requirement/domain-plan-feature-coverage","application-creation:evidence-requirement/domain-plan-inventory-plausibility","application-creation:evidence-requirement/domain-plan-module-justification","application-creation:evidence-requirement/domain-plan-relationship-integrity","application-creation:evidence-requirement/domain-plan-requirement-coverage"],"hardFloorRef":"application-creation:hard-floor/domain-plan-output-set-structurally-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/domain-plan-output-set-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/domain-plan-output-set-result","definitionVersion":4,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-domain-plan-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/domain-plan-boundary-discipline","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-boundary-discipline","requirementVersion":1}],"instruction":"Determine whether the output remains at planning depth: modules, resource inventories, relationship intents and resource lifecycles (states, transitions, conversions, locked and final states) only. Treat schema fields, concrete foreign-key placement or generated implementation code as scope leakage.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The output is usable but contains limited premature implementation detail.","GAP":"The output materially crosses into schema, foreign-key or implementation authoring.","INDETERMINATE":"The staged evidence cannot establish the output depth boundary.","PASS":"The output remains within the declared planning-depth boundary."}},{"criterionRef":"application-creation:criterion/domain-plan-engine-concern-discipline","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-engine-concern-discipline","requirementVersion":1}],"instruction":"Determine whether any module or resource stands in for a concern the engine already provides or that is not data a user maintains: roles, permissions or role assignments (the engine roles); members, invitations or teams; an audit history; processing purposes, legal bases, compliance or country declarations typed in by users (a governed document); a next action, stage or status copied from other records (derived, shown in a view). Such a requirement belongs in engineRealizedRequirements, or is derived. A product resource that merely mentions one of these words (an invoice with a status, a job with a stage the user sets as part of the work) is not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A resource may duplicate an engine concern or derived state, but the definition context leaves room for a genuine product reading; name it and the reading.","GAP":"A module or resource models roles or permissions, a compliance or country declaration users type in, or state copied from other records, while the requirement it serves is the engine's or derivable.","INDETERMINATE":"The staged evidence cannot establish what the resources hold.","PASS":"No module or resource models an engine-provided concern, a disclaimer, or state derived from other records."}},{"criterionRef":"application-creation:criterion/domain-plan-feature-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-feature-coverage","requirementVersion":1}],"instruction":"Determine whether every feature draft and benefit-delivering feature is realizable by the proposed module capabilities and resource inventories. Do not infer a home from naming similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All features have homes, but one or more mappings are weak or insufficiently explained.","GAP":"At least one feature or benefit-delivering capability has no resolvable domain home.","INDETERMINATE":"The staged evidence cannot establish complete feature coverage.","PASS":"Every feature and benefit-delivering capability has a resolvable domain home."}},{"criterionRef":"application-creation:criterion/domain-plan-inventory-plausibility","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-inventory-plausibility","requirementVersion":1}],"instruction":"Assess whether main resources form each module semantic center, supporting resources remain genuinely supporting, and ownership boundaries are plausible. Deterministic uniqueness has already passed and must not be reinterpreted.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The inventories are usable but one or more main/supporting classifications are questionable.","GAP":"At least one inventory materially contradicts its declared module capability.","INDETERMINATE":"The staged evidence cannot establish plausible module inventories.","PASS":"Each module inventory has a plausible semantic center and supporting boundary."}},{"criterionRef":"application-creation:criterion/domain-plan-lifecycle-coverage","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-lifecycle-coverage","requirementVersion":1}],"instruction":"Determine whether every resource a current-horizon requirement describes moving through states (sent, accepted, issued, paid, approved, closed) has a lifecycle whose transitions carry the requirement's verbs, whose conversions name the resource they create when one record creates another (\"an accepted quote creates a job\"), and whose locked and final states together cover what the requirements say must stop changing (locked when the record still moves on, final when nothing moves it again). A state change expressed only as a relationship, a status the requirements never move, or a lifecycle for a value derived from other records is not coverage.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Each such record has a lifecycle, but a verb, a conversion target, or a locked or final state the requirements imply is missing from it.","GAP":"A requirement moves a record through states and the plan has no lifecycle for it, or expresses the move only as a relationship.","INDETERMINATE":"The staged evidence cannot establish which requirements move records through states.","PASS":"No requirement moves a record through states, or every such record has a lifecycle carrying the requirement's verbs, its conversions and its final states."}},{"criterionRef":"application-creation:criterion/domain-plan-module-justification","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-module-justification","requirementVersion":1}],"instruction":"Determine whether every proposed module is justified by accepted requirements or features and represents one coherent business capability. Flag speculative or mixed-purpose modules.","schemaVersion":1,"verdictGuidance":{"CONCERN":"One or more modules are weakly justified or combine boundaries that should be reconsidered.","GAP":"At least one module is speculative or materially incoherent with the definition set.","INDETERMINATE":"The staged evidence cannot establish why every module exists.","PASS":"Every proposed module is justified and capability-coherent."}},{"criterionRef":"application-creation:criterion/domain-plan-relationship-integrity","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-relationship-integrity","requirementVersion":1}],"instruction":"Assess whether the typed relationship intents are semantically necessary and coherent with the inventoried resources, conceptual cardinality and ownership direction. Read every cardinality from the source resource to the target resource (how many sources to how many targets): an edge from the resource holding the reference to the resource it references, where many holders share one referenced row, is many-to-one and is correct. Deterministic validation has already refused a one-sided cardinality whose \"one\" end holds the reference; do not re-report that. Do not resolve the intents into physical foreign keys.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The relationships are structurally valid but one or more semantic intents need refinement.","GAP":"At least one necessary relationship is missing or one declared relationship is materially incoherent.","INDETERMINATE":"The staged evidence cannot establish semantic relationship integrity.","PASS":"The relationship intents coherently connect the proposed resource inventory."}},{"criterionRef":"application-creation:criterion/domain-plan-requirement-coverage","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is served by at least one module capability and resource inventory, OR is recorded in engineRealizedRequirements because the engine already provides it (roles, membership, audit, personal data, governed documents, billing, guidance, notifications, localization). Treat a requirement with neither a resolvable module home nor an engine realization as a material gap.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete but one or more requirement-to-module links are weak or indirect.","GAP":"At least one current-horizon functional requirement has neither a resolvable module home nor an engine realization.","INDETERMINATE":"The staged evidence cannot establish complete requirement coverage.","PASS":"Every current-horizon functional requirement has a coherent module and resource home, or an engine realization naming the concern that meets it."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/domain-plan-output-set-result","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:bottom_up.domain-plan"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/domain-plan-output-set-result","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-boundary-discipline","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-boundary-discipline","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-engine-concern-discipline","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-engine-concern-discipline","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-feature-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-feature-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-inventory-plausibility","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-inventory-plausibility","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-lifecycle-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-lifecycle-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-module-justification","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-module-justification","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-relationship-integrity","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-relationship-integrity","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-requirement-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-requirement-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"}],"schemaVersion":1}
|
|
@@ -84,7 +84,8 @@ anything:
|
|
|
84
84
|
|
|
85
85
|
|
|
86
86
|
You **read** `requirements` + `market-snapshot` + `feature-drafts` + `roadmap` +
|
|
87
|
-
`vision-brief
|
|
87
|
+
`vision-brief`, and what the creator stated in the other interviews; you **write**
|
|
88
|
+
the `domain-plan` families.
|
|
88
89
|
|
|
89
90
|
## Step 1 — Derive the modules (the decomposition)
|
|
90
91
|
|
|
@@ -106,14 +107,58 @@ capability. Derive modules by **clustering** the definition set, not by guessing
|
|
|
106
107
|
`businessDomain` (the larger bounded-context label) and `integrationSurfaces`
|
|
107
108
|
(named surfaces the module participates in).
|
|
108
109
|
3. **Keep modules justified.** Every module must earn its existence from
|
|
109
|
-
requirements or features in the definition set
|
|
110
|
+
requirements or features in the definition set, or from a fact the creator
|
|
111
|
+
stated that the requirements neither carry nor exclude (Step 2). Do **not** invent a module the
|
|
110
112
|
definition set does not call for — a speculative module is a coherence CONCERN
|
|
111
|
-
(see the quality gate). Conversely,
|
|
112
|
-
|
|
113
|
+
(see the quality gate). Conversely, a requirement or feature with no home is a
|
|
114
|
+
coverage GAP — and its home is EITHER a module OR an entry of
|
|
115
|
+
`engineRealizedRequirements` when the engine already provides it (Step 1b). Read
|
|
116
|
+
Step 1b before concluding that a requirement needs a module.
|
|
113
117
|
|
|
114
118
|
The `resource-add-module` skill carries the module-scaffolding vocabulary (what a
|
|
115
119
|
module is across the project layout); read it to keep module boundaries idiomatic.
|
|
116
120
|
|
|
121
|
+
## Step 1b — Leave the engine's concerns to the engine
|
|
122
|
+
|
|
123
|
+
### What the engine already provides — never a module, never a resource
|
|
124
|
+
|
|
125
|
+
Some requirements are met by what every Wildo application already has, configured rather than built.
|
|
126
|
+
A module or resource for one of them is read by nothing in the engine: it looks like the feature and
|
|
127
|
+
does none of it. When a requirement falls in one of these areas, record it in the domain plan's
|
|
128
|
+
`engineRealizedRequirements` (the requirement's ref, the concern below, and what the build still has to
|
|
129
|
+
configure) instead of giving it a module home.
|
|
130
|
+
|
|
131
|
+
| The requirement sounds like… | Concern (`realization`) | Where it is configured |
|
|
132
|
+
|---|---|---|
|
|
133
|
+
| "office and field users see different things", "only administrators may…", "a read-only reviewer" | `APPLICATION_ROLES` | the role table, the organization types that offer a role, each operation's `roles` — skill `application-roles-authoring` |
|
|
134
|
+
| "only a chartered / licensed / certified person may approve", "track our staff's certifications" | `APPLICATION_ROLES` | a role, plus the qualification kinds a decision requires (`professionalQualificationKinds`, `requiredQualificationKinds`) and the organization's qualifications register — skill `professional-qualifications` |
|
|
135
|
+
| "invite colleagues", "manage the team", "departments", "regions" | `ORGANIZATION_MEMBERSHIP` | the engine's members, invitations and organization units — skills `authorization-unit-narrowing`, `organization-relationships` |
|
|
136
|
+
| "see who changed what", "a history of changes" | `AUDIT_TRAIL` | operation audit on each resource — skill `resource-config-wiring` |
|
|
137
|
+
| "GDPR", "a customer can ask for their data / its deletion", "keep records for N years" | `PERSONAL_DATA` | personal-data declarations on fields, erasure, export and retention — skills `resource-config-wiring`, `resource-retention-binding` |
|
|
138
|
+
| "the privacy notice lists the purposes", "state the legal basis", "do not claim compliance with X", country disclaimers | `GOVERNED_DOCUMENT` | a governed document composed from the product — skill `compliance-document-authoring` |
|
|
139
|
+
| "customers subscribe to a plan" (the operator charging ITS customers) | `BILLING` | the billing catalogue — skill `configure-billing` |
|
|
140
|
+
| "guide new users", "celebrate the first…" | `GUIDANCE` | onboarding guidance and milestones — skills `guidance-onboarding-authoring`, `milestones-and-celebrations` |
|
|
141
|
+
| "notify the office when…", "email the customer when…" | `NOTIFICATIONS` | notifications declared on the operation that causes them — skills `resource-config-wiring`, `email-add-template` |
|
|
142
|
+
| "available in French and German" | `LOCALIZATION` | the application's languages and generated labels — skill `i18n-label-generation` |
|
|
143
|
+
|
|
144
|
+
Two further rules, because both produced resources nothing reads:
|
|
145
|
+
|
|
146
|
+
- **State derived from other records is never stored.** "The next action for each customer", "what is
|
|
147
|
+
overdue", "the stage a job is in" are computed from the records that carry the work and shown in a
|
|
148
|
+
view. A resource holding them by hand drifts from the records the moment either changes.
|
|
149
|
+
- **A disclaimer is never a resource.** A criterion of the form "does not claim X until Y" or "the product
|
|
150
|
+
states its limits" is a statement the operator makes (`GOVERNED_DOCUMENT`), not data a user types in.
|
|
151
|
+
|
|
152
|
+
An invoice the APPLICATION issues to its own customers (a trade business invoicing a homeowner) IS
|
|
153
|
+
product domain and belongs in a module; `BILLING` is only the operator charging the application's
|
|
154
|
+
subscribers.
|
|
155
|
+
|
|
156
|
+
|
|
157
|
+
`engineRealizedRequirements` is required: write `[]` when no requirement falls in these areas,
|
|
158
|
+
so the plan says it looked. One entry per requirement and concern; a requirement can have a
|
|
159
|
+
module home for its product part AND an engine entry for its access or privacy part (an invoice
|
|
160
|
+
resource in a module, and `APPLICATION_ROLES` for "only the office may issue invoices").
|
|
161
|
+
|
|
117
162
|
## Step 2 — Inventory the resources per module
|
|
118
163
|
|
|
119
164
|
For each module, list the **resources** (persisted entity types) it owns. The
|
|
@@ -132,10 +177,28 @@ Rules for a plausible inventory:
|
|
|
132
177
|
page: a requirement that says "users can label tasks" implies a `task` resource
|
|
133
178
|
and (probably) a `label` resource. The `resource-add-resource` skill carries the
|
|
134
179
|
vocabulary for what a resource is; read it to keep the inventory idiomatic.
|
|
180
|
+
- **What the creator stated reaches the inventory too.** Their answers to the
|
|
181
|
+
other interviews arrive in the declared `creator_stated_facts` context section of your brief, and the
|
|
182
|
+
requirements may have carried only part of them. Each stage of the stated
|
|
183
|
+
workflow has a resource it happens on (a site visit, a quote, a job). A stated
|
|
184
|
+
data class has a home: name the resource that holds a job-site address or a
|
|
185
|
+
VAT number in its module's `purpose`, which is the only place this plan can
|
|
186
|
+
say it (fields are the build's job, and the build reads the plan). A named
|
|
187
|
+
e-invoicing or other regime has a module or resource that serves it, or
|
|
188
|
+
belongs to the engine under Step 1b. Each stated user group is served by a
|
|
189
|
+
module, and its access belongs to the engine. What the creator put out of
|
|
190
|
+
scope, and a fact the requirements list in `excludedStatedFacts`, gets no
|
|
191
|
+
module. A stated fact that neither the requirements carry nor exclude, and
|
|
192
|
+
this plan does not carry, is a coverage GAP. Name it in the module's
|
|
193
|
+
`purpose` or raise it as a clarification; never drop it.
|
|
135
194
|
- **Each resource is inventoried in exactly one module** as its `mainResource`. A
|
|
136
195
|
resource that is genuinely shared across modules is a signal you either have the
|
|
137
196
|
module boundary wrong or you need a relationship (Step 3), not the same main
|
|
138
197
|
resource duplicated in two modules.
|
|
198
|
+
- **Never inventory what Step 1b leaves to the engine.** No resource holding roles,
|
|
199
|
+
permissions or role assignments; no resource holding processing purposes, compliance
|
|
200
|
+
declarations or country rules for users to type in; no resource holding a next action,
|
|
201
|
+
a stage or a status copied from other records.
|
|
139
202
|
- **Do not author fields or schemas here.** The inventory names the resource and
|
|
140
203
|
says which module owns it. What fields the resource carries, its enums, its
|
|
141
204
|
decorators — all of that is the **build loop's** job. If you catch yourself
|
|
@@ -180,6 +243,43 @@ discriminator relationships). Read it to keep your relationship *intents* aligne
|
|
|
180
243
|
with what the build loop can actually wire — but do **not** perform that wiring in
|
|
181
244
|
this planning pass.
|
|
182
245
|
|
|
246
|
+
## Step 4 — Declare the lifecycles
|
|
247
|
+
|
|
248
|
+
For every resource the requirements describe moving through states — a quote that is sent and
|
|
249
|
+
accepted, an invoice that is issued and paid, a case that is opened and closed — declare its
|
|
250
|
+
lifecycle in `lifecycles`:
|
|
251
|
+
|
|
252
|
+
- **`states`** — every state, upper snake case (`DRAFT`, `SENT`, `ACCEPTED`), and the
|
|
253
|
+
**`initialState`** a new record starts in.
|
|
254
|
+
- **`transitions`** — one per verb the business uses, as a lower-case slug (`send`, `accept`,
|
|
255
|
+
`decline`, `issue`, `mark-paid`): the states it may start `from`, the state it moves `to`, and who
|
|
256
|
+
performs it in the requirements' words. One verb is one transition: list every starting state in
|
|
257
|
+
its `from`.
|
|
258
|
+
- **`stampsField`** on a transition whose moment the business needs (when the quote was sent, when the
|
|
259
|
+
invoice was paid): a camelCase timestamp field (`sentAt`, `paidAt`). `null` when nobody needs it.
|
|
260
|
+
- **`createsResourceRef`** on a transition that creates another resource (accepting a quote
|
|
261
|
+
creates a job). The created resource must be inventoried.
|
|
262
|
+
- **`lockedStates`** — the states in which the record can no longer be EDITED but still moves on: an
|
|
263
|
+
issued invoice (later marked paid), a sent quote (later accepted or declined). Empty when none.
|
|
264
|
+
- **`finalStates`** — the TERMINAL states: nothing moves the record out of them, and it is not edited
|
|
265
|
+
there either (a paid invoice, a closed case). Empty when nothing is ever final. No transition starts
|
|
266
|
+
from a final state: a state you can leave is locked, not final.
|
|
267
|
+
|
|
268
|
+
**When the application has a service method** (the firm's method, #2305), each service's CASE is a resource
|
|
269
|
+
you inventory: `case.caseRef` is its ref, listed in `mainResources` of the module the service's work belongs to,
|
|
270
|
+
and its lifecycle is the case's `stages`, in order. Each stage ref becomes a state in upper snake case
|
|
271
|
+
(`in-reconciliation` → `IN_RECONCILIATION`), the first stage is the `initialState`, and the transitions between
|
|
272
|
+
them are the business verbs the steps and decision points describe ("sign the period off" → `sign-off`). A stage a
|
|
273
|
+
case returns to (`reopened`) is a state with a transition back into it. The resources the steps read and produce
|
|
274
|
+
(`readsRefs`, `producesRefs`) and the deliverables come from (`fromResourceRef`) are resources too. This is
|
|
275
|
+
checked: a case of more than one stage with no lifecycle, a stage that is not one of its states, or a deliverable
|
|
276
|
+
produced from a resource you did not inventory is reported against the domain plan.
|
|
277
|
+
|
|
278
|
+
Write `[]` when no resource moves through states. Read the requirements' verbs, not their nouns:
|
|
279
|
+
"an accepted quote can be used to create a job" is a lifecycle (`accept`) and a conversion
|
|
280
|
+
(`createsResourceRef: job`), not a foreign key. A value derived from other records — a next action,
|
|
281
|
+
an overdue flag — is not a state of any resource (Step 1b).
|
|
282
|
+
|
|
183
283
|
## Refine, don't re-author
|
|
184
284
|
|
|
185
285
|
- **Keep what still holds.** On a re-run, do not rename or re-decompose modules
|
|
@@ -200,9 +300,13 @@ atomic manifest must all be valid. That is a non-bypassable eligibility floor,
|
|
|
200
300
|
not a semantic quality opinion.
|
|
201
301
|
|
|
202
302
|
The companion then executes the playbook's structured semantic Treatment over
|
|
203
|
-
the exact staged output-set artifact. Its
|
|
204
|
-
requirement coverage, feature coverage,
|
|
205
|
-
plausibility, relationship integrity,
|
|
303
|
+
the exact staged output-set artifact. Its eight criteria remain distinct:
|
|
304
|
+
requirement coverage (a module home OR an engine realization), feature coverage,
|
|
305
|
+
module justification, inventory plausibility, relationship integrity,
|
|
306
|
+
planning-depth boundary discipline, engine-concern discipline (no module or
|
|
307
|
+
resource for what the engine provides, a disclaimer, or derived state), and
|
|
308
|
+
lifecycle coverage (a requirement that moves a record through states has its
|
|
309
|
+
lifecycle).
|
|
206
310
|
Each criterion produces PASS / CONCERN / GAP / INDETERMINATE evidence, and the
|
|
207
311
|
worst-verdict aggregation policy determines the Decision Rule consequence.
|
|
208
312
|
|
|
@@ -212,9 +316,11 @@ decision is a separate later boundary. CONCERN or GAP requests revision,
|
|
|
212
316
|
INDETERMINATE requests evidence, and evaluator or hard-floor failure blocks
|
|
213
317
|
closed. The evaluation path never mutates accepted specification heads.
|
|
214
318
|
|
|
215
|
-
## Scaffold-depth boundary
|
|
319
|
+
## Scaffold-depth boundary
|
|
216
320
|
|
|
217
|
-
Keep this playbook at scaffold depth.
|
|
321
|
+
Keep this playbook at scaffold depth. Lifecycles (Step 4) are IN scope: they are what the
|
|
322
|
+
resources DO, decided where the resources are, and nothing later decides them. Explicitly
|
|
323
|
+
**out of scope here**:
|
|
218
324
|
|
|
219
325
|
- **Schema / field authoring.** The inventory names resources and their owning
|
|
220
326
|
module; it does **not** author fields, enums, decorators, or Zod schemas. That is
|
|
@@ -236,8 +342,9 @@ Keep this playbook at scaffold depth. Explicitly **out of scope here**:
|
|
|
236
342
|
registering the module across runtimes, generating resource files — all of that is
|
|
237
343
|
the bottom-up build loop, downstream of this plan.
|
|
238
344
|
|
|
239
|
-
If you find yourself perfecting any of the above, stop
|
|
240
|
-
|
|
345
|
+
If you find yourself perfecting any of the above, stop: fields, physical foreign keys and
|
|
346
|
+
generated code are the build's. What the build cannot invent — which states a resource has and
|
|
347
|
+
which moves the business allows — is yours, in Step 4.
|
|
241
348
|
|
|
242
349
|
## What you emit
|
|
243
350
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "bottom_up.domain-plan",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.3",
|
|
4
4
|
"phase": "bottom_up",
|
|
5
5
|
"intent": "Turn the approved definition set into one atomic, planning-depth domain output set: module decomposition with per-module resource inventory plus typed inter-resource relationship intents. The output remains staged until deterministic validation, semantic evaluation and distinct result authority complete.",
|
|
6
6
|
"preconditions": [
|
|
@@ -34,6 +34,9 @@
|
|
|
34
34
|
{
|
|
35
35
|
"family": "vision-brief"
|
|
36
36
|
},
|
|
37
|
+
{
|
|
38
|
+
"family": "service-method"
|
|
39
|
+
},
|
|
37
40
|
{
|
|
38
41
|
"family": "domain-plan"
|
|
39
42
|
}
|
|
@@ -47,7 +50,7 @@
|
|
|
47
50
|
],
|
|
48
51
|
"stepOutputs": [],
|
|
49
52
|
"method": {
|
|
50
|
-
"guidance": "# Domain Plan — Definition Set → Modules + Resources + Relationships (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to be\n> iterated. The decomposition heuristic, the resource-inventory convention, and\n> the relationship-intent shape below are deliberately explicit so they can be\n> tuned against real runs — treat them as a starting rubric, not a frozen\n> contract. The *analytical depth* of domain modelling (a full ERD, a\n> cardinality-to-FK solver and full domain-graph validation) is intentionally\n> shallow here and is deepened in a later phase; do\n> not perfect it in this playbook.\n\n## Where you are in the journey\n\nThis is the **first bottom-up playbook** — the pivot from **product definition**\n(top-down: vision, market, requirements, roadmap, business model) to **project\ndefinition** (bottom-up: the app's modules, resources, and how they relate). It\nruns **only after** the exact\n`top_down-to-bottom_up.bootstrap-non-regulated@0.1.0` route has produced a\ndurable `top_down → bottom_up` transition-commit fact. That fact proves the\nroute-bound readiness, semantic decision, Authority Request/Decision and phase\neffect chain; it is not an arbitrary approval flag. The separate\n`phase_is bottom_up` predicate checks the current phase projection. You are not\nre-opening product questions here — you are turning the currently accepted\nproduct definition into the *shape of the software that delivers it*.\n\n## What this playbook does\n\nYou are the **domain architect**. This playbook reads the approved definition set\nand drafts the **domain plan**: the answer to *\"what modules does this app have,\nwhat resources live in each, and how do those resources relate?\"* You produce\n**two artifacts**:\n\n1. The **domain-plan** family — the **module decomposition** with a **per-module\n resource inventory**, authored as a collection of **ModuleBusinessSemantics\n drafts** (one per proposed module). Each module draft states its purpose, its\n business capability, its primary actors, and its resource inventory\n (`mainResources` — the semantic center of the module; `supportingResources` —\n resources that support without being the center). The resource inventory lives\n **inside** each module draft because an inventory is inherently *per module*.\n2. The **relationship drafts** — carried INSIDE the same domain-plan value — the **inter-resource relationship\n intents**: for each durable association between two inventoried resources, the\n two ends, the **cardinality intent** (one-to-one / one-to-many / many-to-one /\n many-to-many, read from source to target), and the **ownership direction**\n (which resource holds the reference). These are\n typed conceptual drafts — a relationship is not a module, so it earns its own\n family, and the build loop consumes it when it wires FK fields.\n\nThis is a **planning pass**. You name modules, the resources inside them, and how\nthey relate. You do **not** author schemas, resolve a cardinality intent into a\nconcrete foreign-key field, or generate any code — that is the **bottom-up build\nloop's** job, downstream of this plan.\n\n## Read state first — the definition set you read, the two artifacts you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before drafting\nanything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it. Confirm the top-down set is present\n and approved, and check whether a `domain-plan` already\n exist from an earlier run (refine them, do not re-author — see below).\n2. Read the approved definition set. **Load-bearing** (these drive the\n decomposition): the **requirements** (`requirements` family — the functional and\n non-functional requirements the domain must satisfy), the capability-mapped\n **MarketSnapshot** (`market-snapshot` — the benefits wired to their delivering\n features, so you know what capability each feature carries), and the\n **feature-drafts** (the prose capability contracts — what each delivering\n feature actually is). **Contextual** (they shape emphasis, not the core\n decomposition): the **roadmap** (`roadmap` — the release phasing, so you can see\n which modules are MVP-critical vs later) and the **VisionSnapshot**\n (`vision-brief` — the product framing and differentiation).\n\n\nYou **read** `requirements` + `market-snapshot` + `feature-drafts` + `roadmap` +\n`vision-brief`; you **write** the `domain-plan` families.\n\n## Step 1 — Derive the modules (the decomposition)\n\nA **module** is a bounded slice of the app that delivers a coherent business\ncapability. Derive modules by **clustering** the definition set, not by guessing:\n\n1. **Cluster requirements and features by capability.** Group the functional\n requirements and the feature-drafts that serve one coherent capability (e.g.\n \"everything about authoring and tracking tasks\", \"everything about billing and\n plans\"). Each tight cluster is a candidate module. A feature-draft and the\n requirements it realises usually land in the same module.\n2. **Name each module and state its semantics.** For each candidate module author a\n `ModuleBusinessSemantics` draft: a `relatedModuleId` (the id the module registry\n will use — it must be **distinct across all module drafts**; two modules sharing\n an id silently collide, since the registry addresses modules by id), a `purpose`\n (why the module exists, in plain language), a\n `businessCapability` (the capability it delivers), the `primaryActors` (the\n human/business actors that interact with it), and — optionally — a\n `businessDomain` (the larger bounded-context label) and `integrationSurfaces`\n (named surfaces the module participates in).\n3. **Keep modules justified.** Every module must earn its existence from\n requirements or features in the definition set. Do **not** invent a module the\n definition set does not call for — a speculative module is a coherence CONCERN\n (see the quality gate). Conversely, if a requirement or feature has no home\n module, you are missing a module (a coverage GAP).\n\nThe `resource-add-module` skill carries the module-scaffolding vocabulary (what a\nmodule is across the project layout); read it to keep module boundaries idiomatic.\n\n## Step 2 — Inventory the resources per module\n\nFor each module, list the **resources** (persisted entity types) it owns. The\ninventory is **two lists on the module draft**:\n\n- **`mainResources`** — the resources that form the semantic **center** of the\n module (the entities the module is *about*: a `tasks` module's `task`).\n- **`supportingResources`** — resources that **support** the module's capability\n without being its center (lookup tables, join/junction entities, per-entity\n settings). A resource that is the center of the module belongs in `mainResources`,\n not here.\n\nRules for a plausible inventory:\n\n- **Derive resources from the requirements + feature-drafts**, not from a blank\n page: a requirement that says \"users can label tasks\" implies a `task` resource\n and (probably) a `label` resource. The `resource-add-resource` skill carries the\n vocabulary for what a resource is; read it to keep the inventory idiomatic.\n- **Each resource is inventoried in exactly one module** as its `mainResource`. A\n resource that is genuinely shared across modules is a signal you either have the\n module boundary wrong or you need a relationship (Step 3), not the same main\n resource duplicated in two modules.\n- **Do not author fields or schemas here.** The inventory names the resource and\n says which module owns it. What fields the resource carries, its enums, its\n decorators — all of that is the **build loop's** job. If you catch yourself\n writing a field list, stop: that is out of this playbook's depth.\n\n## Step 3 — Draft the inter-resource relationships\n\nOnce the resources are inventoried, capture how they **relate**. For each durable\nassociation between two inventoried resources, author a **relationship draft** in\nthe relationship drafts (inside the domain-plan value) stating:\n\n- **The two ends** — the two resources that relate (both must be inventoried in\n some module's inventory from Step 2; a relationship to an un-inventoried resource\n is a coverage GAP).\n- **The cardinality intent** — one-to-one, one-to-many, many-to-one, or\n many-to-many, **always read from the source to the target**: *how many sources*\n to *how many targets*. \"Each `task` belongs to one `project`, a project has many\n tasks\", authored with `task` as the source and `project` as the target, is\n **many-to-one**. The same association authored with `project` as the source is\n **one-to-many**. This is an *intent*; you are not resolving it into a foreign-key\n placement here.\n- **The ownership direction** — which resource conceptually **holds** the reference\n (e.g. \"a `task` belongs to a `project`\" → the `task` end holds the reference).\n This is the *intent* the build loop needs; it does **not** decide the physical FK\n holder (that resolution — FK holder from cardinality, discriminator relationships,\n conditional relationships — is the `module-relationships` skill's job at build\n time, **not** here).\n- **The two must agree.** In a one-to-many or many-to-one association the **many**\n side holds the reference, so many-to-one goes with *source holds the reference*\n and one-to-many with *target holds the reference*. Deterministic validation\n refuses the other two combinations. Only one-to-one and many-to-many leave the\n holder to you. The simplest habit: make the resource that carries the reference\n the **source**, and the edge is many-to-one.\n- **Make the rationale say the same thing as the labels.** The relationship\n judge reads the rationale against the cardinality, so \"each customer has one\n country context, many customers share one\" belongs on a many-to-one edge from\n customer to country context.\n\nThe `module-relationships` skill carries the technical HOW of realising a\nrelationship (FK fields, cardinality-to-FK-holder resolution, conditional /\ndiscriminator relationships). Read it to keep your relationship *intents* aligned\nwith what the build loop can actually wire — but do **not** perform that wiring in\nthis planning pass.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not rename or re-decompose modules\n that are already correct. Only add a module, move a resource to a different\n module, or add/correct a relationship where the plan genuinely changed.\n- **Reuse existing module ids.** A module that already exists keeps its\n `relatedModuleId` — never mint a second id for the same module. Likewise, keep a\n resource's name stable across runs.\n- **Never orphan a relationship.** A relationship draft must name two resources\n that are actually inventoried in Step 2. If you move or rename a resource, follow\n it into every relationship draft that references it.\n\n## Executable semantic evaluation — `domain-plan-output-set-result`\n\nThe staged output set first passes deterministic structural validation: exact\nmodule/resource identities, typed relationship ends, unique ownership, and the\natomic manifest must all be valid. That is a non-bypassable eligibility floor,\nnot a semantic quality opinion.\n\nThe companion then executes the playbook's structured semantic Treatment over\nthe exact staged output-set artifact. Its six criteria remain distinct:\nrequirement coverage, feature coverage, module justification, inventory\nplausibility, relationship integrity, and planning-depth boundary discipline.\nEach criterion produces PASS / CONCERN / GAP / INDETERMINATE evidence, and the\nworst-verdict aggregation policy determines the Decision Rule consequence.\n\nA semantic PASS does **not** accept or publish the candidate. It transitions the\nresult Decision Point to `AUTHORITY_REQUIRED`; an explicit operator authority\ndecision is a separate later boundary. CONCERN or GAP requests revision,\nINDETERMINATE requests evidence, and evaluator or hard-floor failure blocks\nclosed. The evaluation path never mutates accepted specification heads.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. Explicitly **out of scope here**:\n\n- **Schema / field authoring.** The inventory names resources and their owning\n module; it does **not** author fields, enums, decorators, or Zod schemas. That is\n the build loop. If you catch yourself writing a field list, stop.\n- **Cardinality-to-FK resolution.** A relationship draft states a cardinality\n *intent* and an ownership *intent* in prose. Resolving that into a physical\n foreign-key holder, a discriminator relationship, or a conditional relationship is\n the `module-relationships` skill's job **at build time**, not here.\n- **A full ERD / domain-graph solver.** Phases-of-a-graph, transitive dependency\n ordering, normalization analysis, and diagram generation are a later-phase\n concern. You draft modules, an inventory, and relationship intents — not a solved\n entity-relationship diagram.\n- **A full domain-graph solver.** The framework now ships a typed conceptual\n relationship-draft contract and deterministic structural validation for the\n atomic output set. It deliberately does not solve physical FK placement,\n normalization, graph execution order, discriminator relationships, or\n conditional relationships; those remain build-depth concerns.\n- **Code generation / module registration.** Scaffolding the module folders,\n registering the module across runtimes, generating resource files — all of that is\n the bottom-up build loop, downstream of this plan.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nTwo artifacts for this journey:\n\n- The **domain-plan** under `specifications/src/domain-plan/` — a\n collection of `ModuleBusinessSemantics` drafts: the module decomposition, each\n module carrying its purpose, business capability, primary actors, and its\n `mainResources` / `supportingResources` inventory.\n- The **relationship drafts** inside the landed `specifications/src/domain-plan/` value\n — the inter-resource relationship intents (two ends + cardinality intent read\n source → target + ownership direction) between inventoried resources.\n\nAfter deterministic validation and semantic PASS, the runtime creates a distinct\nresult-bound Authority Request for the exact staged output-set digest. The local\noperator's explicit interface response settles that request; transition authority\ncannot substitute for it. Only then may the atomic specification-family mutation\naccept both files together for consumption by the bottom-up build loop.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `resource-add-module` — the module-scaffolding vocabulary\n (what a module is across the project layout); keeps module boundaries idiomatic.\n- `resource-add-resource` — the resource vocabulary (what a\n resource is); keeps the per-module inventory idiomatic.\n- `module-relationships` — the technical HOW of realising a\n relationship (FK fields, cardinality-to-FK-holder resolution, conditional /\n discriminator relationships) — consulted so relationship *intents* align with what\n the build loop can wire, NOT performed in this planning pass.\n",
|
|
53
|
+
"guidance": "# Domain Plan — Definition Set → Modules + Resources + Relationships (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to be\n> iterated. The decomposition heuristic, the resource-inventory convention, and\n> the relationship-intent shape below are deliberately explicit so they can be\n> tuned against real runs — treat them as a starting rubric, not a frozen\n> contract. The *analytical depth* of domain modelling (a full ERD, a\n> cardinality-to-FK solver and full domain-graph validation) is intentionally\n> shallow here and is deepened in a later phase; do\n> not perfect it in this playbook.\n\n## Where you are in the journey\n\nThis is the **first bottom-up playbook** — the pivot from **product definition**\n(top-down: vision, market, requirements, roadmap, business model) to **project\ndefinition** (bottom-up: the app's modules, resources, and how they relate). It\nruns **only after** the exact\n`top_down-to-bottom_up.bootstrap-non-regulated@0.1.0` route has produced a\ndurable `top_down → bottom_up` transition-commit fact. That fact proves the\nroute-bound readiness, semantic decision, Authority Request/Decision and phase\neffect chain; it is not an arbitrary approval flag. The separate\n`phase_is bottom_up` predicate checks the current phase projection. You are not\nre-opening product questions here — you are turning the currently accepted\nproduct definition into the *shape of the software that delivers it*.\n\n## What this playbook does\n\nYou are the **domain architect**. This playbook reads the approved definition set\nand drafts the **domain plan**: the answer to *\"what modules does this app have,\nwhat resources live in each, and how do those resources relate?\"* You produce\n**two artifacts**:\n\n1. The **domain-plan** family — the **module decomposition** with a **per-module\n resource inventory**, authored as a collection of **ModuleBusinessSemantics\n drafts** (one per proposed module). Each module draft states its purpose, its\n business capability, its primary actors, and its resource inventory\n (`mainResources` — the semantic center of the module; `supportingResources` —\n resources that support without being the center). The resource inventory lives\n **inside** each module draft because an inventory is inherently *per module*.\n2. The **relationship drafts** — carried INSIDE the same domain-plan value — the **inter-resource relationship\n intents**: for each durable association between two inventoried resources, the\n two ends, the **cardinality intent** (one-to-one / one-to-many / many-to-one /\n many-to-many, read from source to target), and the **ownership direction**\n (which resource holds the reference). These are\n typed conceptual drafts — a relationship is not a module, so it earns its own\n family, and the build loop consumes it when it wires FK fields.\n\nThis is a **planning pass**. You name modules, the resources inside them, and how\nthey relate. You do **not** author schemas, resolve a cardinality intent into a\nconcrete foreign-key field, or generate any code — that is the **bottom-up build\nloop's** job, downstream of this plan.\n\n## Read state first — the definition set you read, the two artifacts you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before drafting\nanything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it. Confirm the top-down set is present\n and approved, and check whether a `domain-plan` already\n exist from an earlier run (refine them, do not re-author — see below).\n2. Read the approved definition set. **Load-bearing** (these drive the\n decomposition): the **requirements** (`requirements` family — the functional and\n non-functional requirements the domain must satisfy), the capability-mapped\n **MarketSnapshot** (`market-snapshot` — the benefits wired to their delivering\n features, so you know what capability each feature carries), and the\n **feature-drafts** (the prose capability contracts — what each delivering\n feature actually is). **Contextual** (they shape emphasis, not the core\n decomposition): the **roadmap** (`roadmap` — the release phasing, so you can see\n which modules are MVP-critical vs later) and the **VisionSnapshot**\n (`vision-brief` — the product framing and differentiation).\n\n\nYou **read** `requirements` + `market-snapshot` + `feature-drafts` + `roadmap` +\n`vision-brief`, and what the creator stated in the other interviews; you **write**\nthe `domain-plan` families.\n\n## Step 1 — Derive the modules (the decomposition)\n\nA **module** is a bounded slice of the app that delivers a coherent business\ncapability. Derive modules by **clustering** the definition set, not by guessing:\n\n1. **Cluster requirements and features by capability.** Group the functional\n requirements and the feature-drafts that serve one coherent capability (e.g.\n \"everything about authoring and tracking tasks\", \"everything about billing and\n plans\"). Each tight cluster is a candidate module. A feature-draft and the\n requirements it realises usually land in the same module.\n2. **Name each module and state its semantics.** For each candidate module author a\n `ModuleBusinessSemantics` draft: a `relatedModuleId` (the id the module registry\n will use — it must be **distinct across all module drafts**; two modules sharing\n an id silently collide, since the registry addresses modules by id), a `purpose`\n (why the module exists, in plain language), a\n `businessCapability` (the capability it delivers), the `primaryActors` (the\n human/business actors that interact with it), and — optionally — a\n `businessDomain` (the larger bounded-context label) and `integrationSurfaces`\n (named surfaces the module participates in).\n3. **Keep modules justified.** Every module must earn its existence from\n requirements or features in the definition set, or from a fact the creator\n stated that the requirements neither carry nor exclude (Step 2). Do **not** invent a module the\n definition set does not call for — a speculative module is a coherence CONCERN\n (see the quality gate). Conversely, a requirement or feature with no home is a\n coverage GAP — and its home is EITHER a module OR an entry of\n `engineRealizedRequirements` when the engine already provides it (Step 1b). Read\n Step 1b before concluding that a requirement needs a module.\n\nThe `resource-add-module` skill carries the module-scaffolding vocabulary (what a\nmodule is across the project layout); read it to keep module boundaries idiomatic.\n\n## Step 1b — Leave the engine's concerns to the engine\n\n### What the engine already provides — never a module, never a resource\n\nSome requirements are met by what every Wildo application already has, configured rather than built.\nA module or resource for one of them is read by nothing in the engine: it looks like the feature and\ndoes none of it. When a requirement falls in one of these areas, record it in the domain plan's\n`engineRealizedRequirements` (the requirement's ref, the concern below, and what the build still has to\nconfigure) instead of giving it a module home.\n\n| The requirement sounds like… | Concern (`realization`) | Where it is configured |\n|---|---|---|\n| \"office and field users see different things\", \"only administrators may…\", \"a read-only reviewer\" | `APPLICATION_ROLES` | the role table, the organization types that offer a role, each operation's `roles` — skill `application-roles-authoring` |\n| \"only a chartered / licensed / certified person may approve\", \"track our staff's certifications\" | `APPLICATION_ROLES` | a role, plus the qualification kinds a decision requires (`professionalQualificationKinds`, `requiredQualificationKinds`) and the organization's qualifications register — skill `professional-qualifications` |\n| \"invite colleagues\", \"manage the team\", \"departments\", \"regions\" | `ORGANIZATION_MEMBERSHIP` | the engine's members, invitations and organization units — skills `authorization-unit-narrowing`, `organization-relationships` |\n| \"see who changed what\", \"a history of changes\" | `AUDIT_TRAIL` | operation audit on each resource — skill `resource-config-wiring` |\n| \"GDPR\", \"a customer can ask for their data / its deletion\", \"keep records for N years\" | `PERSONAL_DATA` | personal-data declarations on fields, erasure, export and retention — skills `resource-config-wiring`, `resource-retention-binding` |\n| \"the privacy notice lists the purposes\", \"state the legal basis\", \"do not claim compliance with X\", country disclaimers | `GOVERNED_DOCUMENT` | a governed document composed from the product — skill `compliance-document-authoring` |\n| \"customers subscribe to a plan\" (the operator charging ITS customers) | `BILLING` | the billing catalogue — skill `configure-billing` |\n| \"guide new users\", \"celebrate the first…\" | `GUIDANCE` | onboarding guidance and milestones — skills `guidance-onboarding-authoring`, `milestones-and-celebrations` |\n| \"notify the office when…\", \"email the customer when…\" | `NOTIFICATIONS` | notifications declared on the operation that causes them — skills `resource-config-wiring`, `email-add-template` |\n| \"available in French and German\" | `LOCALIZATION` | the application's languages and generated labels — skill `i18n-label-generation` |\n\nTwo further rules, because both produced resources nothing reads:\n\n- **State derived from other records is never stored.** \"The next action for each customer\", \"what is\n overdue\", \"the stage a job is in\" are computed from the records that carry the work and shown in a\n view. A resource holding them by hand drifts from the records the moment either changes.\n- **A disclaimer is never a resource.** A criterion of the form \"does not claim X until Y\" or \"the product\n states its limits\" is a statement the operator makes (`GOVERNED_DOCUMENT`), not data a user types in.\n\nAn invoice the APPLICATION issues to its own customers (a trade business invoicing a homeowner) IS\nproduct domain and belongs in a module; `BILLING` is only the operator charging the application's\nsubscribers.\n\n\n`engineRealizedRequirements` is required: write `[]` when no requirement falls in these areas,\nso the plan says it looked. One entry per requirement and concern; a requirement can have a\nmodule home for its product part AND an engine entry for its access or privacy part (an invoice\nresource in a module, and `APPLICATION_ROLES` for \"only the office may issue invoices\").\n\n## Step 2 — Inventory the resources per module\n\nFor each module, list the **resources** (persisted entity types) it owns. The\ninventory is **two lists on the module draft**:\n\n- **`mainResources`** — the resources that form the semantic **center** of the\n module (the entities the module is *about*: a `tasks` module's `task`).\n- **`supportingResources`** — resources that **support** the module's capability\n without being its center (lookup tables, join/junction entities, per-entity\n settings). A resource that is the center of the module belongs in `mainResources`,\n not here.\n\nRules for a plausible inventory:\n\n- **Derive resources from the requirements + feature-drafts**, not from a blank\n page: a requirement that says \"users can label tasks\" implies a `task` resource\n and (probably) a `label` resource. The `resource-add-resource` skill carries the\n vocabulary for what a resource is; read it to keep the inventory idiomatic.\n- **What the creator stated reaches the inventory too.** Their answers to the\n other interviews arrive in the declared `creator_stated_facts` context section of your brief, and the\n requirements may have carried only part of them. Each stage of the stated\n workflow has a resource it happens on (a site visit, a quote, a job). A stated\n data class has a home: name the resource that holds a job-site address or a\n VAT number in its module's `purpose`, which is the only place this plan can\n say it (fields are the build's job, and the build reads the plan). A named\n e-invoicing or other regime has a module or resource that serves it, or\n belongs to the engine under Step 1b. Each stated user group is served by a\n module, and its access belongs to the engine. What the creator put out of\n scope, and a fact the requirements list in `excludedStatedFacts`, gets no\n module. A stated fact that neither the requirements carry nor exclude, and\n this plan does not carry, is a coverage GAP. Name it in the module's\n `purpose` or raise it as a clarification; never drop it.\n- **Each resource is inventoried in exactly one module** as its `mainResource`. A\n resource that is genuinely shared across modules is a signal you either have the\n module boundary wrong or you need a relationship (Step 3), not the same main\n resource duplicated in two modules.\n- **Never inventory what Step 1b leaves to the engine.** No resource holding roles,\n permissions or role assignments; no resource holding processing purposes, compliance\n declarations or country rules for users to type in; no resource holding a next action,\n a stage or a status copied from other records.\n- **Do not author fields or schemas here.** The inventory names the resource and\n says which module owns it. What fields the resource carries, its enums, its\n decorators — all of that is the **build loop's** job. If you catch yourself\n writing a field list, stop: that is out of this playbook's depth.\n\n## Step 3 — Draft the inter-resource relationships\n\nOnce the resources are inventoried, capture how they **relate**. For each durable\nassociation between two inventoried resources, author a **relationship draft** in\nthe relationship drafts (inside the domain-plan value) stating:\n\n- **The two ends** — the two resources that relate (both must be inventoried in\n some module's inventory from Step 2; a relationship to an un-inventoried resource\n is a coverage GAP).\n- **The cardinality intent** — one-to-one, one-to-many, many-to-one, or\n many-to-many, **always read from the source to the target**: *how many sources*\n to *how many targets*. \"Each `task` belongs to one `project`, a project has many\n tasks\", authored with `task` as the source and `project` as the target, is\n **many-to-one**. The same association authored with `project` as the source is\n **one-to-many**. This is an *intent*; you are not resolving it into a foreign-key\n placement here.\n- **The ownership direction** — which resource conceptually **holds** the reference\n (e.g. \"a `task` belongs to a `project`\" → the `task` end holds the reference).\n This is the *intent* the build loop needs; it does **not** decide the physical FK\n holder (that resolution — FK holder from cardinality, discriminator relationships,\n conditional relationships — is the `module-relationships` skill's job at build\n time, **not** here).\n- **The two must agree.** In a one-to-many or many-to-one association the **many**\n side holds the reference, so many-to-one goes with *source holds the reference*\n and one-to-many with *target holds the reference*. Deterministic validation\n refuses the other two combinations. Only one-to-one and many-to-many leave the\n holder to you. The simplest habit: make the resource that carries the reference\n the **source**, and the edge is many-to-one.\n- **Make the rationale say the same thing as the labels.** The relationship\n judge reads the rationale against the cardinality, so \"each customer has one\n country context, many customers share one\" belongs on a many-to-one edge from\n customer to country context.\n\nThe `module-relationships` skill carries the technical HOW of realising a\nrelationship (FK fields, cardinality-to-FK-holder resolution, conditional /\ndiscriminator relationships). Read it to keep your relationship *intents* aligned\nwith what the build loop can actually wire — but do **not** perform that wiring in\nthis planning pass.\n\n## Step 4 — Declare the lifecycles\n\nFor every resource the requirements describe moving through states — a quote that is sent and\naccepted, an invoice that is issued and paid, a case that is opened and closed — declare its\nlifecycle in `lifecycles`:\n\n- **`states`** — every state, upper snake case (`DRAFT`, `SENT`, `ACCEPTED`), and the\n **`initialState`** a new record starts in.\n- **`transitions`** — one per verb the business uses, as a lower-case slug (`send`, `accept`,\n `decline`, `issue`, `mark-paid`): the states it may start `from`, the state it moves `to`, and who\n performs it in the requirements' words. One verb is one transition: list every starting state in\n its `from`.\n- **`stampsField`** on a transition whose moment the business needs (when the quote was sent, when the\n invoice was paid): a camelCase timestamp field (`sentAt`, `paidAt`). `null` when nobody needs it.\n- **`createsResourceRef`** on a transition that creates another resource (accepting a quote\n creates a job). The created resource must be inventoried.\n- **`lockedStates`** — the states in which the record can no longer be EDITED but still moves on: an\n issued invoice (later marked paid), a sent quote (later accepted or declined). Empty when none.\n- **`finalStates`** — the TERMINAL states: nothing moves the record out of them, and it is not edited\n there either (a paid invoice, a closed case). Empty when nothing is ever final. No transition starts\n from a final state: a state you can leave is locked, not final.\n\n**When the application has a service method** (the firm's method, #2305), each service's CASE is a resource\nyou inventory: `case.caseRef` is its ref, listed in `mainResources` of the module the service's work belongs to,\nand its lifecycle is the case's `stages`, in order. Each stage ref becomes a state in upper snake case\n(`in-reconciliation` → `IN_RECONCILIATION`), the first stage is the `initialState`, and the transitions between\nthem are the business verbs the steps and decision points describe (\"sign the period off\" → `sign-off`). A stage a\ncase returns to (`reopened`) is a state with a transition back into it. The resources the steps read and produce\n(`readsRefs`, `producesRefs`) and the deliverables come from (`fromResourceRef`) are resources too. This is\nchecked: a case of more than one stage with no lifecycle, a stage that is not one of its states, or a deliverable\nproduced from a resource you did not inventory is reported against the domain plan.\n\nWrite `[]` when no resource moves through states. Read the requirements' verbs, not their nouns:\n\"an accepted quote can be used to create a job\" is a lifecycle (`accept`) and a conversion\n(`createsResourceRef: job`), not a foreign key. A value derived from other records — a next action,\nan overdue flag — is not a state of any resource (Step 1b).\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not rename or re-decompose modules\n that are already correct. Only add a module, move a resource to a different\n module, or add/correct a relationship where the plan genuinely changed.\n- **Reuse existing module ids.** A module that already exists keeps its\n `relatedModuleId` — never mint a second id for the same module. Likewise, keep a\n resource's name stable across runs.\n- **Never orphan a relationship.** A relationship draft must name two resources\n that are actually inventoried in Step 2. If you move or rename a resource, follow\n it into every relationship draft that references it.\n\n## Executable semantic evaluation — `domain-plan-output-set-result`\n\nThe staged output set first passes deterministic structural validation: exact\nmodule/resource identities, typed relationship ends, unique ownership, and the\natomic manifest must all be valid. That is a non-bypassable eligibility floor,\nnot a semantic quality opinion.\n\nThe companion then executes the playbook's structured semantic Treatment over\nthe exact staged output-set artifact. Its eight criteria remain distinct:\nrequirement coverage (a module home OR an engine realization), feature coverage,\nmodule justification, inventory plausibility, relationship integrity,\nplanning-depth boundary discipline, engine-concern discipline (no module or\nresource for what the engine provides, a disclaimer, or derived state), and\nlifecycle coverage (a requirement that moves a record through states has its\nlifecycle).\nEach criterion produces PASS / CONCERN / GAP / INDETERMINATE evidence, and the\nworst-verdict aggregation policy determines the Decision Rule consequence.\n\nA semantic PASS does **not** accept or publish the candidate. It transitions the\nresult Decision Point to `AUTHORITY_REQUIRED`; an explicit operator authority\ndecision is a separate later boundary. CONCERN or GAP requests revision,\nINDETERMINATE requests evidence, and evaluator or hard-floor failure blocks\nclosed. The evaluation path never mutates accepted specification heads.\n\n## Scaffold-depth boundary\n\nKeep this playbook at scaffold depth. Lifecycles (Step 4) are IN scope: they are what the\nresources DO, decided where the resources are, and nothing later decides them. Explicitly\n**out of scope here**:\n\n- **Schema / field authoring.** The inventory names resources and their owning\n module; it does **not** author fields, enums, decorators, or Zod schemas. That is\n the build loop. If you catch yourself writing a field list, stop.\n- **Cardinality-to-FK resolution.** A relationship draft states a cardinality\n *intent* and an ownership *intent* in prose. Resolving that into a physical\n foreign-key holder, a discriminator relationship, or a conditional relationship is\n the `module-relationships` skill's job **at build time**, not here.\n- **A full ERD / domain-graph solver.** Phases-of-a-graph, transitive dependency\n ordering, normalization analysis, and diagram generation are a later-phase\n concern. You draft modules, an inventory, and relationship intents — not a solved\n entity-relationship diagram.\n- **A full domain-graph solver.** The framework now ships a typed conceptual\n relationship-draft contract and deterministic structural validation for the\n atomic output set. It deliberately does not solve physical FK placement,\n normalization, graph execution order, discriminator relationships, or\n conditional relationships; those remain build-depth concerns.\n- **Code generation / module registration.** Scaffolding the module folders,\n registering the module across runtimes, generating resource files — all of that is\n the bottom-up build loop, downstream of this plan.\n\nIf you find yourself perfecting any of the above, stop: fields, physical foreign keys and\ngenerated code are the build's. What the build cannot invent — which states a resource has and\nwhich moves the business allows — is yours, in Step 4.\n\n## What you emit\n\nTwo artifacts for this journey:\n\n- The **domain-plan** under `specifications/src/domain-plan/` — a\n collection of `ModuleBusinessSemantics` drafts: the module decomposition, each\n module carrying its purpose, business capability, primary actors, and its\n `mainResources` / `supportingResources` inventory.\n- The **relationship drafts** inside the landed `specifications/src/domain-plan/` value\n — the inter-resource relationship intents (two ends + cardinality intent read\n source → target + ownership direction) between inventoried resources.\n\nAfter deterministic validation and semantic PASS, the runtime creates a distinct\nresult-bound Authority Request for the exact staged output-set digest. The local\noperator's explicit interface response settles that request; transition authority\ncannot substitute for it. Only then may the atomic specification-family mutation\naccept both files together for consumption by the bottom-up build loop.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `resource-add-module` — the module-scaffolding vocabulary\n (what a module is across the project layout); keeps module boundaries idiomatic.\n- `resource-add-resource` — the resource vocabulary (what a\n resource is); keeps the per-module inventory idiomatic.\n- `module-relationships` — the technical HOW of realising a\n relationship (FK fields, cardinality-to-FK-holder resolution, conditional /\n discriminator relationships) — consulted so relationship *intents* align with what\n the build loop can wire, NOT performed in this planning pass.\n",
|
|
51
54
|
"skillRefs": [
|
|
52
55
|
"resource-add-module",
|
|
53
56
|
"resource-add-resource",
|
|
@@ -68,7 +71,9 @@
|
|
|
68
71
|
}
|
|
69
72
|
]
|
|
70
73
|
},
|
|
71
|
-
"contextSources": [
|
|
74
|
+
"contextSources": [
|
|
75
|
+
"creator_stated_facts"
|
|
76
|
+
],
|
|
72
77
|
"draftableDocumentDefinitionRefs": [],
|
|
73
78
|
"suspendsForClarification": true,
|
|
74
79
|
"briefAdequacyGate": false,
|