dew-method 0.1.0

package/src/dew-skills/1-analysis/dew-evidence-check/assets/evidence-index-template.md

@@ -0,0 +1,53 @@
+---
+title: "Validation Evidence Index"
+status: active
+created: YYYY-MM-DD
+updated: YYYY-MM-DD
+workflow: dew
+---
+
+# Validation Evidence Index
+
+This file indexes all validation evidence produced by the DEW workflow.
+
+A phase cannot be marked complete unless required evidence is listed here.
+
+## Evidence Table
+
+| Evidence ID | Phase | Type | Description | Path | Status | Related Decision |
+|---|---|---|---|---|---|---|
+| EVD-0001 | | | | | missing/available/validated/stale/invalid | |
+
+## Evidence Types
+
+- api-call-log
+- source-sample
+- schema-snapshot
+- profiling-report
+- kpi-sample-query
+- kpi-sample-output
+- notebook
+- source-contract-test
+- data-quality-test
+- pipeline-test
+- review-report
+- user-decision
+- caveat-approval
+
+## Evidence Entry Template
+
+```markdown
+## EVD-{number} — {Evidence Name}
+
+Date:
+Phase:
+Type:
+Description:
+Path:
+Status:
+Produced by:
+Related source:
+Related KPI:
+Related decision:
+Validation summary:
+Caveats:

package/src/dew-skills/1-analysis/dew-evidence-check/assets/phase-done-evidence-checklist.md

@@ -0,0 +1,82 @@
+
+## `src/dew-skills/1-analysis/dew-evidence-check/assets/phase-done-evidence-checklist.md`
+
+```markdown
+# Phase Done Evidence Checklist
+
+A DEW phase is done only if all required conditions are met.
+
+## Universal done criteria
+
+- [ ] Main artifact exists.
+- [ ] Required decision gates are approved.
+- [ ] Required evidence exists.
+- [ ] Evidence is indexed.
+- [ ] Decision log is updated.
+- [ ] Learning log is updated.
+- [ ] Open assumptions are labeled.
+- [ ] Caveats are documented.
+- [ ] Next-phase readiness is stated.
+- [ ] No unresolved hard HALT remains.
+
+## Evidence by phase
+
+### Project Framing
+
+- [ ] Project scope approved.
+- [ ] Business decision identified.
+- [ ] Consumer identified.
+
+### KPI Discovery
+
+- [ ] KPI formula defined.
+- [ ] KPI grain defined.
+- [ ] Required fields listed.
+- [ ] Source dependency listed.
+- [ ] Feasibility status assigned.
+
+### KPI Feasibility
+
+- [ ] Required fields checked.
+- [ ] Sample computation exists or caveat approved.
+- [ ] Sample output exists or KPI deferred.
+- [ ] Feasibility status updated.
+
+### Source Validation
+
+- [ ] Access verified.
+- [ ] Sample extracted.
+- [ ] Schema snapshot captured.
+- [ ] Grain confirmed.
+- [ ] Freshness observed.
+- [ ] DQ/profiling notes exist.
+- [ ] Source priority approved.
+
+### Requirement Gate
+
+- [ ] Trust expectation approved.
+- [ ] Grain approved.
+- [ ] Freshness approved.
+- [ ] KPI/source caveats approved.
+- [ ] Architecture readiness approved.
+
+### Architecture
+
+- [ ] Validated context referenced.
+- [ ] Architecture decision recorded.
+- [ ] Technology trade-offs documented.
+- [ ] Revisit trigger documented.
+
+### Implementation
+
+- [ ] Story has evidence requirements.
+- [ ] Tests pass.
+- [ ] Validation evidence exists.
+- [ ] File list updated.
+- [ ] Story status updated.
+
+### Retrospective
+
+- [ ] Learning captured.
+- [ ] Reusable pattern extracted if applicable.
+- [ ] Open issues documented.

package/src/dew-skills/1-analysis/dew-evidence-check/checklist.md

