What is the purpose of the case studies?

Case studies translate resume language into architecture, technologies, architecture notes, and reviewer paths.

Do case studies disclose proprietary implementation details?

They describe architecture patterns and public proof surfaces while protecting private code, secrets, and client-confidential details.

What are the case studies for?

Case studies give technical reviewers a direct path from a resume claim to architecture, evidence stage, related Architecture Notes, and implementation context.

How should strategy-backed case studies be read?

Strategy-backed case studies are presented as architecture background material and refined as implementation details are confirmed.

Which case study should an Angular reviewer open first?

The Angular/Python architecture case study and Angular/RxJS architecture page are the best first path for Angular, TypeScript, RxJS, SSR/SSG, hydration, and testing review.

Case Study / Public Platform / Enterprise Validated

MikeKappel.com Capability Resolver

A public-platform case study for browser-local job matching, alias normalization, evidence cards, proof pages, and claim-boundary warnings.

Portfolio label: Enterprise Validated Evidence category: portfolio-evidence-routing

Problem / constraint

What needed structure

Recruiters and technical reviewers need a fast way to map role language to evidence without fake fit percentages or hidden ATS-style scoring.

Legacy risk

What could regress

Role matching should help recruiters without becoming fake ATS scoring, external tracking, or hidden data collection.

Validation method

How the claim is checked

Run JavaScript syntax checks, component QA for menu/tool behavior, and text-extraction scans for concatenated card text.

Architecture strategy

How the proof is structured.

Architecture evidence is presented with private implementation details abstracted and explicit not-claimed boundaries.

Keep the matcher optional rather than the dominant homepage surface. Explain what pasted text is used for and provide a manual evidence-map fallback. Use bounded client-side scoring and clear labels for reviewer trust. Link matched skills back to route-backed evidence instead of unsupported claims.

Implementation evidence

Homepage Role Matcher states pasted text stays browser-local.
Evidence cards connect role terms to resume, docs, projects, and static JSON.
The resolver avoids fake fit percentages and exposes clarification gaps.

Result / current status

Public portfolio workflow aid; not a hiring guarantee or credential surface.

Technologies

JavaScript WordPress REST JSON HTML CSS AI memory metadata

Technical value

Portfolio as proof system
Evidence-first recruiter workflow
Agent-readable profile design

Not claimed / boundary

No private ATS integration.
No fake fit percentage or hiring prediction.
No external tracking, analytics, or server-side storage of pasted text.

Related architecture notes

/docs/capability-resolver-map.md
/docs/resume-source-map.md
/docs/project-evidence-map.md

Related AI handoff reference

AI handoff memory package

Related static structured data

/case-studies.json
/evidence-map.json

Suggested reviewer path

/
/role-fit/
/evidence-map/
/portfolio-review-guide/
/assets/js/site.js