Tools
How Atoi decides which tool to use, and where its authority stops.
Atoi can search, use connected services, run structured tools, drive a browser, use a computer, and keep long work going as a task. It picks the least powerful option that gets the job done.
#The order
- What is already in the thread, project, files, or memory.
- A connection or an API.
- Structured read, shell, file, and git operations.
- A browser it can read.
- A browser it can only see.
- A full desktop on a computer.
- Handing control to you.
#The pieces
| Piece | Role |
|---|---|
| Model | Reasons and writes |
| Skill | Instructions for a kind of work |
| Connection | Authorization to use a service |
| Tool | One bounded operation available right now |
| Computer | A place to run, with stated capabilities |
| Task | Long work with a state |
| Receipt | The proof of what happened |
#Only real tools
A capability summary says what Atoi may use in this thread. Only the tools that are actually loaded can run. If one is missing, Atoi says so instead of pretending.
#Code work
Code that changes a project runs as a task and comes back with changes, checks, and proof. There is no separate "code mode".
#Where authority stops
Having a tool is not permission to use it for anything. Sending, deleting, credentials, payments, permissions, and settings keep their gates.
Read Computers for where a tool runs, or Asks and approvals for where its authority stops.
Was this useful?