retrievelisted

## Intent Execute **retrieve** to fetch specific, known information from specified sources. Unlike `search` (which explores under uncertainty), retrieve fetches identified items with full provenance tracking. **Success criteria:** - Requested data is fetched completely - Source and timestamp are recorded - Data integrity is verified where possible - Citations enable re-retrieval - Missing data is explicitly flagged **World Modeling Context:** Retrieve feeds into all world modeling layers by providing grounded observations for `world-state`, timestamps for `temporal-reasoning`, and evidence for `grounding`. **Compatible schemas:** - `schemas/output_schema.yaml` ## Inputs | Parameter | Required | Type | Description | |-----------|----------|------|-------------| | `target` | Yes | string\|object | What to retrieve (path, URL, query, or identifier) | | `source` | No | string | Where to retrieve from (file, api, database); default: infer | | `format` | No | string | Expected format (json, text, binary); default: auto-detect | | `constraints` | No | object | Filters, projections, version specifications | ## Procedure 1) **Identify target**: Determine exactly what to fetch - File path: Exact file location - URL: Web resource address - API endpoint: Service + parameters - Record: Database/system identifier 2) **Verify source accessibility**: Confirm retrieval is possible - Check permissions - Verify network access if remote - Confirm source exists 3) *