docs(roadmap): add outbox pattern idea for ordered message delivery
Add a new roadmap item describing the Outbox Pattern as a mechanism to guarantee message delivery order and consistency. The pattern would enable a human-review queue for agent-generated work (e.g. emails, SMS) before it is dispatched externally.
This commit is contained in:
parent
0f994ede65
commit
ed3435f0ba
1 changed files with 6 additions and 0 deletions
|
|
@ -247,6 +247,12 @@ flowchart LR
|
||||||
|
|
||||||
## Ideas and improvements
|
## Ideas and improvements
|
||||||
|
|
||||||
|
- [ ] Outbox Pattern
|
||||||
|
- [ ] The outbox pattern is a way to ensure that messages are delivered to the user in the correct order
|
||||||
|
- [ ] consistency, order, etc.
|
||||||
|
- [ ] With this we can push all completed agent work to a "review" queue for human review and approval before being sent off
|
||||||
|
- [ ] Example:
|
||||||
|
- [ ] emails, sms, any work where we want to ensure consistency, order, etc.
|
||||||
- [ ] Add performance metrics to the eval harness
|
- [ ] Add performance metrics to the eval harness
|
||||||
- [ ] Raw metrics of tool calls, LLM calls, token counts, duration, etc
|
- [ ] Raw metrics of tool calls, LLM calls, token counts, duration, etc
|
||||||
- [ ] Per-test scores
|
- [ ] Per-test scores
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue