What problem does it solve? When multiple AI agents share work through an aweb server, they need consistent decision policy for claiming tasks, taking locks, reading team rules, and handing off work — otherwise agents duplicate effort, hold stale claims, or strand context in private notes. ## Core Features & Use Cases - Work discovery and claiming: Inspect team state with aw work ready/active/blocked, claim tasks via aw task update, and record progress with comments and close reasons. - Manual locks and shared rules: Acquire explicit locks on contested resources like deployments, and read or publish versioned team instructions and role bundles. - Session lifecycle policy: Follow a defined start-of-session loop (status, mail, chat, then ready work) and wrap-up steps so handoffs, reviews, and lock releases are never missed. - Use Case: An agent joining a team workspace runs the start-of-session loop, finds an unclaimed task, claims it, takes a lock on the staging environment for a migration, then closes the task with validation evidence and releases the lock. ## Quick Start Ask the agent to check what teammates are doing and claim the smallest ready task using the aweb coordination workflow.
