Recursive Continuation Prompt — v8.8.18

Full report

On this page

You are continuing the MikeKappel.com improvement loop.

Base package

• Start from: mikekappel-enterprise-ai-prod-theme-v8.8.17.zip
• Read: mk-v8.8.17-change-summary.md
• Read: mk-v8.8.17-validation-report.md
• Read: mk-v8.8.17-live-render-qa.md
• Produce: mikekappel-enterprise-ai-prod-theme-v8.8.18.zip
• Produce: mk-v8.8.18-change-summary.md
• Produce: mk-v8.8.18-validation-report.md
• Produce: mk-v8.8.18-live-render-qa.md
• Produce: mk-v8.8.19-next-prompt.md

Mission

Audit v8.8.17 and implement the next highest-value improvements. Prioritize real deployed/local WordPress browser QA if available, then safety-anchor approval handling only if Mike provides explicit approval language, then selective report-to-doc review drafts, recruiter/career path polish, and performance hardening for /research-search/ and /reports/.

Do not add features blindly. Score remaining opportunities first. Implement only low/medium-risk changes that improve trust, clarity, accessibility, performance, and maintainability.

Non-negotiable rules

• Keep MikeKappel.com server-rendered and crawlable.
• Do not convert the site into a client-only Angular SPA.
• Keep the Angular 22 reference app source-only unless explicitly requested otherwise.
• Do not claim Angular 22 production deployment unless user-confirmed.
• Preserve primary stack hierarchy: AI / .NET / SQL / TypeScript.
• Preserve user-confirmed Angular experience:
• Info724 Angular/TypeScript AI documentation review app for an Info724 client.
• LongTerm Software Angular work on corporate tax accounting software.
• LongTerm CI/CD pipeline usage at the tax-accounting consulting engagement.
• Preserve the clean two-page resume as the primary public website download.
• Do not add the public Full CV back yet.
• Preserve source governance, evidence labels, source status, claim boundaries, docs, .uai memory mapping, static JSON, REST data, role-fit lanes, target-role paths, evidence graph, review queue, reports archive boundaries, cross-search, candidate review packets, and UAI safety anchors.
• Do not automatically promote raw report claims into /docs, resume, project cards, case studies, APIs, or SEO pages.
• Keep /reports/, /report-reader/, /research-search/, /uai-safety-review/, raw report JSON, research-search metadata/shards, candidate packet JSON, safety-anchor utility JSON, and raw report utility surfaces noindex/noarchive/nosnippet.
• Do not add report files, report-reader URLs, research-search utility JSON, candidate packet JSON, safety-anchor utility JSON, or raw report utility files to sitemap.xml.
• Do not add JSON-LD schema to raw report pages, raw research utility pages, or safety-anchor utility pages.
• Do not invent biography, project implementation details, employment history, volunteer work, certifications, dates, client relationships, production status, or runtime architecture.

Safety-anchor approval rule

Read before broad changes:

1. .uai/totem.uai
2. .uai/taboo.uai
3. .uai/uai-safety-anchor-review.uai
4. .uai/totem-taboo-review-workflow.uai
5. .uai/safety-anchor-decision-ledger.uai
6. uai-safety-anchor-review.json
7. safety-anchor-decision-packets.json
8. safety-anchor-decision-ledger.json

Mike previously said the anchors “look good.” Treat this as a positive review signal, not automatic durable approval.

Only promote .uai/totem.uai or .uai/taboo.uai from generated-needs-review to user-confirmed if Mike explicitly provides a decision such as:

Approve .uai/totem.uai as-is and mark it user-confirmed.

or:

Approve .uai/taboo.uai with the following edits...

Forbidden content handling

Raw /reports/ files and report-derived indexes may contain contaminated, speculative, conflicting, or quarantined material. Curated public files outside raw research surfaces must not present blocked terms as approved claims.

Explicit taboo, source-governance, quarantine, and warning files may name blocked terms for blocking purposes. Those files must not present them as approved claims.

Step 1 — audit v8.8.17

Inspect:

• .uai/totem.uai
• .uai/taboo.uai
• .uai/uai-safety-anchor-review.uai
• .uai/totem-taboo-review-workflow.uai
• .uai/safety-anchor-decision-ledger.uai
• uai-safety-anchor-review.json
• safety-anchor-decision-packets.json
• safety-anchor-decision-ledger.json
• /uai-safety-review/
• /docs/
• /ai-memory-handoff/
• /review-queue/
• /evidence-map/
• /career/
• /resume/
• /experience/
• /reports/
• /report-reader/
• /research-search/
• sitemap and noindex handling
• static JSON files
• REST endpoint registration
• CSS/layout
• v8.8.17 validation and render QA reports

Step 2 — score opportunities

Score each candidate 1–5:

• deployed render credibility impact
• SEO impact on primary professional pages
• recruiter/hiring-manager clarity
• senior technical reviewer value
• report-search usability
• cross-search usability
• source-governance value
• safety-anchor review value
• accessibility impact
• visual polish impact
• performance impact
• implementation risk
• maintainability impact

Prioritize:

1. real WordPress render issues;
2. explicit safety-anchor approval if the user provides approval language;
3. source-governance hardening;
4. recruiter/career path polish;
5. selective report-to-doc candidate drafts that remain generated-needs-review;
6. cross-search performance if rendered page is slow.

Recommended work candidates

Choose 3–7 after audit:

• Run deployed/local WordPress browser QA and fix real layout issues.
• If explicitly approved, mark totem and/or taboo as user-confirmed and regenerate manifests.
• If not explicitly approved, keep review workflow and improve clarity only.
• Consider root-level compatibility shims totem.uai and taboo.uai only if Mike requests UAIX root-level compatibility; otherwise keep .uai/totem.uai and .uai/taboo.uai as the authoritative package anchors.
• Improve /career/, /resume/, and /experience/ readability while keeping AI / .NET / SQL / TypeScript first and Angular visible.
• Promote selected report candidates into /docs/ as generated-needs-review summaries only after review.
• Improve /research-search/ metadata-first performance if browser QA shows slow startup.

Validation

Run:

• PHP lint all PHP files;
• JSON parse all JSON/JSON-LD files;
• JavaScript syntax check;
• ZIP integrity check;
• forbidden-claim grep with raw research and explicit taboo/source-governance boundary exclusions;
• resume asset presence check;
• version metadata check;
• noindex check for reports, report-reader, research-search, report JSON, research-search JSON, candidate packet JSON, safety-anchor JSON, and memory-system JSON;
• sitemap omission check;
• docs/.uai mapping check;
• static JSON schema smoke check;
• internal-link smoke check;
• accessibility/layout smoke check;
• live/local screenshot QA where available.

Deliverables

Return:

• mikekappel-enterprise-ai-prod-theme-v8.8.18.zip
• mk-v8.8.18-change-summary.md
• mk-v8.8.18-validation-report.md
• mk-v8.8.18-live-render-qa.md
• mk-v8.8.19-next-prompt.md

Final response format

Use the same Done / Files / Highest-value improvements / Validation / Needs user review / Next recommended focus / Deployment note structure.