@wildo-ai/framework-knowledge 1.1.1 → 1.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +43 -2
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts +19 -0
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js +32 -0
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts +12 -0
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +46 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +55 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +4 -4
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +3 -3
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -3
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +0 -3
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +2 -7
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +8 -3
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +22 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +0 -3
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +0 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +4 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +4 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -13
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +3 -4
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +3 -3
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +2 -7
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +2 -7
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +54 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +127 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +76 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +92 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +30 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +29 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +9 -44
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +4 -53
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +31 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +26 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -7
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +0 -8
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +2 -7
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -7
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +2 -7
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +5 -3
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +0 -3
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +4 -5
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +25 -4
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
- package/dist/knowledge/manifest.json +8 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +51 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +27 -10
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +8 -7
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +6 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +4 -6
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +5 -4
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +4 -6
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +0 -4
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +4 -6
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +49 -22
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +14 -6
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +2 -4
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +46 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +7 -3
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +18 -4
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +4 -2
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +2 -3
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +8 -7
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +3 -5
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +0 -2
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +100 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +117 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +86 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +21 -4
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +14 -57
- package/dist/knowledge/playbooks/top_down.compliance-research/method.md +76 -0
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +42 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +3 -5
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +3 -1
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +3 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +3 -5
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +8 -4
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +9 -7
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +8 -7
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +0 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +4 -6
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +8 -7
- package/dist/knowledge/references/companion.technical-doc.service.md +102 -2
- package/dist/knowledge/references/example.config.app-shell.full.md +0 -1
- package/dist/knowledge/references/example.module.companion-exports.full.md +1 -0
- package/dist/knowledge/references/platform.config.saas.md +1 -0
- package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +25 -1
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +45 -0
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
- package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +89 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +31 -4
- package/dist/knowledge/references/saas.models.engine-capabilities.md +26 -6
- package/dist/knowledge/references/saas.models.file-upload-grant.md +179 -0
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +127 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +4 -3
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
- package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +11 -31
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +32 -2
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +29 -6
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +20 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +6 -0
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +31 -5
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +43 -0
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +15 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
- package/dist/knowledge/registries/framework-topics.json +99 -1
- package/dist/knowledge/registries/playbooks.json +81 -8
- package/dist/knowledge/registries/source-tags.json +757 -588
- package/dist/knowledge/skills/INDEX.md +3 -3
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +5 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +66 -37
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +40 -7
- package/dist/knowledge/skills/config-app-shell/SKILL.md +25 -1
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +25 -1
- package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +23 -1
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
- package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
- package/dist/knowledge/skills/config-navigation/SKILL.md +75 -2
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +149 -0
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +114 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +133 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +19 -2
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +111 -0
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +30 -9
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +1 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +2 -1
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +20 -0
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +20 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +20 -0
- package/dist/knowledge/skills/resource-add-field/SKILL.md +3 -3
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +104 -0
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +13 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +71 -4
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +89 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +22 -1
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +192 -0
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +28 -8
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +15 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +6 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +89 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +43 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +1 -1
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +20 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +31 -5
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +22 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +45 -0
- package/dist/knowledge/topic-index.json +504 -156
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/esm/.builder.pid +0 -9
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"attributionNotices":["Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record."],"evaluatedAt":"2026-09-05T12:54:53.265Z","mapped":[{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-govern-accountable-role-retention","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Every scope keeps at least one usable administrator: a removal, demotion or deactivation that would strand an application or a tenant is refused, concurrent reductions are serialized so two of them cannot pass each other, a data-protection erasure proceeds only on an explicit acknowledgement that records the breach it causes, and any scope that has already been stranded is reported at startup.","objectiveRef":"WILDO.ACCESS.ADMINISTRATIVE_CONTINUITY","title":"Retain an administrator for every scope"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-audit-of-access-decisions","reviewedAt":"2026-09-01T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"Access-control decisions, refusals included, are attributable and reviewable; repeated refusals stay detectable without the record itself becoming an availability risk; and a failure of the recording pipeline is detectable and attributable to the specific action it lost.","objectiveRef":"WILDO.ACCESS.AUTHORIZATION_DECISION_AUDIT","title":"Record access decisions, refusals included"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-access-authorization-recording","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"}],"intent":"Platform-tier administration of a tenant is never ambient: a crossing is admitted only by an explicitly enumerated operation variant, requires an elevation that was requested rather than assumed and — where the tenant demands it — approved by that tenant, is recorded as a distinct event naming the tenant reached, and an undeclared crossing fails closed.","objectiveRef":"WILDO.ACCESS.CROSS_TENANT_ADMINISTRATION","title":"Declare every crossing of a tenant boundary"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-least-privilege-enforcement","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-least-privilege-authority-limit","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A principal can never grant authority it does not itself hold — role assignment and machine-credential minting are bounded by the caller’s own ceiling — and a non-controller surface facing an external caller applies the same declared operation-role gate the controller tier applies, through the same predicate, before a self-service verb, a retrieval corpus or an agent-facing tool is reached.","objectiveRef":"WILDO.ACCESS.LEAST_PRIVILEGE","title":"Grant no more authority than the action needs"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-workforce-access-termination","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-account-disable-on-relationship-end","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"Access rights, and the credentials that assert them, are withdrawn when the relationship conferring them ends, and restoring access is as attributable as removing it.","objectiveRef":"WILDO.ACCESS.LIFECYCLE","title":"Withdraw and restore access attributably"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-temporary-account-expiry","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"An access restriction declared as time-boxed is lifted when its window elapses, through the same guarded authority that imposed it, so a measure taken as temporary cannot silently become permanent.","objectiveRef":"WILDO.ACCESS.LIFECYCLE_TIME_BOUND","title":"Release a time-boxed restriction automatically"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hipaa-security-privileged-access-review","reviewedAt":"2026-08-13T08:57:58.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-govern-access-review","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Privileged access is explicitly scoped, periodically reviewed, decided by authorized people and retained as traceable evidence without implying remediation completion.","objectiveRef":"WILDO.ACCESS.PRIVILEGED_REVIEW","title":"Review privileged access"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-privileged-grant-evidence","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Every grant, widening, narrowing and revocation of privilege — a role, a unit-scoped membership, a discretionary entitlement or a subscription-derived one — leaves durable evidence of the assignment’s full life, not merely of its current state.","objectiveRef":"WILDO.ACCESS.PRIVILEGE_EVIDENCE","title":"Keep evidence of a privileged assignment’s whole life"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-processing-confidentiality","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-information-flow-confinement","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"Reads and writes are narrowed to the tenant, unit subtree or parent row the caller’s own grant reaches; the conferring grant is recorded alongside the decision, a unit grant expands to exactly its declared subtree and no further, and a tenant cannot lift a narrowing the platform imposed on it.","objectiveRef":"WILDO.ACCESS.SCOPE_CONFINEMENT","title":"Confine a query to the scope the caller reached it by"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-accountability-demonstration","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-detect-attributable-event-record","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A security-relevant action records who performed it, and never disguises an unattributable action as an ordinary automated one; read-through access to an external system carries the real initiating user through the shared service principal, and an outbound deletion there names the subject it served and the system it reached.","objectiveRef":"WILDO.AUDIT.ATTRIBUTION","title":"Name who performed a security-relevant action"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-audit-record-context-binding","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"The actor and tenant an audit row names survive the trusted-system write that persists it, and a log record names which application and which environment produced it — so a record cannot silently lose or change the principal, tenant or deployment it belongs to.","objectiveRef":"WILDO.AUDIT.CONTEXT_ATTRIBUTION","title":"Bind a record to the context it actually ran in"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-audit-record-content-and-protection","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A privileged action on a resource is attributable, and the authorization effect it had is reconstructable from the record itself rather than re-derived from role tables afterwards; the configuration deciding what the trail captures is governed as part of the trail.","objectiveRef":"WILDO.AUDIT.EVIDENCE_INTEGRITY","title":"Govern the audit trail as evidence in its own right"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.29","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-detect-security-event-logging","reviewedAt":"2026-09-01T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Authentication, authorization, privilege, credential and security-configuration changes each emit a typed auditable event; non-human privileged access is audited or refused; and the absence of the audit delivery path is surfaced at boot rather than tolerated silently.","objectiveRef":"WILDO.AUDIT.SECURITY_EVENT","title":"Emit a typed event for every security-relevant change"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-transaction-authorization-separation","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"An increase in a credit balance is reachable only through a system or payment-gated door, so no ordinary principal can grant itself economic value.","objectiveRef":"WILDO.BILLING.CREDIT_GRANT_INTEGRITY","title":"Gate a credit grant to system or payment authority"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-transmission-confidentiality","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"}],"intent":"Material a schema declares backend-only does not cross the client boundary, except at a single first exposure that is itself audited.","objectiveRef":"WILDO.DATA.CONFIDENTIALITY","title":"Keep backend-only material off the client boundary"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-information-integrity-verification","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A uniqueness or integrity control the schema declares is proven to exist in the datastore before the application serves traffic, rather than assumed to have been created.","objectiveRef":"WILDO.DATA.INTEGRITY_CONSTRAINTS","title":"Prove a declared constraint exists before serving traffic"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-erasure-with-retention-carve-out","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-media-sanitization-and-disposal","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"Destruction of an identity, a tenant or its data is a deliberate, attributable, evidenced decision, reversible until its declared window elapses and then carried out on schedule; an erased-but-retained record is hidden from, and immutable to, every ORDINARY access path — the only door is an audited see-through read — and its derived copies are excluded by a live check against the parent row rather than by waiting for a sweep.","objectiveRef":"WILDO.DATA.SECURE_LIFECYCLE","title":"Destroy data deliberately, on a recorded schedule"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-shared-resource-isolation","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A caller cannot widen its own query scope: tenancy narrowing is derived from the resolved execution context and never offered as a parameter — to a client, to an agent, or to a retrieval surface — and where the read is a similarity search the predicate is evaluated INSIDE the traversal rather than over its results, then re-checked by an authorized read of the owning row.","objectiveRef":"WILDO.DATA.TENANT_ISOLATION","title":"Derive tenancy from the caller, never from the request"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-transaction-recovery-integrity","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A resource declares its persistence isolation before it may sit on a non-default adapter, and a configuration whose cross-resource writes could not be atomic is refused when the registry is built rather than discovered under load.","objectiveRef":"WILDO.DATA.TRANSACTIONAL_INTEGRITY","title":"Refuse a configuration that cannot write atomically"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-entitlement-change-authority","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Feature and entitlement writes are reachable only through an operator-gated door, so a principal cannot widen what it is entitled to.","objectiveRef":"WILDO.ENTITLEMENT.NO_SELF_GRANT","title":"Keep an entitlement write operator-gated"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-identify-service-identity-verification","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A client identity is bound to a domain the client demonstrably controls, and both a client identity created by a party that authenticated to nothing and every refused client assertion are recorded.","objectiveRef":"WILDO.IDENTITY.CLIENT_IDENTITY_ASSERTION","title":"Bind a client identity to a verifiable assertion"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-credential-management","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-credential-state-transitions","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Issuance, refresh, rotation, revocation and expiry of a credential are explicit attributable transitions; credential theft is detected and answered by invalidation; and a revocation actually terminates the sessions and tokens it names rather than merely marking a record.","objectiveRef":"WILDO.IDENTITY.CREDENTIAL_LIFECYCLE","title":"Make every credential state transition explicit"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-delegated-access-authorization","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A third party acts for a user only on that user’s recorded authorization: approval, refusal, persistence and failure of the delegated exchange are each audited, proof of possession is enforced on the exchange, and the issued token carries no more than the grant declared.","objectiveRef":"WILDO.IDENTITY.DELEGATED_AUTHORIZATION","title":"Let a user authorize third-party access deliberately"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-automated-account-management","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"Where an application opts in, a directory becomes the authority for accounts and for unit membership — which is an authorization grant, not a label — and the switches conferring that authority are declared explicitly rather than implied by the presence of a connection.","objectiveRef":"WILDO.IDENTITY.DIRECTORY_PROVISIONING","title":"Honour the directory as the provisioning authority"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-account-enable-disable-authority","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A change to whether a principal may authenticate runs through one guarded, evidenced authority: the status carrying it is excluded from ordinary updates, so the change cannot arrive as a side effect of an unrelated write.","objectiveRef":"WILDO.IDENTITY.LIFECYCLE","title":"Record every change to whether a principal may authenticate"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hipaa-security-authentication-controls","reviewedAt":"2026-09-01T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"}],"intent":"Enrolled second factors are verified through one authority that is replay-resistant and timing-safe, so no caller builds a second, weaker door onto the same credential.","objectiveRef":"WILDO.IDENTITY.MULTI_FACTOR","title":"Verify enrolled second factors through one authority"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-redirect-target-constraint","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A registered OAuth redirect target is constrained to a safe absolute URL, closing the open-redirect and stored-XSS delegation primitive a permissive target would otherwise create.","objectiveRef":"WILDO.IDENTITY.REDIRECT_TARGET_VALIDATION","title":"Constrain a registered redirect target"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-govern-authentication-posture-change","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"How principals may authenticate — the MFA, password, lockout, methods, step-up and session posture, whether single sign-on is enforced, which identity provider is trusted, and whether its assertions are actually verified — is explicitly configured, and every genuine change to that posture is detected at startup and evidenced once, from the runtime that puts it into effect.","objectiveRef":"WILDO.IDENTITY.SESSION_ASSURANCE","title":"Decide, and record changes to, the assurance a session carries"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-concurrent-session-control","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A principal holds a bounded number of concurrent sessions, and the eviction enforcing that bound retires the OLDEST refresh chain — the property that pushes a stolen chain out instead of a legitimate one.","objectiveRef":"WILDO.IDENTITY.SESSION_CONCURRENCY_LIMIT","title":"Bound the concurrent sessions a principal holds"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-cryptographic-key-establishment-and-management","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A rotated signing key can be given an explicit retirement instant, after which it stops being advertised and stops verifying tokens — so an aged or compromised prior key need not stay trusted until someone edits configuration.","objectiveRef":"WILDO.IDENTITY.SIGNING_KEY_LIFECYCLE","title":"Bound the lifetime of a retired signing key"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-person-or-entity-reverification","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-reauthentication-for-privileged-action","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A high-impact action requires a fresh re-proof of identity, over any factor the principal actually holds, and that ceremony cannot be satisfied by a credential presented for a different purpose.","objectiveRef":"WILDO.IDENTITY.STEP_UP_AUTHENTICATION","title":"Re-prove identity before a high-impact action"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-assertion-integrity","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"An ID token’s protocol and security claims are authored by the server alone, from one named reserved-claim set, so a caller cannot smuggle a reserved claim in through supplied extras.","objectiveRef":"WILDO.IDENTITY.TOKEN_INTEGRITY","title":"Author a token’s protocol claims on the server only"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-detect-outbound-connection-monitoring","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Outbound traffic leaves through a single named egress per capability, and every physical call is recorded — provider, model, usage and outcome for a provider call, the initiating actor for an administrative probe — so a reviewer can enumerate what was sent and when.","objectiveRef":"WILDO.INTEGRATION.OUTBOUND_ACTIVITY_AUDIT","title":"Attribute every outbound connection the application makes"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-authority-not-inferred-from-state","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A self-reported lifecycle stage confers no capability and cannot cross a scope boundary; authority comes only from a decision an authorized party actually made.","objectiveRef":"WILDO.LIFECYCLE.STAGE_IS_NOT_AUTHORITY","title":"Confer no capability from a self-reported stage"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-error-handling-diagnostics","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A constraint conflict is reported with the identity that was violated rather than as an opaque datastore failure, so an operator can tell a benign duplicate from an unexpected collision.","objectiveRef":"WILDO.OPERATIONS.CONFLICT_DIAGNOSTICS","title":"Report a conflict by the identity it violated"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-declared-interface-integrity","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A declared, API-reachable operation stays reachable and is actually implemented: an interface must not report success for an action it did not perform, and a named verb must not silently widen into an unconstrained write over fields its resource never exposed for update.","objectiveRef":"WILDO.OPERATIONS.EXECUTION_INTEGRITY","title":"Never report success for an action that was not performed"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-denial-of-service-resource-bounds","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"An unauthenticated request consumes a bounded amount of resource, and an over-limit request is answered as a client error rather than surfacing as a server failure.","objectiveRef":"WILDO.OPERATIONS.RESOURCE_LIMIT","title":"Bound what an unauthenticated request may consume"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-bulk-disclosure-record","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"A bulk export of a resource collection is a recorded event naming the resource exported, the operation it was taken from, and the format it was rendered in.","objectiveRef":"WILDO.PRIVACY.COLLECTION_DATA_EXPORT","title":"Record a bulk export of a resource collection"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-consent-demonstrability","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"A consent decision — given, changed or withdrawn — is recorded exactly once and never lost to a race, naming the previous and the resulting value; every verb able to change consent routes through one emission point, and resetting a subject’s privacy preferences is itself such a decision.","objectiveRef":"WILDO.PRIVACY.CONSENT_RECORD","title":"Record a consent decision exactly once"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-data-minimisation","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"Only the data a declared purpose requires leaves its boundary: an external processor receives the payload and nothing identifying the requester or its row, observability surfaces receive summaries rather than the raw content, and a device-stored pseudonymous identifier is collected only under an explicit application opt-in — absent that policy, not at all — and can be withdrawn or narrowed afterwards.","objectiveRef":"WILDO.PRIVACY.DATA_MINIMIZATION","title":"Send only what the declared purpose requires"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-records-of-processing-categories","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"The application declares, on the field itself, which CATEGORIES of personal data it holds — never inferred from the field’s name, because an inventory assembled by pattern-matching identifiers is a guess whose misses go silently undisclosed.","objectiveRef":"WILDO.PRIVACY.PERSONAL_DATA_INVENTORY","title":"Declare in the schema which fields hold personal data"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-storage-limitation","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"Declared row-retention windows are enforced, and a configuration whose derived copies of subject text could outlive the row they came from — unreachable by the erasure seams — is refused at startup.","objectiveRef":"WILDO.PRIVACY.STORAGE_LIMITATION","title":"Keep data no longer than its declared window"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-subject-access-portability","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"Authorized subject access and portability exports are purpose-specific, resource-opted-in, subject-isolated and auditable: the export event names the purpose, the subject, the resource types included, the record count and the fields withheld as derived.","objectiveRef":"WILDO.PRIVACY.SUBJECT_DATA_EXPORT","title":"Export subject data safely"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-erasure-and-restriction","reviewedAt":"2026-09-01T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"A subject’s erasure request is recorded on intake whether the subject or the controller raised it, may be withdrawn by the subject while it is pending, is executed on the declared schedule, and terminates the erased person’s sessions.","objectiveRef":"WILDO.PRIVACY.SUBJECT_ERASURE","title":"Execute a subject erasure request, and evidence it"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-processor-engagement","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"Routing data to an external service makes that service a processor of it, so such routing is opt-in by construction: nothing leaves unless the application selects a provider for that capability, and with no selection the work is served locally with no egress at all.","objectiveRef":"WILDO.PRIVACY.THIRD_PARTY_PROCESSING","title":"Name the processors that data is routed to"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-authenticator-storage-protection","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"The shape of a provider’s secret contract is tracked so that drift in it is detectable, without ever persisting the secret values themselves.","objectiveRef":"WILDO.SECRETS.CONTRACT_INTEGRITY","title":"Detect drift in a values-free secret contract"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-authenticator-disclosure-record","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"The first disclosure of server-minted secret material is an attributable, audited event.","objectiveRef":"WILDO.SECRETS.DISCLOSURE_AUDIT","title":"Audit the first disclosure of minted secret material"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-fail-secure-behaviour","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A control that cannot be evaluated refuses what it guards, and stays diagnosable while doing so: untrusted input is rejected whole rather than partly sanitized, and a validator whose dependency is unavailable fails closed without its degradation being mistaken for a rejected signature.","objectiveRef":"WILDO.SECURITY.FAIL_CLOSED","title":"Refuse rather than degrade when a control cannot run"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-configuration-settings-enforcement","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A server-owned field has exactly one named authority that writes it, and that authority is proven at boot rather than assumed — so no second path can set the field and no reader has to work out which value is current.","objectiveRef":"WILDO.SOFTWARE.AUTHORITY_INTEGRITY","title":"Give every server-owned field exactly one named authority"}],"mappingRef":"assurance-external-mapping:wildo-safe-baseline-v1","mappingVersion":1,"normativeSourceContentIncluded":false,"tailoringCaveat":"A control catalog requires tailoring, implementation and assessment; catalog inclusion is not proof of operation. This mapping records which external source each Wildo objective was reviewed against. It is not a conformity assertion, it claims no operating effectiveness, and it reproduces no normative source text.","unmapped":[]}
|
|
@@ -1,11 +1,11 @@
|
|
|
1
1
|
{
|
|
2
2
|
"artifactVersion": "3",
|
|
3
|
-
"frameworkVersion": "1.1.
|
|
4
|
-
"generatorVersion": "1.1.
|
|
5
|
-
"generatedAt": "2026-
|
|
3
|
+
"frameworkVersion": "1.1.2",
|
|
4
|
+
"generatorVersion": "1.1.2",
|
|
5
|
+
"generatedAt": "2026-09-05T12:54:53.265Z",
|
|
6
6
|
"packageName": "@wildo-ai/framework-knowledge",
|
|
7
|
-
"topicCount":
|
|
8
|
-
"referenceFileCount":
|
|
7
|
+
"topicCount": 547,
|
|
8
|
+
"referenceFileCount": 547,
|
|
9
9
|
"payload": {
|
|
10
10
|
"topicIndexPath": "topic-index.json",
|
|
11
11
|
"registriesDirectory": "registries",
|
|
@@ -21,19 +21,19 @@
|
|
|
21
21
|
"registryName": "source-tags",
|
|
22
22
|
"filePath": "registries/source-tags.json",
|
|
23
23
|
"description": "Source-derived tag registry for extracted framework references.",
|
|
24
|
-
"entryCount":
|
|
24
|
+
"entryCount": 440
|
|
25
25
|
},
|
|
26
26
|
{
|
|
27
27
|
"registryName": "framework-topics",
|
|
28
28
|
"filePath": "registries/framework-topics.json",
|
|
29
29
|
"description": "Topic registry derived from extracted framework-knowledge tags.",
|
|
30
|
-
"entryCount":
|
|
30
|
+
"entryCount": 547
|
|
31
31
|
},
|
|
32
32
|
{
|
|
33
33
|
"registryName": "playbooks",
|
|
34
34
|
"filePath": "registries/playbooks.json",
|
|
35
35
|
"description": "Compiled meta-workflow playbooks (app-creation methodology definitions).",
|
|
36
|
-
"entryCount":
|
|
36
|
+
"entryCount": 26
|
|
37
37
|
},
|
|
38
38
|
{
|
|
39
39
|
"registryName": "assurance-authority-bases",
|
|
@@ -0,0 +1,51 @@
|
|
|
1
|
+
# Assemble & verify — does the built application hold together?
|
|
2
|
+
|
|
3
|
+
This is the last bottom-up step. Everything before it AUTHORED the application; this one asks
|
|
4
|
+
whether what was authored is one working program.
|
|
5
|
+
|
|
6
|
+
## What this playbook does
|
|
7
|
+
|
|
8
|
+
It runs a fixed set of deterministic checks against the application's workspace packages, outside
|
|
9
|
+
any coding agent, and reports one outcome per check. It changes nothing.
|
|
10
|
+
|
|
11
|
+
The check set is host-owned, not authored here. A playbook names semantic check references; turning
|
|
12
|
+
one into an executable command is reviewed host work, which is why a new check cannot be introduced
|
|
13
|
+
by editing this file.
|
|
14
|
+
|
|
15
|
+
## What it verifies today, and what it does not
|
|
16
|
+
|
|
17
|
+
**It verifies** that the application typechecks as a whole — `specifications`, `shared-lib`,
|
|
18
|
+
`backend-api` and `frontend`. That is the question no earlier step answers: the dispatch lane
|
|
19
|
+
typechecks the one package a task mutated, so a build can consist entirely of green tasks and still
|
|
20
|
+
not compile as a program. Cross-package breakage is the characteristic failure of a build assembled
|
|
21
|
+
from independent tasks, and this is where it surfaces.
|
|
22
|
+
|
|
23
|
+
**It does not** boot the application, run its test suite, validate its configuration, or regenerate
|
|
24
|
+
OpenAPI and documentation. Each needs a running stack or a companion affordance that does not exist
|
|
25
|
+
yet. They are absent rather than declared-and-skipped on purpose: the previous version of this
|
|
26
|
+
playbook declared all of them, ran none, and carried a long disclaimer saying so — a check that is
|
|
27
|
+
announced and not executed is worse than one that is missing, because a reader counts it.
|
|
28
|
+
|
|
29
|
+
## Reading the result
|
|
30
|
+
|
|
31
|
+
Three outcomes, and they mean different things:
|
|
32
|
+
|
|
33
|
+
- **every check passed** — the application assembles. This is the signal the phase gate wants.
|
|
34
|
+
- **a check failed** — the application does not assemble. The failure names the package; remediation
|
|
35
|
+
is a refinement re-dispatch, not this playbook.
|
|
36
|
+
- **an infrastructure error** — the check could not be RUN. This is reported separately and must not
|
|
37
|
+
be read as a failure: "the application does not typecheck" and "we could not run the typecheck"
|
|
38
|
+
lead you to entirely different places, and only the first is the application's fault.
|
|
39
|
+
|
|
40
|
+
A dry run resolves the check set and executes nothing, so it tells you what would be verified
|
|
41
|
+
without paying for it.
|
|
42
|
+
|
|
43
|
+
## Quality gate
|
|
44
|
+
|
|
45
|
+
The gate is the check set itself, run by the host. There is no declared gate restating it — a second
|
|
46
|
+
description of a live check is exactly what the retired `qualityGates` field was.
|
|
47
|
+
|
|
48
|
+
## Acceptance
|
|
49
|
+
|
|
50
|
+
The creator reviews the reported outcomes. As everywhere in this lane, the run accepts nothing: a
|
|
51
|
+
human commit is the only acceptance there has ever been.
|
|
@@ -0,0 +1,43 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ref": "bottom_up.assemble-verify",
|
|
3
|
+
"version": "0.2.0",
|
|
4
|
+
"phase": "bottom_up",
|
|
5
|
+
"intent": "Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over the application's four workspace packages (specifications, shared-lib, backend-api, frontend) OUTSIDE any coding agent, and reports a per-check outcome. It fixes NOTHING: a failure is surfaced for a refinement re-dispatch, which is a different playbook's job, and it authors no schemas and writes no code. Deliberately DISTINCT from the refinement phase's coverage audit, which also binds topic 7 but asks a SEMANTIC question (does the built app match the intent — specs diffed against introspected reality). This playbook never diffs intent against reality; if you are judging coverage you are in the refinement lane. Scope honesty for v0.2: the check set is the whole-application TYPECHECK across the four packages — the question 'does it compile as one program', which no per-task check can answer because the dispatch lane typechecks only the package a task mutated. A boot probe, the whole test suite, `wildo config validate` and OpenAPI/docs regeneration are NOT in this set: each needs a running stack or a companion affordance that does not exist, and declaring them here without running them is exactly what made the deleted version of this playbook inert.",
|
|
6
|
+
"functionalTopics": [
|
|
7
|
+
"assemble_verify_and_iterate"
|
|
8
|
+
],
|
|
9
|
+
"preconditions": [
|
|
10
|
+
{
|
|
11
|
+
"kind": "artifact_exists",
|
|
12
|
+
"selector": {
|
|
13
|
+
"family": "build-plan"
|
|
14
|
+
}
|
|
15
|
+
}
|
|
16
|
+
],
|
|
17
|
+
"inputs": [
|
|
18
|
+
{
|
|
19
|
+
"family": "build-plan"
|
|
20
|
+
}
|
|
21
|
+
],
|
|
22
|
+
"outputs": [],
|
|
23
|
+
"stepOutputs": [],
|
|
24
|
+
"method": {
|
|
25
|
+
"guidance": "# Assemble & verify — does the built application hold together?\n\nThis is the last bottom-up step. Everything before it AUTHORED the application; this one asks\nwhether what was authored is one working program.\n\n## What this playbook does\n\nIt runs a fixed set of deterministic checks against the application's workspace packages, outside\nany coding agent, and reports one outcome per check. It changes nothing.\n\nThe check set is host-owned, not authored here. A playbook names semantic check references; turning\none into an executable command is reviewed host work, which is why a new check cannot be introduced\nby editing this file.\n\n## What it verifies today, and what it does not\n\n**It verifies** that the application typechecks as a whole — `specifications`, `shared-lib`,\n`backend-api` and `frontend`. That is the question no earlier step answers: the dispatch lane\ntypechecks the one package a task mutated, so a build can consist entirely of green tasks and still\nnot compile as a program. Cross-package breakage is the characteristic failure of a build assembled\nfrom independent tasks, and this is where it surfaces.\n\n**It does not** boot the application, run its test suite, validate its configuration, or regenerate\nOpenAPI and documentation. Each needs a running stack or a companion affordance that does not exist\nyet. They are absent rather than declared-and-skipped on purpose: the previous version of this\nplaybook declared all of them, ran none, and carried a long disclaimer saying so — a check that is\nannounced and not executed is worse than one that is missing, because a reader counts it.\n\n## Reading the result\n\nThree outcomes, and they mean different things:\n\n- **every check passed** — the application assembles. This is the signal the phase gate wants.\n- **a check failed** — the application does not assemble. The failure names the package; remediation\n is a refinement re-dispatch, not this playbook.\n- **an infrastructure error** — the check could not be RUN. This is reported separately and must not\n be read as a failure: \"the application does not typecheck\" and \"we could not run the typecheck\"\n lead you to entirely different places, and only the first is the application's fault.\n\nA dry run resolves the check set and executes nothing, so it tells you what would be verified\nwithout paying for it.\n\n## Quality gate\n\nThe gate is the check set itself, run by the host. There is no declared gate restating it — a second\ndescription of a live check is exactly what the retired `qualityGates` field was.\n\n## Acceptance\n\nThe creator reviews the reported outcomes. As everywhere in this lane, the run accepts nothing: a\nhuman commit is the only acceptance there has ever been.\n",
|
|
26
|
+
"skillRefs": [
|
|
27
|
+
"journey-status",
|
|
28
|
+
"journey-report",
|
|
29
|
+
"journey-approve"
|
|
30
|
+
],
|
|
31
|
+
"contextSources": [],
|
|
32
|
+
"suspendsForClarification": false,
|
|
33
|
+
"briefAdequacyGate": false,
|
|
34
|
+
"briefAdequacyExcludedSources": []
|
|
35
|
+
},
|
|
36
|
+
"executor": "deterministic_cli",
|
|
37
|
+
"approval": "approve_result",
|
|
38
|
+
"budget": {
|
|
39
|
+
"maxDurationMs": 3600000,
|
|
40
|
+
"maxRuns": 40
|
|
41
|
+
},
|
|
42
|
+
"onFailure": "keep_and_flag"
|
|
43
|
+
}
|
|
@@ -67,10 +67,9 @@ anything:
|
|
|
67
67
|
sequenced before later ones) and the **requirements** + **feature-drafts** (the
|
|
68
68
|
prose contracts each task's brief points the coding agent at).
|
|
69
69
|
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
// (read the module decomposition + per-module resource inventory to decompose)
|
|
70
|
+
(Both are already in your brief: the domain plan renders under "# Accepted application truth", and
|
|
71
|
+
the real module/resource state arrives as the declared `workspace_truth` context section of your brief. There is no command to
|
|
72
|
+
run in this mode.)
|
|
74
73
|
|
|
75
74
|
You **read** `domain-plan` (incl. its relationship drafts) + `roadmap` + `requirements` +
|
|
76
75
|
`feature-drafts`; you **write** the `build-plan` family.
|
|
@@ -97,10 +96,12 @@ chain — so keep them separate and satisfy both:
|
|
|
97
96
|
`extend_application` → `connect_runtime_and_external_capabilities` →
|
|
98
97
|
`assemble_verify_and_iterate`. You author neither the foundation nor the final
|
|
99
98
|
assemble/verify — you decompose the middle bands (Topics 2–6). Topic 1 IS a sibling
|
|
100
|
-
playbook (`bottom_up.foundation`)
|
|
101
|
-
(issue #147
|
|
102
|
-
|
|
103
|
-
than a delegation
|
|
99
|
+
playbook (`bottom_up.foundation`), and Topic 7 IS one again
|
|
100
|
+
(`bottom_up.assemble-verify`, rebuilt under issue #147 after its producer was removed
|
|
101
|
+
with the verification/digest demolition). You still emit no Topic 7 task, and the reason
|
|
102
|
+
is structural rather than a delegation: `BuildPlanTaskTargetKind` has no verification
|
|
103
|
+
member, so app-wide verification cannot be expressed as a build-plan task at all — see
|
|
104
|
+
the verify/quality-gate exclusion below. The edges you must respect: an
|
|
104
105
|
operation task after the resources it acts on; an **app-level** view / navigation
|
|
105
106
|
task after the interaction semantics and resources it composes; an extension after
|
|
106
107
|
the UX it extends; an integration after the resources it connects.
|
|
@@ -261,6 +262,16 @@ skill folder). Do **not** guess a skill name; route through the index.
|
|
|
261
262
|
- **`connect_runtime_and_external_capabilities`** — providers, external connectors,
|
|
262
263
|
billing wiring, email / notification wiring, storage, infra / environment config.
|
|
263
264
|
|
|
265
|
+
## Posture constraints are work, not commentary
|
|
266
|
+
|
|
267
|
+
The vision family's compliance posture and constraints are INPUT on equal footing with the
|
|
268
|
+
requirements: an obligation the posture states — a retention/erasure rule over customer data, a
|
|
269
|
+
terminal-access (cookie/telemetry) posture, an operational-vs-marketing email distinction — needs a
|
|
270
|
+
task that lands it, serving the nfr it substantiates. Do not compress a posture into an adjective
|
|
271
|
+
inside another task's objective ("GDPR-appropriate handling"): an adjective is not schedulable,
|
|
272
|
+
reviewable or landable. If the posture states an obligation and no task expresses it, the
|
|
273
|
+
decomposition is incomplete.
|
|
274
|
+
|
|
264
275
|
(Seed authoring and the label / email generation are companion-owned generation steps —
|
|
265
276
|
see Step 4 — not coding-agent extension tasks.)
|
|
266
277
|
|
|
@@ -268,7 +279,7 @@ Rules:
|
|
|
268
279
|
|
|
269
280
|
- **Every task names a real topic + a real skill.** A task with an invented topic or a
|
|
270
281
|
skill folder that does not exist is a GAP (the dispatch playbook would have nothing
|
|
271
|
-
to run). Route through the
|
|
282
|
+
to run). Route through the declared `skill_catalog` context section of your brief; do not invent.
|
|
272
283
|
- **Respect the topic dependency edges.** An operation task after the resources it acts
|
|
273
284
|
on; an app-level view / navigation task after the interaction semantics **and** every
|
|
274
285
|
resource it composes; an extension after the UX it extends; an integration after the
|
|
@@ -290,6 +301,12 @@ surfaces whose output they consume**:
|
|
|
290
301
|
after the resources / ui-behavior / views whose labels it generates.
|
|
291
302
|
- **`email-templates`** — email template + label generation and label translation.
|
|
292
303
|
Order it after the notification/email surfaces it renders.
|
|
304
|
+
- **`logo`** — the brand mark: an expert panel derives creative directions, marks are
|
|
305
|
+
generated, a vision judge scores them, and the winner is promoted into the
|
|
306
|
+
specifications brand SSOT. Order it after the brand brief exists; it depends on no
|
|
307
|
+
code surface, so it may run early and in parallel with resource work. Author it at
|
|
308
|
+
most once — an application has one accepted mark, and the step skips itself without
|
|
309
|
+
calling a model when one is already accepted.
|
|
293
310
|
|
|
294
311
|
Seed generation joins this vocabulary when its companion pipeline exists. Until then,
|
|
295
312
|
do **not** author a seeds generation step — an unknown `generationStepRef` refuses at
|
|
@@ -404,4 +421,4 @@ turn into dispatched, verified coding-agent runs.
|
|
|
404
421
|
|
|
405
422
|
Formerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim, minus the retired runner's closing sentence:
|
|
406
423
|
|
|
407
|
-
Judge whether the drafted build plan is a coherent, complete, correctly-ordered decomposition of the approved domain plan into coding-agent tasks — WITHOUT straying into how those tasks execute. Assess seven invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) MODULE + RESOURCE COVERAGE — every resource in every module's inventory (mainResources + supportingResources) has build tasks; a resource with no task is a GAP (the build would not produce it). Task `moduleRef` values must be module ids the workspace section lists (an invented module id is a GAP — the dispatcher cannot route it), and a task whose objective CREATES a resource the workspace section shows already exists — instead of enriching it — is a CONCERN (it dispatches a no-op). Module slices are scaffolded by the foundation step (a sibling playbook), so a module needs a dedicated ensure-module task ONLY where foundation did not establish it — a module whose resources have tasks but which carries no redundant scaffold task is NOT a GAP (do not flag the absence of a module-scaffold task foundation already owns); a module added to the plan after foundation with neither a foundation slice nor an ensure-module task IS a GAP. (2) TASK WELL-FORMEDNESS — every task names exactly ONE functional topic that is a real MetaWorkflow_FunctionalTopic value (configure_application_foundation / model_domain_graph / define_interaction_semantics / shape_user_experience / extend_application / connect_runtime_and_external_capabilities / assemble_verify_and_iterate) and at least one skill that is a real folder in the app-knowledge skill catalog; a task with an invented topic or a dangling skill is a GAP. (3) PER-RESOURCE STAGE ORDER — for each resource, its tasks respect the inner order schema -> config -> ui-behavior -> spec; a config task ordered before that resource's schema task, or a spec task before its ui-behavior task, is a GAP (the build stage would run against a missing prerequisite). A supportingResource (e.g. a pure junction / lookup entity) may legitimately OMIT stages it does not need — a junction with schema + config and no ui-behavior is fine; only an out-of-ORDER stage (or a mainResource missing schema/config) is a GAP, not an intentionally-omitted stage on a supporting resource. (4) TOPIC DEPENDENCY ORDER — tasks respect the topic dependency edges (model_domain_graph before define_interaction_semantics; app-level shape_user_experience [views / navigation composing multiple resources or operations] after the interaction semantics and resources it composes; extend_application after the UX it extends; connect_runtime_and_external_capabilities after the resources it connects). Note the deliberate exception: a resource's OWN ui-behavior (its field displays / forms, a shape_user_experience task) depends only on that resource's own schema + config and MAY precede cross-resource operations — that is NOT a violation. What IS a GAP: an app-level view composing resources/operations placed before they exist, an integration task before the resources it connects, or any user-experience task before that resource's schema task. The per-resource spec task is a documentation capstone (topic model_domain_graph) and must be ordered after the schema / config / ui-behavior stages it documents; a spec task before its ui-behavior stage is a GAP. (5) RELATIONSHIP COVERAGE — every relationship-draft has a wiring task (bound to the module-relationships skill) ordered AFTER both endpoint resources' schema tasks; a relationship with no wiring task, or one ordered before its endpoints exist, is a GAP. (6) COMPANION-GENERATION INTERLEAVE — the executable companion-owned generation steps (`i18n-labels`, `email-templates`) are present and placed AFTER the resources / modules whose output they consume; a labels-generation task ordered before the resources it labels, or a missing executable generation step for authored surfaces, is a CONCERN. Do NOT flag the absence of a seeds step — seed generation has no companion pipeline yet and must not be authored. (7) BOUNDARY DISCIPLINE — the plan stays at DECOMPOSITION depth: it names tasks, their topic, their skill(s), their target, and their ordering intent; it does NOT specify how a task is DISPATCHED (single-flight locking, change-set capture, git baseline, verify/quality-gate mechanics = the dispatch-orchestration playbook) and does NOT solve multi-agent SCALE or interleaving concurrency (= the scale playbook). Any task that describes how a task EXECUTES rather than WHAT it builds, or that authors a schema / resolves a cardinality into a concrete FK / generates code, is a CONCERN (scope creep out of the decomposition phase). (The checklist is declarative: nothing executes it; the deterministic gates and the creator's approval remain the floors.)
|
|
424
|
+
Judge whether the drafted build plan is a coherent, complete, correctly-ordered decomposition of the approved domain plan into coding-agent tasks — WITHOUT straying into how those tasks execute. Assess seven invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) MODULE + RESOURCE COVERAGE — every resource in every module's inventory (mainResources + supportingResources) has build tasks; a resource with no task is a GAP (the build would not produce it). Task `moduleRef` values must be module ids the workspace section lists (an invented module id is a GAP — the dispatcher cannot route it), and a task whose objective CREATES a resource the workspace section shows already exists — instead of enriching it — is a CONCERN (it dispatches a no-op). Module slices are scaffolded by the foundation step (a sibling playbook), so a module needs a dedicated ensure-module task ONLY where foundation did not establish it — a module whose resources have tasks but which carries no redundant scaffold task is NOT a GAP (do not flag the absence of a module-scaffold task foundation already owns); a module added to the plan after foundation with neither a foundation slice nor an ensure-module task IS a GAP. (2) TASK WELL-FORMEDNESS — every task names exactly ONE functional topic that is a real MetaWorkflow_FunctionalTopic value (configure_application_foundation / model_domain_graph / define_interaction_semantics / shape_user_experience / extend_application / connect_runtime_and_external_capabilities / assemble_verify_and_iterate) and at least one skill that is a real folder in the app-knowledge skill catalog; a task with an invented topic or a dangling skill is a GAP. (3) PER-RESOURCE STAGE ORDER — for each resource, its tasks respect the inner order schema -> config -> ui-behavior -> spec; a config task ordered before that resource's schema task, or a spec task before its ui-behavior task, is a GAP (the build stage would run against a missing prerequisite). A supportingResource (e.g. a pure junction / lookup entity) may legitimately OMIT stages it does not need — a junction with schema + config and no ui-behavior is fine; only an out-of-ORDER stage (or a mainResource missing schema/config) is a GAP, not an intentionally-omitted stage on a supporting resource. (4) TOPIC DEPENDENCY ORDER — tasks respect the topic dependency edges (model_domain_graph before define_interaction_semantics; app-level shape_user_experience [views / navigation composing multiple resources or operations] after the interaction semantics and resources it composes; extend_application after the UX it extends; connect_runtime_and_external_capabilities after the resources it connects). Note the deliberate exception: a resource's OWN ui-behavior (its field displays / forms, a shape_user_experience task) depends only on that resource's own schema + config and MAY precede cross-resource operations — that is NOT a violation. What IS a GAP: an app-level view composing resources/operations placed before they exist, an integration task before the resources it connects, or any user-experience task before that resource's schema task. The per-resource spec task is a documentation capstone (topic model_domain_graph) and must be ordered after the schema / config / ui-behavior stages it documents; a spec task before its ui-behavior stage is a GAP. (5) RELATIONSHIP COVERAGE — every relationship-draft has a wiring task (bound to the module-relationships skill) ordered AFTER both endpoint resources' schema tasks; a relationship with no wiring task, or one ordered before its endpoints exist, is a GAP. (6) COMPANION-GENERATION INTERLEAVE — the executable companion-owned generation steps (`i18n-labels`, `email-templates`, `logo`) are present and placed AFTER the resources / modules whose output they consume; a labels-generation task ordered before the resources it labels, or a missing executable generation step for authored surfaces, is a CONCERN. `logo` is the exception to the ordering half — it consumes the brand brief rather than any code surface, so it is unordered with respect to resource work and only its ABSENCE (on an application with a brand brief) is a CONCERN. Do NOT flag the absence of a seeds step — seed generation has no companion pipeline yet and must not be authored. (7) BOUNDARY DISCIPLINE — the plan stays at DECOMPOSITION depth: it names tasks, their topic, their skill(s), their target, and their ordering intent; it does NOT specify how a task is DISPATCHED (single-flight locking, change-set capture, git baseline, verify/quality-gate mechanics = the dispatch-orchestration playbook) and does NOT solve multi-agent SCALE or interleaving concurrency (= the scale playbook). Any task that describes how a task EXECUTES rather than WHAT it builds, or that authors a schema / resolves a cardinality into a concrete FK / generates code, is a CONCERN (scope creep out of the decomposition phase). (The checklist is declarative: nothing executes it; the deterministic gates and the creator's approval remain the floors.)
|