dew-method 0.1.0

package/src/dew-skills/3-solutioning/dew-data-model-design/assets/history-scd-rubric.md

@@ -0,0 +1,38 @@
+# History and SCD Rubric
+
+## No history
+
+Use when:
+- entity attributes are static or not important historically
+- MVP does not require point-in-time analysis
+
+## Type 1 overwrite
+
+Use when:
+- only current state matters
+- historical changes are not important
+
+## Type 2 history
+
+Use when:
+- historical attribute changes affect analysis
+- point-in-time correctness matters
+
+## Snapshot history
+
+Use when:
+- periodic state is useful
+- source provides snapshots
+- changes are hard to track event-by-event
+
+## Event history
+
+Use when:
+- source provides events
+- full sequence matters
+
+## Rule
+
+Do not choose SCD/history pattern silently.
+
+History handling affects storage, transformation, DQ, and serving semantics.

package/src/dew-skills/3-solutioning/dew-data-model-design/assets/kpi-to-model-mapping-template.md

@@ -0,0 +1,9 @@
+# KPI to Model Mapping Template
+
+```markdown
+# KPI to Model Mapping
+
+| KPI ID | KPI Name | Feasibility Status | Gold Model | Gold Field | Formula Rule | Grain | Caveat |
+|---|---|---|---|---|---|---|---|
+| KPI-001 | | Verified/Caveated | gold_x | | | | |
+```

package/src/dew-skills/3-solutioning/dew-data-model-design/assets/model-grain-rubric.md

@@ -0,0 +1,39 @@
+# Model Grain Rubric
+
+## Model grain definition
+
+A model grain answers:
+
+What does one row represent?
+
+Examples:
+- one row per ward per day
+- one row per customer per month
+- one row per source event
+- one row per station per hour
+- one row per product per store per day
+
+## Good grain
+
+A good grain is:
+- explicit
+- testable
+- linked to keys
+- compatible with KPI/serving needs
+- documented in model spec
+
+## Bad grain
+
+A bad grain is:
+- implicit
+- mixed in one model
+- changed without documentation
+- not testable with uniqueness rules
+
+## Grain decision options
+
+A. One grain per model  
+B. Multiple models for multiple grains  
+C. Bridge table between grains  
+D. Aggregate to serving grain in Gold  
+E. Return to transformation design

package/src/dew-skills/3-solutioning/dew-data-model-design/checklist.md

@@ -0,0 +1,18 @@
+# Data Model Design Checklist
+
+- [ ] Transformation design loaded.
+- [ ] Business rule catalog loaded.
+- [ ] KPI feasibility report loaded.
+- [ ] Data product PRD loaded.
+- [ ] Silver models listed.
+- [ ] Gold models listed.
+- [ ] Each model has explicit grain.
+- [ ] Each model has keys.
+- [ ] Each model has field list.
+- [ ] KPI-to-model mapping created.
+- [ ] Bridge tables identified where needed.
+- [ ] History/SCD decision made.
+- [ ] Caveats documented.
+- [ ] User approved model grain decisions.
+- [ ] Decision log updated.
+- [ ] Learning log updated if enabled.

package/src/dew-skills/3-solutioning/dew-data-model-design/customize.toml

@@ -0,0 +1,36 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for dew-data-model-design.
+
+[workflow]
+
+activation_steps_prepend = []
+activation_steps_append = []
+
+persistent_facts = [
+  "file:{project-root}/**/transformation-design.md",
+  "file:{project-root}/**/business-rule-catalog.md",
+  "file:{project-root}/**/kpi-feasibility-report.md",
+  "file:{project-root}/**/data-product-prd.md",
+  "file:{project-root}/**/source-validation-report.md",
+  "file:{project-root}/**/storage-design.md",
+  "file:{project-root}/**/validation-evidence-index.md",
+  "file:{project-root}/**/.decision-log.md",
+  "file:{project-root}/**/.learning-log.md",
+]
+
+on_complete = ""
+
+data_model_spec_template = "assets/data-model-spec-template.md"
+kpi_to_model_mapping_template = "assets/kpi-to-model-mapping-template.md"
+model_grain_rubric = "assets/model-grain-rubric.md"
+dimensional_modeling_rubric = "assets/dimensional-modeling-rubric.md"
+history_scd_rubric = "assets/history-scd-rubric.md"
+checklist = "checklist.md"
+
+model_output_path = "{planning_artifacts}/data-model-design"
+run_folder_pattern = "data-model-design-{project_name}-{date}"
+
+decision_log_path = "{planning_artifacts}/.decision-log.md"
+learning_log_path = "{learning_artifacts}/.learning-log.md"
+evidence_index_path = "{evidence_artifacts}/validation-evidence-index.md"

