domain-ideal-whole-substrate

Files (34)

• SKILL.md
• domain-agent-fleet-template.yaml · assets/
• domain-agent-fleet.yaml · assets/
• domain-attractor-template.md · assets/
• domain-attractor.md · assets/
• domain-constellation-template.yaml · assets/
• domain-constellation.yaml · assets/
• domain-contribution-charter-template.md · assets/
• domain-contribution-charter.md · assets/
• domain-gap-map-template.md · assets/
• domain-gap-map.md · assets/
• domain-lineage-template.md · assets/
• domain-lineage.md · assets/
• domain-meta-study-template.md · assets/
• domain-meta-study.md · assets/
• domain-ontology-template.md · assets/
• domain-ontology.md · assets/
• domain-production-stack-template.md · assets/
• domain-production-stack.md · assets/
• engine-overlap-board.md · assets/
• portfolio-resonance-template.md · assets/
• portfolio-reuse-map.md · assets/
• README.md · proof-instances/voodoo/
• domain-contribution-charter.md · proof-instances/voodoo/
• domain-meta-study.md · proof-instances/voodoo/
• domain-ontology.md · proof-instances/voodoo/
• 4-operators-spec.md · references/
• 8-strata-spec.md · references/
• diws-msp-mapping.md · references/
• engine-taxonomy.md · references/
• portfolio-composition-map.md · references/
• audit-portfolio.sh · scripts/
• audit.sh · scripts/
• portfolio-gap-audit.sh · scripts/

SKILL.md (first lines)

# 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:
1. **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.
2. **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.

## Invariants

These hold across every flag-pierce, regardless of domain:

