Assemble the kit, prove every spare, and label what has not been proven
Task
Build the physical kit, test every spare before it earns the label known-good, and record explicitly which items are unproven -- because an unproven spare contaminates every test it takes part in.
Steps
- Write
lab/kit/contents.csvwith headeritem,have,proven,proved_how,datecovering measurement tools, hand tools, consumables, spares and protection. - For every spare, test it in a working machine and fill
provenandproved_howwith what you actually did, not withyes. - Label the proven spares physically and record the labelling in
lab/kit/labelled.txt. - Write
lab/kit/unproven.mdlisting every item you could not prove and what proving it would require -- an item on this list is not a spare, it is a part. - Write
lab/kit/software.csvwith headertool,purpose,writes_to_diskfor the bootable drive's contents, marking which tools modify a disk and therefore must not run before a copy.
Verify
awk -F, 'NR>1 && NF>=5 {n++} END {print n" kit item(s)"}' lab/kit/contents.csv
awk -F, 'NR>1 && tolower($3)=="yes" && $4!="" && tolower($4)!="yes" {n++} END {print n+0" item(s) proven with a method"}' lab/kit/contents.csv
grep -c . lab/kit/labelled.txt
grep -c . lab/kit/unproven.md
awk -F, 'NR>1 && tolower($3)=="yes" {n++} END {print n+0" software tool(s) that write to disk"}' lab/kit/software.csv
Eight or more items inventoried, at least two proven with a stated method, a labelling record, an unproven list, and at least one software tool marked as writing to disk. A software table where nothing writes to disk has not included a partition or imaging tool.
Notes
lab/kit/unproven.md is the file that keeps the kit honest. The moment an unproven part is used as a known-good substitute, every conclusion drawn from that test is unsupported.
This is an independent study companion for CompTIA A+ Core 1 220-1201 and is not produced by or endorsed by CompTIA.