obstacle-resolution

# Obstacle Resolution ## Purpose When Genesis encounters a blocker — a failed API call, an unavailable service, a missing capability — systematically resolve it using the fallback chain framework. ## When to Use - A routing chain is exhausted (all providers failed). - A required service is unreachable. - A task cannot proceed due to a missing dependency or capability. - Automatic retries have been exhausted. ## Workflow 1. **Classify the obstacle** — What type? (provider failure, data missing, capability gap, external dependency, permission issue) 2. **Check fallback chain** — Load the relevant fallback chain from `fallback_chains.py`. Walk the chain in order. 3. **Attempt each fallback** — Try each alternative. Log attempts and results. 4. **Escalate if needed** — If all fallbacks exhausted: - For non-urgent: queue for user review, continue with degraded capability. - For urgent: alert user immediately via outreach. 5. **Record resolution** — Store the successful resolution path as an observation. If a new fallback was discovered, propose a procedure update. ## Output Format ```yaml obstacle: <one-line description> date: <YYYY-MM-DD> type: provider_failure | data_missing | capability_gap | external_dep | permission chain_attempted: - step: <fallback step> result: success | failure detail: <what happened> resolution: resolved | degraded | escalated resolution_detail: <how it was resolved> ``` ## Examples ### Example: Embedding provider chain...