decompose-components
Purpose
Decompose a system into components and functions, preserving dependencies relevant to transformation.
Input contract
yamlrequired: [system_or_design, decomposition_purpose] optional: [component_inventory, dependency_evidence] constraints: [components must have a function or interface and a parent relation]
Procedure
- Enumerate observable components and their functions.
- Split compound components until each unit has a distinct transformation boundary.
- Link dependencies, interfaces, and affected outcomes.
Output contract
yamlproduces: [component_tree, function_map, dependency_map] delta_fields: [findings, assumption_updates, decisions]
Quality gates
- Decomposition is complete for the declared boundary; no dependency is implied only by proximity.
Failure and counterexamples
Mark a component unresolved when its function or dependency cannot be evidenced; do not invent subcomponents.
Provenance map
creative-ideation/component-decomposition: resolved.stress-test/function-analysis: resolved.


