product-domain-engine
Product Domain Engine
The meta-system. Every product tied to a domain is an instance of the same operation: formalize informal knowledge into computable structure, then express that structure through four independent rhetorical channels.
This skill does not invent new patterns. It names a system that was already running across four products (public-record-data-scrapper, styx, sovereign-systems--elevate-align, hokage-chess) and was being re-derived every time. Naming it converts re-derivation into composition.
What This Is
A conductor, not a monolith. The PDE sequences seven existing skills through a five-phase protocol, adds the rhetorical-mode framework that none of them carries, and provides the composition matrix that selects which output blends which mode.
You invoke this skill when the work to be done is building a new product tied to a domain — chess improvement, public records, behavioral economics, wellness, anything where lived knowledge needs to become computable structure.
The Five-Phase Formalization Protocol
Every domain receives the same treatment. Phases are sequential within a single pass and recursive across product lifecycle.
Phase 1 — IDENTIFY: the domain's agents
Who acts in this space? Their roles, incentives, constraints. The agent census is the first ontological move; it forces the domain to reveal itself as a graph of actors rather than a topic.