\chapter{Introduction} \ChapterLabel{Introduction} \index{introduction} \index{DevOps} \section{How to Use This Assignment} Replace bracketed text with approved assignment facts. Delete instructional examples before release, but retain the stable identifiers, history, glossary, index, appendices, and evidence structure. This document is an assignment brief and operational record, not a requirements or software-design document. \section{Purpose and Learning Objectives} State the DevOps capability students will practice and the observable learning outcomes. \textit{Example: Students will provision a minimal Linux service, automate its deployment, collect operational evidence, and demonstrate a safe rollback.} \section{Scope and Constraints} State the permitted cloud or local environment, team size, required tools, budget limits, source-control repository, timebox, and prohibited actions. Do not include credentials, access tokens, student records, or production data. \section{Deliverables and Due Date} \begin{tabularx}{\linewidth}{L{3.2cm}Y} \toprule \textbf{Item} & \textbf{Expectation}\\ \midrule Due date & \DueDate\\ Repository & \textit{[repository URL or LMS location]}\\ Required deliverables & \textit{[automation, runbook, evidence, reflection]}\\ Team policy & \textit{[individual or team; contribution expectations]}\\ \bottomrule \end{tabularx} \section{Using This Template with AI Agents} \index{AI agent!DevOps workflow} AI may assist with explanation, drafting, troubleshooting, and reviewing automation. It does not replace student understanding or authorize an agent to operate accounts, approve work, invent results, or receive secrets. Before editing, an AI agent shall read \texttt{devopsAIAgentGuide.tex}, load only the relevant assignment files, identify assumptions, and preserve evidence boundaries. Record material AI assistance in \ChapterRef{AIPromptLog}. \begin{verbatim} Read devopsAIAgentGuide.tex first. For this SSW 590 assignment, identify the requested task and read only the listed sources. Use supplied evidence only; do not invent commands, deployment results, approvals, credentials, or costs. Preserve stable IDs and history. Make the smallest appropriate change, build the PDF, and report assumptions, risks, and actions requiring human approval. \end{verbatim}