@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
|
@@ -0,0 +1,91 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* The compliance-conception step `top_down.compliance-posture` defers to.
|
|
3
|
+
*
|
|
4
|
+
* That playbook stops at scaffold depth on purpose — regimes as prose constraints on the vision — and names its successor in
|
|
5
|
+
* `method.md`: "a later, separately approved compliance-conception step [which] may initialize or revise the optional
|
|
6
|
+
* structured family only after it resolves exact source versions and rights records, declarative application scope,
|
|
7
|
+
* applicability authority, Wildo objective bindings, implementation choices, responsibilities, documentation requirements
|
|
8
|
+
* and explicit gaps." This is that step, and that sentence is its specification rather than something re-derived here.
|
|
9
|
+
*
|
|
10
|
+
* `guidance` is deliberately absent: the method prose is the single source of truth in `method.md`, and the generator renders
|
|
11
|
+
* it (partials + references expanded) and injects it as `method.guidance`. Declaring it here would be a second copy that
|
|
12
|
+
* drifts — the folder contract rejects an inline one.
|
|
13
|
+
*/
|
|
14
|
+
export const playbookDefinition = {
|
|
15
|
+
"ref": "top_down.compliance-conception",
|
|
16
|
+
"version": "0.1.0",
|
|
17
|
+
"phase": "top_down",
|
|
18
|
+
"intent": "Compliance-conception pass: turn the applicable regimes the posture step recorded as prose constraints into the application's accepted `compliance-program` — the structured, reviewable record of which Wildo control objectives this product binds, which external requirement each answers, who is accountable, and what is explicitly undetermined. It does NOT re-elicit the vision and it does not draft any document. It is the first step in the lane that produces a POSITIVE compliance claim, so every claim it makes is either derived from an engine authority or answered by the creator in this run; nothing is inferred from a vision sentence.",
|
|
19
|
+
"preconditions": [
|
|
20
|
+
{ "kind": "artifact_exists", "selector": { "family": "vision-brief" } }
|
|
21
|
+
],
|
|
22
|
+
"inputs": [
|
|
23
|
+
{ "family": "vision-brief" }
|
|
24
|
+
],
|
|
25
|
+
"outputs": [
|
|
26
|
+
{
|
|
27
|
+
"family": "compliance-program",
|
|
28
|
+
"schemaRef": "saas-specifications:AssuranceProgramSpecification",
|
|
29
|
+
"description": "The application's accepted assurance programme: source references and their applicability, one obligation per bound Wildo objective with its coverage decision and implementation decision, responsibility assignments, and the limitations it does not claim beyond. Answered against the STRICT generation contract (`AssuranceProgramGenerationSchema`) and normalized into a v3 `AssuranceProgramSpecification` — the runtime stamps every ref, version and ordering, and refuses an objective the authority basis has no expectation for or a source the registry does not carry."
|
|
30
|
+
}
|
|
31
|
+
],
|
|
32
|
+
"method": {
|
|
33
|
+
"skillRefs": ["journey-status"],
|
|
34
|
+
/*
|
|
35
|
+
* ASSURANCE_PROGRAM_AUTHORITY supplies the two CLOSED SETS — bindable objectives with their intent, and citable sources.
|
|
36
|
+
* Without it the model guesses, and a guess here is not a weaker artifact but a REFUSED run out of the three budgeted.
|
|
37
|
+
*
|
|
38
|
+
* COMPLIANCE_PRIMARY_FACTS supplies what the application's resource declarations actually say: erasure treatment, data
|
|
39
|
+
* subject kinds, whether subject export is declared. That is the evidence for deciding whether an objective is genuinely
|
|
40
|
+
* met, and it is the difference between binding `WILDO.PRIVACY.SUBJECT_DATA_EXPORT` because the app declares the export
|
|
41
|
+
* and binding it because the objective sounded right.
|
|
42
|
+
*/
|
|
43
|
+
"contextSources": ["assurance_program_authority", "compliance_primary_facts"],
|
|
44
|
+
"elicitation": {
|
|
45
|
+
"questions": [
|
|
46
|
+
{
|
|
47
|
+
"ref": "programme-scope",
|
|
48
|
+
"question": "What exactly does this compliance programme cover — which product, environments and services? Name what is INSIDE the boundary, and anything a reader might assume is included that is not.",
|
|
49
|
+
"kind": "free_text"
|
|
50
|
+
},
|
|
51
|
+
{
|
|
52
|
+
"ref": "accountable-role",
|
|
53
|
+
"question": "Which role in this application is accountable for the compliance programme — the one that approves what it claims? Give the application's own role key (e.g. APP_ADMIN_SUPER_ADMIN) and a short name for it.",
|
|
54
|
+
"kind": "free_text"
|
|
55
|
+
},
|
|
56
|
+
{
|
|
57
|
+
"ref": "operating-role",
|
|
58
|
+
"question": "Which role OPERATES the controls day to day and produces the evidence, if different from the accountable role? Answer \"same\" if one role does both.",
|
|
59
|
+
"kind": "free_text"
|
|
60
|
+
},
|
|
61
|
+
{
|
|
62
|
+
"ref": "coverage-review-date",
|
|
63
|
+
"question": "On what date are you making these coverage decisions? Answer as an ISO date (YYYY-MM-DD). This is recorded as when the review happened — it is not generated, because nobody but you can say when you decided.",
|
|
64
|
+
"kind": "free_text"
|
|
65
|
+
},
|
|
66
|
+
{
|
|
67
|
+
"ref": "next-review-date",
|
|
68
|
+
"question": "When is this programme next reviewed? Answer as an ISO date (YYYY-MM-DD), after today's. A review schedule is a commitment, so it is asked rather than assumed.",
|
|
69
|
+
"kind": "free_text"
|
|
70
|
+
},
|
|
71
|
+
{
|
|
72
|
+
"ref": "objective-coverage",
|
|
73
|
+
"question": "For each bindable objective you were shown, does this application actually meet it today — and do you APPROVE binding it? Answer per objective, with the reason. Approving is a review: it says you read what the objective demands and accept that the product does it.",
|
|
74
|
+
"kind": "free_text"
|
|
75
|
+
},
|
|
76
|
+
{
|
|
77
|
+
"ref": "undetermined-and-gaps",
|
|
78
|
+
"question": "What is genuinely undetermined — something you cannot answer today without more work? List them. These become explicit UNDETERMINED applicability or stated limitations rather than silent omissions.",
|
|
79
|
+
"kind": "free_text"
|
|
80
|
+
}
|
|
81
|
+
]
|
|
82
|
+
}
|
|
83
|
+
},
|
|
84
|
+
"executor": "companion_agent",
|
|
85
|
+
"approval": "approve_result",
|
|
86
|
+
"budget": {
|
|
87
|
+
"maxRuns": 3
|
|
88
|
+
},
|
|
89
|
+
"onFailure": "keep_and_flag"
|
|
90
|
+
};
|
|
91
|
+
//# sourceMappingURL=playbook.definition.js.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.compliance-conception/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,gCAAgC;IACvC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,UAAU;IACnB,QAAQ,EAAE,ioBAAioB;IAC3oB,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,cAAc,EAAE,EAAE;KACxE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,cAAc,EAAE;KAC7B;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,oBAAoB;YAC9B,WAAW,EAAE,mDAAmD;YAChE,aAAa,EAAE,wjBAAwjB;SACxkB;KACF;IACD,QAAQ,EAAE;QACR,WAAW,EAAE,CAAC,gBAAgB,CAAC;QAC/B;;;;;;;;WAQG;QACH,gBAAgB,EAAE,CAAC,6BAA6B,EAAE,0BAA0B,CAAC;QAC7E,aAAa,EAAE;YACb,WAAW,EAAE;gBACX;oBACE,KAAK,EAAE,iBAAiB;oBACxB,UAAU,EAAE,6LAA6L;oBACzM,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,kBAAkB;oBACzB,UAAU,EAAE,8MAA8M;oBAC1N,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,gBAAgB;oBACvB,UAAU,EAAE,uJAAuJ;oBACnK,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,sBAAsB;oBAC7B,UAAU,EAAE,gNAAgN;oBAC5N,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,kBAAkB;oBACzB,UAAU,EAAE,iKAAiK;oBAC7K,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,oBAAoB;oBAC3B,UAAU,EAAE,0QAA0Q;oBACtR,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,uBAAuB;oBAC9B,UAAU,EAAE,uMAAuM;oBACnN,MAAM,EAAE,WAAW;iBACpB;aACF;SACF;KACF;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * The compliance-conception step `top_down.compliance-posture` defers to.\n *\n * That playbook stops at scaffold depth on purpose — regimes as prose constraints on the vision — and names its successor in\n * `method.md`: \"a later, separately approved compliance-conception step [which] may initialize or revise the optional\n * structured family only after it resolves exact source versions and rights records, declarative application scope,\n * applicability authority, Wildo objective bindings, implementation choices, responsibilities, documentation requirements\n * and explicit gaps.\" This is that step, and that sentence is its specification rather than something re-derived here.\n *\n * `guidance` is deliberately absent: the method prose is the single source of truth in `method.md`, and the generator renders\n * it (partials + references expanded) and injects it as `method.guidance`. Declaring it here would be a second copy that\n * drifts — the folder contract rejects an inline one.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"top_down.compliance-conception\",\n \"version\": \"0.1.0\",\n \"phase\": \"top_down\",\n \"intent\": \"Compliance-conception pass: turn the applicable regimes the posture step recorded as prose constraints into the application's accepted `compliance-program` — the structured, reviewable record of which Wildo control objectives this product binds, which external requirement each answers, who is accountable, and what is explicitly undetermined. It does NOT re-elicit the vision and it does not draft any document. It is the first step in the lane that produces a POSITIVE compliance claim, so every claim it makes is either derived from an engine authority or answered by the creator in this run; nothing is inferred from a vision sentence.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"vision-brief\" } }\n ],\n \"inputs\": [\n { \"family\": \"vision-brief\" }\n ],\n \"outputs\": [\n {\n \"family\": \"compliance-program\",\n \"schemaRef\": \"saas-specifications:AssuranceProgramSpecification\",\n \"description\": \"The application's accepted assurance programme: source references and their applicability, one obligation per bound Wildo objective with its coverage decision and implementation decision, responsibility assignments, and the limitations it does not claim beyond. Answered against the STRICT generation contract (`AssuranceProgramGenerationSchema`) and normalized into a v3 `AssuranceProgramSpecification` — the runtime stamps every ref, version and ordering, and refuses an objective the authority basis has no expectation for or a source the registry does not carry.\"\n }\n ],\n \"method\": {\n \"skillRefs\": [\"journey-status\"],\n /*\n * ASSURANCE_PROGRAM_AUTHORITY supplies the two CLOSED SETS — bindable objectives with their intent, and citable sources.\n * Without it the model guesses, and a guess here is not a weaker artifact but a REFUSED run out of the three budgeted.\n *\n * COMPLIANCE_PRIMARY_FACTS supplies what the application's resource declarations actually say: erasure treatment, data\n * subject kinds, whether subject export is declared. That is the evidence for deciding whether an objective is genuinely\n * met, and it is the difference between binding `WILDO.PRIVACY.SUBJECT_DATA_EXPORT` because the app declares the export\n * and binding it because the objective sounded right.\n */\n \"contextSources\": [\"assurance_program_authority\", \"compliance_primary_facts\"],\n \"elicitation\": {\n \"questions\": [\n {\n \"ref\": \"programme-scope\",\n \"question\": \"What exactly does this compliance programme cover — which product, environments and services? Name what is INSIDE the boundary, and anything a reader might assume is included that is not.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"accountable-role\",\n \"question\": \"Which role in this application is accountable for the compliance programme — the one that approves what it claims? Give the application's own role key (e.g. APP_ADMIN_SUPER_ADMIN) and a short name for it.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"operating-role\",\n \"question\": \"Which role OPERATES the controls day to day and produces the evidence, if different from the accountable role? Answer \\\"same\\\" if one role does both.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"coverage-review-date\",\n \"question\": \"On what date are you making these coverage decisions? Answer as an ISO date (YYYY-MM-DD). This is recorded as when the review happened — it is not generated, because nobody but you can say when you decided.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"next-review-date\",\n \"question\": \"When is this programme next reviewed? Answer as an ISO date (YYYY-MM-DD), after today's. A review schedule is a commitment, so it is asked rather than assumed.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"objective-coverage\",\n \"question\": \"For each bindable objective you were shown, does this application actually meet it today — and do you APPROVE binding it? Answer per objective, with the reason. Approving is a review: it says you read what the objective demands and accept that the product does it.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"undetermined-and-gaps\",\n \"question\": \"What is genuinely undetermined — something you cannot answer today without more work? List them. These become explicit UNDETERMINED applicability or stated limitations rather than silent omissions.\",\n \"kind\": \"free_text\"\n }\n ]\n }\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
|
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
import { MetaWorkflow_ApprovalPolicy, MetaWorkflow_Executor, MetaWorkflow_FailurePolicy, MetaWorkflow_Phase, MetaWorkflow_PredicateKind } from '@wildo-ai/saas-specifications/application-creation';
|
|
2
|
+
export declare const playbookDefinition: {
|
|
3
|
+
ref: string;
|
|
4
|
+
version: string;
|
|
5
|
+
phase: MetaWorkflow_Phase.TOP_DOWN;
|
|
6
|
+
intent: string;
|
|
7
|
+
preconditions: {
|
|
8
|
+
kind: MetaWorkflow_PredicateKind.STEP_AVAILABLE;
|
|
9
|
+
ref: string;
|
|
10
|
+
}[];
|
|
11
|
+
inputs: {
|
|
12
|
+
family: string;
|
|
13
|
+
}[];
|
|
14
|
+
outputs: any[];
|
|
15
|
+
stepOutputs: {
|
|
16
|
+
ref: string;
|
|
17
|
+
schemaRef: string;
|
|
18
|
+
condensation: string;
|
|
19
|
+
description: string;
|
|
20
|
+
}[];
|
|
21
|
+
method: {
|
|
22
|
+
skillRefs: string[];
|
|
23
|
+
};
|
|
24
|
+
executor: MetaWorkflow_Executor.COMPANION_AGENT;
|
|
25
|
+
approval: MetaWorkflow_ApprovalPolicy.AUTO;
|
|
26
|
+
budget: {};
|
|
27
|
+
onFailure: MetaWorkflow_FailurePolicy.KEEP_AND_FLAG;
|
|
28
|
+
};
|
|
29
|
+
//# sourceMappingURL=playbook.definition.d.ts.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,qBAAqB,EACrB,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,EAE3B,MAAM,oDAAoD,CAAC;AAE5D,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;CA4B9B,CAAC"}
|
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
import { MetaWorkflow_ApprovalPolicy, MetaWorkflow_Executor, MetaWorkflow_FailurePolicy, MetaWorkflow_Phase, MetaWorkflow_PredicateKind, } from '@wildo-ai/saas-specifications/application-creation';
|
|
2
|
+
export const playbookDefinition = {
|
|
3
|
+
ref: 'top_down.compliance-evidence-adequacy',
|
|
4
|
+
version: '0.1.1',
|
|
5
|
+
phase: MetaWorkflow_Phase.TOP_DOWN,
|
|
6
|
+
intent: 'Judge whether the regime evidence gathered so far is ENOUGH to state a compliance posture 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.',
|
|
7
|
+
preconditions: [
|
|
8
|
+
{ kind: MetaWorkflow_PredicateKind.STEP_AVAILABLE, ref: 'compliance-evidence' },
|
|
9
|
+
],
|
|
10
|
+
inputs: [{ family: 'vision-brief' }],
|
|
11
|
+
outputs: [],
|
|
12
|
+
stepOutputs: [{
|
|
13
|
+
ref: 'compliance-adequacy',
|
|
14
|
+
// The SAME generic adequacy contract the market gate uses — its own JSDoc predicted this reuse:
|
|
15
|
+
// "the next lane will find the same hole and will ask the same question of the same shape".
|
|
16
|
+
schemaRef: 'saas-specifications:MetaWorkflow_EvidenceAdequacy',
|
|
17
|
+
condensation: 'A verdict, the gaps that produced it, and a rationale grounded in what was actually gathered.',
|
|
18
|
+
description: 'The adequacy gate the posture step is conditioned on.',
|
|
19
|
+
}],
|
|
20
|
+
method: {
|
|
21
|
+
skillRefs: ['journey-status'],
|
|
22
|
+
},
|
|
23
|
+
executor: MetaWorkflow_Executor.COMPANION_AGENT,
|
|
24
|
+
approval: MetaWorkflow_ApprovalPolicy.AUTO,
|
|
25
|
+
budget: {},
|
|
26
|
+
onFailure: MetaWorkflow_FailurePolicy.KEEP_AND_FLAG,
|
|
27
|
+
};
|
|
28
|
+
//# sourceMappingURL=playbook.definition.js.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,qBAAqB,EACrB,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,GAE3B,MAAM,oDAAoD,CAAC;AAE5D,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,GAAG,EAAE,uCAAuC;IAC5C,OAAO,EAAE,OAAO;IAChB,KAAK,EAAE,kBAAkB,CAAC,QAAQ;IAClC,MAAM,EACJ,uSAAuS;IACzS,aAAa,EAAE;QACb,EAAE,IAAI,EAAE,0BAA0B,CAAC,cAAc,EAAE,GAAG,EAAE,qBAAqB,EAAE;KAChF;IACD,MAAM,EAAE,CAAC,EAAE,MAAM,EAAE,cAAc,EAAE,CAAC;IACpC,OAAO,EAAE,EAAE;IACX,WAAW,EAAE,CAAC;YACZ,GAAG,EAAE,qBAAqB;YAC1B,gGAAgG;YAChG,4FAA4F;YAC5F,SAAS,EAAE,mDAAmD;YAC9D,YAAY,EAAE,+FAA+F;YAC7G,WAAW,EAAE,uDAAuD;SACrE,CAAC;IACF,MAAM,EAAE;QACN,SAAS,EAAE,CAAC,gBAAgB,CAAC;KAC9B;IACD,QAAQ,EAAE,qBAAqB,CAAC,eAAe;IAC/C,QAAQ,EAAE,2BAA2B,CAAC,IAAI;IAC1C,MAAM,EAAE,EAAE;IACV,SAAS,EAAE,0BAA0B,CAAC,aAAa;CAGpD,CAAC","sourcesContent":["import {\n MetaWorkflow_ApprovalPolicy,\n MetaWorkflow_Executor,\n MetaWorkflow_FailurePolicy,\n MetaWorkflow_Phase,\n MetaWorkflow_PredicateKind,\n type MetaWorkflowPlaybookAuthoring,\n} from '@wildo-ai/saas-specifications/application-creation';\n\nexport const playbookDefinition = {\n ref: 'top_down.compliance-evidence-adequacy',\n version: '0.1.1',\n phase: MetaWorkflow_Phase.TOP_DOWN,\n intent:\n 'Judge whether the regime evidence gathered so far is ENOUGH to state a compliance posture 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.',\n preconditions: [\n { kind: MetaWorkflow_PredicateKind.STEP_AVAILABLE, ref: 'compliance-evidence' },\n ],\n inputs: [{ family: 'vision-brief' }],\n outputs: [],\n stepOutputs: [{\n ref: 'compliance-adequacy',\n // The SAME generic adequacy contract the market gate uses — its own JSDoc predicted this reuse:\n // \"the next lane will find the same hole and will ask the same question of the same shape\".\n schemaRef: 'saas-specifications:MetaWorkflow_EvidenceAdequacy',\n condensation: 'A verdict, the gaps that produced it, and a rationale grounded in what was actually gathered.',\n description: 'The adequacy gate the posture step is conditioned on.',\n }],\n method: {\n skillRefs: ['journey-status'],\n },\n executor: MetaWorkflow_Executor.COMPANION_AGENT,\n approval: MetaWorkflow_ApprovalPolicy.AUTO,\n budget: {},\n onFailure: MetaWorkflow_FailurePolicy.KEEP_AND_FLAG,\n} satisfies Omit<MetaWorkflowPlaybookAuthoring, 'method'> & {\n method: Omit<NonNullable<MetaWorkflowPlaybookAuthoring['method']>, 'guidance'>;\n};\n"]}
|
|
@@ -9,18 +9,21 @@
|
|
|
9
9
|
*/
|
|
10
10
|
export declare const playbookDefinition: {
|
|
11
11
|
readonly ref: "top_down.compliance-posture";
|
|
12
|
-
readonly version: "0.1
|
|
12
|
+
readonly version: "0.2.1";
|
|
13
13
|
readonly phase: "top_down";
|
|
14
|
-
readonly intent: "Compliance-posture pass: a focused elicitation that determines which legal, regulatory, contractual and external-assurance regimes the product operates under by reasoning over its jurisdictions, the classes of data it handles, its sector and customer commitments — and records each applicable regime as a `compliance`-kind constraint (prose statement) on the product's VisionSnapshot (the `vision-brief` artifact family). This SHARPENS the compliance seam the vision-elicitation step named in passing; it does NOT re-elicit the whole vision. SCAFFOLD depth: compliance stays PROSE constraints here — the deep per-regime obligation model (control catalogs, data-residency matrices, obligation graphs) is a deferred later concern, not built here. v1 scaffold methodology — iterate the regime-derivation rubric.";
|
|
15
|
-
readonly functionalTopics: readonly [];
|
|
14
|
+
readonly intent: "Compliance-posture pass: a focused elicitation that determines which legal, regulatory, contractual and external-assurance regimes the product operates under by reasoning over its jurisdictions, the classes of data it handles, its sector and customer commitments — and records each applicable regime as a `compliance`-kind constraint (prose statement) on the product's VisionSnapshot (the `vision-brief` artifact family). This SHARPENS the compliance seam the vision-elicitation step named in passing; it does NOT re-elicit the whole vision. SCAFFOLD depth: compliance stays PROSE constraints here — the deep per-regime obligation model (control catalogs, data-residency matrices, obligation graphs) is a deferred later concern, not built here. v1 scaffold methodology — iterate the regime-derivation rubric. Its regimes used to be derived from nine interview answers plus a model's recollection; it now runs as the artifact-producing child of the `top_down.compliance-analysis` composite, only once an adequacy gate has read the gathered regime evidence and returned ADEQUATE.";
|
|
16
15
|
readonly preconditions: readonly [{
|
|
17
|
-
readonly kind: "phase_is";
|
|
18
|
-
readonly phase: "top_down";
|
|
19
|
-
}, {
|
|
20
16
|
readonly kind: "artifact_exists";
|
|
21
17
|
readonly selector: {
|
|
22
18
|
readonly family: "vision-brief";
|
|
23
19
|
};
|
|
20
|
+
}, {
|
|
21
|
+
readonly kind: "step_available";
|
|
22
|
+
readonly ref: "compliance-adequacy";
|
|
23
|
+
readonly requires: {
|
|
24
|
+
readonly path: "verdict";
|
|
25
|
+
readonly equals: "adequate";
|
|
26
|
+
};
|
|
24
27
|
}];
|
|
25
28
|
readonly inputs: readonly [{
|
|
26
29
|
readonly family: "vision-brief";
|
|
@@ -32,45 +35,6 @@ export declare const playbookDefinition: {
|
|
|
32
35
|
}];
|
|
33
36
|
readonly method: {
|
|
34
37
|
readonly skillRefs: readonly ["journey-status"];
|
|
35
|
-
readonly elicitation: {
|
|
36
|
-
readonly questions: readonly [{
|
|
37
|
-
readonly ref: "handles-regulated-data";
|
|
38
|
-
readonly question: "Does the product store, process, or transmit personal data or otherwise regulated data (health, financial, biometric, children's, government) — either from end users or on behalf of customers?";
|
|
39
|
-
readonly kind: "confirm";
|
|
40
|
-
}, {
|
|
41
|
-
readonly ref: "data-classes";
|
|
42
|
-
readonly question: "Which classes of sensitive data does the product touch? List them (e.g. names/emails, health records, payment card data, government IDs, precise location, employee data). Answer \"none\" if it handles no personal or sensitive data.";
|
|
43
|
-
readonly kind: "free_text";
|
|
44
|
-
}, {
|
|
45
|
-
readonly ref: "jurisdictions";
|
|
46
|
-
readonly question: "In which jurisdictions do your users live and your data reside or transit (e.g. EU/EEA, UK, US, California, Canada, specific countries)? This is what drives which privacy regimes apply.";
|
|
47
|
-
readonly kind: "free_text";
|
|
48
|
-
}, {
|
|
49
|
-
readonly ref: "sector";
|
|
50
|
-
readonly question: "Does the product operate in a regulated sector with its own rules (healthcare, finance/banking, insurance, education, government, telecoms)? Name the sector, or answer \"none\".";
|
|
51
|
-
readonly kind: "free_text";
|
|
52
|
-
}, {
|
|
53
|
-
readonly ref: "gdpr-applies";
|
|
54
|
-
readonly question: "Do you serve EU/EEA (or UK) individuals or process their personal data? (This is the primary trigger for GDPR / UK GDPR.)";
|
|
55
|
-
readonly kind: "confirm";
|
|
56
|
-
}, {
|
|
57
|
-
readonly ref: "hipaa-applies";
|
|
58
|
-
readonly question: "Do you handle US protected health information as, or on behalf of, a covered entity or business associate? (This is the primary trigger for HIPAA.)";
|
|
59
|
-
readonly kind: "confirm";
|
|
60
|
-
}, {
|
|
61
|
-
readonly ref: "external-assurance-applies";
|
|
62
|
-
readonly question: "Do enterprise customers (or your own security posture) require an independent attestation or certification covering security / availability / confidentiality of the service? Name the requested target only as an external source requirement.";
|
|
63
|
-
readonly kind: "confirm";
|
|
64
|
-
}, {
|
|
65
|
-
readonly ref: "data-residency";
|
|
66
|
-
readonly question: "Are there data-residency or sovereignty requirements — must certain data stay within a region or country (e.g. EU-only hosting, in-country storage)? Describe them, or answer \"none\".";
|
|
67
|
-
readonly kind: "free_text";
|
|
68
|
-
}, {
|
|
69
|
-
readonly ref: "additional-regimes";
|
|
70
|
-
readonly question: "Any other legal regimes, sector frameworks, government programs, or contractual security commitments that apply? List the externally named sources, or answer \"none\".";
|
|
71
|
-
readonly kind: "free_text";
|
|
72
|
-
}];
|
|
73
|
-
};
|
|
74
38
|
};
|
|
75
39
|
readonly executor: "companion_agent";
|
|
76
40
|
readonly approval: "approve_result";
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.compliance-posture/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,eAAO,MAAM,kBAAkB
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.compliance-posture/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6BrB,CAAC"}
|
|
@@ -9,13 +9,12 @@
|
|
|
9
9
|
*/
|
|
10
10
|
export const playbookDefinition = {
|
|
11
11
|
"ref": "top_down.compliance-posture",
|
|
12
|
-
"version": "0.1
|
|
12
|
+
"version": "0.2.1",
|
|
13
13
|
"phase": "top_down",
|
|
14
|
-
"intent": "Compliance-posture pass: a focused elicitation that determines which legal, regulatory, contractual and external-assurance regimes the product operates under by reasoning over its jurisdictions, the classes of data it handles, its sector and customer commitments — and records each applicable regime as a `compliance`-kind constraint (prose statement) on the product's VisionSnapshot (the `vision-brief` artifact family). This SHARPENS the compliance seam the vision-elicitation step named in passing; it does NOT re-elicit the whole vision. SCAFFOLD depth: compliance stays PROSE constraints here — the deep per-regime obligation model (control catalogs, data-residency matrices, obligation graphs) is a deferred later concern, not built here. v1 scaffold methodology — iterate the regime-derivation rubric.",
|
|
15
|
-
"functionalTopics": [],
|
|
14
|
+
"intent": "Compliance-posture pass: a focused elicitation that determines which legal, regulatory, contractual and external-assurance regimes the product operates under by reasoning over its jurisdictions, the classes of data it handles, its sector and customer commitments — and records each applicable regime as a `compliance`-kind constraint (prose statement) on the product's VisionSnapshot (the `vision-brief` artifact family). This SHARPENS the compliance seam the vision-elicitation step named in passing; it does NOT re-elicit the whole vision. SCAFFOLD depth: compliance stays PROSE constraints here — the deep per-regime obligation model (control catalogs, data-residency matrices, obligation graphs) is a deferred later concern, not built here. v1 scaffold methodology — iterate the regime-derivation rubric. Its regimes used to be derived from nine interview answers plus a model's recollection; it now runs as the artifact-producing child of the `top_down.compliance-analysis` composite, only once an adequacy gate has read the gathered regime evidence and returned ADEQUATE.",
|
|
16
15
|
"preconditions": [
|
|
17
|
-
{ "kind": "
|
|
18
|
-
{ "kind": "
|
|
16
|
+
{ "kind": "artifact_exists", "selector": { "family": "vision-brief" } },
|
|
17
|
+
{ "kind": "step_available", "ref": "compliance-adequacy", "requires": { "path": "verdict", "equals": "adequate" } }
|
|
19
18
|
],
|
|
20
19
|
"inputs": [
|
|
21
20
|
{ "family": "vision-brief" }
|
|
@@ -29,55 +28,6 @@ export const playbookDefinition = {
|
|
|
29
28
|
],
|
|
30
29
|
"method": {
|
|
31
30
|
"skillRefs": ["journey-status"],
|
|
32
|
-
"elicitation": {
|
|
33
|
-
"questions": [
|
|
34
|
-
{
|
|
35
|
-
"ref": "handles-regulated-data",
|
|
36
|
-
"question": "Does the product store, process, or transmit personal data or otherwise regulated data (health, financial, biometric, children's, government) — either from end users or on behalf of customers?",
|
|
37
|
-
"kind": "confirm"
|
|
38
|
-
},
|
|
39
|
-
{
|
|
40
|
-
"ref": "data-classes",
|
|
41
|
-
"question": "Which classes of sensitive data does the product touch? List them (e.g. names/emails, health records, payment card data, government IDs, precise location, employee data). Answer \"none\" if it handles no personal or sensitive data.",
|
|
42
|
-
"kind": "free_text"
|
|
43
|
-
},
|
|
44
|
-
{
|
|
45
|
-
"ref": "jurisdictions",
|
|
46
|
-
"question": "In which jurisdictions do your users live and your data reside or transit (e.g. EU/EEA, UK, US, California, Canada, specific countries)? This is what drives which privacy regimes apply.",
|
|
47
|
-
"kind": "free_text"
|
|
48
|
-
},
|
|
49
|
-
{
|
|
50
|
-
"ref": "sector",
|
|
51
|
-
"question": "Does the product operate in a regulated sector with its own rules (healthcare, finance/banking, insurance, education, government, telecoms)? Name the sector, or answer \"none\".",
|
|
52
|
-
"kind": "free_text"
|
|
53
|
-
},
|
|
54
|
-
{
|
|
55
|
-
"ref": "gdpr-applies",
|
|
56
|
-
"question": "Do you serve EU/EEA (or UK) individuals or process their personal data? (This is the primary trigger for GDPR / UK GDPR.)",
|
|
57
|
-
"kind": "confirm"
|
|
58
|
-
},
|
|
59
|
-
{
|
|
60
|
-
"ref": "hipaa-applies",
|
|
61
|
-
"question": "Do you handle US protected health information as, or on behalf of, a covered entity or business associate? (This is the primary trigger for HIPAA.)",
|
|
62
|
-
"kind": "confirm"
|
|
63
|
-
},
|
|
64
|
-
{
|
|
65
|
-
"ref": "external-assurance-applies",
|
|
66
|
-
"question": "Do enterprise customers (or your own security posture) require an independent attestation or certification covering security / availability / confidentiality of the service? Name the requested target only as an external source requirement.",
|
|
67
|
-
"kind": "confirm"
|
|
68
|
-
},
|
|
69
|
-
{
|
|
70
|
-
"ref": "data-residency",
|
|
71
|
-
"question": "Are there data-residency or sovereignty requirements — must certain data stay within a region or country (e.g. EU-only hosting, in-country storage)? Describe them, or answer \"none\".",
|
|
72
|
-
"kind": "free_text"
|
|
73
|
-
},
|
|
74
|
-
{
|
|
75
|
-
"ref": "additional-regimes",
|
|
76
|
-
"question": "Any other legal regimes, sector frameworks, government programs, or contractual security commitments that apply? List the externally named sources, or answer \"none\".",
|
|
77
|
-
"kind": "free_text"
|
|
78
|
-
}
|
|
79
|
-
]
|
|
80
|
-
}
|
|
81
31
|
},
|
|
82
32
|
"executor": "companion_agent",
|
|
83
33
|
"approval": "approve_result",
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.compliance-posture/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,6BAA6B;IACpC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,UAAU;IACnB,QAAQ,EAAE,
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.compliance-posture/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,6BAA6B;IACpC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,UAAU;IACnB,QAAQ,EAAE,ujCAAujC;IACjkC,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,cAAc,EAAE,EAAE;QACvE,EAAE,MAAM,EAAE,gBAAgB,EAAE,KAAK,EAAE,qBAAqB,EAAE,UAAU,EAAE,EAAE,MAAM,EAAE,SAAS,EAAE,QAAQ,EAAE,UAAU,EAAE,EAAE;KACpH;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,cAAc,EAAE;KAC7B;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,cAAc;YACxB,WAAW,EAAE,oCAAoC;YACjD,aAAa,EAAE,uZAAuZ;SACva;KACF;IACD,QAAQ,EAAE;QACR,WAAW,EAAE,CAAC,gBAAgB,CAAC;KAChC;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * The structured method remains intentionally rich: its intent, inputs, output\n * contracts, elicitation, deterministic verification and skill routing are the\n * application knowledge a later generic assessment loop composes. This source\n * intentionally omits the superseded per-playbook evaluation-treatment object;\n * generation records that absence rather than fabricating legacy judge behavior.\n */\nexport const playbookDefinition = \n{\n \"ref\": \"top_down.compliance-posture\",\n \"version\": \"0.2.1\",\n \"phase\": \"top_down\",\n \"intent\": \"Compliance-posture pass: a focused elicitation that determines which legal, regulatory, contractual and external-assurance regimes the product operates under by reasoning over its jurisdictions, the classes of data it handles, its sector and customer commitments — and records each applicable regime as a `compliance`-kind constraint (prose statement) on the product's VisionSnapshot (the `vision-brief` artifact family). This SHARPENS the compliance seam the vision-elicitation step named in passing; it does NOT re-elicit the whole vision. SCAFFOLD depth: compliance stays PROSE constraints here — the deep per-regime obligation model (control catalogs, data-residency matrices, obligation graphs) is a deferred later concern, not built here. v1 scaffold methodology — iterate the regime-derivation rubric. Its regimes used to be derived from nine interview answers plus a model's recollection; it now runs as the artifact-producing child of the `top_down.compliance-analysis` composite, only once an adequacy gate has read the gathered regime evidence and returned ADEQUATE.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"vision-brief\" } },\n { \"kind\": \"step_available\", \"ref\": \"compliance-adequacy\", \"requires\": { \"path\": \"verdict\", \"equals\": \"adequate\" } }\n ],\n \"inputs\": [\n { \"family\": \"vision-brief\" }\n ],\n \"outputs\": [\n {\n \"family\": \"vision-brief\",\n \"schemaRef\": \"saas-specifications:VisionSnapshot\",\n \"description\": \"The same VisionSnapshot the vision-elicitation step seeded, refined in place: this playbook adds/updates the `constraints[]` entries whose `kind` is `compliance`, each a prose `statement` naming an applicable regime and the data / jurisdiction it governs. Other vision entities (idea, problem, mission, success criteria, non-compliance constraints) are left untouched. Validated by validateVisionSnapshot.\"\n }\n ],\n \"method\": {\n \"skillRefs\": [\"journey-status\"],\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
|
|
@@ -0,0 +1,30 @@
|
|
|
1
|
+
import { MetaWorkflow_ApprovalPolicy, MetaWorkflow_Executor, MetaWorkflow_FailurePolicy, MetaWorkflow_Phase, MetaWorkflow_PredicateKind } from '@wildo-ai/saas-specifications/application-creation';
|
|
2
|
+
export declare const playbookDefinition: {
|
|
3
|
+
ref: string;
|
|
4
|
+
version: string;
|
|
5
|
+
phase: MetaWorkflow_Phase.TOP_DOWN;
|
|
6
|
+
intent: string;
|
|
7
|
+
preconditions: {
|
|
8
|
+
kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID;
|
|
9
|
+
selector: {
|
|
10
|
+
family: string;
|
|
11
|
+
};
|
|
12
|
+
}[];
|
|
13
|
+
inputs: {
|
|
14
|
+
family: string;
|
|
15
|
+
}[];
|
|
16
|
+
outputs: any[];
|
|
17
|
+
stepOutputs: {
|
|
18
|
+
ref: string;
|
|
19
|
+
condensation: string;
|
|
20
|
+
description: string;
|
|
21
|
+
}[];
|
|
22
|
+
method: {
|
|
23
|
+
skillRefs: string[];
|
|
24
|
+
};
|
|
25
|
+
executor: MetaWorkflow_Executor.RESEARCH_AGENT;
|
|
26
|
+
approval: MetaWorkflow_ApprovalPolicy.AUTO;
|
|
27
|
+
budget: {};
|
|
28
|
+
onFailure: MetaWorkflow_FailurePolicy.KEEP_AND_FLAG;
|
|
29
|
+
};
|
|
30
|
+
//# sourceMappingURL=playbook.definition.d.ts.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.compliance-research/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,qBAAqB,EACrB,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,EAE3B,MAAM,oDAAoD,CAAC;AAE5D,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0B9B,CAAC"}
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
import { MetaWorkflow_ApprovalPolicy, MetaWorkflow_Executor, MetaWorkflow_FailurePolicy, MetaWorkflow_Phase, MetaWorkflow_PredicateKind, } from '@wildo-ai/saas-specifications/application-creation';
|
|
2
|
+
export const playbookDefinition = {
|
|
3
|
+
ref: 'top_down.compliance-research',
|
|
4
|
+
version: '0.1.0',
|
|
5
|
+
phase: MetaWorkflow_Phase.TOP_DOWN,
|
|
6
|
+
intent: 'Gather EVIDENCE about which legal and regulatory regimes plausibly apply to this product — the applicability trigger of each candidate regime (jurisdiction, data class, sector), verified against authoritative sources — and return a condensed, source-attributed brief. A voluntary security certification or attestation is NOT a regime and is not researched here: it binds only if the creator commits to it, so it is a one-line category note and the commitment itself comes from elicitation. 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.',
|
|
7
|
+
preconditions: [
|
|
8
|
+
{ kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'vision-brief' } },
|
|
9
|
+
],
|
|
10
|
+
inputs: [{ family: 'vision-brief' }],
|
|
11
|
+
outputs: [],
|
|
12
|
+
stepOutputs: [{
|
|
13
|
+
ref: 'compliance-evidence',
|
|
14
|
+
condensation: 'A brief of at most ~2000 words: each candidate regime by NAME — public law and regulator instruments, never a proprietary certification standard — with the applicability trigger that makes it apply or not apply to THIS product (jurisdiction, data class, sector), the authoritative source consulted (regulator page, official text — never a vendor blog when an official source exists), and an explicit list of what could NOT be established. 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.',
|
|
15
|
+
description: 'Source-attributed regime-applicability evidence, condensed for the sibling that derives from it.',
|
|
16
|
+
}],
|
|
17
|
+
method: {
|
|
18
|
+
skillRefs: ['journey-status'],
|
|
19
|
+
},
|
|
20
|
+
executor: MetaWorkflow_Executor.RESEARCH_AGENT,
|
|
21
|
+
approval: MetaWorkflow_ApprovalPolicy.AUTO,
|
|
22
|
+
budget: {},
|
|
23
|
+
onFailure: MetaWorkflow_FailurePolicy.KEEP_AND_FLAG,
|
|
24
|
+
};
|
|
25
|
+
//# sourceMappingURL=playbook.definition.js.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.compliance-research/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,qBAAqB,EACrB,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,GAE3B,MAAM,oDAAoD,CAAC;AAE5D,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,GAAG,EAAE,8BAA8B;IACnC,OAAO,EAAE,OAAO;IAChB,KAAK,EAAE,kBAAkB,CAAC,QAAQ;IAClC,MAAM,EACJ,qqBAAqqB;IACvqB,aAAa,EAAE;QACb,EAAE,IAAI,EAAE,0BAA0B,CAAC,cAAc,EAAE,QAAQ,EAAE,EAAE,MAAM,EAAE,cAAc,EAAE,EAAE;KAC1F;IACD,MAAM,EAAE,CAAC,EAAE,MAAM,EAAE,cAAc,EAAE,CAAC;IACpC,OAAO,EAAE,EAAE;IACX,WAAW,EAAE,CAAC;YACZ,GAAG,EAAE,qBAAqB;YAC1B,YAAY,EACV,4lBAA4lB;YAC9lB,WAAW,EAAE,kGAAkG;SAChH,CAAC;IACF,MAAM,EAAE;QACN,SAAS,EAAE,CAAC,gBAAgB,CAAC;KAC9B;IACD,QAAQ,EAAE,qBAAqB,CAAC,cAAc;IAC9C,QAAQ,EAAE,2BAA2B,CAAC,IAAI;IAC1C,MAAM,EAAE,EAAE;IACV,SAAS,EAAE,0BAA0B,CAAC,aAAa;CAGpD,CAAC","sourcesContent":["import {\n MetaWorkflow_ApprovalPolicy,\n MetaWorkflow_Executor,\n MetaWorkflow_FailurePolicy,\n MetaWorkflow_Phase,\n MetaWorkflow_PredicateKind,\n type MetaWorkflowPlaybookAuthoring,\n} from '@wildo-ai/saas-specifications/application-creation';\n\nexport const playbookDefinition = {\n ref: 'top_down.compliance-research',\n version: '0.1.0',\n phase: MetaWorkflow_Phase.TOP_DOWN,\n intent:\n 'Gather EVIDENCE about which legal and regulatory regimes plausibly apply to this product — the applicability trigger of each candidate regime (jurisdiction, data class, sector), verified against authoritative sources — and return a condensed, source-attributed brief. A voluntary security certification or attestation is NOT a regime and is not researched here: it binds only if the creator commits to it, so it is a one-line category note and the commitment itself comes from elicitation. 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.',\n preconditions: [\n { kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'vision-brief' } },\n ],\n inputs: [{ family: 'vision-brief' }],\n outputs: [],\n stepOutputs: [{\n ref: 'compliance-evidence',\n condensation:\n 'A brief of at most ~2000 words: each candidate regime by NAME — public law and regulator instruments, never a proprietary certification standard — with the applicability trigger that makes it apply or not apply to THIS product (jurisdiction, data class, sector), the authoritative source consulted (regulator page, official text — never a vendor blog when an official source exists), and an explicit list of what could NOT be established. 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.',\n description: 'Source-attributed regime-applicability evidence, condensed for the sibling that derives from it.',\n }],\n method: {\n skillRefs: ['journey-status'],\n },\n executor: MetaWorkflow_Executor.RESEARCH_AGENT,\n approval: MetaWorkflow_ApprovalPolicy.AUTO,\n budget: {},\n onFailure: MetaWorkflow_FailurePolicy.KEEP_AND_FLAG,\n} satisfies Omit<MetaWorkflowPlaybookAuthoring, 'method'> & {\n method: Omit<NonNullable<MetaWorkflowPlaybookAuthoring['method']>, 'guidance'>;\n};\n"]}
|
|
@@ -23,18 +23,12 @@ export declare const playbookDefinition: {
|
|
|
23
23
|
version: string;
|
|
24
24
|
phase: MetaWorkflow_Phase.TOP_DOWN;
|
|
25
25
|
intent: string;
|
|
26
|
-
|
|
27
|
-
preconditions: ({
|
|
28
|
-
kind: MetaWorkflow_PredicateKind.PHASE_IS;
|
|
29
|
-
phase: MetaWorkflow_Phase.TOP_DOWN;
|
|
30
|
-
selector?: undefined;
|
|
31
|
-
} | {
|
|
26
|
+
preconditions: {
|
|
32
27
|
kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID;
|
|
33
28
|
selector: {
|
|
34
29
|
family: string;
|
|
35
30
|
};
|
|
36
|
-
|
|
37
|
-
})[];
|
|
31
|
+
}[];
|
|
38
32
|
inputs: {
|
|
39
33
|
family: string;
|
|
40
34
|
}[];
|
|
@@ -45,7 +39,6 @@ export declare const playbookDefinition: {
|
|
|
45
39
|
admits: string[];
|
|
46
40
|
maximumIterations: number;
|
|
47
41
|
maximumLanesPerIteration: number;
|
|
48
|
-
maximumDepth: number;
|
|
49
42
|
maximumDurationMs: number;
|
|
50
43
|
};
|
|
51
44
|
};
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.market-analysis/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,EAE3B,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;GAkBG;AACH,eAAO,MAAM,kBAAkB
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.market-analysis/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,EAE3B,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;GAkBG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6D9B,CAAC"}
|
|
@@ -23,15 +23,20 @@ export const playbookDefinition = {
|
|
|
23
23
|
version: '0.2.0',
|
|
24
24
|
phase: MetaWorkflow_Phase.TOP_DOWN,
|
|
25
25
|
intent: 'Produce the market snapshot by gathering EVIDENCE, judging whether it is enough, and deriving the snapshot only once it is. An umbrella: it authors nothing itself — its deliverable is what its children land, and the order between them is decided by their own preconditions rather than declared here.',
|
|
26
|
-
functionalTopics: [],
|
|
27
26
|
preconditions: [
|
|
28
|
-
{ kind: MetaWorkflow_PredicateKind.PHASE_IS, phase: MetaWorkflow_Phase.TOP_DOWN },
|
|
29
27
|
{ kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'vision-brief' } },
|
|
30
28
|
],
|
|
31
29
|
inputs: [{ family: 'vision-brief' }],
|
|
32
30
|
// Nothing. A composite's deliverable is what its children land; declaring its child's output here
|
|
33
|
-
// would be two playbooks claiming one family
|
|
34
|
-
//
|
|
31
|
+
// would be two playbooks claiming one family and a landing path expecting THIS run to produce a file
|
|
32
|
+
// it never produces.
|
|
33
|
+
//
|
|
34
|
+
// It stays empty, and the loop no longer reads that emptiness as "writes nothing": the disjointness
|
|
35
|
+
// admission resolves a lane's write scope TRANSITIVELY through `admits`, so this playbook is scoped
|
|
36
|
+
// to `market-snapshot` and cannot be admitted beside `top_down.value-proposition`,
|
|
37
|
+
// `top_down.capability-map` or its own producing child. An earlier version of this comment argued
|
|
38
|
+
// that declaring the output would force the admission to "choose between a parent and its own
|
|
39
|
+
// child" — which is precisely the choice it must make, and could not.
|
|
35
40
|
outputs: [],
|
|
36
41
|
method: {
|
|
37
42
|
skillRefs: ['journey-status', 'market-authoring-overview'],
|
|
@@ -61,7 +66,6 @@ export const playbookDefinition = {
|
|
|
61
66
|
// Breadth-first: research is the case where several lanes with DIFFERENT invented objectives
|
|
62
67
|
// (category, competitors, pricing, buyers) beat one lane asked everything at once.
|
|
63
68
|
maximumLanesPerIteration: 3,
|
|
64
|
-
maximumDepth: 1,
|
|
65
69
|
// A literal: playbook definitions are read by an effect-free evaluator that does not compute
|
|
66
70
|
// expressions, so `20 * 60_000` is not something it can resolve. 20 minutes.
|
|
67
71
|
// 40 minutes: ~10 iterations at the measured 168s, with headroom. A breaker, not a budget —
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.market-analysis/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,GAE3B,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,GAAG,EAAE,0BAA0B;IAC/B,OAAO,EAAE,OAAO;IAChB,KAAK,EAAE,kBAAkB,CAAC,QAAQ;IAClC,MAAM,EACJ,6SAA6S;IAC/S,
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.market-analysis/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,GAE3B,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,GAAG,EAAE,0BAA0B;IAC/B,OAAO,EAAE,OAAO;IAChB,KAAK,EAAE,kBAAkB,CAAC,QAAQ;IAClC,MAAM,EACJ,6SAA6S;IAC/S,aAAa,EAAE;QACb,EAAE,IAAI,EAAE,0BAA0B,CAAC,cAAc,EAAE,QAAQ,EAAE,EAAE,MAAM,EAAE,cAAc,EAAE,EAAE;KAC1F;IACD,MAAM,EAAE,CAAC,EAAE,MAAM,EAAE,cAAc,EAAE,CAAC;IACpC,kGAAkG;IAClG,qGAAqG;IACrG,qBAAqB;IACrB,EAAE;IACF,oGAAoG;IACpG,oGAAoG;IACpG,mFAAmF;IACnF,kGAAkG;IAClG,8FAA8F;IAC9F,sEAAsE;IACtE,OAAO,EAAE,EAAE;IACX,MAAM,EAAE;QACN,SAAS,EAAE,CAAC,gBAAgB,EAAE,2BAA2B,CAAC;QAC1D,YAAY,EAAE;YACZ;;;;eAIG;YACH,MAAM,EAAE;gBACN,kCAAkC;gBAClC,0BAA0B;gBAC1B,mCAAmC;aACpC;YACD;;;;;;;;;;eAUG;YACH,iBAAiB,EAAE,EAAE;YACrB,6FAA6F;YAC7F,mFAAmF;YACnF,wBAAwB,EAAE,CAAC;YAC3B,6FAA6F;YAC7F,6EAA6E;YAC7E,4FAA4F;YAC5F,mFAAmF;YACnF,iBAAiB,EAAE,SAAS;SAC7B;KACF;IACD,QAAQ,EAAE,2BAA2B,CAAC,cAAc;IACpD,MAAM,EAAE,EAAE;IACV,SAAS,EAAE,0BAA0B,CAAC,aAAa;CAGpD,CAAC","sourcesContent":["import {\n MetaWorkflow_ApprovalPolicy,\n MetaWorkflow_FailurePolicy,\n MetaWorkflow_Phase,\n MetaWorkflow_PredicateKind,\n type MetaWorkflowPlaybookAuthoring,\n} from '@wildo-ai/saas-specifications/application-creation';\n\n/**\n * The market-analysis UMBRELLA — a composite, not a producer.\n *\n * It keeps the `top_down.market-analysis` ref deliberately: downstream gates on the FAMILY\n * (`top_down.phase-gate` requires `artifact_valid: market-snapshot`), never on a playbook ref, so the\n * producing work could move to a child without a single downstream edit. The ref is also what a\n * creator asks for by name.\n *\n * ## What changed, and why it is not a workflow\n *\n * This playbook used to be a single generation call whose intent claimed derivation from \"sealed\n * research evidence\" while nothing anywhere supplied evidence and its own method admitted it. It is\n * now three children — gather, judge, produce — and the ORDER between them is nowhere in this file.\n * `admits` is a set. Order comes from the children's own preconditions, re-evaluated every iteration\n * against the tree and against what siblings have returned, plus the model's choice among whatever is\n * eligible. That is what makes re-search possible at all: when the gate returns INSUFFICIENT, produce\n * stays ineligible and research becomes the reasonable choice again — with an objective aimed at the\n * gaps the gate named, not a repeat of the first one.\n */\nexport const playbookDefinition = {\n ref: 'top_down.market-analysis',\n version: '0.2.0',\n phase: MetaWorkflow_Phase.TOP_DOWN,\n intent:\n 'Produce the market snapshot by gathering EVIDENCE, judging whether it is enough, and deriving the snapshot only once it is. An umbrella: it authors nothing itself — its deliverable is what its children land, and the order between them is decided by their own preconditions rather than declared here.',\n preconditions: [\n { kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'vision-brief' } },\n ],\n inputs: [{ family: 'vision-brief' }],\n // Nothing. A composite's deliverable is what its children land; declaring its child's output here\n // would be two playbooks claiming one family and a landing path expecting THIS run to produce a file\n // it never produces.\n //\n // It stays empty, and the loop no longer reads that emptiness as \"writes nothing\": the disjointness\n // admission resolves a lane's write scope TRANSITIVELY through `admits`, so this playbook is scoped\n // to `market-snapshot` and cannot be admitted beside `top_down.value-proposition`,\n // `top_down.capability-map` or its own producing child. An earlier version of this comment argued\n // that declaring the output would force the admission to \"choose between a parent and its own\n // child\" — which is precisely the choice it must make, and could not.\n outputs: [],\n method: {\n skillRefs: ['journey-status', 'market-authoring-overview'],\n choreography: {\n /*\n * UNORDERED. Listed produce-first on purpose: if anything ever read this array as a sequence\n * the composite would try to author a snapshot before any evidence existed, and the run would\n * fail loudly rather than silently degrading.\n */\n admits: [\n 'top_down.market-snapshot-produce',\n 'top_down.market-research',\n 'top_down.market-evidence-adequacy',\n ],\n /*\n * MEASURED, not guessed (wonder-crm run 5, 2026-08-29). That run needed\n * research → judge(INSUFFICIENT) → research → research → judge(ADEQUATE) → produce: the\n * adequacy loop consumed FIVE of six iterations and produce landed on the last one, stopping on\n * the ceiling rather than on a decision. A run needing one more re-search cycle would have spent\n * the evidence gathering and landed nothing.\n *\n * At ~168s per iteration the WALL CLOCK was the real constraint, not this count — eight\n * iterations would have exceeded the old 20-minute breaker, so raising one without the other\n * would have changed nothing. Both moved together.\n */\n maximumIterations: 10,\n // Breadth-first: research is the case where several lanes with DIFFERENT invented objectives\n // (category, competitors, pricing, buyers) beat one lane asked everything at once.\n maximumLanesPerIteration: 3,\n // A literal: playbook definitions are read by an effect-free evaluator that does not compute\n // expressions, so `20 * 60_000` is not something it can resolve. 20 minutes.\n // 40 minutes: ~10 iterations at the measured 168s, with headroom. A breaker, not a budget —\n // it exists to stop a loop spinning, never to refuse work for want of spend (D11).\n maximumDurationMs: 2_400_000,\n },\n },\n approval: MetaWorkflow_ApprovalPolicy.APPROVE_RESULT,\n budget: {},\n onFailure: MetaWorkflow_FailurePolicy.KEEP_AND_FLAG,\n} satisfies Omit<MetaWorkflowPlaybookAuthoring, 'method'> & {\n method: Omit<NonNullable<MetaWorkflowPlaybookAuthoring['method']>, 'guidance'>;\n};\n"]}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.market-evidence-adequacy/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,qBAAqB,EACrB,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,EAE3B,MAAM,oDAAoD,CAAC;AAE5D,eAAO,MAAM,kBAAkB
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.market-evidence-adequacy/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,qBAAqB,EACrB,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,EAE3B,MAAM,oDAAoD,CAAC;AAE5D,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;CA0B9B,CAAC"}
|
|
@@ -4,7 +4,6 @@ export const playbookDefinition = {
|
|
|
4
4
|
version: '0.1.0',
|
|
5
5
|
phase: MetaWorkflow_Phase.TOP_DOWN,
|
|
6
6
|
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.',
|
|
7
|
-
functionalTopics: [],
|
|
8
7
|
preconditions: [
|
|
9
8
|
{ kind: MetaWorkflow_PredicateKind.STEP_AVAILABLE, ref: 'market-evidence' },
|
|
10
9
|
],
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.market-evidence-adequacy/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,qBAAqB,EACrB,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,GAE3B,MAAM,oDAAoD,CAAC;AAE5D,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,GAAG,EAAE,mCAAmC;IACxC,OAAO,EAAE,OAAO;IAChB,KAAK,EAAE,kBAAkB,CAAC,QAAQ;IAClC,MAAM,EACJ,8RAA8R;IAChS,
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.market-evidence-adequacy/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,qBAAqB,EACrB,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,GAE3B,MAAM,oDAAoD,CAAC;AAE5D,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,GAAG,EAAE,mCAAmC;IACxC,OAAO,EAAE,OAAO;IAChB,KAAK,EAAE,kBAAkB,CAAC,QAAQ;IAClC,MAAM,EACJ,8RAA8R;IAChS,aAAa,EAAE;QACb,EAAE,IAAI,EAAE,0BAA0B,CAAC,cAAc,EAAE,GAAG,EAAE,iBAAiB,EAAE;KAC5E;IACD,MAAM,EAAE,CAAC,EAAE,MAAM,EAAE,cAAc,EAAE,CAAC;IACpC,OAAO,EAAE,EAAE;IACX,WAAW,EAAE,CAAC;YACZ,GAAG,EAAE,mBAAmB;YACxB,SAAS,EAAE,mDAAmD;YAC9D,YAAY,EAAE,+FAA+F;YAC7G,WAAW,EAAE,uDAAuD;SACrE,CAAC;IACF,MAAM,EAAE;QACN,SAAS,EAAE,CAAC,gBAAgB,EAAE,4BAA4B,CAAC;KAC5D;IACD,QAAQ,EAAE,qBAAqB,CAAC,eAAe;IAC/C,QAAQ,EAAE,2BAA2B,CAAC,IAAI;IAC1C,MAAM,EAAE,EAAE;IACV,SAAS,EAAE,0BAA0B,CAAC,aAAa;CAGpD,CAAC","sourcesContent":["import {\n MetaWorkflow_ApprovalPolicy,\n MetaWorkflow_Executor,\n MetaWorkflow_FailurePolicy,\n MetaWorkflow_Phase,\n MetaWorkflow_PredicateKind,\n type MetaWorkflowPlaybookAuthoring,\n} from '@wildo-ai/saas-specifications/application-creation';\n\nexport const playbookDefinition = {\n ref: 'top_down.market-evidence-adequacy',\n version: '0.1.0',\n phase: MetaWorkflow_Phase.TOP_DOWN,\n intent:\n '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.',\n preconditions: [\n { kind: MetaWorkflow_PredicateKind.STEP_AVAILABLE, ref: 'market-evidence' },\n ],\n inputs: [{ family: 'vision-brief' }],\n outputs: [],\n stepOutputs: [{\n ref: 'evidence-adequacy',\n schemaRef: 'saas-specifications:MetaWorkflow_EvidenceAdequacy',\n condensation: 'A verdict, the gaps that produced it, and a rationale grounded in what was actually gathered.',\n description: 'The adequacy gate the produce step is conditioned on.',\n }],\n method: {\n skillRefs: ['journey-status', 'market-snapshot-validation'],\n },\n executor: MetaWorkflow_Executor.COMPANION_AGENT,\n approval: MetaWorkflow_ApprovalPolicy.AUTO,\n budget: {},\n onFailure: MetaWorkflow_FailurePolicy.KEEP_AND_FLAG,\n} satisfies Omit<MetaWorkflowPlaybookAuthoring, 'method'> & {\n method: Omit<NonNullable<MetaWorkflowPlaybookAuthoring['method']>, 'guidance'>;\n};\n"]}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.market-research/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,qBAAqB,EACrB,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,EAE3B,MAAM,oDAAoD,CAAC;AAE5D,eAAO,MAAM,kBAAkB
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.market-research/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,qBAAqB,EACrB,0BAA0B,EAC1B,kBAAkB,EAClB,0BAA0B,EAE3B,MAAM,oDAAoD,CAAC;AAE5D,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0B9B,CAAC"}
|