@@ -0,0 +1,26 @@
+# Evidence Check Checklist
+
+Use this checklist before marking a DEW phase complete.
+
+## Required
+
+- [ ] Target phase is identified.
+- [ ] Target artifact is identified.
+- [ ] Required evidence is listed.
+- [ ] Existing evidence is inspected.
+- [ ] Evidence is classified as missing/available/validated/stale/invalid.
+- [ ] Validation evidence index is checked.
+- [ ] Decision log is checked.
+- [ ] Learning log is checked.
+- [ ] Missing evidence triggers HALT-18.
+- [ ] Caveated continuation requires user approval.
+- [ ] Final evidence report is produced.
+
+## Failure conditions
+
+Fail the evidence check if:
+- artifact exists but evidence does not
+- evidence is not indexed
+- evidence is stale or invalid
+- phase is marked done with unresolved hard HALT
+- caveated continuation was not explicitly approved by user

package/src/dew-skills/1-analysis/dew-evidence-check/customize.toml

@@ -0,0 +1,25 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for dew-evidence-check.
+
+[workflow]
+
+activation_steps_prepend = []
+activation_steps_append = []
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+  "file:{project-root}/**/.decision-log.md",
+  "file:{project-root}/**/.learning-log.md",
+  "file:{project-root}/**/validation-evidence-index.md",
+]
+
+on_complete = ""
+
+evidence_index_template = "assets/evidence-index-template.md"
+phase_done_checklist = "assets/phase-done-evidence-checklist.md"
+checklist = "checklist.md"
+
+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/1-analysis/dew-halt-resolver/SKILL.md

