<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jermaine E. Whiteside Evidence CV — AI / Common-Sense Failure RSS</title><link>https://cv.jermainewhiteside.com/ai-failures/</link><description>Public failure records for AI-assisted work on this site. An entry appears only when all six gate criteria are true.</description><language>en-us</language><lastBuildDate>Sun, 18 Oct 2026 07:40:00 -0400</lastBuildDate><atom:link href="https://cv.jermainewhiteside.com/ai-failures/feed.xml" rel="self" type="application/rss+xml"/><item><title>JW-CV-CSF-2026-10-18-012 — Sixteen merges shipped without release controls</title><link>https://cv.jermainewhiteside.com/ai-failures/#jw-cv-csf-2026-10-18-012</link><guid isPermaLink="false">JW-CV-CSF-2026-10-18-012</guid><pubDate>Sun, 18 Oct 2026 13:15:00 -0400</pubDate><category>RELEASE_CONTROLS_SKIPPED</category><description>Pull requests #4 to #19 changed pages, data and print layouts on production without advancing the footer version, adding deployment-history entries or writing a SHA-256 manifest, as AI_DEPLOYMENT_CONTEXT.md requires. Every page kept saying Candidate 03 and the Candidate 03 manifest no longer matched the served files. Three new pages (Grant Biosketch, Executive Supplement, Course Register) had no deployment footer. Rule: Any merge that changes served files advances the release: footer, deployment history, release notes and manifest.</description></item><item><title>JW-CV-CSF-2026-10-18-011 — Homepage content deleted by a navigation edit</title><link>https://cv.jermainewhiteside.com/ai-failures/#jw-cv-csf-2026-10-18-011</link><guid isPermaLink="false">JW-CV-CSF-2026-10-18-011</guid><pubDate>Sun, 18 Oct 2026 13:10:00 -0400</pubDate><category>PAGE_CONTENT_TRUNCATED_BY_PARTIAL_EDIT</category><description>Commit b00f78c (&#x27;Consolidate CV and evidence navigation with accessible dropdown&#x27;) replaced about 86 lines of index.html with 2, removing the hero, every homepage section and the opening of the footer (17,780 bytes to 5,095). The follow-up &#x27;restore&#x27; commit a81ff98 changed the menu but did not bring the content back. The broken page was served at /index.html; the bare domain root was still answered by the legacy Worker route, which hid the problem. Rule: After any edit, compare page size and structure (header, main, footer present) against the previous version before merging.</description></item><item><title>JW-CV-CSF-2026-10-18-010 — Work pushed to already-merged pull requests</title><link>https://cv.jermainewhiteside.com/ai-failures/#jw-cv-csf-2026-10-18-010</link><guid isPermaLink="false">JW-CV-CSF-2026-10-18-010</guid><pubDate>Sun, 18 Oct 2026 10:20:00 -0400</pubDate><category>POST_MERGE_PUSH_REPORTED_AS_IN_REVIEW</category><description>Commits were pushed to the branches of jermainewhiteside-cv PR #2, ewtechnerd-corporate PR #6 and evision-business-center PR #4 after the owner had merged them, and were reported to the owner as part of those pull requests. They never reached production. Found when the owner&#x27;s screenshot showed zero open pull requests on ewtechnerd-corporate. Rule: Before every push, read the pull request state. If it is merged or closed, start a new branch and a new pull request, and say so.</description></item><item><title>JW-CV-CSF-2026-10-18-009 — Printable CV degree title did not match the diploma</title><link>https://cv.jermainewhiteside.com/ai-failures/#jw-cv-csf-2026-10-18-009</link><guid isPermaLink="false">JW-CV-CSF-2026-10-18-009</guid><pubDate>Sun, 18 Oct 2026 08:45:00 -0400</pubDate><category>CREDENTIAL_TITLE_MISMATCH_ACROSS_SURFACES</category><description>The printable CV listed the Walden master&#x27;s degree as &#x27;M.S., Information Management Systems&#x27;. The diploma (conferred December 25, 2022) and the Evidence CV education pages read &#x27;Master of Information Systems Management&#x27;. Found while reviewing the owner&#x27;s diploma on 2026-10-18. Rule: Any degree, credential or date shown on more than one surface must match the governing evidence record exactly before release.</description></item><item><title>JW-CV-CSF-2026-10-18-006 — Inconsistent primary navigation and no Escape close</title><link>https://cv.jermainewhiteside.com/ai-failures/#jw-cv-csf-2026-10-18-006</link><guid isPermaLink="false">JW-CV-CSF-2026-10-18-006</guid><pubDate>Sun, 18 Oct 2026 07:35:00 -0400</pubDate><category>NAVIGATION_SET_INCONSISTENT</category><description>A 375px menu test of all pages found /publications/ with 7 primary links (no Applied or Evidence CV) and /deployments/ with 10, while other pages had 9. The menu did not close with Escape on any page. Rule: Primary navigation is one canonical list on every page; an open menu closes with Escape and returns focus to its button.</description></item><item><title>JW-CV-CSF-2026-10-18-005 — Test release line dropped live pages</title><link>https://cv.jermainewhiteside.com/ai-failures/#jw-cv-csf-2026-10-18-005</link><guid isPermaLink="false">JW-CV-CSF-2026-10-18-005</guid><pubDate>Sun, 18 Oct 2026 07:30:00 -0400</pubDate><category>RELEASE_LINE_DIVERGENCE</category><description>The v2.6 test packages were built from v2.4 and lacked /applied/, /evidence-cv/, /deployments/ and /orcid/, which were live in v2.5 Candidate 16. Deploying Candidate 20 would have removed them. Found on 2026-10-18 before any v2.6 deployment. Rule: Before promoting a package, diff its route list against the live site and stop on any missing route.</description></item><item><title>JW-CV-CSF-2026-10-18-004 — Footer version line outside the layout column</title><link>https://cv.jermainewhiteside.com/ai-failures/#jw-cv-csf-2026-10-18-004</link><guid isPermaLink="false">JW-CV-CSF-2026-10-18-004</guid><pubDate>Sun, 18 Oct 2026 07:25:00 -0400</pubDate><category>FOOTER_VERSION_LINE_OUTSIDE_LAYOUT_COLUMN</category><description>The deployment line and AI-Readable Website Edition link sat outside the footer&#x27;s 1120px column and rendered at the far left on desktop. The owner found it from a screenshot. Candidate 01 copied the footer markup unchanged although its pages were screenshotted before release. Rule: Release screenshots must include the footer at desktop width, and every footer line must share one left edge.</description></item><item><title>JW-CV-CSF-2026-10-18-003 — Deployment registry current_version stale</title><link>https://cv.jermainewhiteside.com/ai-failures/#jw-cv-csf-2026-10-18-003</link><guid isPermaLink="false">JW-CV-CSF-2026-10-18-003</guid><pubDate>Sun, 18 Oct 2026 07:20:00 -0400</pubDate><category>CURRENT_VERSION_ALIAS_STALE</category><description>deployments/registry.json kept current_version at Candidate 15 while the footer, manifest and AI context all said Candidate 16 was live. Rule: Every current-version field must equal the release named in the footer before a package ships.</description></item><item><title>JW-CV-CSF-2026-10-18-002 — Publication-scope claim false on the real host</title><link>https://cv.jermainewhiteside.com/ai-failures/#jw-cv-csf-2026-10-18-002</link><guid isPermaLink="false">JW-CV-CSF-2026-10-18-002</guid><pubDate>Sun, 18 Oct 2026 07:15:00 -0400</pubDate><category>PUBLICATION_SCOPE_CLAIM_FALSE_UNDER_ACTUAL_HOST</category><description>The Candidate 01 manifest and release notes said repository tooling was excluded from publication through .assetsignore. Cloudflare Pages does not read .assetsignore, so automation/, tools/ and .github/ were published. No secrets were exposed. Rule: State what a host publishes only after fetching a file that should be excluded from the deployed URL.</description></item><item><title>JW-CV-CSF-2026-10-18-001 — Deployment target assumed, not verified</title><link>https://cv.jermainewhiteside.com/ai-failures/#jw-cv-csf-2026-10-18-001</link><guid isPermaLink="false">JW-CV-CSF-2026-10-18-001</guid><pubDate>Sun, 18 Oct 2026 07:10:00 -0400</pubDate><category>DEPLOYMENT_TARGET_ASSUMED_NOT_VERIFIED</category><description>Candidate 01 recorded Worker jermaine-whiteside-cv and Workers Builds as the deploy path without checking which Cloudflare project held cv.jermainewhiteside.com. AI_DEPLOYMENT_CONTEXT.md already warned that production and the jw-certified-cv Pages project had diverged. After merge, jw-certified-cv published Candidate 01 at jw-certified-cv.pages.dev while the custom domain still served v2.5 Candidate 16. The owner moved the custom domain to jw-certified-cv. Rule: Before naming a deploy target, read which project holds the custom domain. After every deploy, check the footer on the custom domain itself.</description></item></channel></rss>
