# Agent Agency — Desktop Prototype v007 · Owner Walkthrough Status: **READY FOR HUMAN OWNER WALKTHROUGH** Implementation gate: **CLOSED** PM handoff: **DRAFT / WAITING OWNER PROTOTYPE APPROVAL** ## Open Prototype: https://files.anpavel.ru/Agency/Prototype/Desktop/index.html Target desktop: - 1366–1920 px - synthetic but realistic fixtures - no production writes - no Hub data mutations - no Mission execution ## Recommended walkthrough 1. **Projects** - Compare Agent Agency and Mama Aba. - Check human description, current stage, next action and Owner Attention. 2. **Agent Agency → Overview** - Read NOW / NEXT / ATTENTION without opening technical details. - Inspect Team preview, Recent Activity, Results, execution recommendation and Drive status. 3. **Roadmap** - Follow completed journey → current stage → next → future. - Expand a completed stage and verify WHY / WHAT / WHO / RESULT / WHAT IT UNLOCKED. - Open the current Desktop UX task. 4. **Task inspector** - Owner summary appears first. - Responsible / planned / actual execution are separate. - Open execution planning and compare Automatic / Preferred / Exact. - Expand Technical details only deliberately. - Use Discuss. 5. **Result** - Open the accepted Result from Task or Overview. - Confirm human action buttons are primary and raw locator is secondary. 6. **Team** - Check why each Employee is in the project. - Check responsibility, observed execution, accepted version and global/project Drive workspaces. 7. **Employee Library** - Search QA, архитектор, Product, разработчик. - Open profession detail. - Reuse an existing Employee or choose Create. - Preview Add Employee to Project. 8. **New Project** - Sources → Interview → Bootstrap Proposal → Provisioning. - Confirm the flow is understandable without knowing Hub internals. 9. **Scenario selector** - Empty states - Unavailable / error - Data inconsistency - Long content stress ## What to judge - Is Project Overview the right opening screen? - Does Roadmap tell a meaningful project story? - Is Task inspector calm enough for normal Owner use? - Is Results/Artifacts understandable without raw URLs? - Does Team explain why each Employee exists in the project? - Can you find a profession in ≤3 meaningful actions? - Is reuse/create/add-to-project now unambiguous? - Is New Project Bootstrap understandable as one flow? - Are execution controls useful without becoming a model console? ## Not an acceptance gate in this iteration - mobile redesign - production API wiring - real Google Drive provisioning - real runtime launch - production Hub redesign Those follow only after Owner prototype approval.