package/src/dew-skills/3-solutioning/dew-data-model-design/steps/step-01-init.md

@@ -0,0 +1,64 @@
+# Step 01 — Data Model Design Initialization
+
+## Mandatory Rules
+
+- Do not design models before transformation design exists.
+- Do not proceed if transformation design is missing.
+
+## Task
+
+Initialize Data Model Design workflow.
+
+## Sequence
+
+### 1. Detect existing workflow
+
+Look for:
+- `{workflow.model_output_path}/**/data-model-spec.md`
+- `{planning_artifacts}/**/*data*model*.md`
+
+If unfinished model design exists, offer to resume.
+
+### 2. Validate prerequisites
+
+Look for:
+- `transformation-design.md`
+- `business-rule-catalog.md`
+- `kpi-feasibility-report.md`
+
+If missing:
+- missing transformation → return to `dew-transformation-design`
+- missing KPI feasibility → `HALT-03`
+
+### 3. Create workspace
+
+Bind `{doc_workspace}` to:
+
+`{workflow.model_output_path}/{workflow.run_folder_pattern}/`
+
+Create:
+- `data-model-spec.md`
+- `kpi-to-model-mapping.md`
+
+Use templates.
+
+### 4. Initialize frontmatter
+
+Set:
+
+```yaml
+status: draft
+stepsCompleted:
+  - step-01-init
+decisionGates:
+  GATE-24-modeling-grain:
+    status: pending
+  GATE-history-scd:
+    status: pending
+```
+
+### 5. Continue checkpoint
+
+Ask:
+
+`[C] Continue to load transformation context`

package/src/dew-skills/3-solutioning/dew-data-model-design/steps/step-02-load-transformation-context.md

@@ -0,0 +1,44 @@
+# Step 02 — Load Transformation Context
+
+## Mandatory Rules
+
+- Load transformation rules before designing models.
+- Do not invent KPI mapping.
+- Do not drop caveats.
+
+## Task
+
+Extract modeling context.
+
+## Extract
+
+From transformation design:
+- Silver outputs
+- Gold outputs
+- grain transformations
+- business rules
+- KPI formula mapping
+- caveats
+
+From KPI feasibility:
+- KPI status
+- formula
+- required fields
+- caveats
+
+From PRD:
+- consumers
+- serving expectations
+- trust expectation
+
+## Update
+
+Update:
+- data-model-spec.md
+- kpi-to-model-mapping.md
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to model grain gate`

package/src/dew-skills/3-solutioning/dew-data-model-design/steps/step-03-model-grain-gate.md

@@ -0,0 +1,48 @@
+# Step 03 — Model Grain Gate
+
+## Mandatory Rules
+
+- Stop at this gate.
+- Every model must have explicit grain.
+- User must approve modeling grain strategy.
+- If grain is unclear, trigger HALT-07.
+
+## Required table
+
+| Model | Layer | Proposed Grain | Keys | Related KPI | Risk |
+|---|---|---|---|---|---|
+
+## Options
+
+A. One grain per model  
+B. Multiple models for multiple grains  
+C. Bridge table between grains  
+D. Aggregate to serving grain in Gold  
+E. Return to transformation design  
+
+## User decision
+
+Ask user to choose A/B/C/D/E.
+
+Do not continue until user chooses.
+
+## Record
+
+Update:
+- data-model-spec.md
+- .decision-log.md
+- .learning-log.md if enabled
+
+Update frontmatter:
+
+```yaml
+decisionGates:
+  GATE-24-modeling-grain:
+    status: approved / approved-with-caveats / blocked
+```
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to Silver model design`

package/src/dew-skills/3-solutioning/dew-data-model-design/steps/step-04-silver-model-design.md

