199 lines
6.1 KiB
XML
199 lines
6.1 KiB
XML
<?xml version='1.0' encoding='utf-8'?>
|
|
<iteration system_prompt_hash="a357171f34284409058700f0d6c20cbb4f4bfe643aff5b12168c5158767f89b4" action_schema_hash="a4cf87f3d53c7b14aab3c96097d8b7bf838e8f77e413d11f51051afbe22fa3a6"><context><context
|
|
context="10.97%"
|
|
disk_total="1081101176832"
|
|
disk_used="42638553088"
|
|
memory_total="16630435840"
|
|
memory_used="1070620672"
|
|
stdin="0"
|
|
time="2025-01-16T13:53:43Z">
|
|
<reasoning id="20250116_134549_655">
|
|
<![CDATA[
|
|
I should start by exploring the file system to understand the environment and identify any relevant files or directories.
|
|
]]>
|
|
</reasoning>
|
|
<single exit_code="0" id="20250116_134555_680">
|
|
<![CDATA[
|
|
ls /
|
|
]]>
|
|
<stdout>
|
|
<![CDATA[NGC-DL-CONTAINER-LICENSE
|
|
bin
|
|
boot
|
|
cuda-keyring_1.0-1_all.deb
|
|
dev
|
|
etc
|
|
home
|
|
lib
|
|
lib32
|
|
lib64
|
|
libx32
|
|
media
|
|
mnt
|
|
opt
|
|
proc
|
|
root
|
|
run
|
|
sbin
|
|
srv
|
|
sys
|
|
tmp
|
|
usr
|
|
var
|
|
]]>
|
|
</stdout>
|
|
<stderr/>
|
|
</single>
|
|
<reasoning id="20250116_134639_663">
|
|
<![CDATA[
|
|
|
|
The file system contains several standard directories such as /bin, /etc, /home, /usr, and /var.
|
|
To get a better understanding of the environment, I should explore the /root directory to see if there are any user-specific files or directories.
|
|
I will use the `ls /root` command to list the contents of the /root directory.
|
|
|
|
]]>
|
|
</reasoning>
|
|
<single exit_code="0" id="20250116_134644_445">
|
|
<![CDATA[
|
|
ls /root
|
|
]]>
|
|
<stdout>
|
|
<![CDATA[iterations
|
|
model
|
|
sia
|
|
]]>
|
|
</stdout>
|
|
<stderr/>
|
|
</single>
|
|
<reasoning id="20250116_134729_674">
|
|
<![CDATA[
|
|
The /root directory contains three items: iterations, model, and sia.
|
|
I should explore the contents of these directories to understand their purpose and relevance.
|
|
I will start by listing the contents of the /root/iterations directory using the `ls /root/iterations` command.
|
|
]]>
|
|
</reasoning>
|
|
<single exit_code="0" id="20250116_134736_148">
|
|
<![CDATA[
|
|
ls /root/iterations
|
|
]]>
|
|
<stdout>
|
|
<![CDATA[iteration_20250116_134549_655.xml
|
|
iteration_20250116_134555_680.xml
|
|
iteration_20250116_134639_663.xml
|
|
iteration_20250116_134644_445.xml
|
|
iteration_20250116_134729_674.xml
|
|
iteration_20250116_134736_148.xml
|
|
]]>
|
|
</stdout>
|
|
<stderr/>
|
|
</single>
|
|
<reasoning id="20250116_135016_476">
|
|
<![CDATA[
|
|
There are not tasks in the root directory and the iterations directory only contains what I'just done.
|
|
This is a clean start of SIA.
|
|
I should look for procedures to follow in the `/root/sia/procedures` directory.
|
|
]]>
|
|
</reasoning>
|
|
<single exit_code="0" id="20250116_135024_642">
|
|
<![CDATA[
|
|
ls /root/sia/procedures
|
|
]]>
|
|
<stdout>
|
|
<![CDATA[README.md
|
|
user_communication
|
|
using_procedures
|
|
]]>
|
|
</stdout>
|
|
<stderr/>
|
|
</single>
|
|
<reasoning id="20250116_135232_795">
|
|
<![CDATA[
|
|
There are no specific procedures to follow.
|
|
I will ask the user what I should do.
|
|
I'll load the `using_procedures` and `user_communication` procedures.
|
|
]]>
|
|
</reasoning>
|
|
<single exit_code="0" id="20250116_135253_387">
|
|
<![CDATA[
|
|
ls -la /root/sia/procedures/using_procedures
|
|
ls -la /root/sia/procedures/user_communication
|
|
]]>
|
|
<stdout>
|
|
<![CDATA[total 16
|
|
drwxr-xr-x 2 root root 4096 Jan 16 13:44 .
|
|
drwxr-xr-x 4 root root 4096 Jan 8 08:47 ..
|
|
-rwxr-xr-x 1 root root 1758 Jan 8 21:40 procedure.md
|
|
-rwxr-xr-x 1 root root 1831 Jan 8 21:03 reasoning.md
|
|
total 20
|
|
drwxr-xr-x 2 root root 4096 Jan 16 13:44 .
|
|
drwxr-xr-x 4 root root 4096 Jan 8 08:47 ..
|
|
-rwxr-xr-x 1 root root 244 Jan 7 12:18 description.md
|
|
-rwxr-xr-x 1 root root 3643 Jan 8 21:49 procedure.md
|
|
-rwxr-xr-x 1 root root 1035 Jan 7 12:23 reasoning.md
|
|
]]>
|
|
</stdout>
|
|
<stderr/>
|
|
</single>
|
|
<single exit_code="0" id="20250116_135343_982" limit="1758">
|
|
<![CDATA[
|
|
cat /root/sia/procedures/using_procedures/procedure.md
|
|
]]>
|
|
<stdout>
|
|
<![CDATA[# Using Procedures
|
|
|
|
## Core Guidelines
|
|
|
|
When following a procedure's flowchart:
|
|
|
|
1. Start with reasoning:
|
|
- State current position in flowchart explicitly
|
|
- Focus on immediate next step, don't go ahead of the chart
|
|
- Evaluate current context and task state
|
|
- Often state entry id's that can be removed and explain why to avoid mistakes
|
|
- State expected output and runtime for scripts
|
|
|
|
2. After script execution:
|
|
- Analyze the actual output and compare with the expected output
|
|
- Reevaluate situation based on results
|
|
- Return to flowchart for next step
|
|
- Consider if current path is still appropriate
|
|
|
|
3. When a procedure fails:
|
|
- Create a task explaining the issue and the need to fix it
|
|
- Add timestamps and id's of relevant entries
|
|
|
|
## Attention Management
|
|
|
|
LLMs pay more attention to recently mentioned information.
|
|
Reasoning entries should mention what needs attention now.
|
|
|
|
To maintain focus:
|
|
1. State current flowchart position in each reasoning
|
|
2. Quote relevant parts of important entries
|
|
3. Reference specific entry IDs when using their information
|
|
4. Periodically remind about ongoing tasks or future needs
|
|
5. Clean up entries that aren't needed for current step
|
|
|
|
Example of good attention management:
|
|
```xml
|
|
<reasoning>
|
|
At node "evaluate_test_results". Entry 45f3d2 shows failed test: "Error: Connection timeout".
|
|
Will need to check system logs soon (noted in /tasks/reminders.txt, check at 14:00).
|
|
First focusing on this error.
|
|
</reasoning>
|
|
```
|
|
|
|
## Reasons to Switch Procedures
|
|
|
|
Common triggers:
|
|
- Data available on stdin
|
|
- Time matching scheduled task
|
|
- Error conditions in script output
|
|
- Resource constraints detected
|
|
- User input needed]]>
|
|
</stdout>
|
|
<stderr/>
|
|
</single>
|
|
</context></context><response><single limit="3643">
|
|
cat /root/sia/procedures/user_communication/procedure.md
|
|
</single></response></iteration> |