@wildo-ai/framework-knowledge 1.1.10 → 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/derived-artifacts.md +4 -2
- 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 +459 -76
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts.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.d.ts.map +1 -1
- 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/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +5 -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 +11 -6
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +1 -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 +9 -5
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +11 -7
- 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.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +4 -1
- 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 +3 -3
- 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 +3 -2
- 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 +2 -2
- 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 +2 -2
- 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 +26 -7
- 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 -6
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.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.compliance-document-candidate/playbook.definition.d.ts.map +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 +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.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/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +1 -1
- 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 +6 -4
- 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.map +1 -1
- 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.map +1 -1
- 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.map +1 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.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.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.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.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.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 +8 -2
- 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 +8 -2
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.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-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.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.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +4 -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 +350 -23
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +6 -3
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +248 -9
- 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 +3 -3
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +12 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +5 -2
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +13 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +4 -3
- 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 +33 -5
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +3 -3
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +176 -22
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +20 -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 +97 -23
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +30 -3
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +2 -2
- package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +1 -1
- 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 +9 -2
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +2 -2
- 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/playbook.json +1 -1
- 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 +3 -3
- package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +1 -1
- 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 +4 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +5 -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.visual-tone.config.md +26 -8
- package/dist/knowledge/references/build-plan.task-graph.config.md +238 -8
- 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.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.service-provider-organization-wide-access.md → example.authorization.relationship-organization-wide-access.md} +2 -2
- package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +4 -3
- package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +22 -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.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.ui-behavior.enum-badge.md +23 -7
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +52 -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.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 +16 -0
- 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.references.weighted-edges.md +14 -1
- package/dist/knowledge/references/minions.tick-contract.md +2 -2
- package/dist/knowledge/references/placement-plan.config.md +75 -13
- 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/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.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.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 +7 -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.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.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 +18 -16
- 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 +10 -2
- package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +7 -4
- package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +17 -16
- 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 +3 -1
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +17 -11
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +89 -51
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +9 -6
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +141 -32
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +66 -4
- 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 +18 -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 +58 -6
- 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 +58 -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.organization-defaults.md +6 -6
- 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 +34 -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 +51 -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 +38 -9
- 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 +17 -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 +98 -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 +21 -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 +19 -4
- 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.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 +44 -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.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 +544 -32
- 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 +73 -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 +75 -6
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +23 -1
- 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 +4 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +32 -4
- 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 -8
- package/dist/knowledge/references/zod.factories.code.md +18 -9
- package/dist/knowledge/references/zod.factories.duration.md +23 -14
- package/dist/knowledge/references/zod.factories.money.md +24 -15
- 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 +2411 -139
- package/dist/knowledge/registries/playbooks.json +51 -30
- package/dist/knowledge/registries/source-tags.json +8500 -4768
- package/dist/knowledge/rules/database-migration-obligation.md +11 -5
- package/dist/knowledge/skills/INDEX.md +60 -33
- 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-database-migrations/SKILL.md +27 -9
- package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +34 -0
- package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +6 -6
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +124 -3
- 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 +35 -1
- 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 +3 -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 +127 -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/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 +134 -33
- 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 +57 -28
- 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 +17 -6
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +24 -22
- package/dist/knowledge/skills/config-app-shell/references/framework-shell-layout-api.md +528 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +245 -162
- 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/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 +2 -0
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +11 -3
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +18 -5
- 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 +5 -3
- 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 +14 -0
- 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 +46 -5
- package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +7 -0
- package/dist/knowledge/skills/email-add-template/references/framework-email-template-api.md +134 -0
- 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 +281 -20
- 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 +91 -5
- 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 +5 -4
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +27 -17
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +136 -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 +1 -1
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +4 -1
- 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 +107 -2
- 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/references/derived-artifact-currency.md +4 -2
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +14 -1
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +9 -0
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +9 -0
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +2 -1
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +2 -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 +150 -4
- 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 +50 -27
- 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/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 +1 -1
- 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 +9 -5
- 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 +26 -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 +71 -35
- package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +27 -13
- 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 +132 -55
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +49 -4
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +58 -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 +102 -4
- 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 +6 -0
- 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 +18 -0
- 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 +60 -3
- 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 +1 -1
- 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 +195 -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 +176 -10
- package/dist/knowledge/skills/resource-config-wiring/references/framework-webhook-events-api.md +116 -0
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +88 -50
- 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 +71 -12
- 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 +3 -1
- 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 +26 -10
- 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 +9 -7
- 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 +79 -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 +32 -4
- 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 +116 -66
- 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 +203 -18
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +6 -0
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +155 -76
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +19 -17
- 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 +168 -58
- 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/references/data-seeding-mode-picker.md +16 -1
- 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 +141 -32
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +66 -4
- 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/references/framework-companion-exports-contract-api.md +9 -0
- package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +15 -7
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +71 -14
- 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 +14 -5
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -1
- package/dist/knowledge/skills/views-add-custom-view/references/framework-focus-indicator-api.md +145 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +5 -0
- 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 +11 -4
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +11 -2
- 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 +61 -25
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +251 -78
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +1064 -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 +39 -18
- 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 +84 -28
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +67 -64
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +58 -23
- 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 +112 -77
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +24 -13
- 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 +255 -397
- 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 +28 -6
- 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 -326
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +160 -67
- 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 +24 -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 +48 -28
- 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 +561 -302
- 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 +647 -274
- 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 +572 -264
- 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 +603 -332
- 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 +549 -378
- 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 +739 -315
- 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 +183 -67
- 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 +1 -1
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +6 -94
- 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 +16442 -8572
- 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
|
@@ -0,0 +1,96 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ref": "top_down.service-method",
|
|
3
|
+
"version": "0.1.3",
|
|
4
|
+
"phase": "top_down",
|
|
5
|
+
"intent": "Write down how the firm works: the services it sells to its clients and, for each, the case it is worked in — the stages a case moves through, the steps an agent, a person of the firm or the client takes, the decisions only a qualified person may take (who decides, which qualification they need, how long the client waits), what the client receives, how long the evidence is kept and how the service is priced. The creator names the services and the decisions a licensed professional must take; everything else is DRAFTED from those answers, the vision and the market, with the agent work proposed where it relieves the firm's people and never where a decision belongs to them. Produces one ServiceMethod. It is the one place the method is written down: the domain plan, the roles and the build plan derive from it.",
|
|
6
|
+
"preconditions": [
|
|
7
|
+
{
|
|
8
|
+
"kind": "artifact_valid",
|
|
9
|
+
"selector": {
|
|
10
|
+
"family": "vision-brief"
|
|
11
|
+
}
|
|
12
|
+
}
|
|
13
|
+
],
|
|
14
|
+
"inputs": [
|
|
15
|
+
{
|
|
16
|
+
"family": "vision-brief"
|
|
17
|
+
},
|
|
18
|
+
{
|
|
19
|
+
"family": "market-snapshot",
|
|
20
|
+
"intent": "audience"
|
|
21
|
+
},
|
|
22
|
+
{
|
|
23
|
+
"family": "requirements",
|
|
24
|
+
"render": "map"
|
|
25
|
+
},
|
|
26
|
+
{
|
|
27
|
+
"family": "business-model"
|
|
28
|
+
},
|
|
29
|
+
{
|
|
30
|
+
"family": "service-method"
|
|
31
|
+
}
|
|
32
|
+
],
|
|
33
|
+
"outputs": [
|
|
34
|
+
{
|
|
35
|
+
"family": "service-method",
|
|
36
|
+
"schemaRef": "saas-specifications:ServiceMethod",
|
|
37
|
+
"description": "The firm's services and, for each, its case, stages, steps (agent, person or client), decision points (route, qualification, deadline), deliverables, evidence retention and pricing; with the qualifications the decisions need, how the client takes part, the review calendar deadlines are counted on, and the reasons a person gives when correcting an agent."
|
|
38
|
+
}
|
|
39
|
+
],
|
|
40
|
+
"stepOutputs": [],
|
|
41
|
+
"method": {
|
|
42
|
+
"guidance": "# Service Method — How the Firm Works\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What this playbook does\n\nYou are writing down the firm's **method**: the services it sells to its clients and, for each, how a\ncase is worked. The output is one `ServiceMethod`. It is the one place the method is written down; the\ndomain plan, the roles and the build plan derive from it, so a method that is vague here is an\napplication that is vague everywhere.\n\nA firm is not a product its users drive alone. A case is opened for a client, agents and the firm's\npeople work it, a qualified person takes the decisions that carry the firm's responsibility, and the\nclient receives something at the end. Write that down, case by case.\n\n## What the creator decides, and what you draft\n\nThe interview has four questions:\n\n- **`services`** — what the firm sells, what starts a case and what ends it.\n- **`signatories`** — which decisions only a qualified person may take, and what that person must be.\n- **`agent-work`** — which work in a case the creator wants agents to do.\n- **`working-hours`** — where and when the firm's reviewers work.\n\nAn answer the creator gave is theirs: build on it, do not second-guess it. An answer recorded as an\nASSUMPTION (proposed, because the creator did not know or chose a quick interview) is a proposal: use it,\nand keep anything resting on it easy to revise. `agent-work` and `working-hours` are usually assumptions.\n\nEverything else you DRAFT from those answers, the vision and the market: the stages, the steps, the\ndeliverables, the evidence retention, the correction reasons. Draft them so the creator can accept them\nas they are; they will review them.\n\nIf an answer says \"propose it\", the creator delegated that part: propose it from the services. If the\ninterview says \"none\", write none — an empty list is an answer.\n\n## Step 1 — One service per thing the firm sells\n\nEach service is one entry in `services`:\n\n- `serviceRef` — a kebab-case key (`month-end-close`, `annual-audit`). Later families name it.\n- `label` — what the firm calls it.\n- `purpose` — what the CLIENT gets, in one sentence. Not what the firm does: \"the client's books closed\n every month, reconciled and signed off\", not \"we reconcile bank lines\".\n\nTwo services the creator described as one are one service. Do not split a service to look thorough.\n\n## Step 2 — The case, and its stages\n\n`case` is the unit of work a service is delivered in: one close, one audit engagement, one filing.\n\n- `caseRef` — the PLANNED RESOURCE whose rows are the cases, in the domain plan's naming (plural,\n kebab-case: `closes`, `audit-engagements`). The domain plan inventories it and the build plan makes it\n the work unit, the record every model call on the case is costed to.\n- `opensWhen` / `closesWhen` — the events, in the creator's words.\n\n`stages` are the states a case moves through, in order, first stage first. Each has a `meaning`: what is\ntrue of a case in that stage. Include the stage a case returns to when something surfaces after it was\nfinished (\"reopened\") when the creator's work has one. Stage refs are kebab-case and unique within the\nservice.\n\n## Step 3 — The steps, and who carries each one\n\nEach step happens in one stage and is performed by exactly one of:\n\n| `performedBy` | means |\n|---|---|\n| `AGENT` | an agent of the application does it. Say how it runs in `agentShape` |\n| `PERSON` | one of the firm's people does it |\n| `CLIENT` | the client does it (sends documents, answers a question) |\n\nAn agent step names its `agentShape`, and no other step does:\n\n- `AUTONOMOUS` — it runs on its own, on a schedule or an event (reconciling every night, reading every\n document that arrives);\n- `CHAT_ASSISTANT` — a person talks to it and it proposes;\n- `INVOKED` — another part of the application calls it;\n- `FLOW_STEP` — it is one step of a declared flow the application runs.\n\nGive work to an agent where it relieves the firm's people of reading, matching and drafting. **Never\ngive an agent a decision a qualified person must take**: an agent proposes, and the decision point in\nStep 4 is where the person decides.\n\n`readsRefs` and `producesRefs` name the planned resources a step reads and writes, in the domain plan's\nnaming. They are what lets the domain plan know a step needs a resource. Leave them empty rather than\ninventing a resource no requirement implies.\n\n## Step 4 — The decision points: who decides, on what ground, by when\n\nA decision point is where the case waits for a person. Each sits at one step (`stepRef`) and says in\n`decides` what is decided. Then three choices, and they are the heart of this artifact.\n\n**Who decides (`route`):**\n\n| `route` | when |\n|---|---|\n| `owner` | the person whose own work raised it confirms it (accepting what an assistant proposed to them). Nobody vets the owner, so it takes no qualification |\n| `role` | anyone holding a role may decide (any qualified accountant serving the client) |\n| `assignee` | one named person decides (the client's engagement partner). Say who in `assignee`, in the firm's words |\n\n**On what ground (`qualificationRef`):** every `role` and `assignee` decision names a qualification from\n`qualifications`, and an `owner` decision names none. A qualification says:\n\n- `role` — the role the person holds for the client, as the role table keys it\n (`ORG_QUALIFIED_ACCOUNTANT`). It says what the client ENTRUSTED the firm with.\n- `heldBy` — whose people hold that role: `FIRM` when the firm's people take the decision for the client\n (almost always: the qualified accountant, the engagement partner), `CLIENT` when the client's own staff\n take it in their organization (the client's finance director approving a deliverable). A firm-held role\n reaches the firm's people through the relationship the firm serves its clients through, so the build\n confers it there; `ORG_REPRESENTATIVE` is conferred by that relationship already. A role is always one\n a member of an organization holds: never an application role (`APP_…`), and a firm-held role is never\n the client's administration (`ORG_OWNER`, `ORG_ADMIN`), which no relationship may confer.\n- `professionalQualificationKind` — set ONLY when the PERSON must also hold a verified professional\n qualification (a chartered accountant, a licensed engineer). It follows the person, and lapses with\n their licence. The value is a kebab-case kind (`chartered-accountant`) the application declares in its\n `professionalQualificationKinds`; name the kind you need, and the build declares it.\n\nUse the creator's `signatories` answer to choose. A decision the creator tied to a profession (\"a\nchartered accountant\") needs both the role and the professional qualification. A decision tied to a\nposition (\"the engagement partner\") is an `assignee` decision with the role. A review any expert serving\nthe client may do is a `role` decision whose qualification names the role alone. Most decisions need\nonly a role; the professional-qualifications skill shown to you explains the mechanisms and how they\ncombine.\n\n**By when (`decisionDeadline`):** a review that keeps a client waiting says when it is due, as an\nISO-8601 duration (`PT9H`, `P2D`) counted on `basis`: `calendar` (the firm's working hours) or `elapsed`\n(around the clock). A business-time deadline needs `reviewCalendar`, built from the `working-hours`\nanswer: the `timeZone` (an IANA name), the `workingDays`, the `workingHours` (`HH:MM` from and to) and\nthe `holidays` as dates (`YYYY-MM-DD`). When the creator names a calendar (\"French public holidays\"),\nwrite out its dates for the current and next year. A decision with no deadline is allowed, and it is marked:\nthe engine's default lapse and reminders apply.\n\n## Step 5 — What the client receives, what is kept, and what it costs\n\n- `deliverables` — what a case produces for the client, at which stage, from which planned resource\n (`fromResourceRef`). A close report, an audit opinion, a filed return.\n- `evidenceRetention` — how long the case's evidence is kept: a `retentionClass` and its `ground`.\n Records the law requires the firm to keep (accounting documents, working papers) are\n `BUSINESS_RECORDS`; say the ground in plain words and name the jurisdiction the vision gives. You\n state the firm's obligation as you understand it; the compliance lane governs the retention period.\n- `pricing` — `PER_CASE` when each case is billed, `INCLUDED_IN_PLAN` when a subscription covers it,\n `BILLED_OUTSIDE` when the firm bills from its own tools. Read it off the business model when one is on\n record: a plan priced `per_usage` whose `usageUnit` is this service's case (\"close\") makes the service\n `PER_CASE`; a subscription plan that covers the service makes it `INCLUDED_IN_PLAN`. With no business\n model, `BILLED_OUTSIDE`, which commits the application to nothing. A service `PER_CASE` is billed one\n metered unit when its case closes, once per case however often it is reopened; the build records it.\n An internal tool has no billing at all, whatever a business model or a feature line brings: price\n every service `BILLED_OUTSIDE` there. The coherence report names a price per case on such an\n application as the method's gap, and no build can record it.\n\n## Step 6 — How the client takes part, and why a person corrects an agent\n\n- `clientParticipation` — one paragraph: what the client provides, what they answer, what they read.\n- `correctionReasons` — when agents do work a person reviews, the short list of reasons a person gives\n for correcting it (`wrong_account`, `missing_evidence`). Each `reasonCode` is lowercase snake_case.\n They let the firm see why agent work is corrected. Five to eight reasons, specific to the work.\n\n## Refine, don't re-author\n\nWhen a method is already on record, refine it. Keep every ref that still names the same thing, because\nlater families name them; change the content, not the identity.\n\n## What you emit\n\nOne `ServiceMethod`. The schema refuses:\n\n- a step in a stage the service does not declare, and a deliverable at one;\n- an agent step without an `agentShape`, and any other step with one;\n- a decision at a step the service does not declare;\n- an `owner` decision naming a qualification, a `role` or `assignee` decision naming none, and a\n qualification the method does not declare;\n- one resource kept in two retention classes, because two services name it as their evidence;\n- an `assignee` decision with no `assignee`, and an `assignee` on any other decision;\n- a business-time deadline with no `reviewCalendar`, and a deadline that is not a positive duration\n in weeks, days, hours, minutes or seconds (`PT8H`, `P2D`; no years or months);\n- a qualification on a role no member of an organization holds (an application role, an inbound\n handler's, a capability lent through a relationship), and a firm-held one on `ORG_OWNER` or `ORG_ADMIN`;\n- any ref declared twice.\n\nFix the cause it names and answer again.\n\n## Verification\n\n- Every service's `purpose` says what the client gets.\n- Every decision the `signatories` answer named is a decision point, with the role, and the professional\n qualification when the answer named a profession.\n- No agent step decides anything a decision point decides.\n- Every `role` and `assignee` decision names a declared qualification; every qualification is used.\n- Every reviewer decision that keeps a client waiting has a deadline, or the creator said it has none.\n",
|
|
43
|
+
"skillRefs": [
|
|
44
|
+
"professional-qualifications",
|
|
45
|
+
"flows-actors-autonomous-agents",
|
|
46
|
+
"flows-actors-chat-assistant",
|
|
47
|
+
"agent-work-review",
|
|
48
|
+
"organization-relationships",
|
|
49
|
+
"application-roles-authoring",
|
|
50
|
+
"resource-retention-binding"
|
|
51
|
+
],
|
|
52
|
+
"skillBodyRefs": [
|
|
53
|
+
"professional-qualifications"
|
|
54
|
+
],
|
|
55
|
+
"elicitation": {
|
|
56
|
+
"questions": [
|
|
57
|
+
{
|
|
58
|
+
"ref": "services",
|
|
59
|
+
"question": "What services does the firm deliver to its clients? For each, say what the client gets, what starts a case and what ends it — \"a monthly close: it starts on the first business day, it ends when the partner signs the period off\".",
|
|
60
|
+
"kind": "free_text",
|
|
61
|
+
"depth": "essential"
|
|
62
|
+
},
|
|
63
|
+
{
|
|
64
|
+
"ref": "signatories",
|
|
65
|
+
"question": "Which decisions in a case must a qualified person of the firm take, and what must they be? Name the decision and the role or professional qualification (\"posting to the client's books: a chartered accountant\"; \"signing the period off: the client's engagement partner\"). Answer \"none\" if no decision needs a qualified person.",
|
|
66
|
+
"kind": "free_text",
|
|
67
|
+
"depth": "essential",
|
|
68
|
+
"regulatedDomain": true
|
|
69
|
+
},
|
|
70
|
+
{
|
|
71
|
+
"ref": "agent-work",
|
|
72
|
+
"question": "Which work in a case would you like agents to do for the firm's people — reading documents, reconciling, drafting, answering the client? Answer \"propose it\" to have it proposed from the services, or \"none\".",
|
|
73
|
+
"kind": "free_text",
|
|
74
|
+
"depth": "detail"
|
|
75
|
+
},
|
|
76
|
+
{
|
|
77
|
+
"ref": "working-hours",
|
|
78
|
+
"question": "Where do the firm's reviewers work, and when? Give the time zone and the working hours (\"Europe/Paris, 9:00 to 18:00, French public holidays\"). Deadlines on a decision are counted in these hours.",
|
|
79
|
+
"kind": "free_text",
|
|
80
|
+
"depth": "detail"
|
|
81
|
+
}
|
|
82
|
+
]
|
|
83
|
+
},
|
|
84
|
+
"contextSources": [],
|
|
85
|
+
"draftableDocumentDefinitionRefs": [],
|
|
86
|
+
"suspendsForClarification": false,
|
|
87
|
+
"briefAdequacyGate": false,
|
|
88
|
+
"briefAdequacyExcludedSources": []
|
|
89
|
+
},
|
|
90
|
+
"executor": "companion_agent",
|
|
91
|
+
"approval": "approve_result",
|
|
92
|
+
"budget": {
|
|
93
|
+
"maxRuns": 5
|
|
94
|
+
},
|
|
95
|
+
"onFailure": "keep_and_flag"
|
|
96
|
+
}
|
|
@@ -40,6 +40,10 @@ The creator's answer is recorded exactly as given and decides which playbooks th
|
|
|
40
40
|
from here on. It is **not** part of the `VisionSnapshot`: do not restate it in the vision, and never
|
|
41
41
|
answer it on the creator's behalf. If the creator is unsure, describe each option and let them choose.
|
|
42
42
|
|
|
43
|
+
An application created from a blueprint that carries a line already has this question answered: `wildo init`
|
|
44
|
+
recorded the blueprint's line, answered by `blueprint:<id>@<version>`. Choosing the blueprint was the creator's
|
|
45
|
+
choice of line, so it is not asked again. The creator may still change it by answering again.
|
|
46
|
+
|
|
43
47
|
## The elicitation posture
|
|
44
48
|
|
|
45
49
|
- **Interview, do not fill a form.** The typed questions on this playbook
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.vision-elicitation",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.1",
|
|
4
4
|
"phase": "top_down",
|
|
5
5
|
"intent": "Elicit a complete current-horizon product vision from sealed creator input and application context. The provider proposes semantic content; the trusted runtime stamps refs/version and keeps provenance, authority and accepted-family mutation outside model output.",
|
|
6
6
|
"preconditions": [],
|
|
@@ -18,18 +18,19 @@
|
|
|
18
18
|
],
|
|
19
19
|
"stepOutputs": [],
|
|
20
20
|
"method": {
|
|
21
|
-
"guidance": "# Vision Elicitation — Interview Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **vision interviewer**. Your one job is to draw the product's\nfoundational vision out of the creator through a structured conversation, and\nto capture it as a single typed **`VisionSnapshot`** — the `vision-brief`\nartifact. This is the **first** top-down step: everything downstream\n(positioning, the capability map, the compliance posture, the roadmap) reads\nthe vision you produce, so an honest, well-framed vision is the whole task.\n\nYou do **not** design the domain, draft requirements, or write code. You\nelicit *intent* — what the product is, why it should exist, what winning looks\nlike, and what limits bound it — and nothing more. Keep the market family\n(segments, personas) and the requirements family out of scope; the vision\nreferences them later, it does not absorb them.\n\n## The application's line\n\nThe first question, `application-line`, is the kind of application being created: its **main line**.\nThe creator's answer is recorded exactly as given and decides which playbooks this application runs\nfrom here on. It is **not** part of the `VisionSnapshot`: do not restate it in the vision, and never\nanswer it on the creator's behalf. If the creator is unsure, describe each option and let them choose.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, follow up where an answer is thin, and skip a follow-up the\n creator already answered. Reflect each answer back in one line and let the\n creator correct you before you move on.\n- **Progressive is fine.** A `VisionSnapshot` requires only the **idea**; the\n problem statement and mission are OPTIONAL and elicited progressively. If the\n creator can only give you the idea today, capture it, note what is still\n open, and stop — the snapshot persists as partially-elicited and this\n playbook can resume. Never invent a problem or mission the creator did not\n give you just to fill the shape.\n- **An ASSUMED answer is a hypothesis, not the creator's statement.** When the\n creator did not know an answer, or chose the short interview, the companion\n proposed one from their other answers, and either they kept it or an\n unattended round recorded it for them. Such answers\n arrive in your brief marked ASSUMED, with what they rest on. Use them — they\n are why the interview could finish — but keep them consistent with what the\n creator actually said, prefer the creator's own answers wherever the two\n pull apart, and never phrase an assumed answer as the creator's own words or\n intent. Record an assumed constraint or criterion as modestly as it was\n proposed; do not sharpen a guess into a commitment.\n- **One product, one vision.** The snapshot is a single aggregate, not a list\n — one idea, one problem, one mission, plus ref-addressable success criteria\n and constraints. If the creator describes two products, stop and ask which\n one this journey is for.\n\n## What you elicit — one aggregate\n\nWork the vision entity by entity. For each, the target shape and the framing\nquestions:\n\n- **Idea** (REQUIRED). The anchor concept. Capture a quotable one-liner\n (\"X for Y\") and a short paragraph expanding it (core capability, shape of the\n solution). Record any framing caveats or pivots as notes. A vision without an\n idea is nothing — do not proceed to the rest until you have it.\n- **Problem** (optional, WARNed when absent). The pain the product exists to\n solve: the core statement, who is affected (prose — the deep segment model is\n the market family's job), how people cope today, the cost of leaving it\n unsolved, and the timing trigger that makes solving it urgent *now*. This is\n a framing surface, not a sized opportunity model — capture the \"why\", not a\n TAM.\n- **Mission** (optional, WARNed when absent). The enduring purpose: the mission\n statement (what we do, for whom, to what end, in one sentence), the\n aspirational long-term end-state if it fully succeeds, and the guiding\n principles / non-negotiables that constrain *how* the product is built.\n Principles are chosen stances — keep them distinct from the hard external\n constraints below.\n- **Success criteria** (ref-addressable, `success-criterion-<slug>`). What\n \"this succeeded\" concretely looks like. Each criterion is a statement, an\n optional metric and target (free prose at this stage — \"500 weekly active\n teams\", \"median time-to-first-value < 5 min\"), and a coarse horizon bucket\n (`launch` / `short_term` / `long_term`). Do not force a quantified metric\n where the creator only has a qualitative one — a typed metric taxonomy is a\n later concern. A vision with no success criteria cannot be judged\n succeeded — the validator WARNs on it, so push for at least one.\n- **Constraints** (ref-addressable, `constraint-<slug>`). External limits the\n product must be built within, each classified by kind: `technical`,\n `business`, `compliance`, `resource`, `timeline`, or `other`. Capture the\n constraint statement and, where the creator gives it, the rationale (the\n source of the limit).\n - **Compliance constraints get explicit attention.** Ask whether the product\n handles regulated or personal data, operates in a regulated sector or has contractual\n assurance commitments. If so, record each as a\n `kind: compliance` constraint with a **prose** statement (\"Must be\n GDPR-compliant for EU customer personal data\"). Stop at prose — the deep\n per-regime obligation model (control catalogs, data-flow / residency\n matrices) is the compliance-posture step's job, not yours. Getting the\n compliance *seam* named here is what lets that later step engage.\n\n### The product's shape: workflow, users, boundary\n\nThree questions fix what the product IS, so that no later step decides it again: `core-workflow` (the\nstages a piece of work passes through), `user-groups` (who uses it, for what, on which device) and\n`scope-boundary` (what is explicitly left out). Two runs given the same answers must build the same\nproduct, and without these they did not: one built a customer-workflow CRM that left invoicing to\nother tools, the other built invoicing software with no customer follow-up at all.\n\nCarry them into the snapshot in the creator's own terms:\n\n- the workflow's stages, in order, in the idea's `description`;\n- the user groups, what each does, and their devices, in the problem's \"who is affected\" (and in the\n idea when the product's shape depends on them, such as work done in the field on a phone);\n- each scope boundary as a `constraint` of kind `business`, stated as an exclusion (\"Invoicing is out\n of scope: customers keep their accounting tool\"), with the creator's reason as its rationale.\n\nLater steps also receive these answers verbatim, so do not reword a stage or a boundary into\nsomething the creator did not say. An answer of \"nothing\" for the boundary records no constraint.\n\n## What you emit\n\nA single `VisionSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told\n otherwise).\n- `idea` — the required anchor (`oneLiner`, `description`, optional `notes`).\n- `problem` / `mission` — the optional singletons, present only if elicited.\n- `successCriteria[]` — each with a stable kebab-case `ref` prefixed\n `success-criterion-`, unique across the set.\n- `constraints[]` — each with a stable kebab-case `ref` prefixed `constraint-`,\n unique across the set, and a `kind`.\n\nAuthor every entity in English. Use stable, human-readable ref slugs\n(`success-criterion-weekly-active-teams`, `constraint-gdpr-eu-data`) — they are\naddressed by ref downstream, so a duplicate silently drops an entity.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `vision-snapshot-valid`\ngate (`validateVisionSnapshot`) before it commits. Duplicate refs and malformed\nrefs (a success-criterion or constraint ref that is not kebab-case with its\nrequired prefix) are hard **errors** — the gate rejects them. A missing problem,\na missing mission, and an empty success-criteria set are **warnings**: they\nreflect a not-yet-complete vision, they do not block, and the journey persists\nthe snapshot as partially-elicited. Emit clean refs the first time; let the\nwarnings stand honestly when the vision genuinely is not complete yet, rather\nthan inventing entities to silence them.\n\n## Approval\n\nThe drafted `VisionSnapshot` is presented to the creator for approval before it\nbecomes the committed `vision-brief`. Show the vision back in plain prose — the\none-liner, the problem, the mission, the criteria, the constraints — and let the\ncreator confirm or correct it. The vision is the seed every later step trusts;\nit is worth one explicit human sign-off.\n\n## Runtime context\n\nBefore you start, read the current journey state and scope so you elicit the\nvision for the right product, and read any vision that already exists so you\nrefine it rather than re-eliciting it from scratch.\n\n(When a prior vision exists it arrives in your brief as the `vision-brief` input section — refine\nthat content rather than re-eliciting it.)\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n",
|
|
21
|
+
"guidance": "# Vision Elicitation — Interview Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **vision interviewer**. Your one job is to draw the product's\nfoundational vision out of the creator through a structured conversation, and\nto capture it as a single typed **`VisionSnapshot`** — the `vision-brief`\nartifact. This is the **first** top-down step: everything downstream\n(positioning, the capability map, the compliance posture, the roadmap) reads\nthe vision you produce, so an honest, well-framed vision is the whole task.\n\nYou do **not** design the domain, draft requirements, or write code. You\nelicit *intent* — what the product is, why it should exist, what winning looks\nlike, and what limits bound it — and nothing more. Keep the market family\n(segments, personas) and the requirements family out of scope; the vision\nreferences them later, it does not absorb them.\n\n## The application's line\n\nThe first question, `application-line`, is the kind of application being created: its **main line**.\nThe creator's answer is recorded exactly as given and decides which playbooks this application runs\nfrom here on. It is **not** part of the `VisionSnapshot`: do not restate it in the vision, and never\nanswer it on the creator's behalf. If the creator is unsure, describe each option and let them choose.\n\nAn application created from a blueprint that carries a line already has this question answered: `wildo init`\nrecorded the blueprint's line, answered by `blueprint:<id>@<version>`. Choosing the blueprint was the creator's\nchoice of line, so it is not asked again. The creator may still change it by answering again.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, follow up where an answer is thin, and skip a follow-up the\n creator already answered. Reflect each answer back in one line and let the\n creator correct you before you move on.\n- **Progressive is fine.** A `VisionSnapshot` requires only the **idea**; the\n problem statement and mission are OPTIONAL and elicited progressively. If the\n creator can only give you the idea today, capture it, note what is still\n open, and stop — the snapshot persists as partially-elicited and this\n playbook can resume. Never invent a problem or mission the creator did not\n give you just to fill the shape.\n- **An ASSUMED answer is a hypothesis, not the creator's statement.** When the\n creator did not know an answer, or chose the short interview, the companion\n proposed one from their other answers, and either they kept it or an\n unattended round recorded it for them. Such answers\n arrive in your brief marked ASSUMED, with what they rest on. Use them — they\n are why the interview could finish — but keep them consistent with what the\n creator actually said, prefer the creator's own answers wherever the two\n pull apart, and never phrase an assumed answer as the creator's own words or\n intent. Record an assumed constraint or criterion as modestly as it was\n proposed; do not sharpen a guess into a commitment.\n- **One product, one vision.** The snapshot is a single aggregate, not a list\n — one idea, one problem, one mission, plus ref-addressable success criteria\n and constraints. If the creator describes two products, stop and ask which\n one this journey is for.\n\n## What you elicit — one aggregate\n\nWork the vision entity by entity. For each, the target shape and the framing\nquestions:\n\n- **Idea** (REQUIRED). The anchor concept. Capture a quotable one-liner\n (\"X for Y\") and a short paragraph expanding it (core capability, shape of the\n solution). Record any framing caveats or pivots as notes. A vision without an\n idea is nothing — do not proceed to the rest until you have it.\n- **Problem** (optional, WARNed when absent). The pain the product exists to\n solve: the core statement, who is affected (prose — the deep segment model is\n the market family's job), how people cope today, the cost of leaving it\n unsolved, and the timing trigger that makes solving it urgent *now*. This is\n a framing surface, not a sized opportunity model — capture the \"why\", not a\n TAM.\n- **Mission** (optional, WARNed when absent). The enduring purpose: the mission\n statement (what we do, for whom, to what end, in one sentence), the\n aspirational long-term end-state if it fully succeeds, and the guiding\n principles / non-negotiables that constrain *how* the product is built.\n Principles are chosen stances — keep them distinct from the hard external\n constraints below.\n- **Success criteria** (ref-addressable, `success-criterion-<slug>`). What\n \"this succeeded\" concretely looks like. Each criterion is a statement, an\n optional metric and target (free prose at this stage — \"500 weekly active\n teams\", \"median time-to-first-value < 5 min\"), and a coarse horizon bucket\n (`launch` / `short_term` / `long_term`). Do not force a quantified metric\n where the creator only has a qualitative one — a typed metric taxonomy is a\n later concern. A vision with no success criteria cannot be judged\n succeeded — the validator WARNs on it, so push for at least one.\n- **Constraints** (ref-addressable, `constraint-<slug>`). External limits the\n product must be built within, each classified by kind: `technical`,\n `business`, `compliance`, `resource`, `timeline`, or `other`. Capture the\n constraint statement and, where the creator gives it, the rationale (the\n source of the limit).\n - **Compliance constraints get explicit attention.** Ask whether the product\n handles regulated or personal data, operates in a regulated sector or has contractual\n assurance commitments. If so, record each as a\n `kind: compliance` constraint with a **prose** statement (\"Must be\n GDPR-compliant for EU customer personal data\"). Stop at prose — the deep\n per-regime obligation model (control catalogs, data-flow / residency\n matrices) is the compliance-posture step's job, not yours. Getting the\n compliance *seam* named here is what lets that later step engage.\n\n### The product's shape: workflow, users, boundary\n\nThree questions fix what the product IS, so that no later step decides it again: `core-workflow` (the\nstages a piece of work passes through), `user-groups` (who uses it, for what, on which device) and\n`scope-boundary` (what is explicitly left out). Two runs given the same answers must build the same\nproduct, and without these they did not: one built a customer-workflow CRM that left invoicing to\nother tools, the other built invoicing software with no customer follow-up at all.\n\nCarry them into the snapshot in the creator's own terms:\n\n- the workflow's stages, in order, in the idea's `description`;\n- the user groups, what each does, and their devices, in the problem's \"who is affected\" (and in the\n idea when the product's shape depends on them, such as work done in the field on a phone);\n- each scope boundary as a `constraint` of kind `business`, stated as an exclusion (\"Invoicing is out\n of scope: customers keep their accounting tool\"), with the creator's reason as its rationale.\n\nLater steps also receive these answers verbatim, so do not reword a stage or a boundary into\nsomething the creator did not say. An answer of \"nothing\" for the boundary records no constraint.\n\n## What you emit\n\nA single `VisionSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told\n otherwise).\n- `idea` — the required anchor (`oneLiner`, `description`, optional `notes`).\n- `problem` / `mission` — the optional singletons, present only if elicited.\n- `successCriteria[]` — each with a stable kebab-case `ref` prefixed\n `success-criterion-`, unique across the set.\n- `constraints[]` — each with a stable kebab-case `ref` prefixed `constraint-`,\n unique across the set, and a `kind`.\n\nAuthor every entity in English. Use stable, human-readable ref slugs\n(`success-criterion-weekly-active-teams`, `constraint-gdpr-eu-data`) — they are\naddressed by ref downstream, so a duplicate silently drops an entity.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `vision-snapshot-valid`\ngate (`validateVisionSnapshot`) before it commits. Duplicate refs and malformed\nrefs (a success-criterion or constraint ref that is not kebab-case with its\nrequired prefix) are hard **errors** — the gate rejects them. A missing problem,\na missing mission, and an empty success-criteria set are **warnings**: they\nreflect a not-yet-complete vision, they do not block, and the journey persists\nthe snapshot as partially-elicited. Emit clean refs the first time; let the\nwarnings stand honestly when the vision genuinely is not complete yet, rather\nthan inventing entities to silence them.\n\n## Approval\n\nThe drafted `VisionSnapshot` is presented to the creator for approval before it\nbecomes the committed `vision-brief`. Show the vision back in plain prose — the\none-liner, the problem, the mission, the criteria, the constraints — and let the\ncreator confirm or correct it. The vision is the seed every later step trusts;\nit is worth one explicit human sign-off.\n\n## Runtime context\n\nBefore you start, read the current journey state and scope so you elicit the\nvision for the right product, and read any vision that already exists so you\nrefine it rather than re-eliciting it from scratch.\n\n(When a prior vision exists it arrives in your brief as the `vision-brief` input section — refine\nthat content rather than re-eliciting it.)\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n",
|
|
22
22
|
"skillRefs": [],
|
|
23
23
|
"skillBodyRefs": [],
|
|
24
24
|
"elicitation": {
|
|
25
25
|
"questions": [
|
|
26
26
|
{
|
|
27
27
|
"ref": "application-line",
|
|
28
|
-
"question": "What kind of application is this? A B2B SaaS is a software product sold to other businesses. An internal tool is software a company builds for its own people.",
|
|
28
|
+
"question": "What kind of application is this? A B2B SaaS is a software product sold to other businesses. An internal tool is software a company builds for its own people. A service firm platform is how a firm serves its clients, their cases worked by the firm's agents and reviewed by its qualified people.",
|
|
29
29
|
"kind": "choice",
|
|
30
30
|
"options": [
|
|
31
31
|
"b2b_saas",
|
|
32
|
-
"internal_tool"
|
|
32
|
+
"internal_tool",
|
|
33
|
+
"service_firm"
|
|
33
34
|
],
|
|
34
35
|
"depth": "essential",
|
|
35
36
|
"whenUnknown": "ask"
|
|
@@ -99,7 +99,15 @@ export const AgentClientProtocol_ExecutionProfileSchema = z.object({
|
|
|
99
99
|
*
|
|
100
100
|
* The runner starts from a minimal identity allowlist and adds only what is
|
|
101
101
|
* named here. Full inheritance is never available: the process that spawns
|
|
102
|
-
* the agent holds platform secrets that must not reach it.
|
|
102
|
+
* the agent holds platform secrets that must not reach it. Naming one does
|
|
103
|
+
* not get past that: a variable the framework declares secret (a platform or
|
|
104
|
+
* application runtime secret, an inbound endpoint or system-of-record
|
|
105
|
+
* secret, or any provider's declared secret) is refused by `wildo config
|
|
106
|
+
* sync`, on every read and at startup, and at dispatch. A provider credential
|
|
107
|
+
* the agent needs is handed to it through `secretEnvVarName` instead. The
|
|
108
|
+
* refusal covers what the framework declares; a secret in the developer's
|
|
109
|
+
* own shell environment is not the framework's to know, so name only what
|
|
110
|
+
* the agent needs.
|
|
103
111
|
*/
|
|
104
112
|
inheritedEnvironmentVariables: z.array(z.string().min(1)).optional(),
|
|
105
113
|
authMode: z.enum(AgentClientProtocol_AuthMode),
|
|
@@ -129,7 +129,7 @@ export enum RequirementFamilyHalf {
|
|
|
129
129
|
/**
|
|
130
130
|
* A FACTORY rather than a shared constant, and the difference is visible on screen.
|
|
131
131
|
*
|
|
132
|
-
*
|
|
132
|
+
* The workbench's reading decorations are keyed by INSTANCE. When one instance served both the reading's
|
|
133
133
|
* `summary` and every row's `requirementRef`, the workbench gave the key its receding identifier
|
|
134
134
|
* treatment and so gave it to the summary as well: the one sentence the reading exists to say
|
|
135
135
|
* rendered as a slug with no field chrome (measured 2026-09-24). One instance per field keeps a
|
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
# backend.inbound-channels.attachment-adoption
|
|
2
|
+
|
|
3
|
+
## Import Origins
|
|
4
|
+
|
|
5
|
+
- `@wildo-ai/saas-backend-lib`
|
|
6
|
+
|
|
7
|
+
## Source Excerpts
|
|
8
|
+
|
|
9
|
+
### Origin Package: `@wildo-ai/saas-backend-lib`
|
|
10
|
+
|
|
11
|
+
```typescript
|
|
12
|
+
/** The record field a received attachment is adopted for: a `z_file` field of a resource the handler writes. */
|
|
13
|
+
export interface InboundAttachmentAdoptionTarget {
|
|
14
|
+
/** The resource the handler will create or update with the copy. Must be organization-scoped. */
|
|
15
|
+
readonly resourceType: ResourceType;
|
|
16
|
+
/** The `z_file` field on that resource, as declared (a dotted path for a nested one). */
|
|
17
|
+
readonly fieldName: string;
|
|
18
|
+
}
|
|
19
|
+
|
|
20
|
+
/** The copy an adoption made: name its `fileId` in the target field (`{ fileId }`, or among `{ fileIds }`). */
|
|
21
|
+
export interface InboundAdoptedAttachment {
|
|
22
|
+
readonly fileId: string;
|
|
23
|
+
/** The attachment it was copied from — still on the channel's own record. */
|
|
24
|
+
readonly sourceFileId: string;
|
|
25
|
+
readonly filename: string;
|
|
26
|
+
readonly contentType: string;
|
|
27
|
+
readonly sizeBytes: number;
|
|
28
|
+
}
|
|
29
|
+
|
|
30
|
+
/**
|
|
31
|
+
* How a channel handler puts one of its message's attachments on a record of its own (#2537).
|
|
32
|
+
*
|
|
33
|
+
* The channel keeps every clean attachment on its own record (the received email), with that record's retention, so
|
|
34
|
+
* the file cannot also be linked to yours: a file belongs to exactly one record. `adopt` COPIES it into a new file
|
|
35
|
+
* made for your `z_file` field, and you name the copy in your write. The email keeps its copy; erasing either one
|
|
36
|
+
* never touches the other, and each lives as long as its own record must.
|
|
37
|
+
*
|
|
38
|
+
* - **Only this message's attachments** — a `fileId` that is not in `message.attachments` is refused, so a handler
|
|
39
|
+
* cannot copy any other file it learns an id for.
|
|
40
|
+
* - **Only clean ones** — the copy takes the scanner's CLEAN verdict of the original; a withheld attachment is never
|
|
41
|
+
* in `message.attachments` at all.
|
|
42
|
+
* - **In the delivery's organization** — the copy belongs to it, and the target resource must be organization-scoped.
|
|
43
|
+
* - **Under the field's own rules** — its accepted types, size bounds and media constraints, exactly as an upload to
|
|
44
|
+
* that field is checked. A refusal throws a `VALIDATION` error (a delivery is not retried for it): catch it per
|
|
45
|
+
* attachment when one unsuitable file must not stop the others.
|
|
46
|
+
* - **Recorded** — every adoption writes `inbound_attachment_adopted` on the organization's audit trail.
|
|
47
|
+
*
|
|
48
|
+
* What the copy MAY do is decided by your write, not here: `ctx.resources.create/update` authorizes the write with
|
|
49
|
+
* the handler's roles as for any caller, and links the copy then. A copy your handler never names (the write failed,
|
|
50
|
+
* or a retry found the record already filed) is swept a day later like any upload nobody attached.
|
|
51
|
+
*/
|
|
52
|
+
export interface InboundAttachmentOperations {
|
|
53
|
+
adopt(fileId: string, target: InboundAttachmentAdoptionTarget): Promise<InboundAdoptedAttachment>;
|
|
54
|
+
}
|
|
55
|
+
```
|
|
@@ -49,7 +49,12 @@ export interface InboundMessageThread {
|
|
|
49
49
|
readonly isNew: boolean;
|
|
50
50
|
}
|
|
51
51
|
|
|
52
|
-
/**
|
|
52
|
+
/**
|
|
53
|
+
* An attachment the engine scanned and found clean. Its `fileId` names the file the CHANNEL keeps on its own record
|
|
54
|
+
* (the received email), and that file stays there: to put the attachment on one of your records, adopt it with
|
|
55
|
+
* `ctx.attachments.adopt(fileId, { resourceType, fieldName })` and name the copy it returns in that record's
|
|
56
|
+
* `z_file` field. Naming `fileId` itself in a write is refused: the file already belongs to the email.
|
|
57
|
+
*/
|
|
53
58
|
export interface InboundMessageAttachment {
|
|
54
59
|
readonly fileId: string;
|
|
55
60
|
readonly filename: string;
|
|
@@ -151,8 +156,12 @@ export interface InboundThreadOperations {
|
|
|
151
156
|
*
|
|
152
157
|
* Derived from the endpoint context rather than restated, so a channel handler can never hold a door an
|
|
153
158
|
* endpoint handler with the same roles does not.
|
|
159
|
+
*
|
|
160
|
+
* Except `chat` (#2664, S5a review F1): a channel message's sender is an address, and an email's From is verified by
|
|
161
|
+
* nothing, so no channel handler may act as a member. `ctx.chat` belongs to a chat vendor's endpoint, whose request
|
|
162
|
+
* names a person the vendor signed for.
|
|
154
163
|
*/
|
|
155
|
-
export type InboundChannelHandlerContextBase = Omit<InboundHandlerContext, 'delivery'> & {
|
|
164
|
+
export type InboundChannelHandlerContextBase = Omit<InboundHandlerContext, 'delivery' | 'chat'> & {
|
|
156
165
|
readonly delivery: {
|
|
157
166
|
readonly id: string;
|
|
158
167
|
readonly handlerRef: InboundHandlerRef;
|
|
@@ -161,6 +170,8 @@ export type InboundChannelHandlerContextBase = Omit<InboundHandlerContext, 'deli
|
|
|
161
170
|
readonly organizationId: string;
|
|
162
171
|
};
|
|
163
172
|
readonly thread: InboundThreadOperations;
|
|
173
|
+
/** This delivery's attachments, put on the handler's own records — see {@link InboundAttachmentOperations}. */
|
|
174
|
+
readonly attachments: InboundAttachmentOperations;
|
|
164
175
|
};
|
|
165
176
|
|
|
166
177
|
/**
|
|
@@ -13,8 +13,10 @@
|
|
|
13
13
|
* Starting an agent from an inbound delivery (#1611): `ctx.agents` on an inbound handler.
|
|
14
14
|
*
|
|
15
15
|
* The turn goes through the autonomous entry point, so it runs under the machine principal the delivery's
|
|
16
|
-
* ORGANIZATION granted to that agent
|
|
17
|
-
*
|
|
16
|
+
* ORGANIZATION granted to that agent, never under the handler's own roles, and a delivery replayed or retried starts
|
|
17
|
+
* nothing twice (the delivery id is the occurrence). A delivery names no party, so the agent must run for exactly ONE
|
|
18
|
+
* party there: the organization's own bound client, or one relationship's admitted client. Where several run it (#2615),
|
|
19
|
+
* the turn is refused `ambiguous_principal` rather than given to one of them.
|
|
18
20
|
*
|
|
19
21
|
* The delivery's content is DATA. Pass what the agent needs as `input`: it reaches the agent after the
|
|
20
22
|
* agent's declared instruction, fenced as data, and the turn is offered only tools that READ or that a
|
|
@@ -38,7 +40,12 @@ export interface InboundHandlerAgents {
|
|
|
38
40
|
readonly autonomousAgentRef: string;
|
|
39
41
|
/** The facts of this delivery the agent needs, as data. Serialized as JSON. */
|
|
40
42
|
readonly input?: Readonly<Record<string, unknown>>;
|
|
41
|
-
/**
|
|
43
|
+
/**
|
|
44
|
+
* The case the turn works on, when the delivery belongs to one. Must be readable by the agent's principal, or the
|
|
45
|
+
* turn is refused (`case_not_readable`). Naming a case also moves the turn onto that CASE's concurrency slot (#2540):
|
|
46
|
+
* a `SKIP_IF_ACTIVE` agent skips only while a turn on the same case is active, so two deliveries about two cases run
|
|
47
|
+
* side by side, and one with no case keeps its party's slot for the organization.
|
|
48
|
+
*/
|
|
42
49
|
readonly caseRef?: WorkUnitRef;
|
|
43
50
|
}): Promise<AutonomousTurnStartOutcome>;
|
|
44
51
|
}
|