amcos-transfer-management

Agent transfers require dual approvals from both source and target COS managers. The workflow tracks state progression from pending to source-approved, then target-approved, and finally executed, while enforcing team scoping throughout.

The approval workflow requires dual sign-offs from outbound and inbound COS managers. It uses a state machine moving from pending to source-approved to target-approved, ensuring proper oversight and auditability before updating team memberships.

Initiate a team transfer by creating a TransferRequest via the GovernanceRequest API to move an agent from source to target team. The system then awaits dual approvals before updating team memberships and access controls.

Yes, governed agent transfers use AMP for notifications throughout the approval workflow. The system sends alerts to source and target managers as the state progresses from pending to executed.

When an agent transfer executes, the system automatically updates team rosters and access controls via registry updates. This finalizes the governed movement and reflects the new team membership accurately.

Rejected transfer requests trigger rejection handling within the state machine, logging the event in audit trails. This maintains governance oversight and prevents unauthorized agent movements between teams.