dew-method 0.1.0

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

@@ -0,0 +1,53 @@
+# DQ Rule Type Rubric
+
+## not_null
+
+Use for required fields.
+
+## unique
+
+Use for primary keys and grain checks.
+
+## accepted_range
+
+Use for numeric values with valid domain.
+
+## accepted_values
+
+Use for categorical fields.
+
+## referential_integrity
+
+Use when foreign key/dimension relationship must hold.
+
+## freshness
+
+Use when source/product freshness matters.
+
+## schema_contract
+
+Use for expected columns/types/schema drift.
+
+## row_count_anomaly
+
+Use to detect unexpected row volume changes.
+
+## duplicate_check
+
+Use when duplicate records affect metrics.
+
+## valid_geography
+
+Use for region/province/ward/station consistency.
+
+## valid_time_window
+
+Use for date/time range and completeness.
+
+## business_rule_consistency
+
+Use for domain-specific logic or KPI assumptions.
+
+## KPI_plausibility
+
+Use for final metric output sanity checks.

package/src/dew-skills/3-solutioning/dew-data-quality-design/assets/dq-severity-rubric.md

@@ -0,0 +1,44 @@
+# DQ Severity Rubric
+
+## Critical
+
+Use when:
+- failure invalidates primary KPI
+- failure creates unsafe/misleading decision
+- privacy/security issue exists
+- grain uniqueness fails for Gold model
+
+Default action:
+- fail pipeline
+- do not serve data
+
+## High
+
+Use when:
+- required field missing
+- key uniqueness fails
+- critical range invalid
+- source freshness misses requirement
+
+Default action:
+- fail or quarantine
+- user review required
+
+## Medium
+
+Use when:
+- non-critical field has quality issue
+- sample coverage incomplete
+- partial missingness affects caveat
+
+Default action:
+- warn and document caveat
+
+## Low
+
+Use when:
+- documentation/naming/minor issue
+- does not affect KPI or decision
+
+Default action:
+- log only

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

@@ -0,0 +1,19 @@
+# Data Quality Design Checklist
+
+- [ ] Data model spec loaded.
+- [ ] Transformation design loaded.
+- [ ] Source validation loaded.
+- [ ] KPI feasibility loaded.
+- [ ] Trust expectation loaded.
+- [ ] DQ rules linked to source/model/KPI.
+- [ ] Source-level DQ rules defined.
+- [ ] Silver DQ rules defined.
+- [ ] Gold/KPI DQ rules defined.
+- [ ] Serving DQ expectations defined.
+- [ ] Rule severity assigned.
+- [ ] Rule action assigned.
+- [ ] DQ gate policy created.
+- [ ] DQ evidence requirements defined.
+- [ ] User approved DQ rule gate.
+- [ ] Decision log updated.
+- [ ] Learning log updated if enabled.

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

@@ -0,0 +1,38 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for dew-data-quality-design.
+
+[workflow]
+
+activation_steps_prepend = []
+activation_steps_append = []
+
+persistent_facts = [
+  "file:{project-root}/**/data-model-spec.md",
+  "file:{project-root}/**/kpi-to-model-mapping.md",
+  "file:{project-root}/**/transformation-design.md",
+  "file:{project-root}/**/business-rule-catalog.md",
+  "file:{project-root}/**/source-validation-report.md",
+  "file:{project-root}/**/source-contract-test*.md",
+  "file:{project-root}/**/kpi-feasibility-report.md",
+  "file:{project-root}/**/data-product-prd.md",
+  "file:{project-root}/**/validation-evidence-index.md",
+  "file:{project-root}/**/.decision-log.md",
+  "file:{project-root}/**/.learning-log.md",
+]
+
+on_complete = ""
+
+data_quality_rules_template = "assets/data-quality-rules-template.md"
+dq_rule_catalog_template = "assets/dq-rule-catalog-template.md"
+dq_severity_rubric = "assets/dq-severity-rubric.md"
+dq_rule_type_rubric = "assets/dq-rule-type-rubric.md"
+dq_gate_policy_template = "assets/dq-gate-policy-template.md"
+checklist = "checklist.md"
+
+dq_output_path = "{planning_artifacts}/data-quality-design"
+run_folder_pattern = "data-quality-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-quality-design/steps/step-01-init.md

