Skip to content

Execution patterns ​

简体中文 / Detailed index · All examples

These 16 patterns combine Agent capabilities and control flow. Each directory documents its workflow, composition and design requirements.

Complete scenario contract ​

Use RAG question answering as the application and verification reference. Execution patterns connect a trusted user request to actual deliverables, documenting stage inputs/outputs, authority, stopping conditions and failures. A model call or an isolated node is not a complete scenario.

Provide a runnable CLI and programmatic entry, real source/system integration, attributable user results, durable state and recovery. Context uses Redis; Memory uses a database; business/vendor adapters remain separately configured application tools. Compose Workers through public package exports and Runtime / Graph / Loop, without source-tree imports.

Verify normal business outcomes, missing information, faults, cancellation, process interruption and cache expiry against actual artifacts/effects. Report real model/storage experiments separately from explicit unit doubles. README and API documentation include complete calls and scope limits.

Web search question answering

Ditto · @codesoul-co/ditto · Node.js 24+