Product UX and seeded data
Navigation, mapping, playbook structure, visual plan preview, kickoff workspace, Delivery Receipt, replay model, settings expectations, and failure states.
Seeded demo workspace
Review ClientFlow with the Northstar Studio sample workspace: a signed SEO retainer becomes a governed delivery plan with missing-input checks, approval, Notion provisioning, readiness state, and a Delivery Receipt.
Navigation, mapping, playbook structure, visual plan preview, kickoff workspace, Delivery Receipt, replay model, settings expectations, and failure states.
Account creation, email verification, OAuth authorization, live workspace discovery, real database writes, disconnect and reconnect behavior.
This workspace is seeded with the Northstar Studio scenario. It is designed for product review and sales proof without touching a real workspace.
Review path
The demo uses the same scenario as the homepage, but lays it out like a product audit: account gate, Notion authorization, discovery, mapping, playbooks, visual plan preview, execution, Delivery Receipt, replay, and the expected failure paths.
31tasks generated
6owners and queues
2recurring deliverables
90 daystarget receipt retention
Password rules, confirmation, email verification copy, Notion-after-account sequence.
Permission explanation, cancel paths, plan limit messaging, reconnect expectations.
Workspace and database selection states for populated, empty, and unavailable data.
Clients, Projects, Tasks, Services, and the fields needed for access requests.
Versioned SEO Retainer playbook with inputs, owners, dates, and recurring deliverables.
Visual plan before writing projects, tasks, relations, dates, access requests, and recurring rows.
Provisioning progress, partial success, warnings, and plain-language recovery.
Business summary, action status, generated Notion links, and failed-action replay.
Seeded workspace
These product views are intentionally concrete: the reviewer can see the mapped databases, service playbook, visual plan, generated workspace, and Delivery Receipt.
Kickoff readiness
31tasks
1blocking input
v4playbook
Required access
Playbook+ SEO Retainer v4
Missing Input+ Search Console access request
New Project+ SEO Retainer - Northstar Studio
New Tasks+ 31 generated tasks
New Relations+ Client -> Project -> Tasks
Owners+ Sarah, Analytics, Content
Dates+ Kickoff Jul 22, Audit Jul 28
Recurring+ Weekly report, Monthly review
Kickoff MeetingSarahJul 22Ready
GA4 ConnectedAnalyticsJul 24Ready
Search Console AccessAnalyticsJul 24Blocked
Technical AuditSarahJul 28Queued
Monthly ReportContentAug 01Recurring
10:42:11Playbook approvedSEO Retainer v4 plan hash lockedsuccess
10:42:1831 tasks generatedTask pack linked to projectsuccess
10:42:23Missing inputSearch Console access blocks full readinessreview
10:42:31Delivery Receipt storedReceipt and replay context availablesuccess
Mapped roles, SEO playbook, visual plan preview, generated workspace, run history, and Delivery Receipt examples.
Real account session, Notion OAuth, live database discovery, saved mappings, and workspace-specific validation.
Polling, production writes, recurrence top-up, drift recovery, and the 20-minute first-run acceptance path.
Settings and controls
A mature product audit needs more than a happy path. This section documents the settings surface the authenticated app needs to expose around workspace control, ownership, notifications, and data handling.
Northstar Studio Demo, connected state, pause rules, disconnect path.
Sarah owner, Analytics queue, Content queue, role handoff warnings.
Execution success, warning, failed replay, monthly top-up alerts.
Stored IDs, encrypted vault, receipt retention, export/delete request path.
Failure testing
These are the cases a Notion power user will test first. The demo frames the expected product behavior so QA can compare real authenticated screens against it.
Block activation until Clients -> Projects and Projects -> Tasks relations are valid.
Pause dependent rules and show the database role that needs remapping.
Create safe warning when Sarah exists but Analytics queue needs review.
Respect Retry-After, continue queued actions, keep run visible.
Replay failed actions only so completed Notion pages are not duplicated.
Require validation when status, date, owner, or relation properties change.
Power user audit