Gate it, run it, verify it

Test-and-Check: Six Gates + Three Stages

Test-and-Check is one of ANIMA's defining moves: it turns the claim of task completion into a proposition that must be re-verified. Six gates reject uninterpretable specs before execution; three stages (Pre / Runtime / Post) ensure failure never gets silently papered over.

Before execution (six gates)

JSON / intent vocabulary / skill availability / parameter ranges / safety bounds / preconditions — any gate failing rejects the TaskSpec and triggers re-parsing at L1 or a clarification request to the user.

During execution (Runtime)

The behavior tree ticks observably: every node status change, every skill call, every failure-and-retry pushes an event toward L5. This catches drift earlier than checking logs after the fact.

After execution (Post-check)

Observe the world again: object poses, states, scene changes. Confirm the claim of success before trusting it — otherwise enter retry, rollback, or an explicit natural-language report.

Failure recovery

The system never fakes success. Failures route to one of three exits: retry (idempotent actions), graceful degradation (switch to a safer skill), or human handoff (report in natural language and request).

Key points

Why this layer matters

  • The Pre-execution gates are cheaper than Post-checks — reject what you can before you run
  • Failure is part of the system, not something to hide
  • This is the precondition for long-horizon home tasks to actually converge
Related robots

Current robot carriers