About · Transparency

Disclosure & Critical Making

This ePortfolio was co-created with an AI system. In the spirit of the disclosure it asks of its own students, here is an honest account of how it was made — and with which tools.

Human Author
Vee Kennedy
AI Collaborator
Claude Opus 4.8
Environment
Claude Code
Hosting
GitHub Pages
The Disclosure, Plainly

This website was designed and built by Vee Kennedy in collaboration with Claude Opus 4.8 (Anthropic's large language model, claude-opus-4-8), working in Claude Code. Kennedy set the direction, supplied the source materials, and made the editorial decisions; Claude wrote the site's code and drafted its connective copy from those materials. The project is versioned and published with GitHub.

Every teacher who assigns disclosure should be willing to practice it. The teaching philosophy on this site argues that any use of generative AI “must be attributed and its output verified, exactly as we attribute and verify any other source.” The signature assignment requires students to “disclose all GenAI use” — even when they use none. This page holds the portfolio itself to that same standard.

What This Page Is

Critical making.

Critical making treats building something as a way of thinking — the act of construction becomes an occasion to reckon with the tools, and the politics, behind it.

Building this ePortfolio was itself a small act of critical making. A site about teaching rhetoric at the meeting point of writing and technology was assembled using the very kind of AI tool the course asks students to examine. That is not a contradiction to hide; it is the material to think with. Naming what the machine did, what a person directed, and where judgment stayed human is the whole exercise — the same critical attention the philosophy brings to reading a large language model “the way d'Ignazio and Klein read a dataset: to ask what it was trained on, whose language it treats as standard, whom it renders invisible, and who profits.”

The author takes up this thread — and what it means that a portfolio like this now comes together in a handful of commits — in the written reflection on the home page.


Division of Labor

Who did what.

A collaboration is only honest if the roles are legible. Here is the split.

Directed by Vee Kennedy

  • Chose the three source documents and the scope of an ENC 6813 ePortfolio.
  • Set the design direction: a technology theme, primarily purple, a clean layout.
  • Set the hard constraint — content drawn only from the three documents, no outside sources.
  • Authored the underlying teaching materials themselves: the philosophy, the syllabus, and the assignment.
  • Reviewed each draft and directed the revisions — including the creation of this page.
  • Holds final editorial judgment and publishes the site via GitHub.

Produced by Claude Opus 4.8

  • Extracted and read the three source documents (PDF and DOCX).
  • Designed and wrote the site's HTML, CSS, and JavaScript — framework-free.
  • Drafted the connective copy and section summaries from the source materials.
  • Recreated the two example posters as on-page HTML (originally AI-generated teaching samples).
  • Built the responsive layout, the light/dark theming, and the interactions.
  • Verified rendering and links in a local preview before hand-off.
Tools & Stack

What it was built with.

AI

Claude Opus 4.8

Anthropic's model claude-opus-4-8 — the collaborator that designed and wrote the site.

Environment

Claude Code

Anthropic's agentic coding tool, where the reading, writing, and previewing took place.

Version Control

GitHub

Hosts the repository crispy-chainsaw-6813eportfolio and publishes the site through GitHub Pages.

Publishing

GitHub Desktop

Used by the author to review the changes and push commits to GitHub.

Front End

HTML · CSS · JavaScript

Hand-authored, with no framework or build step. Type set in Space Grotesk, Inter, and JetBrains Mono via Google Fonts.

Extraction

pdftotext & unzip

Command-line tools used to pull the text out of the source PDF and DOCX files so their content could be read.


The Prompt Log

The specific prompts.

The instructions that produced this site, reproduced as given and lightly trimmed for length (marked with …). Routine messages are summarized at the end.

Prompt 01 · Create the ePortfolioVee Kennedy
Claude, my friend, this repository contains three files: a course syllabus for ENC 3375 at UCF in Fall '26 (Rhetoric in Pop Culture: Anime), a teaching philosophy statement, and a signature assignment for ENC 3375 where students are asked to take a stake in a debate about the proliferation of GenAI tools in the Japanese animation industry. Create an ePortfolio website for ENC 6813: Interdisciplinary Teaching that showcases these three deliverables. I'd like the website to have a technology theme and be primarily purple. Do not pull from any other web sources or prior sessions, only these three documents. The layout for the site should be clean. If you cannot push to the github server directly, save the files locally in crispy-chainsaw-6813eportfolio.
Prompt 02 · Disclose & reviseVee Kennedy
This is a good first draft, Claude. I'd like you to be more transparent about the fact that this was co-created with Claude Opus 4.8. Add an about page entitled "Disclosure & Critical Making" that details the creation of this ePortfolio and the tools used, including GitHub and Claude. Include my specific prompts, where sensible. Additionally, I have some smaller revisions. First, please take care of that typo on philosophy.html — that stray "'s" should not be here. Reorder the header so that "Syllabus" comes first, then "teaching philosophy," then "signature assignment," with the AI disclosure page coming last. On the front page, the button that reads "read the philosophy" should instead state "Teaching Philosophy." Remove the "Teaching Approach / Four convictions that travel across courses…" window from the front page. Instead, reserve this space for a written reflection (which I will add manually later). Make sure that the text space in this area is scrollable in case the reflection runs long; it will probably be in the ballpark of 1000 words. Do not draft this reflection; I will do this myself.
Prompt 03 · Add the reflectionVee Kennedy
Add this text to the reflection space. Once you've added it, don't push the file yourself — I'll do this manually, just update the file. You can also update the Disclosure page. Here's your update: […the written reflection now shown on the portfolio home page…]
Also in the sessionProcess notes
A couple of routine “continue where you left off” resumptions followed sleep interruptions, and the author chose to commit and push each round by hand from GitHub Desktop — a direct push from the tooling had been declined by GitHub's authentication.

Provenance of Content

Where the words came from.

  • All substantive content is drawn from the three source documents Vee Kennedy authored.
  • The teaching philosophy statement appears in Kennedy's own words, reproduced faithfully.
  • The two example posters on the Signature Assignment page were generated with AI assistance as classroom teaching samples — disclosed there and here.
  • No outside web sources or prior AI sessions were used, per the original brief.
A Note on Verification

The course's own policy warns that AI research claims must be double-checked “for hallucinations.” The same applies here: the AI's output is a draft, not the final word. The human author checks it against the source documents, keeps editorial control, and is the one who decides what gets published.