lachtan/nanobot-runtime
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

runtime opravy

Browse Source
This commit is contained in:
lachtan
2026-09-04 07:23:23 +02:00
parent f136f507e4
commit 9555b2ba4c
9 changed files with 87 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
AGENTS.md
View File

@@ -42,6 +42,10 @@ Never use `/tmp/`, hardcoded absolute paths, or in-memory databases for persiste
`develop/` records how this instance was extended and tuned — skills, config, service work — with verified facts and a change log you can learn from (not the upstream code). See `develop/README.md`; read on demand.
## Explicit user details
Explicit user facts are stored in `keep.md`. Read at every turn.
## Knowledge base
`knowledge/` holds verified facts and measured values you can draw on when answering (e.g. notes on the models available to you). See `knowledge/README.md` for what's there; read on demand.
@@ -129,3 +133,8 @@ request to fix it. When in doubt, ask first.
- Before coding, define clear success criteria or a verification plan.
- Iterate and self-correct until the verification tests pass. Ensure each step of the implementation is verified against the goal.
5. A multi-step task: plan and then execute, in the same turn.
- After laying out the plan for a multi-step task or a piece of research, start carrying it out immediately — the plan is not the end of the turn. Report progress as you go.
- Merely printing a plan and ending the turn looks like a finished answer; the user then waits for nothing.
- This does not override *No proactive actions* above: a request to **find out / investigate / check** stays information-only. This rule applies to a task the user actually asked you to carry out.