1. **Phase 0 portfolio-audit runs BEFORE layer-1 ontology** — never scratch-build what an existing engine can re-skin (rule 41: audit before building)
2. **Phase 0.5 engine-overlap board comes between Phase 0 and layer-1** — visualize candidate engines + gaps before scaffolding (rule 36: seed not specification)
3. **All 8 strata instantiate** — even if a stratum is sparse for the domain (load shifts, layers don't disappear)
4. **All 4 operators fire on every instantiation** — selfish-altruistic + magnetic + portfolio + reflexive (Tenet Protocol — both directions simultaneously)
5. **Layer 4 (gap-map) and Layer 8 (contribution) close as a loop** — heist + contribute round-trip; never steal without giving back
6. **Layer 8 produces dissertation-grade research output** — academic capital is substrate, not garnish
7. **Reflexive Operator produces `domain-meta-study.md` alongside the 8 stratum artifacts** — every build co-arises with a study-of-build
8. **Capital flow is N-channel, not 1-channel** — monetary is one of many; meta-skill capital, audience cross-flow, tool extraction, work-improvement all count

## The 8 Strata

Every domain composes from these. See [`references/8-strata-spec.md`](references/8-strata-spec.md) for full per-stratum spec.

| # | Layer | Question | Output artifact |
|---|---|---|---|
| 1 | **Ontology** | What is the domain made of? | `domain-ontology.md` |
| 2 | **Lineage** | How did it become what it is? | `domain-lineage.md` (3 timeslices × 2 registers) |
| 3 | **Constellation** | Who is doing it well, where do we exist relative? | `domain-constellation.yaml` (75-person file) |
| 4 | **Gap-map** | Where is unexploited terrain? | `domain-gap-map.md` (gaps + heist targets) |
| 5 | **Agent fleet** | Who serves the work when you arrive? | `domain-agent-fleet.yaml` |
| 6 | **Production stack** | What does shipping require? | `domain-production-stack.md` |
| 7 | **Internal magnet** | What flows IN when the flag pierces? | `domain-attractor.md` |
| 8 | **External contribution** | What flows OUT to the community? | `domain-contribution-charter.md` |

Voodoo loads layer 8 heavily (ethical floor, anti-extraction guard). Chess and fitness share a similar load profile. Both shapes validate the schema — generative across radically dissimilar domains rather than overfit to one.

## The 4 Operators

See [`references/4-operators-spec.md`](references/4-operators-spec.md) for full spec. All four fire simultaneously on every flag-pierce.

### 1. Selfish-altruistic loop (single-engagement)

```
Learn-for-self → Quality-of-product → Service-to-friends →
Friends-elevated → Network-effect → Self-elevated → More-learning
```

The selfishness is a feature. It locks the user into being a real practitioner rather than a curator. Without the lock, the system curates dead.

### 2. Magnetic membrane (single-domain, two-way)

```
Flag pierces →
  INTERNAL: magnetize all applicable, transmute through user's lens, alchemize toward ideal
  EXTERNAL: contribute to community
```

Pull-in = refinery. Push-out = gift. Per Tenet Protocol — both directions simultaneously, never one without the other.

### 3. Portfolio Operator (cross-portfolio, two-way) — v2 + v2.1

**Push** (v2): every flag-pierce produces three cross-flows simultaneously:
- meta-skill extraction (writing / voice / community-building)
- domain-pair overlaps (each new domain creates N-1 publishable conversation surfaces)
- tool/audience cross-flow (engines amortize across portfolio nodes)

**Pull** (v2.1): every flag-pierce begins with portfolio-audit — scan `~/Workspace/` for engines / skills / primitives that match candidate-domain shape; only enter layers 1-8 after `portfolio-reuse-map.md` is filled.

### 4. Reflexive Operator (build + study, parallel) — v2.2

Every domain instantiation produces `domain-meta-study.md` alongside the 8 stratum artifacts. Where the other three operators govern *flow*, this one governs *recursion* — the thing and the thing-studied co-arise. Per Tenet Protocol, every build-action triggers its opposing reflection-action simultaneously.

## The Use Protocol

Sequential within a single instantiation; recursive across portfolio lifecycle.

### Phase 0 — Portfolio audit (PULL)

Run [`scripts/audit-portfolio.sh`](scripts/audit-portfolio.sh). Globs `~/Workspace/` for existing engines and classifies them into the 3-tier engine taxonomy (see [`references/engine-taxonomy.md`](references/engine-taxonomy.md)):

- **Domain engines** — re-skinnable within similar domain (a membership 4-level funnel, a visual-flow renderer, a landing-page engine)
- **Meta-engines** — cross-domain pattern (cross-pollination diagnosis, 75-person Constellation, PDE skill, Bridge Content templates, Discord rituals)
- **Consultant engines** — every engagement regardless of domain (knowledge base, application pipeline, plan-mode discipline, IRF/MEMORY/chezmoi protocols, conversation-corpus pipeline)

Output: `portfolio-reuse-map.md` showing which engines re-skin, which need invention, which are skin-only domain-specific work.

### Phase 0.5 — Engine overlap board (THE STRETCHING RACK)

Run [`scripts/portfolio-gap-audit.sh`](scripts/portfolio-gap-audit.sh). Operates across N concurrent DIWS instances simultaneously to surface holes and fat at portfolio scale.

For each axis (the 8 strata + 4 operators), the script reports:
- **Holes** — under-developed in 1+ instances; transplantable from a sibling instance
- **Fat** — over-engineered in 1+ instances; consolidatable into a shared engine
- **N-way overlap** — concept present in ≥2 instances; promotion candidate to meta-engine

Output: `holes-fat-report.md`. Refines portfolio reuse from listing engines to *seeing* them in spatial relation, identifying white-space across the whole portfolio.

### Phase 1-8 — Stratum instantiation

Walk each stratum in order, filling its template from [`assets/`](assets/) into the domain's instantiation directory. Use [`references/8-strata-spec.md`](references/8-strata-spec.md) for canonical questions.

Order is canonical but not strictly serial — strata 1-3 can be parallelized; 4 depends on 3; 5-8 are largely independent once 1-4 are in place.

### Phase 9 — Operators fire (REFLEXIVE)

After stratum artifacts ship:
- Selfish-altruistic loop: confirm the user is in practitioner-mode, not curator-mode (gate)

From 4444J99/a-i--skills, MIT.

More from 4444J99/a-i--skills