Evidence
Nothing on this site is published above what its artifact supports. This page is the audit behind that sentence: the grading scheme, the claims that matter, and the ones that were withdrawn.
How claims are graded
| Tier | Means |
|---|---|
| **Verified | document** |
| **Verified | code / run** |
| Automated validation | a check passes without proving a live run |
| Lab | works on my own equipment; numbers describe one machine, one day |
| Self-stated | my own statement, with no document behind it |
| Proposed | designed, not implemented |
Claims and what is behind them
| Claim | Tier | Artifact |
|---|---|---|
| Scaleforce: employed Nov 2023 - Aug 2025; contract from Sep 2025 | Verified | document |
| Ansible estate: 5 roles, 7 playbooks, executable inventory, CI gates that fail the build | Verified | code and local run |
| Edge access, DNS chain with no plaintext fallback, expected-state assertions | Verified | code |
| Incident ownership, escalation point, 24/7 shift-covered service | Self-stated | employer record |
| AWS Solutions Architect - Professional, Oct 2024 → Oct 2027 | Self-stated | LinkedIn certifications; the certificate is not published |
| Terraform / OpenTofu provisioning for Proxmox | Automated validation only | tofu validate and fmt -check pass; no plan, no apply, no state |
| OpenWrt control plane, VLAN segmentation, generated nftables policy | Proposed | Design documents only; the live LAN is one flat subnet |
| Self-hosted inference latency | Lab | Measured on one host on one day; re-measured before any figure is quoted |
What is not claimed
Stated plainly, because a portfolio that only lists what it can prove is more useful than one that overstates:
- No Kubernetes certification. The CKA was never sat.
- No pager rota, on-call rotation or change ownership. What is evidenced is incident ownership, escalation, and a shift-covered 24/7 service.
- No “sole owner” of an employer estate. The only “sole” in the record is sole trader, a contracting status.
- No percentage outcomes. Figures such as −40 % downtime or −50 % deployment time have no measurement behind them, so none are published.
- No user counts or ticket volumes. The two figures in circulation conflicted by a factor of seven.
- No professional Terraform experience. Lab level: validation passes, nothing has been applied.
- No multi-data-centre operations claim. The platform spans two data centres; operating both sites personally is a different claim and is not made.
- No cellular alerting path. No such configuration exists in the estate.
If a claim anywhere on this site is not traceable to an artifact, that is a defect, and the fix is the claim, not the ledger.
- Ansible CI estate: Five roles, seven playbooks and an executable inventory, with validation that fails the build.
- Ariadne: CV parsing research and a parser spine: A dependency-free Python parser that reports what the extraction lost, with typed failure codes, beside a research corpus where every claim carries a source id and a grade.
- Edge router and DNS controls: Tunnel-based access with internal services kept private, expected-state assertions with a drift check, and a DNS chain with no plaintext fallback.
- MCP Gateway (AI Agent Tool Bridge): A bridge exposing internal services (GPU inference, RAG memory, Docker, browser, search, host status) as standardized MCP tools behind one authenticated endpoint.
- Portfolio pipeline: The delivery path that builds this site: a private source repository, two fail-closed character gates, a Hugo build in GitHub Actions, and a one-way publish to GitHub Pages.
- Proxmox VE estate: VLAN-aware bridges, isolated guest bridges, SDN/VNet isolation and firewall-path audits on a self-directed estate.