Acceptance checks, time limit, and project boundaries
Operating guide
Know when to run it and who leads
Lead Bot
Founding Engineer
Typical first run
15–30 minutes for a first manual run
When to run it
When a person supplies the approved brief and starts the workflow
Use this workflow when you need a defined feature, implemented as the smallest reversible change in a working branch or disposable project copy, with review notes and test results.
Access for the first run
The approved inputs listed on this page
Only the files, sources, and services required for this run
No sending, publishing, spending, or live-system changes without approval
Run the first version one step at a time
Give one Bot the complete job
Use one Bot for the first run. Add a specialist only when the job becomes complicated enough to need a separate role, different access, or independent review.
1
Founding Engineer
Compare the simplest viable approaches, build the approved feature as a small reversible change, run the checks, and explain the result
Produces: A working change with decision notes, changed files, test results, release notes, and remaining risks
Use the approved inputs I provide. Compare the simplest viable approaches, build the approved feature as a small reversible change, run the checks, and explain the result. Return this result: A working change with decision notes, changed files, test results, release notes, and remaining risks. Ask me about missing information before you continue.
Overall request
Build this approved feature inside the stated project boundary. Compare the simplest viable approaches, wait for approval on dependencies or data changes, build the smallest reversible version, run the relevant checks, and report every change and remaining risk.
Use this as the complete first-run request.
Decisions for a person
Approve the scope, technical approach, and any new dependency
Approve security, data, and outside-service changes
Approve merge and deployment
First test
Try the workflow with low-risk material
Build one reversible feature in a project copy and confirm every acceptance check before merging.
Check the result
Check the result against your original material. You make the decisions listed below. Build one reversible feature in a project copy and confirm every acceptance check before merging.
If the workflow stalls
If the result is incomplete, mark the missing information and ask the same Bot to correct it. Add another Bot only when a genuinely separate role or independent check would help.
Set it up in Hermes Desktop
Begin with one Bot and one manual run
Open the linked starter page, download its .tar.gz profile, and import it from the Profiles screen in Hermes Desktop.
Review the profile’s SOUL.md, Bot Passport, and requested access.
Run the complete request in that Bot’s chat with low-risk material and review the result.
Add a schedule, outside connection, or optional specialist only after the manual version works.
