@wildo-ai/framework-knowledge 1.1.2 → 1.1.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +351 -18
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts +1 -2
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/index.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +3 -4
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +4 -4
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +3 -4
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +4 -4
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +1 -2
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +1 -2
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +2 -3
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +3 -3
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -2
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -2
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +0 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +0 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +0 -2
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +2 -2
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +0 -2
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +9 -4
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/manifest.json +8 -9
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +13 -70
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +11 -19
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +5 -88
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +15 -8
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +4 -5
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +15 -8
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +4 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -7
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +22 -49
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +8 -17
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +15 -780
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +11 -11
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +20 -141
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +15 -10
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +3 -2
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +16 -11
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +14 -6
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +4 -2
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +16 -7
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +4 -21
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +65 -16
- package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-analysis/method.md +165 -51
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +43 -23
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +4 -8
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +7 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +7 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +15 -7
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +3 -3
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +16 -11
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +4 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +15 -7
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +16 -11
- package/dist/knowledge/references/build-plan.task-graph.config.md +1 -45
- package/dist/knowledge/references/companion.technical-doc.service.md +2 -102
- package/dist/knowledge/references/example.config.app-shell.full.md +5 -0
- package/dist/knowledge/references/example.module.companion-exports.full.md +0 -1
- package/dist/knowledge/references/example.provider.backend-module-shape.md +0 -7
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +1 -0
- package/dist/knowledge/references/platform.config.saas.md +0 -51
- package/dist/knowledge/references/presets.models.surface-policy.md +10 -19
- package/dist/knowledge/references/saas.external-data.admin-endpoints.md +48 -0
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +11 -31
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +1 -0
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +0 -45
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +0 -198
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -164
- package/dist/knowledge/references/saas.models.engine-capabilities.md +6 -26
- package/dist/knowledge/references/saas.models.http-api-binding.md +29 -3
- package/dist/knowledge/references/saas.models.provider-capabilities.md +3 -4
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +2 -4
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +0 -2
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +0 -14
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +31 -11
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +2 -32
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +6 -29
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +0 -56
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +0 -22
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +0 -26
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +0 -45
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +1 -7
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +5 -31
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +1 -44
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +0 -3
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +0 -1
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +0 -15
- package/dist/knowledge/registries/assurance-authority-bases.json +2 -3
- package/dist/knowledge/registries/framework-topics.json +11 -146
- package/dist/knowledge/registries/playbooks.json +18 -154
- package/dist/knowledge/registries/source-tags.json +630 -883
- package/dist/knowledge/skills/INDEX.md +3 -4
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +1 -2
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -16
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +9 -31
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +74 -252
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +8 -26
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +53 -97
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +21 -84
- package/dist/knowledge/skills/config-app-shell/SKILL.md +9 -31
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +12 -31
- package/dist/knowledge/skills/config-design-system/SKILL.md +1 -23
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +10 -19
- package/dist/knowledge/skills/config-navigation/SKILL.md +2 -75
- package/dist/knowledge/skills/config-saas/SKILL.md +2 -19
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +9 -30
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +0 -51
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +0 -7
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +1 -2
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +3 -4
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +0 -56
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +0 -56
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +0 -1
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +0 -56
- package/dist/knowledge/skills/resource-add-field/SKILL.md +3 -3
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +0 -213
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +1 -2
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +2 -4
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +0 -15
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +2 -224
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +0 -198
- package/dist/knowledge/skills/resource-external-data/SKILL.md +2 -0
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +29 -3
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +70 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +1 -22
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +8 -28
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +0 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +0 -17
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +0 -46
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +0 -15
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +0 -26
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +1 -7
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +0 -198
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +1 -44
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +0 -3
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +0 -1
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +0 -56
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +5 -31
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +0 -22
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +0 -45
- package/dist/knowledge/topic-index.json +220 -725
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +0 -1
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +0 -51
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +0 -43
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +0 -185
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +0 -64
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +0 -41
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +0 -100
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +0 -117
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +0 -86
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +0 -61
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +0 -41
- package/dist/knowledge/playbooks/top_down.compliance-research/method.md +0 -76
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +0 -42
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +0 -56
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -42
- package/dist/knowledge/playbooks/top_down.market-research/method.md +0 -68
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -44
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +0 -239
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +0 -67
- package/dist/knowledge/references/placement-plan.config.md +0 -330
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +0 -34
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +0 -45
- package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +0 -65
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +0 -58
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +0 -118
- package/dist/knowledge/references/saas.models.file-upload-grant.md +0 -179
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +0 -124
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +0 -99
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +0 -127
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +0 -42
- package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +0 -29
- package/dist/knowledge/references/zod.decorators.data-categories.md +0 -197
- package/dist/knowledge/rules/resource-schema-awareness.md +0 -77
- package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +0 -124
- package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +0 -47
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +0 -98
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +0 -54
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +0 -232
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +0 -149
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +0 -114
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +0 -133
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +0 -111
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +0 -622
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +0 -192
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +0 -245
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +0 -134
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +0 -65
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +0 -127
- /package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/structured-artifact-action.json +0 -0
|
@@ -18,7 +18,7 @@ Read and apply these patterns from the application-developer point of view:
|
|
|
18
18
|
> the provider-selection rubric are deliberately explicit so they can be tuned
|
|
19
19
|
> against real runs. The deterministic steps that *materialize the skeleton* and
|
|
20
20
|
> *install app-knowledge* are a later greenfield-enablement phase and are **not
|
|
21
|
-
> built**. Those two steps are authored as
|
|
21
|
+
> built**. Those two steps are authored as `// TODO CLI COMMAND:` placeholders;
|
|
22
22
|
> headless setup and verified local initialization are registered commands. **This playbook is the
|
|
23
23
|
> METHOD — the description of the foundation sequence — not a runnable
|
|
24
24
|
> foundation.** If you find yourself building or wiring the greenfield CLI
|
|
@@ -48,19 +48,16 @@ into the *configured application skeleton the build loop then fills in*.
|
|
|
48
48
|
You are the **foundation engineer**. This playbook reads the approved domain plan
|
|
49
49
|
and the vision brief, then configures and brings up the application skeleton so the
|
|
50
50
|
build loop has a real workspace to author into. You perform a **mixed sequence**
|
|
51
|
-
(the runner sequences the tiers per this guidance):
|
|
51
|
+
(hence the `composite` executor — the runner sequences the tiers per this guidance):
|
|
52
52
|
a config/skeleton **authoring** pass, then a **deterministic bring-up** pass. The
|
|
53
53
|
work, in order:
|
|
54
54
|
|
|
55
55
|
1. **Derive the engine capabilities** from the compliance/vision constraints (and
|
|
56
56
|
the market/business-model facts) and enable them in `./wildo.saas.config.ts`.
|
|
57
57
|
2. **Declare the domain-plan's modules** at the SaaS root (they are registered across
|
|
58
|
-
the runtimes after Step
|
|
58
|
+
the runtimes after Step 4 materializes the skeleton, so it boots with them).
|
|
59
59
|
3. **Select the providers** the enabled capabilities need.
|
|
60
|
-
4. **
|
|
61
|
-
the jurisdictions, from the elicitation answers, into `./wildo.saas.config.ts`.
|
|
62
|
-
See `config-saas` and its `references/compliance-declarations.md`.
|
|
63
|
-
5. **Run the deterministic bring-up** — materialize the skeleton, install
|
|
60
|
+
4. **Run the deterministic bring-up** — materialize the skeleton, install
|
|
64
61
|
app-knowledge, `wildo setup --non-interactive`, then `wildo local init`.
|
|
65
62
|
|
|
66
63
|
You emit **no artifact**. The deliverable is the app itself: `./wildo.saas.config.ts`,
|
|
@@ -68,6 +65,10 @@ the materialized skeleton, and a verified local initialization. Record *why* eac
|
|
|
68
65
|
capability, module and provider was chosen in the config's own comments, where the
|
|
69
66
|
next reader of that file will find it.
|
|
70
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
|
+
|
|
71
72
|
This is a **foundation pass**. You enable capabilities, declare modules as shells,
|
|
72
73
|
select providers, and bring the skeleton up. You do **not** author resource schemas,
|
|
73
74
|
fields, ui-behavior, views, or navigation — that is the **build loop's** job,
|
|
@@ -98,9 +99,10 @@ anything:
|
|
|
98
99
|
- the **roadmap** (which modules are MVP-critical, so you enable what the first
|
|
99
100
|
release needs and defer the rest).
|
|
100
101
|
|
|
101
|
-
//
|
|
102
|
-
//
|
|
103
|
-
//
|
|
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)
|
|
104
106
|
|
|
105
107
|
You **read** `domain-plan` + `vision-brief` + `market-snapshot` + `business-model`
|
|
106
108
|
+ `requirements` + `roadmap` (the domain plan carries its relationship drafts); you **write**
|
|
@@ -141,15 +143,15 @@ enabled capability **and its justification** as a comment beside it in the confi
|
|
|
141
143
|
|
|
142
144
|
**Mind the ordering.** At *config-authoring* time (this step, before the skeleton
|
|
143
145
|
exists) you can only **declare** the modules at the SaaS root. The shared / frontend /
|
|
144
|
-
backend module registry files do not exist until Step
|
|
146
|
+
backend module registry files do not exist until Step 4 materializes the skeleton, so
|
|
145
147
|
the cross-runtime **registration** happens *after* materialization — do not edit
|
|
146
148
|
registry files the skeleton has not yet created.
|
|
147
149
|
|
|
148
150
|
1. **Declare each module at the SaaS root (now).** Add each domain-plan module to the
|
|
149
151
|
`modules` composition in `./wildo.saas.config.ts` (the `config-saas` skill owns this
|
|
150
152
|
surface). This declares the module's *existence* and is exactly what the skeleton
|
|
151
|
-
materialization (Step
|
|
152
|
-
2. **Register across the runtimes (after Step
|
|
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
|
|
153
155
|
skeleton exists, each declared module is registered across the shared / frontend /
|
|
154
156
|
backend registries so every runtime loads it — regenerated by `config sync` from the
|
|
155
157
|
declared modules where the tooling supports it, or wired with the `module-registration`
|
|
@@ -182,36 +184,7 @@ the provider surfaces):
|
|
|
182
184
|
bring-up / environment step, not authored inline. Record the selected providers
|
|
183
185
|
(each matched to its capability) as a comment beside it in the config.
|
|
184
186
|
|
|
185
|
-
## Step 4 —
|
|
186
|
-
|
|
187
|
-
The creator answered `operating-entity` and `operating-jurisdictions`. Write those answers
|
|
188
|
-
into `operatorComplianceIdentity` and `operatingJurisdictions`, and **nothing else**.
|
|
189
|
-
|
|
190
|
-
- **Record the PART you were given.** Every part of `operatorComplianceIdentity` is
|
|
191
|
-
independently declarable, so a creator who named the company and not its lawful bases
|
|
192
|
-
gets `legalEntityName` and `registeredAddress` written and the rest left absent. A
|
|
193
|
-
missing part is reported downstream as outstanding; it does not block anything here.
|
|
194
|
-
- **NEVER invent one.** Not a company name, not an address, not a privacy contact, and
|
|
195
|
-
above all not a lawful basis — that is a legal determination, and `CONSENT` in
|
|
196
|
-
particular would tell a person their data rests on an agreement they could withdraw.
|
|
197
|
-
A produced privacy notice quotes these as fact. An absent declaration is reported as an
|
|
198
|
-
open gap a reader can see; an invented one is published.
|
|
199
|
-
- **Omit the key entirely when you were told nothing.** Absence means "nobody answered",
|
|
200
|
-
which is the honest state and the one every consumer already renders correctly. An
|
|
201
|
-
empty object is refused by the schema precisely because it would satisfy the field while
|
|
202
|
-
disclosing nothing.
|
|
203
|
-
- **A jurisdiction needs its `basis`.** "eu" alone does not say whether you are established
|
|
204
|
-
there, sell there, or hold data about people there, and those imply different obligations.
|
|
205
|
-
If the creator gave a place without a reason, record neither — ask, or leave it out.
|
|
206
|
-
|
|
207
|
-
This step CANNOT fail the run. If the creator answered nothing, write nothing and continue:
|
|
208
|
-
the application boots, and the gap is visible where it matters rather than here.
|
|
209
|
-
|
|
210
|
-
(A `foundation-manifest` artifact was declared here until 2026-08-25 and is now
|
|
211
|
-
retired with the app-creation verification/digest aspect. It was a bookkeeping record
|
|
212
|
-
of decisions the config already carries — deleting it costs no fact about the app.)
|
|
213
|
-
|
|
214
|
-
## Step 5 — The deterministic bring-up sequence (partially deferred)
|
|
187
|
+
## Step 4 — The deterministic bring-up sequence (partially deferred)
|
|
215
188
|
|
|
216
189
|
With the config authored, run the **deterministic bring-up** in prerequisite order.
|
|
217
190
|
The skeleton template and app-knowledge installer remain deferred; do not invent
|
|
@@ -223,15 +196,15 @@ executed after the app structure exists.
|
|
|
223
196
|
module registries from the empty-app template, so the declared modules have a real
|
|
224
197
|
workspace.
|
|
225
198
|
|
|
226
|
-
//
|
|
227
|
-
//
|
|
199
|
+
// TODO CLI COMMAND: wildo materialize skeleton
|
|
200
|
+
// (scaffold app/ shared-lib/ backend-api/ specifications/ + module registries — greenfield tooling, deferred)
|
|
228
201
|
|
|
229
202
|
2. **Install app-knowledge** — drop the compiled skills / rules / agents into the
|
|
230
203
|
project's agent-config folders so the build loop's coding agent reads them
|
|
231
204
|
naturally with cwd at the app root.
|
|
232
205
|
|
|
233
|
-
//
|
|
234
|
-
//
|
|
206
|
+
// TODO CLI COMMAND: wildo install app-knowledge
|
|
207
|
+
// (install compiled skills/rules/agents into the app's .claude/ — greenfield tooling, deferred)
|
|
235
208
|
|
|
236
209
|
3. **Run setup** — configure the app from the authored `./wildo.saas.config.ts` and
|
|
237
210
|
the `./infrastructure/` env configs (the `infra-environment-config` skill owns the
|
|
@@ -292,8 +265,8 @@ Keep this playbook at scaffold depth **and** honour the tooling deferral. Explic
|
|
|
292
265
|
|
|
293
266
|
- **The remaining greenfield CLI tooling itself.** The skeleton-materialization
|
|
294
267
|
template and app-knowledge installer do **not** exist yet and are a later
|
|
295
|
-
greenfield-enablement phase. Their two
|
|
296
|
-
|
|
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
|
|
297
270
|
the registered lifecycle once the app structure is present.
|
|
298
271
|
- **Resource / field / schema authoring.** The config declares modules as shells and
|
|
299
272
|
enables capabilities; it does **not** author resource schemas, fields, enums,
|
|
@@ -7,6 +7,10 @@
|
|
|
7
7
|
"configure_application_foundation"
|
|
8
8
|
],
|
|
9
9
|
"preconditions": [
|
|
10
|
+
{
|
|
11
|
+
"kind": "phase_is",
|
|
12
|
+
"phase": "bottom_up"
|
|
13
|
+
},
|
|
10
14
|
{
|
|
11
15
|
"kind": "artifact_exists",
|
|
12
16
|
"selector": {
|
|
@@ -41,9 +45,8 @@
|
|
|
41
45
|
}
|
|
42
46
|
],
|
|
43
47
|
"outputs": [],
|
|
44
|
-
"stepOutputs": [],
|
|
45
48
|
"method": {
|
|
46
|
-
"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 explicit deferred-tooling notes;\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(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 5 materializes the skeleton, so it boots with them).\n3. **Select the providers** the enabled capabilities need.\n4. **Record the compliance declarations you were given** — the operating entity and\n the jurisdictions, from the elicitation answers, into `./wildo.saas.config.ts`.\n See `config-saas` and its `references/compliance-declarations.md`.\n5. **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\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// Operator affordances (the executor itself is handed the domain-plan VALUE directly):\n// `wildo context journey` — current phase, the eligibility board, runs in flight\n// `wildo context info specification-artifacts` — per-family landed state and rendered content\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 5 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 5) builds the per-module workspaces and registries from.\n2. **Register across the runtimes (after Step 5 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 — Record the compliance declarations (only what you were told)\n\nThe creator answered `operating-entity` and `operating-jurisdictions`. Write those answers\ninto `operatorComplianceIdentity` and `operatingJurisdictions`, and **nothing else**.\n\n- **Record the PART you were given.** Every part of `operatorComplianceIdentity` is\n independently declarable, so a creator who named the company and not its lawful bases\n gets `legalEntityName` and `registeredAddress` written and the rest left absent. A\n missing part is reported downstream as outstanding; it does not block anything here.\n- **NEVER invent one.** Not a company name, not an address, not a privacy contact, and\n above all not a lawful basis — that is a legal determination, and `CONSENT` in\n particular would tell a person their data rests on an agreement they could withdraw.\n A produced privacy notice quotes these as fact. An absent declaration is reported as an\n open gap a reader can see; an invented one is published.\n- **Omit the key entirely when you were told nothing.** Absence means \"nobody answered\",\n which is the honest state and the one every consumer already renders correctly. An\n empty object is refused by the schema precisely because it would satisfy the field while\n disclosing nothing.\n- **A jurisdiction needs its `basis`.** \"eu\" alone does not say whether you are established\n there, sell there, or hold data about people there, and those imply different obligations.\n If the creator gave a place without a reason, record neither — ask, or leave it out.\n\nThis step CANNOT fail the run. If the creator answered nothing, write nothing and continue:\nthe application boots, and the gap is visible where it matters rather than here.\n\n(A `foundation-manifest` artifact was declared here until 2026-08-25 and is now\nretired with the app-creation verification/digest aspect. It was a bookkeeping record\nof decisions the config already carries — deleting it costs no fact about the app.)\n\n## Step 5 — 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 // (Deferred greenfield tooling: skeleton materialization is not yet a registered command —\n // do not invent one.)\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 // (Deferred greenfield tooling: the app-knowledge installer is not yet a registered command —\n // do not invent one. `wildo fwk dev-skills` covers the framework-development flow only.)\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 deferred-tooling notes must not be turned\n into invented commands. `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",
|
|
49
|
+
"guidance": "# Foundation — Domain Plan → Configured, Bootable App Skeleton (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\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",
|
|
47
50
|
"skillRefs": [
|
|
48
51
|
"journey-status",
|
|
49
52
|
"config-saas",
|
|
@@ -61,24 +64,12 @@
|
|
|
61
64
|
"organizations",
|
|
62
65
|
"users"
|
|
63
66
|
]
|
|
64
|
-
},
|
|
65
|
-
{
|
|
66
|
-
"ref": "operating-entity",
|
|
67
|
-
"question": "Which legal entity operates this service? Give the registered company name, its registered address, and the route a person uses to reach you about privacy (an email, a URL or a postal address). Answer only the parts you actually know today — anything you leave out is recorded as outstanding and nothing is blocked by it. Do NOT supply a placeholder or a plausible-looking value: a produced privacy notice quotes these as fact, and the address is what a person would use to serve a legal request on a real company.",
|
|
68
|
-
"kind": "free_text"
|
|
69
|
-
},
|
|
70
|
-
{
|
|
71
|
-
"ref": "operating-jurisdictions",
|
|
72
|
-
"question": "Which jurisdictions does this application operate in, and why does each one reach it — are you established there, do you sell there, or do you hold data about people there? Use country codes (`fr`, `us`), the supranational `eu`, or a subdivision (`us-ca`). Answer \"not decided\" if the market is genuinely unsettled; an absent answer is read as unanswered, never as \"nowhere\".",
|
|
73
|
-
"kind": "free_text"
|
|
74
67
|
}
|
|
75
68
|
]
|
|
76
|
-
}
|
|
77
|
-
"contextSources": [],
|
|
78
|
-
"suspendsForClarification": false,
|
|
79
|
-
"briefAdequacyGate": false,
|
|
80
|
-
"briefAdequacyExcludedSources": []
|
|
69
|
+
}
|
|
81
70
|
},
|
|
71
|
+
"executor": "composite",
|
|
72
|
+
"qualityGates": [],
|
|
82
73
|
"approval": "approve_result",
|
|
83
74
|
"budget": {
|
|
84
75
|
"maxRuns": 3
|