Literacy perspective
How workflows, handoffs, roles, state, tools, memory, permissions, and orchestration create control.
What lecturers should notice
Trace intermediate artefacts, state transitions, capabilities, validation, stop conditions, and human approval points.
Related units
The role may be primary, secondary, supporting, integrated, or part of the attack surface; consult each unit’s metadata for the exact relationship.
Participants clarify a task before execution and keep accepted decisions in files. They move from a virtual Markdown workspace to local Python analysis, then use verified results to prepare a report across fresh contexts.
Participants turn a single request into an inspectable process with consequential human decisions. Four cumulative exercises use the same equipment-loan case: introduce three process cuts, make the intermediate artefacts and checkpoints explicit, add reviewing perspectives and roles, then evaluate quality, control and effort. PDCA brings these elements together. A live demonstration shows how project folders, Markdown files and skills support continuity and reuse.
Participants learn to move beyond a sequence of chat turns and design a controllable agentic system with explicit state, capabilities, routing, validation, permissions, stop conditions, and human approval. They learn when orchestration improves reliability and when it only adds complexity.
This final Friday makes security concrete as a control problem. Participants integrate learning from the preceding units to recognize where an AI-supported office task can lose control and to redesign the collaboration so that data, instructions, permissions, actions, and human responsibility remain appropriately separated.