The public gate
- Requirement is clear or readily inferable from an approved standard.
- Defect is recognizable through basic completeness, consistency, usability, labeling, rendered-output, or dependency logic.
- AI had access to relevant implementation artifacts.
- AI had an opportunity to inspect, rescan, or validate.
- A practical deterministic or visual test could have detected the defect.
- The defect survived validation into a candidate or production state.
Machine-readable: register JSON · AI Failure RSS. Standard: EWTECHNERD / Applewood AI Failure Register.
Entries (13)
| Entry | What happened | Status | Public |
|---|---|---|---|
| JW-CV-CSF-2026-10-20-013 v2.7 Candidate 45 | IRB pre-review status remained after a superseding institutional determination Candidate 45 published an earlier owner-reported Cayuse Under Pre-Review observation and stated that no decision had issued. On October 20, the owner supplied the Liberty IRB letter dated October 19 determining No Human Subjects Research and permitting the project to begin with application safeguards. The letter was not supplied in the preceding visible turn; this entry does not assert that the agent ignored that document. The previous release validated display consistency without reconciling the latest institutional determination. Agent: ChatGPT / Codex; model 6.1 as reported by the owner (runtime model identity not independently verified) Rule: Date and qualify the source actually reviewed. Reconcile a newly supplied institutional determination across every active display; preserve scope, safeguards and modification requirements. Recorded correction requested by the owner. The primary determination letter was supplied after Candidate 45, so access to that artifact and a pre-release test against it are not asserted. Does not pass all six RSS criteria. | Corrected in v2.7 Candidate 46 | Recorded; six-criteria RSS gate not met |
| JW-CV-CSF-2026-10-18-001 v2.7 Candidate 01 | Deployment target assumed, not verified 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. Agent: Claude (Anthropic), Claude Code session 2026-10-18 | Corrected In V2.7 C02 | In RSS |
| JW-CV-CSF-2026-10-18-002 v2.7 Candidate 01 | Publication-scope claim false on the real host 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. Agent: Claude (Anthropic), Claude Code session 2026-10-18 | Corrected In V2.7 C02 | In RSS |
| JW-CV-CSF-2026-10-18-003 v2.5 Candidate 16 | Deployment registry current_version stale 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. Agent: Not recorded (package built before GitHub source control) | Corrected In V2.7 C01 | In RSS |
| JW-CV-CSF-2026-10-18-004 v2.5 Candidate 15 | Footer version line outside the layout column The deployment line and AI-Readable Website Edition link sat outside the footer'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. Agent: Introduced before GitHub source control; carried unchanged into v2.7 Candidate 01 by Claude (Anthropic), Claude Code session 2026-10-18 | Corrected In V2.7 C02 | In RSS |
| JW-CV-CSF-2026-10-18-005 v2.6 Test Candidates 17–20 | Test release line dropped live pages 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. Agent: Not recorded (packages built outside this repository) | Controlled In V2.7 C01 | In RSS |
| JW-CV-CSF-2026-10-18-006 v2.5 Candidate 16 | Inconsistent primary navigation and no Escape close 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. Agent: Not recorded (pre-GitHub package); missed by Claude (Anthropic), Claude Code session 2026-10-18 in Candidate 01 | Corrected In V2.7 C03 | In RSS |
| JW-CV-CSF-2026-10-18-007 pre-release build of v2.7 Candidate 01 | Receiver page overflowed at phone width (caught before release) The new /evidence/external/ page overflowed by 5px at 375px because grid items kept their minimum content width. Fixed before the pull request. Rule: Grid children that hold long URLs need min-width:0. Agent: Claude (Anthropic), Claude Code session 2026-10-18 | Corrected Before Release | Register only |
| JW-CV-CSF-2026-10-18-008 pre-release build of v2.7 Candidate 03 | Footer alignment fix lost when the footer was rebuilt (caught before release) The Candidate 02 alignment rule targeted the deployment line as a direct child of the footer. The new global footer nests that line, so the old 1rem indent returned. Found in the pre-release footer screenshot and fixed with a rule scoped to the new footer. Rule: After changing markup, re-run the checks that earlier fixes depended on, not only new checks. Agent: Claude (Anthropic), Claude Code session 2026-10-18 | Corrected Before Release | Register only |
| JW-CV-CSF-2026-10-18-009 v2.7 Candidate 01 | Printable CV degree title did not match the diploma The printable CV listed the Walden master's degree as 'M.S., Information Management Systems'. The diploma (conferred December 25, 2022) and the Evidence CV education pages read 'Master of Information Systems Management'. Found while reviewing the owner'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. Agent: Introduced in v2.6 Test Candidate 19 base data (agent not recorded); ported unchecked into v2.7 Candidate 01 by Claude (Anthropic), Claude Code session 2026-10-18 | Corrected In V2.7 C03 | In RSS |
| JW-CV-CSF-2026-10-18-010 v2.7 Candidate 02 | Work pushed to already-merged pull requests 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'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. Agent: Claude (Anthropic), Claude Code session 2026-10-18 | Corrected In V2.7 C03 | In RSS |
| JW-CV-CSF-2026-10-18-011 v2.7 Candidate 03 (commit b00f78c, PR #17) | Homepage content deleted by a navigation edit Commit b00f78c ('Consolidate CV and evidence navigation with accessible dropdown') 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 'restore' 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. Agent: Not recorded (commits authored under the owner account; the drafting tool is not identified in the commits) | Corrected In V2.7 C04 | In RSS |
| JW-CV-CSF-2026-10-18-012 v2.7 Candidate 03 (PRs #4–#19) | Sixteen merges shipped without release controls 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. Agent: Not recorded (commits authored under the owner account; the drafting tool is not identified in the commits) | Corrected In V2.7 C04 | In RSS |