context-lookup

Context lookup retrieves CFN Loop context stored in Redis with optional in-memory caching to accelerate repeated reads. Initialize ContextLookup with a Redis client, logger, and cache flag enabled, then call lookupContext with task ID and iteration number to fetch and cache the result.

Yes, context lookup includes built-in validation to ensure retrieved context meets structural correctness requirements. This prevents downstream processing errors by catching malformed or incomplete context early in the orchestration pipeline.

Context lookup supports both single and batch lookups, allowing you to retrieve context for multiple tasks and iterations in one operation. Batch mode is efficient for agent ecosystems coordinating multiple Loop implementations simultaneously.

Enable caching when your workflow repeatedly accesses the same task context within a session. Caching reduces Redis round trips and latency for consensus collection, gate checks, and Product Owner decision flows in container-based agent orchestration.

Yes, context lookup is designed for container-based CFN Loop execution, agent spawning, and loop management across Docker environments. It provides Redis-backed state management and consensus collection for Loop 3 implementers and Loop 2 validators.

Context lookup includes error handling for retrieval failures. Failures during consensus collection block the GOAP-informed decision flow; implement retry logic or fallback handlers to manage transient Redis unavailability in your orchestration workflow.