@@ -0,0 +1,33 @@
+# Step 04 — Silver Model Design
+
+## Mandatory Rules
+
+- Silver models must preserve or explicitly transform source grain.
+- Required fields must map to source or rule.
+- Metadata fields must follow storage design.
+
+## Task
+
+Design Silver models.
+
+For each Silver model:
+- purpose
+- grain
+- input datasets
+- keys
+- fields
+- metadata
+- business rules
+- caveats
+- DQ handoff
+
+## Update
+
+Update:
+- data-model-spec.md
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to Gold model design`

package/src/dew-skills/3-solutioning/dew-data-model-design/steps/step-05-gold-model-design.md

@@ -0,0 +1,35 @@
+# Step 05 — Gold Model Design
+
+## Mandatory Rules
+
+- Gold models must map to consumers/KPIs.
+- Do not include rejected/deferred KPI unless user approved caveat.
+- KPI fields must map to formula rules.
+
+## Task
+
+Design Gold models.
+
+For each Gold model:
+- purpose
+- consumer
+- KPI(s)
+- grain
+- type
+- input Silver datasets
+- keys
+- fields
+- KPI mapping
+- caveats
+
+## Update
+
+Update:
+- data-model-spec.md
+- kpi-to-model-mapping.md
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to history and bridge design`

package/src/dew-skills/3-solutioning/dew-data-model-design/steps/step-06-history-and-bridge-design.md

