updates to readme, docs, guides

todo.md

@@ -1,36 +1,43 @@
 # todo list
-[x] multi-goal <br />
-    [x] set goal to list agents when done <br />
-    [x] make this better/smoother <br />
-
 [ ] clean up workflow/make functions
 
 [ ] make the debugging confirms optional <br />
-[ ] grok integration <br />
-[ ] document *why* temporal for ai agents - scalability, durability in the readme <br />
+ <br />
+[ ] document *why* temporal for ai agents - scalability, durability, visibility in the readme <br />
 [ ] fix readme: move setup to its own page, demo to its own page, add the why /|\ section <br />
 [ ] add architecture to readme <br />
+- elements of app <br />
+- dive into llm interaction <br />
+- workflow breakdown - interactive loop <br />
+- why temporal <br />
+
+[ ] setup readme, why readme, architecture readme, what this is in main readme with temporal value props and pictures <br />
+[ ] how to add more scenarios, tools <br />
+ <br />
+ <br />
 [ ] create tests<br />
 
 [ ] create people management scenario <br />
-  -- check pay status
-  -- book work travel
-  -- check PTO levels
-  -- check insurance coverages
-  -- book PTO around a date (https://developers.google.com/calendar/api/guides/overview)? 
-  -- scenario should use multiple tools
-  -- expense management
-  -- check in on the health of the team
-[ ] demo the reasons why:
-  -- Orchestrate interactions across distributed data stores and tools
-  -- Hold state, potentially over long periods of time
-  -- Ability to ‘self-heal’ and retry until the (probabilistic) LLM returns valid data
-  -- Support for human intervention such as approvals
-  -- Parallel processing for efficiency of data retrieval and tool use
-  -- Insight into the agent’s performance
+- check pay status <br />
+- book work travel <br />
+- check PTO levels <br />
+- check insurance coverages <br />
+- book PTO around a date (https://developers.google.com/calendar/api/guides/overview)?  <br />
+- scenario should use multiple tools <br />
+- expense management <br />
+- check in on the health of the team <br />
+
+[ ] demo the reasons why: <br />
+- Orchestrate interactions across distributed data stores and tools <br />
+- Hold state, potentially over long periods of time <br />
+- Ability to ‘self-heal’ and retry until the (probabilistic) LLM returns valid data <br />
+- Support for human intervention such as approvals <br />
+- Parallel processing for efficiency of data retrieval and tool use <br />
+- Insight into the agent’s performance <br />
+    - ask the ai agent how it did at the end of the conversation, was it efficient? successful? insert a search attribute to document that before return
 
 [ ] customize prompts in [workflow to manage scenario](./workflows/tool_workflow.py)<br />
 [ ] add in new tools? <br />
 
-[ ] non-retry the api key error - "Invalid API Key provided: sk_test_**J..." and "AuthenticationError"
-[ ] make it so you can yeet yourself out of a goal and pick a new one
+[ ] non-retry the api key error - "Invalid API Key provided: sk_test_**J..." and "AuthenticationError" <br />
+[ ] make it so you can yeet yourself out of a goal and pick a new one <br />