# Project Evidence

This folder holds reviewer-facing evidence for portfolio projects such as the home lab, Microsoft 365 lab, PowerShell automation, identity and access administration, endpoint management, infrastructure networking, monitoring, backup/recovery, and troubleshooting work.

## Project Documentation Pattern

Each project artifact should identify:

- **Objective:** what operational requirement, support workflow, or infrastructure scenario the file addresses.
- **Technical areas covered:** Windows administration, Microsoft 365, Active Directory fundamentals, PowerShell, DNS/DHCP, VLANs, pfSense, Proxmox, backup/recovery, monitoring, ticket triage, RCA, validation, or documentation.
- **Implementation or workflow:** the steps performed, configuration logic, troubleshooting path, change sequence, or runbook procedure.
- **Validation or verification:** how syntax, connectivity, service health, restore integrity, documentation quality, or rollback readiness is checked.
- **Associated proof:** the diagram, script, log, checklist, runbook, CSV, JSON, or report that supports the summary.

The project evidence library is preservation-first. Canonical proof should be selected carefully, while archive and generated variants remain traceable until reviewed.

Future project evidence should be copied in small reviewed batches and validated after each batch.