Case Studies
Published research and practice-based examples, grouped by research area.
01 · AI ethics, governance & provenance
01.1 · Provenance in AI-mediated knowledge
How source discovery, curation, human contribution and attribution can remain visible when research passes through automated systems.
The case examines both technical and governance questions: what should be recorded, who receives credit, and how a later reader can reconstruct the chain from original source to machine-assisted synthesis.
02 · Sustainable infrastructure
02.1 · London Smart Piezoelectric Flooring Pilot
A proposed London pilot combining kinetic energy harvesting, AI-optimised infrastructure and public-space design, published on Zenodo.
The case joins engineering feasibility with accessibility, ESG, public engagement, governance and urban systems rather than treating renewable technology as an isolated device problem.
View the paper →04 · Technical and professional systems
04.1 · AV reliability, latency & intelligent tracking
Professional audiovisual environments provide a concrete way to study reliability, failure modes, automation, human oversight and the difference between nominal specification and real performance.
05 · Heritage, archives & historical method
05.1 · Two-corridor genealogy and evidence grading
The Heritage project compares Ghanaian Ga-Dangme family research with English biological and adoptive-family records while keeping biological descent, legal adoption, collateral connection and community belonging distinct.
It also tests an evidence scale—documented, highly probable, probable, plausible, unresolved or contradicted—so incomplete records are neither exaggerated nor discarded prematurely.
Tottenham Hotspur: AV testing, user training & operational readiness
Scope and responsibilities
In my AV engineering lead work, I supported integrated meeting-room and audiovisual systems through setup, installation checks, functional testing, commissioning/UAT-related activity, troubleshooting and ongoing support. I used third-party schematics to understand equipment relationships and connectivity, alongside manuals and research into equipment types, functions, features and navigation.
Testing and practical problem-solving
Much of the work involved routine functionality and setup issues. I used equipment documentation, system knowledge and practical trial-and-error testing to identify working configurations and resolve problems, often through toggling settings or resets. I also provided user familiarisation and training across the equipment ranges.
Interface development
A touchscreen graphical user interface required programmatic adaptation during the development lifecycle. This example records the adaptation requirement within the work; it does not assign personal authorship of the programming.
QA reporting and outcome
After tests, I reported QA results to confirm whether rooms and equipment were fully installed, tested and ready for use. The professional contribution was practical verification and communication of readiness, alongside helping people operate the systems.
Evidence and relevance
The supplied Tottenham schematics document integrated AV configurations. Third parties produced the drawings and the handwritten annotations are not mine. My account describes how I used the documentation in engineering practice; the drawings alone do not establish individual test results. This experience illustrates schematic interpretation, systems understanding, functional assurance, issue resolution, technical research, training and readiness reporting—capabilities relevant to technology assurance, operational governance and responsible adoption.
Professional capability map · CESI: capability, opportunity and recognition
Account clarified . Source basis: personal account and supplied third-party technical schematics.
Practice example: evaluating an AI automation supplier
· Independent enterprise evaluation
Question
What evidence would be needed to assess whether a proposed AI automation platform was suitable for the intended business use?
My contribution
I participated in a supplier demonstration, questioned the distinction between autonomous agents and predefined workflows, and examined third-party dependencies, integrations, access controls, scalability, costs, testing and human oversight. I developed a structured technical due-diligence questionnaire and prepared follow-up correspondence to obtain written clarification.
Judgement demonstrated
I treated demonstration claims as matters to verify before making implementation commitments. The questionnaire connected technical questions to business decisions about reliability, security, operating costs and approval boundaries.
Recorded output and outcome
A questionnaire was created and a follow-up email draft prepared. The published activity record records the draft as unsent. Written supplier responses, technical validation, procurement approval and implemented safeguards are not established by this example.
Relevance to professional roles
The example demonstrates structured inquiry, supplier evaluation, risk identification and communication relevant to responsible AI adoption and governance support. It can be assessed alongside my earlier institutional and operational work when considering role-specific requirements.
Dated activity and output record · Capability-to-requirements map · CESI interpretation
Case-study standard
Each case should identify the question, evidence base, stakeholders, technical or institutional mechanism, competing interpretations and current status. Where a conclusion is disputed, the page should describe why one interpretation is more or less likely on the current evidence rather than disguising uncertainty.
Longer papers, diagrams, code, media or source registers can then sit behind the case summary without turning this landing page into a wall of text.