Hermes Pipeline
57 lines
2.4 KiB
Markdown
57 lines
2.4 KiB
Markdown
---
|
|
name: conditional-review-workflow
|
|
version: 1.0.0
|
|
description: Process a user request through branching logic to approve or reject it,
|
|
producing a routed decision result
|
|
inputs:
|
|
- 'request: string - The user''s request or input collected at runtime via the input
|
|
agent'
|
|
steps:
|
|
- 'Start: Input agent collects the user request and stores it in the ''request'' state
|
|
field, then routes to Classify node'
|
|
- 'Classify: Branching agent evaluates the ''request'' field and routes to Approve
|
|
node on success or Reject node on failure (on_failure)'
|
|
- 'Approve: Default agent formats an approval message using the request and stores
|
|
it in the ''result'' output field'
|
|
- 'Reject: Default agent formats a rejection message using the request and stores
|
|
it in the ''result'' output field'
|
|
outputs:
|
|
- 'result: string - Final message indicating whether the request was approved or rejected,
|
|
containing the original request'
|
|
tags: []
|
|
metadata:
|
|
source_repo: https://github.com/jwwelbor/AgentMap.git
|
|
extracted_at: ''
|
|
confidence: 0.85
|
|
---
|
|
|
|
# conditional-review-workflow
|
|
|
|
Process a user request through branching logic to approve or reject it, producing a routed decision result
|
|
|
|
## Steps
|
|
|
|
1. Start: Input agent collects the user request and stores it in the 'request' state field, then routes to Classify node
|
|
2. Classify: Branching agent evaluates the 'request' field and routes to Approve node on success or Reject node on failure (on_failure)
|
|
3. Approve: Default agent formats an approval message using the request and stores it in the 'result' output field
|
|
4. Reject: Default agent formats a rejection message using the request and stores it in the 'result' output field
|
|
|
|
## Inputs
|
|
|
|
- request: string - The user's request or input collected at runtime via the input agent
|
|
|
|
## Outputs
|
|
|
|
- result: string - Final message indicating whether the request was approved or rejected, containing the original request
|
|
|
|
## Failure Modes
|
|
|
|
- Input collection failure - user provides no or invalid input (no explicit on_failure defined for Start node in example)
|
|
- Branching classification failure - if branching agent cannot evaluate, it routes to Reject via on_failure configuration
|
|
- LLM provider unavailability - if branching or agents rely on LLM backends that are misconfigured or offline
|
|
|
|
## Source
|
|
|
|
Extracted from: [https://github.com/jwwelbor/AgentMap.git](https://github.com/jwwelbor/AgentMap.git)
|
|
Confidence: 0.85
|