operator-identity-context

To enforce an operator authority model across automated agent sessions, you load this skill at session start to establish identity, define roles like Manager and Admin, and apply governance rules without manual prompts.

A baton handoff rule for multi-platform agent governance enforces a single-thread execution mandate during sessions, ensuring only one operator role holds authority at a time to coordinate automated tasks safely across the fleet.

Yes, you can automate end-to-end tasks without manual intervention by applying the automation mandate, which uses hard rules and safety checks to reference inventory and runtime resources for autonomous execution.

Yes, the operator identity model supports self-audit and risk analysis by implementing self-audit triggers and tooling that validate changes and ensure policy compliance before executing actions across the fleet.

You establish role-based access for Manager, Collaborator, and Admin roles by loading the skill at session start, which defines the global operator authority model and enforces these roles across all active automation sessions.

The single-thread baton handoff limits session governance to one active operator authority at a time, preventing parallel role execution but ensuring strict safety checks and coordinated policy compliance across multi-platform fleets.