Persistent Goals
Persistent Goals
Start with meaning, then move to detail.
This lesson explains Persistent Goals as part of Hermes internals and extension points. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect When to use it, Goals vs Kanban: which one do I want?, Quick start, then verify failure modes and version compatibility.
Know Python, Git, and basic project structure before changing code.
A clear outcome before you read.
- Understand Persistent Goals without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Automation
- Running work later or repeatedly with explicit success and failure conditions.
Set a standing goal and let Hermes keep working across turns until it's done. Our take on the Ralph loop.
What does the source say, and in what order?
- 01When to use it
Start here to understand the core idea or structure.
- 02Goals vs Kanban: which one do I want?
Read this after the foundation, then connect it to the previous step.
- 03Quick start
Read this after the foundation, then connect it to the previous step.
- 04Commands
Read this after the foundation, then connect it to the previous step.
- 05Completion contracts
Read this after the foundation, then connect it to the previous step.
- 06Two ways to set a contract
Read this after the foundation, then connect it to the previous step.
- 07Adding criteria mid-goal: /subgoal
Read this after the foundation, then connect it to the previous step.
- 08Quality gates
Read this after the foundation, then connect it to the previous step.
- 09Parking on a background process: automatic, with a manual override
Read this after the foundation, then connect it to the previous step.
- 10Behavior details
Finish here to verify the result and special cases.
Copy only after you understand the effect.
/goal Fix every failing test in tests/hermes_cli/ and make sure scripts/run_tests.sh passes for that directory/goal draft Migrate the auth service from session cookies to JWT/goal Migrate auth to JWT
verify: pytest tests/auth passes
constraints: keep the /login response shape unchanged
boundaries: only touch services/auth and its tests
stop when: a DB schema migration is requiredRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.