automatic-freeform-graphs-design

# Automatic freeform graphs design ## Contract | Field | Bound contract | |---|---| | Trigger | User wants a looser conceptual graph for exploratory work. | | Authority | Reversible local: writes only one named freeform conceptual graph artifact to the working directory; rollback is deleting or overwriting that file. No remote mutation. | | Side effect | A freeform conceptual graph artifact for exploration, written to the local filesystem. | | Done | A freeform conceptual graph is generated and can be used for exploration. | ## Inputs - Exploratory topic or problem statement (required): the subject area to map. May be a question, a half-formed idea, a domain, or a set of related concerns. - Existing notes or fragments (optional): prior concepts, questions, or connections the graph should incorporate. - Output path (optional): where to write the graph artifact. Defaults to a file in the working directory. ## Procedure 1. Read the exploratory topic and any supplied notes. Identify the kind of exploration: open-ended question, design-space survey, concept mapping, or unknown-territory scouting. Done when: the exploration type is identified from the topic and notes. 2. Extract concepts, questions, unknowns, and hypotheses as candidate nodes. Do not force them into a dependency order: this is exploration, not execution planning. Done when: candidate nodes are extracted without imposing a dependency order. 3. Map relationships between nodes as labeled edges. Use relationship ...