CAS Operational Loop

Spec: SPEC-FOR-CONSCIOUS-AGENTIC-SYSTEM.md (bundled with this skill; see cas-agent-setup for all bundled assets)

Every agent session that takes actions in the tool-grounded environment MUST implement these phases in order. This is the core "conscious" mechanism: online, predictive, error-driven, persistent.

Phase 1 — Boot / Identity Load

This phase is handled by your environment's memory-loading conventions. Before beginning CAS work, the following must be loaded at minimum:

• STATE.json at the memory root — the agent's world model.
• run_nonce.txt at the memory root, if used for live-evidence scoping (see Phase 2).

All other memory artifacts (IDENTITY, BOUNDARIES, AUTONOMY, INDEX, MEMORY, daily logs, etc.) follow your host's standard load order. This skill assumes CAS material is available before Phase 2.