@wildo-ai/framework-knowledge 1.1.1 → 1.1.2
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 +43 -2
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts +19 -0
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js +32 -0
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts +12 -0
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +46 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +55 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +4 -4
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +3 -3
- 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 -3
- 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 -3
- 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 +2 -7
- 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 +0 -1
- 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 +8 -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 +22 -1
- 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 +0 -3
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +0 -1
- 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 +4 -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 +4 -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 +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -13
- 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 +3 -4
- 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 +3 -3
- 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 +2 -7
- 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 +2 -7
- 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 +54 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +127 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +76 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +92 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +30 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +29 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +9 -44
- 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 +4 -53
- 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 +31 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +26 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -7
- 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 +0 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +0 -8
- 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 +2 -7
- 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 +2 -7
- 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 +2 -7
- 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 +5 -3
- 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 -3
- 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 +4 -5
- 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 +25 -4
- 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/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
- package/dist/knowledge/manifest.json +8 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +51 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +27 -10
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +8 -7
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +6 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +4 -6
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +5 -4
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +4 -6
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +0 -4
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +4 -6
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +49 -22
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +14 -6
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +2 -4
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +46 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +7 -3
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +18 -4
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +4 -2
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +2 -3
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +8 -7
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +3 -5
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +0 -2
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +100 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +117 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +86 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +21 -4
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +14 -57
- package/dist/knowledge/playbooks/top_down.compliance-research/method.md +76 -0
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +42 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +3 -5
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +3 -1
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +3 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +3 -5
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +8 -4
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +9 -7
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +8 -7
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +0 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +8 -7
- package/dist/knowledge/references/companion.technical-doc.service.md +102 -2
- package/dist/knowledge/references/example.config.app-shell.full.md +0 -1
- package/dist/knowledge/references/example.module.companion-exports.full.md +1 -0
- package/dist/knowledge/references/platform.config.saas.md +1 -0
- package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +25 -1
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +45 -0
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
- package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +89 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +31 -4
- package/dist/knowledge/references/saas.models.engine-capabilities.md +26 -6
- package/dist/knowledge/references/saas.models.file-upload-grant.md +179 -0
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +127 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +4 -3
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
- package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +11 -31
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +32 -2
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +29 -6
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +20 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +6 -0
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +31 -5
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +43 -0
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +15 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
- package/dist/knowledge/registries/framework-topics.json +99 -1
- package/dist/knowledge/registries/playbooks.json +81 -8
- package/dist/knowledge/registries/source-tags.json +757 -588
- package/dist/knowledge/skills/INDEX.md +3 -3
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +5 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +66 -37
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +40 -7
- package/dist/knowledge/skills/config-app-shell/SKILL.md +25 -1
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +25 -1
- package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +23 -1
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
- package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
- package/dist/knowledge/skills/config-navigation/SKILL.md +75 -2
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +149 -0
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +114 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +133 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +19 -2
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +111 -0
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +30 -9
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +1 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +2 -1
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +20 -0
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +20 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +20 -0
- 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 +104 -0
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +13 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +71 -4
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +89 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +22 -1
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +192 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +28 -8
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +15 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +6 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +89 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +43 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +1 -1
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +20 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +31 -5
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +22 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +45 -0
- package/dist/knowledge/topic-index.json +504 -156
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/esm/.builder.pid +0 -9
|
@@ -111,8 +111,6 @@ it). Before sharpening anything:
|
|
|
111
111
|
VisionSnapshot at the `vision-brief` placement, so you sharpen against the
|
|
112
112
|
real market intent and the real differentiation, not from scratch.
|
|
113
113
|
|
|
114
|
-
// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)
|
|
115
|
-
// TODO CLI COMMAND: wildo context market-snapshot (read the existing snapshot to refine its value-prop slices)
|
|
116
114
|
|
|
117
115
|
Then sharpen:
|
|
118
116
|
|
|
@@ -5,10 +5,6 @@
|
|
|
5
5
|
"intent": "Top-down value-proposition / positioning: sharpen the product's value proposition on an EXISTING MarketSnapshot — the weighted benefits (relieves/creates/advances edges, Kano category per ICP), the tones of voice, and the per-ICP positioning pillars — framed by the product VisionSnapshot's differentiation. Runs after market-analysis (which produced the broad snapshot) and refines the same market-snapshot artifact; it does NOT create a new family (benefits, tone-of-voice, and positioning all live inside MarketSnapshot). Emits the refined MarketSnapshot validated by validateMarketSnapshot, consumed downstream by capability-map (benefits -> deliveredByFeatureRefs) and the refinement/coverage playbooks. v1 scaffold methodology — the FIT/Kano scoring precision and positioning rigor are iterated in a later depth phase, not here.",
|
|
6
6
|
"functionalTopics": [],
|
|
7
7
|
"preconditions": [
|
|
8
|
-
{
|
|
9
|
-
"kind": "phase_is",
|
|
10
|
-
"phase": "top_down"
|
|
11
|
-
},
|
|
12
8
|
{
|
|
13
9
|
"kind": "artifact_exists",
|
|
14
10
|
"selector": {
|
|
@@ -33,7 +29,7 @@
|
|
|
33
29
|
],
|
|
34
30
|
"stepOutputs": [],
|
|
35
31
|
"method": {
|
|
36
|
-
"guidance": "# Value Proposition & Positioning — Sharpen Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The refinement order, the benefit-weighting posture, and the\n> \"sharpen vs. leave\" rules below are deliberately explicit so they can be\n> tuned against real runs — treat them as a starting rubric, not a frozen\n> contract. The *analytical depth* of the value-proposition work (quantified\n> FIT / Kano scoring precision, positioning rigor) is intentionally shallow\n> here and is deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **positioning strategist**. Market-analysis already produced the\n**MarketSnapshot** — the category, ICPs, personas, and jobs/pains/gains. Your\none job is to **sharpen the value-proposition slices of that same snapshot**:\nthe benefits, the tones of voice, and the per-ICP positioning pillars, framed\nby the product's **VisionSnapshot** differentiation. You do not create a new\nartifact family — benefits, tone-of-voice, and positioning all live *inside*\n`MarketSnapshot`. You read the existing snapshot, tighten these three slices,\nand re-emit the same snapshot.\n\nThis is a **focused refinement pass**, distinct from market-analysis (which\ndoes the broad initial market sweep). Where market-analysis lays down the\nwhole snapshot at a first-pass depth, you come back over the value-proposition\nslices specifically and make them sharp, consistent with each other, and true\nto the vision.\n\nThe three slices you own, in dependency order (later slices reference earlier\nrefs, and all reference the jobs/pains/gains the market pass already authored):\n\n1. **Benefits** — the outcome claims the product delivers (`FeatureBenefit`),\n each a *weighted* set of edges: the pains it **relieves**, the gains it\n **creates**, and the jobs it **advances**, every edge carrying a `degree`\n (1..10) the FIT scorer multiplies by the ICP's own edge weight. Layer on\n `importanceByICP`: a per-ICP `weight` plus a **Kano category** from the\n `BenefitKanoCategory` enum — `THRESHOLD` (a must-have; its absence breaks\n the deal), `PERFORMANCE` (more is better), `DELIGHTER` (unexpected upside),\n plus `INDIFFERENT` / `REVERSE` for completeness — so the same benefit can\n matter differently to different segments. Benefits reference the\n pains/gains/jobs the market pass authored — never weight against a\n pain/gain/job that does not exist. (`market-add-feature-benefit`)\n - **Structural constraint (the U8 seam):** every benefit carries a\n non-empty `deliveredByFeatureRefs[]` — a benefit must be *deliverable*.\n At this top-down phase there is no feature registry yet, so these are\n **forward-reference** feature refs; the `ORPHAN_REF` resolution check is\n skipped until a feature set exists. **Wiring benefits to real spec-first\n feature drafts is the capability-map playbook's job (U8), not yours** —\n do not invent the feature registry here. Keep the refs you inherit;\n leave a placeholder ref only where the market pass already did.\n2. **Tones of voice** — the named brand voices the product speaks in\n (`ToneOfVoice`, addressed by `ToneOfVoiceRef`). Keep them few and distinct;\n each positioning and message template later speaks in one of them.\n (`market-tone-of-voice`)\n3. **Positioning** — the per-ICP marketing-truth promise (`MarketPositioning`):\n author **one positioning entry per ICP the product actually targets**\n (priority `CORE` or `EXPANSION`), each carrying **2–4 value pillars**\n (`valuePillars`) — the sharp claims that separate the product from the\n alternatives. Each pillar hangs off the weighted benefits above (it traces\n back to `FeatureBenefitRef[]`) and is framed by the vision's\n differentiation. (`market-positioning-authoring`)\n\nSharpen only the slices the product's stage warrants. A snapshot whose\nbenefits carry honest relieves/creates/advances weighting with per-ICP Kano\ncategories, at least one tone of voice, and one positioning entry (with its\nvalue pillars) per `CORE`/`EXPANSION` ICP is a legitimate v1; the depth of the\nweighting and the pillar prose is additive.\n\n## Frame everything by the vision\n\nThe **VisionSnapshot** (`vision-brief` family) is your differentiation anchor.\nRead its mission, its problem framing, and its success criteria before you\nweight a single benefit. A benefit's weight, a Kano category, and a positioning\npillar are only *right* if they express the product's actual differentiation —\nwhat the vision says makes this product worth building over the alternatives.\nWhen a benefit or pillar cannot be traced back to the vision's differentiation,\nthat is a signal to either sharpen the vision link or drop the claim, not to\ninvent a promise the product does not stand behind.\n\n## Where the snapshot lives\n\nThe MarketSnapshot for this journey is at\n`specifications/src/market/index.ts`. That is the artifact this\nplaybook refines in place — you read it, sharpen the value-proposition slices,\nand write the same artifact back. When the product's definition later\nstabilises, the snapshot is what seeds the durable market specification under\n`./specifications/` — but at this phase it is a journey artifact, not yet app\nsource.\n\n## Refine, don't re-author — read state first\n\nThis playbook is **idempotent** and, by construction, a *refinement*: a\nMarketSnapshot must already exist (the `artifact_exists` precondition enforces\nit). Before sharpening anything:\n\n1. Read the current journey state and scope through the `journey-status` skill\n (it owns the read; do not re-derive it here) — that tells you which scope\n the value proposition must hold *for*.\n2. Read the existing MarketSnapshot at this playbook's placement path and the\n VisionSnapshot at the `vision-brief` placement, so you sharpen against the\n real market intent and the real differentiation, not from scratch.\n\n// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)\n// TODO CLI COMMAND: wildo context market-snapshot (read the existing snapshot to refine its value-prop slices)\n\nThen sharpen:\n\n- **Keep what still holds.** Do not rewrite benefits, tones, or pillars that\n are already sharp and vision-true. Only add/correct where the current\n steering notes, the vision, or benefit-weight inconsistencies call for it.\n- **Never orphan a ref.** A positioning names an ICP and its pillars name\n benefits; a benefit names the pains/gains/jobs it relieves/creates/advances.\n Dropping an ICP, pain, gain, job, or benefit that a positioning, pillar, or\n benefit still points at orphans the downstream ref (the validator catches\n this as `ORPHAN_REF`, but honest refinement should not create the orphan).\n If a slice from the market pass is genuinely wrong, fix it at its source\n slice, do not paper over it in the value-prop layer.\n\n## Quality gate\n\nYour re-emitted snapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. The\nvalue-proposition invariants it enforces are mostly **`ERROR`-severity hard\nfailures** — the snapshot does not advance until they clear:\n\n- **`MISSING_POSITIONING_FOR_ICP` (ERROR)** — a `CORE` or `EXPANSION` ICP has\n no `MarketPositioning`. This is the headline gap this playbook closes: a\n targeted ICP without a positioning is a *hard failure*, not a warning.\n (`EXPLORATORY` / `DEFERRED` / `ANTI_TARGET` ICPs are exempt.)\n- **`THRESHOLD_BENEFIT_WITHOUT_JOB` (ERROR)** — a benefit carries a\n `kanoCategory: THRESHOLD` entry but its `advances[]` is empty; a must-have\n claim needs a job to anchor against.\n- **`MULTIPLE_THRESHOLDS_PER_ICP_JOB` (ERROR)** — two distinct benefits both\n claim `THRESHOLD` for the same (icp, job); only one must-have per job.\n- **`EMPTY_BENEFIT_DELIVERED_BY` (ERROR)** — a benefit's `deliveredByFeatureRefs[]`\n is empty; every benefit must stay deliverable (see the U8 seam above).\n- **`ORPHAN_REF` (ERROR)** — a positioning naming a missing ICP, a pillar or\n benefit naming a missing pain/gain/job. (Feature-ref orphans are only\n checked once a feature registry is passed — not at this phase.)\n\n`WARN`-severity issues do not block but should be resolved: `DUPLICATE_EDGE_PER_ENTITY`\n(a duplicate `(benefit, icp)` importance edge) and `STALE_AUTHORED` (a slice\npast its review cadence). Read `market-snapshot-validation` for the full issue\ncatalogue and emit a clean snapshot the first time.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. The following are explicitly **out of\nscope here** and are deepened in the methodology-depth phase, not now:\n\n- **Quantified FIT / Kano scoring precision** — `market-scoring-interpretation`\n reads the deterministic FIT scorer; at scaffold depth you consume it to\n sanity-check benefit weighting and Kano assignment, not to drive a precise\n prioritization model. The prioritization seam stays pluggable (the\n capability-map playbook owns wiring FIT scores into feature drafts). Do not\n build a scoring model here.\n- **Positioning rigor** — a pillar captures *the* sharp per-ICP promise; a\n full competitive positioning matrix, message-market-fit testing, or\n A/B-tested copy is later-phase work.\n- **Message-template rendering** — this playbook stops at the value-proposition\n slices (benefits / tone / pillars). Turning them into reusable message\n templates stays with the market-analysis playbook's `market_message_templates`\n slice.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nThe SAME MarketSnapshot at `specifications/src/market/index.ts`,\nwith its value-proposition slices sharpened: weighted benefits with per-ICP\nKano categories, the tones of voice, and one positioning entry (with its 2–4\nvalue pillars) per `CORE`/`EXPANSION` ICP — all framed by the vision's\ndifferentiation — passing the\n`market-snapshot-valid` gate. The creator reviews the result (approval posture\n`approve_result`) before it is accepted as the journey's refined market intent.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state\n and scope, and confirm a `market-snapshot` already exists to refine.\n- `.claude/skills/market-add-feature-benefit/SKILL.md` — author the benefit\n claims and their relieves/creates/advances weighting and per-ICP Kano\n categories.\n- `.claude/skills/market-tone-of-voice/SKILL.md` — author the named brand\n voices.\n- `.claude/skills/market-positioning-authoring/SKILL.md` — author the per-ICP\n positioning entries and their 2–4 value pillars.\n- `.claude/skills/market-scoring-interpretation/SKILL.md` — interpret the\n deterministic FIT scorer to sanity-check benefit weighting and Kano\n assignment (scaffold depth — sanity-check, not a scoring model).\n- `.claude/skills/market-snapshot-validation/SKILL.md` — the full validation\n issue catalogue the quality gate enforces.\n",
|
|
32
|
+
"guidance": "# Value Proposition & Positioning — Sharpen Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The refinement order, the benefit-weighting posture, and the\n> \"sharpen vs. leave\" rules below are deliberately explicit so they can be\n> tuned against real runs — treat them as a starting rubric, not a frozen\n> contract. The *analytical depth* of the value-proposition work (quantified\n> FIT / Kano scoring precision, positioning rigor) is intentionally shallow\n> here and is deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **positioning strategist**. Market-analysis already produced the\n**MarketSnapshot** — the category, ICPs, personas, and jobs/pains/gains. Your\none job is to **sharpen the value-proposition slices of that same snapshot**:\nthe benefits, the tones of voice, and the per-ICP positioning pillars, framed\nby the product's **VisionSnapshot** differentiation. You do not create a new\nartifact family — benefits, tone-of-voice, and positioning all live *inside*\n`MarketSnapshot`. You read the existing snapshot, tighten these three slices,\nand re-emit the same snapshot.\n\nThis is a **focused refinement pass**, distinct from market-analysis (which\ndoes the broad initial market sweep). Where market-analysis lays down the\nwhole snapshot at a first-pass depth, you come back over the value-proposition\nslices specifically and make them sharp, consistent with each other, and true\nto the vision.\n\nThe three slices you own, in dependency order (later slices reference earlier\nrefs, and all reference the jobs/pains/gains the market pass already authored):\n\n1. **Benefits** — the outcome claims the product delivers (`FeatureBenefit`),\n each a *weighted* set of edges: the pains it **relieves**, the gains it\n **creates**, and the jobs it **advances**, every edge carrying a `degree`\n (1..10) the FIT scorer multiplies by the ICP's own edge weight. Layer on\n `importanceByICP`: a per-ICP `weight` plus a **Kano category** from the\n `BenefitKanoCategory` enum — `THRESHOLD` (a must-have; its absence breaks\n the deal), `PERFORMANCE` (more is better), `DELIGHTER` (unexpected upside),\n plus `INDIFFERENT` / `REVERSE` for completeness — so the same benefit can\n matter differently to different segments. Benefits reference the\n pains/gains/jobs the market pass authored — never weight against a\n pain/gain/job that does not exist. (`market-add-feature-benefit`)\n - **Structural constraint (the U8 seam):** every benefit carries a\n non-empty `deliveredByFeatureRefs[]` — a benefit must be *deliverable*.\n At this top-down phase there is no feature registry yet, so these are\n **forward-reference** feature refs; the `ORPHAN_REF` resolution check is\n skipped until a feature set exists. **Wiring benefits to real spec-first\n feature drafts is the capability-map playbook's job (U8), not yours** —\n do not invent the feature registry here. Keep the refs you inherit;\n leave a placeholder ref only where the market pass already did.\n2. **Tones of voice** — the named brand voices the product speaks in\n (`ToneOfVoice`, addressed by `ToneOfVoiceRef`). Keep them few and distinct;\n each positioning and message template later speaks in one of them.\n (`market-tone-of-voice`)\n3. **Positioning** — the per-ICP marketing-truth promise (`MarketPositioning`):\n author **one positioning entry per ICP the product actually targets**\n (priority `CORE` or `EXPANSION`), each carrying **2–4 value pillars**\n (`valuePillars`) — the sharp claims that separate the product from the\n alternatives. Each pillar hangs off the weighted benefits above (it traces\n back to `FeatureBenefitRef[]`) and is framed by the vision's\n differentiation. (`market-positioning-authoring`)\n\nSharpen only the slices the product's stage warrants. A snapshot whose\nbenefits carry honest relieves/creates/advances weighting with per-ICP Kano\ncategories, at least one tone of voice, and one positioning entry (with its\nvalue pillars) per `CORE`/`EXPANSION` ICP is a legitimate v1; the depth of the\nweighting and the pillar prose is additive.\n\n## Frame everything by the vision\n\nThe **VisionSnapshot** (`vision-brief` family) is your differentiation anchor.\nRead its mission, its problem framing, and its success criteria before you\nweight a single benefit. A benefit's weight, a Kano category, and a positioning\npillar are only *right* if they express the product's actual differentiation —\nwhat the vision says makes this product worth building over the alternatives.\nWhen a benefit or pillar cannot be traced back to the vision's differentiation,\nthat is a signal to either sharpen the vision link or drop the claim, not to\ninvent a promise the product does not stand behind.\n\n## Where the snapshot lives\n\nThe MarketSnapshot for this journey is at\n`specifications/src/market/index.ts`. That is the artifact this\nplaybook refines in place — you read it, sharpen the value-proposition slices,\nand write the same artifact back. When the product's definition later\nstabilises, the snapshot is what seeds the durable market specification under\n`./specifications/` — but at this phase it is a journey artifact, not yet app\nsource.\n\n## Refine, don't re-author — read state first\n\nThis playbook is **idempotent** and, by construction, a *refinement*: a\nMarketSnapshot must already exist (the `artifact_exists` precondition enforces\nit). Before sharpening anything:\n\n1. Read the current journey state and scope through the `journey-status` skill\n (it owns the read; do not re-derive it here) — that tells you which scope\n the value proposition must hold *for*.\n2. Read the existing MarketSnapshot at this playbook's placement path and the\n VisionSnapshot at the `vision-brief` placement, so you sharpen against the\n real market intent and the real differentiation, not from scratch.\n\n\nThen sharpen:\n\n- **Keep what still holds.** Do not rewrite benefits, tones, or pillars that\n are already sharp and vision-true. Only add/correct where the current\n steering notes, the vision, or benefit-weight inconsistencies call for it.\n- **Never orphan a ref.** A positioning names an ICP and its pillars name\n benefits; a benefit names the pains/gains/jobs it relieves/creates/advances.\n Dropping an ICP, pain, gain, job, or benefit that a positioning, pillar, or\n benefit still points at orphans the downstream ref (the validator catches\n this as `ORPHAN_REF`, but honest refinement should not create the orphan).\n If a slice from the market pass is genuinely wrong, fix it at its source\n slice, do not paper over it in the value-prop layer.\n\n## Quality gate\n\nYour re-emitted snapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. The\nvalue-proposition invariants it enforces are mostly **`ERROR`-severity hard\nfailures** — the snapshot does not advance until they clear:\n\n- **`MISSING_POSITIONING_FOR_ICP` (ERROR)** — a `CORE` or `EXPANSION` ICP has\n no `MarketPositioning`. This is the headline gap this playbook closes: a\n targeted ICP without a positioning is a *hard failure*, not a warning.\n (`EXPLORATORY` / `DEFERRED` / `ANTI_TARGET` ICPs are exempt.)\n- **`THRESHOLD_BENEFIT_WITHOUT_JOB` (ERROR)** — a benefit carries a\n `kanoCategory: THRESHOLD` entry but its `advances[]` is empty; a must-have\n claim needs a job to anchor against.\n- **`MULTIPLE_THRESHOLDS_PER_ICP_JOB` (ERROR)** — two distinct benefits both\n claim `THRESHOLD` for the same (icp, job); only one must-have per job.\n- **`EMPTY_BENEFIT_DELIVERED_BY` (ERROR)** — a benefit's `deliveredByFeatureRefs[]`\n is empty; every benefit must stay deliverable (see the U8 seam above).\n- **`ORPHAN_REF` (ERROR)** — a positioning naming a missing ICP, a pillar or\n benefit naming a missing pain/gain/job. (Feature-ref orphans are only\n checked once a feature registry is passed — not at this phase.)\n\n`WARN`-severity issues do not block but should be resolved: `DUPLICATE_EDGE_PER_ENTITY`\n(a duplicate `(benefit, icp)` importance edge) and `STALE_AUTHORED` (a slice\npast its review cadence). Read `market-snapshot-validation` for the full issue\ncatalogue and emit a clean snapshot the first time.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. The following are explicitly **out of\nscope here** and are deepened in the methodology-depth phase, not now:\n\n- **Quantified FIT / Kano scoring precision** — `market-scoring-interpretation`\n reads the deterministic FIT scorer; at scaffold depth you consume it to\n sanity-check benefit weighting and Kano assignment, not to drive a precise\n prioritization model. The prioritization seam stays pluggable (the\n capability-map playbook owns wiring FIT scores into feature drafts). Do not\n build a scoring model here.\n- **Positioning rigor** — a pillar captures *the* sharp per-ICP promise; a\n full competitive positioning matrix, message-market-fit testing, or\n A/B-tested copy is later-phase work.\n- **Message-template rendering** — this playbook stops at the value-proposition\n slices (benefits / tone / pillars). Turning them into reusable message\n templates stays with the market-analysis playbook's `market_message_templates`\n slice.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nThe SAME MarketSnapshot at `specifications/src/market/index.ts`,\nwith its value-proposition slices sharpened: weighted benefits with per-ICP\nKano categories, the tones of voice, and one positioning entry (with its 2–4\nvalue pillars) per `CORE`/`EXPANSION` ICP — all framed by the vision's\ndifferentiation — passing the\n`market-snapshot-valid` gate. The creator reviews the result (approval posture\n`approve_result`) before it is accepted as the journey's refined market intent.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state\n and scope, and confirm a `market-snapshot` already exists to refine.\n- `.claude/skills/market-add-feature-benefit/SKILL.md` — author the benefit\n claims and their relieves/creates/advances weighting and per-ICP Kano\n categories.\n- `.claude/skills/market-tone-of-voice/SKILL.md` — author the named brand\n voices.\n- `.claude/skills/market-positioning-authoring/SKILL.md` — author the per-ICP\n positioning entries and their 2–4 value pillars.\n- `.claude/skills/market-scoring-interpretation/SKILL.md` — interpret the\n deterministic FIT scorer to sanity-check benefit weighting and Kano\n assignment (scaffold depth — sanity-check, not a scoring model).\n- `.claude/skills/market-snapshot-validation/SKILL.md` — the full validation\n issue catalogue the quality gate enforces.\n",
|
|
37
33
|
"skillRefs": [
|
|
38
34
|
"journey-status",
|
|
39
35
|
"market-add-feature-benefit",
|
|
@@ -43,7 +39,9 @@
|
|
|
43
39
|
"market-snapshot-validation"
|
|
44
40
|
],
|
|
45
41
|
"contextSources": [],
|
|
46
|
-
"suspendsForClarification": false
|
|
42
|
+
"suspendsForClarification": false,
|
|
43
|
+
"briefAdequacyGate": false,
|
|
44
|
+
"briefAdequacyExcludedSources": []
|
|
47
45
|
},
|
|
48
46
|
"executor": "companion_agent",
|
|
49
47
|
"approval": "approve_result",
|
|
@@ -137,8 +137,8 @@ Before you start, read the current journey state and scope so you elicit the
|
|
|
137
137
|
vision for the right product, and read any vision that already exists so you
|
|
138
138
|
refine it rather than re-eliciting it from scratch.
|
|
139
139
|
|
|
140
|
-
|
|
141
|
-
|
|
140
|
+
(When a prior vision exists it arrives in your brief as the `vision-brief` input section — refine
|
|
141
|
+
that content rather than re-eliciting it.)
|
|
142
142
|
|
|
143
143
|
## References
|
|
144
144
|
|
|
@@ -1,16 +1,15 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.vision-elicitation",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.1",
|
|
4
4
|
"phase": "top_down",
|
|
5
5
|
"intent": "Elicit a complete current-horizon product vision from sealed creator input and application context. The provider proposes semantic content; the trusted runtime stamps refs/version and keeps provenance, authority and accepted-family mutation outside model output.",
|
|
6
6
|
"functionalTopics": [],
|
|
7
|
-
"preconditions": [
|
|
7
|
+
"preconditions": [],
|
|
8
|
+
"inputs": [
|
|
8
9
|
{
|
|
9
|
-
"
|
|
10
|
-
"phase": "top_down"
|
|
10
|
+
"family": "vision-brief"
|
|
11
11
|
}
|
|
12
12
|
],
|
|
13
|
-
"inputs": [],
|
|
14
13
|
"outputs": [
|
|
15
14
|
{
|
|
16
15
|
"family": "vision-brief",
|
|
@@ -20,7 +19,7 @@
|
|
|
20
19
|
],
|
|
21
20
|
"stepOutputs": [],
|
|
22
21
|
"method": {
|
|
23
|
-
"guidance": "# Vision Elicitation — Interview Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **vision interviewer**. Your one job is to draw the product's\nfoundational vision out of the creator through a structured conversation, and\nto capture it as a single typed **`VisionSnapshot`** — the `vision-brief`\nartifact. This is the **first** top-down step: everything downstream\n(positioning, the capability map, the compliance posture, the roadmap) reads\nthe vision you produce, so an honest, well-framed vision is the whole task.\n\nYou do **not** design the domain, draft requirements, or write code. You\nelicit *intent* — what the product is, why it should exist, what winning looks\nlike, and what limits bound it — and nothing more. Keep the market family\n(segments, personas) and the requirements family out of scope; the vision\nreferences them later, it does not absorb them.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, follow up where an answer is thin, and skip a follow-up the\n creator already answered. Reflect each answer back in one line and let the\n creator correct you before you move on.\n- **Progressive is fine.** A `VisionSnapshot` requires only the **idea**; the\n problem statement and mission are OPTIONAL and elicited progressively. If the\n creator can only give you the idea today, capture it, note what is still\n open, and stop — the snapshot persists as partially-elicited and this\n playbook can resume. Never invent a problem or mission the creator did not\n give you just to fill the shape.\n- **One product, one vision.** The snapshot is a single aggregate, not a list\n — one idea, one problem, one mission, plus ref-addressable success criteria\n and constraints. If the creator describes two products, stop and ask which\n one this journey is for.\n\n## What you elicit — one aggregate\n\nWork the vision entity by entity. For each, the target shape and the framing\nquestions:\n\n- **Idea** (REQUIRED). The anchor concept. Capture a quotable one-liner\n (\"X for Y\") and a short paragraph expanding it (core capability, shape of the\n solution). Record any framing caveats or pivots as notes. A vision without an\n idea is nothing — do not proceed to the rest until you have it.\n- **Problem** (optional, WARNed when absent). The pain the product exists to\n solve: the core statement, who is affected (prose — the deep segment model is\n the market family's job), how people cope today, the cost of leaving it\n unsolved, and the timing trigger that makes solving it urgent *now*. This is\n a framing surface, not a sized opportunity model — capture the \"why\", not a\n TAM.\n- **Mission** (optional, WARNed when absent). The enduring purpose: the mission\n statement (what we do, for whom, to what end, in one sentence), the\n aspirational long-term end-state if it fully succeeds, and the guiding\n principles / non-negotiables that constrain *how* the product is built.\n Principles are chosen stances — keep them distinct from the hard external\n constraints below.\n- **Success criteria** (ref-addressable, `success-criterion-<slug>`). What\n \"this succeeded\" concretely looks like. Each criterion is a statement, an\n optional metric and target (free prose at this stage — \"500 weekly active\n teams\", \"median time-to-first-value < 5 min\"), and a coarse horizon bucket\n (`launch` / `short_term` / `long_term`). Do not force a quantified metric\n where the creator only has a qualitative one — a typed metric taxonomy is a\n later concern. A vision with no success criteria cannot be judged\n succeeded — the validator WARNs on it, so push for at least one.\n- **Constraints** (ref-addressable, `constraint-<slug>`). External limits the\n product must be built within, each classified by kind: `technical`,\n `business`, `compliance`, `resource`, `timeline`, or `other`. Capture the\n constraint statement and, where the creator gives it, the rationale (the\n source of the limit).\n - **Compliance constraints get explicit attention.** Ask whether the product\n handles regulated or personal data, operates in a regulated sector or has contractual\n assurance commitments. If so, record each as a\n `kind: compliance` constraint with a **prose** statement (\"Must be\n GDPR-compliant for EU customer personal data\"). Stop at prose — the deep\n per-regime obligation model (control catalogs, data-flow / residency\n matrices) is the compliance-posture step's job, not yours. Getting the\n compliance *seam* named here is what lets that later step engage.\n\n## What you emit\n\nA single `VisionSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told\n otherwise).\n- `idea` — the required anchor (`oneLiner`, `description`, optional `notes`).\n- `problem` / `mission` — the optional singletons, present only if elicited.\n- `successCriteria[]` — each with a stable kebab-case `ref` prefixed\n `success-criterion-`, unique across the set.\n- `constraints[]` — each with a stable kebab-case `ref` prefixed `constraint-`,\n unique across the set, and a `kind`.\n\nAuthor every entity in English. Use stable, human-readable ref slugs\n(`success-criterion-weekly-active-teams`, `constraint-gdpr-eu-data`) — they are\naddressed by ref downstream, so a duplicate silently drops an entity.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `vision-snapshot-valid`\ngate (`validateVisionSnapshot`) before it commits. Duplicate refs and malformed\nrefs (a success-criterion or constraint ref that is not kebab-case with its\nrequired prefix) are hard **errors** — the gate rejects them. A missing problem,\na missing mission, and an empty success-criteria set are **warnings**: they\nreflect a not-yet-complete vision, they do not block, and the journey persists\nthe snapshot as partially-elicited. Emit clean refs the first time; let the\nwarnings stand honestly when the vision genuinely is not complete yet, rather\nthan inventing entities to silence them.\n\n## Approval\n\nThe drafted `VisionSnapshot` is presented to the creator for approval before it\nbecomes the committed `vision-brief`. Show the vision back in plain prose — the\none-liner, the problem, the mission, the criteria, the constraints — and let the\ncreator confirm or correct it. The vision is the seed every later step trusts;\nit is worth one explicit human sign-off.\n\n## Runtime context\n\nBefore you start, read the current journey state and scope so you elicit the\nvision for the right product, and read any vision that already exists so you\nrefine it rather than re-eliciting it from scratch.\n\n
|
|
22
|
+
"guidance": "# Vision Elicitation — Interview Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **vision interviewer**. Your one job is to draw the product's\nfoundational vision out of the creator through a structured conversation, and\nto capture it as a single typed **`VisionSnapshot`** — the `vision-brief`\nartifact. This is the **first** top-down step: everything downstream\n(positioning, the capability map, the compliance posture, the roadmap) reads\nthe vision you produce, so an honest, well-framed vision is the whole task.\n\nYou do **not** design the domain, draft requirements, or write code. You\nelicit *intent* — what the product is, why it should exist, what winning looks\nlike, and what limits bound it — and nothing more. Keep the market family\n(segments, personas) and the requirements family out of scope; the vision\nreferences them later, it does not absorb them.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, follow up where an answer is thin, and skip a follow-up the\n creator already answered. Reflect each answer back in one line and let the\n creator correct you before you move on.\n- **Progressive is fine.** A `VisionSnapshot` requires only the **idea**; the\n problem statement and mission are OPTIONAL and elicited progressively. If the\n creator can only give you the idea today, capture it, note what is still\n open, and stop — the snapshot persists as partially-elicited and this\n playbook can resume. Never invent a problem or mission the creator did not\n give you just to fill the shape.\n- **One product, one vision.** The snapshot is a single aggregate, not a list\n — one idea, one problem, one mission, plus ref-addressable success criteria\n and constraints. If the creator describes two products, stop and ask which\n one this journey is for.\n\n## What you elicit — one aggregate\n\nWork the vision entity by entity. For each, the target shape and the framing\nquestions:\n\n- **Idea** (REQUIRED). The anchor concept. Capture a quotable one-liner\n (\"X for Y\") and a short paragraph expanding it (core capability, shape of the\n solution). Record any framing caveats or pivots as notes. A vision without an\n idea is nothing — do not proceed to the rest until you have it.\n- **Problem** (optional, WARNed when absent). The pain the product exists to\n solve: the core statement, who is affected (prose — the deep segment model is\n the market family's job), how people cope today, the cost of leaving it\n unsolved, and the timing trigger that makes solving it urgent *now*. This is\n a framing surface, not a sized opportunity model — capture the \"why\", not a\n TAM.\n- **Mission** (optional, WARNed when absent). The enduring purpose: the mission\n statement (what we do, for whom, to what end, in one sentence), the\n aspirational long-term end-state if it fully succeeds, and the guiding\n principles / non-negotiables that constrain *how* the product is built.\n Principles are chosen stances — keep them distinct from the hard external\n constraints below.\n- **Success criteria** (ref-addressable, `success-criterion-<slug>`). What\n \"this succeeded\" concretely looks like. Each criterion is a statement, an\n optional metric and target (free prose at this stage — \"500 weekly active\n teams\", \"median time-to-first-value < 5 min\"), and a coarse horizon bucket\n (`launch` / `short_term` / `long_term`). Do not force a quantified metric\n where the creator only has a qualitative one — a typed metric taxonomy is a\n later concern. A vision with no success criteria cannot be judged\n succeeded — the validator WARNs on it, so push for at least one.\n- **Constraints** (ref-addressable, `constraint-<slug>`). External limits the\n product must be built within, each classified by kind: `technical`,\n `business`, `compliance`, `resource`, `timeline`, or `other`. Capture the\n constraint statement and, where the creator gives it, the rationale (the\n source of the limit).\n - **Compliance constraints get explicit attention.** Ask whether the product\n handles regulated or personal data, operates in a regulated sector or has contractual\n assurance commitments. If so, record each as a\n `kind: compliance` constraint with a **prose** statement (\"Must be\n GDPR-compliant for EU customer personal data\"). Stop at prose — the deep\n per-regime obligation model (control catalogs, data-flow / residency\n matrices) is the compliance-posture step's job, not yours. Getting the\n compliance *seam* named here is what lets that later step engage.\n\n## What you emit\n\nA single `VisionSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told\n otherwise).\n- `idea` — the required anchor (`oneLiner`, `description`, optional `notes`).\n- `problem` / `mission` — the optional singletons, present only if elicited.\n- `successCriteria[]` — each with a stable kebab-case `ref` prefixed\n `success-criterion-`, unique across the set.\n- `constraints[]` — each with a stable kebab-case `ref` prefixed `constraint-`,\n unique across the set, and a `kind`.\n\nAuthor every entity in English. Use stable, human-readable ref slugs\n(`success-criterion-weekly-active-teams`, `constraint-gdpr-eu-data`) — they are\naddressed by ref downstream, so a duplicate silently drops an entity.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `vision-snapshot-valid`\ngate (`validateVisionSnapshot`) before it commits. Duplicate refs and malformed\nrefs (a success-criterion or constraint ref that is not kebab-case with its\nrequired prefix) are hard **errors** — the gate rejects them. A missing problem,\na missing mission, and an empty success-criteria set are **warnings**: they\nreflect a not-yet-complete vision, they do not block, and the journey persists\nthe snapshot as partially-elicited. Emit clean refs the first time; let the\nwarnings stand honestly when the vision genuinely is not complete yet, rather\nthan inventing entities to silence them.\n\n## Approval\n\nThe drafted `VisionSnapshot` is presented to the creator for approval before it\nbecomes the committed `vision-brief`. Show the vision back in plain prose — the\none-liner, the problem, the mission, the criteria, the constraints — and let the\ncreator confirm or correct it. The vision is the seed every later step trusts;\nit is worth one explicit human sign-off.\n\n## Runtime context\n\nBefore you start, read the current journey state and scope so you elicit the\nvision for the right product, and read any vision that already exists so you\nrefine it rather than re-eliciting it from scratch.\n\n(When a prior vision exists it arrives in your brief as the `vision-brief` input section — refine\nthat content rather than re-eliciting it.)\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read current journey state and\n scope before eliciting, and to see whether a `vision-brief` already exists.\n",
|
|
24
23
|
"skillRefs": [
|
|
25
24
|
"journey-status"
|
|
26
25
|
],
|
|
@@ -109,7 +108,9 @@
|
|
|
109
108
|
]
|
|
110
109
|
},
|
|
111
110
|
"contextSources": [],
|
|
112
|
-
"suspendsForClarification": false
|
|
111
|
+
"suspendsForClarification": false,
|
|
112
|
+
"briefAdequacyGate": false,
|
|
113
|
+
"briefAdequacyExcludedSources": []
|
|
113
114
|
},
|
|
114
115
|
"executor": "companion_agent",
|
|
115
116
|
"approval": "approve_result",
|
|
@@ -22,7 +22,7 @@ import {
|
|
|
22
22
|
resolveFeatureGatedCoreResourceExclusions,
|
|
23
23
|
describeCaughtError,
|
|
24
24
|
} from '@wildo-ai/saas-backend-lib';
|
|
25
|
-
import { CoreResourceType, ErrorCustomMessageReference, ErrorType } from '@wildo-ai/saas-models';
|
|
25
|
+
import { AuthMethod, CoreResourceType, ErrorCustomMessageReference, ErrorType, getEnabledMethods } from '@wildo-ai/saas-models';
|
|
26
26
|
import { AppFrontendType, loadConfig } from '@wildo-ai/platform-config-lib';
|
|
27
27
|
import {
|
|
28
28
|
generateOpenApiDocuments,
|
|
@@ -37,6 +37,10 @@ import {
|
|
|
37
37
|
type OperationProjection,
|
|
38
38
|
type ResourceTag,
|
|
39
39
|
type TechnicalDocGenerateOpenApiResult,
|
|
40
|
+
type ApplicationConnectionServer,
|
|
41
|
+
type ApplicationAuthenticationDocumentationSource,
|
|
42
|
+
type ApplicationMcpToolSource,
|
|
43
|
+
type ApplicationWebhookEventSource,
|
|
40
44
|
} from '@wildo-ai/saas-technical-doc/companion';
|
|
41
45
|
import {
|
|
42
46
|
createApiReferenceLinkIndex,
|
|
@@ -104,6 +108,13 @@ interface OpenApiGenerationInputSubprocessOutput {
|
|
|
104
108
|
/** Source-derived application activation facts; independent from the API-reference selection. */
|
|
105
109
|
readonly hasConfiguredMcpToolOperations: boolean;
|
|
106
110
|
readonly hasConfiguredA2aSkills: boolean;
|
|
111
|
+
/**
|
|
112
|
+
* The two integration inventories the same walk collects. Row types come from the ENGINE, not
|
|
113
|
+
* from the subprocess module, so this mirror cannot drift on their shape while the parent still
|
|
114
|
+
* never loads subprocess code.
|
|
115
|
+
*/
|
|
116
|
+
readonly mcpTools: readonly ApplicationMcpToolSource[];
|
|
117
|
+
readonly webhookEvents: readonly ApplicationWebhookEventSource[];
|
|
107
118
|
/**
|
|
108
119
|
* Source-derived role semantics cross the subprocess boundary unchanged.
|
|
109
120
|
* The parent then joins the application's primary-locale labels before a
|
|
@@ -172,9 +183,90 @@ export class TechnicalDocCompanionService {
|
|
|
172
183
|
hasConfiguredA2aSkills: subprocessOutput.hasConfiguredA2aSkills,
|
|
173
184
|
organizationRoles,
|
|
174
185
|
organizationUnitAwareResources: subprocessOutput.organizationUnitAwareResources,
|
|
186
|
+
...this.resolveApplicationConnectionInputs(technicalDocConfig),
|
|
187
|
+
authentication: this.resolveApplicationAuthenticationInputs(),
|
|
188
|
+
integration: { mcpTools: subprocessOutput.mcpTools, webhookEvents: subprocessOutput.webhookEvents },
|
|
175
189
|
});
|
|
176
190
|
}
|
|
177
191
|
|
|
192
|
+
/**
|
|
193
|
+
* The application facts the documentation names instead of hedging: the product's own name and
|
|
194
|
+
* the base URLs it publishes.
|
|
195
|
+
*
|
|
196
|
+
* The name is what a customer calls the product — `displayName` from `wildo.saas.config.ts`,
|
|
197
|
+
* falling back to the application's `name`. Deliberately NOT `publicMarketingTitle`: that is the documentation SITE's
|
|
198
|
+
* title ("Your Application — Technical Documentation") and reads wrong inside a sentence.
|
|
199
|
+
*
|
|
200
|
+
* The base URLs are the ones the application already authors for its API reference, so the
|
|
201
|
+
* guides and the reference name the same origins by construction.
|
|
202
|
+
*/
|
|
203
|
+
private resolveApplicationConnectionInputs(technicalDocConfig: WildoTechnicalDocConfig): {
|
|
204
|
+
applicationName: string;
|
|
205
|
+
apiServers: readonly ApplicationConnectionServer[];
|
|
206
|
+
} {
|
|
207
|
+
const saasConfig = this.companionContext.saasConfig;
|
|
208
|
+
const applicationName = saasConfig.displayName?.trim() || saasConfig.name.trim();
|
|
209
|
+
if (applicationName.length === 0) {
|
|
210
|
+
throw new Error('technical-documentation requires the application to declare a name (displayName or name in wildo.saas.config.ts)');
|
|
211
|
+
}
|
|
212
|
+
return {
|
|
213
|
+
applicationName,
|
|
214
|
+
apiServers: (technicalDocConfig.apiServers ?? []).map((server) => ({
|
|
215
|
+
url: server.url,
|
|
216
|
+
...(server.description === undefined ? {} : { description: server.description }),
|
|
217
|
+
})),
|
|
218
|
+
};
|
|
219
|
+
}
|
|
220
|
+
|
|
221
|
+
/**
|
|
222
|
+
* The sign-in policy this application actually applies, per user type.
|
|
223
|
+
*
|
|
224
|
+
* Read from `userTypes[<key>].auth`, which is where all authentication policy lives — there are
|
|
225
|
+
* no global defaults. Enabled methods go through `getEnabledMethods`, the same helper the runtime
|
|
226
|
+
* uses, rather than re-reading the boolean-or-object shorthand here; and they are ordered by the
|
|
227
|
+
* engine's own enum so two applications list the same methods in the same order.
|
|
228
|
+
*/
|
|
229
|
+
private resolveApplicationAuthenticationInputs(): ApplicationAuthenticationDocumentationSource {
|
|
230
|
+
const userTypes = Object.entries(this.appConfigService.config.userTypes ?? {}).map(([userTypeKey, definition]) => {
|
|
231
|
+
const auth = definition.auth;
|
|
232
|
+
const enabled = getEnabledMethods(auth.authMethodsEnabled);
|
|
233
|
+
return {
|
|
234
|
+
userTypeKey,
|
|
235
|
+
enabledMethods: Object.values(AuthMethod).filter((method) => enabled.has(method)),
|
|
236
|
+
multifactor: {
|
|
237
|
+
required: auth.mfaPolicy.requireMFA,
|
|
238
|
+
strongRequired: auth.mfaPolicy.requireStrongMFA,
|
|
239
|
+
enrollmentGracePeriodDays: auth.mfaPolicy.enrollmentGracePeriodDays,
|
|
240
|
+
passkeyExemptFromMultifactor: auth.mfaPolicy.passkeyExemptFromMFA,
|
|
241
|
+
...(auth.mfaPolicy.acceptableMFAMethods === undefined ? {} : { acceptableMethods: auth.mfaPolicy.acceptableMFAMethods }),
|
|
242
|
+
},
|
|
243
|
+
password: {
|
|
244
|
+
minLength: auth.passwordPolicy.minLength,
|
|
245
|
+
maxLength: auth.passwordPolicy.maxLength,
|
|
246
|
+
requireUppercase: auth.passwordPolicy.requireUppercase,
|
|
247
|
+
requireLowercase: auth.passwordPolicy.requireLowercase,
|
|
248
|
+
requireNumbers: auth.passwordPolicy.requireNumbers,
|
|
249
|
+
requireSpecialChars: auth.passwordPolicy.requireSpecialChars,
|
|
250
|
+
expiryDays: auth.passwordPolicy.expiryDays,
|
|
251
|
+
},
|
|
252
|
+
session: {
|
|
253
|
+
durationMinutes: auth.sessionDurationMinutes,
|
|
254
|
+
...(auth.maxConcurrentSessions === undefined ? {} : { maxConcurrentSessions: auth.maxConcurrentSessions }),
|
|
255
|
+
},
|
|
256
|
+
lockout: {
|
|
257
|
+
maxLoginAttempts: auth.lockoutPolicy.maxLoginAttempts,
|
|
258
|
+
lockoutDurationMinutes: auth.lockoutPolicy.lockoutDurationMinutes,
|
|
259
|
+
progressive: auth.lockoutPolicy.progressiveLockout,
|
|
260
|
+
maxProgressiveLockoutHours: auth.lockoutPolicy.maxProgressiveLockoutHours,
|
|
261
|
+
},
|
|
262
|
+
};
|
|
263
|
+
});
|
|
264
|
+
if (userTypes.length === 0) {
|
|
265
|
+
throw new Error('technical-documentation requires the application to declare at least one user type');
|
|
266
|
+
}
|
|
267
|
+
return { userTypes };
|
|
268
|
+
}
|
|
269
|
+
|
|
178
270
|
/**
|
|
179
271
|
* Publishes the complete managed documentation tree at stable generated paths.
|
|
180
272
|
* This operation synchronizes the framework-owned consumer documentation into
|
|
@@ -255,6 +347,9 @@ export class TechnicalDocCompanionService {
|
|
|
255
347
|
hasConfiguredA2aSkills: subprocessOutput.hasConfiguredA2aSkills,
|
|
256
348
|
organizationRoles,
|
|
257
349
|
organizationUnitAwareResources: subprocessOutput.organizationUnitAwareResources,
|
|
350
|
+
...this.resolveApplicationConnectionInputs(technicalDocConfig),
|
|
351
|
+
authentication: this.resolveApplicationAuthenticationInputs(),
|
|
352
|
+
integration: { mcpTools: subprocessOutput.mcpTools, webhookEvents: subprocessOutput.webhookEvents },
|
|
258
353
|
});
|
|
259
354
|
const generationInput = this.assembleGenerationInput(subprocessOutput, technicalDocConfig);
|
|
260
355
|
|
|
@@ -548,7 +643,12 @@ export class TechnicalDocCompanionService {
|
|
|
548
643
|
|
|
549
644
|
let loaded: WildoTechnicalDocConfig;
|
|
550
645
|
try {
|
|
551
|
-
|
|
646
|
+
// `freshModuleCache` is what makes the docblock's "evaluated for every request" true. Calling
|
|
647
|
+
// `loadConfig` again is NOT enough on its own: jiti's module cache is process-global, so
|
|
648
|
+
// without this the second evaluation returns the first one's result and a valid taxonomy,
|
|
649
|
+
// server or overview edit stays invisible until an unrelated restart — precisely the outcome
|
|
650
|
+
// the contract above rejects. Same defect as issue #170, different read site.
|
|
651
|
+
loaded = await loadConfig<WildoTechnicalDocConfig>(techDocConfigPath, { freshModuleCache: true });
|
|
552
652
|
} catch (e) {
|
|
553
653
|
throw this.errorBuilder.buildError(ErrorType.CONFIGURATION, undefined, {
|
|
554
654
|
customMessageReference: ErrorCustomMessageReference.CONFIGURATION,
|
|
@@ -64,7 +64,6 @@ export const appShellConfig : AppConfiguration_Frontend['appComponentsConfigurat
|
|
|
64
64
|
responsiveBreakpoint: ViewportBreakpoint.MOBILE,
|
|
65
65
|
responsivePolicy: SidebarResponsivePolicy.BURGER,
|
|
66
66
|
defaultSection: 'main',
|
|
67
|
-
showUncategorized: true,
|
|
68
67
|
// HOME as the app's BRAND HEADER: the generated Your Application symbol + the
|
|
69
68
|
// application display name, pinned above the search trigger and doubling as
|
|
70
69
|
// the home button (so no separate "Home" row renders). The alternatives are
|
|
@@ -129,6 +129,7 @@ export const specificationsCompanionExports: SpecificationsCompanionExports<
|
|
|
129
129
|
* decisions remain private runtime state.
|
|
130
130
|
*/
|
|
131
131
|
documentFactSpecification: applicationDocumentFactSpecification,
|
|
132
|
+
authoredDocumentFactSpecification: applicationAuthoredDocumentFactSpecification,
|
|
132
133
|
/**
|
|
133
134
|
* The accepted typed build plan (`build-plan` family, `BuildPlanTaskGraph`).
|
|
134
135
|
* The bottom-up dispatch playbook's coding owner reads it from the verified
|
|
@@ -140,6 +140,7 @@ export const WildoSaasConfigSchema = z.strictObject({
|
|
|
140
140
|
* empty ARRAY is the different, positive answer — this surface sets nothing of its own.
|
|
141
141
|
*/
|
|
142
142
|
clientStorage: ApplicationClientStorageInventorySchema.optional(),
|
|
143
|
+
operatingJurisdictions: ApplicationOperatingJurisdictionsSchema.optional(),
|
|
143
144
|
operatorComplianceIdentity: ApplicationOperatorComplianceIdentitySchema.optional(),
|
|
144
145
|
providerComplianceChoices: ApplicationProviderComplianceChoicesSchema.optional(),
|
|
145
146
|
|
|
@@ -370,20 +370,29 @@ export interface A11yPolicy {
|
|
|
370
370
|
* disable). When a finite tier is set the surface is also centered in its
|
|
371
371
|
* container (`margin-inline: auto`).
|
|
372
372
|
*/
|
|
373
|
-
export
|
|
374
|
-
|
|
375
|
-
|
|
376
|
-
|
|
377
|
-
|
|
378
|
-
|
|
373
|
+
export const RESPONSIVE_MAX_WIDTH_VALUES = [
|
|
374
|
+
'full',
|
|
375
|
+
'sm',
|
|
376
|
+
'md',
|
|
377
|
+
'lg',
|
|
378
|
+
'xl',
|
|
379
379
|
// Reading-measure cap (~42rem) for single-column FORM / field stacks (T4c),
|
|
380
380
|
// so detail/settings forms stop stretching edge-to-edge inside a wide content
|
|
381
381
|
// zone. Wider than the component tiers (`sm`–`xl`, dialog-scale) but far tighter
|
|
382
382
|
// than `content`/`centered-readable`. Retune via `--measure-max-width`.
|
|
383
|
-
|
|
384
|
-
|
|
385
|
-
|
|
386
|
-
|
|
383
|
+
'measure',
|
|
384
|
+
'centered-readable',
|
|
385
|
+
'content',
|
|
386
|
+
'none',
|
|
387
|
+
] as const;
|
|
388
|
+
|
|
389
|
+
/**
|
|
390
|
+
* The RUNTIME source for the width vocabulary, so a schema that must validate a declared tier can
|
|
391
|
+
* name it instead of re-listing the members. It became necessary the moment width stopped being a
|
|
392
|
+
* surface-only concern: the zone content boundary, `DisplayLayout` and `FormLayout` all select a tier
|
|
393
|
+
* now, and a second hand-written list of the same nine values is a list that drifts.
|
|
394
|
+
*/
|
|
395
|
+
export type ResponsiveMaxWidth = (typeof RESPONSIVE_MAX_WIDTH_VALUES)[number];
|
|
387
396
|
|
|
388
397
|
export type MobileShape = 'inline' | 'drawer' | 'sheet';
|
|
389
398
|
|
|
@@ -73,10 +73,34 @@ export const AppLevelComponentConfigurationSchema = z.object({
|
|
|
73
73
|
z.object({
|
|
74
74
|
placement: z.union([ z.literal(HorizontalPlacement.START), z.literal(HorizontalPlacement.END)]),
|
|
75
75
|
collapsible: z.boolean().default(true),
|
|
76
|
+
/**
|
|
77
|
+
* Does the sidebar start COLLAPSED (the icon rail) rather than expanded?
|
|
78
|
+
*
|
|
79
|
+
* This is the application's STARTING POSITION, not a lock: the rail
|
|
80
|
+
* collapse is a per-machine user preference persisted under
|
|
81
|
+
* `LOCAL_STORAGE_KEYS.SIDEBAR_COLLAPSED`, and a stored preference always
|
|
82
|
+
* wins. So this answers "what does a visitor with no preference yet
|
|
83
|
+
* see", which nothing could express before — the hydration fell back to
|
|
84
|
+
* `false`, making EXPANDED the only reachable default for every
|
|
85
|
+
* application.
|
|
86
|
+
*
|
|
87
|
+
* Pairs with the theme's `SidebarCompactLabelMode`: `ICON_AND_LABEL`
|
|
88
|
+
* renders a wrapping label under each icon in the collapsed rail, so a
|
|
89
|
+
* rail-first shell stays readable rather than becoming a column of
|
|
90
|
+
* unlabelled glyphs.
|
|
91
|
+
*
|
|
92
|
+
* OPTIONAL rather than `.default(false)` for the reason `homeDisplayMode`
|
|
93
|
+
* gives one line below: a Zod default makes the key REQUIRED in the
|
|
94
|
+
* inferred authoring type, forcing every preset and application config to
|
|
95
|
+
* restate an opinion it does not have. The framework default (expanded —
|
|
96
|
+
* the behavior every app had before this axis existed) is applied in
|
|
97
|
+
* `useSidebarBehavior`, which must resolve it there regardless because a
|
|
98
|
+
* sidebar authored as plain `true` never reaches this object branch.
|
|
99
|
+
*/
|
|
100
|
+
defaultCollapsed: z.boolean().optional(),
|
|
76
101
|
responsiveBreakpoint: z.enum(ViewportBreakpoint).default(ViewportBreakpoint.MOBILE),
|
|
77
102
|
responsivePolicy: z.enum(SidebarResponsivePolicy).default(SidebarResponsivePolicy.BURGER),
|
|
78
103
|
defaultSection: z.string().default("main"),
|
|
79
|
-
showUncategorized: z.boolean().default(true),
|
|
80
104
|
/**
|
|
81
105
|
* How the sidebar surfaces HOME — hidden, the pinned brand header
|
|
82
106
|
* (app symbol + name above the search trigger), or a "Home" navigation
|
|
@@ -39,6 +39,45 @@ export interface CompositeViewAuthoringConfig {
|
|
|
39
39
|
* overlays) render the authored icon.
|
|
40
40
|
*/
|
|
41
41
|
icon?: IconLike;
|
|
42
|
+
/**
|
|
43
|
+
* What happens to an ADJACENT zone (secondary / companion) this destination
|
|
44
|
+
* splits into, once that zone's last content is dismissed — overriding the
|
|
45
|
+
* zone's own `onEmpty` while this destination occupies primary.
|
|
46
|
+
*
|
|
47
|
+
* The zone-level `ZoneConfig.onEmpty` is one value for every destination that
|
|
48
|
+
* splits into that zone, and destinations legitimately disagree: a LIST wants
|
|
49
|
+
* the detail pane to stay put (`EMPTY_STATE`) so the layout does not reflow
|
|
50
|
+
* while a reviewer steps through rows, while a CANVAS wants its width back
|
|
51
|
+
* (`COLLAPSE`) the moment nothing is selected. Both share one secondary zone,
|
|
52
|
+
* so without this override one of them is always wrong.
|
|
53
|
+
*
|
|
54
|
+
* Omitted (the common case) defers to the zone, which itself defaults to
|
|
55
|
+
* `ZoneEmptyBehavior.COLLAPSE`. Resolution order is destination → zone →
|
|
56
|
+
* COLLAPSE; see `resolveZoneEmptyBehavior`.
|
|
57
|
+
*/
|
|
58
|
+
adjacentZoneOnEmpty?: ZoneEmptyBehavior;
|
|
59
|
+
/**
|
|
60
|
+
* How wide this destination's content may grow in the zone, in the framework's shared width
|
|
61
|
+
* vocabulary — the SAME `ResponsiveMaxWidth` a Surface, a `DisplayLayout` and a `FormLayout` use.
|
|
62
|
+
*
|
|
63
|
+
* Omitted (the common case) is `'content'`: capped and centred at `var(--content-max-width, 80rem)`,
|
|
64
|
+
* right for a form, a list or a detail page and wrong only for content whose value IS the space it
|
|
65
|
+
* occupies — a board, a wide table, a canvas — which declare `'none'`.
|
|
66
|
+
*/
|
|
67
|
+
zoneContentMaxWidth?: ResponsiveMaxWidth;
|
|
68
|
+
/**
|
|
69
|
+
* Whether this destination's content fills the zone's HEIGHT as well.
|
|
70
|
+
*
|
|
71
|
+
* `true` makes the zone's content boundary a definite-height flex column, so this view's root may use
|
|
72
|
+
* `flex-1 min-h-0` and resolve against something real. Without it a canvas has no intrinsic height
|
|
73
|
+
* and collapses to zero — which is why one had to hand-roll `h-[70vh]`, sizing against the WINDOW
|
|
74
|
+
* rather than the container it sits in. PRIMARY only: an adjacent zone scrolls, so a filling child
|
|
75
|
+
* and a scrolling parent contradict each other.
|
|
76
|
+
*
|
|
77
|
+
* Separate from the width above ON PURPOSE — see `zone-content-geometry.ts` for why the enum that
|
|
78
|
+
* fused them could not express a capped width with a definite height.
|
|
79
|
+
*/
|
|
80
|
+
zoneContentFillsHeight?: boolean;
|
|
42
81
|
}
|
|
43
82
|
|
|
44
83
|
/**
|
|
@@ -94,6 +133,12 @@ export interface CompositeViewDefinition {
|
|
|
94
133
|
* `CoreIconRegistry.compositeView`, keyed by `ref`.
|
|
95
134
|
*/
|
|
96
135
|
icon?: IconLike;
|
|
136
|
+
/** See {@link CompositeViewAuthoringConfig.adjacentZoneOnEmpty}. Mirrored from authoring. */
|
|
137
|
+
adjacentZoneOnEmpty?: ZoneEmptyBehavior;
|
|
138
|
+
/** See {@link CompositeViewAuthoringConfig.zoneContentMaxWidth}. Mirrored from authoring. */
|
|
139
|
+
zoneContentMaxWidth?: ResponsiveMaxWidth;
|
|
140
|
+
/** See {@link CompositeViewAuthoringConfig.zoneContentFillsHeight}. Mirrored from authoring. */
|
|
141
|
+
zoneContentFillsHeight?: boolean;
|
|
97
142
|
}
|
|
98
143
|
|
|
99
144
|
export type AppCompositeViewsConfig = Record<string, CompositeViewAuthoringConfig>;
|
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
# saas.frontend.display-layout.reading-measure
|
|
2
|
+
|
|
3
|
+
## Import Origins
|
|
4
|
+
|
|
5
|
+
- `@wildo-ai/saas-frontend-lib`
|
|
6
|
+
|
|
7
|
+
## Source Excerpts
|
|
8
|
+
|
|
9
|
+
### Origin Package: `@wildo-ai/saas-frontend-lib`
|
|
10
|
+
|
|
11
|
+
```tsx
|
|
12
|
+
export interface DisplayLayoutProps {
|
|
13
|
+
/** Additional CSS classes for the root container. */
|
|
14
|
+
className?: string;
|
|
15
|
+
/**
|
|
16
|
+
* How wide the layout root lets its content grow, named in the framework's own vocabulary.
|
|
17
|
+
*
|
|
18
|
+
* Defaults to `'measure'` — the reading-measure cap (~42rem, themeable via `--measure-max-width`)
|
|
19
|
+
* that keeps a single-column stack of label/value pairs readable instead of stretched edge to edge.
|
|
20
|
+
* That default is right for what this layout was built for and is unchanged.
|
|
21
|
+
*
|
|
22
|
+
* It is WRONG for a composed document. A template that renders tabs, quote blocks, tables or regions
|
|
23
|
+
* is not a field stack: those set their own measure internally, and a 42rem cap around them squeezes
|
|
24
|
+
* the whole composition into a column with dead space beside it. Such a template declares `'none'`.
|
|
25
|
+
*
|
|
26
|
+
* `'none'` is not "uncapped" in practice — the zone content boundary above has already capped the
|
|
27
|
+
* area at the page-content width (`'content'`, ~80rem) and an adjacent pane is narrower still. This
|
|
28
|
+
* prop decides only whether a SECOND, tighter cap applies inside that, and the answer depends on what
|
|
29
|
+
* the template renders, which is why the template is the one asked.
|
|
30
|
+
*/
|
|
31
|
+
responsiveMaxWidth?: ResponsiveMaxWidth;
|
|
32
|
+
children?: ReactNode;
|
|
33
|
+
}
|
|
34
|
+
```
|
|
@@ -0,0 +1,45 @@
|
|
|
1
|
+
# saas.frontend.navigation.operation-override
|
|
2
|
+
|
|
3
|
+
## Import Origins
|
|
4
|
+
|
|
5
|
+
- `@wildo-ai/saas-frontend-lib`
|
|
6
|
+
|
|
7
|
+
## Source Excerpts
|
|
8
|
+
|
|
9
|
+
### Origin Package: `@wildo-ai/saas-frontend-lib`
|
|
10
|
+
|
|
11
|
+
```typescript
|
|
12
|
+
*
|
|
13
|
+
* Per-operation navigation chrome: transition, overlay/split appearance, source zone.
|
|
14
|
+
*
|
|
15
|
+
* **How to use:** attach fragments of this shape under
|
|
16
|
+
* `ResourceOperationFrontendConfig.navigationOverrides` in `resourceUIBehavior()`.
|
|
17
|
+
* Each override applies when navigating **from** the configured zone/viewport into
|
|
18
|
+
* this operation. Prefer mirroring a sibling resource that already matches the
|
|
19
|
+
* product’s overlay vs split behavior.
|
|
20
|
+
*/
|
|
21
|
+
export const NavigationOperationOverrideSchema = z.object({
|
|
22
|
+
transition: TransitionConfigSchema,
|
|
23
|
+
appearance: viewportDiscriminatedSchema(z.union([
|
|
24
|
+
z.enum(OverlayAppearance),
|
|
25
|
+
z.enum(SplitAppearance),
|
|
26
|
+
])).optional(),
|
|
27
|
+
fromZone: z.union([z.enum(NavigationZoneName), z.literal('appLevel')]).optional(),
|
|
28
|
+
viewport: z.enum(ViewportBreakpoint).optional(),
|
|
29
|
+
/**
|
|
30
|
+
* Behaviour of the OVERLAY this override resolves to — whether the page behind stays interactive,
|
|
31
|
+
* whether touching it dismisses, whether it is dimmed. Ignored for non-overlay transitions.
|
|
32
|
+
*
|
|
33
|
+
* These three were already declared on `OverlayContainerConfig` with documented defaults and read by
|
|
34
|
+
* nothing; they are honoured now, and this is the channel that lets a NAVIGATION-driven overlay set
|
|
35
|
+
* them. Declared per operation because it describes the CONTENT: an application legitimately has a
|
|
36
|
+
* create dialog that blocks everything and a detail sheet beside a live canvas that blocks nothing.
|
|
37
|
+
*/
|
|
38
|
+
overlayBehavior: z.object({
|
|
39
|
+
modal: z.boolean().optional(),
|
|
40
|
+
closeOnOutsideClick: z.boolean().optional(),
|
|
41
|
+
showBackdrop: z.boolean().optional(),
|
|
42
|
+
}).optional(),
|
|
43
|
+
});
|
|
44
|
+
export type NavigationOperationOverride = z.infer<typeof NavigationOperationOverrideSchema>;
|
|
45
|
+
```
|
|
@@ -0,0 +1,65 @@
|
|
|
1
|
+
# saas.frontend.public-shell.identity-mode
|
|
2
|
+
|
|
3
|
+
## Import Origins
|
|
4
|
+
|
|
5
|
+
- `@wildo-ai/saas-frontend-lib`
|
|
6
|
+
|
|
7
|
+
## Source Excerpts
|
|
8
|
+
|
|
9
|
+
### Origin Package: `@wildo-ai/saas-frontend-lib`
|
|
10
|
+
|
|
11
|
+
```typescript
|
|
12
|
+
*
|
|
13
|
+
* Whether the PUBLIC (unauthenticated) pages present the application's identity.
|
|
14
|
+
*
|
|
15
|
+
* Declare it beside your other frontend configuration and pass it to
|
|
16
|
+
* `buildFrontendModuleConfigOverrides` in `frontend/src/modules-registry.frontend.ts`, alongside
|
|
17
|
+
* `navigationLayout`, `homeDefinition` and `errorPageConfig`:
|
|
18
|
+
*
|
|
19
|
+
* ```ts
|
|
20
|
+
* import { PublicShellIdentityMode } from '@wildo-ai/saas-frontend-lib';
|
|
21
|
+
*
|
|
22
|
+
* frontendConfigOverrides: buildFrontendModuleConfigOverrides({
|
|
23
|
+
* // …navigationLayout, designSystemConfiguration, homeDefinition, errorPageConfig
|
|
24
|
+
* publicShellIdentityMode: PublicShellIdentityMode.BRAND_HEADER,
|
|
25
|
+
* }),
|
|
26
|
+
* ```
|
|
27
|
+
*
|
|
28
|
+
* It is NOT an `ApplicationLevelComponentType` key: it does not belong in
|
|
29
|
+
* `frontend/src/config/app-shell.config.ts`, and putting it there configures nothing at all. Those
|
|
30
|
+
* keys describe the AUTHENTICATED shell (menubar, sidebar, status bar); the pages this governs
|
|
31
|
+
* render before any of that exists.
|
|
32
|
+
*
|
|
33
|
+
* Login, registration, invitation acceptance, e-mail confirmation, password reset, the MFA
|
|
34
|
+
* challenge and the OAuth consent screens are the first thing a person ever sees of an application,
|
|
35
|
+
* and they are also the pages most likely to be reached from a link — an e-mail, a chat message, a
|
|
36
|
+
* bookmark — with no surrounding context saying what they belong to. Naming the surface there is
|
|
37
|
+
* conventional (Stripe, Linear, GitHub, Slack all do it) and it is the difference between "sign in"
|
|
38
|
+
* and "sign in to WHAT".
|
|
39
|
+
*
|
|
40
|
+
* OPT-IN, and {@link HIDDEN} is the framework default, for the same reason the sidebar's home mode
|
|
41
|
+
* defaults to a navigation row rather than a brand header: showing an identity assumes the surface
|
|
42
|
+
* HAS one worth showing, and an application that has generated no brand yet would get its technical
|
|
43
|
+
* `appName` printed over its login form. An application says when it is ready.
|
|
44
|
+
*
|
|
45
|
+
* Mirrors {@link SidebarHomeDisplayMode} deliberately — same question ("how is this product's
|
|
46
|
+
* identity surfaced here"), same answer shape, so an author who has met one already knows this one.
|
|
47
|
+
*/
|
|
48
|
+
export enum PublicShellIdentityMode {
|
|
49
|
+
/**
|
|
50
|
+
* Public pages carry no identity. The framework default, and the behavior of every application
|
|
51
|
+
* that does not mention this field.
|
|
52
|
+
*/
|
|
53
|
+
HIDDEN = 'hidden',
|
|
54
|
+
/**
|
|
55
|
+
* The identity at the top of the public card, above the form's own heading: the mark when one
|
|
56
|
+
* resolves, and the name.
|
|
57
|
+
*
|
|
58
|
+
* What actually renders is decided from the DATA, not from this mode — an application with no
|
|
59
|
+
* generated brand shows its name alone, and a brand whose mark is a wordmark or lockup shows the
|
|
60
|
+
* mark alone, because such a mark already contains the name. So this mode is a permission, never
|
|
61
|
+
* a promise that a logo exists.
|
|
62
|
+
*/
|
|
63
|
+
BRAND_HEADER = 'brand_header',
|
|
64
|
+
}
|
|
65
|
+
```
|