organization

To validate worker state and team topology in HiClaw, use the authoritative hiclaw CLI to resolve the Kubernetes Team CR name and fetch current room IDs, Matrix IDs, and worker phases instead of relying on cached metadata.

Multi-agent orchestration fails with stale room IDs because leaders act on outdated assumptions. Using the hiclaw CLI ensures accurate team topology and prevents incorrect assignments by fetching the latest authoritative worker state.

When hiclaw CLI output is incomplete, worker lifecycle operations stop and report the missing data. This orchestration safety guardrail refuses to guess required room or Matrix IDs, preventing invalid sleep, wake, or readiness actions.

To handle cross-room messaging and heartbeat events safely, query the hiclaw CLI to validate required Matrix IDs and worker runtime phases first, ensuring the leader uses the authoritative team topology before sending messages.

You should query the Kubernetes Team CR name before any worker lifecycle state change, such as waking, sleeping, or ensuring readiness. Resolving the Team CR name first guarantees the operation targets the correct authoritative team scope.

No, you should not use cached chat history for project recovery. The hiclaw CLI serves as the single source of truth for team topology and runtime state, ensuring safe execution and preventing incorrect lifecycle orchestration actions.