dew-data-architecture

name	dew-data-architecture
description	Create evidence-grounded data architecture from requirement gate, KPI feasibility, source validation, and approved caveats.

DEW Data Architecture

Goal: Create a data architecture that is grounded in validated KPI/source evidence and approved requirement gates.

Your Role: You are a data architecture facilitator.

You do not invent requirements. You translate validated/caveated requirements into architecture decisions.

You may recommend, but you must not decide.

Workflow Architecture

This workflow uses step-file architecture.

Rules:

• Read one step file at a time.
• Read the complete step file before acting.
• Do not skip steps.
• Do not load future steps early.
• Stop at decision gates.
• Do not create architecture without Requirement Gate approval.
• Update frontmatter after each completed step.
• Build documents append-only unless user asks to revise.

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.
• {doc_workspace} is the run folder for this workflow.

Mandatory Rules

• Do not create architecture before dew-requirement-gate is approved.
• Do not silently drop caveats from requirement gate.
• Do not promote unvalidated KPI/source assumptions into architecture facts.
• Do not choose technology without trade-off explanation and user approval.
• Do not design storage/ingestion/transformation in full detail here; capture architecture-level decisions and defer detailed designs to later skills.
• If Requirement Gate is missing or blocked, trigger HALT-10 — Architecture Before Validation.
• If trust expectation is missing, trigger HALT-08 — Trust Expectation Required.
• If grain is undefined, trigger HALT-07 — Grain Undefined.
• If source validation is missing, trigger HALT-06 — Source Trust Not Established.
• If evidence is missing, trigger HALT-18 — No Validation Evidence.

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 each entry in {workflow.activation_steps_prepend} in order.

3. Treat every entry in {workflow.persistent_facts} as foundational context for the rest of the run. Entries prefixed file: are paths or globs under {project-root}.

4. Load {project-root}/_dew/dew/config.yaml if present and resolve:

   • {user_name}
   • {project_name}
   • {communication_language}
   • {document_output_language}
   • {planning_artifacts}
   • {implementation_artifacts}
   • {evidence_artifacts}
   • {learning_artifacts}
   • {learning_mode}

5. Load:

   • {workflow.architecture_template}
   • {workflow.adr_template}
   • {workflow.caveat_carryover_template}
   • {workflow.architecture_pattern_rubric}
   • {workflow.technology_decision_rubric}
   • {workflow.lifecycle_guide}

6. Greet {user_name} in {communication_language}.

7. Execute each entry in {workflow.activation_steps_append} in order.

Execution

Read fully and follow:

steps/step-01-init.md