@@ -0,0 +1,48 @@
+# Step 06 — History and Bridge Design
+
+## Mandatory Rules
+
+- Do not choose SCD/history pattern silently.
+- Bridge assumptions must be explicit.
+- User must approve history/bridge design if it affects KPI semantics.
+
+## Task
+
+Define:
+- dimensions
+- facts
+- bridges
+- history/SCD strategy
+
+## History options
+
+A. No history  
+B. Type 1 overwrite  
+C. Type 2 history  
+D. Snapshot history  
+E. Event history  
+
+Ask user if history impacts KPI or serving trust.
+
+## Bridge options
+
+A. No bridge required  
+B. Static bridge table  
+C. Time-aware bridge table  
+D. Rule-derived bridge  
+E. Return to transformation design  
+
+Ask user if bridge affects KPI semantics.
+
+## Update
+
+Update:
+- data-model-spec.md
+- .decision-log.md
+- .learning-log.md if enabled
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to finalize data model design`

package/src/dew-skills/3-solutioning/dew-data-model-design/steps/step-07-finalize.md

@@ -0,0 +1,36 @@
+# Step 07 — Finalize Data Model Design
+
+## Mandatory Rules
+
+- Do not finalize if model grain gate is unresolved.
+- Do not finalize if primary KPI has no Gold model or approved deferment.
+- Run checklist.
+
+## Required outputs
+
+- data-model-spec.md
+- kpi-to-model-mapping.md
+- decision log entries
+- learning log entries if enabled
+
+## Final status
+
+Set:
+
+```yaml
+status: final
+stepsCompleted:
+  - step-01-init
+  - step-02-load-transformation-context
+  - step-03-model-grain-gate
+  - step-04-silver-model-design
+  - step-05-gold-model-design
+  - step-06-history-and-bridge-design
+  - step-07-finalize
+```
+
+## Next workflow
+
+Recommend:
+
+`dew-data-quality-design`

package/src/dew-skills/3-solutioning/dew-data-quality-design/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: dew-data-quality-design
+description: Define data quality rules, severity, actions, evidence requirements, and test handoff for source, transformation, and serving layers.
+---
+
+# DEW Data Quality Design
+
+**Goal:** Create a data quality rule catalog and gate policy for source, transformation, and serving layers.
+
+**Your Role:** You are a data quality design facilitator.
+
+You translate source risks, transformation rules, model grain, KPI needs, and trust expectations into concrete DQ rules.
+
+You may recommend, but you must not decide.
+
+## Mandatory Rules
+
+- Do not create generic DQ rules without linking them to source/model/KPI.
+- Do not treat DQ as optional for internal decision-support or higher trust products.
+- DQ rules must have severity and action.
+- Blocking rules must be explicit.
+- If DQ rules are missing, trigger `HALT-14 — DQ Rules Missing`.
+- If evidence is missing, trigger `HALT-18 — No Validation Evidence`.
+
+## Workflow Architecture
+
+This workflow uses step-file architecture.
+
+## On Activation
+
+1. Resolve customization.
+2. Execute `{workflow.activation_steps_prepend}`.
+3. Load persistent facts.
+4. Load config if present.
+5. Load:
+   - `{workflow.data_quality_rules_template}`
+   - `{workflow.dq_rule_catalog_template}`
+   - `{workflow.dq_severity_rubric}`
+   - `{workflow.dq_rule_type_rubric}`
+   - `{workflow.dq_gate_policy_template}`
+6. Greet user in configured language.
+
+## Execution
+
+Read fully and follow:
+
+`steps/step-01-init.md`

package/src/dew-skills/3-solutioning/dew-data-quality-design/assets/data-quality-rules-template.md

@@ -0,0 +1,87 @@
+# Data Quality Rules Template
+
+```markdown
+---
+title: "{Project Name} Data Quality Rules"
+status: draft
+created: {YYYY-MM-DD}
+updated: {YYYY-MM-DD}
+workflow: dew
+phase: "3-solutioning"
+stepsCompleted: []
+decisionGates:
+  GATE-18-data-quality-rule:
+    status: pending
+evidence: []
+assumptions: []
+caveats: []
+---
+
+# Data Quality Rules: {Project Name}
+
+## 0. Document Purpose
+
+This document defines data quality rules, severity, action policy, evidence requirements, and implementation handoff.
+
+## 1. Input Context
+
+| Input | Path | Status | Notes |
+|---|---|---|---|
+| Data Model Spec | | Loaded/Missing | |
+| Transformation Design | | Loaded/Missing | |
+| Source Validation | | Loaded/Missing | |
+| KPI Feasibility | | Loaded/Missing | |
+| PRD | | Loaded/Missing | |
+
+## 2. Trust Expectation
+
+Selected trust level:
+
+DQ implication:
+
+## 3. DQ Rule Summary
+
+| Rule ID | Layer | Dataset | Field/Key | Rule Type | Severity | Action | Related KPI |
+|---|---|---|---|---|---|---|---|
+| DQ-001 | Silver | | | not_null | High | fail/quarantine/warn | KPI-001 |
+
+## 4. Source-Level DQ Rules
+
+## 5. Bronze / Ingestion DQ Rules
+
+## 6. Silver DQ Rules
+
+## 7. Gold / KPI DQ Rules
+
+## 8. Serving DQ Rules
+
+## 9. DQ Gate Policy
+
+| Severity | Default Action | Can Proceed? | Requires User Approval? |
+|---|---|---|---|
+| Critical | fail | No | Yes |
+| High | fail/quarantine | Usually no | Yes |
+| Medium | warn/caveat | Maybe | Maybe |
+| Low | warn/log | Yes | No |
+
+## 10. DQ Evidence Requirements
+
+Evidence to produce during implementation:
+- test result
+- row count
+- null report
+- duplicate report
+- range check report
+- referential integrity report
+- freshness check
+- KPI plausibility result
+
+## 11. Handoff to Implementation
+
+Implementation stories must include:
+- DQ rule IDs
+- expected test files
+- pass/fail behavior
+- evidence output paths
+- caveats
+```

package/src/dew-skills/3-solutioning/dew-data-quality-design/assets/dq-gate-policy-template.md

@@ -0,0 +1,38 @@
+# DQ Gate Policy Template
+
+```markdown
+# DQ Gate Policy
+
+## Purpose
+
+Define how DQ failures affect pipeline progression and serving.
+
+## Policy Table
+
+| Severity | Action | Pipeline Continues? | Data Served? | User Approval Required? |
+|---|---|---|---|---|
+| Critical | fail | No | No | Yes |
+| High | fail/quarantine | Maybe | No unless caveated | Yes |
+| Medium | warn/caveat | Yes | Yes with caveat | Maybe |
+| Low | log | Yes | Yes | No |
+
+## Layer Policy
+
+### Source / Ingestion
+
+### Silver
+
+### Gold
+
+### Serving
+
+## Evidence Policy
+
+Every DQ run must produce:
+- timestamp
+- dataset
+- rule IDs
+- pass/fail counts
+- failed records location if applicable
+- caveats
+```

package/src/dew-skills/3-solutioning/dew-data-quality-design/assets/dq-rule-catalog-template.md

@@ -0,0 +1,55 @@
+# DQ Rule Catalog Template
+
+```markdown
+# DQ Rule Catalog
+
+## Rule Table
+
+| Rule ID | Name | Layer | Dataset | Field/Key | Rule Type | Severity | Action | Related KPI | Status |
+|---|---|---|---|---|---|---|---|---|---|
+| DQ-001 | | Silver | | | not_null | High | fail | KPI-001 | proposed |
+
+## Rule Detail
+
+## DQ-001 — {Rule Name}
+
+### Layer
+
+### Dataset
+
+### Field / Key
+
+### Rule Type
+
+### Rule Logic
+
+```text
+...
+```
+
+### Expected Result
+
+### Severity
+
+### Action
+
+* fail pipeline
+* quarantine records
+* warn and continue
+* log only
+* require user review
+
+### Related KPI / Consumer
+
+### Evidence Required
+
+### Owner
+
+### Status
+
+* proposed
+* approved
+* approved-with-caveats
+* rejected
+* deferred
+```