azoth-session-closeout

End-of-session workflow orchestration is automated by triggering the Azoth /session-closeout workflow through the Codex interface, unifying evaluation, closing, and synchronization steps into a single command contract.

The session-closeout workflow process is an automated end-of-session governance mechanism that reads authoritative sources to preserve stage structures, gate rules, evaluation rules, and orchestrator agent bindings for safe execution.

Yes, you can pass optional arguments to the Codex session closeout command. The workflow reads these arguments from user prompts while preserving the command contract and write-enabled orchestrator agent semantics.

The best way to trigger end-of-session evaluation and synchronization is invoking the azoth-session-closeout skill, which coordinates execution via command.yaml and body.md to maintain governance gate rules.

Yes, the session closeout workflow preserves gate rules and evaluation rules. It reads authoritative sources at commands/session-closeout/command.yaml and body.md to maintain the workflow's stage structure and referenced skills.