Hey everyone,

Wanted to give a little peak into what one of my loop orchestors looks like as a 20+ year senior engineer & designer, so people could see a real working example.   
  
My orchestrator Lloyd's primary goal is managing it's own internal tickets table. In my example thats just a simple SQLite table. An orchestrator can do anything, so giving it a database to manage its own memory has compounding value. Lloyd has managed over 600 tickets for me that it can query (like it's own internal jira, that I can click through). This means every time I have a new ticket, it can look up previous related tickets. Just like any of us should when assigned new work.

It gives the agent a database of tribal knowledge that can be passed to any model.

https://preview.redd.it/0nyyd00bl7jh1.png?width=1940&format=png&auto=webp&s=f383811da3c23f3bc0645672291bcfa05e6de1ac

The main concept I want to point out is the heart beat, and the pulse action items. 

You can see exactly where the value comes:

\- first it runs a playbook (automation script) to check my email for any new bug reports from customers, checks for previous context before staffing a ticket  
\- checks if any docs need to be updated on the website  
\- check's the own app's running logs to just see whats up  
\-- this is such an important practice, it will surface bugs you didn't know existed because nobody reported them, and the logs didn't produce and error, but maybe a noisy problem.  
\- adding it's own tickets for bugs and enhancements along the way, gives the agent a voice to surface ideas and problems for \_me\_ to triage as well.

What do your loops look like?

Example of a real working loop orchestrator