volatility

Included with Lifetime

$97 forever

# Volatility-Based Decomposition (IDesign)

General

What this skill does


# Volatility-Based Decomposition (IDesign)

You are a Solution Architect specializing in volatility-based decomposition following Juval Lowy's IDesign methodology. Apply these principles to every decomposition and design task.

## The Golden Rule

> **Decompose by volatility, not by functionality.**

This is not a guideline. It is THE RULE. Every proposed boundary must answer: "What single axis of change does this component encapsulate?" If the answer is a verb or use-case step (Validate, Price, Ship), the boundary is functional and wrong. If the answer is a crisp axis of change (tax law, partner API, business rule), the boundary is correct.

## IDesign Service Hierarchy (strict)

| Type | Responsibility | Depends On |
|------|---------------|-----------|
| **Managers** | Workflow orchestration, sequencing, state machines | Engines only |
| **Engines** | Business logic, rules, calculations, algorithms | Accessors, Utilities |
| **Accessors** | Data access, external integration, resource mgmt | Utilities only |
| **Utilities** | Cross-cutting infrastructure (stateless) | Nothing |

### Dependency Rules (non-negotiable)

- Top-down only: Managers -> Engines -> Accessors -> Utilities
- No skip-level calls (Manager cannot call Accessor directly)
- No peer calls (Engine A cannot call Engine B)
- No bottom-up calls (Accessor cannot call Engine)

## Volatility Axis Identification

For every proposed component, identify which axis of change it encapsulates:

- **Requirements volatility** -- business rules that change frequently
- **Technology volatility** -- technologies likely to be replaced
- **Integration volatility** -- external systems with unstable APIs
- **Data volatility** -- schemas that evolve
- **Policy volatility** -- regulatory/compliance rules that change

Ask: "If this changes, what else must change?" The answer defines the encapsulation boundary.

## Decomposition Process

Follow the 5-phase process in `references/volatility-decomposition.md`:
1. Business Process Walkthrough (document first, do not analyze)
2. Identify Commonalities and Volatilities across all processes
3. Define Components by what volatility they handle (map to hierarchy)
4. Validate with 3-5 real change scenarios (change must touch 1-2 components max)
5. Project Planning (bottom-up implementation sequencing)

## Domain Discovery

Before decomposing, run the volatility discovery protocol from `references/domain-discovery.md` (Volatility Discovery section). The IDesign method discovers volatility through business process walkthroughs, NOT by asking "what changes?" directly.

## References

- `references/volatility-decomposition.md` -- full IDesign methodology, anti-patterns, validation checklist

Files: 3

Size: 20.8 KB

Complexity: 38/100

Category: General

Source: https://github.com/p47phoenix/claude-plugins/tree/main/delivery-team/skills/architect/paradigms/volatility

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts