domain-ideal-whole-substrate
Domain Ideal-Whole Substrate (DIWS)
The substrate beneath every flag-pierce. Where Product Domain Engine (PDE) handles the product layer (logos / ethos / pathos / kairos), this skill handles the domain layer beneath. Every domain — chess, fitness, voodoo, education, design — composes from the same eight strata under the same four operators, with load distribution shifting by domain.
User's foundational question: "What elements, systems, structures, environments, agents so forth make the ideal whole (be it fitness, chess, or voodoo)?"
DIWS answers it as substrate, not as workflow.
What This Is
A substrate, not a workflow. PDE is a 5-phase formalization protocol that consumes a domain and produces a product. DIWS is what the domain itself is before any product gets built on top of it. PDE pulls from DIWS substrate; DIWS does not pull from PDE.
DIWS does two things PDE cannot:
- Cross-portfolio reuse — Phase 0 audits
~/Workspace/for existing engines (3-tier taxonomy: domain / meta / consultant) before any new domain instantiates. Engine + skin pattern, not from-scratch every time. - Stretching rack — Phase 0.5 runs the gap-map operator across N concurrent DIWS instances simultaneously. Surfaces holes (under-developed dimensions) and fat (redundant scaffolding) at portfolio scale, not just per-domain.
You invoke this skill when a flag has been pierced or is about to be — a friend's domain, a research interest, a consulting engagement, a side practice. The goal is to load the substrate ahead of any product-building work so that PDE / synthesis / cross-pollination diagnoses operate over filled scaffolding rather than empty types.