atomize-concept
Purpose
Split a broad concept into definitional facets and distinguishable subconstructs.
Input contract
yamlrequired: [concept_definition, domain_context] optional: [theory, neighboring_concepts, examples] constraints: [facets must be non-duplicate and retain the parent concept boundary]
Procedure
- Extract the concept's necessary, typical, and optional properties.
- Separate facets by mechanism, function, level, or context.
- Compare neighboring concepts and mark overlaps or gaps.
- Emit a facet hierarchy with definitions and boundary examples.
If the atomic concepts are stable enough to connect semantically, consider type-relation as the next tactic.
Output contract
yamlproduces: [concept_facets, facet_definitions, overlap_map, boundary_examples] delta_fields: [findings, uncertainties, open_questions]
Quality gates
- Facets are distinguishable in principle.
- Parent and child scopes are explicit.
Failure and counterexamples
Do not treat synonyms as distinct facets or split a concept solely by examples.
Provenance map
resolved: atomize-concept


