observelisted

## Intent Observe and report the current state of a specified target without modifying it. This is the foundation for situational awareness and state modeling. **Success criteria:** - Current state accurately captured with timestamp - Relevant aspects of the target documented - At least one evidence anchor per observation - Uncertainty explicitly noted where state is ambiguous **Compatible schemas:** - `schemas/output_schema.yaml` ## Inputs | Parameter | Required | Type | Description | |-----------|----------|------|-------------| | `target` | Yes | string | What to observe (file path, URL, process, system) | | `aspects` | No | array[string] | Specific aspects to focus on (e.g., ["status", "errors", "metrics"]) | | `depth` | No | string | Observation depth: surface, detailed, exhaustive | ## Procedure 1) **Identify observation target**: Clarify exactly what system, process, or entity to observe - Validate target is accessible and observable - Determine appropriate observation method (read file, query API, check process) 2) **Select observation aspects**: Determine what properties/attributes to capture - If aspects not specified, observe: status, configuration, recent changes, anomalies - Prioritize aspects relevant to apparent context or goal 3) **Capture current state**: Execute observation without modifying target - Use Read for file-based targets - Use Bash for process/system state (ps, systemctl status, etc.) - Record timestamp of observation