Ketryx Academy — Season 1: AI in Practice
Learn the principles, understand the applicable obligations, practice with AI, and demonstrate the evidence in Ketryx.
Core customer jobs first, expanding across the TPLC; AI use and safe AI taught together in every episode.
Act 1 · Connected development
- S01E01Coming soon
Follow a requirement from Jira to release evidence
A requirement is in Jira, implementation is in Git, and the reviewer needs evidence for one release.
8–12 min - S01E02Coming soon
Turn a product need into requirements your team can review
A vague robot restart behavior needs a measurable requirement before implementation.
8–12 min - S01E03Coming soon
Find conflicting requirements before they reach implementation
Two requirements disagree about whether motion can resume without an operator reset.
8–12 min - S01E04Coming soon
Prove what was tested for this software version
A green build is available, but the reviewer needs to know which requirements and configuration it tested.
8–12 min - S01E05Coming soon
Change a requirement—and see what needs another review
A changed response-time threshold may invalidate existing verification.
8–12 min - S01E06Coming soon
Build a release evidence package your reviewer can follow
The release owner needs a coherent package rather than a folder of unrelated exports.
8–12 min
Act 2 · Risk and product configuration
- S01E07Coming soon
Connect a safety risk to the control and test that address it
Unexpected robot motion presents a hazard that needs a traceable control and verification.
8–12 min - S01E08Coming soon
Connect a cyber threat to an engineering control
A robot maintenance interface introduces an attack path with a possible safety consequence.
8–12 min - S01E09Coming soon
A dependency has a vulnerability. Does it affect this release?
A vulnerability is associated with a dependency used by the robot software.
8–12 min - S01E10Coming soon
Reassess risk when the product or field evidence changes
A changed behavior or new field signal challenges an existing risk assumption.
8–12 min - S01E11Coming soon
Release components independently—and assemble the right system
Perception and motion-control software release on different schedules.
8–12 min - S01E12Coming soon
Support an older release while developing the next one
A field patch must be tested while development continues on a newer version.
8–12 min
Act 3 · Quality and field operations
- S01E13Coming soon
Revise an SOP without losing its history
The service procedure needs a controlled revision after a new lesson from the field.
8–12 min - S01E14Coming soon
Make sure the right people are trained on the right procedure
A changed SOP creates a training obligation for a defined team.
8–12 min - S01E15Coming soon
Turn a field complaint into an investigation-ready record
A provider reports intermittent tracking but leaves out timing and device details.
8–12 min - S01E16Coming soon
After a sensor replacement, can this robot return to service?
A technician replaces the robot sensor and must establish whether service evidence applies to this unit.
8–12 min - S01E17Coming soon
Show whether a corrective action actually worked
Repeated field signals justify an investigation and a decision about corrective action.
8–12 min - S01E18Coming soon
Update release documents without losing source and revision context
A product change affects a generated table and a manually written section of the evidence package.
8–12 min
Act 4 · AI assurance and lifecycle change
- S01E19Coming soon
Evaluate an AI agent before relying on its findings
The conflict agent prompt is changing and the team needs evidence about intended-use performance.
10–14 min - S01E20Coming soon
Validate the workflow your team actually uses
A team introduces a Ketryx configuration and integrations into a regulated process.
10–14 min - S01E21Coming soon
One robot, multiple functions: what can actually be shared?
The medical robot includes a therapeutic function and another function sharing resources; the industrial variant also reuses a component.
10–14 min - S01E22Coming soon
Does this AI model update fit the predetermined change control plan?
A proposed perception-model update must be compared with a specified medical PCCP scenario.
10–14 min - S01E23Coming soon
Assess a robot software change in a functional-safety lifecycle
An industrial robot update affects a safety-related function and existing evidence.
10–14 min - S01E24Coming soon
Close the loop: use field evidence to decide what changes next
New field observations, component support status and model behavior challenge the released baseline.
10–14 min