These examples demonstrate how SUBIT‑encoded packets form valid dialogues within the protocol.
All payloads are SUBIT sequences; all dialogues follow the structural rules defined in the specification.
A minimal STATE → INTENT → ACTION flow.
STATE
000110
INTENT
000110110001
ACTION
011011110001
- STATE sets the agent’s configuration.
- INTENT expresses a desired transition.
- ACTION executes the transition.
A simple query‑response with reasoning.
STATE
010101
INTENT
010101001111
ACTION
001111011000
TRACE
001111011000011011
- The agent receives context.
- It generates intent.
- It performs the action.
- It returns a reasoning trace.
A structured reasoning chain.
STATE
000010
PLAN
000010 110001 011011 010100
TRACE
110001 011011 010100
- PLAN encodes a multi‑step transformation.
- TRACE explains the reasoning.
Two agents coordinating.
STATE(A)
000110
INTENT(B)
000110110001
ACTION(A)
110001011000
- A provides context.
- B generates intent.
- A executes the action.
A dialogue with structural failure and reset.
STATE
001100
INTENT
001100111000
ERROR
111111
STATE
010000
INTENT
010000110001
ACTION
110001011011
- ERROR invalidates the previous chain.
- A new STATE resets the dialogue.
- The cycle continues normally.
A longer reasoning cycle combining planning and execution.
STATE
000001
PLAN
000001 000111 001111 011111
ACTION
011111010101
TRACE
000111 001111 011111
- PLAN defines the reasoning path.
- ACTION executes the final step.
- TRACE provides explanation.
{
"type": "STATE",
"payload": "000110"
}
{
"type": "INTENT",
"payload": "000110110001"
}
{
"type": "ACTION",
"payload": "011011110001"
}
{
"type": "PLAN",
"payload": "000110110001011011"
}
{
"type": "TRACE",
"payload": "110001011011"
}
{
"type": "ERROR",
"payload": "111111"
}
INTENT → ACTION
ACTION → STATE
PLAN → INTENT
These violate the dialogue rules and must produce an ERROR.