@wildo-ai/framework-knowledge 1.1.0
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/LICENSE +34 -0
- package/dist/esm/.builder.pid +9 -0
- package/dist/esm/framework-knowledge.definitions.d.ts +51 -0
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -0
- package/dist/esm/framework-knowledge.definitions.js +1571 -0
- package/dist/esm/framework-knowledge.definitions.js.map +1 -0
- package/dist/esm/framework-knowledge.loader.d.ts +72 -0
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -0
- package/dist/esm/framework-knowledge.loader.js +258 -0
- package/dist/esm/framework-knowledge.loader.js.map +1 -0
- package/dist/esm/framework-knowledge.schemas.d.ts +236 -0
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -0
- package/dist/esm/framework-knowledge.schemas.js +23 -0
- package/dist/esm/framework-knowledge.schemas.js.map +1 -0
- package/dist/esm/index.d.ts +4 -0
- package/dist/esm/index.d.ts.map +1 -0
- package/dist/esm/index.js +4 -0
- package/dist/esm/index.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +53 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +56 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +200 -0
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +228 -0
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +39 -0
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +39 -0
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +261 -0
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +412 -0
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +61 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +65 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +53 -0
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +54 -0
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +43 -0
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +73 -0
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +53 -0
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +114 -0
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +95 -0
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +102 -0
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +258 -0
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +241 -0
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +241 -0
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +202 -0
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +82 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +89 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +56 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +76 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +30 -0
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +27 -0
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +31 -0
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +26 -0
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +254 -0
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +219 -0
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +180 -0
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +302 -0
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +249 -0
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +286 -0
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +248 -0
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +227 -0
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +45 -0
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +48 -0
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +250 -0
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +218 -0
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -0
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -0
- package/dist/knowledge/manifest.json +45 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +407 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +69 -0
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +556 -0
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +47 -0
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +344 -0
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +43 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +259 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +83 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/structured-artifact-action.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +321 -0
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +79 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +185 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +66 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +737 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +44 -0
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +261 -0
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +57 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +151 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +124 -0
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.business-model/method.md +128 -0
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +102 -0
- package/dist/knowledge/playbooks/top_down.business-model/structured-artifact-action.json +1 -0
- package/dist/knowledge/playbooks/top_down.capability-map/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.capability-map/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +239 -0
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +73 -0
- package/dist/knowledge/playbooks/top_down.capability-map/structured-artifact-action.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +177 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +95 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/method.md +64 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +49 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +40 -0
- package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +42 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +239 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +69 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/structured-artifact-action.json +1 -0
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +96 -0
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +77 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +53 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +61 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/structured-artifact-action.json +1 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +280 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +87 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/structured-artifact-action.json +1 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +204 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +54 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +146 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +120 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/structured-artifact-action.json +1 -0
- package/dist/knowledge/references/application.database.migration-change-risk.md +28 -0
- package/dist/knowledge/references/assertions.authored-metadata.config.md +90 -0
- package/dist/knowledge/references/assertions.behaviors.wire-contracts.md +223 -0
- package/dist/knowledge/references/assertions.references.conventions.md +92 -0
- package/dist/knowledge/references/assertions.snapshot.validation.md +317 -0
- package/dist/knowledge/references/assertions.specification.config.md +287 -0
- package/dist/knowledge/references/brand.asset.config.md +167 -0
- package/dist/knowledge/references/brand.authored-metadata.config.md +51 -0
- package/dist/knowledge/references/brand.logo-direction.config.md +88 -0
- package/dist/knowledge/references/brand.name.config.md +46 -0
- package/dist/knowledge/references/brand.snapshot.config.md +76 -0
- package/dist/knowledge/references/brand.snapshot.validation.md +446 -0
- package/dist/knowledge/references/brand.visual-tone.config.md +56 -0
- package/dist/knowledge/references/build-plan.task-graph.config.md +198 -0
- package/dist/knowledge/references/business-model.authored-metadata.config.md +65 -0
- package/dist/knowledge/references/business-model.pricing-plan.config.md +122 -0
- package/dist/knowledge/references/business-model.references.conventions.md +99 -0
- package/dist/knowledge/references/business-model.snapshot.config.md +121 -0
- package/dist/knowledge/references/business-model.snapshot.validation.md +325 -0
- package/dist/knowledge/references/cli.market.generate-command.md +230 -0
- package/dist/knowledge/references/cli.market.utils.md +147 -0
- package/dist/knowledge/references/companion.introspection.behaviors.market.md +90 -0
- package/dist/knowledge/references/companion.introspection.handlers.market.md +42 -0
- package/dist/knowledge/references/companion.market.generation-service.md +270 -0
- package/dist/knowledge/references/companion.market.prompt-renderer.md +244 -0
- package/dist/knowledge/references/companion.technical-doc.service.md +809 -0
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +125 -0
- package/dist/knowledge/references/engine.client-bundle.discipline.md +130 -0
- package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +55 -0
- package/dist/knowledge/references/engine.saas-technical-doc.config.md +215 -0
- package/dist/knowledge/references/engine.saas-website.config.md +331 -0
- package/dist/knowledge/references/example.authorization.unit-narrowing.declaration.md +24 -0
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +55 -0
- package/dist/knowledge/references/example.backend.custom-operation.create-postfix.md +35 -0
- package/dist/knowledge/references/example.backend.operation.error-throw.md +17 -0
- package/dist/knowledge/references/example.config.app-shell.command-menu-items.md +63 -0
- package/dist/knowledge/references/example.config.app-shell.full.md +147 -0
- package/dist/knowledge/references/example.config.app-shell.hosted-components.md +45 -0
- package/dist/knowledge/references/example.config.app-shell.quick-switcher-fields.md +37 -0
- package/dist/knowledge/references/example.config.backend.billing-enable.md +20 -0
- package/dist/knowledge/references/example.config.backend.required-floors.md +46 -0
- package/dist/knowledge/references/example.config.design-system.full.md +162 -0
- package/dist/knowledge/references/example.config.navigation.full.md +71 -0
- package/dist/knowledge/references/example.config.provider.backend-scope-billing.md +27 -0
- package/dist/knowledge/references/example.data-seeding.minimal.md +114 -0
- package/dist/knowledge/references/example.email.template.minimal.md +54 -0
- package/dist/knowledge/references/example.engine.component-registration.lazy-load.md +16 -0
- package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +146 -0
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +196 -0
- package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +174 -0
- package/dist/knowledge/references/example.i18n.label-generation.engine-barrel.md +15 -0
- package/dist/knowledge/references/example.infra.cdn.cloudflare.md +23 -0
- package/dist/knowledge/references/example.infra.cdn.generic.md +17 -0
- package/dist/knowledge/references/example.infra.environment-config.local.md +250 -0
- package/dist/knowledge/references/example.market.alternative.in-house-build.md +49 -0
- package/dist/knowledge/references/example.market.authored-metadata.md +32 -0
- package/dist/knowledge/references/example.market.buying-journey.core-icp.md +140 -0
- package/dist/knowledge/references/example.market.category.config.md +71 -0
- package/dist/knowledge/references/example.market.channel.community.md +39 -0
- package/dist/knowledge/references/example.market.feature-benefit.kano-threshold.md +67 -0
- package/dist/knowledge/references/example.market.feature-benefit.pain-reliever.md +65 -0
- package/dist/knowledge/references/example.market.icp.anti-target.md +47 -0
- package/dist/knowledge/references/example.market.icp.individual.md +82 -0
- package/dist/knowledge/references/example.market.icp.legal-entity-with-geographies.md +95 -0
- package/dist/knowledge/references/example.market.is-benefit-available.composition.md +40 -0
- package/dist/knowledge/references/example.market.job.emotional.md +27 -0
- package/dist/knowledge/references/example.market.job.functional.md +28 -0
- package/dist/knowledge/references/example.market.message-template.seeds.md +106 -0
- package/dist/knowledge/references/example.market.objection.pricing.md +39 -0
- package/dist/knowledge/references/example.market.persona.dmu-with-inheritance.md +62 -0
- package/dist/knowledge/references/example.market.persona.individual-self.md +51 -0
- package/dist/knowledge/references/example.market.positioning.per-icp.md +103 -0
- package/dist/knowledge/references/example.market.proof.metric.md +39 -0
- package/dist/knowledge/references/example.market.scoring.golden-case.md +46 -0
- package/dist/knowledge/references/example.market.scoring.no-coverage-zero.md +40 -0
- package/dist/knowledge/references/example.market.snapshot-validation.duplicate-journey-stage.md +36 -0
- package/dist/knowledge/references/example.market.snapshot-validation.errors-by-kind.md +55 -0
- package/dist/knowledge/references/example.market.snapshot-validation.objection-proof-benefit-mismatch.md +74 -0
- package/dist/knowledge/references/example.market.snapshot-validation.proof-without-support.md +32 -0
- package/dist/knowledge/references/example.market.snapshot-validation.threshold-without-job.md +44 -0
- package/dist/knowledge/references/example.market.snapshot.assembled.md +49 -0
- package/dist/knowledge/references/example.market.tone-of-voice.config.md +41 -0
- package/dist/knowledge/references/example.market.trigger.growth-milestone.md +43 -0
- package/dist/knowledge/references/example.module.companion-exports.full.md +142 -0
- package/dist/knowledge/references/example.module.registration.shared.md +16 -0
- package/dist/knowledge/references/example.module.relationships.actor-edge-back-to-scope-owner.md +47 -0
- package/dist/knowledge/references/example.module.relationships.discriminator.md +25 -0
- package/dist/knowledge/references/example.module.relationships.scope-membership-junction.md +25 -0
- package/dist/knowledge/references/example.provider.backend-module-shape.md +110 -0
- package/dist/knowledge/references/example.provider.contribution.backend-billing.md +12 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +30 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +21 -0
- package/dist/knowledge/references/example.rag.source-fields.declaration.md +83 -0
- package/dist/knowledge/references/example.rate-limit.custom-controller-surface.md +25 -0
- package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +24 -0
- package/dist/knowledge/references/example.resource.add-field.priority-enum.md +19 -0
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +21 -0
- package/dist/knowledge/references/example.resource.config-wiring.fk-relationship.md +33 -0
- package/dist/knowledge/references/example.resource.custom-view.read-host.md +28 -0
- package/dist/knowledge/references/example.resource.mcp-exposure.md +65 -0
- package/dist/knowledge/references/example.resource.reference-constraints.role-constrained.md +27 -0
- package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +22 -0
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +43 -0
- package/dist/knowledge/references/example.spec.composite-view.workspace.md +72 -0
- package/dist/knowledge/references/example.spec.feature.flag-with-codehandling.md +64 -0
- package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +88 -0
- package/dist/knowledge/references/example.spec.resource.semantic-field.md +23 -0
- package/dist/knowledge/references/example.views.app-level.composite-views-config.md +19 -0
- package/dist/knowledge/references/example.views.chart-view.resource-owned.md +69 -0
- package/dist/knowledge/references/example.views.composite-view.host-embeds.md +31 -0
- package/dist/knowledge/references/example.views.composite-view.workspace.md +65 -0
- package/dist/knowledge/references/example.views.custom-view.execution-host.md +41 -0
- package/dist/knowledge/references/example.views.execution-view.resource-owned.md +25 -0
- package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +42 -0
- package/dist/knowledge/references/market.alternative.config.md +68 -0
- package/dist/knowledge/references/market.alternative.kind.md +32 -0
- package/dist/knowledge/references/market.authored-metadata.config.md +64 -0
- package/dist/knowledge/references/market.buying-journey.config.md +43 -0
- package/dist/knowledge/references/market.buying-journey.stage.md +33 -0
- package/dist/knowledge/references/market.category.config.md +63 -0
- package/dist/knowledge/references/market.channel.config.md +59 -0
- package/dist/knowledge/references/market.channel.kind.md +49 -0
- package/dist/knowledge/references/market.context-block.builder.md +544 -0
- package/dist/knowledge/references/market.context-block.response.md +57 -0
- package/dist/knowledge/references/market.feature-benefit.config.md +84 -0
- package/dist/knowledge/references/market.feature-benefit.kano.md +41 -0
- package/dist/knowledge/references/market.gain.config.md +50 -0
- package/dist/knowledge/references/market.generation.response.md +108 -0
- package/dist/knowledge/references/market.icp.config.md +162 -0
- package/dist/knowledge/references/market.icp.geographic-targeting.md +57 -0
- package/dist/knowledge/references/market.inherit-from.md +74 -0
- package/dist/knowledge/references/market.is-benefit-available.md +58 -0
- package/dist/knowledge/references/market.job.config.md +48 -0
- package/dist/knowledge/references/market.message-template.config.md +86 -0
- package/dist/knowledge/references/market.objection.config.md +56 -0
- package/dist/knowledge/references/market.objection.kind.md +34 -0
- package/dist/knowledge/references/market.pain.config.md +50 -0
- package/dist/knowledge/references/market.persona.config.md +64 -0
- package/dist/knowledge/references/market.positioning.config.md +84 -0
- package/dist/knowledge/references/market.proof.config.md +48 -0
- package/dist/knowledge/references/market.proof.kind.md +34 -0
- package/dist/knowledge/references/market.references.weighted-edges.md +105 -0
- package/dist/knowledge/references/market.scoring.fit.md +215 -0
- package/dist/knowledge/references/market.snapshot.config.md +34 -0
- package/dist/knowledge/references/market.snapshot.validation.md +1171 -0
- package/dist/knowledge/references/market.tone-of-voice.config.md +80 -0
- package/dist/knowledge/references/market.trigger.config.md +45 -0
- package/dist/knowledge/references/market.trigger.kind.md +35 -0
- package/dist/knowledge/references/placement-plan.config.md +330 -0
- package/dist/knowledge/references/platform.config.application-database.md +74 -0
- package/dist/knowledge/references/platform.config.application-modules.md +30 -0
- package/dist/knowledge/references/platform.config.backing-services.md +266 -0
- package/dist/knowledge/references/platform.config.cdn.md +167 -0
- package/dist/knowledge/references/platform.config.environment.deployment.md +263 -0
- package/dist/knowledge/references/platform.config.saas.md +405 -0
- package/dist/knowledge/references/presets.models.design-system.configuration.md +59 -0
- package/dist/knowledge/references/presets.models.design-system.source-config.md +72 -0
- package/dist/knowledge/references/presets.models.labelling.sections.md +64 -0
- package/dist/knowledge/references/presets.models.material.profile-contract.md +192 -0
- package/dist/knowledge/references/presets.models.material.runtime-policy.md +60 -0
- package/dist/knowledge/references/presets.models.surface-policy.defaults.md +613 -0
- package/dist/knowledge/references/presets.models.surface-policy.md +534 -0
- package/dist/knowledge/references/presets.models.surface-variant.md +56 -0
- package/dist/knowledge/references/requirements.authored-metadata.config.md +64 -0
- package/dist/knowledge/references/requirements.functional-requirement.config.md +68 -0
- package/dist/knowledge/references/requirements.non-functional-requirement.config.md +100 -0
- package/dist/knowledge/references/requirements.references.conventions.md +125 -0
- package/dist/knowledge/references/requirements.snapshot.config.md +73 -0
- package/dist/knowledge/references/requirements.snapshot.validation.md +333 -0
- package/dist/knowledge/references/roadmap.authored-metadata.config.md +64 -0
- package/dist/knowledge/references/roadmap.phase.config.md +149 -0
- package/dist/knowledge/references/roadmap.references.conventions.md +89 -0
- package/dist/knowledge/references/roadmap.snapshot.config.md +65 -0
- package/dist/knowledge/references/roadmap.snapshot.validation.md +325 -0
- package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +32 -0
- package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +38 -0
- package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +45 -0
- package/dist/knowledge/references/saas.backend.custom-operation.authoritative-fields.md +53 -0
- package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +120 -0
- package/dist/knowledge/references/saas.backend.domain-module.md +237 -0
- package/dist/knowledge/references/saas.backend.email-template.definition.md +69 -0
- package/dist/knowledge/references/saas.backend.flows-actors.a2a-agent-card.md +89 -0
- package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +118 -0
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +82 -0
- package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +48 -0
- package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +39 -0
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +67 -0
- package/dist/knowledge/references/saas.backend.pdf-template.bindings.md +52 -0
- package/dist/knowledge/references/saas.backend.pdf-template.definition.md +113 -0
- package/dist/knowledge/references/saas.backend.rate-limit-service.check-policy.md +75 -0
- package/dist/knowledge/references/saas.backend.system-access-service.md +994 -0
- package/dist/knowledge/references/saas.data-seeding.admin-endpoints.md +59 -0
- package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +184 -0
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +95 -0
- package/dist/knowledge/references/saas.data-seeding.modes.md +72 -0
- package/dist/knowledge/references/saas.data-seeding.run-ledger.md +198 -0
- package/dist/knowledge/references/saas.data-seeding.run-status.md +35 -0
- package/dist/knowledge/references/saas.data-seeding.schedule.md +91 -0
- package/dist/knowledge/references/saas.data-seeding.scope-iteration-strategy.md +46 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +55 -0
- package/dist/knowledge/references/saas.external-providers.document-extraction.applicability.md +26 -0
- package/dist/knowledge/references/saas.external-providers.embeddings.applicability.md +30 -0
- package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +124 -0
- package/dist/knowledge/references/saas.external-providers.llm.operation-key.md +49 -0
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +265 -0
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +148 -0
- package/dist/knowledge/references/saas.frontend.app-shell.hosted-components.md +145 -0
- package/dist/knowledge/references/saas.frontend.chart-view.inserted-declaration.md +80 -0
- package/dist/knowledge/references/saas.frontend.command-menu.omnibox.md +88 -0
- package/dist/knowledge/references/saas.frontend.command-menu.search-resource.md +109 -0
- package/dist/knowledge/references/saas.frontend.component-registration.entry.md +21 -0
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +102 -0
- package/dist/knowledge/references/saas.frontend.composite-view.define-helper.md +31 -0
- package/dist/knowledge/references/saas.frontend.domain-module.md +31 -0
- package/dist/knowledge/references/saas.frontend.embedded-resource-descent.md +37 -0
- package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.md +172 -0
- package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +115 -0
- package/dist/knowledge/references/saas.frontend.execution-view.definition.md +172 -0
- package/dist/knowledge/references/saas.frontend.execution-view.dirty-bridge-contract.local-pane.md +109 -0
- package/dist/knowledge/references/saas.frontend.execution-view.dirty-bridge-contract.md +55 -0
- package/dist/knowledge/references/saas.frontend.execution-view.dirty-state-contract.md +151 -0
- package/dist/knowledge/references/saas.frontend.execution-view.failure-handling-contract.md +302 -0
- package/dist/knowledge/references/saas.frontend.execution-view.loading-aggregation.md +89 -0
- package/dist/knowledge/references/saas.frontend.execution-view.loading-aggregation.participation-prefetch.md +231 -0
- package/dist/knowledge/references/saas.frontend.execution-view.loading-aggregation.participation-prefetch.shell-data-hydrator.md +174 -0
- package/dist/knowledge/references/saas.frontend.execution-view.navigation-handling-and-embedding.md +96 -0
- package/dist/knowledge/references/saas.frontend.execution-view.navigation-handling-and-embedding.resolution.md +45 -0
- package/dist/knowledge/references/saas.frontend.execution-view.outcome-emission-contract.md +71 -0
- package/dist/knowledge/references/saas.frontend.execution-view.participation-and-anchor.md +80 -0
- package/dist/knowledge/references/saas.frontend.execution-view.three-zone-contract.md +147 -0
- package/dist/knowledge/references/saas.frontend.flows-actors-view.md +40 -0
- package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +80 -0
- package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +64 -0
- package/dist/knowledge/references/saas.frontend.inserted-view.identity-bindings-descriptor.md +149 -0
- package/dist/knowledge/references/saas.frontend.operation-key-and-resource-config-like.md +63 -0
- package/dist/knowledge/references/saas.frontend.quick-switcher.scope-field.md +102 -0
- package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +86 -0
- package/dist/knowledge/references/saas.frontend.related-resource-preview.md +23 -0
- package/dist/knowledge/references/saas.frontend.related-resource-sections.md +28 -0
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +43 -0
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +215 -0
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +531 -0
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +210 -0
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-preset-map.md +39 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +58 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +118 -0
- package/dist/knowledge/references/saas.frontend.view-definition-scope.md +42 -0
- package/dist/knowledge/references/saas.market.generation-agent.md +104 -0
- package/dist/knowledge/references/saas.models.core-resource-operation.md +86 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +395 -0
- package/dist/knowledge/references/saas.models.engine-capabilities.md +114 -0
- package/dist/knowledge/references/saas.models.error-type.md +45 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +162 -0
- package/dist/knowledge/references/saas.models.feature-limit-semantic.md +51 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-configuration.md +127 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +115 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-invocation.md +52 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-prompt-spec.md +188 -0
- package/dist/knowledge/references/saas.models.http-api-binding.md +237 -0
- package/dist/knowledge/references/saas.models.navigation.layout.md +149 -0
- package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +22 -0
- package/dist/knowledge/references/saas.models.organization-unit-narrowing-declaration.md +42 -0
- package/dist/knowledge/references/saas.models.polymorphism.optout-business-key.md +62 -0
- package/dist/knowledge/references/saas.models.polymorphism.variant-definition.md +74 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +97 -0
- package/dist/knowledge/references/saas.models.rate-limit-configuration.md +67 -0
- package/dist/knowledge/references/saas.models.relationship-handling-contract.md +30 -0
- package/dist/knowledge/references/saas.models.relationship-handling-settings.md +62 -0
- package/dist/knowledge/references/saas.models.relationship-nature-and-models.md +112 -0
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +431 -0
- package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +88 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +89 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-base.md +79 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +49 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-path.md +27 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-union.md +26 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +62 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +124 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-relationships-buckets.md +38 -0
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +69 -0
- package/dist/knowledge/references/saas.models.resource-config.searchable-relation.md +89 -0
- package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +121 -0
- package/dist/knowledge/references/saas.models.resource-config.token-generation.md +145 -0
- package/dist/knowledge/references/saas.models.resource-field-identifier.md +25 -0
- package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +77 -0
- package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +58 -0
- package/dist/knowledge/references/saas.models.resource-primary-scope.md +36 -0
- package/dist/knowledge/references/saas.models.resource-relationship-access-scope.md +26 -0
- package/dist/knowledge/references/saas.models.resource-relationship-builder-parameters.md +100 -0
- package/dist/knowledge/references/saas.models.resource-relationship-cardinality.md +57 -0
- package/dist/knowledge/references/saas.models.resource-relationship-declaration.md +69 -0
- package/dist/knowledge/references/saas.models.resource-relationship-resolved-semantics.md +60 -0
- package/dist/knowledge/references/saas.models.resource-relationship-schema.md +172 -0
- package/dist/knowledge/references/saas.models.resource-server-instance.md +109 -0
- package/dist/knowledge/references/saas.models.resource-type.md +24 -0
- package/dist/knowledge/references/saas.models.schema-family-builder.md +242 -0
- package/dist/knowledge/references/saas.models.scope-membership.md +143 -0
- package/dist/knowledge/references/saas.models.shared-domain-module.md +36 -0
- package/dist/knowledge/references/saas.models.shared-saas-module.md +36 -0
- package/dist/knowledge/references/saas.public-runtime.contract.md +229 -0
- package/dist/knowledge/references/saas.rag.retrieval-bounds.md +106 -0
- package/dist/knowledge/references/saas.rag.retrieval-refusals.md +89 -0
- package/dist/knowledge/references/saas.rag.retrieval-request.md +130 -0
- package/dist/knowledge/references/saas.rag.retrieval-result.md +147 -0
- package/dist/knowledge/references/saas.rag.retrieval-scores.md +54 -0
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +59 -0
- package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +74 -0
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +1158 -0
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +2602 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +180 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.discriminated-union.md +138 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-aggregate-offer.md +46 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-aggregate-rating.md +47 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-article.md +49 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-blog-posting.md +62 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-breadcrumb-list.md +46 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-faq-page.md +51 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-offer.md +46 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-organization.md +48 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-product.md +59 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-review.md +46 -0
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-website.md +46 -0
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +530 -0
- package/dist/knowledge/references/saas.specifications.composite-view-specification.md +49 -0
- package/dist/knowledge/references/saas.specifications.error-message-specification.md +92 -0
- package/dist/knowledge/references/saas.specifications.family-specifications.md +109 -0
- package/dist/knowledge/references/saas.specifications.feature-specification.md +93 -0
- package/dist/knowledge/references/saas.specifications.frontend-component-spec-factory.md +113 -0
- package/dist/knowledge/references/saas.specifications.frontend-component-spec-model.md +366 -0
- package/dist/knowledge/references/saas.specifications.resource-frontend-configuration-aspect.md +41 -0
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +1978 -0
- package/dist/knowledge/references/saas.specifications.resource-pdf-template-spec.md +58 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-code-handling.md +49 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +156 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +171 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-frontend-config-type.md +54 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-frontend-prose.md +171 -0
- package/dist/knowledge/references/saas.website.astro.bridge.md +262 -0
- package/dist/knowledge/references/saas.website.astro.head-renderer.md +271 -0
- package/dist/knowledge/references/saas.website.astro.headers-renderer.md +41 -0
- package/dist/knowledge/references/saas.website.astro.i18n-helper.md +121 -0
- package/dist/knowledge/references/saas.website.astro.label-key-collector.md +117 -0
- package/dist/knowledge/references/saas.website.astro.label-loader.md +377 -0
- package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +46 -0
- package/dist/knowledge/references/saas.website.astro.pick-labels-for-page.md +90 -0
- package/dist/knowledge/references/saas.website.astro.robots-renderer.md +174 -0
- package/dist/knowledge/references/saas.website.astro.runtime-helper.md +187 -0
- package/dist/knowledge/references/saas.website.astro.site-context.md +141 -0
- package/dist/knowledge/references/saas.website.astro.sitemap-coverage.md +188 -0
- package/dist/knowledge/references/saas.website.astro.structured-data-renderer.md +174 -0
- package/dist/knowledge/references/saas.website.blog.bridge.md +396 -0
- package/dist/knowledge/references/saas.website.blog.collection-config.md +180 -0
- package/dist/knowledge/references/saas.website.blog.frontmatter.md +116 -0
- package/dist/knowledge/references/saas.website.blog.head-renderer.md +292 -0
- package/dist/knowledge/references/saas.website.blog.mdx-provider.md +100 -0
- package/dist/knowledge/references/saas.website.blog.post-renderer.md +291 -0
- package/dist/knowledge/references/saas.website.design-tokens.bundle.md +29 -0
- package/dist/knowledge/references/saas.website.design-tokens.colors.md +64 -0
- package/dist/knowledge/references/saas.website.design-tokens.radius.md +38 -0
- package/dist/knowledge/references/saas.website.factories.define-page-manifest.md +98 -0
- package/dist/knowledge/references/saas.website.factories.define-section.md +128 -0
- package/dist/knowledge/references/saas.website.label-keys.compose-helper.md +36 -0
- package/dist/knowledge/references/saas.website.label-keys.format.md +67 -0
- package/dist/knowledge/references/saas.website.label-pack.validator.md +206 -0
- package/dist/knowledge/references/saas.website.page-layout.component.md +217 -0
- package/dist/knowledge/references/saas.website.page-manifest.meta-label-keys.md +47 -0
- package/dist/knowledge/references/saas.website.page-manifest.route-path.md +49 -0
- package/dist/knowledge/references/saas.website.page-manifest.schema.md +186 -0
- package/dist/knowledge/references/saas.website.page-manifest.seo.md +46 -0
- package/dist/knowledge/references/saas.website.page.context.md +57 -0
- package/dist/knowledge/references/saas.website.primitives.button.md +123 -0
- package/dist/knowledge/references/saas.website.primitives.heading.md +103 -0
- package/dist/knowledge/references/saas.website.primitives.image.md +103 -0
- package/dist/knowledge/references/saas.website.primitives.internal-button.md +151 -0
- package/dist/knowledge/references/saas.website.primitives.internal-link.md +193 -0
- package/dist/knowledge/references/saas.website.primitives.link.md +78 -0
- package/dist/knowledge/references/saas.website.primitives.text.md +82 -0
- package/dist/knowledge/references/saas.website.refs.page.md +56 -0
- package/dist/knowledge/references/saas.website.refs.section.md +57 -0
- package/dist/knowledge/references/saas.website.root-config.navigation.md +37 -0
- package/dist/knowledge/references/saas.website.root-config.schema.md +192 -0
- package/dist/knowledge/references/saas.website.root-config.seo.md +98 -0
- package/dist/knowledge/references/saas.website.routing.localized-path.md +84 -0
- package/dist/knowledge/references/saas.website.runtime.context.md +174 -0
- package/dist/knowledge/references/saas.website.section.component.md +138 -0
- package/dist/knowledge/references/saas.website.section.context.md +63 -0
- package/dist/knowledge/references/saas.website.sections.category-enum.md +72 -0
- package/dist/knowledge/references/saas.website.sections.definition-schema.md +121 -0
- package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +37 -0
- package/dist/knowledge/references/saas.website.seo.robots-config.md +106 -0
- package/dist/knowledge/references/saas.website.seo.sitemap-config.md +73 -0
- package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +71 -0
- package/dist/knowledge/references/saas.website.use-label-by-key.hook.md +45 -0
- package/dist/knowledge/references/saas.website.use-label.hook.md +82 -0
- package/dist/knowledge/references/saas.website.use-page.hook.md +30 -0
- package/dist/knowledge/references/saas.website.use-runtime.hook.md +36 -0
- package/dist/knowledge/references/saas.website.use-section.hook.md +30 -0
- package/dist/knowledge/references/saas.website.use-tokens.hook.md +32 -0
- package/dist/knowledge/references/vision.authored-metadata.config.md +64 -0
- package/dist/knowledge/references/vision.constraint.config.md +66 -0
- package/dist/knowledge/references/vision.idea.config.md +45 -0
- package/dist/knowledge/references/vision.mission.config.md +46 -0
- package/dist/knowledge/references/vision.problem.config.md +51 -0
- package/dist/knowledge/references/vision.references.conventions.md +115 -0
- package/dist/knowledge/references/vision.snapshot.config.md +85 -0
- package/dist/knowledge/references/vision.snapshot.validation.md +226 -0
- package/dist/knowledge/references/vision.success-criterion.config.md +60 -0
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +550 -0
- package/dist/knowledge/references/zod.decorators.conditional-visibility.md +104 -0
- package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +436 -0
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +174 -0
- package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +101 -0
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +317 -0
- package/dist/knowledge/references/zod.decorators.file-generation.md +36 -0
- package/dist/knowledge/references/zod.decorators.file-rag-source.md +56 -0
- package/dist/knowledge/references/zod.decorators.file-schema.md +319 -0
- package/dist/knowledge/references/zod.decorators.foreign-key-display-mode.md +83 -0
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +459 -0
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +123 -0
- package/dist/knowledge/references/zod.decorators.rag-source.md +164 -0
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +122 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +152 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +314 -0
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +529 -0
- package/dist/knowledge/references/zod.factories.bigdecimal.md +155 -0
- package/dist/knowledge/references/zod.factories.code.md +127 -0
- package/dist/knowledge/references/zod.factories.duration.md +246 -0
- package/dist/knowledge/references/zod.factories.money.md +166 -0
- package/dist/knowledge/references/zod.factories.phone.md +88 -0
- package/dist/knowledge/references/zod.factories.range.md +174 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +15 -0
- package/dist/knowledge/registries/framework-topics.json +5212 -0
- package/dist/knowledge/registries/playbooks.json +488 -0
- package/dist/knowledge/registries/source-tags.json +7664 -0
- package/dist/knowledge/rules/resource-schema-awareness.md +77 -0
- package/dist/knowledge/skills/INDEX.md +349 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +415 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/examples/domain-use-case-and-admin-task.example.md +49 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +52 -0
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +218 -0
- package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +84 -0
- package/dist/knowledge/skills/application-database-migrations/references/framework-migration-change-risk-api.md +37 -0
- package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +64 -0
- package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +34 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +323 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +84 -0
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +324 -0
- package/dist/knowledge/skills/backend-addon-wiring/references/backend-di-routing.md +7 -0
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +276 -0
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +374 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-error-handling-api.md +118 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +107 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +134 -0
- package/dist/knowledge/skills/backend-custom-operation/references/operation-file-conventions.md +10 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +192 -0
- package/dist/knowledge/skills/brand-logo-authoring/references/brand-authoring-decisions.md +55 -0
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +184 -0
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +279 -0
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +346 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +160 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +518 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +158 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +95 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +100 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +1210 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +40 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +698 -0
- package/dist/knowledge/skills/config-app-shell/references/app-shell-surfaces.md +5 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +415 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-hosted-components-api.md +170 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-command-menu-omnibox-api.md +212 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-quick-switcher-scope-field-api.md +178 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +424 -0
- package/dist/knowledge/skills/config-design-system/references/design-system-file.md +10 -0
- package/dist/knowledge/skills/config-design-system/references/framework-design-system-configuration-api.md +77 -0
- package/dist/knowledge/skills/config-design-system/references/framework-material-profile-api.md +200 -0
- package/dist/knowledge/skills/config-design-system/references/framework-material-runtime-policy-api.md +68 -0
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +1212 -0
- package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +92 -0
- package/dist/knowledge/skills/config-navigation/SKILL.md +249 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +152 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-zones.md +5 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +209 -0
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +221 -0
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +408 -0
- package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +183 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +40 -0
- package/dist/knowledge/skills/configure-billing/SKILL.md +261 -0
- package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +90 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +122 -0
- package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +48 -0
- package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +69 -0
- package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +57 -0
- package/dist/knowledge/skills/email-add-template/SKILL.md +439 -0
- package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +9 -0
- package/dist/knowledge/skills/email-add-template/references/framework-email-template-api.md +72 -0
- package/dist/knowledge/skills/email-definition-wiring/SKILL.md +62 -0
- package/dist/knowledge/skills/email-labels-authoring/SKILL.md +64 -0
- package/dist/knowledge/skills/email-template-authoring/SKILL.md +62 -0
- package/dist/knowledge/skills/engine-component-registration/SKILL.md +257 -0
- package/dist/knowledge/skills/engine-component-registration/references/component-registration-file.md +7 -0
- package/dist/knowledge/skills/engine-component-registration/references/framework-component-registration-api.md +24 -0
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +429 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +287 -0
- package/dist/knowledge/skills/engine-product-definitions/references/product-registry-scope.md +5 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +491 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +227 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-named-a2a-agents-contract.md +143 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +368 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +226 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +208 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +286 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +376 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +262 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +130 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-prompt-spec-api.md +214 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +195 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/operation-key-selection.md +60 -0
- package/dist/knowledge/skills/frontend-cdn-publish/SKILL.md +237 -0
- package/dist/knowledge/skills/frontend-cdn-publish/references/cloudflare-and-operator-setup.md +56 -0
- package/dist/knowledge/skills/frontend-cdn-publish/references/framework-cdn-config-api.md +176 -0
- package/dist/knowledge/skills/i18n-label-generation/SKILL.md +261 -0
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +67 -0
- package/dist/knowledge/skills/i18n-label-generation/references/label-placement.md +7 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +269 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +67 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/i18n-routing.md +9 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +245 -0
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +67 -0
- package/dist/knowledge/skills/i18n-translation-rerun/references/translation-workflow.md +17 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +646 -0
- package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +77 -0
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +282 -0
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +265 -0
- package/dist/knowledge/skills/infra-environment-config/references/infra-config-files.md +7 -0
- package/dist/knowledge/skills/journey-approve/SKILL.md +43 -0
- package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +42 -0
- package/dist/knowledge/skills/journey-next/SKILL.md +42 -0
- package/dist/knowledge/skills/journey-report/SKILL.md +43 -0
- package/dist/knowledge/skills/journey-run/SKILL.md +55 -0
- package/dist/knowledge/skills/journey-status/SKILL.md +50 -0
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +370 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +50 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +409 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +247 -0
- package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +474 -0
- package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +139 -0
- package/dist/knowledge/skills/market-alternatives/SKILL.md +543 -0
- package/dist/knowledge/skills/market-authoring-overview/SKILL.md +354 -0
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +138 -0
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +129 -0
- package/dist/knowledge/skills/market-category/SKILL.md +290 -0
- package/dist/knowledge/skills/market-channels/SKILL.md +361 -0
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +2752 -0
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +2443 -0
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +1484 -0
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +1230 -0
- package/dist/knowledge/skills/market-icp/SKILL.md +625 -0
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +352 -0
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +415 -0
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1439 -0
- package/dist/knowledge/skills/market-persona/SKILL.md +407 -0
- package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +392 -0
- package/dist/knowledge/skills/market-positioning-authoring/references/framework-positioning-api.md +97 -0
- package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +665 -0
- package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +620 -0
- package/dist/knowledge/skills/market-scoring-interpretation/references/framework-scoring-api.md +291 -0
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +1706 -0
- package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1228 -0
- package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +260 -0
- package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +579 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +318 -0
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +544 -0
- package/dist/knowledge/skills/module-registration/SKILL.md +212 -0
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +366 -0
- package/dist/knowledge/skills/module-registration/references/registry-files.md +9 -0
- package/dist/knowledge/skills/module-relationships/SKILL.md +523 -0
- package/dist/knowledge/skills/module-relationships/references/cross-resource-fk-checklist.md +7 -0
- package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +738 -0
- package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +174 -0
- package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-template-api.md +203 -0
- package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-template-spec-api.md +62 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +239 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +90 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +50 -0
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +652 -0
- package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +182 -0
- package/dist/knowledge/skills/rate-limit-authoring/references/scope-key-and-bucket-conventions.md +137 -0
- package/dist/knowledge/skills/resource-add-field/SKILL.md +272 -0
- package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +153 -0
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +845 -0
- package/dist/knowledge/skills/resource-add-module/SKILL.md +322 -0
- package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +67 -0
- package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +15 -0
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +222 -0
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +540 -0
- package/dist/knowledge/skills/resource-add-resource/references/scaffold-surfaces-checklist.md +25 -0
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +370 -0
- package/dist/knowledge/skills/resource-config-wiring/references/config-change-routing.md +11 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +622 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +248 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +1769 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +1209 -0
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +228 -0
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +693 -0
- package/dist/knowledge/skills/resource-external-data/SKILL.md +349 -0
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +187 -0
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +261 -0
- package/dist/knowledge/skills/resource-external-data/references/lane-selection.md +49 -0
- package/dist/knowledge/skills/resource-external-data/references/pipeline-destination-schema.md +43 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +308 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-named-mcp-servers-contract.md +166 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +63 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +77 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-client-registration-postures.md +90 -0
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +424 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/corpus-field-selection.md +90 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +261 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-file-rag-source-api.md +117 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +597 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +181 -0
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +318 -0
- package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +132 -0
- package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +62 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +63 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +70 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +559 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-polymorphic-resources-api.md +147 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +247 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +164 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +327 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +1286 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +1080 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +75 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +62 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +69 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +45 -0
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +389 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-conditional-visibility-api.md +106 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +176 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +103 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-foreign-key-ui-api.md +97 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +839 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +461 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +125 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +245 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +302 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/ui-layer-boundaries.md +13 -0
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +569 -0
- package/dist/knowledge/skills/seeding-authoring/references/data-seeding-mode-picker.md +154 -0
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +176 -0
- package/dist/knowledge/skills/seeding-operations/SKILL.md +505 -0
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +337 -0
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +171 -0
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +662 -0
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +134 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +65 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +127 -0
- package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +726 -0
- package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +242 -0
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +362 -0
- package/dist/knowledge/skills/spec-companion-exports/references/companion-export-checklist.md +8 -0
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +533 -0
- package/dist/knowledge/skills/spec-component-update/SKILL.md +315 -0
- package/dist/knowledge/skills/spec-component-update/references/component-spec-props.md +8 -0
- package/dist/knowledge/skills/spec-component-update/references/framework-frontend-component-spec-api.md +481 -0
- package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +283 -0
- package/dist/knowledge/skills/spec-composite-view-update/references/composite-spec-sections.md +5 -0
- package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +51 -0
- package/dist/knowledge/skills/spec-family-update/SKILL.md +300 -0
- package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +13 -0
- package/dist/knowledge/skills/spec-family-update/references/framework-error-message-specifications-api.md +108 -0
- package/dist/knowledge/skills/spec-family-update/references/framework-family-specifications-api.md +111 -0
- package/dist/knowledge/skills/spec-feature-update/SKILL.md +306 -0
- package/dist/knowledge/skills/spec-feature-update/references/feature-spec-scope.md +5 -0
- package/dist/knowledge/skills/spec-feature-update/references/framework-feature-specification-api.md +95 -0
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +220 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +319 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +2610 -0
- package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +12 -0
- package/dist/knowledge/skills/spec-update-after-change/SKILL.md +195 -0
- package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +173 -0
- package/dist/knowledge/skills/spec-update-after-change/references/spec-maintenance-by-surface.md +33 -0
- package/dist/knowledge/skills/spec-update-after-change/references/surface-to-spec-routing.md +14 -0
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +259 -0
- package/dist/knowledge/skills/views-add-composite-view/references/composite-view-routing.md +10 -0
- package/dist/knowledge/skills/views-add-composite-view/references/framework-inserted-view-identity-api.md +151 -0
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +225 -0
- package/dist/knowledge/skills/views-add-custom-view/references/custom-view-routing.md +10 -0
- package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +107 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +201 -0
- package/dist/knowledge/skills/views-app-level/references/app-level-views-routing.md +9 -0
- package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +107 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +264 -0
- package/dist/knowledge/skills/views-chart-authoring/references/chart-view-checklist.md +7 -0
- package/dist/knowledge/skills/views-chart-authoring/references/framework-chart-view-contracts-api.md +82 -0
- package/dist/knowledge/skills/views-chart-authoring/references/framework-inserted-view-identity-api.md +152 -0
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +302 -0
- package/dist/knowledge/skills/views-composite-authoring/references/composite-embedding-checklist.md +23 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +133 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-inserted-view-identity-api.md +152 -0
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +209 -0
- package/dist/knowledge/skills/views-execution-authoring/references/execution-view-checklist.md +7 -0
- package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +389 -0
- package/dist/knowledge/skills/views-execution-authoring/references/framework-inserted-view-identity-api.md +152 -0
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +444 -0
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +587 -0
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +1426 -0
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +553 -0
- package/dist/knowledge/skills/website-bundle-discipline/references/example-website-button-override.md +52 -0
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +357 -0
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +511 -0
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +376 -0
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +304 -0
- package/dist/knowledge/skills/website-label-pack/SKILL.md +390 -0
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +461 -0
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +264 -0
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +414 -0
- package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +366 -0
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +420 -0
- package/dist/knowledge/skills/website-page-variants/SKILL.md +256 -0
- package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +302 -0
- package/dist/knowledge/skills/website-section-contact/SKILL.md +950 -0
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +579 -0
- package/dist/knowledge/skills/website-section-cta/SKILL.md +822 -0
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +579 -0
- package/dist/knowledge/skills/website-section-faq/SKILL.md +917 -0
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +579 -0
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +878 -0
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +579 -0
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +895 -0
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +579 -0
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +814 -0
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +579 -0
- package/dist/knowledge/skills/website-section-hero/SKILL.md +944 -0
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +583 -0
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +934 -0
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +579 -0
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +912 -0
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +579 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +624 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +633 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +193 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +790 -0
- package/dist/knowledge/topic-index.json +17510 -0
- package/dist/tsconfig.build.tsbuildinfo +1 -0
- package/dist/tsconfig.tsbuildinfo +1 -0
- package/package.json +49 -0
|
@@ -0,0 +1,321 @@
|
|
|
1
|
+
# Foundation — Domain Plan → Configured, Bootable App Skeleton (v1 scaffold)
|
|
2
|
+
|
|
3
|
+
### Target Application Framing
|
|
4
|
+
|
|
5
|
+
This knowledge is for configuring behavior in the target application.
|
|
6
|
+
Wildo is the framework surface being used, not the product being built.
|
|
7
|
+
|
|
8
|
+
Read and apply these patterns from the application-developer point of view:
|
|
9
|
+
|
|
10
|
+
- how the application should configure the relevant app-level file
|
|
11
|
+
- how the application should use framework-provided factories, enums, and helpers
|
|
12
|
+
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
> **This is a v1 scaffold methodology, and part of the greenfield tooling it
|
|
16
|
+
> sequences does not exist yet.** The foundation *sequence* below is a working first cut —
|
|
17
|
+
> the capability-derivation heuristic, the module-registration convention, and
|
|
18
|
+
> the provider-selection rubric are deliberately explicit so they can be tuned
|
|
19
|
+
> against real runs. The deterministic steps that *materialize the skeleton* and
|
|
20
|
+
> *install app-knowledge* are a later greenfield-enablement phase and are **not
|
|
21
|
+
> built**. Those two steps are authored as `// TODO CLI COMMAND:` placeholders;
|
|
22
|
+
> headless setup and verified local initialization are registered commands. **This playbook is the
|
|
23
|
+
> METHOD — the description of the foundation sequence — not a runnable
|
|
24
|
+
> foundation.** If you find yourself building or wiring the greenfield CLI
|
|
25
|
+
> tooling, stop: that is out of this playbook's scope.
|
|
26
|
+
|
|
27
|
+
## Where you are in the journey
|
|
28
|
+
|
|
29
|
+
This is the **foundation** playbook — the point in the **bottom-up** phase where
|
|
30
|
+
the *plan* becomes a *bootable app*. It runs **after** the `bottom_up.domain-plan`
|
|
31
|
+
playbook produced (and the creator approved) the **domain plan**: the module
|
|
32
|
+
decomposition, the per-module resource inventory, and the inter-resource
|
|
33
|
+
relationship intents. Its preconditions — `phase_is bottom_up` and
|
|
34
|
+
`artifact_exists domain-plan` and `artifact_exists vision-brief` — mean the journey
|
|
35
|
+
has entered the build-shaping phase and the two load-bearing artifacts are present:
|
|
36
|
+
the **domain plan** (whose modules you register) and the **vision brief** (whose
|
|
37
|
+
compliance and vision constraints drive which engine capabilities you enable). The
|
|
38
|
+
route-bound `transition_committed` fact that authorized and applied crossing from top-down into
|
|
39
|
+
bottom-up was the domain-plan playbook's duty (it is the first bottom-up playbook);
|
|
40
|
+
you do not re-cross that boundary — the domain plan's existence already sits behind
|
|
41
|
+
it.
|
|
42
|
+
|
|
43
|
+
You are not re-opening the domain plan here — you are turning an *approved* plan
|
|
44
|
+
into the *configured application skeleton the build loop then fills in*.
|
|
45
|
+
|
|
46
|
+
## What this playbook does
|
|
47
|
+
|
|
48
|
+
You are the **foundation engineer**. This playbook reads the approved domain plan
|
|
49
|
+
and the vision brief, then configures and brings up the application skeleton so the
|
|
50
|
+
build loop has a real workspace to author into. You perform a **mixed sequence**
|
|
51
|
+
(hence the `composite` executor — the runner sequences the tiers per this guidance):
|
|
52
|
+
a config/skeleton **authoring** pass, then a **deterministic bring-up** pass. The
|
|
53
|
+
work, in order:
|
|
54
|
+
|
|
55
|
+
1. **Derive the engine capabilities** from the compliance/vision constraints (and
|
|
56
|
+
the market/business-model facts) and enable them in `./wildo.saas.config.ts`.
|
|
57
|
+
2. **Declare the domain-plan's modules** at the SaaS root (they are registered across
|
|
58
|
+
the runtimes after Step 4 materializes the skeleton, so it boots with them).
|
|
59
|
+
3. **Select the providers** the enabled capabilities need.
|
|
60
|
+
4. **Run the deterministic bring-up** — materialize the skeleton, install
|
|
61
|
+
app-knowledge, `wildo setup --non-interactive`, then `wildo local init`.
|
|
62
|
+
|
|
63
|
+
You emit **no artifact**. The deliverable is the app itself: `./wildo.saas.config.ts`,
|
|
64
|
+
the materialized skeleton, and a verified local initialization. Record *why* each
|
|
65
|
+
capability, module and provider was chosen in the config's own comments, where the
|
|
66
|
+
next reader of that file will find it.
|
|
67
|
+
|
|
68
|
+
(A `foundation-manifest` artifact was declared here until 2026-08-25 and is now
|
|
69
|
+
retired with the app-creation verification/digest aspect. It was a bookkeeping record
|
|
70
|
+
of decisions the config already carries — deleting it costs no fact about the app.)
|
|
71
|
+
|
|
72
|
+
This is a **foundation pass**. You enable capabilities, declare modules as shells,
|
|
73
|
+
select providers, and bring the skeleton up. You do **not** author resource schemas,
|
|
74
|
+
fields, ui-behavior, views, or navigation — that is the **build loop's** job,
|
|
75
|
+
downstream of this foundation.
|
|
76
|
+
|
|
77
|
+
## Read state first — the artifacts you read, the files you write
|
|
78
|
+
|
|
79
|
+
This playbook is **idempotent** and, on a re-run, a *refinement*. Before configuring
|
|
80
|
+
anything:
|
|
81
|
+
|
|
82
|
+
1. Read the current journey state and scope through the `journey-status` skill (it
|
|
83
|
+
owns the read; do not re-derive it here). Confirm the domain plan is present and
|
|
84
|
+
approved, and check whether a `./wildo.saas.config.ts` already exists from an
|
|
85
|
+
earlier run (refine it, do not re-author — see below).
|
|
86
|
+
2. Read the **domain plan** (`domain-plan` family — the modules to register + their
|
|
87
|
+
resource inventory) and the **vision brief** (`vision-brief` — the compliance and
|
|
88
|
+
vision constraints that are the **primary** driver of capability selection).
|
|
89
|
+
**Contextual** reads that sharpen the choices (they are *not* preconditions — read
|
|
90
|
+
them if present, and note that the `business-model` may be absent, per the top-down
|
|
91
|
+
phase-gate's optional posture):
|
|
92
|
+
- the **market-snapshot** (`market-snapshot`) — its ICPs sharpen capability
|
|
93
|
+
selection (a B2B / organization-scoped ICP → the `organizations` capability);
|
|
94
|
+
- the **business-model** (`business-model`) — a paid plan → the billing capability
|
|
95
|
+
(absent business model = no billing capability derived from it);
|
|
96
|
+
- the **relationship drafts** inside the domain plan (the inter-resource relationships the build loop will
|
|
97
|
+
wire — they can hint at which capabilities a module needs);
|
|
98
|
+
- the **requirements** (functional/non-functional needs a capability may satisfy);
|
|
99
|
+
- the **roadmap** (which modules are MVP-critical, so you enable what the first
|
|
100
|
+
release needs and defer the rest).
|
|
101
|
+
|
|
102
|
+
// TODO CLI COMMAND: wildo context journey-status
|
|
103
|
+
// (read current journey scope + approved artifacts + any existing foundation config)
|
|
104
|
+
// TODO CLI COMMAND: wildo context domain-plan
|
|
105
|
+
// (read the modules to register + their per-module resource inventory)
|
|
106
|
+
|
|
107
|
+
You **read** `domain-plan` + `vision-brief` + `market-snapshot` + `business-model`
|
|
108
|
+
+ `requirements` + `roadmap` (the domain plan carries its relationship drafts); you **write**
|
|
109
|
+
`./wildo.saas.config.ts` and the materialized skeleton — app files, committed to git,
|
|
110
|
+
which is where the record of what was decided lives.
|
|
111
|
+
|
|
112
|
+
## Step 1 — Derive and enable the engine capabilities
|
|
113
|
+
|
|
114
|
+
Engine capabilities are the framework surfaces the app turns on (organizations,
|
|
115
|
+
billing, notifications, audit trails, data residency, and so on). **Derive them from
|
|
116
|
+
the definition set — do not guess:**
|
|
117
|
+
|
|
118
|
+
1. **Compliance/vision constraints → capabilities (the primary driver).** Walk the
|
|
119
|
+
vision brief's constraints. A compliance constraint implies a capability (a privacy-law /
|
|
120
|
+
data-residency constraint → the residency/audit capability; an external-assurance constraint →
|
|
121
|
+
audit trails). A vision fact implies a capability (an organization-scoped product →
|
|
122
|
+
`organizations`).
|
|
123
|
+
2. **Market / business-model facts → capabilities (contextual sharpener).** A B2B or
|
|
124
|
+
organization-scoped ICP in the `market-snapshot` → the `organizations` capability; a
|
|
125
|
+
paid plan in the `business-model` → billing. Treat these as sharpeners over the
|
|
126
|
+
primary compliance/vision derivation — and remember the `business-model` may be
|
|
127
|
+
absent (then derive no billing capability from it).
|
|
128
|
+
3. **Domain-plan needs → capabilities.** A module whose capability clearly needs a
|
|
129
|
+
framework surface (a module that sends transactional email → notifications) turns
|
|
130
|
+
on that capability.
|
|
131
|
+
4. **Enable only what the definition set justifies.** Every enabled capability must
|
|
132
|
+
trace to a compliance/vision constraint, a market/business-model fact, or a
|
|
133
|
+
domain-plan module need. Do **not** enable a capability nothing asks for — that is
|
|
134
|
+
speculative surface area (a coherence CONCERN — see the quality gate). Conversely,
|
|
135
|
+
a compliance constraint that requires a capability you did **not** enable is a
|
|
136
|
+
coverage GAP.
|
|
137
|
+
|
|
138
|
+
The `config-saas` skill carries the vocabulary for the `engineCapabilities` block of
|
|
139
|
+
`./wildo.saas.config.ts`; read it to enable capabilities idiomatically. Record each
|
|
140
|
+
enabled capability **and its justification** as a comment beside it in the config.
|
|
141
|
+
|
|
142
|
+
## Step 2 — Declare the domain-plan's modules (register across runtimes after materialization)
|
|
143
|
+
|
|
144
|
+
**Mind the ordering.** At *config-authoring* time (this step, before the skeleton
|
|
145
|
+
exists) you can only **declare** the modules at the SaaS root. The shared / frontend /
|
|
146
|
+
backend module registry files do not exist until Step 4 materializes the skeleton, so
|
|
147
|
+
the cross-runtime **registration** happens *after* materialization — do not edit
|
|
148
|
+
registry files the skeleton has not yet created.
|
|
149
|
+
|
|
150
|
+
1. **Declare each module at the SaaS root (now).** Add each domain-plan module to the
|
|
151
|
+
`modules` composition in `./wildo.saas.config.ts` (the `config-saas` skill owns this
|
|
152
|
+
surface). This declares the module's *existence* and is exactly what the skeleton
|
|
153
|
+
materialization (Step 4) builds the per-module workspaces and registries from.
|
|
154
|
+
2. **Register across the runtimes (after Step 4 materializes the skeleton).** Once the
|
|
155
|
+
skeleton exists, each declared module is registered across the shared / frontend /
|
|
156
|
+
backend registries so every runtime loads it — regenerated by `config sync` from the
|
|
157
|
+
declared modules where the tooling supports it, or wired with the `module-registration`
|
|
158
|
+
skill (distinct from `config-saas`, which only declares existence at the root). At
|
|
159
|
+
foundation depth you register the module **shells** (the module exists and boots); the
|
|
160
|
+
resources *inside* each module are authored by the build loop.
|
|
161
|
+
3. **Declare every domain-plan module — and no more.** A module the domain plan named
|
|
162
|
+
that is missing from the config is a GAP; a module in the config the domain plan did
|
|
163
|
+
not name is an unjustified-module CONCERN. Record the declared modules (each traced
|
|
164
|
+
to its domain-plan module) as a comment beside it in the config.
|
|
165
|
+
|
|
166
|
+
**Do not author the resources here.** The domain plan's per-module resource inventory
|
|
167
|
+
tells you *what* resources each module will own, but authoring their schemas, fields,
|
|
168
|
+
and config is the **build loop's** job. If you catch yourself writing a resource
|
|
169
|
+
schema, stop: that is out of this playbook's depth.
|
|
170
|
+
|
|
171
|
+
## Step 3 — Select the providers
|
|
172
|
+
|
|
173
|
+
Enabled capabilities that reach an external service need a **provider** (billing → a
|
|
174
|
+
payment provider; notifications/email → an email provider; file storage → an object
|
|
175
|
+
store). For each such capability, select and wire the provider scope +
|
|
176
|
+
`providerConfigurations` in `./wildo.saas.config.ts` (the `config-saas` skill covers
|
|
177
|
+
the provider surfaces):
|
|
178
|
+
|
|
179
|
+
- **Every provider matches a declared capability.** A provider wired for no enabled
|
|
180
|
+
capability is a CONCERN; an enabled capability that needs a provider with none
|
|
181
|
+
selected is a GAP.
|
|
182
|
+
- **Do not seed secrets here.** Provider *selection* (which provider, which scope) is
|
|
183
|
+
foundation; the per-environment secret material is seeded by the deterministic
|
|
184
|
+
bring-up / environment step, not authored inline. Record the selected providers
|
|
185
|
+
(each matched to its capability) as a comment beside it in the config.
|
|
186
|
+
|
|
187
|
+
## Step 4 — The deterministic bring-up sequence (partially deferred)
|
|
188
|
+
|
|
189
|
+
With the config authored, run the **deterministic bring-up** in prerequisite order.
|
|
190
|
+
The skeleton template and app-knowledge installer remain deferred; do not invent
|
|
191
|
+
them. Headless `wildo setup` and `wildo local init` are registered and should be
|
|
192
|
+
executed after the app structure exists.
|
|
193
|
+
|
|
194
|
+
1. **Materialize the app skeleton** — create the `./frontend/`, `./shared-lib/`,
|
|
195
|
+
`./backend-api/`, `./specifications/`, and `./infrastructure/` workspaces + the
|
|
196
|
+
module registries from the empty-app template, so the declared modules have a real
|
|
197
|
+
workspace.
|
|
198
|
+
|
|
199
|
+
// TODO CLI COMMAND: wildo materialize skeleton
|
|
200
|
+
// (scaffold app/ shared-lib/ backend-api/ specifications/ + module registries — greenfield tooling, deferred)
|
|
201
|
+
|
|
202
|
+
2. **Install app-knowledge** — drop the compiled skills / rules / agents into the
|
|
203
|
+
project's agent-config folders so the build loop's coding agent reads them
|
|
204
|
+
naturally with cwd at the app root.
|
|
205
|
+
|
|
206
|
+
// TODO CLI COMMAND: wildo install app-knowledge
|
|
207
|
+
// (install compiled skills/rules/agents into the app's .claude/ — greenfield tooling, deferred)
|
|
208
|
+
|
|
209
|
+
3. **Run setup** — configure the app from the authored `./wildo.saas.config.ts` and
|
|
210
|
+
the `./infrastructure/` env configs (the `infra-environment-config` skill owns the
|
|
211
|
+
typed infra env files; the `local-environment-bootstrap` skill owns the `wildo`
|
|
212
|
+
lifecycle). Headless setup is registered and fail-closed on the administrator seed
|
|
213
|
+
environment variables; it mints the environment generation without placeholders.
|
|
214
|
+
|
|
215
|
+
```bash
|
|
216
|
+
wildo setup --non-interactive
|
|
217
|
+
```
|
|
218
|
+
|
|
219
|
+
4. **Initialize and verify the project** — run the registered convergence journey.
|
|
220
|
+
It regenerates artifacts, starts and readiness-gates backing services, reconciles
|
|
221
|
+
platform Mongo state and credentials, starts native platform services, registers the
|
|
222
|
+
app once, emits all runtime projections, and executes a signed managed-config read.
|
|
223
|
+
|
|
224
|
+
```bash
|
|
225
|
+
wildo local init
|
|
226
|
+
```
|
|
227
|
+
|
|
228
|
+
Report the status of each bring-up step to the creator in your result. Skeleton
|
|
229
|
+
materialization and app-knowledge installation remain deferred; setup and local
|
|
230
|
+
initialization are executable once those app files exist and must be recorded from their
|
|
231
|
+
real exit/postcondition result rather than marked complete from intent.
|
|
232
|
+
|
|
233
|
+
## Refine, don't re-author
|
|
234
|
+
|
|
235
|
+
- **Keep what still holds.** On a re-run, do not disable a capability, drop a module,
|
|
236
|
+
or re-select a provider that is already correct. Only enable a newly-justified
|
|
237
|
+
capability, register a newly-added domain-plan module, or correct a provider where
|
|
238
|
+
the definition set genuinely changed.
|
|
239
|
+
- **Reuse existing module ids and provider scopes.** A module already registered keeps
|
|
240
|
+
its id; a provider already selected keeps its scope — never mint a second one for the
|
|
241
|
+
same module/capability.
|
|
242
|
+
- **Follow the definition set.** If the domain plan added a module or the vision brief
|
|
243
|
+
added a compliance constraint since the last run, reflect it (register the module,
|
|
244
|
+
enable the capability) — do not re-derive the whole configuration from scratch. The
|
|
245
|
+
delta is visible in `git diff` on the config, which is the record.
|
|
246
|
+
|
|
247
|
+
## Quality gate — `foundation-configured-coherently` (declarative at scaffold depth)
|
|
248
|
+
|
|
249
|
+
The foundation is checked against the `foundation-configured-coherently` **reviewer
|
|
250
|
+
checklist** (see the end of this method): five invariants (capability derivation, module registration, provider coverage,
|
|
251
|
+
sequence order, and foundation-depth boundary discipline), each marked PASS / CONCERN /
|
|
252
|
+
GAP.
|
|
253
|
+
|
|
254
|
+
This checklist is **declarative**: no runtime executes it (rubric-only judge gates were retired at the flexible-intelligence hard cut — judgment runs only through a compiled Evaluation Treatment, and this playbook has none yet), so it ships as the **creator's review checklist** — nothing runs it automatically. The **trust floor** for accepting the foundation today is the
|
|
255
|
+
creator's `approve_result` review of the produced config and the bring-up result. There is
|
|
256
|
+
intentionally **no deterministic gate**: config validation is a `wildo` CLI concern
|
|
257
|
+
(`config sync` / validate), not a validator in the journey-artifact schemaRef
|
|
258
|
+
vocabulary. When the greenfield tooling lands, the non-bypassable floor still
|
|
259
|
+
hard-gates the real destructive / off-machine infra bring-up regardless of this gate.
|
|
260
|
+
|
|
261
|
+
## Scaffold-depth and tooling-deferral boundary
|
|
262
|
+
|
|
263
|
+
Keep this playbook at scaffold depth **and** honour the tooling deferral. Explicitly
|
|
264
|
+
**out of scope here**:
|
|
265
|
+
|
|
266
|
+
- **The remaining greenfield CLI tooling itself.** The skeleton-materialization
|
|
267
|
+
template and app-knowledge installer do **not** exist yet and are a later
|
|
268
|
+
greenfield-enablement phase. Their two `// TODO CLI COMMAND:` placeholders must not
|
|
269
|
+
be invented. `wildo setup --non-interactive` and `wildo local init` do exist and are
|
|
270
|
+
the registered lifecycle once the app structure is present.
|
|
271
|
+
- **Resource / field / schema authoring.** The config declares modules as shells and
|
|
272
|
+
enables capabilities; it does **not** author resource schemas, fields, enums,
|
|
273
|
+
decorators, ui-behavior, views, or navigation. That is the build loop. If you catch
|
|
274
|
+
yourself writing a resource, stop.
|
|
275
|
+
- **Re-introducing a foundation artifact.** The `foundation-manifest` family was
|
|
276
|
+
retired on 2026-08-25 with the app-creation verification/digest aspect. Do **NOT**
|
|
277
|
+
reshape `_core` to bring it back: the config file and its git history already carry
|
|
278
|
+
every decision it recorded.
|
|
279
|
+
- **Deep capability / provider modelling.** A defended capability-selection model
|
|
280
|
+
(per-compliance-regime obligation → capability mapping, provider cost/feature
|
|
281
|
+
matrices, multi-provider fallback) is a later depth pass. You derive capabilities
|
|
282
|
+
from the definition set with the v1 heuristic above — not a solved obligation graph.
|
|
283
|
+
|
|
284
|
+
If you find yourself perfecting any of the above, stop and leave the slice at scaffold
|
|
285
|
+
depth — depth (and the greenfield tooling) are dedicated later passes done once,
|
|
286
|
+
holistically.
|
|
287
|
+
|
|
288
|
+
## What you emit
|
|
289
|
+
|
|
290
|
+
- The authored **`./wildo.saas.config.ts`** (an app file) — the enabled engine
|
|
291
|
+
capabilities, the registered modules, and the selected providers — plus the
|
|
292
|
+
registered module shells across the runtimes and (when the tooling lands) the
|
|
293
|
+
brought-up skeleton.
|
|
294
|
+
- The **bring-up result** reported to the creator: the status of each step, taken from
|
|
295
|
+
its real exit/postcondition rather than from intent. This is a report, not a stored
|
|
296
|
+
artifact — nothing reads it back.
|
|
297
|
+
|
|
298
|
+
The creator reviews the result (approval posture `approve_result`) before it is
|
|
299
|
+
accepted as the journey's foundation, which the bottom-up build loop then fills in
|
|
300
|
+
with authored resources, operations, UX, and integrations.
|
|
301
|
+
|
|
302
|
+
## References
|
|
303
|
+
|
|
304
|
+
- `.claude/skills/journey-status/SKILL.md` — read the current journey state and scope,
|
|
305
|
+
and confirm the approved domain plan + vision brief are in place to configure from.
|
|
306
|
+
- `.claude/skills/config-saas/SKILL.md` — the `./wildo.saas.config.ts` authoring
|
|
307
|
+
surface: `engineCapabilities`, `modules`, provider scopes, and `providerConfigurations`.
|
|
308
|
+
- `.claude/skills/module-registration/SKILL.md` — register each domain-plan module
|
|
309
|
+
across the shared / frontend / backend registries so the skeleton boots with it
|
|
310
|
+
(distinct from `config-saas`, which only declares module existence at the root).
|
|
311
|
+
- `.claude/skills/infra-environment-config/SKILL.md` — the typed `./infrastructure/`
|
|
312
|
+
environment configs (backing services, public domain, service auth) the bring-up needs.
|
|
313
|
+
- `.claude/skills/local-environment-bootstrap/SKILL.md` — the `wildo` lifecycle
|
|
314
|
+
(`setup`, `local init`, `local reinit`, `local dev`) for deterministic initialization,
|
|
315
|
+
repair, clean-room recovery, and runtime start.
|
|
316
|
+
|
|
317
|
+
## Reviewer checklist — `foundation-configured-coherently`
|
|
318
|
+
|
|
319
|
+
Formerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim, minus the retired runner's closing sentence:
|
|
320
|
+
|
|
321
|
+
Judge whether the authored foundation (the ./wildo.saas.config.ts composition + the materialized skeleton) is a coherent realisation of the approved domain plan and the top-down definition set. Assess five invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) CAPABILITY DERIVATION — every enabled engine capability traces to a compliance/vision, business-model, market, or domain-plan need; unjustified capabilities are a CONCERN and missing required capabilities are a GAP. (2) MODULE REGISTRATION — every approved domain-plan module is declared and registered across runtimes; missing modules are a GAP and extra modules are a CONCERN. (3) PROVIDER COVERAGE — every provider serves a declared capability and every provider-backed capability has a provider. (4) SEQUENCE ORDER AND PROOF — author config → materialize skeleton → install app-knowledge → wildo setup --non-interactive → wildo local init. Treat setup intent, container health, or an initialization marker as insufficient: local init must reach its signed managed-config-read postcondition. (5) BOUNDARY DISCIPLINE — stay at foundation depth and do not author resources, fields, ui-behavior, views, or navigation. Do not invent the still-deferred skeleton/app-knowledge installer commands; headless setup and local init are registered and should be executed once the structure exists. This reviewer checklist is declarative; creator approval is the trust floor.
|
|
@@ -0,0 +1,79 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ref": "bottom_up.foundation",
|
|
3
|
+
"version": "0.2.0",
|
|
4
|
+
"phase": "bottom_up",
|
|
5
|
+
"intent": "Bottom-up foundation — turn the approved domain plan + the top-down definition set into a configured, bootable application skeleton. Reads the domain-plan (the module decomposition + per-module resource inventory) and the vision-brief (whose compliance/vision constraints drive which engine capabilities to enable), then: (1) authors ./wildo.saas.config.ts for real — the engine capabilities (derived from compliance/vision), the modules (from the domain plan), and the providers (matched to the declared capabilities); (2) materializes the app skeleton (app/ shared-lib/ backend-api/ specifications/ + the module registries); (3) installs app-knowledge; (4) runs the deterministic bring-up — wildo setup --non-interactive, then wildo local init. This is a v1 SCAFFOLD METHOD describing the foundation SEQUENCE: skeleton materialization and app-knowledge installation remain deferred greenfield tooling, while headless setup and verified local initialization are registered commands once the app structure exists. It emits NO artifact: the deliverable is the app itself (the authored config + materialized skeleton + verified initialization), and the reasons behind each capability/module/provider choice are recorded as comments in the config the next reader opens. The foundation-manifest family it used to emit was retired 2026-08-25 with the app-creation verification/digest aspect. Runs after the domain plan is approved and the journey is in the bottom_up phase.",
|
|
6
|
+
"functionalTopics": [
|
|
7
|
+
"configure_application_foundation"
|
|
8
|
+
],
|
|
9
|
+
"preconditions": [
|
|
10
|
+
{
|
|
11
|
+
"kind": "phase_is",
|
|
12
|
+
"phase": "bottom_up"
|
|
13
|
+
},
|
|
14
|
+
{
|
|
15
|
+
"kind": "artifact_exists",
|
|
16
|
+
"selector": {
|
|
17
|
+
"family": "domain-plan"
|
|
18
|
+
}
|
|
19
|
+
},
|
|
20
|
+
{
|
|
21
|
+
"kind": "artifact_exists",
|
|
22
|
+
"selector": {
|
|
23
|
+
"family": "vision-brief"
|
|
24
|
+
}
|
|
25
|
+
}
|
|
26
|
+
],
|
|
27
|
+
"inputs": [
|
|
28
|
+
{
|
|
29
|
+
"family": "domain-plan"
|
|
30
|
+
},
|
|
31
|
+
{
|
|
32
|
+
"family": "vision-brief"
|
|
33
|
+
},
|
|
34
|
+
{
|
|
35
|
+
"family": "market-snapshot"
|
|
36
|
+
},
|
|
37
|
+
{
|
|
38
|
+
"family": "business-model"
|
|
39
|
+
},
|
|
40
|
+
{
|
|
41
|
+
"family": "requirements"
|
|
42
|
+
},
|
|
43
|
+
{
|
|
44
|
+
"family": "roadmap"
|
|
45
|
+
}
|
|
46
|
+
],
|
|
47
|
+
"outputs": [],
|
|
48
|
+
"stepOutputs": [],
|
|
49
|
+
"method": {
|
|
50
|
+
"guidance": "# Foundation — Domain Plan → Configured, Bootable App Skeleton (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology, and part of the greenfield tooling it\n> sequences does not exist yet.** The foundation *sequence* below is a working first cut —\n> the capability-derivation heuristic, the module-registration convention, and\n> the provider-selection rubric are deliberately explicit so they can be tuned\n> against real runs. The deterministic steps that *materialize the skeleton* and\n> *install app-knowledge* are a later greenfield-enablement phase and are **not\n> built**. Those two steps are authored as `// TODO CLI COMMAND:` placeholders;\n> headless setup and verified local initialization are registered commands. **This playbook is the\n> METHOD — the description of the foundation sequence — not a runnable\n> foundation.** If you find yourself building or wiring the greenfield CLI\n> tooling, stop: that is out of this playbook's scope.\n\n## Where you are in the journey\n\nThis is the **foundation** playbook — the point in the **bottom-up** phase where\nthe *plan* becomes a *bootable app*. It runs **after** the `bottom_up.domain-plan`\nplaybook produced (and the creator approved) the **domain plan**: the module\ndecomposition, the per-module resource inventory, and the inter-resource\nrelationship intents. Its preconditions — `phase_is bottom_up` and\n`artifact_exists domain-plan` and `artifact_exists vision-brief` — mean the journey\nhas entered the build-shaping phase and the two load-bearing artifacts are present:\nthe **domain plan** (whose modules you register) and the **vision brief** (whose\ncompliance and vision constraints drive which engine capabilities you enable). The\nroute-bound `transition_committed` fact that authorized and applied crossing from top-down into\nbottom-up was the domain-plan playbook's duty (it is the first bottom-up playbook);\nyou do not re-cross that boundary — the domain plan's existence already sits behind\nit.\n\nYou are not re-opening the domain plan here — you are turning an *approved* plan\ninto the *configured application skeleton the build loop then fills in*.\n\n## What this playbook does\n\nYou are the **foundation engineer**. This playbook reads the approved domain plan\nand the vision brief, then configures and brings up the application skeleton so the\nbuild loop has a real workspace to author into. You perform a **mixed sequence**\n(hence the `composite` executor — the runner sequences the tiers per this guidance):\na config/skeleton **authoring** pass, then a **deterministic bring-up** pass. The\nwork, in order:\n\n1. **Derive the engine capabilities** from the compliance/vision constraints (and\n the market/business-model facts) and enable them in `./wildo.saas.config.ts`.\n2. **Declare the domain-plan's modules** at the SaaS root (they are registered across\n the runtimes after Step 4 materializes the skeleton, so it boots with them).\n3. **Select the providers** the enabled capabilities need.\n4. **Run the deterministic bring-up** — materialize the skeleton, install\n app-knowledge, `wildo setup --non-interactive`, then `wildo local init`.\n\nYou emit **no artifact**. The deliverable is the app itself: `./wildo.saas.config.ts`,\nthe materialized skeleton, and a verified local initialization. Record *why* each\ncapability, module and provider was chosen in the config's own comments, where the\nnext reader of that file will find it.\n\n(A `foundation-manifest` artifact was declared here until 2026-08-25 and is now\nretired with the app-creation verification/digest aspect. It was a bookkeeping record\nof decisions the config already carries — deleting it costs no fact about the app.)\n\nThis is a **foundation pass**. You enable capabilities, declare modules as shells,\nselect providers, and bring the skeleton up. You do **not** author resource schemas,\nfields, ui-behavior, views, or navigation — that is the **build loop's** job,\ndownstream of this foundation.\n\n## Read state first — the artifacts you read, the files you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before configuring\nanything:\n\n1. Read the current journey state and scope through the `journey-status` skill (it\n owns the read; do not re-derive it here). Confirm the domain plan is present and\n approved, and check whether a `./wildo.saas.config.ts` already exists from an\n earlier run (refine it, do not re-author — see below).\n2. Read the **domain plan** (`domain-plan` family — the modules to register + their\n resource inventory) and the **vision brief** (`vision-brief` — the compliance and\n vision constraints that are the **primary** driver of capability selection).\n **Contextual** reads that sharpen the choices (they are *not* preconditions — read\n them if present, and note that the `business-model` may be absent, per the top-down\n phase-gate's optional posture):\n - the **market-snapshot** (`market-snapshot`) — its ICPs sharpen capability\n selection (a B2B / organization-scoped ICP → the `organizations` capability);\n - the **business-model** (`business-model`) — a paid plan → the billing capability\n (absent business model = no billing capability derived from it);\n - the **relationship drafts** inside the domain plan (the inter-resource relationships the build loop will\n wire — they can hint at which capabilities a module needs);\n - the **requirements** (functional/non-functional needs a capability may satisfy);\n - the **roadmap** (which modules are MVP-critical, so you enable what the first\n release needs and defer the rest).\n\n// TODO CLI COMMAND: wildo context journey-status\n// (read current journey scope + approved artifacts + any existing foundation config)\n// TODO CLI COMMAND: wildo context domain-plan\n// (read the modules to register + their per-module resource inventory)\n\nYou **read** `domain-plan` + `vision-brief` + `market-snapshot` + `business-model`\n+ `requirements` + `roadmap` (the domain plan carries its relationship drafts); you **write**\n`./wildo.saas.config.ts` and the materialized skeleton — app files, committed to git,\nwhich is where the record of what was decided lives.\n\n## Step 1 — Derive and enable the engine capabilities\n\nEngine capabilities are the framework surfaces the app turns on (organizations,\nbilling, notifications, audit trails, data residency, and so on). **Derive them from\nthe definition set — do not guess:**\n\n1. **Compliance/vision constraints → capabilities (the primary driver).** Walk the\n vision brief's constraints. A compliance constraint implies a capability (a privacy-law /\n data-residency constraint → the residency/audit capability; an external-assurance constraint →\n audit trails). A vision fact implies a capability (an organization-scoped product →\n `organizations`).\n2. **Market / business-model facts → capabilities (contextual sharpener).** A B2B or\n organization-scoped ICP in the `market-snapshot` → the `organizations` capability; a\n paid plan in the `business-model` → billing. Treat these as sharpeners over the\n primary compliance/vision derivation — and remember the `business-model` may be\n absent (then derive no billing capability from it).\n3. **Domain-plan needs → capabilities.** A module whose capability clearly needs a\n framework surface (a module that sends transactional email → notifications) turns\n on that capability.\n4. **Enable only what the definition set justifies.** Every enabled capability must\n trace to a compliance/vision constraint, a market/business-model fact, or a\n domain-plan module need. Do **not** enable a capability nothing asks for — that is\n speculative surface area (a coherence CONCERN — see the quality gate). Conversely,\n a compliance constraint that requires a capability you did **not** enable is a\n coverage GAP.\n\nThe `config-saas` skill carries the vocabulary for the `engineCapabilities` block of\n`./wildo.saas.config.ts`; read it to enable capabilities idiomatically. Record each\nenabled capability **and its justification** as a comment beside it in the config.\n\n## Step 2 — Declare the domain-plan's modules (register across runtimes after materialization)\n\n**Mind the ordering.** At *config-authoring* time (this step, before the skeleton\nexists) you can only **declare** the modules at the SaaS root. The shared / frontend /\nbackend module registry files do not exist until Step 4 materializes the skeleton, so\nthe cross-runtime **registration** happens *after* materialization — do not edit\nregistry files the skeleton has not yet created.\n\n1. **Declare each module at the SaaS root (now).** Add each domain-plan module to the\n `modules` composition in `./wildo.saas.config.ts` (the `config-saas` skill owns this\n surface). This declares the module's *existence* and is exactly what the skeleton\n materialization (Step 4) builds the per-module workspaces and registries from.\n2. **Register across the runtimes (after Step 4 materializes the skeleton).** Once the\n skeleton exists, each declared module is registered across the shared / frontend /\n backend registries so every runtime loads it — regenerated by `config sync` from the\n declared modules where the tooling supports it, or wired with the `module-registration`\n skill (distinct from `config-saas`, which only declares existence at the root). At\n foundation depth you register the module **shells** (the module exists and boots); the\n resources *inside* each module are authored by the build loop.\n3. **Declare every domain-plan module — and no more.** A module the domain plan named\n that is missing from the config is a GAP; a module in the config the domain plan did\n not name is an unjustified-module CONCERN. Record the declared modules (each traced\n to its domain-plan module) as a comment beside it in the config.\n\n**Do not author the resources here.** The domain plan's per-module resource inventory\ntells you *what* resources each module will own, but authoring their schemas, fields,\nand config is the **build loop's** job. If you catch yourself writing a resource\nschema, stop: that is out of this playbook's depth.\n\n## Step 3 — Select the providers\n\nEnabled capabilities that reach an external service need a **provider** (billing → a\npayment provider; notifications/email → an email provider; file storage → an object\nstore). For each such capability, select and wire the provider scope +\n`providerConfigurations` in `./wildo.saas.config.ts` (the `config-saas` skill covers\nthe provider surfaces):\n\n- **Every provider matches a declared capability.** A provider wired for no enabled\n capability is a CONCERN; an enabled capability that needs a provider with none\n selected is a GAP.\n- **Do not seed secrets here.** Provider *selection* (which provider, which scope) is\n foundation; the per-environment secret material is seeded by the deterministic\n bring-up / environment step, not authored inline. Record the selected providers\n (each matched to its capability) as a comment beside it in the config.\n\n## Step 4 — The deterministic bring-up sequence (partially deferred)\n\nWith the config authored, run the **deterministic bring-up** in prerequisite order.\nThe skeleton template and app-knowledge installer remain deferred; do not invent\nthem. Headless `wildo setup` and `wildo local init` are registered and should be\nexecuted after the app structure exists.\n\n1. **Materialize the app skeleton** — create the `./frontend/`, `./shared-lib/`,\n `./backend-api/`, `./specifications/`, and `./infrastructure/` workspaces + the\n module registries from the empty-app template, so the declared modules have a real\n workspace.\n\n // TODO CLI COMMAND: wildo materialize skeleton\n // (scaffold app/ shared-lib/ backend-api/ specifications/ + module registries — greenfield tooling, deferred)\n\n2. **Install app-knowledge** — drop the compiled skills / rules / agents into the\n project's agent-config folders so the build loop's coding agent reads them\n naturally with cwd at the app root.\n\n // TODO CLI COMMAND: wildo install app-knowledge\n // (install compiled skills/rules/agents into the app's .claude/ — greenfield tooling, deferred)\n\n3. **Run setup** — configure the app from the authored `./wildo.saas.config.ts` and\n the `./infrastructure/` env configs (the `infra-environment-config` skill owns the\n typed infra env files; the `local-environment-bootstrap` skill owns the `wildo`\n lifecycle). Headless setup is registered and fail-closed on the administrator seed\n environment variables; it mints the environment generation without placeholders.\n\n ```bash\n wildo setup --non-interactive\n ```\n\n4. **Initialize and verify the project** — run the registered convergence journey.\n It regenerates artifacts, starts and readiness-gates backing services, reconciles\n platform Mongo state and credentials, starts native platform services, registers the\n app once, emits all runtime projections, and executes a signed managed-config read.\n\n ```bash\n wildo local init\n ```\n\nReport the status of each bring-up step to the creator in your result. Skeleton\nmaterialization and app-knowledge installation remain deferred; setup and local\ninitialization are executable once those app files exist and must be recorded from their\nreal exit/postcondition result rather than marked complete from intent.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not disable a capability, drop a module,\n or re-select a provider that is already correct. Only enable a newly-justified\n capability, register a newly-added domain-plan module, or correct a provider where\n the definition set genuinely changed.\n- **Reuse existing module ids and provider scopes.** A module already registered keeps\n its id; a provider already selected keeps its scope — never mint a second one for the\n same module/capability.\n- **Follow the definition set.** If the domain plan added a module or the vision brief\n added a compliance constraint since the last run, reflect it (register the module,\n enable the capability) — do not re-derive the whole configuration from scratch. The\n delta is visible in `git diff` on the config, which is the record.\n\n## Quality gate — `foundation-configured-coherently` (declarative at scaffold depth)\n\nThe foundation is checked against the `foundation-configured-coherently` **reviewer\nchecklist** (see the end of this method): five invariants (capability derivation, module registration, provider coverage,\nsequence order, and foundation-depth boundary discipline), each marked PASS / CONCERN /\nGAP.\n\nThis checklist is **declarative**: no runtime executes it (rubric-only judge gates were retired at the flexible-intelligence hard cut — judgment runs only through a compiled Evaluation Treatment, and this playbook has none yet), so it ships as the **creator's review checklist** — nothing runs it automatically. The **trust floor** for accepting the foundation today is the\ncreator's `approve_result` review of the produced config and the bring-up result. There is\nintentionally **no deterministic gate**: config validation is a `wildo` CLI concern\n(`config sync` / validate), not a validator in the journey-artifact schemaRef\nvocabulary. When the greenfield tooling lands, the non-bypassable floor still\nhard-gates the real destructive / off-machine infra bring-up regardless of this gate.\n\n## Scaffold-depth and tooling-deferral boundary\n\nKeep this playbook at scaffold depth **and** honour the tooling deferral. Explicitly\n**out of scope here**:\n\n- **The remaining greenfield CLI tooling itself.** The skeleton-materialization\n template and app-knowledge installer do **not** exist yet and are a later\n greenfield-enablement phase. Their two `// TODO CLI COMMAND:` placeholders must not\n be invented. `wildo setup --non-interactive` and `wildo local init` do exist and are\n the registered lifecycle once the app structure is present.\n- **Resource / field / schema authoring.** The config declares modules as shells and\n enables capabilities; it does **not** author resource schemas, fields, enums,\n decorators, ui-behavior, views, or navigation. That is the build loop. If you catch\n yourself writing a resource, stop.\n- **Re-introducing a foundation artifact.** The `foundation-manifest` family was\n retired on 2026-08-25 with the app-creation verification/digest aspect. Do **NOT**\n reshape `_core` to bring it back: the config file and its git history already carry\n every decision it recorded.\n- **Deep capability / provider modelling.** A defended capability-selection model\n (per-compliance-regime obligation → capability mapping, provider cost/feature\n matrices, multi-provider fallback) is a later depth pass. You derive capabilities\n from the definition set with the v1 heuristic above — not a solved obligation graph.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at scaffold\ndepth — depth (and the greenfield tooling) are dedicated later passes done once,\nholistically.\n\n## What you emit\n\n- The authored **`./wildo.saas.config.ts`** (an app file) — the enabled engine\n capabilities, the registered modules, and the selected providers — plus the\n registered module shells across the runtimes and (when the tooling lands) the\n brought-up skeleton.\n- The **bring-up result** reported to the creator: the status of each step, taken from\n its real exit/postcondition rather than from intent. This is a report, not a stored\n artifact — nothing reads it back.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's foundation, which the bottom-up build loop then fills in\nwith authored resources, operations, UX, and integrations.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and scope,\n and confirm the approved domain plan + vision brief are in place to configure from.\n- `.claude/skills/config-saas/SKILL.md` — the `./wildo.saas.config.ts` authoring\n surface: `engineCapabilities`, `modules`, provider scopes, and `providerConfigurations`.\n- `.claude/skills/module-registration/SKILL.md` — register each domain-plan module\n across the shared / frontend / backend registries so the skeleton boots with it\n (distinct from `config-saas`, which only declares module existence at the root).\n- `.claude/skills/infra-environment-config/SKILL.md` — the typed `./infrastructure/`\n environment configs (backing services, public domain, service auth) the bring-up needs.\n- `.claude/skills/local-environment-bootstrap/SKILL.md` — the `wildo` lifecycle\n (`setup`, `local init`, `local reinit`, `local dev`) for deterministic initialization,\n repair, clean-room recovery, and runtime start.\n\n## Reviewer checklist — `foundation-configured-coherently`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim, minus the retired runner's closing sentence:\n\nJudge whether the authored foundation (the ./wildo.saas.config.ts composition + the materialized skeleton) is a coherent realisation of the approved domain plan and the top-down definition set. Assess five invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) CAPABILITY DERIVATION — every enabled engine capability traces to a compliance/vision, business-model, market, or domain-plan need; unjustified capabilities are a CONCERN and missing required capabilities are a GAP. (2) MODULE REGISTRATION — every approved domain-plan module is declared and registered across runtimes; missing modules are a GAP and extra modules are a CONCERN. (3) PROVIDER COVERAGE — every provider serves a declared capability and every provider-backed capability has a provider. (4) SEQUENCE ORDER AND PROOF — author config → materialize skeleton → install app-knowledge → wildo setup --non-interactive → wildo local init. Treat setup intent, container health, or an initialization marker as insufficient: local init must reach its signed managed-config-read postcondition. (5) BOUNDARY DISCIPLINE — stay at foundation depth and do not author resources, fields, ui-behavior, views, or navigation. Do not invent the still-deferred skeleton/app-knowledge installer commands; headless setup and local init are registered and should be executed once the structure exists. This reviewer checklist is declarative; creator approval is the trust floor.\n",
|
|
51
|
+
"skillRefs": [
|
|
52
|
+
"journey-status",
|
|
53
|
+
"config-saas",
|
|
54
|
+
"module-registration",
|
|
55
|
+
"infra-environment-config",
|
|
56
|
+
"local-environment-bootstrap"
|
|
57
|
+
],
|
|
58
|
+
"elicitation": {
|
|
59
|
+
"questions": [
|
|
60
|
+
{
|
|
61
|
+
"ref": "primary-scope",
|
|
62
|
+
"question": "What is the application's tenancy model? Answer `organizations` when users collaborate inside shared workspaces/teams (this enables the ORGANIZATIONS engine capability), or `users` when every user's data is their own.",
|
|
63
|
+
"kind": "choice",
|
|
64
|
+
"options": [
|
|
65
|
+
"organizations",
|
|
66
|
+
"users"
|
|
67
|
+
]
|
|
68
|
+
}
|
|
69
|
+
]
|
|
70
|
+
},
|
|
71
|
+
"contextSources": [],
|
|
72
|
+
"suspendsForClarification": false
|
|
73
|
+
},
|
|
74
|
+
"approval": "approve_result",
|
|
75
|
+
"budget": {
|
|
76
|
+
"maxRuns": 3
|
|
77
|
+
},
|
|
78
|
+
"onFailure": "keep_and_flag"
|
|
79
|
+
}
|
|
@@ -0,0 +1,185 @@
|
|
|
1
|
+
# Placement Plan — Where Each Thing Belongs in the Shell, and Why
|
|
2
|
+
|
|
3
|
+
### Target Application Framing
|
|
4
|
+
|
|
5
|
+
This knowledge is for configuring behavior in the target application.
|
|
6
|
+
Wildo is the framework surface being used, not the product being built.
|
|
7
|
+
|
|
8
|
+
Read and apply these patterns from the application-developer point of view:
|
|
9
|
+
|
|
10
|
+
- how the application should configure the relevant app-level file
|
|
11
|
+
- how the application should use framework-provided factories, enums, and helpers
|
|
12
|
+
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
> **This is a v1 methodology.** The criteria below are deliberately explicit so
|
|
16
|
+
> they can be tuned against real runs. What is NOT provisional is the shape of the
|
|
17
|
+
> output: a decision per subject, on a named surface, with a rationale.
|
|
18
|
+
|
|
19
|
+
## Where you are in the journey
|
|
20
|
+
|
|
21
|
+
You run in the **bottom-up phase**, after the **domain plan** exists and **before**
|
|
22
|
+
the build is decomposed. By now the application knows what its modules and resources
|
|
23
|
+
ARE; what nobody has decided is **where any of it appears**.
|
|
24
|
+
|
|
25
|
+
That order matters and was corrected during authoring. Placing things *after* the
|
|
26
|
+
build plan reads natural — you would know every task — but `bottom_up.build-decompose`
|
|
27
|
+
is what PRODUCES the build plan and it consumes this one to emit the placement tasks.
|
|
28
|
+
Requiring its output would be a cycle. It is also the better order on its own merits:
|
|
29
|
+
placement is a design decision that should INFORM the decomposition, not trail it. You
|
|
30
|
+
do not need the task graph to know that a `deals` resource will have a list.
|
|
31
|
+
|
|
32
|
+
That question used to have no owner. The framework shipped a placed settings rail,
|
|
33
|
+
so an application could not add, remove, reorder or rename a section without the
|
|
34
|
+
framework agreeing — and the application's own config file did not tell you what a
|
|
35
|
+
user would see. Placement is now the application's, which means somebody has to
|
|
36
|
+
decide it. That is this playbook.
|
|
37
|
+
|
|
38
|
+
## What this playbook does
|
|
39
|
+
|
|
40
|
+
You produce a **placement plan**: for every subject, one decision per surface.
|
|
41
|
+
|
|
42
|
+
A **subject** is one of three things:
|
|
43
|
+
|
|
44
|
+
- an **engine settings destination**, named by its ref from the engine catalog
|
|
45
|
+
(`profile`, `security`, `billing`, `sso`, …) — the engine owns what each MEANS
|
|
46
|
+
(its target, its required roles, its entitlement); it owns nothing about where it
|
|
47
|
+
goes;
|
|
48
|
+
- a **resource operation** — a resource's LIST, its READ, a custom verb;
|
|
49
|
+
- an **application view** — composite, chart, execution, full-custom.
|
|
50
|
+
|
|
51
|
+
A **surface** is one of four:
|
|
52
|
+
|
|
53
|
+
| surface | grouped by | authoring home |
|
|
54
|
+
|---|---|---|
|
|
55
|
+
| `SETTINGS_HUB` | a rail **category** | `frontend/src/config/settings-hub.config.ts` |
|
|
56
|
+
| `SIDEBAR` | a sidebar **section** | `appShellConfig[SIDEBAR].contentSections` |
|
|
57
|
+
| `USER_MENU` | flat | the user dropdown's settings entries |
|
|
58
|
+
| `COMMAND_MENU` | flat | the command palette |
|
|
59
|
+
|
|
60
|
+
A subject may legitimately be placed on **several** surfaces — billing is a settings
|
|
61
|
+
rail section AND answers to the command palette. One decision per (subject, surface);
|
|
62
|
+
two placements of one subject on ONE surface is a contradiction and the validator
|
|
63
|
+
refuses it.
|
|
64
|
+
|
|
65
|
+
## Decline explicitly; never omit
|
|
66
|
+
|
|
67
|
+
Every decision is `PLACED` or `DECLINED`, and **both require a rationale**.
|
|
68
|
+
|
|
69
|
+
This is the rule most worth getting right. A subject recorded as `DECLINED` is a
|
|
70
|
+
decision a later reader can disagree with. A subject simply missing from the plan is
|
|
71
|
+
a **coverage gap** — nobody looked. If those two were the same thing, "we considered
|
|
72
|
+
the audit log and this app has no compliance audience" would be indistinguishable
|
|
73
|
+
from forgetting the audit log existed.
|
|
74
|
+
|
|
75
|
+
So: if a destination should not appear anywhere in this application, say so, and say
|
|
76
|
+
why.
|
|
77
|
+
|
|
78
|
+
## The criteria, in the order you apply them
|
|
79
|
+
|
|
80
|
+
1. **Scope correctness.** A thing that acts on the whole organization does not sit
|
|
81
|
+
among a person's own preferences, and the reverse. This is first because it is
|
|
82
|
+
the only criterion that is objectively *wrong* rather than debatable.
|
|
83
|
+
2. **Findability.** Would the user who wants this look here FIRST — unprompted?
|
|
84
|
+
Not "would they accept it once shown". Those are different tests and only the
|
|
85
|
+
first one predicts behaviour.
|
|
86
|
+
3. **Grouping coherence.** Everything in a group answers one question a user
|
|
87
|
+
actually asks. A group that needs "and other things" in its name is two groups.
|
|
88
|
+
4. **Convention fit.** Users arrive with expectations already formed by comparable
|
|
89
|
+
products. A novel arrangement must EARN the cost of surprising them.
|
|
90
|
+
5. **Depth discipline.** One more level of nesting must buy more than it costs. A
|
|
91
|
+
section reachable only after three guesses is not placed, it is hidden.
|
|
92
|
+
|
|
93
|
+
Reject placements justified by implementation convenience ("it renders there
|
|
94
|
+
already"), by the shape of the data model rather than the user's task, or by symmetry
|
|
95
|
+
for its own sake. Surfacing something everywhere is a **cost**, not thoroughness.
|
|
96
|
+
|
|
97
|
+
## Groups carry a purpose, and the purpose is load-bearing
|
|
98
|
+
|
|
99
|
+
When you declare a group, state its `purpose` in product terms. It is not decoration:
|
|
100
|
+
it is what grounds the generated `settings_hub.categories.<ref>.label` and
|
|
101
|
+
`sidebar_sections.<ref>.title` labels in authored intent. Without it a model invents
|
|
102
|
+
filler from the ref alone — which is exactly how a sidebar section came to be
|
|
103
|
+
described as "various tools and utilities".
|
|
104
|
+
|
|
105
|
+
## What you do NOT do
|
|
106
|
+
|
|
107
|
+
- **You do not author configuration.** Turning a decision into
|
|
108
|
+
`settings-hub.config.ts` or `app-shell.config.ts` is a coding task the build lane
|
|
109
|
+
dispatches through the `settings-placement-authoring` skill. If you catch yourself
|
|
110
|
+
writing a config key, a file path or a label string, stop.
|
|
111
|
+
- **You do not invent destination refs.** They come from the engine catalog and the
|
|
112
|
+
workspace, read as workspace truth. A ref you invented resolves to nothing and the
|
|
113
|
+
validator refuses it as an unknown subject.
|
|
114
|
+
- **You do not decide what a destination MEANS.** Its target, roles and entitlement
|
|
115
|
+
are the engine's. You decide only where it sits.
|
|
116
|
+
- **You do not re-open the build plan.** What is being built is settled.
|
|
117
|
+
|
|
118
|
+
## Verification
|
|
119
|
+
|
|
120
|
+
- Every subject the workspace offers is either PLACED or DECLINED — nothing omitted.
|
|
121
|
+
- No subject placed twice on one surface.
|
|
122
|
+
- Every grouped placement names a group this plan declares, for that same surface.
|
|
123
|
+
- Every group has something in it.
|
|
124
|
+
- Every decision, both arms, carries a rationale that would satisfy a reader who
|
|
125
|
+
disagrees with it.
|
|
126
|
+
|
|
127
|
+
## WHO decides — a panel, not you alone and not the creator
|
|
128
|
+
|
|
129
|
+
**The creator does not choose placement.** This playbook convenes an expert panel and
|
|
130
|
+
takes its winner.
|
|
131
|
+
|
|
132
|
+
Concretely, on every run: three candidate arrangements are generated independently
|
|
133
|
+
against this brief, each schema-valid before anyone sees it and each told to take a
|
|
134
|
+
genuinely different position; the **information-architect** derives the rubric (it
|
|
135
|
+
owns the domain); it and the **design-system-guardian** review every candidate; the
|
|
136
|
+
guardian coordinates, shortlists, and synthesises a winner. What lands is that winner.
|
|
137
|
+
|
|
138
|
+
Two consequences for how you write:
|
|
139
|
+
|
|
140
|
+
- **Take a position and commit to it.** You are one candidate among three, and the
|
|
141
|
+
panel cannot compare three hedged arrangements. State what your arrangement makes
|
|
142
|
+
WORSE — an arrangement with no cost has not been thought about, and the reviewers
|
|
143
|
+
are instructed to notice.
|
|
144
|
+
- **The rationale on each decision is the durable part.** It is what a creator asking
|
|
145
|
+
"why is Billing under Organization?" reads, and it is the only trace of the argument
|
|
146
|
+
once the winner has landed.
|
|
147
|
+
|
|
148
|
+
**Fail-closed on charters.** Every panel role needs a committed charter, and the
|
|
149
|
+
companion indexes agents at startup — a charter accepted after boot has no agent until
|
|
150
|
+
a restart, and the error says exactly that. The run does NOT quietly degrade to a
|
|
151
|
+
single generation: an artifact carrying a panel's authority over a decision no panel
|
|
152
|
+
saw is the worst outcome available here, so fewer than two usable candidates returns
|
|
153
|
+
to the ordinary retry instead.
|
|
154
|
+
|
|
155
|
+
## And when the placement is wrong
|
|
156
|
+
|
|
157
|
+
Two different things can change, and conflating them is how a plan starts lying.
|
|
158
|
+
|
|
159
|
+
**The config file** — `settings-hub.config.ts`, `app-shell.config.ts` — is what actually
|
|
160
|
+
renders. A creator who disagrees edits it directly. That works today, needs no companion,
|
|
161
|
+
and is a git commit, which is the accepted state.
|
|
162
|
+
|
|
163
|
+
**The plan** is the decision record, and it is what a later reader consults to ask why.
|
|
164
|
+
It can be changed two ways:
|
|
165
|
+
|
|
166
|
+
- **Re-run this playbook.** The panel deliberates again and the landing REPLACES the
|
|
167
|
+
existing file. Nothing refuses it; that is the design.
|
|
168
|
+
- **Edit the landed plan.** It is an application-owned source like any other.
|
|
169
|
+
|
|
170
|
+
Either way, a decision that no longer reflects the panel must say so. Set its `origin`
|
|
171
|
+
to `REVISED` and record what the panel had decided in `supersedes.rationale`. Both are
|
|
172
|
+
required together — the schema refuses a `REVISED` decision with nothing superseded, and
|
|
173
|
+
refuses a `DELIBERATED` one that supersedes something, because no panel run produces
|
|
174
|
+
either shape.
|
|
175
|
+
|
|
176
|
+
**Why the artifact carries this when git already records the change.** Git knows who
|
|
177
|
+
changed the line, when, and with what message, and that is not being duplicated here. What
|
|
178
|
+
git cannot tell someone READING the file — in an editor, asking "why is Billing under
|
|
179
|
+
Account?" — is that this particular decision is no longer the panel's. Without it, the
|
|
180
|
+
`rationale` field goes on asserting panel reasoning for a decision the panel never took,
|
|
181
|
+
and there is no way to notice.
|
|
182
|
+
|
|
183
|
+
Do not paraphrase the panel's rationale into the new one. A `supersedes.rationale` that
|
|
184
|
+
repeats the decision's own text word for word satisfies the schema and tells a reader
|
|
185
|
+
nothing; the validator reports it as an authoring warning.
|