# Agent Agency — B0.UI Project View Prototype

Status: **OWNER-DIRECTION INTEGRATED / V006 / SYNTHETIC / B1 NOT ADMITTED**

This prototype validates the Owner-facing product hierarchy after the Human Owner review of the first B0.UI iteration.

## Product hierarchy

Outside a project:
- Projects
- global Agent Library

Inside an opened project, the project is the root. Primary navigation is deliberately limited to:
1. Dashboard
2. Roadmap
3. Team

Task, Mission, Run, Result, Decision, Context, History, MD/handoff and GitHub/runtime references are supporting drill-down evidence. They do not get their own project-level navigation merely because those entities exist in the architecture.

## Core Owner use cases

1. Open a Project.
2. Understand project state in seconds.
3. See the current delivery stage, what is blocked, and what comes next.
4. Read the full Roadmap as project stages and dependencies.
5. See which agents form the Project Team and what each is responsible for.
6. Add/remove a reusable Employee from the global Agent Library.
7. Open a Roadmap item to reach evidence, handoff and execution/runtime references when needed.

Agent Agency is an information/control layer. Execution continues in native runtimes such as ChatGPT, Grok and Cursor.

## Roadmap model

Roadmap is a vertical stage map rather than a kanban board.

- Stages are project-specific.
- Stage order runs top-to-bottom.
- Tasks/items live inside stages.
- Parallel work may branch from a stage.
- Gates/dependencies are visible on the stage that cannot proceed.
- Current stage visually dominates.
- Mission/Run detail is drill-down evidence, not the Roadmap's primary organizing model.

The seeded Agent Agency software project and Mama Aba content/design project intentionally use different stage definitions.

## Mobile accessibility direction

The v004 mobile layout uses:
- 18px root text scale;
- 37px page heading;
- 25px Roadmap stage headings;
- 17px Roadmap item titles;
- large tap targets and only three project-level bottom-navigation destinations.

The objective is readable status/decision use on a phone, not merely technical responsiveness.

## Run locally

```bash
cd target-v2/prototype/b0-ui
python -m http.server 4173
```

Open `http://localhost:4173/`.

This is a synthetic prototype with no production credentials and no Mission execution.

## Agent identity vs execution observation

An Agent/Employee is a reusable professional profile living in Agent Agency. It is not equal to a runtime or model.

The UI deliberately distinguishes:

- **Agent identity** — professional profile, specialization, skills, instructions and project membership;
- **available/supported runtimes** — where this professional may be initiated when policy/bindings allow;
- **execution observation** — the runtime/provider/model actually observed for a concrete work item / Mission / Run.

Example:

`AA-101 · PRODUCT / UX · Observed: ChatGPT · GPT-5.6 Sol · now`

If a runtime or model cannot be proven, the prototype displays `unknown`. Assignment or membership is never treated as proof of execution.

The adapter-level observability matrix is tracked in GitHub issue #15.


## Google Drive Employee workspaces

The accepted architecture addendum introduces human-editable Google Drive workspaces without making Drive the canonical project/task/runtime store.

### Global Employee workspace

Human-facing path:

`Employees / <Employee> /`

Typical sections:
- Profile
- Skills
- Playbooks
- References
- Materials

B0.UI exposes **Open global workspace in Google Drive** from Agent Library and Team.

### Project-local Employee workspace

Human-facing path:

`Projects / <Project> / Team / <Employee> /`

Typical sections:
- Project Notes
- Project References
- Materials
- Local Instructions

B0.UI exposes **Open project workspace in Google Drive** from Team and directly from a Roadmap item's responsible-agent detail.

### Product truth

The UI distinguishes:
- editable Drive draft;
- approved Employee/profile version;
- approved project material package;
- last checked / pending change state;
- Mission-pinned inputs.

A Drive edit does not silently replace an approved version or an active Mission's pinned snapshot.

The prototype uses synthetic workspace locators only. Real Google Drive folder provisioning and folder_id deep-links belong to the later Drive integration vertical slice.