Skip to content

Lab evidence and reasoning

Create a separate private submission for each lab using this template. Leave this shared repository file unchanged. Replace the prompts in your copy with your own work; follow the lab page for its specific artifacts and rubric. If a lab supplies a completed worksheet structure, attach it and refer to its sections here rather than answering the same question twice. Independent learners can use the self-check guide. The terminal supplies execution evidence, not your interpretation or independent-task response. Use the course-wide evidence labels when they help distinguish observed, expected, proposed, simulated and supplied material.

1. Lab and execution evidence

  • Lab number and title:
  • Command actually run:
  • Relevant result excerpt from your own run:

Copy only the relevant PASS lines, expected denial, test result or other evidence specified by the lab. Do not paste the full installation transcript or package list. For reading-only activities, write "No execution required" and identify the sources used instead. A screenshot is optional; readable text evidence is sufficient.

2. Prediction or initial expectation

For labs that ask you to predict before running, record your prediction first, then preserve it even if the result differs. Do not rewrite it to match the output.

Complete this section only when requested by the lab. Otherwise write "Not required for this activity," or use the specific wording provided by the lab. Do not invent a prediction after seeing the result. For a reading-only activity, state an initial assumption or question only when requested.

3. Observed result and explanation

In your own words, explain what the evidence establishes and how the relevant mechanism works. Compare with your prediction when one was recorded. If an error occurred, describe the error and recovery accurately; do not invent a successful run.

4. Investigation and independent transfer

Include the artifact and responses requested on the lab page. These are your work, not additional lines you should expect the terminal to print. A text diagram is acceptable where a diagram is requested unless the activity specifies an editable model.

5. Evidence limitations and questions

State one conclusion the evidence does not establish and why. Identify any unresolved question; if none remains, say so rather than inventing one.

6. Assistance and verification

State whether you used AI assistance. If used, describe where it helped and how you checked the result. If not, write "None." Follow the current course's AI-use rules; this disclosure is not permission to use tools that an assignment prohibits.

Before submitting

  • Include only your own observed evidence and clearly labeled reasoning.
  • Remove shell prompts showing usernames/hostnames and personal filesystem paths.
  • Never include .env, passwords, tokens or full connection strings.
  • Keep work in the private course system or, for independent study, locally. Do not commit filled submissions to this public repository.

Author: Isaac K. Nti. Citation and reuse terms.