Learning paths

Four paths, one per job. Each path is a thin ordered checklist: it links the Product and Build pages that show how, and adds no reference of its own. Keep the wiki open alongside as reference.

• Day-0 admin: from invite to first governed session. For every customer admin. About 45 minutes. Outcome: a live tenant with org identity set, people invited, one agent shaped, and one recorded session.
• User sessions: run governed sessions day to day. For tenant users. About 20 minutes. Outcome: one recorded session, one deliberate approval decision, a troubleshooting starting point.
• FDE blank to live: empty tenant to one live tenant-level enhancement. For field engineers. A multi-session engagement. Outcome: a scoped, verified, handed-over enhancement with artifacts.
• Platform ops provision: create, provision, invite, verify, hand off. For the PRESHai operating team (org 1, internal). Outcome: a core-ready tenant at first value, tracked into steady state.

How to use these paths

1. Read in order within a path. Steps build on each other; checks confirm each step landed.
2. New to the platform first: What is PRESHos Platform, Core concepts, and the Naming guide.
3. Respect the scope notes. Steps link real pages; where coverage is still thin the path says so honestly instead of inventing procedure.