AiSymptom

Remarks

⚠ Four symptoms, and every one of them is a shape in the record stream rather than a fact about a tree. That is what makes the same reader work for all three planners, and it is what makes doc 37 § P7's exit criterion — diagnosed from the recorded log alone — possible at all: a reader that needed the tree would need the world, and the world is what is not there when a headless test fails on a build machine at three in the morning.

⚠ There were five, and P9's sample deleted one. NeverFinishes reported an agent that had run a single action for the whole window — and a patrol between two waypoints, a MoveTo across a courtyard and every other long action in a working game is exactly that. The log has no notion of progress, so it cannot tell a guard walking its beat from one stuck against a wall, and a symptom that fires on healthy agents is worse than no symptom because people learn to ignore the list it is in. It was found by a village of three agents that were all behaving perfectly and two of which were reported.

Fields and properties (5)

• None

  Nothing to report.

• Flapping

  It keeps changing its mind. The visible failure of a utility agent, and of a tree whose decorators disagree.

• StuckFailing

  The same thing failed over and over and nothing else was ever tried.

• Idle

  Its planner produced nothing: no action, or the same nothing every step. An unfinished set, an unreachable goal, a tree whose root fails.

• Thrashing

  Its steps are doing far more work than a settled agent's — a tree churning branches.

Used by (4)

• AiDiagnosisVixen.Ai
• AiDiagnosisExitCriteriaTestsVixen.Ai.Tests
• AiFindingVixen.Ai
• AgentDebugModelTestsVixen.Editor.AssetEditors.Tests