discoverlisted

## Intent Explore data or systems to find patterns, relationships, or anomalies that were not explicitly requested or expected. Discovery is open-ended exploration that surfaces novel insights rather than confirming hypotheses. **Success criteria:** - At least one non-obvious finding surfaced - Significance level assigned to each discovery - Novelty classified (known, suspected, surprising) - Methodology documented for reproducibility **Compatible schemas:** - `schemas/output_schema.yaml` ## Inputs | Parameter | Required | Type | Description | |-----------|----------|------|-------------| | `search_space` | Yes | string\|object | Where to look (files, data, systems, domains) | | `discovery_type` | No | string | What kind of discovery: relationship, pattern, anomaly, gap, opportunity | | `constraints` | No | object | Bounds on exploration (time, scope, depth) | | `seed_observations` | No | array | Initial observations that may hint at discoveries | ## Procedure 1) **Define search space boundaries**: Establish what is in and out of scope - File patterns, directories, or data sources - Conceptual boundaries (domain, time range) - Depth limits (how many hops of relationships) 2) **Apply discovery heuristics**: Use exploration strategies systematically - **Pattern mining**: Look for recurring structures, naming conventions, code patterns - **Relationship mapping**: Find connections between entities (imports, calls, references) - **Anomaly detection**: Ide