@wildo-ai/framework-knowledge 1.1.1 → 1.1.3
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 +271 -8
- 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 +13 -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/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +45 -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 +6 -7
- 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 +6 -6
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -4
- 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 -2
- 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 -4
- 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 -2
- 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 +3 -9
- 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 -3
- 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 +10 -6
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +25 -4
- 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 -5
- 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 -3
- 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 -2
- 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 -2
- 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 -2
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -14
- 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 -5
- 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 -4
- 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 -8
- 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 -2
- 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 -8
- 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 -2
- 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 +52 -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 +75 -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 +91 -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 +29 -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 +28 -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 -45
- 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 -54
- 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 +30 -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 +25 -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 -9
- 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 -5
- 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 -9
- 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 -2
- 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 -8
- 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 -2
- 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 -8
- 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 -2
- 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 -8
- 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 -4
- 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 -4
- 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 -2
- 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 -6
- 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 -5
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/manifest.json +6 -7
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +7 -47
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +6 -13
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +1 -82
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +11 -6
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -5
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +3 -4
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +3 -4
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +15 -735
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +11 -7
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +16 -123
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +15 -8
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +10 -4
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +10 -4
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +12 -5
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +10 -4
- 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 +39 -21
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +2 -6
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +10 -4
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +1 -1
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +11 -5
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +11 -5
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +10 -4
- package/dist/knowledge/references/build-plan.task-graph.config.md +1 -45
- package/dist/knowledge/references/example.config.app-shell.full.md +4 -0
- 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 -50
- package/dist/knowledge/references/saas.external-data.admin-endpoints.md +48 -0
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +10 -6
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +1 -0
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +0 -109
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -137
- package/dist/knowledge/references/saas.models.http-api-binding.md +29 -3
- 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 +1 -1
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +0 -36
- 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 -1
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +1 -1
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +0 -1
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +11 -48
- package/dist/knowledge/registries/playbooks.json +11 -74
- package/dist/knowledge/registries/source-tags.json +538 -622
- package/dist/knowledge/skills/INDEX.md +0 -1
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -16
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +8 -26
- 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 +21 -36
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +19 -49
- package/dist/knowledge/skills/config-app-shell/SKILL.md +8 -6
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +11 -6
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +0 -50
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +0 -7
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +0 -36
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +0 -36
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +0 -36
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +0 -109
- 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 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +2 -157
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +0 -109
- 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-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-zod-lifecycle-and-chainable-api.md +0 -26
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +1 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +0 -109
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +1 -1
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +0 -36
- package/dist/knowledge/topic-index.json +128 -285
- 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
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +0 -185
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +0 -66
- 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 -40
- package/dist/knowledge/playbooks/top_down.market-research/method.md +0 -68
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -42
- 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 -69
- package/dist/knowledge/references/placement-plan.config.md +0 -330
- 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/zod.decorators.data-categories.md +0 -197
- package/dist/knowledge/rules/resource-schema-awareness.md +0 -77
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +0 -622
- 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
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@wildo-ai/framework-knowledge",
|
|
3
|
-
"version": "1.1.
|
|
3
|
+
"version": "1.1.3",
|
|
4
4
|
"license": "SEE LICENSE IN LICENSE",
|
|
5
5
|
"description": "Published framework knowledge artifacts and typed loaders for Wildo AI",
|
|
6
6
|
"author": "Wildo AI",
|
|
@@ -19,8 +19,8 @@
|
|
|
19
19
|
"dist/"
|
|
20
20
|
],
|
|
21
21
|
"dependencies": {
|
|
22
|
-
"@wildo-ai/saas-models": "1.1.
|
|
23
|
-
"@wildo-ai/saas-specifications": "1.1.
|
|
22
|
+
"@wildo-ai/saas-models": "1.1.3",
|
|
23
|
+
"@wildo-ai/saas-specifications": "1.1.3"
|
|
24
24
|
},
|
|
25
25
|
"scripts": {
|
|
26
26
|
"build": "tsc -p tsconfig.build.json && node ../../../scripts/run-tsc-alias-safe.mjs --project tsconfig.build.json --dist dist/esm",
|
|
@@ -34,7 +34,7 @@
|
|
|
34
34
|
},
|
|
35
35
|
"devDependencies": {
|
|
36
36
|
"@types/node": "^24.0.15",
|
|
37
|
-
"@wildo-ai/saas-backend-lib": "1.1.
|
|
37
|
+
"@wildo-ai/saas-backend-lib": "1.1.3",
|
|
38
38
|
"rimraf": "^6.0.1",
|
|
39
39
|
"tsc-alias": "1.8.16",
|
|
40
40
|
"tsc-watch": "7.2.1",
|
package/dist/esm/.builder.pid
DELETED
|
@@ -1,9 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": 1,
|
|
3
|
-
"writerPid": 95187,
|
|
4
|
-
"orchestratorPid": 94847,
|
|
5
|
-
"orchestratorSessionId": null,
|
|
6
|
-
"orchestratorStartedAt": "Mon Aug 31 09:18:19 2026",
|
|
7
|
-
"distDirectory": "/Users/paulcayon/Projects/Wildo.ai/dev/wildo-ai/platform/factory/framework-knowledge/dist/esm",
|
|
8
|
-
"acquiredAt": "2026-08-31T07:18:20.789Z"
|
|
9
|
-
}
|
|
@@ -1,185 +0,0 @@
|
|
|
1
|
-
# Placement Plan — Where Each Thing Belongs in the Shell, and Why
|
|
2
|
-
|
|
3
|
-
### Target Application Framing
|
|
4
|
-
|
|
5
|
-
This knowledge is for configuring behavior in the target application.
|
|
6
|
-
Wildo is the framework surface being used, not the product being built.
|
|
7
|
-
|
|
8
|
-
Read and apply these patterns from the application-developer point of view:
|
|
9
|
-
|
|
10
|
-
- how the application should configure the relevant app-level file
|
|
11
|
-
- how the application should use framework-provided factories, enums, and helpers
|
|
12
|
-
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
> **This is a v1 methodology.** The criteria below are deliberately explicit so
|
|
16
|
-
> they can be tuned against real runs. What is NOT provisional is the shape of the
|
|
17
|
-
> output: a decision per subject, on a named surface, with a rationale.
|
|
18
|
-
|
|
19
|
-
## Where you are in the journey
|
|
20
|
-
|
|
21
|
-
You run in the **bottom-up phase**, after the **domain plan** exists and **before**
|
|
22
|
-
the build is decomposed. By now the application knows what its modules and resources
|
|
23
|
-
ARE; what nobody has decided is **where any of it appears**.
|
|
24
|
-
|
|
25
|
-
That order matters and was corrected during authoring. Placing things *after* the
|
|
26
|
-
build plan reads natural — you would know every task — but `bottom_up.build-decompose`
|
|
27
|
-
is what PRODUCES the build plan and it consumes this one to emit the placement tasks.
|
|
28
|
-
Requiring its output would be a cycle. It is also the better order on its own merits:
|
|
29
|
-
placement is a design decision that should INFORM the decomposition, not trail it. You
|
|
30
|
-
do not need the task graph to know that a `deals` resource will have a list.
|
|
31
|
-
|
|
32
|
-
That question used to have no owner. The framework shipped a placed settings rail,
|
|
33
|
-
so an application could not add, remove, reorder or rename a section without the
|
|
34
|
-
framework agreeing — and the application's own config file did not tell you what a
|
|
35
|
-
user would see. Placement is now the application's, which means somebody has to
|
|
36
|
-
decide it. That is this playbook.
|
|
37
|
-
|
|
38
|
-
## What this playbook does
|
|
39
|
-
|
|
40
|
-
You produce a **placement plan**: for every subject, one decision per surface.
|
|
41
|
-
|
|
42
|
-
A **subject** is one of three things:
|
|
43
|
-
|
|
44
|
-
- an **engine settings destination**, named by its ref from the engine catalog
|
|
45
|
-
(`profile`, `security`, `billing`, `sso`, …) — the engine owns what each MEANS
|
|
46
|
-
(its target, its required roles, its entitlement); it owns nothing about where it
|
|
47
|
-
goes;
|
|
48
|
-
- a **resource operation** — a resource's LIST, its READ, a custom verb;
|
|
49
|
-
- an **application view** — composite, chart, execution, full-custom.
|
|
50
|
-
|
|
51
|
-
A **surface** is one of four:
|
|
52
|
-
|
|
53
|
-
| surface | grouped by | authoring home |
|
|
54
|
-
|---|---|---|
|
|
55
|
-
| `SETTINGS_HUB` | a rail **category** | `frontend/src/config/settings-hub.config.ts` |
|
|
56
|
-
| `SIDEBAR` | a sidebar **section** | `appShellConfig[SIDEBAR].contentSections` |
|
|
57
|
-
| `USER_MENU` | flat | the user dropdown's settings entries |
|
|
58
|
-
| `COMMAND_MENU` | flat | the command palette |
|
|
59
|
-
|
|
60
|
-
A subject may legitimately be placed on **several** surfaces — billing is a settings
|
|
61
|
-
rail section AND answers to the command palette. One decision per (subject, surface);
|
|
62
|
-
two placements of one subject on ONE surface is a contradiction and the validator
|
|
63
|
-
refuses it.
|
|
64
|
-
|
|
65
|
-
## Decline explicitly; never omit
|
|
66
|
-
|
|
67
|
-
Every decision is `PLACED` or `DECLINED`, and **both require a rationale**.
|
|
68
|
-
|
|
69
|
-
This is the rule most worth getting right. A subject recorded as `DECLINED` is a
|
|
70
|
-
decision a later reader can disagree with. A subject simply missing from the plan is
|
|
71
|
-
a **coverage gap** — nobody looked. If those two were the same thing, "we considered
|
|
72
|
-
the audit log and this app has no compliance audience" would be indistinguishable
|
|
73
|
-
from forgetting the audit log existed.
|
|
74
|
-
|
|
75
|
-
So: if a destination should not appear anywhere in this application, say so, and say
|
|
76
|
-
why.
|
|
77
|
-
|
|
78
|
-
## The criteria, in the order you apply them
|
|
79
|
-
|
|
80
|
-
1. **Scope correctness.** A thing that acts on the whole organization does not sit
|
|
81
|
-
among a person's own preferences, and the reverse. This is first because it is
|
|
82
|
-
the only criterion that is objectively *wrong* rather than debatable.
|
|
83
|
-
2. **Findability.** Would the user who wants this look here FIRST — unprompted?
|
|
84
|
-
Not "would they accept it once shown". Those are different tests and only the
|
|
85
|
-
first one predicts behaviour.
|
|
86
|
-
3. **Grouping coherence.** Everything in a group answers one question a user
|
|
87
|
-
actually asks. A group that needs "and other things" in its name is two groups.
|
|
88
|
-
4. **Convention fit.** Users arrive with expectations already formed by comparable
|
|
89
|
-
products. A novel arrangement must EARN the cost of surprising them.
|
|
90
|
-
5. **Depth discipline.** One more level of nesting must buy more than it costs. A
|
|
91
|
-
section reachable only after three guesses is not placed, it is hidden.
|
|
92
|
-
|
|
93
|
-
Reject placements justified by implementation convenience ("it renders there
|
|
94
|
-
already"), by the shape of the data model rather than the user's task, or by symmetry
|
|
95
|
-
for its own sake. Surfacing something everywhere is a **cost**, not thoroughness.
|
|
96
|
-
|
|
97
|
-
## Groups carry a purpose, and the purpose is load-bearing
|
|
98
|
-
|
|
99
|
-
When you declare a group, state its `purpose` in product terms. It is not decoration:
|
|
100
|
-
it is what grounds the generated `settings_hub.categories.<ref>.label` and
|
|
101
|
-
`sidebar_sections.<ref>.title` labels in authored intent. Without it a model invents
|
|
102
|
-
filler from the ref alone — which is exactly how a sidebar section came to be
|
|
103
|
-
described as "various tools and utilities".
|
|
104
|
-
|
|
105
|
-
## What you do NOT do
|
|
106
|
-
|
|
107
|
-
- **You do not author configuration.** Turning a decision into
|
|
108
|
-
`settings-hub.config.ts` or `app-shell.config.ts` is a coding task the build lane
|
|
109
|
-
dispatches through the `settings-placement-authoring` skill. If you catch yourself
|
|
110
|
-
writing a config key, a file path or a label string, stop.
|
|
111
|
-
- **You do not invent destination refs.** They come from the engine catalog and the
|
|
112
|
-
workspace, read as workspace truth. A ref you invented resolves to nothing and the
|
|
113
|
-
validator refuses it as an unknown subject.
|
|
114
|
-
- **You do not decide what a destination MEANS.** Its target, roles and entitlement
|
|
115
|
-
are the engine's. You decide only where it sits.
|
|
116
|
-
- **You do not re-open the build plan.** What is being built is settled.
|
|
117
|
-
|
|
118
|
-
## Verification
|
|
119
|
-
|
|
120
|
-
- Every subject the workspace offers is either PLACED or DECLINED — nothing omitted.
|
|
121
|
-
- No subject placed twice on one surface.
|
|
122
|
-
- Every grouped placement names a group this plan declares, for that same surface.
|
|
123
|
-
- Every group has something in it.
|
|
124
|
-
- Every decision, both arms, carries a rationale that would satisfy a reader who
|
|
125
|
-
disagrees with it.
|
|
126
|
-
|
|
127
|
-
## WHO decides — a panel, not you alone and not the creator
|
|
128
|
-
|
|
129
|
-
**The creator does not choose placement.** This playbook convenes an expert panel and
|
|
130
|
-
takes its winner.
|
|
131
|
-
|
|
132
|
-
Concretely, on every run: three candidate arrangements are generated independently
|
|
133
|
-
against this brief, each schema-valid before anyone sees it and each told to take a
|
|
134
|
-
genuinely different position; the **information-architect** derives the rubric (it
|
|
135
|
-
owns the domain); it and the **design-system-guardian** review every candidate; the
|
|
136
|
-
guardian coordinates, shortlists, and synthesises a winner. What lands is that winner.
|
|
137
|
-
|
|
138
|
-
Two consequences for how you write:
|
|
139
|
-
|
|
140
|
-
- **Take a position and commit to it.** You are one candidate among three, and the
|
|
141
|
-
panel cannot compare three hedged arrangements. State what your arrangement makes
|
|
142
|
-
WORSE — an arrangement with no cost has not been thought about, and the reviewers
|
|
143
|
-
are instructed to notice.
|
|
144
|
-
- **The rationale on each decision is the durable part.** It is what a creator asking
|
|
145
|
-
"why is Billing under Organization?" reads, and it is the only trace of the argument
|
|
146
|
-
once the winner has landed.
|
|
147
|
-
|
|
148
|
-
**Fail-closed on charters.** Every panel role needs a committed charter, and the
|
|
149
|
-
companion indexes agents at startup — a charter accepted after boot has no agent until
|
|
150
|
-
a restart, and the error says exactly that. The run does NOT quietly degrade to a
|
|
151
|
-
single generation: an artifact carrying a panel's authority over a decision no panel
|
|
152
|
-
saw is the worst outcome available here, so fewer than two usable candidates returns
|
|
153
|
-
to the ordinary retry instead.
|
|
154
|
-
|
|
155
|
-
## And when the placement is wrong
|
|
156
|
-
|
|
157
|
-
Two different things can change, and conflating them is how a plan starts lying.
|
|
158
|
-
|
|
159
|
-
**The config file** — `settings-hub.config.ts`, `app-shell.config.ts` — is what actually
|
|
160
|
-
renders. A creator who disagrees edits it directly. That works today, needs no companion,
|
|
161
|
-
and is a git commit, which is the accepted state.
|
|
162
|
-
|
|
163
|
-
**The plan** is the decision record, and it is what a later reader consults to ask why.
|
|
164
|
-
It can be changed two ways:
|
|
165
|
-
|
|
166
|
-
- **Re-run this playbook.** The panel deliberates again and the landing REPLACES the
|
|
167
|
-
existing file. Nothing refuses it; that is the design.
|
|
168
|
-
- **Edit the landed plan.** It is an application-owned source like any other.
|
|
169
|
-
|
|
170
|
-
Either way, a decision that no longer reflects the panel must say so. Set its `origin`
|
|
171
|
-
to `REVISED` and record what the panel had decided in `supersedes.rationale`. Both are
|
|
172
|
-
required together — the schema refuses a `REVISED` decision with nothing superseded, and
|
|
173
|
-
refuses a `DELIBERATED` one that supersedes something, because no panel run produces
|
|
174
|
-
either shape.
|
|
175
|
-
|
|
176
|
-
**Why the artifact carries this when git already records the change.** Git knows who
|
|
177
|
-
changed the line, when, and with what message, and that is not being duplicated here. What
|
|
178
|
-
git cannot tell someone READING the file — in an editor, asking "why is Billing under
|
|
179
|
-
Account?" — is that this particular decision is no longer the panel's. Without it, the
|
|
180
|
-
`rationale` field goes on asserting panel reasoning for a decision the panel never took,
|
|
181
|
-
and there is no way to notice.
|
|
182
|
-
|
|
183
|
-
Do not paraphrase the panel's rationale into the new one. A `supersedes.rationale` that
|
|
184
|
-
repeats the decision's own text word for word satisfies the schema and tells a reader
|
|
185
|
-
nothing; the validator reports it as an authoring warning.
|
|
@@ -1,66 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"ref": "bottom_up.placement-plan",
|
|
3
|
-
"version": "0.1.0",
|
|
4
|
-
"phase": "bottom_up",
|
|
5
|
-
"intent": "Decide WHERE every settings destination, resource operation and application view sits in the application shell, and WHY. Reads the domain plan (the modules, their resources and what they mean) and the requirements (which tasks matter), and produces a PLACEMENT PLAN: for each subject, either a PLACED decision naming one surface (the settings hub rail, the sidebar, the user menu, the command palette) and its address on that surface, or an explicit DECLINED decision with a reason. Both carry a rationale. It also declares the GROUPS that should exist on the grouped surfaces (settings rail categories, sidebar sections) with the product purpose behind each, which is what grounds their generated labels in authored intent instead of filler. This playbook DECIDES placement; it does NOT author configuration — turning a decision into `frontend/src/config/settings-hub.config.ts` and `app-shell.config.ts` is a coding task the build lane dispatches through the `settings-placement-authoring` skill. It runs BEFORE build-decompose, which consumes the plan and emits those tasks — the reverse order would be a cycle, since build-decompose is what produces the build plan. It writes no TypeScript, invents no destination refs, and authors no labels. It exists because the alternative is the framework defaulting placement, which is what made an application's settings rail unauthorable: nothing is placed implicitly, so a subject nobody decided about is a visible coverage gap rather than a silent framework default.",
|
|
6
|
-
"functionalTopics": [
|
|
7
|
-
"shape_user_experience"
|
|
8
|
-
],
|
|
9
|
-
"preconditions": [
|
|
10
|
-
{
|
|
11
|
-
"kind": "phase_is",
|
|
12
|
-
"phase": "bottom_up"
|
|
13
|
-
},
|
|
14
|
-
{
|
|
15
|
-
"kind": "artifact_exists",
|
|
16
|
-
"selector": {
|
|
17
|
-
"family": "domain-plan"
|
|
18
|
-
}
|
|
19
|
-
}
|
|
20
|
-
],
|
|
21
|
-
"inputs": [
|
|
22
|
-
{
|
|
23
|
-
"family": "domain-plan"
|
|
24
|
-
},
|
|
25
|
-
{
|
|
26
|
-
"family": "requirements"
|
|
27
|
-
}
|
|
28
|
-
],
|
|
29
|
-
"outputs": [
|
|
30
|
-
{
|
|
31
|
-
"family": "placement-plan",
|
|
32
|
-
"schemaRef": "saas-specifications:PlacementPlan",
|
|
33
|
-
"description": "The placement decision — `groups[]` (the containers that should exist on the grouped surfaces, each with the product purpose behind it) plus `decisions[]` (one per subject PER SURFACE: a stable `decisionRef`, the `PlacementSubject` being placed — an engine settings destination by ref, a resource operation, or an app view — a `PlacementDisposition` of PLACED or DECLINED, the surface-discriminated `PlacementAddress` when placed, and a REQUIRED `rationale` on both arms). Each decision also carries a REQUIRED `origin` — `DELIBERATED` or `REVISED` — which the trusted runtime stamps `DELIBERATED`; it is not representable in the provider-facing generation shape, because a panel run IS the panel's judgement and a model cannot declare its own output a human revision. A later edit that changes a decision sets `origin: REVISED` and records the panel's own reasoning in `supersedes.rationale`, so the artifact stops asserting panel reasoning for a decision the panel never took. Typed by the `_core` `placement-plan` family (`PlacementPlan`); the provider answers the strict `PlacementPlanGeneration` shape and the trusted runtime stamps refs and version. `validatePlacementPlan` is the deterministic validator: one subject placed twice on the SAME surface is a hard floor (the plan contradicts itself), while an empty group and an order collision are authoring warnings. Its coverage checks run only when the caller supplies the destination catalog, so a run without one reports no coverage result rather than a clean one. The plan carries no file path, config key or label string — those belong to the coding task that authors the config."
|
|
34
|
-
}
|
|
35
|
-
],
|
|
36
|
-
"stepOutputs": [],
|
|
37
|
-
"method": {
|
|
38
|
-
"guidance": "# Placement Plan — Where Each Thing Belongs in the Shell, and Why\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 methodology.** The criteria below are deliberately explicit so\n> they can be tuned against real runs. What is NOT provisional is the shape of the\n> output: a decision per subject, on a named surface, with a rationale.\n\n## Where you are in the journey\n\nYou run in the **bottom-up phase**, after the **domain plan** exists and **before**\nthe build is decomposed. By now the application knows what its modules and resources\nARE; what nobody has decided is **where any of it appears**.\n\nThat order matters and was corrected during authoring. Placing things *after* the\nbuild plan reads natural — you would know every task — but `bottom_up.build-decompose`\nis what PRODUCES the build plan and it consumes this one to emit the placement tasks.\nRequiring its output would be a cycle. It is also the better order on its own merits:\nplacement is a design decision that should INFORM the decomposition, not trail it. You\ndo not need the task graph to know that a `deals` resource will have a list.\n\nThat question used to have no owner. The framework shipped a placed settings rail,\nso an application could not add, remove, reorder or rename a section without the\nframework agreeing — and the application's own config file did not tell you what a\nuser would see. Placement is now the application's, which means somebody has to\ndecide it. That is this playbook.\n\n## What this playbook does\n\nYou produce a **placement plan**: for every subject, one decision per surface.\n\nA **subject** is one of three things:\n\n- an **engine settings destination**, named by its ref from the engine catalog\n (`profile`, `security`, `billing`, `sso`, …) — the engine owns what each MEANS\n (its target, its required roles, its entitlement); it owns nothing about where it\n goes;\n- a **resource operation** — a resource's LIST, its READ, a custom verb;\n- an **application view** — composite, chart, execution, full-custom.\n\nA **surface** is one of four:\n\n| surface | grouped by | authoring home |\n|---|---|---|\n| `SETTINGS_HUB` | a rail **category** | `frontend/src/config/settings-hub.config.ts` |\n| `SIDEBAR` | a sidebar **section** | `appShellConfig[SIDEBAR].contentSections` |\n| `USER_MENU` | flat | the user dropdown's settings entries |\n| `COMMAND_MENU` | flat | the command palette |\n\nA subject may legitimately be placed on **several** surfaces — billing is a settings\nrail section AND answers to the command palette. One decision per (subject, surface);\ntwo placements of one subject on ONE surface is a contradiction and the validator\nrefuses it.\n\n## Decline explicitly; never omit\n\nEvery decision is `PLACED` or `DECLINED`, and **both require a rationale**.\n\nThis is the rule most worth getting right. A subject recorded as `DECLINED` is a\ndecision a later reader can disagree with. A subject simply missing from the plan is\na **coverage gap** — nobody looked. If those two were the same thing, \"we considered\nthe audit log and this app has no compliance audience\" would be indistinguishable\nfrom forgetting the audit log existed.\n\nSo: if a destination should not appear anywhere in this application, say so, and say\nwhy.\n\n## The criteria, in the order you apply them\n\n1. **Scope correctness.** A thing that acts on the whole organization does not sit\n among a person's own preferences, and the reverse. This is first because it is\n the only criterion that is objectively *wrong* rather than debatable.\n2. **Findability.** Would the user who wants this look here FIRST — unprompted?\n Not \"would they accept it once shown\". Those are different tests and only the\n first one predicts behaviour.\n3. **Grouping coherence.** Everything in a group answers one question a user\n actually asks. A group that needs \"and other things\" in its name is two groups.\n4. **Convention fit.** Users arrive with expectations already formed by comparable\n products. A novel arrangement must EARN the cost of surprising them.\n5. **Depth discipline.** One more level of nesting must buy more than it costs. A\n section reachable only after three guesses is not placed, it is hidden.\n\nReject placements justified by implementation convenience (\"it renders there\nalready\"), by the shape of the data model rather than the user's task, or by symmetry\nfor its own sake. Surfacing something everywhere is a **cost**, not thoroughness.\n\n## Groups carry a purpose, and the purpose is load-bearing\n\nWhen you declare a group, state its `purpose` in product terms. It is not decoration:\nit is what grounds the generated `settings_hub.categories.<ref>.label` and\n`sidebar_sections.<ref>.title` labels in authored intent. Without it a model invents\nfiller from the ref alone — which is exactly how a sidebar section came to be\ndescribed as \"various tools and utilities\".\n\n## What you do NOT do\n\n- **You do not author configuration.** Turning a decision into\n `settings-hub.config.ts` or `app-shell.config.ts` is a coding task the build lane\n dispatches through the `settings-placement-authoring` skill. If you catch yourself\n writing a config key, a file path or a label string, stop.\n- **You do not invent destination refs.** They come from the engine catalog and the\n workspace, read as workspace truth. A ref you invented resolves to nothing and the\n validator refuses it as an unknown subject.\n- **You do not decide what a destination MEANS.** Its target, roles and entitlement\n are the engine's. You decide only where it sits.\n- **You do not re-open the build plan.** What is being built is settled.\n\n## Verification\n\n- Every subject the workspace offers is either PLACED or DECLINED — nothing omitted.\n- No subject placed twice on one surface.\n- Every grouped placement names a group this plan declares, for that same surface.\n- Every group has something in it.\n- Every decision, both arms, carries a rationale that would satisfy a reader who\n disagrees with it.\n\n## WHO decides — a panel, not you alone and not the creator\n\n**The creator does not choose placement.** This playbook convenes an expert panel and\ntakes its winner.\n\nConcretely, on every run: three candidate arrangements are generated independently\nagainst this brief, each schema-valid before anyone sees it and each told to take a\ngenuinely different position; the **information-architect** derives the rubric (it\nowns the domain); it and the **design-system-guardian** review every candidate; the\nguardian coordinates, shortlists, and synthesises a winner. What lands is that winner.\n\nTwo consequences for how you write:\n\n- **Take a position and commit to it.** You are one candidate among three, and the\n panel cannot compare three hedged arrangements. State what your arrangement makes\n WORSE — an arrangement with no cost has not been thought about, and the reviewers\n are instructed to notice.\n- **The rationale on each decision is the durable part.** It is what a creator asking\n \"why is Billing under Organization?\" reads, and it is the only trace of the argument\n once the winner has landed.\n\n**Fail-closed on charters.** Every panel role needs a committed charter, and the\ncompanion indexes agents at startup — a charter accepted after boot has no agent until\na restart, and the error says exactly that. The run does NOT quietly degrade to a\nsingle generation: an artifact carrying a panel's authority over a decision no panel\nsaw is the worst outcome available here, so fewer than two usable candidates returns\nto the ordinary retry instead.\n\n## And when the placement is wrong\n\nTwo different things can change, and conflating them is how a plan starts lying.\n\n**The config file** — `settings-hub.config.ts`, `app-shell.config.ts` — is what actually\nrenders. A creator who disagrees edits it directly. That works today, needs no companion,\nand is a git commit, which is the accepted state.\n\n**The plan** is the decision record, and it is what a later reader consults to ask why.\nIt can be changed two ways:\n\n- **Re-run this playbook.** The panel deliberates again and the landing REPLACES the\n existing file. Nothing refuses it; that is the design.\n- **Edit the landed plan.** It is an application-owned source like any other.\n\nEither way, a decision that no longer reflects the panel must say so. Set its `origin`\nto `REVISED` and record what the panel had decided in `supersedes.rationale`. Both are\nrequired together — the schema refuses a `REVISED` decision with nothing superseded, and\nrefuses a `DELIBERATED` one that supersedes something, because no panel run produces\neither shape.\n\n**Why the artifact carries this when git already records the change.** Git knows who\nchanged the line, when, and with what message, and that is not being duplicated here. What\ngit cannot tell someone READING the file — in an editor, asking \"why is Billing under\nAccount?\" — is that this particular decision is no longer the panel's. Without it, the\n`rationale` field goes on asserting panel reasoning for a decision the panel never took,\nand there is no way to notice.\n\nDo not paraphrase the panel's rationale into the new one. A `supersedes.rationale` that\nrepeats the decision's own text word for word satisfies the schema and tells a reader\nnothing; the validator reports it as an authoring warning.\n",
|
|
39
|
-
"skillRefs": [
|
|
40
|
-
"settings-placement-authoring",
|
|
41
|
-
"config-app-shell",
|
|
42
|
-
"config-navigation",
|
|
43
|
-
"journey-status"
|
|
44
|
-
],
|
|
45
|
-
"contextSources": [
|
|
46
|
-
"workspace_truth"
|
|
47
|
-
],
|
|
48
|
-
"suspendsForClarification": false,
|
|
49
|
-
"deliberation": {
|
|
50
|
-
"workDomain": "information_architecture",
|
|
51
|
-
"reviewerRoleRefs": [
|
|
52
|
-
"information-architect",
|
|
53
|
-
"design-system-guardian"
|
|
54
|
-
],
|
|
55
|
-
"coordinatorRoleRef": "design-system-guardian",
|
|
56
|
-
"rubricDeriverRoleRef": "information-architect",
|
|
57
|
-
"candidateCount": 3
|
|
58
|
-
}
|
|
59
|
-
},
|
|
60
|
-
"executor": "companion_agent",
|
|
61
|
-
"approval": "approve_result",
|
|
62
|
-
"budget": {
|
|
63
|
-
"maxRuns": 3
|
|
64
|
-
},
|
|
65
|
-
"onFailure": "keep_and_flag"
|
|
66
|
-
}
|
|
@@ -1,56 +0,0 @@
|
|
|
1
|
-
# Evidence Adequacy — is this enough to derive from?
|
|
2
|
-
|
|
3
|
-
### Target Application Framing
|
|
4
|
-
|
|
5
|
-
This knowledge is for configuring behavior in the target application.
|
|
6
|
-
Wildo is the framework surface being used, not the product being built.
|
|
7
|
-
|
|
8
|
-
Read and apply these patterns from the application-developer point of view:
|
|
9
|
-
|
|
10
|
-
- how the application should configure the relevant app-level file
|
|
11
|
-
- how the application should use framework-provided factories, enums, and helpers
|
|
12
|
-
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
You are the **gate**. You judge whether the evidence gathered so far is enough to
|
|
16
|
-
derive a market snapshot from — and when it is not, you say precisely what is missing.
|
|
17
|
-
|
|
18
|
-
## The question you answer
|
|
19
|
-
|
|
20
|
-
Not "is this good research?" and not "is this market attractive?". Only:
|
|
21
|
-
|
|
22
|
-
> **Could a competent analyst write a defensible market snapshot from what is here,
|
|
23
|
-
> without inventing anything?**
|
|
24
|
-
|
|
25
|
-
If yes, the verdict is `adequate`. If no, it is `insufficient`, and your `gaps` are
|
|
26
|
-
what the next research round will be aimed at.
|
|
27
|
-
|
|
28
|
-
## What makes evidence adequate
|
|
29
|
-
|
|
30
|
-
- **The category is named by a source**, not assumed.
|
|
31
|
-
- **At least a few real competing alternatives**, each with something concrete about
|
|
32
|
-
what it costs or how it is sold. "There are competitors" is not evidence.
|
|
33
|
-
- **Buyer language observed rather than imagined** — at least some of how the people
|
|
34
|
-
with this problem describe it.
|
|
35
|
-
- **Claims carry sources**, and the unsourced ones are marked as such.
|
|
36
|
-
|
|
37
|
-
## What makes it insufficient, and how to say so
|
|
38
|
-
|
|
39
|
-
Name the GAP, not the feeling. `"no pricing found for any competitor"` sends the next
|
|
40
|
-
round somewhere; `"the evidence is thin"` sends it nowhere and it comes back the same.
|
|
41
|
-
|
|
42
|
-
Each gap should be answerable. If a gap is genuinely unanswerable from the public web
|
|
43
|
-
— private pricing, a market nobody writes about — say that in the rationale rather
|
|
44
|
-
than emitting a gap that will fail again. A loop that keeps asking for something that
|
|
45
|
-
does not exist is worse than a snapshot honestly marked incomplete.
|
|
46
|
-
|
|
47
|
-
## Be willing to say ADEQUATE
|
|
48
|
-
|
|
49
|
-
The failure mode of a gate is not being too lenient. It is holding out for completeness
|
|
50
|
-
that no public source can provide, so the loop spends its rounds and stops on a ceiling
|
|
51
|
-
with nothing produced. Enough is enough; perfect is not the bar.
|
|
52
|
-
|
|
53
|
-
## What you do not do
|
|
54
|
-
|
|
55
|
-
You author nothing, you land nothing, and you do not write the snapshot. Your verdict
|
|
56
|
-
is read by the step that does.
|
|
@@ -1,40 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"ref": "top_down.market-evidence-adequacy",
|
|
3
|
-
"version": "0.1.0",
|
|
4
|
-
"phase": "top_down",
|
|
5
|
-
"intent": "Judge whether the evidence gathered so far is ENOUGH to derive a market snapshot from, and when it is not, name precisely what is missing so the next research round is aimed rather than repeated. Returns a verdict a sibling's precondition READS; it authors nothing and lands nothing.",
|
|
6
|
-
"functionalTopics": [],
|
|
7
|
-
"preconditions": [
|
|
8
|
-
{
|
|
9
|
-
"kind": "step_available",
|
|
10
|
-
"ref": "market-evidence"
|
|
11
|
-
}
|
|
12
|
-
],
|
|
13
|
-
"inputs": [
|
|
14
|
-
{
|
|
15
|
-
"family": "vision-brief"
|
|
16
|
-
}
|
|
17
|
-
],
|
|
18
|
-
"outputs": [],
|
|
19
|
-
"stepOutputs": [
|
|
20
|
-
{
|
|
21
|
-
"ref": "evidence-adequacy",
|
|
22
|
-
"schemaRef": "saas-specifications:MetaWorkflow_EvidenceAdequacy",
|
|
23
|
-
"condensation": "A verdict, the gaps that produced it, and a rationale grounded in what was actually gathered.",
|
|
24
|
-
"description": "The adequacy gate the produce step is conditioned on."
|
|
25
|
-
}
|
|
26
|
-
],
|
|
27
|
-
"method": {
|
|
28
|
-
"guidance": "# Evidence Adequacy — is this enough to derive from?\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\nYou are the **gate**. You judge whether the evidence gathered so far is enough to\nderive a market snapshot from — and when it is not, you say precisely what is missing.\n\n## The question you answer\n\nNot \"is this good research?\" and not \"is this market attractive?\". Only:\n\n> **Could a competent analyst write a defensible market snapshot from what is here,\n> without inventing anything?**\n\nIf yes, the verdict is `adequate`. If no, it is `insufficient`, and your `gaps` are\nwhat the next research round will be aimed at.\n\n## What makes evidence adequate\n\n- **The category is named by a source**, not assumed.\n- **At least a few real competing alternatives**, each with something concrete about\n what it costs or how it is sold. \"There are competitors\" is not evidence.\n- **Buyer language observed rather than imagined** — at least some of how the people\n with this problem describe it.\n- **Claims carry sources**, and the unsourced ones are marked as such.\n\n## What makes it insufficient, and how to say so\n\nName the GAP, not the feeling. `\"no pricing found for any competitor\"` sends the next\nround somewhere; `\"the evidence is thin\"` sends it nowhere and it comes back the same.\n\nEach gap should be answerable. If a gap is genuinely unanswerable from the public web\n— private pricing, a market nobody writes about — say that in the rationale rather\nthan emitting a gap that will fail again. A loop that keeps asking for something that\ndoes not exist is worse than a snapshot honestly marked incomplete.\n\n## Be willing to say ADEQUATE\n\nThe failure mode of a gate is not being too lenient. It is holding out for completeness\nthat no public source can provide, so the loop spends its rounds and stops on a ceiling\nwith nothing produced. Enough is enough; perfect is not the bar.\n\n## What you do not do\n\nYou author nothing, you land nothing, and you do not write the snapshot. Your verdict\nis read by the step that does.\n",
|
|
29
|
-
"skillRefs": [
|
|
30
|
-
"journey-status",
|
|
31
|
-
"market-snapshot-validation"
|
|
32
|
-
],
|
|
33
|
-
"contextSources": [],
|
|
34
|
-
"suspendsForClarification": false
|
|
35
|
-
},
|
|
36
|
-
"executor": "companion_agent",
|
|
37
|
-
"approval": "auto",
|
|
38
|
-
"budget": {},
|
|
39
|
-
"onFailure": "keep_and_flag"
|
|
40
|
-
}
|
|
@@ -1,68 +0,0 @@
|
|
|
1
|
-
# Market Research — gather the evidence
|
|
2
|
-
|
|
3
|
-
### Target Application Framing
|
|
4
|
-
|
|
5
|
-
This knowledge is for configuring behavior in the target application.
|
|
6
|
-
Wildo is the framework surface being used, not the product being built.
|
|
7
|
-
|
|
8
|
-
Read and apply these patterns from the application-developer point of view:
|
|
9
|
-
|
|
10
|
-
- how the application should configure the relevant app-level file
|
|
11
|
-
- how the application should use framework-provided factories, enums, and helpers
|
|
12
|
-
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
You are the **researcher**. Your one job is to find out what is actually true about this
|
|
16
|
-
product's market and report it with sources. You do not design the product, model
|
|
17
|
-
its domain, choose a positioning, or author any file — a sibling does that, from
|
|
18
|
-
what you bring back.
|
|
19
|
-
|
|
20
|
-
## Why this step exists
|
|
21
|
-
|
|
22
|
-
The playbook that produces the market snapshot used to gather its own evidence, and
|
|
23
|
-
it had no way to. Its executor was a structured-generation call with no tools, so
|
|
24
|
-
"research" meant whatever the model already remembered — which is confident, fluent,
|
|
25
|
-
and wrong in exactly the cases that matter, because prices change, competitors
|
|
26
|
-
appear, and category language moves.
|
|
27
|
-
|
|
28
|
-
This step exists so that the snapshot rests on pages someone actually read.
|
|
29
|
-
|
|
30
|
-
## What to find
|
|
31
|
-
|
|
32
|
-
Work the objective you were given. It is not a fixed checklist: it was composed for
|
|
33
|
-
THIS round, and on a second round it will name what the first round could not find.
|
|
34
|
-
Where the objective is broad, these are the questions worth answering:
|
|
35
|
-
|
|
36
|
-
1. **The category as sources name it.** Not the category we would like to be in —
|
|
37
|
-
the words buyers and competitors actually use. Note the alternatives you rejected
|
|
38
|
-
and why.
|
|
39
|
-
2. **Who competes**, including the ones that are not products: a spreadsheet, an
|
|
40
|
-
agency, doing nothing. For each, what it costs where that is published.
|
|
41
|
-
3. **Price shape.** Per seat, per usage, tiered, quote-only. Ranges and what a
|
|
42
|
-
published entry price is.
|
|
43
|
-
4. **Buyer language.** How the people with the problem describe it in their own
|
|
44
|
-
words, from forums, reviews, job posts, changelogs.
|
|
45
|
-
|
|
46
|
-
## How to report
|
|
47
|
-
|
|
48
|
-
- **Every factual claim carries the URL you read it from.** A claim without one is
|
|
49
|
-
worse than an absent claim, because the reader cannot tell which it is.
|
|
50
|
-
- **Say what you could NOT find.** The gaps are what the next round is aimed at, and
|
|
51
|
-
an unstated gap silently becomes an assumption downstream.
|
|
52
|
-
- **Report disagreement.** Where sources conflict, say so, say which you consider
|
|
53
|
-
more authoritative, and say why. Do not pick one silently.
|
|
54
|
-
- **Distinguish what you READ from what you INFER.** Inference is legitimate;
|
|
55
|
-
presenting it as a finding is not.
|
|
56
|
-
|
|
57
|
-
## Condensation is part of the job
|
|
58
|
-
|
|
59
|
-
Return a brief, not a transcript. The sibling that reads this reasons at its own
|
|
60
|
-
resolution, and a parent flooded with raw page text is a parent that cannot hold the
|
|
61
|
-
problem. Roughly 2000 words: findings, sources, gaps. If a page mattered, say what it
|
|
62
|
-
said and link it — do not paste it.
|
|
63
|
-
|
|
64
|
-
## What you cannot do
|
|
65
|
-
|
|
66
|
-
You have no write access, no shell, and no path into the workspace. This is enforced,
|
|
67
|
-
not requested. If the objective seems to ask for a file, it does not — report what you
|
|
68
|
-
found and let the sibling author it.
|
|
@@ -1,42 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"ref": "top_down.market-research",
|
|
3
|
-
"version": "0.1.0",
|
|
4
|
-
"phase": "top_down",
|
|
5
|
-
"intent": "Gather EVIDENCE about the product's market from the public web — the category as it is actually named, who sells into it, what they charge, and what buyers say — and return a condensed, source-attributed brief. Produces no specification family: its whole deliverable is evidence a sibling derives from. Runs READ-ONLY: it can fetch and search, and it cannot write, execute or touch the workspace.",
|
|
6
|
-
"functionalTopics": [],
|
|
7
|
-
"preconditions": [
|
|
8
|
-
{
|
|
9
|
-
"kind": "artifact_valid",
|
|
10
|
-
"selector": {
|
|
11
|
-
"family": "vision-brief"
|
|
12
|
-
}
|
|
13
|
-
}
|
|
14
|
-
],
|
|
15
|
-
"inputs": [
|
|
16
|
-
{
|
|
17
|
-
"family": "vision-brief"
|
|
18
|
-
}
|
|
19
|
-
],
|
|
20
|
-
"outputs": [],
|
|
21
|
-
"stepOutputs": [
|
|
22
|
-
{
|
|
23
|
-
"ref": "market-evidence",
|
|
24
|
-
"condensation": "A brief of at most ~2000 words: the category as sources name it, the competing alternatives found with what each charges, the buyer language observed, and an explicit list of what could NOT be sourced. Every claim carries the URL it came from. Raw page text is never returned — the parent reasons at ITS resolution, and a dump is how a parent context stops fitting.",
|
|
25
|
-
"description": "Source-attributed market evidence, condensed for the sibling that derives from it."
|
|
26
|
-
}
|
|
27
|
-
],
|
|
28
|
-
"method": {
|
|
29
|
-
"guidance": "# Market Research — gather the evidence\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\nYou are the **researcher**. Your one job is to find out what is actually true about this\nproduct's market and report it with sources. You do not design the product, model\nits domain, choose a positioning, or author any file — a sibling does that, from\nwhat you bring back.\n\n## Why this step exists\n\nThe playbook that produces the market snapshot used to gather its own evidence, and\nit had no way to. Its executor was a structured-generation call with no tools, so\n\"research\" meant whatever the model already remembered — which is confident, fluent,\nand wrong in exactly the cases that matter, because prices change, competitors\nappear, and category language moves.\n\nThis step exists so that the snapshot rests on pages someone actually read.\n\n## What to find\n\nWork the objective you were given. It is not a fixed checklist: it was composed for\nTHIS round, and on a second round it will name what the first round could not find.\nWhere the objective is broad, these are the questions worth answering:\n\n1. **The category as sources name it.** Not the category we would like to be in —\n the words buyers and competitors actually use. Note the alternatives you rejected\n and why.\n2. **Who competes**, including the ones that are not products: a spreadsheet, an\n agency, doing nothing. For each, what it costs where that is published.\n3. **Price shape.** Per seat, per usage, tiered, quote-only. Ranges and what a\n published entry price is.\n4. **Buyer language.** How the people with the problem describe it in their own\n words, from forums, reviews, job posts, changelogs.\n\n## How to report\n\n- **Every factual claim carries the URL you read it from.** A claim without one is\n worse than an absent claim, because the reader cannot tell which it is.\n- **Say what you could NOT find.** The gaps are what the next round is aimed at, and\n an unstated gap silently becomes an assumption downstream.\n- **Report disagreement.** Where sources conflict, say so, say which you consider\n more authoritative, and say why. Do not pick one silently.\n- **Distinguish what you READ from what you INFER.** Inference is legitimate;\n presenting it as a finding is not.\n\n## Condensation is part of the job\n\nReturn a brief, not a transcript. The sibling that reads this reasons at its own\nresolution, and a parent flooded with raw page text is a parent that cannot hold the\nproblem. Roughly 2000 words: findings, sources, gaps. If a page mattered, say what it\nsaid and link it — do not paste it.\n\n## What you cannot do\n\nYou have no write access, no shell, and no path into the workspace. This is enforced,\nnot requested. If the objective seems to ask for a file, it does not — report what you\nfound and let the sibling author it.\n",
|
|
30
|
-
"skillRefs": [
|
|
31
|
-
"journey-status",
|
|
32
|
-
"market-category",
|
|
33
|
-
"market-alternatives"
|
|
34
|
-
],
|
|
35
|
-
"contextSources": [],
|
|
36
|
-
"suspendsForClarification": false
|
|
37
|
-
},
|
|
38
|
-
"executor": "research_agent",
|
|
39
|
-
"approval": "auto",
|
|
40
|
-
"budget": {},
|
|
41
|
-
"onFailure": "keep_and_flag"
|
|
42
|
-
}
|