@@ -0,0 +1,67 @@
+# Step 01 — Data Quality Design Initialization
+
+## Mandatory Rules
+
+- Do not design DQ before data model spec exists.
+- Do not proceed if transformation design is missing.
+- DQ must be tied to source/model/KPI.
+
+## Task
+
+Initialize Data Quality Design workflow.
+
+## Sequence
+
+### 1. Detect existing workflow
+
+Look for:
+- `{workflow.dq_output_path}/**/data-quality-rules.md`
+- `{planning_artifacts}/**/*quality*.md`
+
+If unfinished DQ design exists, offer to resume.
+
+### 2. Validate prerequisites
+
+Look for:
+- `data-model-spec.md`
+- `transformation-design.md`
+- `source-validation-report.md`
+- `kpi-feasibility-report.md`
+
+If missing:
+- missing model → return to `dew-data-model-design`
+- missing transformation → return to `dew-transformation-design`
+- missing source validation → `HALT-06`
+- missing KPI feasibility → `HALT-03`
+
+### 3. Create workspace
+
+Bind `{doc_workspace}` to:
+
+`{workflow.dq_output_path}/{workflow.run_folder_pattern}/`
+
+Create:
+- `data-quality-rules.md`
+- `dq-rule-catalog.md`
+- `dq-gate-policy.md`
+
+Use templates.
+
+### 4. Initialize frontmatter
+
+Set:
+
+```yaml
+status: draft
+stepsCompleted:
+  - step-01-init
+decisionGates:
+  GATE-18-data-quality-rule:
+    status: pending
+```
+
+### 5. Continue checkpoint
+
+Ask:
+
+`[C] Continue to load model and source context`

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

@@ -0,0 +1,48 @@
+# Step 02 — Load Model and Source Context
+
+## Mandatory Rules
+
+- Load model, transformation, source, KPI, and trust context.
+- Do not create generic DQ rules without target.
+
+## Task
+
+Extract DQ-relevant context.
+
+## Extract
+
+From model spec:
+- datasets
+- fields
+- keys
+- grain
+- KPI mapping
+
+From transformation design:
+- transformation rules
+- business rules
+- grain changes
+- caveats
+
+From source validation:
+- source DQ risks
+- field coverage
+- schema risks
+- freshness risks
+
+From PRD:
+- trust expectation
+- consumers
+- serving mode
+
+## Update
+
+Update:
+- data-quality-rules.md
+- dq-rule-catalog.md
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to DQ rule discovery`

package/src/dew-skills/3-solutioning/dew-data-quality-design/steps/step-03-dq-rule-discovery.md

@@ -0,0 +1,53 @@
+# Step 03 — DQ Rule Discovery
+
+## Mandatory Rules
+
+- Every DQ rule must link to dataset/field/key/KPI or source.
+- Do not create vague rules like “check data quality”.
+- Each critical dataset needs at least grain/key check.
+
+## Task
+
+Discover candidate DQ rules.
+
+## Rule categories
+
+- source-level
+- ingestion/Bronze
+- Silver
+- Gold/KPI
+- serving
+
+## Required rule types
+
+Consider:
+- not_null
+- unique
+- accepted_range
+- accepted_values
+- referential_integrity
+- freshness
+- schema_contract
+- row_count_anomaly
+- duplicate_check
+- valid_geography
+- valid_time_window
+- business_rule_consistency
+- KPI_plausibility
+
+## Required table
+
+| Rule ID | Layer | Dataset | Field/Key | Rule Type | Related KPI | Reason |
+|---|---|---|---|---|---|---|
+
+## Update
+
+Update:
+- data-quality-rules.md
+- dq-rule-catalog.md
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to DQ rule gate`

package/src/dew-skills/3-solutioning/dew-data-quality-design/steps/step-04-dq-rule-gate.md

@@ -0,0 +1,57 @@
+# Step 04 — DQ Rule Gate
+
+## Mandatory Rules
+
+- Stop at this gate.
+- User must approve minimum DQ rule set.
+- DQ rules must match trust expectation.
+- If rules are missing, trigger HALT-14.
+
+## Task
+
+Run GATE-18 — Data Quality Rule Gate.
+
+## Options
+
+A. Approve minimum DQ rules  
+B. Approve with caveats  
+C. Add stricter DQ rules  
+D. Reduce DQ scope for MVP  
+E. Return to model/transformation design  
+
+## Required summary
+
+| Area | Minimum Rules | Risk if Missing | Recommendation |
+|---|---|---|---|
+| Source | | | |
+| Silver | | | |
+| Gold | | | |
+| Serving | | | |
+
+## User decision
+
+Ask user to choose A/B/C/D/E.
+
+Do not continue until user chooses.
+
+## Record
+
+Update:
+- dq-rule-catalog.md
+- data-quality-rules.md
+- .decision-log.md
+- .learning-log.md if enabled
+
+Update frontmatter:
+
+```yaml
+decisionGates:
+  GATE-18-data-quality-rule:
+    status: approved / approved-with-caveats / blocked
+```
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to severity and action policy`

package/src/dew-skills/3-solutioning/dew-data-quality-design/steps/step-05-dq-severity-and-action-policy.md

@@ -0,0 +1,44 @@
+# Step 05 — DQ Severity and Action Policy
+
+## Mandatory Rules
+
+- Every DQ rule must have severity.
+- Every DQ rule must have action.
+- Blocking rules must be explicit.
+
+## Task
+
+Assign severity and actions.
+
+## Severity
+
+- Critical
+- High
+- Medium
+- Low
+
+## Actions
+
+- fail pipeline
+- quarantine records
+- warn and continue
+- log only
+- require user review
+
+## Required table
+
+| Rule ID | Severity | Action | Pipeline Continues? | Data Served? |
+|---|---|---|---|---|
+
+## Update
+
+Update:
+- dq-rule-catalog.md
+- dq-gate-policy.md
+- data-quality-rules.md
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to DQ evidence and test handoff`

