@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
|
@@ -132,7 +132,7 @@ product, and `TASK_DECLARES_NO_PRODUCT` is the honest answer rather than a place
|
|
|
132
132
|
| `APPLICATION_VIEW` | `viewRef` | an app-level view. With an experience plan, the `viewRef` is the plan's own (`view-…`), verbatim |
|
|
133
133
|
| `APPLICATION_DOCUMENT` | `documentRef` | a governed document the engine catalog DEFINES — see the closed list below. Never a document you name yourself |
|
|
134
134
|
| `APPLICATION_MODULE` | `moduleRef` | an ensure-module task. The REGISTRY entry, not the directory |
|
|
135
|
-
| `APPLICATION_FRONTEND_CONFIG` | `configSurface` + the `declarationRefs` the file gains | composing ONE app-wide config file — `NAVIGATION`, `DESIGN_SYSTEM`, `APP_SHELL`, `GLOBAL_VIEWS`. The DECLARATIONS (a sidebar section ref, a zone, a token), never the file: `wildo init` writes
|
|
135
|
+
| `APPLICATION_FRONTEND_CONFIG` | `configSurface` + the `declarationRefs` the file gains | composing ONE app-wide config file — `NAVIGATION`, `DESIGN_SYSTEM`, `APP_SHELL`, `GLOBAL_VIEWS`, `SHELL_LAYOUT`. The DECLARATIONS (a sidebar section ref, a zone, a token, the one layout constant), never the file: `wildo init` writes every one of them |
|
|
136
136
|
| `RESOURCE_COMPOSITE_VIEW` | `resourceRef` + `viewRef` | a composite view of one resource, bound in its ui-behavior's `compositeViews`. The plan's `viewRef`, verbatim |
|
|
137
137
|
| `RESOURCE_CUSTOM_VIEW` | `resourceRef` + `viewRef` | a custom operation view or an execution view of one resource, bound in its ui-behavior. The plan's `viewRef`, verbatim — it is how the dispatch tells an execution view from a custom one |
|
|
138
138
|
| `RESOURCE_CHART_VIEW` | `resourceRef` + `chartRef` | a chart view declared under the resource's `chartViews` |
|
|
@@ -142,13 +142,20 @@ product, and `TASK_DECLARES_NO_PRODUCT` is the honest answer rather than a place
|
|
|
142
142
|
| `PDF_TEMPLATE` | `resourceRef` + `templateRef` | a PDF template BOUND to a resource's generated-file field (`generatedSummaryPdf`) |
|
|
143
143
|
| `APPLICATION_WORKER` | `workerRef` + the `jobRefs` its entry file declares | a worker's behaviour. The JOBS, not the package: `add-worker-node` / `add-worker-rust` write the package |
|
|
144
144
|
| `APPLICATION_MINION` | `minionRef` + the `behaviorRefs` its entry file declares | a minion's tick behaviour. Same rule: `add-minion` writes the package |
|
|
145
|
-
| `PROVIDER_BINDING` | `providerRef` + `scope` (`BACKEND`, `COMPANION`, `FRONTEND_APP`, `WEBSITE`) | one provider declared in one runtime owner's scope — the SaaS config block, or the service's `provider-contributions.ts` |
|
|
145
|
+
| `PROVIDER_BINDING` | `providerRef` + `scope` (`BACKEND`, `COMPANION`, `FRONTEND_APP`, `WEBSITE`), + `augments` when the binding has it | one provider declared in one runtime owner's scope — the SaaS config block, or the service's `provider-contributions.ts`. With `augments`, the module's opt-in under `providers.augmentations.<augments>` instead |
|
|
146
146
|
| `WEBSITE_PAGE` | `pageRef` | a marketing page, registered in `website-root.config.ts` by its manifest |
|
|
147
147
|
| `WEBSITE_SECTION` | `pageRef` + `sectionRef` | one section of one page, declared in `<pageRef>.sections.tsx` |
|
|
148
148
|
| `DOCUMENTATION_CHAPTER` | `chapterRef` | the chapter's authored body, keyed by its `chapterRef` in `specifications/src/technical-documentation/index.ts`, which `wildo docs publish` joins to the documentation plan and publishes under `/guides/<slug>` |
|
|
149
149
|
| `APPLICATION_BILLING_PRODUCT` | `productKey` | one product of the application's billing catalogue, named by its catalogue `key` (a slug, e.g. `team`) — declared in `shared-lib/src/engine/product.ts` under the `BILLING_CATALOG` target. The KEY, never the file: `wildo init` writes the file with an empty catalogue |
|
|
150
|
+
| `APPLICATION_ROLE` | `roleRef` | one role the application declares, named by its key in `CUSTOM_ROLES_CONFIGURATION` (upper snake case, e.g. `FIELD_TECHNICIAN`; never a core role such as `ORG_MEMBER`) — declared in `shared-lib/src/engine/roles.ts` under the `APPLICATION_ROLES` target. The NAME, never the file: `wildo init` writes the file with an empty table |
|
|
150
151
|
| `APPLICATION_DATA_SEED` | `seedKey` + `resourceRef` + `content` (`REFERENCE` or `DEMONSTRATION`) | one data seed a module declares, named by its key (`<moduleRef>:<purpose>`, e.g. `crm:demo-customers`) — the file `backend-api/src/modules/<moduleRef>/seeds/<seedKey with : as .>.seed.ts`, registered by the module. A `DEMONSTRATION` seed lands only once it declares the environments it runs in, without production |
|
|
151
152
|
| `INBOUND_CHANNEL_HANDLER` | `channel` + the handler's `handlerRef` (`<moduleRef>.<purpose>`, e.g. `matters.mail-intake`) | the handler that decides what a message arriving on a channel the integration plan declared causes. Its file is `backend-api/src/modules/<moduleRef>/inbound/<handlerRef>.inbound-channel-handler.ts`, and it lands when the module's backend `index.ts` imports that file — which is how it is registered on `inboundHandlers` |
|
|
153
|
+
| `APPLICATION_AGENT` | `agentRef` + `shape` (`CHAT_ASSISTANT`, `AUTONOMOUS`, `INVOKED`, `FLOW_STEP`) | one AI agent, named by the `ref` it is registered under (lower case, e.g. `tasks.overdue-triage`). An `AUTONOMOUS` agent is named by its autonomous declaration's `ref`, every other shape by the agent's own. It lands when the TASK'S module registers that ref (`flowsActors.agents`, or `autonomousAgents` for `AUTONOMOUS`) and the module's backend `index.ts`, its `addons/flows-actors/index.ts` and every file that index imports are committed. The shape also decides the skill the task is built with |
|
|
154
|
+
| `AGENT_APPROVAL_GATE` | `functionRef` + `route` (`owner`, `role`, `assignee`) + `eligibleRole` for `role` and `assignee` | the approval gate on one function tool an agent calls, named by the `functionRef` it is registered under — `resource.<resourceType>.<operation>` for a resource tool, with the resource type as the code spells it (`resource.adjustmentProposals.post`). Its calls wait for the person the route names. `owner` is the person whose turn it is and takes no role; `role` and `assignee` name the role the approver must hold (a role the application declares, or a core role). It lands only when the registered tool's gate has that route AND that role, so a gate routed to anyone else does not land |
|
|
155
|
+
| `WORK_UNIT_RESOURCE` | `resourceRef` | the resource whose rows are the application's CASES — the unit model spend is attributed to and cost per case is read by. It lands when the resource's configuration declares `workUnit: true` |
|
|
156
|
+
| `METERED_USAGE_RECORDING` | `resourceRef` + `operationRef` + `productKey` + `oncePerRecord`, and `serviceMethodServiceRef` when it bills a service of the firm's method | one operation of one resource that records usage of one METERED billing product when it succeeds (`recordsUsage` on the operation), named by the operation as the resource's configuration keys it (`record-sign-off` for `record_sign_off`) and the product's catalogue `key`. `oncePerRecord: true` counts each row once, which is what a price per case needs. It lands when the resource's configuration declares exactly that recording on that operation |
|
|
157
|
+
| `RESOURCE_RETENTION_BINDING` | `resourceRef` + `retentionClass` (`RESOURCE_DATA`, `FILES`, `AUDIT_LOGS`, `OPERATIONAL_LOGS`, `BUSINESS_RECORDS`) | how long one resource's rows are kept: its configuration's `retentionBinding` in that class. It lands when the resource's configuration declares that class |
|
|
158
|
+
| `RELATIONSHIP_CONFERRED_ROLE` | `relationshipRef` (the relationship kind's key, e.g. `service`) + `roleRef` | one role an organization relationship confers: in `wildo.saas.config.ts`, the kind's `confers.roles` holds it and every organization type the kind grants offers it in `availableOrgRoles`. Under the `APPLICATION_ROLES` target. It lands when the configuration, read fresh, says so |
|
|
152
159
|
|
|
153
160
|
**A GOVERNED DOCUMENT is chosen from a closed list, never invented.** There are six,
|
|
154
161
|
and a `documentRef` names one of them in exactly this form:
|
|
@@ -282,7 +289,7 @@ export enum BuildPlanTaskTargetKind {
|
|
|
282
289
|
MODULE_BACKEND = 'MODULE_BACKEND',
|
|
283
290
|
/**
|
|
284
291
|
* ONE application-wide frontend configuration surface — navigation, the design system, the app
|
|
285
|
-
* shell's composition, the global views — named by {@link FrontendConfigSurface}.
|
|
292
|
+
* shell's composition, the global views, the shell layout — named by {@link FrontendConfigSurface}.
|
|
286
293
|
*
|
|
287
294
|
* Distinct from {@link SHELL_PLACEMENT}, which authors the placement plan's decisions into the
|
|
288
295
|
* shell files: a placement puts a decided subject in a decided group, while this kind COMPOSES
|
|
@@ -321,12 +328,24 @@ export enum BuildPlanTaskTargetKind {
|
|
|
321
328
|
* catalogue, so the website re-typed the business model's prices by hand.
|
|
322
329
|
*/
|
|
323
330
|
BILLING_CATALOG = 'BILLING_CATALOG',
|
|
331
|
+
/**
|
|
332
|
+
* The application's own ROLES — `CUSTOM_ROLES_CONFIGURATION` in `shared-lib/src/engine/roles.ts`, the
|
|
333
|
+
* organization types that offer them (`availableOrgRoles` in `wildo.saas.config.ts`), their
|
|
334
|
+
* specifications, and the `roles` of the operations they unlock (#2490).
|
|
335
|
+
*
|
|
336
|
+
* Its own kind because none of the others reaches it: the role table is application-wide and lives in
|
|
337
|
+
* the shared library's ENGINE module. Before it existed a requirement naming user groups ("office and
|
|
338
|
+
* field users see different things") had no task able to declare a role, so app-creation-test-005
|
|
339
|
+
* modelled roles as an access-role RESOURCE that nothing reads.
|
|
340
|
+
*/
|
|
341
|
+
APPLICATION_ROLES = 'APPLICATION_ROLES',
|
|
324
342
|
}
|
|
325
343
|
|
|
326
344
|
/**
|
|
327
|
-
* WHICH application-wide frontend configuration surface a task composes — one file each
|
|
328
|
-
* `frontend/src/config/`,
|
|
329
|
-
* `SHELL_PLACEMENT` resolves
|
|
345
|
+
* WHICH application-wide frontend configuration surface a task composes — one file each (in
|
|
346
|
+
* `frontend/src/config/`, except the shell layout, whose one line lives in the engine registrations
|
|
347
|
+
* file), and the coding policy resolves the member to that file exactly as `SHELL_PLACEMENT` resolves
|
|
348
|
+
* a `PlacementSurface`.
|
|
330
349
|
*
|
|
331
350
|
* Its own vocabulary rather than a reuse of `PlacementSurface`: a placement surface is WHERE a
|
|
332
351
|
* subject sits in the shell (settings hub, sidebar, user menu, command palette), and three of
|
|
@@ -342,6 +361,14 @@ export enum FrontendConfigSurface {
|
|
|
342
361
|
APP_SHELL = 'APP_SHELL',
|
|
343
362
|
/** `frontend/src/config/global-views.config.ts` — the application-level launcher and view registrations. */
|
|
344
363
|
GLOBAL_VIEWS = 'GLOBAL_VIEWS',
|
|
364
|
+
/**
|
|
365
|
+
* `frontend/src/engine/component-registrations.frontend.ts` — the ONE animated 2D shell layout the application moves
|
|
366
|
+
* in (`register2DLayout(MORPH_LAYOUT_2D, { speed })`), decided beside the design system because both are the
|
|
367
|
+
* brand's: the design system its palette and pace, the layout how the shell moves at that pace. Its single
|
|
368
|
+
* declaration names the layout constant, written out. A 3D layout is never decided here: it is the operator's
|
|
369
|
+
* opt-in, through the `add-3d-layout` composition scenario.
|
|
370
|
+
*/
|
|
371
|
+
SHELL_LAYOUT = 'SHELL_LAYOUT',
|
|
345
372
|
}
|
|
346
373
|
|
|
347
374
|
/**
|
|
@@ -593,6 +620,71 @@ export enum BuildPlanTaskProductKind {
|
|
|
593
620
|
* registered. Produced once per channel the integration plan declares (`inboundChannels`).
|
|
594
621
|
*/
|
|
595
622
|
INBOUND_CHANNEL_HANDLER = 'INBOUND_CHANNEL_HANDLER',
|
|
623
|
+
/**
|
|
624
|
+
* One role the application declares, named by its role name (`FIELD_TECHNICIAN`), which is its key in
|
|
625
|
+
* `CUSTOM_ROLES_CONFIGURATION`. The NAME, not the file: `wildo init` writes `roles.ts` with an empty
|
|
626
|
+
* table, so the file proves nothing (#2490).
|
|
627
|
+
*/
|
|
628
|
+
APPLICATION_ROLE = 'APPLICATION_ROLE',
|
|
629
|
+
/*
|
|
630
|
+
* AGENT WORK (#2966). An agent, the approval gate on one of its tools, and the resource whose rows are the cases its
|
|
631
|
+
* work is costed to. None of them is a name the tree spells in one file: an agent's ref and a gate's role are written
|
|
632
|
+
* through constants in other files, and a gate is a property of a tool object. So each is proven from the REGISTRY the
|
|
633
|
+
* application's backend registers at startup, read through introspection, never from text.
|
|
634
|
+
*/
|
|
635
|
+
/**
|
|
636
|
+
* One AI agent the application registers, named by its `ref` — a chat agent's (`agents`) or an autonomous agent's
|
|
637
|
+
* (`autonomousAgents`), as its {@link BuildPlanAgentShape} says. Its shape also decides the skill it is built with.
|
|
638
|
+
*/
|
|
639
|
+
APPLICATION_AGENT = 'APPLICATION_AGENT',
|
|
640
|
+
/**
|
|
641
|
+
* The approval gate on one function tool (`humanApproval`): its calls wait for the person the ROUTE names, holding the
|
|
642
|
+
* role the gate requires. Proven when the registered tool's gate has that route and that role, so a gate routed to the
|
|
643
|
+
* wrong role, or a tool left ungated, does not land.
|
|
644
|
+
*/
|
|
645
|
+
AGENT_APPROVAL_GATE = 'AGENT_APPROVAL_GATE',
|
|
646
|
+
/**
|
|
647
|
+
* One resource declared as the application's unit of work (`workUnit: true`): its rows are the cases model spend is
|
|
648
|
+
* attributed to, and cost per case is read by them.
|
|
649
|
+
*/
|
|
650
|
+
WORK_UNIT_RESOURCE = 'WORK_UNIT_RESOURCE',
|
|
651
|
+
/**
|
|
652
|
+
* One operation of one resource that records usage of one METERED billing product when it succeeds (`recordsUsage`,
|
|
653
|
+
* #2305 S5). How a price per case is billed: the operation that closes a case records one unit, once per case. Proven
|
|
654
|
+
* from the registry like the agent work: the declaration is a property of one operation object in the resource's
|
|
655
|
+
* configuration, which no text in the tree ties to that operation.
|
|
656
|
+
*/
|
|
657
|
+
METERED_USAGE_RECORDING = 'METERED_USAGE_RECORDING',
|
|
658
|
+
/**
|
|
659
|
+
* One resource's rows bound to one of the application's retention classes (`retentionBinding`, #2305 S6): how long the
|
|
660
|
+
* firm's case evidence is kept. Proven from the registry: the binding is a property of the resource's configuration.
|
|
661
|
+
*/
|
|
662
|
+
RESOURCE_RETENTION_BINDING = 'RESOURCE_RETENTION_BINDING',
|
|
663
|
+
/**
|
|
664
|
+
* One role CONFERRED through one organization relationship kind (#2305 S6): the relationship's `confers.roles` holds it
|
|
665
|
+
* and every organization type the relationship grants offers it (`availableOrgRoles`). How the firm's people come to
|
|
666
|
+
* hold, for a client, the role a decision of its method requires. Proven from the application's configuration
|
|
667
|
+
* (`wildo.saas.config.ts`), read fresh at landing: the role is spelled through constants, so no text can prove it.
|
|
668
|
+
* "Conferred" is the kind's CEILING: each client still grants the role, or not, on its own relationship. And the fresh
|
|
669
|
+
* read re-evaluates the configuration and the files it imports by relative path; a value imported from a package is
|
|
670
|
+
* read from that package's build.
|
|
671
|
+
*/
|
|
672
|
+
RELATIONSHIP_CONFERRED_ROLE = 'RELATIONSHIP_CONFERRED_ROLE',
|
|
673
|
+
}
|
|
674
|
+
|
|
675
|
+
/**
|
|
676
|
+
* How an agent is started and talked to (#2966), which decides the skill it is built with
|
|
677
|
+
* ({@link BUILD_PLAN_AGENT_SHAPE_SKILL_REF}) and where its ref is registered.
|
|
678
|
+
*/
|
|
679
|
+
export enum BuildPlanAgentShape {
|
|
680
|
+
/** A person converses with it in the application. Registered under the module's `agents`. */
|
|
681
|
+
CHAT_ASSISTANT = 'CHAT_ASSISTANT',
|
|
682
|
+
/** It runs with nobody signed in: on a schedule, or when a message arrives. Registered under `autonomousAgents`. */
|
|
683
|
+
AUTONOMOUS = 'AUTONOMOUS',
|
|
684
|
+
/** The application's own code calls it once and uses its answer. Registered under `agents`. */
|
|
685
|
+
INVOKED = 'INVOKED',
|
|
686
|
+
/** One step of a declared flow. Registered under `agents`. */
|
|
687
|
+
FLOW_STEP = 'FLOW_STEP',
|
|
596
688
|
}
|
|
597
689
|
|
|
598
690
|
|
|
@@ -614,6 +706,36 @@ export enum BuildPlanDataSeedContent {
|
|
|
614
706
|
* A data seed's key: kebab-case segments joined by `:` (`crm:demo-customers`), the convention a
|
|
615
707
|
* `DataSeedDefinition` documents. Constrained here because the seed's FILE is derived from it.
|
|
616
708
|
*/
|
|
709
|
+
/**
|
|
710
|
+
* An application role's name, as `CUSTOM_ROLES_CONFIGURATION` keys it: upper snake case (`FIELD_TECHNICIAN`).
|
|
711
|
+
* A core role (`ORG_MEMBER`, `APP_ADMIN_SUPER_ADMIN`) is not something an application declares, so the
|
|
712
|
+
* product refuses one: a plan naming it would claim to create a role the engine already owns.
|
|
713
|
+
*/
|
|
714
|
+
export const APPLICATION_ROLE_NAME_PATTERN: RegExp = /^[A-Z][A-Z0-9]*(?:_[A-Z0-9]+)*$/;
|
|
715
|
+
/** Every role the ENGINE defines: an application role may not take one of these names, and a qualification may name one without declaring it. */
|
|
716
|
+
export const CORE_ROLE_NAMES: ReadonlySet<string> = new Set<string>([...Object.values(CORE_APP_ROLES), ...Object.values(CORE_ORG_ROLES)]);
|
|
717
|
+
|
|
718
|
+
/**
|
|
719
|
+
* An agent's or a function tool's ref: segments of letters and digits joined by `.`, `-` or `_`
|
|
720
|
+
* (`close-assistant.chat.agent`, `todos.overdue-triage`, `resource.adjustmentProposals.post`). Case is kept, because a
|
|
721
|
+
* tool ref follows the framework's `resource.<resourceType>.<operation>` convention and a multi-word resource type is
|
|
722
|
+
* camelCase. Constrained because the probe compares it EXACTLY with the registered ref: no space, no slash, no empty
|
|
723
|
+
* segment.
|
|
724
|
+
*/
|
|
725
|
+
export const AGENT_WORK_REF_PATTERN: RegExp = /^[A-Za-z0-9]+(?:[._-][A-Za-z0-9]+)*$/;
|
|
726
|
+
|
|
727
|
+
/**
|
|
728
|
+
* A step or a decision point of the firm's method (#2305), addressed as `<serviceRef>/<elementRef>`
|
|
729
|
+
* (`month-end-close/approve-posting`). A step's and a decision's ref are unique only within their service, so the
|
|
730
|
+
* service qualifies them; the `service-method` family declares both halves as kebab-case slugs.
|
|
731
|
+
*/
|
|
732
|
+
export const SERVICE_METHOD_ELEMENT_REF_PATTERN: RegExp = /^[a-z0-9]+(?:-[a-z0-9]+)*\/[a-z0-9]+(?:-[a-z0-9]+)*$/;
|
|
733
|
+
|
|
734
|
+
/** The ref a build-plan product carries for one step or decision point of the method (#2305). */
|
|
735
|
+
export function serviceMethodElementRef(serviceRef: string, elementRef: string): string {
|
|
736
|
+
return `${serviceRef}/${elementRef}`;
|
|
737
|
+
}
|
|
738
|
+
|
|
617
739
|
export const DATA_SEED_KEY_PATTERN: RegExp = /^[a-z0-9]+(?:-[a-z0-9]+)*(?::[a-z0-9]+(?:-[a-z0-9]+)*)*$/;
|
|
618
740
|
|
|
619
741
|
/**
|
|
@@ -676,6 +798,11 @@ export const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [
|
|
|
676
798
|
resourceRef: SlugSchema,
|
|
677
799
|
/** The generated-file FIELD the template is bound to (`generatedSummaryPdf`) — a symbol, so any spelling. */
|
|
678
800
|
templateRef: NonEmptyStringSchema,
|
|
801
|
+
/**
|
|
802
|
+
* #2305 S6: the deliverable of the firm's method this document is, as `<serviceRef>/<deliverableRef>`. Its resource
|
|
803
|
+
* must be the one the deliverable is produced from; the derivation check compares them.
|
|
804
|
+
*/
|
|
805
|
+
serviceMethodDeliverableRef: z.string().regex(SERVICE_METHOD_ELEMENT_REF_PATTERN).optional(),
|
|
679
806
|
}),
|
|
680
807
|
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_WORKER).systemEnum('BuildPlanTaskProductKind'), workerRef: SlugSchema, jobRefs: z.array(NonEmptyStringSchema).min(1) }),
|
|
681
808
|
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MINION).systemEnum('BuildPlanTaskProductKind'), minionRef: SlugSchema, behaviorRefs: z.array(NonEmptyStringSchema).min(1) }),
|
|
@@ -683,8 +810,20 @@ export const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [
|
|
|
683
810
|
kind: z.literal(BuildPlanTaskProductKind.PROVIDER_BINDING).systemEnum('BuildPlanTaskProductKind'),
|
|
684
811
|
providerRef: SlugSchema,
|
|
685
812
|
scope: z.enum(ProviderBindingScope).systemEnum('ProviderBindingScope'),
|
|
813
|
+
/**
|
|
814
|
+
* The provider this module adds operations to, copied from the integration plan's binding (#2025). Present, it
|
|
815
|
+
* changes what landing means: the application's opt-in under `providers.augmentations.<augments>` lists the module's
|
|
816
|
+
* package, rather than a scope naming `providerRef` (an augmentation writes no scope entry).
|
|
817
|
+
*/
|
|
818
|
+
augments: SlugSchema.optional(),
|
|
686
819
|
}),
|
|
687
820
|
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_BILLING_PRODUCT).systemEnum('BuildPlanTaskProductKind'), productKey: SlugSchema }),
|
|
821
|
+
z.strictObject({
|
|
822
|
+
kind: z.literal(BuildPlanTaskProductKind.APPLICATION_ROLE).systemEnum('BuildPlanTaskProductKind'),
|
|
823
|
+
roleRef: z.string().regex(APPLICATION_ROLE_NAME_PATTERN).refine((roleRef) => !CORE_ROLE_NAMES.has(roleRef), {
|
|
824
|
+
message: 'A core role is the engine\'s; an application role needs a name of its own.',
|
|
825
|
+
}),
|
|
826
|
+
}),
|
|
688
827
|
z.strictObject({
|
|
689
828
|
kind: z.literal(BuildPlanTaskProductKind.APPLICATION_DATA_SEED).systemEnum('BuildPlanTaskProductKind'),
|
|
690
829
|
seedKey: z.string().regex(DATA_SEED_KEY_PATTERN),
|
|
@@ -695,6 +834,83 @@ export const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [
|
|
|
695
834
|
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_PAGE).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema }),
|
|
696
835
|
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_SECTION).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema, sectionRef: SlugSchema }),
|
|
697
836
|
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.DOCUMENTATION_CHAPTER).systemEnum('BuildPlanTaskProductKind'), chapterRef: SlugSchema }),
|
|
837
|
+
z.strictObject({
|
|
838
|
+
kind: z.literal(BuildPlanTaskProductKind.APPLICATION_AGENT).systemEnum('BuildPlanTaskProductKind'),
|
|
839
|
+
/** The agent's `ref` exactly as it is registered (`close-assistant.chat.agent`, `todos.overdue-triage`). */
|
|
840
|
+
agentRef: z.string().regex(AGENT_WORK_REF_PATTERN),
|
|
841
|
+
shape: z.enum(BuildPlanAgentShape).systemEnum('BuildPlanAgentShape'),
|
|
842
|
+
/**
|
|
843
|
+
* The firm's method steps this agent carries (#2305), as `<serviceRef>/<stepRef>`: set when the application has a
|
|
844
|
+
* service method, so the derivation can be checked as total (every agent step has its agent). One agent may carry
|
|
845
|
+
* several steps; each must be an AGENT step of the same `shape`.
|
|
846
|
+
*/
|
|
847
|
+
serviceMethodStepRefs: z.array(z.string().regex(SERVICE_METHOD_ELEMENT_REF_PATTERN)).min(1).optional(),
|
|
848
|
+
/**
|
|
849
|
+
* The decision points of the firm's method this agent ASKS as a review question (an actor-system question routed
|
|
850
|
+
* to people when its run suspends), as `<serviceRef>/<decisionRef>` (#2305). A decision is realized either so or by
|
|
851
|
+
* a tool's approval gate (`serviceMethodDecisionRef`), never both: a review question IS the review, and its tool
|
|
852
|
+
* carries no gate. Its route is built by the agent's code when it suspends, so only the realization is checked here.
|
|
853
|
+
*/
|
|
854
|
+
serviceMethodAskedDecisionRefs: z.array(z.string().regex(SERVICE_METHOD_ELEMENT_REF_PATTERN)).min(1).optional(),
|
|
855
|
+
}),
|
|
856
|
+
z.strictObject({
|
|
857
|
+
kind: z.literal(BuildPlanTaskProductKind.AGENT_APPROVAL_GATE).systemEnum('BuildPlanTaskProductKind'),
|
|
858
|
+
/** The gated tool's `functionRef` exactly as it is registered (`resource.<resourceType>.<operation>` for a resource tool). */
|
|
859
|
+
functionRef: z.string().regex(AGENT_WORK_REF_PATTERN),
|
|
860
|
+
route: z.enum(HumanDecision_RouteKind).systemEnum('HumanDecision_RouteKind'),
|
|
861
|
+
/**
|
|
862
|
+
* The role every answerer must hold, as the role table keys it: required for a ROLE or ASSIGNEE route, refused for
|
|
863
|
+
* an OWNER route (answered by the person whose turn it is) — the engine's own rule for a gate, so a plan cannot name a
|
|
864
|
+
* gate the engine would refuse at startup.
|
|
865
|
+
*/
|
|
866
|
+
eligibleRole: z.string().regex(APPLICATION_ROLE_NAME_PATTERN).optional(),
|
|
867
|
+
/**
|
|
868
|
+
* The professional qualifications the answerer must ALSO hold (#2967), as the application's
|
|
869
|
+
* `professionalQualificationKinds` keys them: a ROLE or ASSIGNEE gate only, the engine's own rule. Landing compares
|
|
870
|
+
* them with the gate's, so a gate built without the qualification the plan required does not land.
|
|
871
|
+
*/
|
|
872
|
+
requiredQualificationKinds: z.array(z.string().regex(LABEL_KEY_SEGMENT_PATTERN)).min(1).optional(),
|
|
873
|
+
/**
|
|
874
|
+
* The decision point of the firm's method this gate realizes (#2305), as `<serviceRef>/<decisionRef>`: set when the
|
|
875
|
+
* application has a service method. Its route must be the decision's, its role the decision's qualification's
|
|
876
|
+
* role, and its qualifications that qualification's kind; the derivation check compares them.
|
|
877
|
+
*/
|
|
878
|
+
serviceMethodDecisionRef: z.string().regex(SERVICE_METHOD_ELEMENT_REF_PATTERN).optional(),
|
|
879
|
+
}).refine((gate) => (gate.route === HumanDecision_RouteKind.OWNER) === (gate.eligibleRole === undefined), {
|
|
880
|
+
message: 'An OWNER gate names no role; a ROLE or ASSIGNEE gate names the role its answerer must hold.',
|
|
881
|
+
path: ['eligibleRole'],
|
|
882
|
+
}).refine((gate) => gate.route !== HumanDecision_RouteKind.OWNER || gate.requiredQualificationKinds === undefined, {
|
|
883
|
+
message: 'An OWNER gate requires no qualification: its answerer is the person whose turn it is, whom nothing vets.',
|
|
884
|
+
path: ['requiredQualificationKinds'],
|
|
885
|
+
}),
|
|
886
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WORK_UNIT_RESOURCE).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema }),
|
|
887
|
+
z.strictObject({
|
|
888
|
+
kind: z.literal(BuildPlanTaskProductKind.METERED_USAGE_RECORDING).systemEnum('BuildPlanTaskProductKind'),
|
|
889
|
+
resourceRef: SlugSchema,
|
|
890
|
+
/** The operation that records, as the resource's configuration keys it (`record-sign-off` for `record_sign_off`). */
|
|
891
|
+
operationRef: SlugSchema,
|
|
892
|
+
/** The METERED product it records against: an `APPLICATION_BILLING_PRODUCT` of this plan, by its catalogue key. */
|
|
893
|
+
productKey: SlugSchema,
|
|
894
|
+
/** Whether it records at most once per row (`oncePerRecord`). A price per case counts each case once, however often it closes. */
|
|
895
|
+
oncePerRecord: z.boolean(),
|
|
896
|
+
/**
|
|
897
|
+
* #2305 S5: the service of the firm's method whose price PER CASE this records, by its `serviceRef`. Its resource must
|
|
898
|
+
* be that service's case and it must count once per row; the derivation check compares them.
|
|
899
|
+
*/
|
|
900
|
+
serviceMethodServiceRef: SlugSchema.optional(),
|
|
901
|
+
}),
|
|
902
|
+
z.strictObject({
|
|
903
|
+
kind: z.literal(BuildPlanTaskProductKind.RESOURCE_RETENTION_BINDING).systemEnum('BuildPlanTaskProductKind'),
|
|
904
|
+
resourceRef: SlugSchema,
|
|
905
|
+
retentionClass: z.enum(DataRetentionClass).systemEnum('DataRetentionClass'),
|
|
906
|
+
}),
|
|
907
|
+
z.strictObject({
|
|
908
|
+
kind: z.literal(BuildPlanTaskProductKind.RELATIONSHIP_CONFERRED_ROLE).systemEnum('BuildPlanTaskProductKind'),
|
|
909
|
+
/** The relationship kind, by its key in `organizationRelationships` (`service`). */
|
|
910
|
+
relationshipRef: SlugSchema,
|
|
911
|
+
/** The role conferred, by its key in the role table (`ORG_QUALIFIED_ACCOUNTANT`), a core role or the application's. */
|
|
912
|
+
roleRef: z.string().regex(APPLICATION_ROLE_NAME_PATTERN),
|
|
913
|
+
}),
|
|
698
914
|
z.strictObject({
|
|
699
915
|
kind: z.literal(BuildPlanTaskProductKind.INBOUND_CHANNEL_HANDLER).systemEnum('BuildPlanTaskProductKind'),
|
|
700
916
|
/** The channel the handler serves — one the integration plan declared. Email is the only declarable channel. */
|
|
@@ -774,6 +990,8 @@ export function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): r
|
|
|
774
990
|
return [`${product.kind}:${product.scope}:${product.providerRef}`];
|
|
775
991
|
case BuildPlanTaskProductKind.APPLICATION_BILLING_PRODUCT:
|
|
776
992
|
return [`${product.kind}:${product.productKey}`];
|
|
993
|
+
case BuildPlanTaskProductKind.APPLICATION_ROLE:
|
|
994
|
+
return [`${product.kind}:${product.roleRef}`];
|
|
777
995
|
// The key alone: two seeds may write one resource, and the key is what the seed run ledger tracks.
|
|
778
996
|
case BuildPlanTaskProductKind.APPLICATION_DATA_SEED:
|
|
779
997
|
return [`${product.kind}:${product.seedKey}`];
|
|
@@ -785,6 +1003,22 @@ export function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): r
|
|
|
785
1003
|
return [`${product.kind}:${product.chapterRef}`];
|
|
786
1004
|
case BuildPlanTaskProductKind.INBOUND_CHANNEL_HANDLER:
|
|
787
1005
|
return [`${product.kind}:${product.handlerRef}`];
|
|
1006
|
+
case BuildPlanTaskProductKind.APPLICATION_AGENT:
|
|
1007
|
+
return [`${product.kind}:${product.agentRef}`];
|
|
1008
|
+
// The TOOL alone: one tool has one gate, so two tasks gating it differently would make landing ambiguous.
|
|
1009
|
+
case BuildPlanTaskProductKind.AGENT_APPROVAL_GATE:
|
|
1010
|
+
return [`${product.kind}:${product.functionRef}`];
|
|
1011
|
+
case BuildPlanTaskProductKind.WORK_UNIT_RESOURCE:
|
|
1012
|
+
return [`${product.kind}:${product.resourceRef}`];
|
|
1013
|
+
// The operation and the product: one operation may record several products, and two tasks recording one product on
|
|
1014
|
+
// one operation would make landing ambiguous.
|
|
1015
|
+
case BuildPlanTaskProductKind.METERED_USAGE_RECORDING:
|
|
1016
|
+
return [`${product.kind}:${product.resourceRef}:${product.operationRef}:${product.productKey}`];
|
|
1017
|
+
// One resource has one binding, so two tasks binding it would make landing ambiguous.
|
|
1018
|
+
case BuildPlanTaskProductKind.RESOURCE_RETENTION_BINDING:
|
|
1019
|
+
return [`${product.kind}:${product.resourceRef}`];
|
|
1020
|
+
case BuildPlanTaskProductKind.RELATIONSHIP_CONFERRED_ROLE:
|
|
1021
|
+
return [`${product.kind}:${product.relationshipRef}:${product.roleRef}`];
|
|
788
1022
|
default: {
|
|
789
1023
|
const unhandled: never = product;
|
|
790
1024
|
throw new Error(`Unhandled build-plan task product ${JSON.stringify(unhandled)}.`);
|
|
@@ -796,10 +1030,18 @@ export function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): r
|
|
|
796
1030
|
* The skill every billing-catalogue task is authored with (#1835): the product-catalogue contract, the
|
|
797
1031
|
* money encoding (minor units), and the pricing-surface facts. The dispatch derives it from an
|
|
798
1032
|
* `APPLICATION_BILLING_PRODUCT` product whatever the decomposer wrote, so an agent writing the catalogue
|
|
799
|
-
* the backend sells from is never without it.
|
|
1033
|
+
* the backend sells from is never without it. A `METERED_USAGE_RECORDING` task carries it too (#2305 S5): the skill
|
|
1034
|
+
* says how an operation records usage of a metered product, and how a price per case counts each case once.
|
|
800
1035
|
*/
|
|
801
1036
|
export const BILLING_CATALOG_SKILL_REF = 'configure-billing';
|
|
802
1037
|
|
|
1038
|
+
/**
|
|
1039
|
+
* The skill every application-roles task is authored with (#2490): the role table, the organization
|
|
1040
|
+
* types that offer a role, and the operation roles that make it matter. The dispatch derives it from an
|
|
1041
|
+
* `APPLICATION_ROLE` product whatever the decomposer wrote.
|
|
1042
|
+
*/
|
|
1043
|
+
export const APPLICATION_ROLES_SKILL_REF = 'application-roles-authoring';
|
|
1044
|
+
|
|
803
1045
|
/**
|
|
804
1046
|
* The skill every data-seed task is authored with (#2234): levels, modes, business keys, and the
|
|
805
1047
|
* environment restriction that keeps demonstration rows out of production. The dispatch derives it from
|
|
@@ -807,6 +1049,55 @@ export const BILLING_CATALOG_SKILL_REF = 'configure-billing';
|
|
|
807
1049
|
*/
|
|
808
1050
|
export const DATA_SEED_SKILL_REF = 'seeding-authoring';
|
|
809
1051
|
|
|
1052
|
+
/**
|
|
1053
|
+
* The skill every PDF-template task is authored with (#2495): the template contract, the file field it fills, and
|
|
1054
|
+
* where the generated file is stored. The dispatch derives it from a `PDF_TEMPLATE` product whatever the decomposer
|
|
1055
|
+
* wrote.
|
|
1056
|
+
*/
|
|
1057
|
+
export const PDF_TEMPLATE_SKILL_REF = 'pdf-template-authoring';
|
|
1058
|
+
|
|
1059
|
+
/**
|
|
1060
|
+
* The skill a resource CONFIG task carries when the resource DECLARES personal data (#2495): its retention binding
|
|
1061
|
+
* lives in that configuration file, and storage limitation is a duty about personal data. The dispatch reads the
|
|
1062
|
+
* declaration from the resource's schema (the engine's personal-data markers), whatever the decomposer wrote.
|
|
1063
|
+
*/
|
|
1064
|
+
export const RESOURCE_RETENTION_SKILL_REF = 'resource-retention-binding';
|
|
1065
|
+
|
|
1066
|
+
/**
|
|
1067
|
+
* The skill a task conferring a role through an organization relationship is authored with (#2305 S6): the relationship
|
|
1068
|
+
* kind's `confers`, the granting types that must offer the role, and the startup checks that refuse a mismatch. The
|
|
1069
|
+
* dispatch derives it from a `RELATIONSHIP_CONFERRED_ROLE` product whatever the decomposer wrote.
|
|
1070
|
+
*/
|
|
1071
|
+
export const ORGANIZATION_RELATIONSHIPS_SKILL_REF = 'organization-relationships';
|
|
1072
|
+
|
|
1073
|
+
/**
|
|
1074
|
+
* The skill each agent shape is built with (#2966). The dispatch derives it from an `APPLICATION_AGENT` product whatever
|
|
1075
|
+
* the decomposer wrote. Total over {@link BuildPlanAgentShape}, so a shape added tomorrow must name its skill.
|
|
1076
|
+
*/
|
|
1077
|
+
export const BUILD_PLAN_AGENT_SHAPE_SKILL_REF: Readonly<Record<BuildPlanAgentShape, string>> = {
|
|
1078
|
+
[BuildPlanAgentShape.CHAT_ASSISTANT]: 'flows-actors-chat-assistant',
|
|
1079
|
+
[BuildPlanAgentShape.AUTONOMOUS]: 'flows-actors-autonomous-agents',
|
|
1080
|
+
[BuildPlanAgentShape.INVOKED]: 'flows-actors-llm-agent-invocation',
|
|
1081
|
+
[BuildPlanAgentShape.FLOW_STEP]: 'flows-actors-declared-flow',
|
|
1082
|
+
};
|
|
1083
|
+
|
|
1084
|
+
/**
|
|
1085
|
+
* The skill every agent and every approval gate is ALSO built with (#2966): what the agent's use is for, whether it
|
|
1086
|
+
* decides anything about a person, and its gated writes. An agent built from its shape skill alone is the undeclared,
|
|
1087
|
+
* unguarded shape.
|
|
1088
|
+
*/
|
|
1089
|
+
export const AI_USE_DECLARATION_SKILL_REF = 'ai-use-declaration';
|
|
1090
|
+
|
|
1091
|
+
/**
|
|
1092
|
+
* The skill an approval gate is built with (#2966): `flows-actors-chat-assistant` is where the `humanApproval` contract
|
|
1093
|
+
* is taught whole — the three routes, the eligible role, an assignee, escalation, deadlines and the review calendar —
|
|
1094
|
+
* whichever kind of agent calls the tool.
|
|
1095
|
+
*/
|
|
1096
|
+
export const AGENT_APPROVAL_GATE_SKILL_REF = 'flows-actors-chat-assistant';
|
|
1097
|
+
|
|
1098
|
+
/** The skill a work-unit task is built with (#2966): the `workUnit` declaration, model prices and the case passed to agent turns. */
|
|
1099
|
+
export const WORK_UNIT_SKILL_REF = 'model-cost-attribution';
|
|
1100
|
+
|
|
810
1101
|
export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
|
|
811
1102
|
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE), moduleRef: ModuleRefSchema }),
|
|
812
1103
|
z.strictObject({
|
|
@@ -864,6 +1155,7 @@ export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
|
|
|
864
1155
|
}),
|
|
865
1156
|
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.PROVIDER_BINDING), providerRef: SlugSchema }),
|
|
866
1157
|
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.BILLING_CATALOG) }),
|
|
1158
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.APPLICATION_ROLES) }),
|
|
867
1159
|
]);
|
|
868
1160
|
export type BuildPlanTaskTarget = z.infer<typeof BuildPlanTaskTargetSchema>;
|
|
869
1161
|
|
|
@@ -885,8 +1177,8 @@ export const BuildPlanTaskSchema = z.strictObject({
|
|
|
885
1177
|
* One sentence of intent: what this task delivers.
|
|
886
1178
|
*
|
|
887
1179
|
* Its OWN instance, not the file's shared leaf, which `templateRef` and the product ref lists also
|
|
888
|
-
* hold.
|
|
889
|
-
*
|
|
1180
|
+
* hold. The workbench's reading decorations are keyed by INSTANCE, and it gives those refs a receding
|
|
1181
|
+
* identifier look, which the objective sentence took too while it shared their leaf.
|
|
890
1182
|
*/
|
|
891
1183
|
objective: z.string().trim().min(1),
|
|
892
1184
|
target: BuildPlanTaskTargetSchema,
|
|
@@ -1106,7 +1398,7 @@ emit the ordered per-resource stage tasks:
|
|
|
1106
1398
|
|---|---|---|
|
|
1107
1399
|
| **(only when needed)** Ensure module `<id>` slice exists + is registered across runtimes — **normally already done by the foundation step**; emit this only for a module the foundation step did NOT establish (e.g. one added to the plan after foundation ran). Idempotent, never a blind re-scaffold | `model_domain_graph` | `resource-add-module` + `module-registration` |
|
|
1108
1400
|
| Resource `<name>` — domain schema (fields, enums, structural decorators). **Workspace-aware**: when the resource already exists as a compose-born starter (see the workspace section), the objective names the DOMAIN content to add to it; only a resource the workspace does not list gets a skeleton-creation objective | `model_domain_graph` | `resource-add-resource` (skeleton, only when the resource does not exist yet) + `resource-schema-authoring` (the persisted shape) + `application-database-migrations` (**PostgreSQL applications only** — see below) |
|
|
1109
|
-
| Resource `<name>` — config (registry presence, core operation verbs, access / role scope — but NOT cross-resource relationships, which are the dedicated Step 2 tasks) | `model_domain_graph` | `resource-config-wiring` |
|
|
1401
|
+
| Resource `<name>` — config (registry presence, core operation verbs, access / role scope — but NOT cross-resource relationships, which are the dedicated Step 2 tasks) | `model_domain_graph` | `resource-config-wiring` (plus `resource-retention-binding` when the resource declares personal data — the dispatch adds it whatever you write) |
|
|
1110
1402
|
| Resource `<name>` — ui-behavior (its read, form, summary and header surfaces and field chrome, each decided and stated — the resource's own UX) | `shape_user_experience` | `resource-ui-behavior` |
|
|
1111
1403
|
| Resource `<name>` — spec (canonical business semantics — the per-resource documentation capstone) | `model_domain_graph` | `spec-resource-update` |
|
|
1112
1404
|
|
|
@@ -1187,7 +1479,14 @@ tasks editing one file:
|
|
|
1187
1479
|
|
|
1188
1480
|
| Task | Functional topic | Skill (the HOW) |
|
|
1189
1481
|
|---|---|---|
|
|
1190
|
-
| Author the
|
|
1482
|
+
| Author the settings rail placement config from the accepted placement plan | `shape_user_experience` | `settings-placement-authoring` |
|
|
1483
|
+
| Author the sidebar, command palette or user menu placement config from the accepted placement plan | `shape_user_experience` | `config-app-shell` |
|
|
1484
|
+
|
|
1485
|
+
Bind by the FILE the surface is configured in. The settings rail is `settings-hub.config.ts`. The sidebar, the palette
|
|
1486
|
+
and the user menu (its `settingsEntries`) are `app-shell.config.ts`, and `settings-placement-authoring` itself sends
|
|
1487
|
+
work on them to `config-app-shell`: binding it there hands the agent a skill that tells it to go elsewhere. Only
|
|
1488
|
+
`config-app-shell` teaches `runtimeAvailability.requiredRoles`, which a sidebar group or entry the plan restricts to
|
|
1489
|
+
some roles needs.
|
|
1191
1490
|
|
|
1192
1491
|
Any task whose HOW includes **writing JSX for a bespoke surface** — a ui-behavior
|
|
1193
1492
|
stage, a custom or composite view, an app-level screen — binds
|
|
@@ -1227,7 +1526,9 @@ Rules:
|
|
|
1227
1526
|
|
|
1228
1527
|
- **This is the single home for cross-resource relationships.** A relationship is wired
|
|
1229
1528
|
ONCE, here, by the `module-relationships` skill (which coordinates the FK across the
|
|
1230
|
-
owner's schema + config, the target's relationship map,
|
|
1529
|
+
owner's schema + config, the target's relationship map, the owner's read and edit pages,
|
|
1530
|
+
and both specs coherently). The owner's UI task runs before the FK exists, so showing the
|
|
1531
|
+
reference on its pages is THIS task's work; say so in the objective. Do
|
|
1231
1532
|
NOT also wire it inside the per-resource config task in Step 1 — that config task
|
|
1232
1533
|
establishes the resource's registry presence and core verbs, not its cross-resource
|
|
1233
1534
|
FKs. Emitting the relationship in both places double-counts the work.
|
|
@@ -1259,6 +1560,114 @@ skills". Every skill name you emit MUST appear there, spelled exactly. Do **not*
|
|
|
1259
1560
|
skill name and do not recall one: a name that is not in that list addresses no skill
|
|
1260
1561
|
folder, and the task bound to it cannot be dispatched.
|
|
1261
1562
|
|
|
1563
|
+
### Every requirement verb becomes a task
|
|
1564
|
+
|
|
1565
|
+
Default verbs (create, read, update, list, delete) are what Step 1 already gives every resource.
|
|
1566
|
+
Everything a requirement says the product DOES beyond them is work this step must emit.
|
|
1567
|
+
|
|
1568
|
+
**Start with the domain plan's `lifecycles`.** Each declared transition is one `RESOURCE_OPERATION`
|
|
1569
|
+
task on its resource (target `RESOURCE_STAGE` CONFIG, `operationRef` = the `transitionRef`), skill
|
|
1570
|
+
`resource-status-lifecycle`, ordered after that resource's config task; its objective names the
|
|
1571
|
+
states it moves between and who performs it. A transition with `createsResourceRef` adds a
|
|
1572
|
+
`MODULE_BACKEND` task for the write that creates the target, skill `backend-custom-operation`,
|
|
1573
|
+
ordered after both resources' config tasks. The resource's SCHEMA task objective names the status
|
|
1574
|
+
enum with every declared state, the `initialState` as its default, and each transition's `stampsField`,
|
|
1575
|
+
all excluded from create and update: a transition is the only way to move them.
|
|
1576
|
+
For a resource with `lockedStates` or `finalStates`, the objective of each transition task that moves INTO
|
|
1577
|
+
one of them also restricts the resource's UPDATE to the states that are neither locked nor final. Never plan
|
|
1578
|
+
that freeze as its own `update` operation task: the scaffold already writes `update`, so such a task reads
|
|
1579
|
+
as built before it runs.
|
|
1580
|
+
|
|
1581
|
+
Then read every functional requirement's acceptance criteria for verbs no lifecycle carries, and
|
|
1582
|
+
classify each:
|
|
1583
|
+
|
|
1584
|
+
| The criterion says… | Emit | Skill |
|
|
1585
|
+
|---|---|---|
|
|
1586
|
+
| a record CHANGES STATE ("an accepted quote", "issue the invoice", "mark it paid", "close the case", "a submitted request can be approved") | one `RESOURCE_OPERATION` per transition, on the resource whose state changes, target `RESOURCE_STAGE` (CONFIG). Its objective names the states it moves between and who may call it | `resource-status-lifecycle` |
|
|
1587
|
+
| one record CREATES or FILLS another ("an accepted quote creates a job", "invoice the job") | a `RESOURCE_OPERATION` on the SOURCE resource, plus a `MODULE_BACKEND` task carrying the implementation that writes the target; ordered after both resources' config tasks | `backend-custom-operation` |
|
|
1588
|
+
| a record must not change any more ("an issued invoice cannot be edited") | the objective of the `RESOURCE_OPERATION` task for the transition into that locked or final state also restricts its UPDATE to the open states (never a separate `update` task, which the scaffold already writes) | `resource-status-lifecycle` |
|
|
1589
|
+
| a user group may or may not do something ("technicians cannot see invoices") | an `APPLICATION_ROLES` task (see below), or, for core roles alone, the config tasks' objectives | `application-roles-authoring` / `resource-config-wiring` |
|
|
1590
|
+
| only a QUALIFIED person may take a decision ("only a chartered accountant approves postings", "the reviewer must be licensed") | the `APPLICATION_ROLES` task for the role, and in the same task's objective the declared `professionalQualificationKinds` and the register's Settings placement; the task that raises the decision (an agent's gate, an operation's `requiresApproval`, a flow's person step) names `requiredQualificationKinds` beside its `eligibleRole` | `professional-qualifications` |
|
|
1591
|
+
| the product PRODUCES a document ("send the quote as a PDF", "print the invoice") | a `PDF_TEMPLATE` task bound to a generated-file field of that resource | `pdf-template-authoring` |
|
|
1592
|
+
| the product SENDS a message ("email the customer", "remind the office") | the `email-templates` generation step, and a `RESOURCE_OPERATION` task whose objective declares the notification on the operation that triggers it | `email-add-template` |
|
|
1593
|
+
| something is shown or computed from other records ("the next action", "what is overdue") | NOT a stored field: a view task from the experience plan, or a computed value in the owning resource's config task objective | — |
|
|
1594
|
+
| the product uses AI ("an assistant answers questions about…", "summarise", "classify automatically", "triage every morning", "an agent proposes, a person approves") | one `MODULE_BACKEND` task per AGENT, in the module whose records it reads, ordered after the config tasks of every resource its tools read or write. Its objective states the agent's use (what it is for, whether it decides anything about a person, who reviews), its `contentGuardrails` wherever they can treat something, and which of its writes wait for whose approval | the shape skill: `flows-actors-chat-assistant` (a person converses with it), `flows-actors-llm-agent-invocation` (your code calls it once), `flows-actors-autonomous-agents` (it runs with nobody signed in), `flows-actors-declared-flow` (a step of a flow) — AND `ai-use-declaration` |
|
|
1595
|
+
|
|
1596
|
+
An agent task always names BOTH skills: the shape skill builds it, and `ai-use-declaration` is what makes it
|
|
1597
|
+
declare its use — every agent carries `aiUse`, `contentGuardrails` and gated writes, and an agent built from
|
|
1598
|
+
the shape skill alone is the unguarded shape. The dispatch adds both from the task's products whatever you list.
|
|
1599
|
+
|
|
1600
|
+
An agent task DECLARES what it produces, so landing can prove it:
|
|
1601
|
+
|
|
1602
|
+
- one `APPLICATION_AGENT` product, with the `agentRef` the code will register and the `shape` the requirement
|
|
1603
|
+
describes (a person converses with it → `CHAT_ASSISTANT`; it runs on a schedule or when a message arrives →
|
|
1604
|
+
`AUTONOMOUS`; your code calls it once → `INVOKED`; a step of a flow → `FLOW_STEP`);
|
|
1605
|
+
- one `AGENT_APPROVAL_GATE` product for EVERY tool that changes something and waits for a person, with the
|
|
1606
|
+
route the requirement implies: "the person asking confirms" → `owner`; "a manager approves" → `role` with the
|
|
1607
|
+
role that group holds; "a chartered (licensed, certified) accountant approves" → `role` with that role AND
|
|
1608
|
+
`requiredQualificationKinds` naming the declared kind; "the account's partner signs off" → `assignee` with the
|
|
1609
|
+
role that person must hold. The role is the one an `APPLICATION_ROLE` product declares, or a core role, so a
|
|
1610
|
+
gate whose approver group has its own role is ordered after that roles task. An `owner` gate never names a role
|
|
1611
|
+
or a qualification.
|
|
1612
|
+
|
|
1613
|
+
An assistant's view is still its own `APPLICATION_VIEW` task from the experience plan.
|
|
1614
|
+
|
|
1615
|
+
When a requirement prices, budgets or reports cost PER CASE ("what each engagement costs us in AI", "margin per
|
|
1616
|
+
matter", "cost per ticket"), or names the record the agents' work is about ("each close", "each claim"), the
|
|
1617
|
+
config task of that resource also produces `WORK_UNIT_RESOURCE`, so every model call is attributed to its case.
|
|
1618
|
+
|
|
1619
|
+
### When the application has a service method, realize it whole
|
|
1620
|
+
|
|
1621
|
+
A firm's method (the `service-method` family, #2305) is the application's agent work written down, so read it
|
|
1622
|
+
before the requirement verbs above and realize every element of it:
|
|
1623
|
+
|
|
1624
|
+
- each service's CASE: the config task of the resource named by `case.caseRef` also produces
|
|
1625
|
+
`WORK_UNIT_RESOURCE` for it;
|
|
1626
|
+
- each step `performedBy: AGENT`: an `APPLICATION_AGENT` product in the step's `agentShape`, naming the step in
|
|
1627
|
+
`serviceMethodStepRefs` as `<serviceRef>/<stepRef>`. One agent may carry several steps of one shape;
|
|
1628
|
+
- each decision point, realized ONE way:
|
|
1629
|
+
- when a tool waits for the person's approval before it writes: an `AGENT_APPROVAL_GATE` product on that tool,
|
|
1630
|
+
naming the decision in `serviceMethodDecisionRef` as `<serviceRef>/<decisionRef>`, with the decision's `route`,
|
|
1631
|
+
its qualification's `role` as `eligibleRole` (none for `owner`), and its qualification's
|
|
1632
|
+
`professionalQualificationKind` as the only entry of `requiredQualificationKinds` (none when it names none);
|
|
1633
|
+
- when the agent ASKS the person and continues from the answer (a review question its run suspends on, such as
|
|
1634
|
+
choosing which document pays a bank line): the agent's `APPLICATION_AGENT` product names the decision in
|
|
1635
|
+
`serviceMethodAskedDecisionRefs`, and the task's objective says the question's route and role. Its tool has no
|
|
1636
|
+
gate: the question is the review;
|
|
1637
|
+
- either way, its `decisionDeadline` goes in the task's objective, which the gate's or the question's deadlines are
|
|
1638
|
+
built from;
|
|
1639
|
+
- each qualification's role: an engine role, or an `APPLICATION_ROLE` product. The `APPLICATION_ROLES` task declares
|
|
1640
|
+
every `professionalQualificationKind` the method names in `professionalQualificationKinds`, and is emitted for that
|
|
1641
|
+
even when every qualification's role is an engine role;
|
|
1642
|
+
- each service with `pricing: PER_CASE`: the billing catalogue task produces a METERED product for it (its
|
|
1643
|
+
`productKey` names the case, priced per unit), and a task on the case resource produces a `METERED_USAGE_RECORDING`
|
|
1644
|
+
on the operation that CLOSES the case (`case.closesWhen` says which), with that `productKey`, `oncePerRecord: true`
|
|
1645
|
+
and the service in `serviceMethodServiceRef`. Order it after the catalogue task and after the case's closing
|
|
1646
|
+
operation exists. A service priced `INCLUDED_IN_PLAN` or `BILLED_OUTSIDE` records nothing;
|
|
1647
|
+
- each deliverable: a `PDF_TEMPLATE` product on the resource the deliverable is produced from (`fromResourceRef`), bound
|
|
1648
|
+
to its generated-file field, naming the deliverable in `serviceMethodDeliverableRef` as `<serviceRef>/<deliverableRef>`;
|
|
1649
|
+
- the case's evidence: the config task of the case resource, and of each deliverable's resource, also produces a
|
|
1650
|
+
`RESOURCE_RETENTION_BINDING` in the service's `evidenceRetention.retentionClass`. A `BUSINESS_RECORDS` binding also
|
|
1651
|
+
declares the statutory retention policy (the `resource-retention-binding` skill says how; the dispatch adds it);
|
|
1652
|
+
- each qualification the firm's people hold for the client (`heldBy: FIRM`), unless its role is `ORG_REPRESENTATIVE`
|
|
1653
|
+
(conferred already): the `APPLICATION_ROLES` task also produces a `RELATIONSHIP_CONFERRED_ROLE` for its role on the
|
|
1654
|
+
relationship the firm serves its clients through (`service` in the configuration's `organizationRelationships`). The
|
|
1655
|
+
firm's people hold that role for a client only through the relationship: the task adds it to the kind's
|
|
1656
|
+
`confers.roles` and offers it on every organization type the kind grants. A role the client's own staff hold
|
|
1657
|
+
(`heldBy: CLIENT`) is offered on the client's organization type and conferred nowhere.
|
|
1658
|
+
|
|
1659
|
+
This is checked at landing: a plan that leaves a case without its work unit, an agent step without its agent or a
|
|
1660
|
+
decision point unrealized (or a gate with another route, role or qualification), or a service priced per case with
|
|
1661
|
+
no recording of its case (or one recording elsewhere, every run, or a product the catalogue does not sell), a
|
|
1662
|
+
deliverable with no document, a case's evidence unbound or bound to another class, or a firm-held role no
|
|
1663
|
+
relationship confers is refused, with the list of what is missing. A case's lifecycle that lacks one of its stages is
|
|
1664
|
+
the domain plan's to fix, and is reported rather than refused. A case the domain plan does not declare is the domain plan's to fix, and is reported rather than refused. Name the method's services in `servesRefs` only where a requirement also justifies the task.
|
|
1665
|
+
|
|
1666
|
+
A task emitted from a requirement verb is justified by that requirement: name it in `servesRefs`.
|
|
1667
|
+
It is never the "justified by nothing" speculative work the rule further down warns about. A plan
|
|
1668
|
+
whose requirements describe a workflow and which carries no `define_interaction_semantics` task is
|
|
1669
|
+
not a lighter plan — it is a CRUD shell, and the reviewer reports it as a gap.
|
|
1670
|
+
|
|
1262
1671
|
**Every surface below has its own target kind and its own product kind. Use them.**
|
|
1263
1672
|
Until 2026-09-22 only resources had a vocabulary, so a task for any of these surfaces
|
|
1264
1673
|
either declared no product (and could never be proven landed) or borrowed `MODULE`
|
|
@@ -1270,7 +1679,8 @@ replaced — the judge reports it as a gap.
|
|
|
1270
1679
|
role / scope rules, rate limits — interaction beyond the default resource verbs.
|
|
1271
1680
|
Target `RESOURCE_STAGE` (CONFIG), product `RESOURCE_OPERATION`. Skills: the Backend and
|
|
1272
1681
|
Resources domains of the router (`backend-custom-operation`, `rate-limit-authoring`,
|
|
1273
|
-
`authorization-unit-narrowing`).
|
|
1682
|
+
`authorization-unit-narrowing`). **Derive these from the requirements' VERBS** — read
|
|
1683
|
+
"Every requirement verb becomes a task" below before emitting anything else in this step.
|
|
1274
1684
|
- **`shape_user_experience`** — the cross-resource UX, and you do NOT decide it here. The
|
|
1275
1685
|
**experience plan** (`bottom_up.experience-plan`) already did: which surfaces exist, what
|
|
1276
1686
|
each is for, which presets it reuses, and how the shell, navigation, design system and
|
|
@@ -1288,7 +1698,18 @@ replaced — the judge reports it as a gap.
|
|
|
1288
1698
|
- one task per CONFIGURATION, target `APPLICATION_FRONTEND_CONFIG` with that surface,
|
|
1289
1699
|
product `APPLICATION_FRONTEND_CONFIG` naming the surface's own `declarationRefs`, and
|
|
1290
1700
|
its skill the one the surface names (`config-navigation`, `config-design-system`,
|
|
1291
|
-
`config-app-shell
|
|
1701
|
+
`config-app-shell`, `layout-2d-adoption` for the shell layout; `views-app-level` for global views
|
|
1702
|
+
— derived at dispatch too). A shell layout task depends on the design-system task when both are
|
|
1703
|
+
planned: the layout moves at the theme's pace.
|
|
1704
|
+
When the plan decides a `home`, the `GLOBAL_VIEWS` task sets it: its objective says to make
|
|
1705
|
+
`homeDefinitionFactory` in `frontend/src/config/global-views.config.ts` return that home, carrying
|
|
1706
|
+
the home's rationale. A `VIEW` home is an application view: `{ compositeViewReference: <the view's
|
|
1707
|
+
ref constant> }`, and the task depends on the task that builds that view. A `RESOURCE_OPERATION`
|
|
1708
|
+
home is `{ resourceOperationPath: … }` naming the resource's registered type (camelCase, not the
|
|
1709
|
+
slug), the operation, `isOperationDefault: true`, `isBulkOperation: false` and the default variant's
|
|
1710
|
+
`variantKey`: the root matches all of them exactly and silently shows the welcome page on a
|
|
1711
|
+
mismatch. That task depends on the resource's config task. Without the home the application opens
|
|
1712
|
+
on the framework's welcome page whatever the plan says.
|
|
1292
1713
|
- one task per planned MILESTONE, target `MODULE_BACKEND` on the milestone's module,
|
|
1293
1714
|
product `APPLICATION_MILESTONE` naming its `milestoneRef`, skill
|
|
1294
1715
|
`milestones-and-celebrations` (`EXPERIENCE_MILESTONE_SKILL_REF`). It depends on the config stage of its
|
|
@@ -1318,7 +1739,7 @@ replaced — the judge reports it as a gap.
|
|
|
1318
1739
|
- a custom UI component / widget → target `MODULE_FRONTEND`, product `CUSTOM_COMPONENT`;
|
|
1319
1740
|
skills `engine-component-registration`, `frontend-component-catalog`;
|
|
1320
1741
|
- a PDF template / renderer → target `MODULE_BACKEND`, product `PDF_TEMPLATE`; skill
|
|
1321
|
-
`pdf-template-authoring
|
|
1742
|
+
`pdf-template-authoring` (the dispatch adds it whatever you write);
|
|
1322
1743
|
- custom backend implementation logic → target `MODULE_BACKEND`, product the
|
|
1323
1744
|
`RESOURCE_OPERATION` it serves; skill `backend-addon-wiring`;
|
|
1324
1745
|
- workers and minions → you do NOT decide them here. The **integration plan**
|
|
@@ -1346,12 +1767,32 @@ replaced — the judge reports it as a gap.
|
|
|
1346
1767
|
- **`connect_runtime_and_external_capabilities`** — providers and external connectors,
|
|
1347
1768
|
and the **integration plan** decided these too: one task per PROVIDER BINDING it
|
|
1348
1769
|
declares, target `PROVIDER_BINDING`, product `PROVIDER_BINDING` with the binding's own
|
|
1349
|
-
`scope`, and its skill taken from that scope through
|
|
1770
|
+
`scope` (and its `augments`, copied as written: it is what that task is judged landed by), and its skill taken from that scope through
|
|
1350
1771
|
`INTEGRATION_PROVIDER_BINDING_SKILL_REF` — do not choose it yourself, the map is total
|
|
1351
1772
|
over the scope vocabulary. The binding's `rationale` is the task's objective. Reach for
|
|
1352
1773
|
`provider-operation-calls` and `configure-billing` as the task's further reading when the
|
|
1353
1774
|
binding is one an application then CALLS. Environment and infra config are the
|
|
1354
1775
|
foundation's, not a build task's.
|
|
1776
|
+
- **What the domain plan left to the engine** — its `engineRealizedRequirements` name the
|
|
1777
|
+
requirements met by configuration rather than a module. Each still owes configuration work:
|
|
1778
|
+
`APPLICATION_ROLES` → the roles task below; `NOTIFICATIONS` → the triggering operation's task
|
|
1779
|
+
(the verb table above); `PERSONAL_DATA` and `AUDIT_TRAIL` → the declarations in the resource
|
|
1780
|
+
config tasks' objectives; `BILLING` → the billing catalogue task; `GUIDANCE` → the experience
|
|
1781
|
+
plan's guidance tasks; `GOVERNED_DOCUMENT` → no build task (the compliance lane composes it);
|
|
1782
|
+
`ORGANIZATION_MEMBERSHIP` and `LOCALIZATION` → no task beyond the foundation's capabilities.
|
|
1783
|
+
Never emit a task that builds one of these as a resource.
|
|
1784
|
+
- **The application roles** — target `APPLICATION_ROLES`, when a requirement names groups of
|
|
1785
|
+
users with different access ("office and field staff", "technicians cannot see invoices",
|
|
1786
|
+
"read-only reviewers"). Emit ONE task (the role table is one file) producing one
|
|
1787
|
+
`APPLICATION_ROLE` per group that no core role covers, skill `application-roles-authoring`
|
|
1788
|
+
(the dispatch adds it whatever you write), and `servesRefs` naming the requirement. Reuse the
|
|
1789
|
+
core roles first: the broadest internal group usually holds `ORG_MEMBER`, and a requirement met by
|
|
1790
|
+
them alone ("only administrators may delete") needs no roles task, only config tasks that say which
|
|
1791
|
+
operations are restricted. The task declares the roles, offers them on the organization types,
|
|
1792
|
+
and narrows the `roles` of the operations they govern, so order it AFTER the config tasks of every
|
|
1793
|
+
resource it narrows, and say in its objective which operations each role may call. Never answer a
|
|
1794
|
+
role requirement with a resource holding roles, permissions or role assignments: nothing in the
|
|
1795
|
+
engine reads it.
|
|
1355
1796
|
- **The billing catalogue** — target `BILLING_CATALOG`, and the **business model** decided it:
|
|
1356
1797
|
its pricing plans are the products the application sells. Emit ONE task (the catalogue is one
|
|
1357
1798
|
file, so two tasks would write over each other) producing one `APPLICATION_BILLING_PRODUCT` per
|
|
@@ -1365,7 +1806,9 @@ replaced — the judge reports it as a gap.
|
|
|
1365
1806
|
is announced but the requirements do not yet build it. Order it after the module and resource
|
|
1366
1807
|
tasks whose features the plans grant. The website's PRICING section task depends on it: the
|
|
1367
1808
|
section reads this catalogue, so it must exist first. No business model, or one with no plans,
|
|
1368
|
-
emits nothing.
|
|
1809
|
+
emits nothing. A plan priced `per_usage` is a METERED product, priced per unit of its `usageUnit`
|
|
1810
|
+
(the objective names the unit); its usage is recorded by a `METERED_USAGE_RECORDING` task on the
|
|
1811
|
+
operation that consumes it, ordered after this one.
|
|
1369
1812
|
- **Data seeds** — target `MODULE_BACKEND` on the seed's module, product `APPLICATION_DATA_SEED`,
|
|
1370
1813
|
skill `seeding-authoring` (the dispatch adds it whatever you write). A built application must not
|
|
1371
1814
|
open EMPTY: an empty list is not something a creator can judge, try or show. Emit two kinds, and
|
|
@@ -1378,9 +1821,15 @@ replaced — the judge reports it as a gap.
|
|
|
1378
1821
|
plausible records (three to eight) for each main resource a person meets first, in the market's
|
|
1379
1822
|
own language and examples, consistent with each other (an enquiry names a customer that exists).
|
|
1380
1823
|
One seed per resource. The seed declares `allowedApplicationEnvironments` without production,
|
|
1381
|
-
and the task lands only once it does, so these rows can never sit beside real ones.
|
|
1382
|
-
|
|
1383
|
-
|
|
1824
|
+
and the task lands only once it does, so these rows can never sit beside real ones. A resource
|
|
1825
|
+
that belongs to an organization is seeded per organization, on organization creation.
|
|
1826
|
+
A seed whose rows point at rows ANOTHER seed writes (a contact's customer, a quote's customer, an
|
|
1827
|
+
invoice's job) links them with `referenceDataSeedRow` and lists that seed in `dependsOn` — the
|
|
1828
|
+
engine resolves each reference to the row's `_id`, and nothing else can, because the id is
|
|
1829
|
+
generated. Say so in the task's objective: name the seed it references and the field each
|
|
1830
|
+
reference fills, so the worker does not have to discover the mechanism. Order a seed after its
|
|
1831
|
+
resource's schema and config tasks, after the relationship tasks for the links its rows carry,
|
|
1832
|
+
and after the task of every seed whose rows it references. Name each `seedKey`
|
|
1384
1833
|
`<moduleRef>:<purpose>` (`crm:demo-customers`): the namespace keeps one module's seeds apart from
|
|
1385
1834
|
another's. Never a seed for a resource the engine owns (users, organizations, memberships).
|
|
1386
1835
|
- **The website** — target `WEBSITE`, and you do NOT decide its content here. The
|
|
@@ -1389,18 +1838,24 @@ replaced — the judge reports it as a gap.
|
|
|
1389
1838
|
emit, in this order:
|
|
1390
1839
|
- one `WEBSITE_PAGE` task per page (`produces: { kind: WEBSITE_PAGE, pageRef }`), skill
|
|
1391
1840
|
`website-page-authoring`, its objective the page's own purpose. A page task authors the
|
|
1392
|
-
PAGE — route
|
|
1393
|
-
|
|
1394
|
-
|
|
1841
|
+
PAGE — route (derived from the page's KIND: `/product/<slug>`, `/solutions/<slug>`, …),
|
|
1842
|
+
bridge, component, manifest, registration, its own entry in the site menu, and an EMPTY
|
|
1843
|
+
sections list — and never its sections: say so in the objective. On the first run that
|
|
1844
|
+
built a website the page tasks wrote every section themselves, so no section skill was
|
|
1845
|
+
ever applied. A `PRODUCT_OVERVIEW` page task comes after every `PRODUCT` page task: its
|
|
1846
|
+
menu link is the Product panel's overview, and the panel exists once its first product
|
|
1847
|
+
page does (the dispatch host derives that edge from the plan, so you need not write it);
|
|
1395
1848
|
- one `WEBSITE_SECTION` task per section (`produces: { kind: WEBSITE_SECTION, pageRef,
|
|
1396
1849
|
sectionRef }`), **with its page's task as a prerequisite** — a section is declared in
|
|
1397
1850
|
its page's sections file, so the page must exist first — and its skill taken from the
|
|
1398
|
-
section's KIND through `WEBSITE_SECTION_SKILL_REF
|
|
1399
|
-
`
|
|
1400
|
-
`
|
|
1401
|
-
`website-section-
|
|
1402
|
-
|
|
1403
|
-
`
|
|
1851
|
+
section's KIND through `WEBSITE_SECTION_SKILL_REF`, which gives every kind one: the kind's
|
|
1852
|
+
name in kebab case after `website-section-` (`HERO` → `website-section-hero`,
|
|
1853
|
+
`FEATURE_BENEFIT_SUMMARY` → `website-section-feature-benefit-summary`, `LATEST_POSTS` →
|
|
1854
|
+
`website-section-latest-posts`, and so on for all eighteen kinds, `STATS`, `INTEGRATIONS`
|
|
1855
|
+
and `ROADMAP` included). A
|
|
1856
|
+
`SOLUTION_PATHS` section comes after every `SOLUTION` page task: its cards link to those
|
|
1857
|
+
pages, and nothing at build checks a section's links, so built first it would publish links
|
|
1858
|
+
to pages that do not exist yet (the dispatch host derives that edge too). Name the skill; the
|
|
1404
1859
|
dispatch derives the same skill from the plan and puts it first whatever you wrote, so a
|
|
1405
1860
|
wrong one is harmless but a right one keeps the plan readable.
|
|
1406
1861
|
A plan whose disposition is `NOT_APPLICABLE`, or no plan at all, emits NOTHING here — the
|
|
@@ -1439,7 +1894,8 @@ Rules:
|
|
|
1439
1894
|
in Step 1 and needs only that resource's schema/config — see the ordering axes.)
|
|
1440
1895
|
- **Draw tasks from the definition set, not a blank page.** A UX or operation task
|
|
1441
1896
|
earns its existence from a requirement or feature-draft; a task justified by nothing
|
|
1442
|
-
in the definition set is a CONCERN (speculative work).
|
|
1897
|
+
in the definition set is a CONCERN (speculative work). A task serving a requirement verb
|
|
1898
|
+
(the table above) always earns it, even when no feature-draft mentions the operation.
|
|
1443
1899
|
|
|
1444
1900
|
## Step 4 — Interleave the companion-owned generation steps
|
|
1445
1901
|
|
|
@@ -1484,6 +1940,15 @@ surfaces whose output they consume**:
|
|
|
1484
1940
|
migration. It needs a BUILT `backend-api`, because the plan is computed by importing the compiled
|
|
1485
1941
|
registry; it refuses on an unbuilt tree instead of authoring a migration for a model nobody has.
|
|
1486
1942
|
|
|
1943
|
+
- **`design-system-brand` and `design-tokens`** — derived by the dispatch host around every
|
|
1944
|
+
DESIGN_SYSTEM config task, so do **not** author either. The brand step runs before that task and
|
|
1945
|
+
writes the brand's palette seeds and theme personality to `frontend/src/config/brand-design.ts`, and,
|
|
1946
|
+
when the application has a website, the same palette and point to `website/src/brand-theme.ts`; the
|
|
1947
|
+
tokens step runs after it and regenerates the stylesheet's design-token block from the config. The
|
|
1948
|
+
DESIGN_SYSTEM task itself derives its palette from those seeds and composes its theme from that
|
|
1949
|
+
personality rather than choosing colours or copying a theme (the `config-design-system` skill shows
|
|
1950
|
+
how), so name that skill on it.
|
|
1951
|
+
|
|
1487
1952
|
There is no seeds GENERATION step: do **not** author one — an unknown `generationStepRef`
|
|
1488
1953
|
refuses at dispatch instead of parking the build. Seeding is a CODING task: an
|
|
1489
1954
|
`APPLICATION_DATA_SEED` product under the module's backend (Step 3, "Data seeds").
|
|
@@ -1605,6 +2070,6 @@ what reaches you is this method, your declared inputs, and the brief's own secti
|
|
|
1605
2070
|
|
|
1606
2071
|
## Reviewer checklist — `build-plan-coherent`
|
|
1607
2072
|
|
|
1608
|
-
These
|
|
2073
|
+
These twelve invariants are the criteria of this playbook's compiled evaluation treatment (`application-creation:evaluation-treatment/build-plan-coherent`, one criterion per invariant, invariants 2 and 2b sharing one), which the advisory judge runs after every landing. They are kept here as creator-facing review guidance too, so a reviewer and the judge read the same words:
|
|
1609
2074
|
|
|
1610
|
-
Judge whether the drafted build plan is a coherent, complete, correctly-ordered decomposition of the approved domain plan into coding-agent tasks — WITHOUT straying into how those tasks execute. Assess ten invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) MODULE + RESOURCE COVERAGE — every resource in every module's inventory (mainResources + supportingResources) has build tasks; a resource with no task is a GAP (the build would not produce it). Task `moduleRef` values must be module ids the workspace section lists (an invented module id is a GAP — the dispatcher cannot route it), and a task whose objective CREATES a resource the workspace section shows already exists — instead of enriching it — is a CONCERN (it dispatches a no-op). Module slices are scaffolded by the foundation step (a sibling playbook), so a module needs a dedicated ensure-module task ONLY where foundation did not establish it — a module whose resources have tasks but which carries no redundant scaffold task is NOT a GAP (do not flag the absence of a module-scaffold task foundation already owns); a module added to the plan after foundation with neither a foundation slice nor an ensure-module task IS a GAP. Every pricing plan the business model declares must be an `APPLICATION_BILLING_PRODUCT` of a `BILLING_CATALOG` task whose `servesRefs` name it; a declared plan with no billing product is a GAP. A plan with main resources and no `DEMONSTRATION` `APPLICATION_DATA_SEED` task is a CONCERN: the application would open empty. (2) TASK WELL-FORMEDNESS — every task names exactly ONE functional topic that is a real MetaWorkflow_FunctionalTopic value (configure_application_foundation / model_domain_graph / define_interaction_semantics / shape_user_experience / extend_application / connect_runtime_and_external_capabilities / assemble_verify_and_iterate) and at least one skill that is a real folder in the app-knowledge skill catalog; a task with an invented topic or a dangling skill is a GAP. (2b) PRODUCT DECLARATION — every task except a COMPANION_GENERATION_STEP declares at least one product in `produces`, and a generation step declares none; a coding task with an empty `produces` is a GAP, because it has no declared output to probe. The host can advance after a COMPLETED durable run, but carries the task in `unverifiableLandedTaskRefs`; that means ran, not proven. Repair the product declaration rather than treating this fallback as evidence of correct output. A product must name something COMPOSITION DOES NOT ALREADY WRITE — the fields a schema gains rather than its file, the verbs a config gains rather than its file, both endpoints of a relationship rather than one — so a product naming only a scaffolded artifact is a GAP wearing a declaration. Two tasks claiming the SAME artifact is a GAP as well (landing becomes undecidable); two tasks enriching one resource with DIFFERENT fields is correct and not a finding. A cross-resource FOREIGN KEY declared on a schema task's `produces` is a GAP — the relationship task is its single home (Step 2), and declaring it twice attributes one artifact to two tasks; a schema task's products are the resource's OWN domain fields. (3) PER-RESOURCE STAGE ORDER — for each resource, its tasks respect the inner order schema -> config -> ui-behavior -> spec; a config task ordered before that resource's schema task, or a spec task before its ui-behavior task, is a GAP (the build stage would run against a missing prerequisite). A supportingResource (e.g. a pure junction / lookup entity) may legitimately OMIT stages it does not need — a junction with schema + config and no ui-behavior is fine; only an out-of-ORDER stage (or a mainResource missing schema/config) is a GAP, not an intentionally-omitted stage on a supporting resource. (4) TOPIC DEPENDENCY ORDER — tasks respect the topic dependency edges (model_domain_graph before define_interaction_semantics; app-level shape_user_experience [views / navigation composing multiple resources or operations] after the interaction semantics and resources it composes; extend_application after the UX it extends; connect_runtime_and_external_capabilities after the resources it connects). Note the deliberate exception: a resource's OWN ui-behavior (its field displays / forms, a shape_user_experience task) depends only on that resource's own schema + config and MAY precede cross-resource operations — that is NOT a violation. What IS a GAP: an app-level view composing resources/operations placed before they exist, an integration task before the resources it connects, or any user-experience task before that resource's schema task. The per-resource spec task is a documentation capstone (topic model_domain_graph) and must be ordered after the schema / config / ui-behavior stages it documents; a spec task before its ui-behavior stage is a GAP. (5) RELATIONSHIP COVERAGE — every relationship-draft whose two endpoints are resources the domain plan declares has a wiring task (bound to the module-relationships skill) ordered AFTER both endpoint resources' schema tasks; a relationship with no wiring task, or one ordered before its endpoints exist, is a GAP. A relationship to a resource no module declares is NOT this invariant: no task can wire it, so it is invariant (8)'s. (6) COMPANION-GENERATION INTERLEAVE — the executable companion-owned generation steps (`i18n-labels`, `email-templates`, `logo`, plus `database-migrations` for a PostgreSQL-backed application) are present and placed AFTER the resources / modules whose output they consume; a labels-generation task ordered before the resources it labels, or a missing executable generation step for authored surfaces, is a CONCERN. `logo` is the exception to the ordering half — it consumes the brand brief rather than any code surface, so it is unordered with respect to resource work and only its ABSENCE (on an application with a brand brief) is a CONCERN. The migration step follows the schema stages whose drift it migrates and is not authored for MongoDB. Do NOT flag the absence of an `i18n-translations` step — the dispatch host derives it after `i18n-labels`. Do NOT flag the absence of a seeds GENERATION step — none exists; seeding is an `APPLICATION_DATA_SEED` coding task, judged under invariant (1). (7) BOUNDARY DISCIPLINE — the plan stays at DECOMPOSITION depth: it names tasks, their topic, their skill(s), their target, and their ordering intent; it does NOT specify how a task is DISPATCHED (dispatch locking and concurrency, change-set capture, git baseline, verify/quality-gate mechanics = the dispatch-orchestration playbook) and does NOT solve multi-agent SCALE or interleaving concurrency (= the scale playbook). Any task that describes how a task EXECUTES rather than WHAT it builds, or that authors a schema / resolves a cardinality into a concrete FK / generates code, is a CONCERN (scope creep out of the decomposition phase). (8) CONCEPTION BUILDABLE — this one faults the CONCEPTION, never the plan: a GAP when the domain plan declares a module, resource or relationship no build target can express however it is decomposed, or when the computed coherence report shows a dangling reference or unrealised decision in the conception (a domain-plan resource another family names that does not exist, a composition surface no plan realises) that the build would have to invent to proceed. An element the plan merely FORGOT is invariant (1), not this one — only a conception GAP sends the application back to its conception lane, which is the most expensive way to fix an omission. Name the conception element. (9) EXPERIENCE COVERAGE — every view, configuration, milestone and piece of guidance the experience plan declares has its task (a view task carrying the plan's viewRef verbatim, an onboarding document's objective naming its hostViewRef); an entry with no task is a GAP, and an objective that drops what the plan decided for its entry (reused components, the moment, the gate) is a CONCERN. With NO experience plan the plan rightly carries none of these tasks: mark PASS and begin the note with 'NO EXPERIENCE PLAN:' naming what the application will lack — never a CONCERN or GAP, because the decomposer cannot produce an upstream family by revising. (The deterministic gates and the creator's approval remain the floors; the judge's verdicts are advisory notes beside them.)
|
|
2075
|
+
Judge whether the drafted build plan is a coherent, complete, correctly-ordered decomposition of the approved domain plan into coding-agent tasks — WITHOUT straying into how those tasks execute. Assess twelve invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) MODULE + RESOURCE COVERAGE — every resource in every module's inventory (mainResources + supportingResources) has build tasks; a resource with no task is a GAP (the build would not produce it). Task `moduleRef` values must be module ids the workspace section lists (an invented module id is a GAP — the dispatcher cannot route it), and a task whose objective CREATES a resource the workspace section shows already exists — instead of enriching it — is a CONCERN (it dispatches a no-op). Module slices are scaffolded by the foundation step (a sibling playbook), so a module needs a dedicated ensure-module task ONLY where foundation did not establish it — a module whose resources have tasks but which carries no redundant scaffold task is NOT a GAP (do not flag the absence of a module-scaffold task foundation already owns); a module added to the plan after foundation with neither a foundation slice nor an ensure-module task IS a GAP. Every pricing plan the business model declares must be an `APPLICATION_BILLING_PRODUCT` of a `BILLING_CATALOG` task whose `servesRefs` name it; a declared plan with no billing product is a GAP. A plan with main resources and no `DEMONSTRATION` `APPLICATION_DATA_SEED` task is a CONCERN: the application would open empty. A seed task whose rows reference another seed's rows (a contact's customer) that is not ordered after that seed's task is a GAP — the reference resolves only against rows already written. (2) TASK WELL-FORMEDNESS — every task names exactly ONE functional topic that is a real MetaWorkflow_FunctionalTopic value (configure_application_foundation / model_domain_graph / define_interaction_semantics / shape_user_experience / extend_application / connect_runtime_and_external_capabilities / assemble_verify_and_iterate) and at least one skill that is a real folder in the app-knowledge skill catalog; a task with an invented topic or a dangling skill is a GAP. (2b) PRODUCT DECLARATION — every task except a COMPANION_GENERATION_STEP declares at least one product in `produces`, and a generation step declares none; a coding task with an empty `produces` is a GAP, because it has no declared output to probe. The host can advance after a COMPLETED durable run, but carries the task in `unverifiableLandedTaskRefs`; that means ran, not proven. Repair the product declaration rather than treating this fallback as evidence of correct output. A product must name something COMPOSITION DOES NOT ALREADY WRITE — the fields a schema gains rather than its file, the verbs a config gains rather than its file, both endpoints of a relationship rather than one — so a product naming only a scaffolded artifact is a GAP wearing a declaration. Two tasks claiming the SAME artifact is a GAP as well (landing becomes undecidable); two tasks enriching one resource with DIFFERENT fields is correct and not a finding. A cross-resource FOREIGN KEY declared on a schema task's `produces` is a GAP — the relationship task is its single home (Step 2), and declaring it twice attributes one artifact to two tasks; a schema task's products are the resource's OWN domain fields. (3) PER-RESOURCE STAGE ORDER — for each resource, its tasks respect the inner order schema -> config -> ui-behavior -> spec; a config task ordered before that resource's schema task, or a spec task before its ui-behavior task, is a GAP (the build stage would run against a missing prerequisite). A supportingResource (e.g. a pure junction / lookup entity) may legitimately OMIT stages it does not need — a junction with schema + config and no ui-behavior is fine; only an out-of-ORDER stage (or a mainResource missing schema/config) is a GAP, not an intentionally-omitted stage on a supporting resource. (4) TOPIC DEPENDENCY ORDER — tasks respect the topic dependency edges (model_domain_graph before define_interaction_semantics; app-level shape_user_experience [views / navigation composing multiple resources or operations] after the interaction semantics and resources it composes; extend_application after the UX it extends; connect_runtime_and_external_capabilities after the resources it connects). Note the deliberate exception: a resource's OWN ui-behavior (its field displays / forms, a shape_user_experience task) depends only on that resource's own schema + config and MAY precede cross-resource operations — that is NOT a violation. What IS a GAP: an app-level view composing resources/operations placed before they exist, an integration task before the resources it connects, or any user-experience task before that resource's schema task. The per-resource spec task is a documentation capstone (topic model_domain_graph) and must be ordered after the schema / config / ui-behavior stages it documents; a spec task before its ui-behavior stage is a GAP. (5) RELATIONSHIP COVERAGE — every relationship-draft whose two endpoints are resources the domain plan declares has a wiring task (bound to the module-relationships skill) ordered AFTER both endpoint resources' schema tasks; a relationship with no wiring task, or one ordered before its endpoints exist, is a GAP. A relationship to a resource no module declares is NOT this invariant: no task can wire it, so it is invariant (8)'s. (6) COMPANION-GENERATION INTERLEAVE — the executable companion-owned generation steps (`i18n-labels`, `email-templates`, `logo`, plus `database-migrations` for a PostgreSQL-backed application) are present and placed AFTER the resources / modules whose output they consume; a labels-generation task ordered before the resources it labels, or a missing executable generation step for authored surfaces, is a CONCERN. `logo` is the exception to the ordering half — it consumes the brand brief rather than any code surface, so it is unordered with respect to resource work and only its ABSENCE (on an application with a brand brief) is a CONCERN. The migration step follows the schema stages whose drift it migrates and is not authored for MongoDB. Do NOT flag the absence of an `i18n-translations` step — the dispatch host derives it after `i18n-labels`. Do NOT flag the absence of a seeds GENERATION step — none exists; seeding is an `APPLICATION_DATA_SEED` coding task, judged under invariant (1). (7) BOUNDARY DISCIPLINE — the plan stays at DECOMPOSITION depth: it names tasks, their topic, their skill(s), their target, and their ordering intent; it does NOT specify how a task is DISPATCHED (dispatch locking and concurrency, change-set capture, git baseline, verify/quality-gate mechanics = the dispatch-orchestration playbook) and does NOT solve multi-agent SCALE or interleaving concurrency (= the scale playbook). Any task that describes how a task EXECUTES rather than WHAT it builds, or that authors a schema / resolves a cardinality into a concrete FK / generates code, is a CONCERN (scope creep out of the decomposition phase). (8) CONCEPTION BUILDABLE — this one faults the CONCEPTION, never the plan: a GAP when the domain plan declares a module, resource or relationship no build target can express however it is decomposed, or when the computed coherence report shows a dangling reference or unrealised decision in the conception (a domain-plan resource another family names that does not exist, a composition surface no plan realises) that the build would have to invent to proceed. An element the plan merely FORGOT is invariant (1), not this one — only a conception GAP sends the application back to its conception lane, which is the most expensive way to fix an omission. Name the conception element. (9) EXPERIENCE COVERAGE — every view, configuration, milestone and piece of guidance the experience plan declares has its task (a view task carrying the plan's viewRef verbatim, an onboarding document's objective naming its hostViewRef), and a decided `home` is set by the `GLOBAL_VIEWS` task's objective (it names `homeDefinitionFactory` and the home); an entry with no task, or a decided home no objective sets, is a GAP, and an objective that drops what the plan decided for its entry (reused components, the moment, the gate) is a CONCERN. With NO experience plan the plan rightly carries none of these tasks: mark PASS and begin the note with 'NO EXPERIENCE PLAN:' naming what the application will lack — never a CONCERN or GAP, because the decomposer cannot produce an upstream family by revising. (10) ROLE COVERAGE — every requirement that names groups of users with different access is served by an `APPLICATION_ROLES` task producing one `APPLICATION_ROLE` per group no core role covers, ordered after the config tasks of the resources it narrows; a group with no role, or a role requirement answered by a task or resource that stores roles or permissions as data, is a GAP; a roles task ordered before a config task it narrows, or whose objective does not say which operations each role may call, is a CONCERN. (11) INTERACTION COVERAGE — every transition the domain plan's lifecycles declare has its `RESOURCE_OPERATION` task (and a `MODULE_BACKEND` task when it creates a resource), and every functional acceptance criterion whose verb goes beyond the default resource verbs (a state change, one record creating or filling another, a record that must stop changing, a produced document, a sent message) is served by a task of the matching kind (`RESOURCE_OPERATION`, a `MODULE_BACKEND` implementation, `PDF_TEMPLATE`, the email generation step) whose `servesRefs` name the requirement; a plan whose requirements describe a workflow and which carries no interaction task, or a state change served only by a config task that leaves the status freely editable, is a GAP; a derived value (a next action, an overdue flag) planned as a stored field is a CONCERN. (The deterministic gates and the creator's approval remain the floors; the judge's verdicts are advisory notes beside them.)
|