SyntheraOS University

TEAM KIT / TAKE IT WITH YOU

Run a session. Keep a useful reference.

Download the practical learning materials, lead a team exercise and review what each person learned.

COMPLETE LEARNING PACK

A training kit your team can use offline.

Interactive course, all nine workflow models, the project handbook, role playbooks, facilitator guide, and the searchable 60-record input/output register.

Download training kit (ZIP) Read the kit guide ↓

Unzip and open the HTML files. Training progress stays in the browser used to open them.

Interactive course12 exercises and 24 checks, with local progress.HTMLWorkflow libraryNine interactive models with input/output descriptions.HTMLInput/output registerAll 60 records in a spreadsheet-friendly format.CSVFacilitator guidePreparation, session agenda and debrief prompts.Markdown

FACILITATOR WORKSPACE

A 95-minute team session

PAUSE AND DISCUSS AS NEEDED

Suggested agenda

  1. 10 minWelcome, establish the fictional TRAIN- example, and practice input/action/output classification.
  2. 20 minWork in pairs on brief, requirement, architecture and interface definitions. Compare assumptions.
  3. 20 minPlan verification, assess evidence and describe the stale-display risk.
  4. 20 minReview the proposed timing change and choose usable delivery artifacts.
  5. 15 minEvaluate a recommendation and interpret telemetry source, timing and quality.
  6. 10 minExchange handovers, trace two claims to their sources and debrief.

Before the session

  • Choose a facilitator and identify each person’s role path.
  • Open the course on each learner’s device. Use the fictional TRAIN- records.
  • Agree who would own requirements, evidence, changes and handovers in your team.
  • Let learners try an answer before explaining it. Ask for the reasoning.

After the session

  • Ask each person to show one complete information chain.
  • Download learning records and review open questions together.
  • Apply one lesson to a real record with its owner.
  • Revisit affected lessons when a criterion or interface changes.
Debrief prompts for the team
  1. Which record was the most useful starting point for understanding the feature, and why?
  2. Where did your team discover an assumption that initially looked like a fact?
  3. What changed in your verification plan when the requirement changed?
  4. How did you distinguish a useful recommendation from an approved project decision?
  5. Which output could a receiving teammate actually open and inspect?
  6. What information would you ask for before using a telemetry value?
  7. Which open item needs an owner before your real team could continue the work?
Keep learning records distinct from project approvals. There is no shared learner database here. Learners choose when to download and share their record. Moving between this site and an offline copy starts separate browser storage.