AOS Work Playbook

This is the AOS Work playbook. It skips model theory and stays on how you use it in your actual work: where to start with a task, which resources it needs, and where the output gets checked.

The four chapters cover four layers: meeting the product and its resources, turning one result into a system, single-task office scenarios, and role scenarios. The lessons follow a dependency order, and every section number and cross-reference in the text matches it.

What Each Chapter Covers

ChapterCoverageThe question it answers
Chapter 1Product positioning, the interface, the four resource types, the two context mechanismsHow does it work, and what do I need to set up
Chapter 2Workspaces and automation, building Skills, designing Work, taking assets furtherHow do I make this work for me over the long term
Chapter 3Six office tasks, end to endHow do I do this task in front of me
Chapter 4Eight role scenarios, end to endWhat are the established uses for my role

How One Task Actually Runs

The whole book is about one thing: you hand the work over, it hands back the finished result. The only difference is who starts it — sometimes you tell it what to do, sometimes you set a time in advance and it starts on its own.

You start a task
  1. You state the goal and acceptance criteria
  2. The agent reads context and breaks the work down
  3. It invokes tools, Skills, and Connectors
  4. It produces and delivers the files
  5. You review: accept, or send it back
A plan starts the task (no one gives an instruction)
  1. A schedule or event fires
  2. The agent reads context and the trigger condition
  3. It invokes tools, Skills, and Connectors
  4. It produces files and files or routes them by rule
  5. It asks for your authorization or notifies you when needed

Both cases run the same work in the middle; only the start and the end differ. A task you hand over comes back for you to accept or reject. A task on a schedule is delivered by the rules you set in advance, and it only comes back to you when it needs authorization or hits an exception.

The picture maps onto the four chapters: Chapter 1 covers the two ways a task starts and the resources it needs; Chapter 2 fixes those practices into a reusable system; Chapters 3 and 4 demonstrate them in real work settings.

The Course Arc

  1. Meet BasilAOS
  2. Read the interface and output exits
  3. Send the first task
  4. Build the resource map
  5. Add a Skill and a Work
  1. Open a Connector
  2. Connect Apps, Memory, and workspaces
  3. Advanced systems and authoring
  4. Office scenarios
  5. Role scenarios

The first five steps get you through one task on your own: you know what the product is, you can hand work over, and you can direct it to the right resources. The last five extend that reach to external systems, organizational assets, and a full role workflow — and let you write a capability built around your own business.

All Lessons

Chapter 1 · Meet BasilAOS — Your New Work Partner

Chapter 2 · Advanced Systems — Turn One-Time Wins Into a System

Chapter 3 · Office Work, Solved — One Task at a Time

Chapter 4 · Role-Specific Scenarios