Concepts · Humans and machines
SOAR chunking creates a production rule from a subgoal result so similar situations can be handled faster without repeating the same problem solving.
What Is SOAR Chunking?
SOAR chunking is how the architecture learns production rules from the results of substate problem solving.
When SOAR hits an impasse, it opens a substate and works the smaller problem. When that work creates a result for a higher-level state, chunking summarizes the relevant reasoning in a new production. Next time a similar situation appears, the system can fire the rule instead of repeating the subproblem.
That is procedural learning, not a saved transcript.
In ACT-R, a chunk is a unit of declarative memory (a fact or episode). In SOAR, chunking is the mechanism that creates a production from a substate result. Same word family, different job.
| Term | What it means |
|---|---|
| ACT-R chunk | A structured unit in declarative memory |
| SOAR chunking | Learning a production from a substate result |
| Production | An if-then rule that matches conditions and takes action |
How SOAR chunking works
SOAR reaches an impasse when it cannot move forward in the normal decision cycle. It creates a substate, where the system works until it produces a result for a higher-level state.
Chunking happens as soon as the result is created. SOAR summarizes the substate reasoning that contributed to it and adds the learned production to production memory.
The learned chunk says, in effect:
When a similar situation appears again,
produce the useful result directly.That is why chunking is powerful. It turns slow problem solving into faster future behavior.
SOAR chunking vs ACT-R chunks
Developers often search "chunk" after reading ACT-R and land here by accident.
Keep the split clean:
- ACT-R chunk = what the system knows (declarative).
- SOAR chunking = how the system learns what to do next (procedural).
If you only need declarative structure, start with Chunks and Declarative Memory. If you need learning from stuck problem solving, stay on this page.
A simple example
Suppose an agent keeps facing the same support ambiguity.
The customer is in a high-trust tier. The refund is below a safe limit. The product was purchased recently. The policy allows an automatic refund.
The first time, the agent may need to check several things. It may create a subtask, inspect policy, compare options, and resolve the impasse.
After that, a learned rule could help:
If the customer is high-trust
and the refund is below the safe limit
and the purchase is recent,
prefer the automatic refund operator.That is not official SOAR syntax. It shows the shape of the lesson.
Why AI builders should care
AI systems often repeat work.
They re-read the same policy. They re-derive the same tool sequence. They recover from the same error in the same slow way.
SOAR chunking gives a useful design question:
What should the system learn from the way this problem was solved?
The answer should not be "save the whole transcript." A transcript may help, but it is noisy. The useful lesson is often smaller: the condition that mattered and the action or preference that resolved the problem.
The caveat
Learned rules need review.
If the system learns from a bad resolution, it can become faster at doing the wrong thing. If the situation changes, an old chunk can mislead future behavior.
So the AI lesson is not "auto-learn every rule."
The lesson is: when a repeated problem is solved well, preserve the useful pattern in a form that can be inspected, weakened, or removed.
The takeaway
SOAR chunking turns solved problem solving into future procedural knowledge.
For AI agents, it points to a better kind of memory: not only saving what happened, but learning which pattern helped the system move forward.
Sources
Go back to Impasses and Subgoals in SOAR, continue with Semantic and Episodic Memory in SOAR, or return to the Concepts hub.