@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
|
@@ -42,10 +42,19 @@ nothing reaches them. That is the one thing this plan refuses.
|
|
|
42
42
|
| `NAVIGATION` | the SHAPE the application navigates in — one thing at a time, list-and-detail, or a canvas with a floating detail — and then the zones and per-operation transitions that say it | `config-navigation` |
|
|
43
43
|
| `DESIGN_SYSTEM` | the palette and typography, from the BRAND's visual tone — never invented here. When the brief says the brand does not apply (an internal tool), keep the scaffold's neutral theme and do not propose this surface | `config-design-system` |
|
|
44
44
|
| `GLOBAL_VIEWS` | which app-level views are registered as launcher entries | `views-app-level` |
|
|
45
|
+
| `SHELL_LAYOUT` | how the shell MOVES — one of the four animated 2D layouts, from the brand's mood and how people work (see below). Its ONE declaration is the layout constant, written out even for glide: `GLIDE_LAYOUT_2D`, `MORPH_LAYOUT_2D`, `CARDS_LAYOUT_2D` or `SPRING_LAYOUT_2D`. Leave the surface out to keep the still default shell. Never a 3D layout: that is the operator's opt-in, not the journey's | `layout-2d-adoption` |
|
|
45
46
|
|
|
46
47
|
Each names the things the file gains (`declarationRefs`) — a sidebar section ref, a zone, a token.
|
|
47
|
-
Never the file: `wildo init` writes
|
|
48
|
-
task ran.
|
|
48
|
+
Never the file: `wildo init` writes every one of these files, so a decision that names nothing was
|
|
49
|
+
true before any task ran.
|
|
50
|
+
|
|
51
|
+
**`SHELL_LAYOUT` follows the brand, like the design system.** The design system gives the palette and
|
|
52
|
+
the PACE (its motion tokens); the layout decides how the shell moves at that pace, so decide it from
|
|
53
|
+
the same brand brief — its `mood` and `styleKeywords` — and from how people work in the product:
|
|
54
|
+
calm, dense, all-day work reads best in glide; an expressive or consumer product in morph or spring; a
|
|
55
|
+
record- or document-centred product, opened beside a list, in cards. The skill's
|
|
56
|
+
`references/choosing-a-layout.md` is the decision table. Settings (`speed`, `bounce`, `travelPx`) are
|
|
57
|
+
optional and follow the brand too — a composed brand a touch slower, a playful one more bounce.
|
|
49
58
|
|
|
50
59
|
**`NAVIGATION` is a product decision before it is a configuration.** The scaffold's default — one
|
|
51
60
|
zone, a detail that replaces the list — is a real shape and it is right for some products and wrong
|
|
@@ -83,6 +92,22 @@ belong to their module and must not. The plan refuses both mistakes, in both dir
|
|
|
83
92
|
**Plan an application view.** An application with none opens on whatever the shell defaults to,
|
|
84
93
|
which is nobody's decision.
|
|
85
94
|
|
|
95
|
+
**Decide the home** (`home`): what a person sees first when they open the application. Two earlier
|
|
96
|
+
runs decided none, and both opened on the framework's welcome page. It is one of two things, the two
|
|
97
|
+
the engine can show at the root:
|
|
98
|
+
|
|
99
|
+
- `VIEW` — a planned `APPLICATION_VIEW`, shown in place (name its slug). Only an application view: the
|
|
100
|
+
root looks the view up among the application-level views, so a view owned by one resource (a
|
|
101
|
+
`RESOURCE_COMPOSITE_VIEW`) is not found there. When the home is one resource's view, plan an
|
|
102
|
+
application view that is the home, or make the home that resource's operation;
|
|
103
|
+
- `RESOURCE_OPERATION` — a resource's operation the root opens (module, resource, and the operation:
|
|
104
|
+
`list`, `read`, or a custom verb), reached through that operation's default variant.
|
|
105
|
+
|
|
106
|
+
Choose it for the group that opens the application most, from what the creator stated about the
|
|
107
|
+
user groups and their devices (the declared `creator_stated_facts` context section of your brief): a field worker on a phone
|
|
108
|
+
lands on today's jobs, an office manager at a desk on the pipeline. Say why in its `rationale`. The
|
|
109
|
+
home is authored in `GLOBAL_VIEWS`, so compose that surface when you decide one.
|
|
110
|
+
|
|
86
111
|
## Step 3 — Name the preset components each surface reuses
|
|
87
112
|
|
|
88
113
|
This is the field this plan exists for. The framework ships a component catalogue, and a coding
|
|
@@ -128,9 +153,12 @@ Five rules decide whether planned guidance will ever be seen — plan against th
|
|
|
128
153
|
earned BEFORE the flow's moment, never the one that same moment earns.
|
|
129
154
|
- **Keep refs stable.** A guidance ref keys every person's saved progress; renaming it forgets it.
|
|
130
155
|
- **A document names its host.** An `ONBOARDING_DOCUMENT` is seen only where a view embeds it, so it
|
|
131
|
-
names that view in `hostViewRef` — a view you plan above
|
|
132
|
-
|
|
133
|
-
|
|
156
|
+
names that view in `hostViewRef` — a view you plan above (this plan lists every view the application
|
|
157
|
+
keeps, so a view it already has is restated here), written as that view's `slug`, and a view of the
|
|
158
|
+
document's OWN module: a document is declared by the module whose view shows it, and its build task
|
|
159
|
+
writes only there. A host you did not plan is reported back to you; if it is still unplanned on the
|
|
160
|
+
last attempt, the document is dropped when the plan lands, never the plan. A flow names none: its
|
|
161
|
+
trigger shows it.
|
|
134
162
|
|
|
135
163
|
Both carry `servesRefs`, like every surface.
|
|
136
164
|
|
|
@@ -143,9 +171,10 @@ identifiers and guidance refs, with one more reason: people's progress is stored
|
|
|
143
171
|
## What you emit
|
|
144
172
|
|
|
145
173
|
- The **experience plan** at `specifications/src/experience-plan/index.ts` — the configuration
|
|
146
|
-
surfaces this application composes, the views it carries — each with its kind,
|
|
147
|
-
person does on it, the presets it reuses and what it serves —
|
|
148
|
-
recognises and the guidance toward them
|
|
174
|
+
surfaces this application composes, the views it carries — each with its kind, the module (and
|
|
175
|
+
resource) it belongs to, what a person does on it, the presets it reuses and what it serves — its
|
|
176
|
+
journey (the milestones it recognises and the guidance toward them), and the application's `home`:
|
|
177
|
+
what a person sees first.
|
|
149
178
|
|
|
150
179
|
## Verification
|
|
151
180
|
|
|
@@ -156,6 +185,8 @@ identifiers and guidance refs, with one more reason: people's progress is stored
|
|
|
156
185
|
- Every `triggerResourceRef` names a resource the domain plan declares, and no two guidance flows are
|
|
157
186
|
planned on the same moment.
|
|
158
187
|
- Every `gatedByMilestoneRefs` entry names a planned milestone or one the application already declares.
|
|
188
|
+
- A home is decided; a `VIEW` home names a planned `APPLICATION_VIEW`, a `RESOURCE_OPERATION` home names a
|
|
189
|
+
module and resource the domain plan declares, and `GLOBAL_VIEWS` is composed.
|
|
159
190
|
|
|
160
191
|
## References — named by REF, because this step cannot open a file
|
|
161
192
|
|
|
@@ -173,8 +204,8 @@ The rest are the contracts the CODING AGENT opens when it builds each task:
|
|
|
173
204
|
- `views-add-composite-view`, `views-add-custom-view`, `views-execution-authoring`,
|
|
174
205
|
`views-chart-authoring`, `views-app-level`, `engine-component-registration` — one per view KIND,
|
|
175
206
|
bound to the emitted task by `EXPERIENCE_VIEW_SKILL_REF`.
|
|
176
|
-
- `config-app-shell`, `config-navigation`, `config-design-system` — one per
|
|
177
|
-
bound by `EXPERIENCE_CONFIGURATION_SKILL_REF`.
|
|
207
|
+
- `config-app-shell`, `config-navigation`, `config-design-system`, `layout-2d-adoption` — one per
|
|
208
|
+
configuration SURFACE, bound by `EXPERIENCE_CONFIGURATION_SKILL_REF`.
|
|
178
209
|
- `milestones-and-celebrations` — how a planned milestone is declared and celebrated, bound by
|
|
179
210
|
`EXPERIENCE_MILESTONE_SKILL_REF`.
|
|
180
211
|
- `guidance-onboarding-authoring` — how a planned document or flow is authored, bound by
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "bottom_up.experience-plan",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.3.1",
|
|
4
4
|
"phase": "bottom_up",
|
|
5
|
-
"intent": "User-experience composition — decide WHAT THIS APPLICATION'S EXPERIENCE IS beyond the screens the framework generates for each resource: which composite, custom, execution and chart views it carries and on which resource, which application-level views and dashboards it opens on, which custom components several views reuse, how its navigation, app shell, design system and global views are composed, and the JOURNEY a new person takes — the milestones it recognises and the onboarding documents and guidance flows that get a person there. Reads the domain plan (the modules, resources and relationships that exist), the requirements and feature drafts (what somebody asked for), the placement plan (where decided subjects already sit) and the brand (the visual tone the design system applies). Every view names the PRESET COMPONENTS it reuses, from the framework's own catalogue, because a coding agent with no catalogue in front of it builds custom surfaces out of raw elements and bypasses the theme, the surface policy and the accessibility behaviour every preset carries. Produces the plan; the decomposer turns it into build tasks, each bound to the skill the view's kind, the configuration's surface, the milestone or the guidance kind names.",
|
|
5
|
+
"intent": "User-experience composition — decide WHAT THIS APPLICATION'S EXPERIENCE IS beyond the screens the framework generates for each resource: which composite, custom, execution and chart views it carries and on which resource, which application-level views and dashboards it opens on, which custom components several views reuse, how its navigation, app shell, design system and global views are composed and which animated 2D layout the shell moves in (from the brand, beside the design system), and the JOURNEY a new person takes — the milestones it recognises and the onboarding documents and guidance flows that get a person there. Reads the domain plan (the modules, resources and relationships that exist), the requirements and feature drafts (what somebody asked for), the placement plan (where decided subjects already sit) and the brand (the visual tone the design system applies). Every view names the PRESET COMPONENTS it reuses, from the framework's own catalogue, because a coding agent with no catalogue in front of it builds custom surfaces out of raw elements and bypasses the theme, the surface policy and the accessibility behaviour every preset carries. Produces the plan; the decomposer turns it into build tasks, each bound to the skill the view's kind, the configuration's surface, the milestone or the guidance kind names.",
|
|
6
6
|
"preconditions": [
|
|
7
7
|
{
|
|
8
8
|
"kind": "artifact_exists",
|
|
@@ -36,12 +36,12 @@
|
|
|
36
36
|
{
|
|
37
37
|
"family": "experience-plan",
|
|
38
38
|
"schemaRef": "saas-specifications:ExperiencePlan",
|
|
39
|
-
"description": "The application's experience: the views it carries beyond the generated screens — each with its kind (which names the skill that authors it), the module and resource it belongs to, what a person does on it, the preset components it reuses and what it is accountable to — the application-wide configuration surfaces it composes, each naming what that file gains and why, and its journey: the milestones it recognises (identifier, module, the resource that earns each, the moment) and the guidance toward them (onboarding documents and guidance flows, the milestones each waits for)."
|
|
39
|
+
"description": "The application's experience: the views it carries beyond the generated screens — each with its kind (which names the skill that authors it), the module and resource it belongs to, what a person does on it, the preset components it reuses and what it is accountable to — the application-wide configuration surfaces it composes, each naming what that file gains and why, and its journey: the milestones it recognises (identifier, module, the resource that earns each, the moment) and the guidance toward them (onboarding documents and guidance flows, the milestones each waits for); and its home: what a person sees first, an application view or a resource's operation, with why."
|
|
40
40
|
}
|
|
41
41
|
],
|
|
42
42
|
"stepOutputs": [],
|
|
43
43
|
"method": {
|
|
44
|
-
"guidance": "# Experience Plan — What This Application's Experience Is\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## Where you are in the journey\n\nThe domain plan is approved: the modules, resources and relationships exist as decisions, and the\nframework generates a list and a read screen for every resource without being asked. You decide\n**what this application carries beyond that** — the surfaces a person actually works on — **how\nits shell, navigation and palette are composed**, and **the journey a new person takes**: the\nmoments the application recognises, and the guidance that gets them there.\n\nYou do not write any of it. `bottom_up.build-decompose` turns each entry here into a build task\nbound to the skill that authors it.\n\n## This is not the placement plan\n\nPlacement decides WHERE a decided subject sits — which settings category, which sidebar section.\nThis decides WHICH SURFACES EXIST. Run in that order: a placement of a view nobody proposed places\nnothing, and the placement plan is an input here so a proposed surface does not duplicate something\nthe shell already reaches.\n\n## Step 1 — Compose the configuration surfaces\n\n**At least one, and in practice always the shell.** An application whose navigation and app shell\nare left at the scaffold's defaults has no route to its own modules: the generated screens exist and\nnothing reaches them. That is the one thing this plan refuses.\n\n| surface | what you decide | skill |\n|---|---|---|\n| `APP_SHELL` | which sidebar sections exist, what the top bar carries, the quick switcher's scope | `config-app-shell` |\n| `NAVIGATION` | the SHAPE the application navigates in — one thing at a time, list-and-detail, or a canvas with a floating detail — and then the zones and per-operation transitions that say it | `config-navigation` |\n| `DESIGN_SYSTEM` | the palette and typography, from the BRAND's visual tone — never invented here. When the brief says the brand does not apply (an internal tool), keep the scaffold's neutral theme and do not propose this surface | `config-design-system` |\n| `GLOBAL_VIEWS` | which app-level views are registered as launcher entries | `views-app-level` |\n\nEach names the things the file gains (`declarationRefs`) — a sidebar section ref, a zone, a token.\nNever the file: `wildo init` writes all four, so a decision that names nothing was true before any\ntask ran.\n\n**`NAVIGATION` is a product decision before it is a configuration.** The scaffold's default — one\nzone, a detail that replaces the list — is a real shape and it is right for some products and wrong\nfor others, and nothing about the domain plan reveals which. The question is *while a person is\nreading one record, what else must stay on screen*, and its answer comes from the ICPs and the\njobs-to-be-done that are already decided (on an application with no market, from\nthe operating team and the work the vision and the requirements describe): users who triage a queue need the list to stay, users who\nopen one record and finish it do not, and a product whose main surface is a board or a map needs the\ndetail to float over it rather than take a share of it.\n\nDecide it HERE, with the market and definition artifacts in front of you, and put the reasoning in\nthe surface's `rationale` — a later task reading only the layout cannot recover why that shape was\nchosen, and the shape decides whether a detail needs its own page chrome, whether a list wants\nselection affordances, and whether operations must be addressable. `config-navigation`\nopens with that question, translates the product shapes into what to declare, and names the trade\nthat is hardest to reverse: content in an overlay has no URL, so nobody can link to it.\n\n## Step 2 — Decide the surfaces\n\nA surface exists because a person has to do something the generated list and read cannot do. Six\nkinds, each naming the skill that authors it:\n\n| kind | what it is | belongs to |\n|---|---|---|\n| `RESOURCE_COMPOSITE_VIEW` | a workspace composing several resources around one | a resource |\n| `RESOURCE_CUSTOM_VIEW` | a bespoke screen for one operation — a wizard, a rich read | a resource |\n| `RESOURCE_EXECUTION_VIEW` | drives a long-running execution and shows its progress | a resource |\n| `RESOURCE_CHART_VIEW` | a chart over one resource's rows | a resource |\n| `APPLICATION_VIEW` | an application-level view or dashboard — the home a person opens on | a module |\n| `CUSTOM_COMPONENT` | a component several surfaces reuse | a module |\n\nThe first four are declared in ONE resource's ui-behavior, so each names its resource; the last two\nbelong to their module and must not. The plan refuses both mistakes, in both directions.\n\n**Plan an application view.** An application with none opens on whatever the shell defaults to,\nwhich is nobody's decision.\n\n## Step 3 — Name the preset components each surface reuses\n\nThis is the field this plan exists for. The framework ships a component catalogue, and a coding\nagent that has not been told which components to reuse builds the surface out of raw elements —\nbypassing the theme, the surface policy and the accessibility behaviour every preset carries. Read\nthe catalogue (`frontend-component-catalog`) and name the components each surface is composed from.\n\nA `CUSTOM_COMPONENT` reuses nothing by definition: it IS the reusable thing.\n\n## Step 4 — Make every surface accountable\n\nEach carries `servesRefs`: the requirement, feature draft, roadmap phase or success criterion that\nasked for it. A surface accountable to nothing is one nobody asked for, and the plan reports it.\n\n## Step 5 — Plan the journey\n\nA new person arrives at an application they have never used. Decide what recognises their progress\nand what tells them what to do first. **Plan at least one of the two** — a plan with neither is\nreported, because a new person then meets a product that neither welcomes nor guides them. An\ninternal tool may rightly have neither; say so by leaving both empty on purpose.\n\n**Milestones** — the moments worth recognising: a person's first record of the thing the product is\nfor, a count that shows it is working for them, a moment a whole organization reaches together. Each\nnames its identifier as a slug (`first-deal-won`, declared `FIRST_DEAL_WON` in code), its module,\nthe resource whose operation earns it, and the moment in the person's own terms. How loudly each one\ncelebrates is decided when it is built, not here.\n\n**Guidance** — two shapes, and choosing between them is the decision:\n\n| kind | what it is | use it when |\n|---|---|---|\n| `ONBOARDING_DOCUMENT` | embedded on a screen — a welcome announcement, a getting-started stepper | the guidance belongs to a place, and should be there whenever that place is |\n| `GUIDANCE_FLOW` | triggered by an event — a banner after the first X, a tour, a one-question survey | the guidance belongs to a moment, and should appear once, right after something happened |\n\nFive rules decide whether planned guidance will ever be seen — plan against them:\n\n- **Only one triggered overlay shows at a time.** The others wait behind it until it is finished,\n skipped or dismissed, and a waiting one is dropped if the page reloads first — so a second flow\n planned on the same moment is often never seen. Give each flow its own moment.\n- **A flow shows once per person.** Guidance that should appear every time — an empty-list message —\n is not a flow; it belongs to the resource's own screen.\n- **A gate is a milestone the person already holds.** `gatedByMilestoneRefs` must name milestones\n earned BEFORE the flow's moment, never the one that same moment earns.\n- **Keep refs stable.** A guidance ref keys every person's saved progress; renaming it forgets it.\n- **A document names its host.** An `ONBOARDING_DOCUMENT` is seen only where a view embeds it, so it\n names that view in `hostViewRef` — a view you plan above, or one the application already has, and\n in either case a view of the document's OWN module: a document is declared by the module whose view\n shows it, and its build task writes only there. A flow names none: its trigger shows it.\n\nBoth carry `servesRefs`, like every surface.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every view ref that still has a reason to exist — build tasks\nname them, and a moved ref orphans the task that produced its surface. The same holds for milestone\nidentifiers and guidance refs, with one more reason: people's progress is stored against them.\n\n## What you emit\n\n- The **experience plan** at `specifications/src/experience-plan/index.ts` — the configuration\n surfaces this application composes, the views it carries — each with its kind, its home, what a\n person does on it, the presets it reuses and what it serves — and its journey: the milestones it\n recognises and the guidance toward them.\n\n## Verification\n\n- Every `moduleRef` and `resourceRef` names something the domain plan declares.\n- Every `reusesComponentRefs` entry names a component the catalogue carries.\n- `rg -n \"kind: ExperienceViewKind\" specifications/src/experience-plan/index.ts | wc -l` — the number\n of view tasks the build lane will emit.\n- Every `triggerResourceRef` names a resource the domain plan declares, and no two guidance flows are\n planned on the same moment.\n- Every `gatedByMilestoneRefs` entry names a planned milestone or one the application already declares.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem, so a path here would be an instruction answered from\nrecollection (#1435). Each skill is named by its REF, and one reaches this step as a BODY\n(`method.skillBodyRefs`): **`frontend-component-catalog`**. That is not a convenience — naming the\npresets each surface reuses is this plan's whole point, and a model without the catalogue in front\nof it invents component names that resolve to nothing.\n\nThe rest are the contracts the CODING AGENT opens when it builds each task:\n\n- `views-composite-authoring` — what a composite view IS, so a planned one is one the build lane can author.\n- `resource-custom-view` — a custom view's shape and its binding.\n- `spec-composite-view-update` — the specification a composite view owes.\n- `views-add-composite-view`, `views-add-custom-view`, `views-execution-authoring`,\n `views-chart-authoring`, `views-app-level`, `engine-component-registration` — one per view KIND,\n bound to the emitted task by `EXPERIENCE_VIEW_SKILL_REF`.\n- `config-app-shell`, `config-navigation`, `config-design-system` — one per configuration SURFACE,\n bound by `EXPERIENCE_CONFIGURATION_SKILL_REF`.\n- `milestones-and-celebrations` — how a planned milestone is declared and celebrated, bound by\n `EXPERIENCE_MILESTONE_SKILL_REF`.\n- `guidance-onboarding-authoring` — how a planned document or flow is authored, bound by\n `EXPERIENCE_GUIDANCE_SKILL_REF`.\n",
|
|
44
|
+
"guidance": "# Experience Plan — What This Application's Experience Is\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## Where you are in the journey\n\nThe domain plan is approved: the modules, resources and relationships exist as decisions, and the\nframework generates a list and a read screen for every resource without being asked. You decide\n**what this application carries beyond that** — the surfaces a person actually works on — **how\nits shell, navigation and palette are composed**, and **the journey a new person takes**: the\nmoments the application recognises, and the guidance that gets them there.\n\nYou do not write any of it. `bottom_up.build-decompose` turns each entry here into a build task\nbound to the skill that authors it.\n\n## This is not the placement plan\n\nPlacement decides WHERE a decided subject sits — which settings category, which sidebar section.\nThis decides WHICH SURFACES EXIST. Run in that order: a placement of a view nobody proposed places\nnothing, and the placement plan is an input here so a proposed surface does not duplicate something\nthe shell already reaches.\n\n## Step 1 — Compose the configuration surfaces\n\n**At least one, and in practice always the shell.** An application whose navigation and app shell\nare left at the scaffold's defaults has no route to its own modules: the generated screens exist and\nnothing reaches them. That is the one thing this plan refuses.\n\n| surface | what you decide | skill |\n|---|---|---|\n| `APP_SHELL` | which sidebar sections exist, what the top bar carries, the quick switcher's scope | `config-app-shell` |\n| `NAVIGATION` | the SHAPE the application navigates in — one thing at a time, list-and-detail, or a canvas with a floating detail — and then the zones and per-operation transitions that say it | `config-navigation` |\n| `DESIGN_SYSTEM` | the palette and typography, from the BRAND's visual tone — never invented here. When the brief says the brand does not apply (an internal tool), keep the scaffold's neutral theme and do not propose this surface | `config-design-system` |\n| `GLOBAL_VIEWS` | which app-level views are registered as launcher entries | `views-app-level` |\n| `SHELL_LAYOUT` | how the shell MOVES — one of the four animated 2D layouts, from the brand's mood and how people work (see below). Its ONE declaration is the layout constant, written out even for glide: `GLIDE_LAYOUT_2D`, `MORPH_LAYOUT_2D`, `CARDS_LAYOUT_2D` or `SPRING_LAYOUT_2D`. Leave the surface out to keep the still default shell. Never a 3D layout: that is the operator's opt-in, not the journey's | `layout-2d-adoption` |\n\nEach names the things the file gains (`declarationRefs`) — a sidebar section ref, a zone, a token.\nNever the file: `wildo init` writes every one of these files, so a decision that names nothing was\ntrue before any task ran.\n\n**`SHELL_LAYOUT` follows the brand, like the design system.** The design system gives the palette and\nthe PACE (its motion tokens); the layout decides how the shell moves at that pace, so decide it from\nthe same brand brief — its `mood` and `styleKeywords` — and from how people work in the product:\ncalm, dense, all-day work reads best in glide; an expressive or consumer product in morph or spring; a\nrecord- or document-centred product, opened beside a list, in cards. The skill's\n`references/choosing-a-layout.md` is the decision table. Settings (`speed`, `bounce`, `travelPx`) are\noptional and follow the brand too — a composed brand a touch slower, a playful one more bounce.\n\n**`NAVIGATION` is a product decision before it is a configuration.** The scaffold's default — one\nzone, a detail that replaces the list — is a real shape and it is right for some products and wrong\nfor others, and nothing about the domain plan reveals which. The question is *while a person is\nreading one record, what else must stay on screen*, and its answer comes from the ICPs and the\njobs-to-be-done that are already decided (on an application with no market, from\nthe operating team and the work the vision and the requirements describe): users who triage a queue need the list to stay, users who\nopen one record and finish it do not, and a product whose main surface is a board or a map needs the\ndetail to float over it rather than take a share of it.\n\nDecide it HERE, with the market and definition artifacts in front of you, and put the reasoning in\nthe surface's `rationale` — a later task reading only the layout cannot recover why that shape was\nchosen, and the shape decides whether a detail needs its own page chrome, whether a list wants\nselection affordances, and whether operations must be addressable. `config-navigation`\nopens with that question, translates the product shapes into what to declare, and names the trade\nthat is hardest to reverse: content in an overlay has no URL, so nobody can link to it.\n\n## Step 2 — Decide the surfaces\n\nA surface exists because a person has to do something the generated list and read cannot do. Six\nkinds, each naming the skill that authors it:\n\n| kind | what it is | belongs to |\n|---|---|---|\n| `RESOURCE_COMPOSITE_VIEW` | a workspace composing several resources around one | a resource |\n| `RESOURCE_CUSTOM_VIEW` | a bespoke screen for one operation — a wizard, a rich read | a resource |\n| `RESOURCE_EXECUTION_VIEW` | drives a long-running execution and shows its progress | a resource |\n| `RESOURCE_CHART_VIEW` | a chart over one resource's rows | a resource |\n| `APPLICATION_VIEW` | an application-level view or dashboard — the home a person opens on | a module |\n| `CUSTOM_COMPONENT` | a component several surfaces reuse | a module |\n\nThe first four are declared in ONE resource's ui-behavior, so each names its resource; the last two\nbelong to their module and must not. The plan refuses both mistakes, in both directions.\n\n**Plan an application view.** An application with none opens on whatever the shell defaults to,\nwhich is nobody's decision.\n\n**Decide the home** (`home`): what a person sees first when they open the application. Two earlier\nruns decided none, and both opened on the framework's welcome page. It is one of two things, the two\nthe engine can show at the root:\n\n- `VIEW` — a planned `APPLICATION_VIEW`, shown in place (name its slug). Only an application view: the\n root looks the view up among the application-level views, so a view owned by one resource (a\n `RESOURCE_COMPOSITE_VIEW`) is not found there. When the home is one resource's view, plan an\n application view that is the home, or make the home that resource's operation;\n- `RESOURCE_OPERATION` — a resource's operation the root opens (module, resource, and the operation:\n `list`, `read`, or a custom verb), reached through that operation's default variant.\n\nChoose it for the group that opens the application most, from what the creator stated about the\nuser groups and their devices (the declared `creator_stated_facts` context section of your brief): a field worker on a phone\nlands on today's jobs, an office manager at a desk on the pipeline. Say why in its `rationale`. The\nhome is authored in `GLOBAL_VIEWS`, so compose that surface when you decide one.\n\n## Step 3 — Name the preset components each surface reuses\n\nThis is the field this plan exists for. The framework ships a component catalogue, and a coding\nagent that has not been told which components to reuse builds the surface out of raw elements —\nbypassing the theme, the surface policy and the accessibility behaviour every preset carries. Read\nthe catalogue (`frontend-component-catalog`) and name the components each surface is composed from.\n\nA `CUSTOM_COMPONENT` reuses nothing by definition: it IS the reusable thing.\n\n## Step 4 — Make every surface accountable\n\nEach carries `servesRefs`: the requirement, feature draft, roadmap phase or success criterion that\nasked for it. A surface accountable to nothing is one nobody asked for, and the plan reports it.\n\n## Step 5 — Plan the journey\n\nA new person arrives at an application they have never used. Decide what recognises their progress\nand what tells them what to do first. **Plan at least one of the two** — a plan with neither is\nreported, because a new person then meets a product that neither welcomes nor guides them. An\ninternal tool may rightly have neither; say so by leaving both empty on purpose.\n\n**Milestones** — the moments worth recognising: a person's first record of the thing the product is\nfor, a count that shows it is working for them, a moment a whole organization reaches together. Each\nnames its identifier as a slug (`first-deal-won`, declared `FIRST_DEAL_WON` in code), its module,\nthe resource whose operation earns it, and the moment in the person's own terms. How loudly each one\ncelebrates is decided when it is built, not here.\n\n**Guidance** — two shapes, and choosing between them is the decision:\n\n| kind | what it is | use it when |\n|---|---|---|\n| `ONBOARDING_DOCUMENT` | embedded on a screen — a welcome announcement, a getting-started stepper | the guidance belongs to a place, and should be there whenever that place is |\n| `GUIDANCE_FLOW` | triggered by an event — a banner after the first X, a tour, a one-question survey | the guidance belongs to a moment, and should appear once, right after something happened |\n\nFive rules decide whether planned guidance will ever be seen — plan against them:\n\n- **Only one triggered overlay shows at a time.** The others wait behind it until it is finished,\n skipped or dismissed, and a waiting one is dropped if the page reloads first — so a second flow\n planned on the same moment is often never seen. Give each flow its own moment.\n- **A flow shows once per person.** Guidance that should appear every time — an empty-list message —\n is not a flow; it belongs to the resource's own screen.\n- **A gate is a milestone the person already holds.** `gatedByMilestoneRefs` must name milestones\n earned BEFORE the flow's moment, never the one that same moment earns.\n- **Keep refs stable.** A guidance ref keys every person's saved progress; renaming it forgets it.\n- **A document names its host.** An `ONBOARDING_DOCUMENT` is seen only where a view embeds it, so it\n names that view in `hostViewRef` — a view you plan above (this plan lists every view the application\n keeps, so a view it already has is restated here), written as that view's `slug`, and a view of the\n document's OWN module: a document is declared by the module whose view shows it, and its build task\n writes only there. A host you did not plan is reported back to you; if it is still unplanned on the\n last attempt, the document is dropped when the plan lands, never the plan. A flow names none: its\n trigger shows it.\n\nBoth carry `servesRefs`, like every surface.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every view ref that still has a reason to exist — build tasks\nname them, and a moved ref orphans the task that produced its surface. The same holds for milestone\nidentifiers and guidance refs, with one more reason: people's progress is stored against them.\n\n## What you emit\n\n- The **experience plan** at `specifications/src/experience-plan/index.ts` — the configuration\n surfaces this application composes, the views it carries — each with its kind, the module (and\n resource) it belongs to, what a person does on it, the presets it reuses and what it serves — its\n journey (the milestones it recognises and the guidance toward them), and the application's `home`:\n what a person sees first.\n\n## Verification\n\n- Every `moduleRef` and `resourceRef` names something the domain plan declares.\n- Every `reusesComponentRefs` entry names a component the catalogue carries.\n- `rg -n \"kind: ExperienceViewKind\" specifications/src/experience-plan/index.ts | wc -l` — the number\n of view tasks the build lane will emit.\n- Every `triggerResourceRef` names a resource the domain plan declares, and no two guidance flows are\n planned on the same moment.\n- Every `gatedByMilestoneRefs` entry names a planned milestone or one the application already declares.\n- A home is decided; a `VIEW` home names a planned `APPLICATION_VIEW`, a `RESOURCE_OPERATION` home names a\n module and resource the domain plan declares, and `GLOBAL_VIEWS` is composed.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem, so a path here would be an instruction answered from\nrecollection (#1435). Each skill is named by its REF, and one reaches this step as a BODY\n(`method.skillBodyRefs`): **`frontend-component-catalog`**. That is not a convenience — naming the\npresets each surface reuses is this plan's whole point, and a model without the catalogue in front\nof it invents component names that resolve to nothing.\n\nThe rest are the contracts the CODING AGENT opens when it builds each task:\n\n- `views-composite-authoring` — what a composite view IS, so a planned one is one the build lane can author.\n- `resource-custom-view` — a custom view's shape and its binding.\n- `spec-composite-view-update` — the specification a composite view owes.\n- `views-add-composite-view`, `views-add-custom-view`, `views-execution-authoring`,\n `views-chart-authoring`, `views-app-level`, `engine-component-registration` — one per view KIND,\n bound to the emitted task by `EXPERIENCE_VIEW_SKILL_REF`.\n- `config-app-shell`, `config-navigation`, `config-design-system`, `layout-2d-adoption` — one per\n configuration SURFACE, bound by `EXPERIENCE_CONFIGURATION_SKILL_REF`.\n- `milestones-and-celebrations` — how a planned milestone is declared and celebrated, bound by\n `EXPERIENCE_MILESTONE_SKILL_REF`.\n- `guidance-onboarding-authoring` — how a planned document or flow is authored, bound by\n `EXPERIENCE_GUIDANCE_SKILL_REF`.\n",
|
|
45
45
|
"skillRefs": [
|
|
46
46
|
"frontend-component-catalog",
|
|
47
47
|
"views-composite-authoring",
|
|
@@ -50,6 +50,7 @@
|
|
|
50
50
|
"config-navigation",
|
|
51
51
|
"config-app-shell",
|
|
52
52
|
"config-design-system",
|
|
53
|
+
"layout-2d-adoption",
|
|
53
54
|
"milestones-and-celebrations",
|
|
54
55
|
"guidance-onboarding-authoring"
|
|
55
56
|
],
|
|
@@ -57,7 +58,8 @@
|
|
|
57
58
|
"frontend-component-catalog"
|
|
58
59
|
],
|
|
59
60
|
"contextSources": [
|
|
60
|
-
"workspace_truth"
|
|
61
|
+
"workspace_truth",
|
|
62
|
+
"creator_stated_facts"
|
|
61
63
|
],
|
|
62
64
|
"draftableDocumentDefinitionRefs": [],
|
|
63
65
|
"suspendsForClarification": false,
|
|
@@ -122,6 +122,11 @@ Exactly three are derivable today, and each from one declared value:
|
|
|
122
122
|
| `EMAIL_TRANSACTIONAL` | the same — tenant invitations send mail |
|
|
123
123
|
| `BILLING` | the business model's revenue model charges users |
|
|
124
124
|
|
|
125
|
+
**The application's line can exclude a capability, and then nothing derives it.** An internal tool has no billing at
|
|
126
|
+
all: on that line the `billing-provider` question is not asked, the executor never enables `BILLING` whatever else
|
|
127
|
+
implies it, and a configuration that enables it anyway is reported on the run result as contradicting the line
|
|
128
|
+
(`engineCapabilitiesContradictingLine`), never switched off for you.
|
|
129
|
+
|
|
125
130
|
**Compliance constraints do NOT select a capability, and this method said for months that they were
|
|
126
131
|
"the primary driver".** They are not, and the reason is recorded where the derivation lives
|
|
127
132
|
(`FOUNDATION_CAPABILITY_BASIS`, which is TOTAL over the capability vocabulary and names why each
|
|
@@ -46,7 +46,7 @@
|
|
|
46
46
|
"outputs": [],
|
|
47
47
|
"stepOutputs": [],
|
|
48
48
|
"method": {
|
|
49
|
-
"guidance": "# Foundation — Domain Plan → Configured, Bootable App Skeleton (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis method composes existing tooling: `wildo init` creates the SaaS skeleton and\nattempts knowledge delivery, `wildo assets sync` refreshes that knowledge, and\n`wildo setup --non-interactive` followed by `wildo local init` configures and verifies\nthe local environment. It is guidance consumed by the application-creation lane,\nnot an automatically executed CLI script. The registered foundation executor composes\nmodule and resource shells and tenancy configuration from the domain plan; it does\nnot execute this full init/assets/setup sequence. Fulfil those prerequisites and\npostconditions separately and record actual command outcomes. Tool availability\nalone does not prove that a foundation run succeeded.\n\n## Where you are in the journey\n\nThis is the **foundation** playbook — the point in the **bottom-up** phase where\nthe *plan* becomes a *bootable app*. It runs **after** the `bottom_up.domain-plan`\nplaybook produced (and the creator approved) the **domain plan**: the module\ndecomposition, the per-module resource inventory, and the inter-resource\nrelationship intents. Its preconditions — `phase_is bottom_up` and\n`artifact_exists domain-plan` and `artifact_expected vision-brief` — mean the journey\nhas entered the build-shaping phase and the load-bearing artifact is present: the\n**domain plan**, whose modules are registered and whose tenancy decides two of the three\nderived capabilities. The vision is SEQUENCING here rather than readiness (#1434): nothing\nin this playbook reads its content, and it is enforced harder upstream — the market\nsnapshot and the requirements both gate on it, and the domain plan gates on those. The\nroute-bound `transition_committed` fact that authorized and applied crossing from top-down into\nbottom-up was the domain-plan playbook's duty (it is the first bottom-up playbook);\nyou do not re-cross that boundary — the domain plan's existence already sits behind\nit.\n\nYou are not re-opening the domain plan here — you are turning an *approved* plan\ninto the *configured application skeleton the build loop then fills in*.\n\n## What this playbook does\n\nYou are the **foundation engineer**. This playbook reads the approved domain plan\nand the vision brief, then configures and brings up the application skeleton so the\nbuild loop has a real workspace to author into. First inspect the destination: create\na fresh skeleton with `wildo init` in an empty directory, or preserve the existing\napplication. Then perform the configuration-authoring and bring-up steps below.\nThe method describes their order; it does not itself execute the commands.\n\n1. **The engine capabilities are DERIVED for you**, from the approved domain plan's tenancy and the\n business model's revenue model. You do not choose them — see \"Engine capabilities\" below.\n2. **Declare the domain-plan's modules** at the SaaS root (they are registered across\n the runtimes after the skeleton is present, so it boots with them).\n3. **Select the providers** the enabled capabilities need.\n4. **Record the compliance declarations you were given** — the operating entity and\n the jurisdictions, from the elicitation answers, into `./wildo.saas.config.ts`.\n See `config-saas` and its `references/compliance-declarations.md`.\n5. **Verify and bring up the configured project** — check the existing skeleton\n and knowledge delivery, run `wildo setup --non-interactive`, then `wildo local init`.\n\nYou emit **no artifact**. The deliverable is the app itself: `./wildo.saas.config.ts`,\nthe materialized skeleton, and a verified local initialization. Record *why* each\ncapability, module and provider was chosen in the config's own comments, where the\nnext reader of that file will find it.\n\nThis is a **foundation pass**. You enable capabilities, declare modules as shells,\nselect providers, and bring the skeleton up. Deterministic composition may create\nresource shells from the domain plan. Business-specific fields, processing, UI behavior,\nviews and navigation are the downstream build work; a generated shell does not\ncomplete that work.\n\n## Read state first — the artifacts you read, the files you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before configuring\nanything, inspect the target directory. For a new application, run `wildo init`\nin an empty destination first, then refine its generated configuration from the\napproved plan. Do not write the planned config into an empty destination and then\nexpect initial scaffolding to merge around it. For an existing application, keep\nits source and use the documented repair/composition paths; never scaffold over it.\nThen:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it. Confirm the domain plan is present and\n approved, and check whether a `./wildo.saas.config.ts` already exists from an\n earlier run (refine it, do not re-author — see below).\n2. Read the **domain plan** (`domain-plan` family — the modules to register + their\n resource inventory). The executor also reads the landed **business model** if there is\n one, for the billing capability alone; it may legitimately be absent, per the top-down\n phase-gate's optional posture.\n\n **Nothing else is read.** This list used to continue with the market snapshot (\"its ICPs sharpen\n capability selection\"), the requirements and the roadmap (\"which modules are MVP-critical, so you\n enable what the first release needs\"). None of the three reaches the executor, and none ever did\n (#1434). They are no longer declared as inputs either, so the declaration and the prose now say\n the same thing.\n\n// Operator affordances (the executor itself is handed the domain-plan VALUE directly):\n// `wildo context journey` — the eligibility board, runs in flight\n// `wildo context info specification-artifacts` — per-family landed state and rendered content\n\nThe executor **reads** `domain-plan` (handed to it, relationship drafts included) and the landed\n`business-model`; it **writes** `./wildo.saas.config.ts` and the materialized skeleton — app files,\ncommitted to git, which is where the record of what was decided lives.\n\nThis line used to name six families (#1434). Four of them reached nothing.\n\n## Step 1 — Derive and enable the engine capabilities\n\nEngine capabilities are the framework surfaces the app turns on (organizations, billing,\nnotifications, audit trails, and so on). **THE EXECUTOR DERIVES THEM. Nothing here chooses one.**\n\nExactly three are derivable today, and each from one declared value:\n\n| capability | derived from |\n|---|---|\n| `ORGANIZATIONS` | the domain plan's `tenancy` is `organizations` |\n| `EMAIL_TRANSACTIONAL` | the same — tenant invitations send mail |\n| `BILLING` | the business model's revenue model charges users |\n\n**Compliance constraints do NOT select a capability, and this method said for months that they were\n\"the primary driver\".** They are not, and the reason is recorded where the derivation lives\n(`FOUNDATION_CAPABILITY_BASIS`, which is TOTAL over the capability vocabulary and names why each\nremaining one is underivable). The clearest case is the one this method used to point at: where an\naudit trail must LIVE — a ledger, a SIEM — is an operator decision about retention and independence\nrather than a product fact, and leaving that capability out removes no control objective, because\nassurance reads the application's own audit store.\n\nA capability nothing derives is not enabled by guessing. It is enabled deliberately, later, by\nwhoever decides it — which is why the basis map records a reason per capability instead of a\nquestion.\n\nHistorical note, kept because it is the defect rather than a detail (#1434): this section described a\nderivation the runtime cannot perform — four steps of \"walk the constraints\", \"treat these as\nsharpeners\", \"every enabled capability must trace to a compliance constraint\" — and a reader believed\ncompliance constraints shaped the foundation. Nothing walked anything. The market snapshot, the\nrequirements and the roadmap were declared inputs of this playbook for the same reason and reached\nthe same nobody; they are no longer declared.\n\nThe `config-saas` skill carries the vocabulary for the `engineCapabilities` block of\n`./wildo.saas.config.ts`. The executor writes that block; read the skill when you need to understand\nwhat an enabled capability means, not to decide one.\n\n## Step 1b — Apply the capability composition's optional packages\n\nWhen a `capability-composition` has landed (`bottom_up.capability-composition`), the executor\napplies every scenario it marks NEEDED after the domain scenarios below — the marketing website\n(`add-website`) and the documentation portal (`add-technical-doc`) today — with the application's\nown host facts: its slug and display name from `wildo.saas.config.ts`, the public domain from its\ninfrastructure environments (a remote one first, `localhost` when none declares one), and its port\nblock (website = app port + 1, docs = app port + 2, the convention the dogfood applications use).\nA package whose workspace already exists is left alone and reported as already composed. The run\nrecord names **every scenario applied and every scenario declined with the declaration each came\nfrom** (`compositionScenarios`), so a reader sees why the application has a website — or why not —\nwithout re-deriving it.\n\n## Step 2 — Declare the domain-plan's modules (register across runtimes after materialization)\n\nThe skeleton supplies the root workspaces and registry structure; declaring a\nmodule in configuration alone does not implement its package or contributions.\n\n1. **Declare each approved module at the SaaS root.** Use `config-saas` for the\n module's application configuration and preserve existing module identifiers.\n2. **Materialize and register module shells.** Use the delivered module-composition\n scenario and `module-registration` guidance to create the corresponding shared,\n backend and frontend contributions. Inspect the resulting registry exports;\n `config sync` is not a substitute for authored module implementation. At foundation\n depth the shells must load; business-specific resource behavior remains the build\n loop's work.\n3. **Declare every domain-plan module — and no more.** A module the domain plan named\n that is missing from the config is a GAP; a module in the config the domain plan did\n not name is an unjustified-module CONCERN. Record the declared modules (each traced\n to its domain-plan module) as a comment beside it in the config.\n\n**Do not author the resources here.** The domain plan's per-module resource inventory\ntells you *what* resources each module will own, but authoring their schemas, fields,\nand config is the **build loop's** job. If you catch yourself writing a resource\nschema, stop: that is out of this playbook's depth.\n\n## Step 3 — Select the providers\n\nEnabled capabilities that reach an external service need a **provider** (billing → a\npayment provider; notifications/email → an email provider; file storage → an object\nstore). For each such capability, select and wire the provider scope +\n`providerConfigurations` in `./wildo.saas.config.ts` (the `config-saas` skill covers\nthe provider surfaces). A value the vendor issues per deployment — an OAuth client ID, a\nfrontend SDK DSN — is authored in each environment's\n`./infrastructure/<env>/wildo.infra.<env>.config.ts > providerConfigurations` instead (the\n`infra-environment-config` skill):\n\n- **Every provider matches a declared capability.** A provider wired for no enabled\n capability is a CONCERN; an enabled capability that needs a provider with none\n selected is a GAP.\n- **Do not seed secrets here.** Provider *selection* (which provider, which scope) is\n foundation; the per-environment secret material is seeded by the deterministic\n bring-up / environment step, not authored inline. Record the selected providers\n (each matched to its capability) as a comment beside it in the config.\n\n**The choice itself is the creator's, and the interview carries it.** Billing and SMS are\nthe two capabilities whose every provider needs an account, so the executor cannot pick one:\nit reads the `billing-provider` and `sms-provider` answers from the dossier, declares the chosen\nprovider in the backend scope, selects it as primary and enables the capability. The provider's\nrequired credentials are recorded on the run result as OWED — the application boots, and the\nprovider answers once an operator sets them. Answering `none` — the interview requires an answer to\nevery question, so \"decide later\" is an option — leaves the capability owed exactly as before. The\noptions are the engine providers serving the capability plus `none`; the interview validator refuses\nanything else before the run starts. Email is the exception the executor decides itself: it has a\ncredential-free development substitute (`email-preview`) and needs no choice.\n\n## Step 4 — Record the compliance declarations (only what you were told)\n\nThe creator answered `operating-entity` and `operating-jurisdictions`. Write those answers\ninto `operatorComplianceIdentity` and `operatingJurisdictions`, and **nothing else**.\n\n- **Record the PART you were given.** Every part of `operatorComplianceIdentity` is\n independently declarable, so a creator who named the company and not its lawful bases\n gets `legalEntityName` and `registeredAddress` written and the rest left absent. A\n missing part is reported downstream as outstanding; it does not block anything here.\n- **NEVER invent one.** Not a company name, not an address, not a privacy contact, and\n above all not a lawful basis — that is a legal determination, and `CONSENT` in\n particular would tell a person their data rests on an agreement they could withdraw.\n A produced privacy notice quotes these as fact. An absent declaration is reported as an\n open gap a reader can see; an invented one is published.\n- **Omit the key entirely when you were told nothing.** Absence means \"nobody answered\",\n which is the honest state and the one every consumer already renders correctly. An\n empty object is refused by the schema precisely because it would satisfy the field while\n disclosing nothing.\n- **A jurisdiction needs its `basis`.** \"eu\" alone does not say whether you are established\n there, sell there, or hold data about people there, and those imply different obligations.\n If the creator gave a place without a reason, record neither — ask, or leave it out.\n\nThis step CANNOT fail the run. If the creator answered nothing, write nothing and continue:\nthe application boots, and the gap is visible where it matters rather than here.\n\n(A `foundation-manifest` artifact was declared here until 2026-08-25 and is now\nretired with the app-creation verification/digest aspect. It was a bookkeeping record\nof decisions the config already carries — deleting it costs no fact about the app.)\n\n## Step 5 — Verify materialization and bring up the environment\n\nRun the existing commands from the intended application root with their documented\nprerequisites. Keep application structure, delivered knowledge and running services\nas separately verified results.\n\n1. **Verify the skeleton.** A fresh project starts with `wildo init` in an empty\n destination before the configuration-authoring steps above. Check `frontend/`,\n `shared-lib/`, `backend-api/`, `specifications/` and the generated configuration.\n On a repeat run, preserve existing source; use init's repair path or the relevant\n composition scenario instead of regenerating the project as a new application.\n\n2. **Verify application knowledge delivery.** Init attempts delivery from the\n installed packages and reports delivered or skipped assets. If dependency\n installation was skipped or a package is unavailable, install the required\n packages, then refresh the supported skills/rules and framework assets:\n\n ```bash\n wildo assets sync\n ```\n\n <!-- fwk-provenance-waiver: the command below is named in order to be REFUSED — `wildo fwk` needs a framework workspace and errors inside a generated application, which is exactly why an agent that might reach for it has to recognise the name; translating it away would leave the prohibition with nothing to prohibit. -->\n Read the result and inspect the delivered application guidance. Do not assume\n arbitrary agents/hooks are installed, and do not substitute a framework-developer\n delivery flow for this one — this command is how an application receives them.\n\n3. **Run setup** — configure the app from the authored `./wildo.saas.config.ts` and\n the `./infrastructure/` env configs (the `infra-environment-config` skill owns the\n typed infra env files; the `local-environment-bootstrap` skill owns the `wildo`\n lifecycle). Headless setup is registered and fail-closed on the administrator seed\n environment variables; it mints the environment generation without placeholders.\n\n ```bash\n wildo setup --non-interactive\n ```\n\n4. **Initialize and verify the project** — run the registered convergence journey.\n It regenerates artifacts, starts and readiness-gates backing services, reconciles\n platform Mongo state and credentials, starts native platform services, registers the\n app once, emits all runtime projections, and executes a signed managed-config read.\n\n ```bash\n wildo local init\n ```\n\n5. **Know what a PostgreSQL store owes — and that you do not write its baseline here.** Read the\n store selection you authored in the infra env config:\n\n ```bash\n rg -n \"applicationDatabase\" infrastructure/*/wildo.infra.*.config.ts\n ```\n\n Absent, or MongoDB: there is nothing to do — a collection exists on first write, there is no\n plan, and no migration is ever owed.\n\n `engine: DatabaseEngine.POSTGRESQL`: nothing creates a table implicitly, so until the INITIAL\n migration exists the backend refuses to boot on every table it declares. Do NOT accept a baseline\n with `wildo db diff --update-lockfile`: that writes the lockfile and NO migration, so it records a\n plan whose tables were never created and the boot gate still refuses.\n\n The build loop owns that migration. For an application that declares PostgreSQL and has no\n `backend-api/migrations/schema-plan.lock.json`, the dispatch host derives a `database-migrations`\n step; it runs `wildo db generate`, which, with no lockfile, renders the whole model as the initial\n migration and writes the baseline in the same invocation. The two are one change and are committed\n together. It needs a built `backend-api` (the plan is computed by importing the compiled backend\n registry), so report the store you found and leave the migration to that step.\n\nReport the status of each bring-up step to the creator from its real exit and\npostcondition results. A skipped knowledge delivery or unsuccessful initialization\nis not completion, even when source files exist.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not disable a capability, drop a module,\n or re-select a provider that is already correct. Only enable a newly-justified\n capability, register a newly-added domain-plan module, or correct a provider where\n the definition set genuinely changed.\n- **Reuse existing module ids and provider scopes.** A module already registered keeps\n its id; a provider already selected keeps its scope — never mint a second one for the\n same module/capability.\n- **Follow the definition set.** If the domain plan added a module since the last run,\n reflect it (register the module) — do not re-derive the whole configuration from\n scratch. The delta is visible in `git diff` on the config, which is the record. A new\n compliance constraint does NOT enable a capability here; see Step 1 for why.\n\n## Quality gate — `foundation-configured-coherently` (declarative at scaffold depth)\n\nThe foundation is checked against the `foundation-configured-coherently` **reviewer\nchecklist** (see the end of this method): five invariants (capability derivation, module registration, provider coverage,\nsequence order, and foundation-depth boundary discipline), each marked PASS / CONCERN /\nGAP.\n\nThis checklist is **declarative**: no runtime executes it (rubric-only judge gates were retired at the flexible-intelligence hard cut — judgment runs only through a compiled Evaluation Treatment, and this playbook has none yet), so it ships as the **creator's review checklist** — nothing runs it automatically. The **trust floor** for accepting the foundation today is the\ncreator's `approve_result` review of the produced config and the bring-up result. There is\nintentionally **no deterministic gate**: config validation is a `wildo` CLI concern\n(`config sync` / validate), not a validator in the journey-artifact schemaRef\nvocabulary. Existing command permission and effect boundaries apply independently\nof this reviewer checklist.\n\n## Scaffold-depth boundary\n\nKeep this playbook at foundation depth. Explicitly **out of scope here**:\n\n- **Implementing replacement CLI tooling.** Use the existing init, asset delivery,\n setup and local initialization owners. If a command fails, retain its diagnostic\n evidence and resolve the prerequisite or concrete defect rather than inventing\n another materializer inside the application.\n- **Resource / field / schema authoring.** The config declares modules as shells and\n enables capabilities. The foundation executor can materialize resource shells\n and scope them to the chosen tenancy. Filling those shells with business-specific\n fields, rules, UI behavior, views and navigation belongs to the later build work.\n- **Re-introducing a foundation artifact.** The `foundation-manifest` family was\n retired on 2026-08-25 with the app-creation verification/digest aspect. Do **NOT**\n reshape `_core` to bring it back: the config file and its git history already carry\n every decision it recorded.\n- **Deep capability / provider modelling.** A defended capability-selection model\n (per-compliance-regime obligation → capability mapping, provider cost/feature\n matrices, multi-provider fallback) is a later depth pass. You derive capabilities\n from the definition set with the v1 heuristic above — not a solved obligation graph.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at scaffold\ndepth — deeper capability modelling belongs to a dedicated later pass,\nholistically.\n\n## What you emit\n\n- The authored **`./wildo.saas.config.ts`** (an app file) — the enabled engine\n capabilities, the registered modules, and the selected providers — plus the\n registered module shells across the runtimes and the\n brought-up skeleton.\n- The **bring-up result** reported to the creator: the status of each step, taken from\n its real exit/postcondition rather than from intent. This is a report, not a stored\n artifact — nothing reads it back.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's foundation, which the bottom-up build loop then fills in\nwith authored resources, operations, UX, and integrations.\n\n## References\n\n- `.claude/skills/config-saas/SKILL.md` — the `./wildo.saas.config.ts` authoring\n surface: `engineCapabilities`, `modules`, provider scopes, and `providerConfigurations`.\n- `.claude/skills/module-registration/SKILL.md` — register each domain-plan module\n across the shared / frontend / backend registries so the skeleton boots with it\n (distinct from `config-saas`, which only declares module existence at the root).\n- `.claude/skills/infra-environment-config/SKILL.md` — the typed `./infrastructure/`\n environment configs (backing services, public domain, service auth) the bring-up needs.\n- `.claude/skills/local-environment-bootstrap/SKILL.md` — the `wildo` lifecycle\n (`setup`, `local init`, `local reinit`, `local dev`) for deterministic initialization,\n repair, clean-room recovery, and runtime start.\n\n## Reviewer checklist — `foundation-configured-coherently`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is maintained here as guidance against the current tooling:\n\nJudge whether the authored foundation (the ./wildo.saas.config.ts composition + the materialized skeleton) is a coherent realisation of the approved domain plan and the top-down definition set. Assess five invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) CAPABILITY DERIVATION — every enabled engine capability traces to a compliance/vision, business-model, market, or domain-plan need; unjustified capabilities are a CONCERN and missing required capabilities are a GAP. (2) MODULE REGISTRATION — every approved domain-plan module is declared and registered across runtimes; missing modules are a GAP and extra modules are a CONCERN. (3) PROVIDER COVERAGE — every provider serves a declared capability and every provider-backed capability has a provider. (4) SEQUENCE ORDER AND PROOF — materialize a fresh skeleton in an empty destination (or preserve an existing project) → refine config and module registrations → verify knowledge delivery → wildo setup --non-interactive → wildo local init. Treat setup intent, container health, or an initialization marker as insufficient: local init must reach its signed managed-config-read postcondition. (5) BOUNDARY DISCIPLINE — stay at foundation depth: deterministic resource shells are allowed, but business-specific fields, processing, UI behavior, views and navigation belong to later build work. Use the existing init/assets owners; do not replace them. Headless setup and local init run once their prerequisites are satisfied. This reviewer checklist is declarative; creator approval is the trust floor.\n",
|
|
49
|
+
"guidance": "# Foundation — Domain Plan → Configured, Bootable App Skeleton (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis method composes existing tooling: `wildo init` creates the SaaS skeleton and\nattempts knowledge delivery, `wildo assets sync` refreshes that knowledge, and\n`wildo setup --non-interactive` followed by `wildo local init` configures and verifies\nthe local environment. It is guidance consumed by the application-creation lane,\nnot an automatically executed CLI script. The registered foundation executor composes\nmodule and resource shells and tenancy configuration from the domain plan; it does\nnot execute this full init/assets/setup sequence. Fulfil those prerequisites and\npostconditions separately and record actual command outcomes. Tool availability\nalone does not prove that a foundation run succeeded.\n\n## Where you are in the journey\n\nThis is the **foundation** playbook — the point in the **bottom-up** phase where\nthe *plan* becomes a *bootable app*. It runs **after** the `bottom_up.domain-plan`\nplaybook produced (and the creator approved) the **domain plan**: the module\ndecomposition, the per-module resource inventory, and the inter-resource\nrelationship intents. Its preconditions — `phase_is bottom_up` and\n`artifact_exists domain-plan` and `artifact_expected vision-brief` — mean the journey\nhas entered the build-shaping phase and the load-bearing artifact is present: the\n**domain plan**, whose modules are registered and whose tenancy decides two of the three\nderived capabilities. The vision is SEQUENCING here rather than readiness (#1434): nothing\nin this playbook reads its content, and it is enforced harder upstream — the market\nsnapshot and the requirements both gate on it, and the domain plan gates on those. The\nroute-bound `transition_committed` fact that authorized and applied crossing from top-down into\nbottom-up was the domain-plan playbook's duty (it is the first bottom-up playbook);\nyou do not re-cross that boundary — the domain plan's existence already sits behind\nit.\n\nYou are not re-opening the domain plan here — you are turning an *approved* plan\ninto the *configured application skeleton the build loop then fills in*.\n\n## What this playbook does\n\nYou are the **foundation engineer**. This playbook reads the approved domain plan\nand the vision brief, then configures and brings up the application skeleton so the\nbuild loop has a real workspace to author into. First inspect the destination: create\na fresh skeleton with `wildo init` in an empty directory, or preserve the existing\napplication. Then perform the configuration-authoring and bring-up steps below.\nThe method describes their order; it does not itself execute the commands.\n\n1. **The engine capabilities are DERIVED for you**, from the approved domain plan's tenancy and the\n business model's revenue model. You do not choose them — see \"Engine capabilities\" below.\n2. **Declare the domain-plan's modules** at the SaaS root (they are registered across\n the runtimes after the skeleton is present, so it boots with them).\n3. **Select the providers** the enabled capabilities need.\n4. **Record the compliance declarations you were given** — the operating entity and\n the jurisdictions, from the elicitation answers, into `./wildo.saas.config.ts`.\n See `config-saas` and its `references/compliance-declarations.md`.\n5. **Verify and bring up the configured project** — check the existing skeleton\n and knowledge delivery, run `wildo setup --non-interactive`, then `wildo local init`.\n\nYou emit **no artifact**. The deliverable is the app itself: `./wildo.saas.config.ts`,\nthe materialized skeleton, and a verified local initialization. Record *why* each\ncapability, module and provider was chosen in the config's own comments, where the\nnext reader of that file will find it.\n\nThis is a **foundation pass**. You enable capabilities, declare modules as shells,\nselect providers, and bring the skeleton up. Deterministic composition may create\nresource shells from the domain plan. Business-specific fields, processing, UI behavior,\nviews and navigation are the downstream build work; a generated shell does not\ncomplete that work.\n\n## Read state first — the artifacts you read, the files you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before configuring\nanything, inspect the target directory. For a new application, run `wildo init`\nin an empty destination first, then refine its generated configuration from the\napproved plan. Do not write the planned config into an empty destination and then\nexpect initial scaffolding to merge around it. For an existing application, keep\nits source and use the documented repair/composition paths; never scaffold over it.\nThen:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it. Confirm the domain plan is present and\n approved, and check whether a `./wildo.saas.config.ts` already exists from an\n earlier run (refine it, do not re-author — see below).\n2. Read the **domain plan** (`domain-plan` family — the modules to register + their\n resource inventory). The executor also reads the landed **business model** if there is\n one, for the billing capability alone; it may legitimately be absent, per the top-down\n phase-gate's optional posture.\n\n **Nothing else is read.** This list used to continue with the market snapshot (\"its ICPs sharpen\n capability selection\"), the requirements and the roadmap (\"which modules are MVP-critical, so you\n enable what the first release needs\"). None of the three reaches the executor, and none ever did\n (#1434). They are no longer declared as inputs either, so the declaration and the prose now say\n the same thing.\n\n// Operator affordances (the executor itself is handed the domain-plan VALUE directly):\n// `wildo context journey` — the eligibility board, runs in flight\n// `wildo context info specification-artifacts` — per-family landed state and rendered content\n\nThe executor **reads** `domain-plan` (handed to it, relationship drafts included) and the landed\n`business-model`; it **writes** `./wildo.saas.config.ts` and the materialized skeleton — app files,\ncommitted to git, which is where the record of what was decided lives.\n\nThis line used to name six families (#1434). Four of them reached nothing.\n\n## Step 1 — Derive and enable the engine capabilities\n\nEngine capabilities are the framework surfaces the app turns on (organizations, billing,\nnotifications, audit trails, and so on). **THE EXECUTOR DERIVES THEM. Nothing here chooses one.**\n\nExactly three are derivable today, and each from one declared value:\n\n| capability | derived from |\n|---|---|\n| `ORGANIZATIONS` | the domain plan's `tenancy` is `organizations` |\n| `EMAIL_TRANSACTIONAL` | the same — tenant invitations send mail |\n| `BILLING` | the business model's revenue model charges users |\n\n**The application's line can exclude a capability, and then nothing derives it.** An internal tool has no billing at\nall: on that line the `billing-provider` question is not asked, the executor never enables `BILLING` whatever else\nimplies it, and a configuration that enables it anyway is reported on the run result as contradicting the line\n(`engineCapabilitiesContradictingLine`), never switched off for you.\n\n**Compliance constraints do NOT select a capability, and this method said for months that they were\n\"the primary driver\".** They are not, and the reason is recorded where the derivation lives\n(`FOUNDATION_CAPABILITY_BASIS`, which is TOTAL over the capability vocabulary and names why each\nremaining one is underivable). The clearest case is the one this method used to point at: where an\naudit trail must LIVE — a ledger, a SIEM — is an operator decision about retention and independence\nrather than a product fact, and leaving that capability out removes no control objective, because\nassurance reads the application's own audit store.\n\nA capability nothing derives is not enabled by guessing. It is enabled deliberately, later, by\nwhoever decides it — which is why the basis map records a reason per capability instead of a\nquestion.\n\nHistorical note, kept because it is the defect rather than a detail (#1434): this section described a\nderivation the runtime cannot perform — four steps of \"walk the constraints\", \"treat these as\nsharpeners\", \"every enabled capability must trace to a compliance constraint\" — and a reader believed\ncompliance constraints shaped the foundation. Nothing walked anything. The market snapshot, the\nrequirements and the roadmap were declared inputs of this playbook for the same reason and reached\nthe same nobody; they are no longer declared.\n\nThe `config-saas` skill carries the vocabulary for the `engineCapabilities` block of\n`./wildo.saas.config.ts`. The executor writes that block; read the skill when you need to understand\nwhat an enabled capability means, not to decide one.\n\n## Step 1b — Apply the capability composition's optional packages\n\nWhen a `capability-composition` has landed (`bottom_up.capability-composition`), the executor\napplies every scenario it marks NEEDED after the domain scenarios below — the marketing website\n(`add-website`) and the documentation portal (`add-technical-doc`) today — with the application's\nown host facts: its slug and display name from `wildo.saas.config.ts`, the public domain from its\ninfrastructure environments (a remote one first, `localhost` when none declares one), and its port\nblock (website = app port + 1, docs = app port + 2, the convention the dogfood applications use).\nA package whose workspace already exists is left alone and reported as already composed. The run\nrecord names **every scenario applied and every scenario declined with the declaration each came\nfrom** (`compositionScenarios`), so a reader sees why the application has a website — or why not —\nwithout re-deriving it.\n\n## Step 2 — Declare the domain-plan's modules (register across runtimes after materialization)\n\nThe skeleton supplies the root workspaces and registry structure; declaring a\nmodule in configuration alone does not implement its package or contributions.\n\n1. **Declare each approved module at the SaaS root.** Use `config-saas` for the\n module's application configuration and preserve existing module identifiers.\n2. **Materialize and register module shells.** Use the delivered module-composition\n scenario and `module-registration` guidance to create the corresponding shared,\n backend and frontend contributions. Inspect the resulting registry exports;\n `config sync` is not a substitute for authored module implementation. At foundation\n depth the shells must load; business-specific resource behavior remains the build\n loop's work.\n3. **Declare every domain-plan module — and no more.** A module the domain plan named\n that is missing from the config is a GAP; a module in the config the domain plan did\n not name is an unjustified-module CONCERN. Record the declared modules (each traced\n to its domain-plan module) as a comment beside it in the config.\n\n**Do not author the resources here.** The domain plan's per-module resource inventory\ntells you *what* resources each module will own, but authoring their schemas, fields,\nand config is the **build loop's** job. If you catch yourself writing a resource\nschema, stop: that is out of this playbook's depth.\n\n## Step 3 — Select the providers\n\nEnabled capabilities that reach an external service need a **provider** (billing → a\npayment provider; notifications/email → an email provider; file storage → an object\nstore). For each such capability, select and wire the provider scope +\n`providerConfigurations` in `./wildo.saas.config.ts` (the `config-saas` skill covers\nthe provider surfaces). A value the vendor issues per deployment — an OAuth client ID, a\nfrontend SDK DSN — is authored in each environment's\n`./infrastructure/<env>/wildo.infra.<env>.config.ts > providerConfigurations` instead (the\n`infra-environment-config` skill):\n\n- **Every provider matches a declared capability.** A provider wired for no enabled\n capability is a CONCERN; an enabled capability that needs a provider with none\n selected is a GAP.\n- **Do not seed secrets here.** Provider *selection* (which provider, which scope) is\n foundation; the per-environment secret material is seeded by the deterministic\n bring-up / environment step, not authored inline. Record the selected providers\n (each matched to its capability) as a comment beside it in the config.\n\n**The choice itself is the creator's, and the interview carries it.** Billing and SMS are\nthe two capabilities whose every provider needs an account, so the executor cannot pick one:\nit reads the `billing-provider` and `sms-provider` answers from the dossier, declares the chosen\nprovider in the backend scope, selects it as primary and enables the capability. The provider's\nrequired credentials are recorded on the run result as OWED — the application boots, and the\nprovider answers once an operator sets them. Answering `none` — the interview requires an answer to\nevery question, so \"decide later\" is an option — leaves the capability owed exactly as before. The\noptions are the engine providers serving the capability plus `none`; the interview validator refuses\nanything else before the run starts. Email is the exception the executor decides itself: it has a\ncredential-free development substitute (`email-preview`) and needs no choice.\n\n## Step 4 — Record the compliance declarations (only what you were told)\n\nThe creator answered `operating-entity` and `operating-jurisdictions`. Write those answers\ninto `operatorComplianceIdentity` and `operatingJurisdictions`, and **nothing else**.\n\n- **Record the PART you were given.** Every part of `operatorComplianceIdentity` is\n independently declarable, so a creator who named the company and not its lawful bases\n gets `legalEntityName` and `registeredAddress` written and the rest left absent. A\n missing part is reported downstream as outstanding; it does not block anything here.\n- **NEVER invent one.** Not a company name, not an address, not a privacy contact, and\n above all not a lawful basis — that is a legal determination, and `CONSENT` in\n particular would tell a person their data rests on an agreement they could withdraw.\n A produced privacy notice quotes these as fact. An absent declaration is reported as an\n open gap a reader can see; an invented one is published.\n- **Omit the key entirely when you were told nothing.** Absence means \"nobody answered\",\n which is the honest state and the one every consumer already renders correctly. An\n empty object is refused by the schema precisely because it would satisfy the field while\n disclosing nothing.\n- **A jurisdiction needs its `basis`.** \"eu\" alone does not say whether you are established\n there, sell there, or hold data about people there, and those imply different obligations.\n If the creator gave a place without a reason, record neither — ask, or leave it out.\n\nThis step CANNOT fail the run. If the creator answered nothing, write nothing and continue:\nthe application boots, and the gap is visible where it matters rather than here.\n\n(A `foundation-manifest` artifact was declared here until 2026-08-25 and is now\nretired with the app-creation verification/digest aspect. It was a bookkeeping record\nof decisions the config already carries — deleting it costs no fact about the app.)\n\n## Step 5 — Verify materialization and bring up the environment\n\nRun the existing commands from the intended application root with their documented\nprerequisites. Keep application structure, delivered knowledge and running services\nas separately verified results.\n\n1. **Verify the skeleton.** A fresh project starts with `wildo init` in an empty\n destination before the configuration-authoring steps above. Check `frontend/`,\n `shared-lib/`, `backend-api/`, `specifications/` and the generated configuration.\n On a repeat run, preserve existing source; use init's repair path or the relevant\n composition scenario instead of regenerating the project as a new application.\n\n2. **Verify application knowledge delivery.** Init attempts delivery from the\n installed packages and reports delivered or skipped assets. If dependency\n installation was skipped or a package is unavailable, install the required\n packages, then refresh the supported skills/rules and framework assets:\n\n ```bash\n wildo assets sync\n ```\n\n <!-- fwk-provenance-waiver: the command below is named in order to be REFUSED — `wildo fwk` needs a framework workspace and errors inside a generated application, which is exactly why an agent that might reach for it has to recognise the name; translating it away would leave the prohibition with nothing to prohibit. -->\n Read the result and inspect the delivered application guidance. Do not assume\n arbitrary agents/hooks are installed, and do not substitute a framework-developer\n delivery flow for this one — this command is how an application receives them.\n\n3. **Run setup** — configure the app from the authored `./wildo.saas.config.ts` and\n the `./infrastructure/` env configs (the `infra-environment-config` skill owns the\n typed infra env files; the `local-environment-bootstrap` skill owns the `wildo`\n lifecycle). Headless setup is registered and fail-closed on the administrator seed\n environment variables; it mints the environment generation without placeholders.\n\n ```bash\n wildo setup --non-interactive\n ```\n\n4. **Initialize and verify the project** — run the registered convergence journey.\n It regenerates artifacts, starts and readiness-gates backing services, reconciles\n platform Mongo state and credentials, starts native platform services, registers the\n app once, emits all runtime projections, and executes a signed managed-config read.\n\n ```bash\n wildo local init\n ```\n\n5. **Know what a PostgreSQL store owes — and that you do not write its baseline here.** Read the\n store selection you authored in the infra env config:\n\n ```bash\n rg -n \"applicationDatabase\" infrastructure/*/wildo.infra.*.config.ts\n ```\n\n Absent, or MongoDB: there is nothing to do — a collection exists on first write, there is no\n plan, and no migration is ever owed.\n\n `engine: DatabaseEngine.POSTGRESQL`: nothing creates a table implicitly, so until the INITIAL\n migration exists the backend refuses to boot on every table it declares. Do NOT accept a baseline\n with `wildo db diff --update-lockfile`: that writes the lockfile and NO migration, so it records a\n plan whose tables were never created and the boot gate still refuses.\n\n The build loop owns that migration. For an application that declares PostgreSQL and has no\n `backend-api/migrations/schema-plan.lock.json`, the dispatch host derives a `database-migrations`\n step; it runs `wildo db generate`, which, with no lockfile, renders the whole model as the initial\n migration and writes the baseline in the same invocation. The two are one change and are committed\n together. It needs a built `backend-api` (the plan is computed by importing the compiled backend\n registry), so report the store you found and leave the migration to that step.\n\nReport the status of each bring-up step to the creator from its real exit and\npostcondition results. A skipped knowledge delivery or unsuccessful initialization\nis not completion, even when source files exist.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not disable a capability, drop a module,\n or re-select a provider that is already correct. Only enable a newly-justified\n capability, register a newly-added domain-plan module, or correct a provider where\n the definition set genuinely changed.\n- **Reuse existing module ids and provider scopes.** A module already registered keeps\n its id; a provider already selected keeps its scope — never mint a second one for the\n same module/capability.\n- **Follow the definition set.** If the domain plan added a module since the last run,\n reflect it (register the module) — do not re-derive the whole configuration from\n scratch. The delta is visible in `git diff` on the config, which is the record. A new\n compliance constraint does NOT enable a capability here; see Step 1 for why.\n\n## Quality gate — `foundation-configured-coherently` (declarative at scaffold depth)\n\nThe foundation is checked against the `foundation-configured-coherently` **reviewer\nchecklist** (see the end of this method): five invariants (capability derivation, module registration, provider coverage,\nsequence order, and foundation-depth boundary discipline), each marked PASS / CONCERN /\nGAP.\n\nThis checklist is **declarative**: no runtime executes it (rubric-only judge gates were retired at the flexible-intelligence hard cut — judgment runs only through a compiled Evaluation Treatment, and this playbook has none yet), so it ships as the **creator's review checklist** — nothing runs it automatically. The **trust floor** for accepting the foundation today is the\ncreator's `approve_result` review of the produced config and the bring-up result. There is\nintentionally **no deterministic gate**: config validation is a `wildo` CLI concern\n(`config sync` / validate), not a validator in the journey-artifact schemaRef\nvocabulary. Existing command permission and effect boundaries apply independently\nof this reviewer checklist.\n\n## Scaffold-depth boundary\n\nKeep this playbook at foundation depth. Explicitly **out of scope here**:\n\n- **Implementing replacement CLI tooling.** Use the existing init, asset delivery,\n setup and local initialization owners. If a command fails, retain its diagnostic\n evidence and resolve the prerequisite or concrete defect rather than inventing\n another materializer inside the application.\n- **Resource / field / schema authoring.** The config declares modules as shells and\n enables capabilities. The foundation executor can materialize resource shells\n and scope them to the chosen tenancy. Filling those shells with business-specific\n fields, rules, UI behavior, views and navigation belongs to the later build work.\n- **Re-introducing a foundation artifact.** The `foundation-manifest` family was\n retired on 2026-08-25 with the app-creation verification/digest aspect. Do **NOT**\n reshape `_core` to bring it back: the config file and its git history already carry\n every decision it recorded.\n- **Deep capability / provider modelling.** A defended capability-selection model\n (per-compliance-regime obligation → capability mapping, provider cost/feature\n matrices, multi-provider fallback) is a later depth pass. You derive capabilities\n from the definition set with the v1 heuristic above — not a solved obligation graph.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at scaffold\ndepth — deeper capability modelling belongs to a dedicated later pass,\nholistically.\n\n## What you emit\n\n- The authored **`./wildo.saas.config.ts`** (an app file) — the enabled engine\n capabilities, the registered modules, and the selected providers — plus the\n registered module shells across the runtimes and the\n brought-up skeleton.\n- The **bring-up result** reported to the creator: the status of each step, taken from\n its real exit/postcondition rather than from intent. This is a report, not a stored\n artifact — nothing reads it back.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's foundation, which the bottom-up build loop then fills in\nwith authored resources, operations, UX, and integrations.\n\n## References\n\n- `.claude/skills/config-saas/SKILL.md` — the `./wildo.saas.config.ts` authoring\n surface: `engineCapabilities`, `modules`, provider scopes, and `providerConfigurations`.\n- `.claude/skills/module-registration/SKILL.md` — register each domain-plan module\n across the shared / frontend / backend registries so the skeleton boots with it\n (distinct from `config-saas`, which only declares module existence at the root).\n- `.claude/skills/infra-environment-config/SKILL.md` — the typed `./infrastructure/`\n environment configs (backing services, public domain, service auth) the bring-up needs.\n- `.claude/skills/local-environment-bootstrap/SKILL.md` — the `wildo` lifecycle\n (`setup`, `local init`, `local reinit`, `local dev`) for deterministic initialization,\n repair, clean-room recovery, and runtime start.\n\n## Reviewer checklist — `foundation-configured-coherently`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is maintained here as guidance against the current tooling:\n\nJudge whether the authored foundation (the ./wildo.saas.config.ts composition + the materialized skeleton) is a coherent realisation of the approved domain plan and the top-down definition set. Assess five invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) CAPABILITY DERIVATION — every enabled engine capability traces to a compliance/vision, business-model, market, or domain-plan need; unjustified capabilities are a CONCERN and missing required capabilities are a GAP. (2) MODULE REGISTRATION — every approved domain-plan module is declared and registered across runtimes; missing modules are a GAP and extra modules are a CONCERN. (3) PROVIDER COVERAGE — every provider serves a declared capability and every provider-backed capability has a provider. (4) SEQUENCE ORDER AND PROOF — materialize a fresh skeleton in an empty destination (or preserve an existing project) → refine config and module registrations → verify knowledge delivery → wildo setup --non-interactive → wildo local init. Treat setup intent, container health, or an initialization marker as insufficient: local init must reach its signed managed-config-read postcondition. (5) BOUNDARY DISCIPLINE — stay at foundation depth: deterministic resource shells are allowed, but business-specific fields, processing, UI behavior, views and navigation belong to later build work. Use the existing init/assets owners; do not replace them. Headless setup and local init run once their prerequisites are satisfied. This reviewer checklist is declarative; creator approval is the trust floor.\n",
|
|
50
50
|
"skillRefs": [
|
|
51
51
|
"config-saas",
|
|
52
52
|
"module-registration",
|
|
@@ -91,6 +91,18 @@ one declaration written twice, and the plan refuses it.
|
|
|
91
91
|
**A minion's or a worker's own providers are not here.** Those are declared on that surface's own
|
|
92
92
|
`providers` block and belong to the task that builds it.
|
|
93
93
|
|
|
94
|
+
**A third-party provider comes from the registry.** the declared `provider_registry` context section of your brief lists every
|
|
95
|
+
provider module on offer, whether this application has installed it, and the ref it is bound as. When a
|
|
96
|
+
requirement needs a vendor (reading documents, posting to a team chat, filing a task), pick the module that
|
|
97
|
+
fills it, bind it by that ref, and put its install command, `wildo registry add wildo/providers/<name>`, in
|
|
98
|
+
the binding's rationale when it is not installed yet. The binding's build task installs it first. An
|
|
99
|
+
augmentation (a module that adds operations to another provider, such as Teams on `microsoft`) is bound by
|
|
100
|
+
its OWN ref with `augments` naming that provider; its task lands when the application opts it in under
|
|
101
|
+
`providers.augmentations.<augments>`, which also needs a binding (or an existing scope) for the provider it
|
|
102
|
+
augments.
|
|
103
|
+
Never bind a third-party vendor that neither that list nor the workspace carries: no module would provide
|
|
104
|
+
it. A need the registry does not cover is written in the plan's rationale as open, not bound.
|
|
105
|
+
|
|
94
106
|
## Step 4b — Say whether work arrives by email
|
|
95
107
|
|
|
96
108
|
Declare an `inboundChannels` entry with `channel: email` only when the product ACTS on messages people
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "bottom_up.integration-plan",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.2.0",
|
|
4
4
|
"phase": "bottom_up",
|
|
5
5
|
"intent": "Background execution and external reach — decide WHAT RUNS BESIDE THE BACKEND and WHAT THIS APPLICATION REACHES OUT TO: which workers exist and on which runtime, which cron minions wake on their own and exactly which resources each one may read and write, and which providers are bound into which runtime owner's scope. Reads the requirements and feature drafts (what somebody asked for, including the work that cannot happen inside a request), the domain plan (the resources a minion's containment whitelist names) and the roadmap (what is owed when). Every surface names what it is accountable to, because a process nobody asked for is a process nobody maintains. Produces the plan; the foundation composes each package and the decomposer emits the work, each task bound to the skill its runtime or scope names.",
|
|
6
6
|
"preconditions": [
|
|
@@ -38,7 +38,7 @@
|
|
|
38
38
|
],
|
|
39
39
|
"stepOutputs": [],
|
|
40
40
|
"method": {
|
|
41
|
-
"guidance": "# Integration Plan — What Runs Beside the Backend\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## Where you are in the journey\n\nThe domain plan is approved and the requirements are written. You decide **what this application\nruns that is not a request** — its workers and its cron minions — and **what it reaches out to** —\nthe providers it binds, and where.\n\nYou do not write any of it. The foundation composes each package, and\n`bottom_up.build-decompose` turns each entry here into a build task bound to the skill that authors\nit.\n\n## Most applications declare nothing here, and that is an answer\n\nThere is no minimum. An application with no worker, no minion and no extra provider binding is the\nordinary case, and a plan that says so — with a rationale saying why — is complete. Inventing a\nworker to fill a collection composes a package nobody maintains.\n\n## Step 1 — Worker or minion? One question settles it\n\nThis is the distinction the whole plan turns on, and planning one as the other produces either a\npackage that never runs or one that runs with nothing to contain it.\n\n| | **worker** | **minion** |\n|---|---|---|\n| what starts it | the backend calls it | the clock |\n| how it is reached | HTTP routes it registers | nothing reaches it |\n| its authority | the caller's | a containment whitelist of its own |\n| plan it when | work cannot finish inside a request | something must happen because time passed |\n\nA nightly sweep is a minion. A slow import the user triggers is a worker. A nightly sweep that the\nbackend also triggers on demand is **both**, and they are two entries.\n\n## The refs carry a prefix, and the schema refuses one that does not\n\nA worker is `worker-<slug>` and a minion is `minion-<slug>`. You supply the SLUG; the runtime stamps\nthe prefix. Keep the slug kebab-case and starting with a LETTER: a ref beginning with a digit parses\nhere and is then refused when the foundation derives the package's identifiers from it.\n\n## Step 2 — Plan each worker\n\n- **`runtime`** — `NODE` unless the work is CPU-bound enough that the choice is the reason the\n worker exists. Rust is a cargo crate: no shared-lib, no pnpm workspace member, a different\n bootstrap. Choose it deliberately or choose Node.\n- **`purpose`** — what the backend delegates, and **why that cannot happen inside a request**. The\n second half is what a reader checks the decision against.\n- **`jobRefs`** — the routes the entry registers, which is what the backend calls. At least one, and\n **not the worker's own name**: `worker-imports` exposing only `imports` says nothing about what is\n delegated, and the plan reports it.\n\n## Step 3 — Plan each minion, and name its containment\n\n- **`purpose`** — what happens because time passed.\n- **`behaviorRefs`** — the named behaviours the tick performs.\n- **`readsResourceRefs` / `writesResourceRefs`** — **the containment decision, and this is why a\n minion is planned rather than left to the coding agent.** A minion's `resourceAccess` whitelist\n starts DENY-ALL, each named resource must separately opt in, and an empty whitelist logs a soft\n warning and **keeps running** — so a minion whose access nobody decided looks healthy and touches\n nothing. Name the decided resources its tick reads and the ones it writes.\n\n**No schedule here.** The plan says what happens because time passed, never how often: a cadence is\nan operational decision, and the minion's own build task sets it beside the whitelist it must widen\nanyway.\n\n## Step 4 — Bind the providers\n\nOne entry per provider per **scope** — the runtime owner whose declaration it lands in:\n\n| scope | the owner | what the binding is |\n|---|---|---|\n| `BACKEND` | the backend service | a package installed in the backend and scoped to it |\n| `COMPANION` | the dev companion | the same act, in the companion's scope |\n| `FRONTEND_APP` | the application frontend | a browser-bound provider module |\n| `WEBSITE` | the marketing site | the same, on the website's frontend service |\n\nThe same provider on two scopes is legitimate and common; the same provider twice on ONE scope is\none declaration written twice, and the plan refuses it.\n\n**A minion's or a worker's own providers are not here.** Those are declared on that surface's own\n`providers` block and belong to the task that builds it.\n\n## Step 4b — Say whether work arrives by email\n\nDeclare an `inboundChannels` entry with `channel: email` only when the product ACTS on messages people\nsend it — a firm whose clients email documents to their matter, a support desk that turns a message\ninto a ticket. Its `purpose` says what arrives and what the application does with it; `servesRefs`\nnames what asked for it.\n\nThis declaration is what switches the receiving capability on: the foundation derives `EMAIL_INBOUND`\nfrom it and records the provider it is owed, so nobody is asked. Do not declare it because the product\nSENDS email — sending is another capability — and never declare a webhook: a signed delivery from\nanother system is derived for that delivery, not planned.\n\n## Step 5 — Make every surface accountable\n\nEach worker and minion carries `servesRefs`: the requirement, feature draft, roadmap phase or\nsuccess criterion that asked for it. A background process accountable to nothing is one nobody\nasked for, and the plan reports it.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every worker and minion ref that still has a reason to exist —\nbuild tasks name them, and a moved ref orphans the task that produced its package.\n\n## What you emit\n\n- The **integration plan** at `specifications/src/integration-plan/index.ts` — the workers, the\n minions, the provider bindings and the inbound channels this application carries, with the\n rationale for the shape as a whole.\n\n## Verification\n\n- Every `readsResourceRefs` / `writesResourceRefs` entry names a resource the domain plan declares.\n- No worker's only `jobRefs` entry repeats its own name.\n- `rg -n \"workerRef|minionRef\" specifications/src/integration-plan/index.ts | wc -l` — the number of\n packages the foundation will compose.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem, so a path here would be an instruction answered from\nrecollection (#1435). Each skill is named by its REF, and two reach this step as BODIES\n(`method.skillBodyRefs`): **`worker-authoring`** and **`minion-authoring`**. That is not a\nconvenience — step 1's question is a runtime contract, and step 3's containment chain has three\nparts of which two live outside the minion's own package, so neither is answerable from memory.\n\nThe rest are the contracts the CODING AGENT opens when it builds each task:\n\n- `provider-backend-package` — installing and scoping a provider on a backend-side owner, bound to\n the emitted task by `INTEGRATION_PROVIDER_BINDING_SKILL_REF` for the `BACKEND` and `COMPANION`\n scopes.\n- `provider-frontend-file-picker` — the frontend provider-module mechanism, bound for the\n `FRONTEND_APP` and `WEBSITE` scopes.\n- `provider-operation-calls` — how a bound provider's operations are actually called, which is what\n makes a binding worth having.\n- `resource-external-data` — the other way to reach another system: read-through or pipeline, when\n what you want is DATA rather than a provider call.\n- `configure-billing` — the worked five-surface chain for the provider binding most applications\n need first.\n- `inbound-channels` — what a declared inbound channel becomes: the handler that decides what a\n message causes, the sender assurance it requires, and whether it answers.\n",
|
|
41
|
+
"guidance": "# Integration Plan — What Runs Beside the Backend\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## Where you are in the journey\n\nThe domain plan is approved and the requirements are written. You decide **what this application\nruns that is not a request** — its workers and its cron minions — and **what it reaches out to** —\nthe providers it binds, and where.\n\nYou do not write any of it. The foundation composes each package, and\n`bottom_up.build-decompose` turns each entry here into a build task bound to the skill that authors\nit.\n\n## Most applications declare nothing here, and that is an answer\n\nThere is no minimum. An application with no worker, no minion and no extra provider binding is the\nordinary case, and a plan that says so — with a rationale saying why — is complete. Inventing a\nworker to fill a collection composes a package nobody maintains.\n\n## Step 1 — Worker or minion? One question settles it\n\nThis is the distinction the whole plan turns on, and planning one as the other produces either a\npackage that never runs or one that runs with nothing to contain it.\n\n| | **worker** | **minion** |\n|---|---|---|\n| what starts it | the backend calls it | the clock |\n| how it is reached | HTTP routes it registers | nothing reaches it |\n| its authority | the caller's | a containment whitelist of its own |\n| plan it when | work cannot finish inside a request | something must happen because time passed |\n\nA nightly sweep is a minion. A slow import the user triggers is a worker. A nightly sweep that the\nbackend also triggers on demand is **both**, and they are two entries.\n\n## The refs carry a prefix, and the schema refuses one that does not\n\nA worker is `worker-<slug>` and a minion is `minion-<slug>`. You supply the SLUG; the runtime stamps\nthe prefix. Keep the slug kebab-case and starting with a LETTER: a ref beginning with a digit parses\nhere and is then refused when the foundation derives the package's identifiers from it.\n\n## Step 2 — Plan each worker\n\n- **`runtime`** — `NODE` unless the work is CPU-bound enough that the choice is the reason the\n worker exists. Rust is a cargo crate: no shared-lib, no pnpm workspace member, a different\n bootstrap. Choose it deliberately or choose Node.\n- **`purpose`** — what the backend delegates, and **why that cannot happen inside a request**. The\n second half is what a reader checks the decision against.\n- **`jobRefs`** — the routes the entry registers, which is what the backend calls. At least one, and\n **not the worker's own name**: `worker-imports` exposing only `imports` says nothing about what is\n delegated, and the plan reports it.\n\n## Step 3 — Plan each minion, and name its containment\n\n- **`purpose`** — what happens because time passed.\n- **`behaviorRefs`** — the named behaviours the tick performs.\n- **`readsResourceRefs` / `writesResourceRefs`** — **the containment decision, and this is why a\n minion is planned rather than left to the coding agent.** A minion's `resourceAccess` whitelist\n starts DENY-ALL, each named resource must separately opt in, and an empty whitelist logs a soft\n warning and **keeps running** — so a minion whose access nobody decided looks healthy and touches\n nothing. Name the decided resources its tick reads and the ones it writes.\n\n**No schedule here.** The plan says what happens because time passed, never how often: a cadence is\nan operational decision, and the minion's own build task sets it beside the whitelist it must widen\nanyway.\n\n## Step 4 — Bind the providers\n\nOne entry per provider per **scope** — the runtime owner whose declaration it lands in:\n\n| scope | the owner | what the binding is |\n|---|---|---|\n| `BACKEND` | the backend service | a package installed in the backend and scoped to it |\n| `COMPANION` | the dev companion | the same act, in the companion's scope |\n| `FRONTEND_APP` | the application frontend | a browser-bound provider module |\n| `WEBSITE` | the marketing site | the same, on the website's frontend service |\n\nThe same provider on two scopes is legitimate and common; the same provider twice on ONE scope is\none declaration written twice, and the plan refuses it.\n\n**A minion's or a worker's own providers are not here.** Those are declared on that surface's own\n`providers` block and belong to the task that builds it.\n\n**A third-party provider comes from the registry.** the declared `provider_registry` context section of your brief lists every\nprovider module on offer, whether this application has installed it, and the ref it is bound as. When a\nrequirement needs a vendor (reading documents, posting to a team chat, filing a task), pick the module that\nfills it, bind it by that ref, and put its install command, `wildo registry add wildo/providers/<name>`, in\nthe binding's rationale when it is not installed yet. The binding's build task installs it first. An\naugmentation (a module that adds operations to another provider, such as Teams on `microsoft`) is bound by\nits OWN ref with `augments` naming that provider; its task lands when the application opts it in under\n`providers.augmentations.<augments>`, which also needs a binding (or an existing scope) for the provider it\naugments.\nNever bind a third-party vendor that neither that list nor the workspace carries: no module would provide\nit. A need the registry does not cover is written in the plan's rationale as open, not bound.\n\n## Step 4b — Say whether work arrives by email\n\nDeclare an `inboundChannels` entry with `channel: email` only when the product ACTS on messages people\nsend it — a firm whose clients email documents to their matter, a support desk that turns a message\ninto a ticket. Its `purpose` says what arrives and what the application does with it; `servesRefs`\nnames what asked for it.\n\nThis declaration is what switches the receiving capability on: the foundation derives `EMAIL_INBOUND`\nfrom it and records the provider it is owed, so nobody is asked. Do not declare it because the product\nSENDS email — sending is another capability — and never declare a webhook: a signed delivery from\nanother system is derived for that delivery, not planned.\n\n## Step 5 — Make every surface accountable\n\nEach worker and minion carries `servesRefs`: the requirement, feature draft, roadmap phase or\nsuccess criterion that asked for it. A background process accountable to nothing is one nobody\nasked for, and the plan reports it.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every worker and minion ref that still has a reason to exist —\nbuild tasks name them, and a moved ref orphans the task that produced its package.\n\n## What you emit\n\n- The **integration plan** at `specifications/src/integration-plan/index.ts` — the workers, the\n minions, the provider bindings and the inbound channels this application carries, with the\n rationale for the shape as a whole.\n\n## Verification\n\n- Every `readsResourceRefs` / `writesResourceRefs` entry names a resource the domain plan declares.\n- No worker's only `jobRefs` entry repeats its own name.\n- `rg -n \"workerRef|minionRef\" specifications/src/integration-plan/index.ts | wc -l` — the number of\n packages the foundation will compose.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem, so a path here would be an instruction answered from\nrecollection (#1435). Each skill is named by its REF, and two reach this step as BODIES\n(`method.skillBodyRefs`): **`worker-authoring`** and **`minion-authoring`**. That is not a\nconvenience — step 1's question is a runtime contract, and step 3's containment chain has three\nparts of which two live outside the minion's own package, so neither is answerable from memory.\n\nThe rest are the contracts the CODING AGENT opens when it builds each task:\n\n- `provider-backend-package` — installing and scoping a provider on a backend-side owner, bound to\n the emitted task by `INTEGRATION_PROVIDER_BINDING_SKILL_REF` for the `BACKEND` and `COMPANION`\n scopes.\n- `provider-frontend-file-picker` — the frontend provider-module mechanism, bound for the\n `FRONTEND_APP` and `WEBSITE` scopes.\n- `provider-operation-calls` — how a bound provider's operations are actually called, which is what\n makes a binding worth having.\n- `resource-external-data` — the other way to reach another system: read-through or pipeline, when\n what you want is DATA rather than a provider call.\n- `configure-billing` — the worked five-surface chain for the provider binding most applications\n need first.\n- `inbound-channels` — what a declared inbound channel becomes: the handler that decides what a\n message causes, the sender assurance it requires, and whether it answers.\n",
|
|
42
42
|
"skillRefs": [
|
|
43
43
|
"worker-authoring",
|
|
44
44
|
"minion-authoring",
|
|
@@ -54,7 +54,8 @@
|
|
|
54
54
|
"minion-authoring"
|
|
55
55
|
],
|
|
56
56
|
"contextSources": [
|
|
57
|
-
"workspace_truth"
|
|
57
|
+
"workspace_truth",
|
|
58
|
+
"provider_registry"
|
|
58
59
|
],
|
|
59
60
|
"draftableDocumentDefinitionRefs": [],
|
|
60
61
|
"suspendsForClarification": false,
|
|
@@ -91,6 +91,56 @@ from forgetting the audit log existed.
|
|
|
91
91
|
So: if a destination should not appear anywhere in this application, say so, and say
|
|
92
92
|
why.
|
|
93
93
|
|
|
94
|
+
## First: does this application need it at all? (the fit test)
|
|
95
|
+
|
|
96
|
+
Before WHERE comes WHETHER. Every engine settings destination exists in the framework; that is not
|
|
97
|
+
a reason to show it. A destination is placed only when something this application declared calls
|
|
98
|
+
for it:
|
|
99
|
+
|
|
100
|
+
- **a requirement** that needs it (single sign-on because a requirement says customers sign in with
|
|
101
|
+
their company identity);
|
|
102
|
+
- **an attribute of the customer profile** in your `market-snapshot` input (the ICPs and personas:
|
|
103
|
+
company size, the tools they already run, their technical staff); or
|
|
104
|
+
- **a capability the application enables** (billing settings because billing is on). What is on is
|
|
105
|
+
not yours to guess: the declared `application_enabled_surface` context section of your brief lists the enabled engine
|
|
106
|
+
capabilities, the billing declaration and each user type's sign-in methods, read from the
|
|
107
|
+
configuration. A capability it does not list is off; one it marks UNREADABLE is unknown, and you
|
|
108
|
+
say so rather than treating it as off. A destination whose capability is off serves nothing yet:
|
|
109
|
+
offer it only when the customer evidence asks for it, and say its capability must be switched on.
|
|
110
|
+
|
|
111
|
+
Otherwise it is DECLINED, with the profile reason. One earlier run, for a 1–20 person trade firm,
|
|
112
|
+
declined single sign-on because such a firm "is not assumed to operate an enterprise identity
|
|
113
|
+
provider". Another, from the same inputs, placed SSO, SCIM, SIEM export, webhooks and legal holds
|
|
114
|
+
because "an admin would look here". Only the first answered the question that comes first.
|
|
115
|
+
|
|
116
|
+
The test cuts both ways. For a 2,000-person insurer whose personas name an identity team and whose
|
|
117
|
+
requirements say staff sign in with their company account, declining single sign-on would be the
|
|
118
|
+
error: there the profile and a requirement both call for it, and it is placed, with both cited. Fit
|
|
119
|
+
is read from THIS application's evidence, never from a habit of declining enterprise features.
|
|
120
|
+
|
|
121
|
+
**Enterprise destinations cite their evidence in the rationale.** Single sign-on, directory sync
|
|
122
|
+
(SCIM), security-event export (SIEM), webhooks, legal holds, API clients and data residency are
|
|
123
|
+
placed only with the requirement, profile attribute or capability named in the rationale. "An admin
|
|
124
|
+
would look here" is findability, not fit; it answers a question you have not earned yet.
|
|
125
|
+
|
|
126
|
+
Read who uses the product from what the creator stated (the declared `creator_stated_facts` context section of your brief):
|
|
127
|
+
the user groups and the devices they use. A field worker on a phone and an office manager at a desk
|
|
128
|
+
want different things first, and the sidebar's order should serve the group that opens it most.
|
|
129
|
+
|
|
130
|
+
**When a section or an entry is for one audience only, say so with `requiredRoles`.** A sidebar group and
|
|
131
|
+
a sidebar or command-menu decision may carry `requiredRoles`: the role keys that see it (a field
|
|
132
|
+
technician does not see the office's "Invoices" section). Use it only when the creator's user groups
|
|
133
|
+
really differ in what they open, and name the application's own roles, or core ones like `ORG_ADMIN`.
|
|
134
|
+
Roles count through the role hierarchy, custom roles included: a role that inherits a listed one sees it. Absent means everyone,
|
|
135
|
+
and that is the right answer for most groups. It is refused on the settings rail and the user menu,
|
|
136
|
+
whose destinations carry their own role gating.
|
|
137
|
+
|
|
138
|
+
Hiding is not access control: the person who cannot see "Invoices" can still be allowed to open it.
|
|
139
|
+
If the field technician must not read invoices, that is a role decision on the operation, not a
|
|
140
|
+
placement, and an entry for an operation a viewer cannot perform is hidden from them already. So
|
|
141
|
+
`requiredRoles` is only for narrowing further: an operation everyone may use that only one group
|
|
142
|
+
needs in its navigation.
|
|
143
|
+
|
|
94
144
|
## The criteria, in the order you apply them
|
|
95
145
|
|
|
96
146
|
1. **Scope correctness.** A thing that acts on the whole organization does not sit
|
|
@@ -118,6 +168,32 @@ it is what grounds the generated `settings_hub.categories.<ref>.label` and
|
|
|
118
168
|
filler from the ref alone — which is exactly how a sidebar section came to be
|
|
119
169
|
described as "various tools and utilities".
|
|
120
170
|
|
|
171
|
+
## A crowded settings category gets sub-categories
|
|
172
|
+
|
|
173
|
+
A settings rail category can hold **sub-categories**: headings inside the category that
|
|
174
|
+
gather its sections. Declare them INSIDE the category's group, as its `subGroups` (each with a
|
|
175
|
+
`groupRef`, a `purpose` and an `order`), and place a section under one with `subGroupRef` on the
|
|
176
|
+
section's address (beside the `groupRef` that names the category). A sub-category's ref is scoped
|
|
177
|
+
to its category, so two categories can each have a `people` sub-category.
|
|
178
|
+
|
|
179
|
+
When to use them:
|
|
180
|
+
|
|
181
|
+
- **Group a category of more than about eight sections.** Below that, a flat list is found
|
|
182
|
+
faster than a heading and the list under it. Above it, people scan for a heading first.
|
|
183
|
+
- **Start from the engine's proposal.** People · Billing & entitlements · Security & access ·
|
|
184
|
+
Integrations · Compliance · AI is what a new application is scaffolded with, for both the
|
|
185
|
+
organization and the administration categories. Using the same headings in both lets the
|
|
186
|
+
same kind of surface sit under the same heading in each. Depart from it when this
|
|
187
|
+
application's sections answer different questions, and say why in the purpose.
|
|
188
|
+
- **Leave a category's general entries ungrouped.** The entries that name the scope itself
|
|
189
|
+
(its general settings, the directory of its members' organizations) sit directly in the
|
|
190
|
+
category, above the sub-categories: omit `subGroupRef` on them.
|
|
191
|
+
- **One level only.** A sub-category has no sub-categories of its own; the plan cannot express
|
|
192
|
+
one. Depth discipline applies: a heading inside a heading inside a category is a section
|
|
193
|
+
nobody finds.
|
|
194
|
+
- **A sub-category is a group, so it carries a `purpose`** like any other, and it must have
|
|
195
|
+
something placed in it.
|
|
196
|
+
|
|
121
197
|
## Placing an operator surface commits the application to an AUDIENCE — say which
|
|
122
198
|
|
|
123
199
|
Some subjects exist for whoever OPERATES the product rather than for the people who use it:
|
|
@@ -169,7 +245,9 @@ so the task that follows has something to implement rather than a default to gue
|
|
|
169
245
|
- No subject placed twice on one surface.
|
|
170
246
|
- No application view placed on the settings rail or the user dropdown.
|
|
171
247
|
- Every grouped placement names a group this plan declares, for that same surface.
|
|
172
|
-
- Every
|
|
248
|
+
- Every `subGroupRef` names a sub-category this plan declares under that placement's category.
|
|
249
|
+
- Sub-categories are declared only on `SETTINGS_HUB` categories, each ref once per category.
|
|
250
|
+
- Every group, sub-categories included, has something in it.
|
|
173
251
|
- Every decision, both arms, carries a rationale that would satisfy a reader who
|
|
174
252
|
disagrees with it.
|
|
175
253
|
- The plan states which AUDIENCE it assumes — one application or two — whenever it places or
|