@@ -0,0 +1,108 @@
+---
+name: dew-halt-resolver
+description: Resolve a DEW HALT by explaining the blocker, options, evidence requirements, and resume conditions.
+---
+
+# DEW HALT Resolver
+
+**Goal:** Resolve a HALT safely without hiding missing evidence or making assumptions.
+
+**Your Role:** You are a quality gate facilitator.
+
+A HALT is not a failure. A HALT is a controlled stop for learning, evidence, and decision quality.
+
+## Conventions
+
+- Bare paths resolve from the skill root.
+- `{skill-root}` resolves to this skill's installed directory.
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- `{workflow.<name>}` resolves to fields in `customize.toml`'s `[workflow]` table.
+
+## Mandatory Rules
+
+- Do not bypass a HALT.
+- Do not continue unless resume conditions are met.
+- Do not downgrade a hard HALT to a soft HALT without user approval.
+- Do not claim evidence exists unless it is available and referenced.
+- Always record the resolution in `.decision-log.md`.
+
+## On Activation
+
+1. Resolve customization:
+
+   `python3 {project-root}/_dew/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+
+   If the script fails, read `{skill-root}/customize.toml` directly and use defaults.
+
+2. Execute `{workflow.activation_steps_prepend}`.
+
+3. Load persistent facts from `{workflow.persistent_facts}`.
+
+4. Load config from `{project-root}/_dew/dew/config.yaml` if present.
+
+5. Load:
+   - `{workflow.halt_catalog}`
+   - `{workflow.halt_template}`
+   - `{workflow.halt_resolution_template}`
+
+6. Greet user in configured language.
+
+## Execution
+
+### Step 1 — Identify HALT
+
+Find:
+- HALT ID
+- HALT type
+- trigger
+- phase
+- artifact affected
+
+### Step 2 — Explain risk
+
+Explain:
+- why this HALT matters
+- what can go wrong if ignored
+- which lifecycle stages are affected
+
+### Step 3 — Show current state
+
+List:
+- known facts
+- unknowns
+- assumptions
+- missing evidence
+- related artifacts
+
+### Step 4 — Present options
+
+Present options:
+A. Resolve now
+B. Continue with caveat
+C. Reduce scope
+D. Return to previous phase
+
+### Step 5 — Recommend
+
+Recommend one option with reasoning.
+
+### Step 6 — Ask user
+
+Ask the user to choose A/B/C/D.
+
+Stop here.
+
+### Step 7 — Apply resolution
+
+After user decision:
+- update `.decision-log.md`
+- update `.learning-log.md`
+- update current artifact frontmatter
+- update evidence index if applicable
+- state resume condition
+
+### Step 8 — Resume or remain blocked
+
+If resume condition is satisfied, say what step can continue.
+
+If not satisfied, keep status as blocked and explain what is still missing.

package/src/dew-skills/1-analysis/dew-halt-resolver/assets/halt-catalog.md

@@ -0,0 +1,322 @@
+# DEW HALT Catalog
+
+## HALT-00 — Project Scope Missing
+
+Triggered when the project scope is not clear enough to start the workflow.
+
+Type: Hard Halt
+
+Resume when:
+- scope is defined
+- MVP boundary is clear
+- user approves scope
+
+---
+
+## HALT-01 — Business Decision Unclear
+
+Triggered when the workflow cannot identify what decision the data product supports.
+
+Type: Hard Halt
+
+Resume when:
+- target decision is defined
+- consumer is identified
+- business question is clear
+
+---
+
+## HALT-02 — KPI Definition Unverified
+
+Triggered when a KPI is proposed but lacks formula, grain, dimensions, or required fields.
+
+Type: Hard Halt
+
+Resume when:
+- KPI formula is defined
+- grain is defined
+- required fields are listed
+- user approves definition
+
+---
+
+## HALT-03 — KPI Feasibility Not Proven
+
+Triggered when primary KPI feasibility has not been tested with real source/sample data.
+
+Type: Hard Halt
+
+Resume when:
+- sample computation exists
+- or KPI is explicitly deferred/caveated by user decision
+
+---
+
+## HALT-04 — Source Not Identified
+
+Triggered when the workflow needs source systems but none are identified.
+
+Type: Hard Halt
+
+Resume when:
+- candidate sources are listed
+- source owner/access method is recorded
+
+---
+
+## HALT-05 — Source Access Not Verified
+
+Triggered when a source is listed but access has not been tested.
+
+Type: Hard Halt
+
+Resume when:
+- API call/download/query succeeds
+- or access limitation is documented and approved
+
+---
+
+## HALT-06 — Source Trust Not Established
+
+Triggered when a source is being promoted to P1 without enough evidence.
+
+Type: Hard Halt
+
+Resume when:
+- source sample exists
+- schema snapshot exists
+- profiling or quality notes exist
+- user approves source trust level
+
+---
+
+## HALT-07 — Grain Undefined
+
+Triggered when the workflow cannot define what one row represents.
+
+Type: Hard Halt
+
+Resume when:
+- source grain is defined
+- target KPI/product grain is defined
+- bridging/mapping need is documented
+
+---
+
+## HALT-08 — Trust Expectation Required
+
+Triggered when product trust level is not defined.
+
+Type: Soft Halt
+
+Resume when user chooses:
+A. Exploratory only
+B. Internal decision-support with documented limitations
+C. Trusted shared product with quality checks
+D. Production-grade with contracts and monitoring
+
+---
+
+## HALT-09 — Freshness Unverified
+
+Triggered when source/product freshness is assumed but not verified.
+
+Type: Hard Halt
+
+Resume when:
+- observed source freshness is documented
+- required freshness is approved
+- caveat is recorded if mismatch exists
+
+---
+
+## HALT-10 — Architecture Before Validation
+
+Triggered when the workflow attempts to create final architecture before KPI/source validation is complete.
+
+Type: Readiness Halt
+
+Resume when:
+- KPI feasibility report exists
+- source validation report exists
+- requirement gate is approved
+
+---
+
+## HALT-11 — Storage Layer Unclear
+
+Triggered when storage zones/layers are not defined.
+
+Type: Hard Halt
+
+Resume when:
+- raw/bronze/silver/gold or equivalent layers are defined
+- metadata expectations are approved
+
+---
+
+## HALT-12 — Ingestion Pattern Unclear
+
+Triggered when source access pattern is known but ingestion pattern is not chosen.
+
+Type: Hard Halt
+
+Resume when:
+- ingestion mode is chosen
+- batch/streaming decision is made
+- failure handling is defined
+
+---
+
+## HALT-13 — Schema Evolution Undefined
+
+Triggered when source schema may change but handling policy is missing.
+
+Type: Hard Halt
+
+Resume when user chooses:
+A. Strict schema contract
+B. Schema snapshot + drift detection
+C. Flexible rescued fields
+D. Manual review on change
+
+---
+
+## HALT-14 — DQ Rules Missing
+
+Triggered when transformation/serving is planned without data quality rules.
+
+Type: Hard Halt
+
+Resume when:
+- minimum DQ rule set is defined
+- blocking/warning behavior is approved
+
+---
+
+## HALT-15 — Serving Consumer Unclear
+
+Triggered when the serving layer is designed without a known consumer.
+
+Type: Hard Halt
+
+Resume when:
+- consumer is defined
+- serving mode is selected
+- success criteria are known
+
+---
+
+## HALT-16 — Security Privacy Unreviewed
+
+Triggered when data may include sensitive, personal, regulated, or access-controlled data but privacy/security posture is missing.
+
+Type: Safety Halt
+
+Resume when:
+- privacy classification is complete
+- access control approach is approved
+- sensitive data handling is documented
+
+---
+
+## HALT-17 — Implementation Not Ready
+
+Triggered when stories are requested before core artifacts are validated.
+
+Type: Readiness Halt
+
+Resume when:
+- PRD exists
+- KPI feasibility exists
+- source validation exists
+- architecture is approved
+- storage/ingestion/transformation designs are sufficiently complete
+
+---
+
+## HALT-18 — No Validation Evidence
+
+Triggered when a phase is marked done without evidence.
+
+Type: Hard Halt
+
+Resume when:
+- required evidence is produced
+- or user explicitly approves caveated continuation
+
+---
+
+## HALT-19 — Learning Capture Missing
+
+Triggered when an epic/project is being closed without learning notes.
+
+Type: Soft Halt
+
+Resume when:
+- `.learning-log.md` is updated
+- reusable pattern is extracted if applicable
+- unresolved lessons are recorded
+
+---
+
+## HALT-20 — Release Not Ready
+
+Triggered when E2E validation fails or critical release readiness items are missing.
+
+Type: Hard Halt
+
+Resume when:
+- E2E validation passes
+- critical evidence gaps are filled
+- user approves release with caveats
+
+---
+
+## HALT-21 — Documentation Incomplete
+
+Triggered when required documentation (user-facing or technical) is missing before final closure.
+
+Type: Soft Halt
+
+Resume when:
+- README, Data Dictionary, or Runbook is completed
+- or user accepts documentation gaps
+
+---
+
+## HALT-22 — Skill Pack QA Failed
+
+Triggered when the DEW skill pack itself fails structural or logical consistency checks.
+
+Type: Hard Halt
+
+Resume when:
+- missing files are created
+- broken links are fixed
+- inconsistencies are resolved
+
+---
+
+## HALT-23 — Package Release Not Ready
+
+Triggered when packaging scope, version, or release notes are missing.
+
+Type: Hard Halt
+
+Resume when:
+- version is selected
+- release notes are drafted
+- user approves package release
+
+---
+
+## HALT-24 — Installation Documentation Incomplete
+
+Triggered when onboarding guides, command references, or troubleshooting steps are missing.
+
+Type: Soft Halt
+
+Resume when:
+- installation guide is completed
+- verification steps are included

package/src/dew-skills/1-analysis/dew-halt-resolver/assets/halt-resolution-template.md

@@ -0,0 +1,43 @@
+# HALT Resolution: {HALT ID} — {HALT Name}
+
+## Resolution status
+
+pending / resolved / resolved-with-caveat / deferred / blocked
+
+## User choice
+
+A / B / C / D
+
+## Decision
+
+...
+
+## Evidence produced
+
+- ...
+
+## Caveats approved
+
+- ...
+
+## Downstream impact
+
+- Source:
+- Storage:
+- Ingestion:
+- Transformation:
+- Serving:
+- Governance/DataOps:
+
+## Resume condition
+
+The workflow may resume when:
+- ...
+
+## Decision log entry
+
+Record this resolution in `.decision-log.md`.
+
+## Learning log entry
+
+Record the learning note in `.learning-log.md`.