Give newcomers a path through the product, its language, and its journeys.
Onboarding turns a current project revision into an AI-narrated book whose chapter structure is derived from the specification and whose prose can be edited by the team. Guidelines and Role FAQ sit beside it as tabs, so one place teaches the product, each role's manual, and the questions that role will ask.
Product walkthrough
Onboarding, in context.
Demo project data shown for illustration.
Screen 01 / 02
Welcome checklist
A first-shift checklist grounds new dispatchers in the customer promise.
The working path
A focused loop around the same project context.
A new engineer joins mid-project and needs a readable explanation of the product, its people, and the journeys behind each epic, with links to the actual flows.
- 01
Generate the book and follow chapter-level progress while the server continues working in the background.
- 02
Read Welcome, Language, People, Journeys, Rules, and Appendix chapters alongside their source flows.
- 03
Edit a chapter, rescan only changed source material, or deliberately regenerate the whole book when a fresh version is needed.
Using Onboarding
The chapter structure comes from the spec; only the prose is AI-written. Document maintenance can check the book, guidelines, and FAQs on publication or daily and either propose updates for review or apply them automatically. Public readers see finished chapters only and have no chat or editing surface.
Continue exploring