First run — empty workspace to published post

First run — empty workspace to published post A workflow diagram generated by Archify. 01 / What the operator does 02 / What Cradle does 03 / What the fleet does Account Fleet Content Sign up · Email or Google · What the operator does › Account Sign up Email or Google Workspace · Name + time zone · What the operator does › Account Workspace Name + time zone Add agent · Guided wizard · What the operator does › Fleet Add agent Guided wizard Add account · Handle + login · What the operator does › Fleet Add account Handle + login Compose · Caption + media · What the operator does › Content Compose Caption + media See history · Every step, timed · What the operator does › Content See history Every step, timed Verify email · 6-digit code · What Cradle does › Account Verify email 6-digit code One-time token · 2-hour expiry · What Cradle does › Fleet · single use One-time token 2-hour expiry single use Store secret · Vault only · What Cradle does › Fleet · write-only Store secret Vault only write-only Schedule · Due-time index · What Cradle does › Content Schedule Due-time index Published · Post state updated · What Cradle does › Content · done Published Post state updated done Devices appear · Agent dials out · What the fleet does › Fleet Devices appear Agent dials out Signed in · On the real app · What the fleet does › Fleet Signed in On the real app Publishes · Real app, real phone · What the fleet does › Content Publishes Real app, real phone account is ready never shown again devices are in generate pick a time follow it verified on device job dispatched code emailed verified operator runs it released for one job empty workspace Legend User UI Agent logic Policy External system

The checklist tells the truth

  • • Every step is ticked by a real event, not by clicking a tour
  • • An agent registering, a device syncing, a post publishing
  • • It disappears on its own once the workspace is running

No hardware needed

  • • The simulator speaks the same contract as a real agent
  • • Simulated devices are badged SIMULATED everywhere
  • • Everything set up now keeps working when phones arrive

Credentials, once

  • • Typed once, stored in a vault, never displayed again
  • • Released only to a device running a sign-in job
  • • Every release is written to the activity log