package/src/dew-skills/3-solutioning/dew-data-quality-design/steps/step-06-dq-evidence-and-test-handoff.md

@@ -0,0 +1,42 @@
+# Step 06 — DQ Evidence and Test Handoff
+
+## Mandatory Rules
+
+- Every DQ rule must produce evidence during implementation.
+- Do not define DQ rules without test/evidence handoff.
+- Missing evidence requirements trigger HALT-18.
+
+## Task
+
+Define implementation handoff.
+
+## For each rule
+
+Record:
+
+| Rule ID | Test Type | Expected Evidence | Output Path | Story Handoff |
+|---|---|---|---|---|
+
+## Evidence examples
+
+- row count report
+- null report
+- duplicate report
+- failed records file
+- DQ summary markdown
+- test result JSON
+- pipeline log
+- freshness report
+
+## Update
+
+Update:
+- data-quality-rules.md
+- dq-rule-catalog.md
+- dq-gate-policy.md
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to finalize DQ design`

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

@@ -0,0 +1,37 @@
+# Step 07 — Finalize Data Quality Design
+
+## Mandatory Rules
+
+- Do not finalize if DQ rule gate is unresolved.
+- Do not finalize if critical datasets have no DQ rules.
+- Run checklist.
+
+## Required outputs
+
+- data-quality-rules.md
+- dq-rule-catalog.md
+- dq-gate-policy.md
+- decision log entries
+- learning log entries if enabled
+
+## Final status
+
+Set:
+
+```yaml
+status: final
+stepsCompleted:
+  - step-01-init
+  - step-02-load-model-and-source-context
+  - step-03-dq-rule-discovery
+  - step-04-dq-rule-gate
+  - step-05-dq-severity-and-action-policy
+  - step-06-dq-evidence-and-test-handoff
+  - step-07-finalize
+```
+
+## Next workflow
+
+Recommend:
+
+`dew-serving-design`

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

@@ -0,0 +1,47 @@
+---
+name: dew-dataops-design
+description: Design operational readiness, monitoring, alerting, incident handling, backfill, change process, environments, and CI/CD handoff.
+---
+
+# DEW DataOps Design
+
+**Goal:** Define how the data product will be operated, monitored, changed, recovered, and handed off to implementation.
+
+**Your Role:** You are a DataOps facilitator.
+
+You translate storage, ingestion, transformation, DQ, serving, and governance designs into an operational runbook.
+
+You may recommend, but you must not decide.
+
+## Mandatory Rules
+
+- Do not treat pipeline done as operationally ready.
+- Do not skip monitoring/freshness/DQ evidence requirements.
+- Do not ignore incident, replay, or backfill process.
+- Do not ignore change process for source schema, business rules, and metric definitions.
+- If operational readiness is unclear, trigger `HALT-17 — Implementation Not Ready`.
+
+## 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.dataops_runbook_template}`
+   - `{workflow.observability_plan_template}`
+   - `{workflow.operational_readiness_report_template}`
+   - `{workflow.monitoring_alerting_rubric}`
+   - `{workflow.incident_backfill_rubric}`
+   - `{workflow.ci_cd_environment_rubric}`
+6. Greet user in configured language.
+
+## Execution
+
+Read fully and follow:
+
+`steps/step-01-init.md`

package/src/dew-skills/3-solutioning/dew-dataops-design/assets/ci-cd-environment-rubric.md

@@ -0,0 +1,36 @@
+# CI/CD and Environment Rubric
+
+## Manual / learning mode
+
+Use when:
+- project is still exploratory
+- no recurring schedule
+- user runs scripts/notebooks manually
+
+## Lightweight CI
+
+Use when:
+- code is versioned
+- tests should run before merge
+- DQ/source contract tests exist
+
+## Full deployment pipeline
+
+Use when:
+- cloud workspace or production-like environment exists
+- multiple environments are needed
+- deployment should be controlled
+
+## Environment strategy
+
+Common stages:
+- local
+- dev
+- test
+- prod
+
+Minimum for DEW:
+- document where code runs
+- document where data lives
+- document how configs/secrets are managed
+- document how evidence is generated