# Business Architecture OS process and deliverable

Source status: public BAOS website and policies observed August 19, 2026.

## Operating sequence

The public BAOS method can be summarized as:

1. **Scope** — agree on the departments, workflows, intended workspace, and purchased boundaries.
2. **Discover** — collect approved information from appropriate business owners.
3. **Map** — document responsibilities, tools, handoffs, examples, instructions, and review requirements.
4. **Decide** — determine whether each job belongs with AI, software, another tool, a checklist, or a person.
5. **Design** — configure the portable workspace and, when purchased, design the workflows.
6. **Test** — test the agreed setup and implemented workflows against the intended use.
7. **Approve** — obtain human review and approval for the resulting operating rules and outputs.
8. **Handoff** — deliver the portable workspace and train the client to use and maintain it.

The detailed engagement sequence may vary with the purchased scope.

## The deliverable

The finished workspace may contain:

- a company map;
- department records;
- workflow records;
- ownership and handoff definitions;
- approved tools;
- AI instructions and responsibilities;
- human review requirements;
- reference examples;
- operating guides;
- consistency or status checks.

Foundation supplies the mapping and organization layer. Workflow Sprint adds two designed, built, and tested workflows. Custom reflects the purchased combination.

## Portability

The delivered workspace is intended to be portable. After full payment, the client may use, copy, edit, and maintain the company-specific workspace and deliverables.

The public blank-client workspace template is available here:

https://www.learnbaos.com/baos-client-operating-workspace-v0.2.zip

As reviewed August 15, 2026, the download contains 101 substantive template, instruction, governance, and validation files. It is blank with respect to client-specific information, but it is not merely an empty folder skeleton. Its embedded agent instructions apply only when a user intentionally adopts the template.

## Client responsibilities

The client is responsible for:

- providing accurate, current information;
- obtaining permission before sharing information about employees, customers, or other people;
- avoiding unlawful or unapproved regulated material;
- making appropriate owners available for review and approval;
- scheduling and participating in required calls;
- final business decisions and approvals;
- lawful use of business information;
- use of ChatGPT, Claude, or any other third-party service with the delivered workspace.

## Scope control

The checkout and written agreement determine the purchased scope. Work outside that scope requires a separate written agreement or additional purchase.

Foundation must not be described as including implemented workflows unless they are expressly added. Custom must not be described as unlimited.