Identify module boundaries that separate sequence and activity volatility.
npx skills add https://github.com/juspay/ci --skill lowy-juspay
Please help me install this Agent Skill. Skill: lowy Source: https://github.com/juspay/ci/tree/main/.claude/skills/lowy Command: npx skills add https://github.com/juspay/ci --skill lowy-juspay
Juval Lowy's volatility-based decomposition provides a principled way to evaluate architecture by asking whether module boundaries encase axes of change rather than simply group related functionality.
Reframe current module boundaries around volatility axes and map likely changes to stable interfaces.
High-intent search queries and answers about installing and using this skill.
Volatility-based decomposition separates sequence volatility (workflow orchestration order) from activity volatility (how each step is performed) across modules. This approach establishes stable interfaces and assesses blast radius for change scenarios to isolate axes of change during architecture reviews.
Apply volatility-based decomposition during architecture reviews when systems undergo change, scaling, or domain evolution. It separates sequence volatility from activity volatility across modules, establishing stable interfaces to encase axes of change and minimize the blast radius of modifications.
Sequence volatility refers to the order of steps in workflow orchestration, while activity volatility concerns how each individual step is performed. Volatility-based decomposition separates these independent axes of change into different modules to establish stable interfaces and reduce blast radius.
Assess blast radius by mapping likely change scenarios to volatility-driven module boundaries and stable interfaces. Encapsulating volatile aspects behind orchestrators and engines isolates the impact of modifications and prevents changes in one axis from cascading across unrelated services.
Yes, volatility-based decomposition supports architecture reviews and boundary decisions across systems undergoing domain evolution. Aligning naming with volatility-driven boundaries and separating sequence from activity volatility establishes stable interfaces that encase axes of change effectively.
sridIdentifies axes of change in modules using volatility-based decomposition.
YukiIto1999Acquire Linux memory with LiME and analyze it using Volatility 3.
bettercallzaalMap code change dependencies and downstream effects to assess blast radius.
RamonsDkaIdentify business domains and group code components into domain-based groupings.
