Case Studies
Enterprise evidence, condensed.
Problem, strategy, validation, and boundary are kept consistent so reviewers can compare work quickly.
Review model
How to read a case study here.
Portfolio-safe case studies show architecture judgment without exposing private client code, unsupported metrics, or confidential implementation detail.
Problem what was brittle, ambiguous, or costly to change
Strategy modernization, testing, data, or AI-handoff pattern
Evidence docs, routes, JSON, resume line, or public platform
Boundary what is not claimed or not public
Choose a path
Pick the closest evidence lane.
Cards stay short first; details open only when the problem matches.
Modernization Legacy behavior, SQL-heavy business rules, API boundaries, and test seams.
Frontend architecture TypeScript, Angular, RxJS, UI/API contracts, and service boundaries.
AI workflow Prompt architecture, research indexing, machine-readable handoff, and review checkpoints.
Evidence standard Source-backed status and not-claimed boundaries are visible before deep reading.
Resume Backed Professional Pattern / Enterprise Validated
Enterprise Modernization and Parity Validation
A resume-backed case study for modernizing legacy Web Forms, Classic ASP, and SQL-heavy systems while preserving business behavior through comparison screens, generated scenarios, and test coverage.
Problem Legacy business systems need modernization while preserving behavior embedded in SQL, forms, and old workflow assumptions.
Constraint Modernization must avoid regression in claims, contracts, commissions, logistics, or tax-accounting workflows where behavior matters more than cosmetic rewrites.
Strategy Capture legacy behavior and SQL-side business rules before changing implementation boundaries.
Validation Use behavioral comparison screens, generated scenario tests, automated unit/integration testing, and source review before treating new code as behavior-compatible.
ASP.NET Core C# SQL Server T-SQL stored procedures TypeScript Angular
Boundary No private source code, client data, production metrics, or confidential workflows are exposed.
Open case study
Public Platform / Confirmed Experience
UAIX AI Memory Package Wizard
A public-platform case study for AI memory, file handoff, project handoff, and compact AI handoff state mapped to long-term Architecture Notes research.
Problem AI-assisted engineering loses continuity when source files, decisions, constraints, and current state are scattered across chats, one-off notes, and non-reviewable prompts.
Constraint AI-assisted handoff has to be useful to the next reviewer without granting autonomous execution authority or replacing human approval.
Strategy Model handoff files as explicit read-order and approval-boundary artifacts.
Validation Validate JSON exports, mirror alignment, package read order, and generated-needs-review status for safety anchors before release packaging.
UAIX AI handoff AI Memory Project Handoff File Handoff Markdown JSON
Boundary The memory package is a handoff/review system, not a guarantee that every downstream agent preserves truth or has execution authority.
Open case study
Public Platform / Confirmed Experience
LLMWikis Trust-Labeled Knowledge
A public-platform case study for durable AI-ready knowledge systems, trust labels, source boundaries, governance, and retrieval-friendly content design.
Problem LLM-facing documentation can become a flat pile of pages with no source state, claim boundary, or reviewer route for humans and AI evaluators.
Constraint Knowledge pages need source labels, trust state, and claim boundaries so humans and AI reviewers do not treat drafts as verified facts.
Strategy Frame knowledge entries around trust labels, route provenance, and claim boundaries.
Validation Check JSON parse, route index consistency, noindex boundary, and evidence labels before promoting research content into public claims.
LLM Wiki Markdown frontmatter metadata trust labels RAG semantic search
Boundary Scale, deployment internals, and private knowledge-base behavior are not claimed without reviewed source support.
Open case study
Prototype / Technical Review / Design Review
NeuralWikis / LocalEndpoint AI Boundaries
A review-stage prototype case study for Python, MySQL, cognitive packet review, passive validation, and no-execution safety boundaries.
Problem AI agents need useful discovery and memory exchange without broad tool authority, private-network probing, or unreviewed packet adoption.
Constraint AI agents need useful discovery without broad probing authority, unreviewed memory adoption, or private-data access.
Strategy Describe hostile-context and zero-blind-import concepts as reviewable boundaries rather than certification claims.
Validation Validate no private helper mirror, public discovery boundary language, JSON manifests, and noindex utility inventory.
Python MySQL TypeScript JSON metadata validation passive validation memory firewall
Boundary No runtime MCP, private-network probing, autonomous execution, secret handling, or production deployment is claimed by this portfolio package.
Open case study
Reference Architecture / Design Review
Angular / RxJS / Python Service Boundary Architecture
Enterprise Angular/RxJS architecture example with TypeScript DTOs, RxJS data access, Python service boundaries, SSR/SSG, hydration, testing, and security.
Problem Public portfolios and commercial web applications need rich interactivity without sacrificing crawlability, accessibility, or clear API/review boundaries.
Constraint Typed front-end and AI/data workflows must stay crawlable, testable, and reviewable while respecting the source-backed Angular work history.
Strategy Present TypeScript and Angular experience through source-backed route and resume evidence.
Validation Keep professional claims tied to resume lines; label reference architecture separately; validate JavaScript syntax and responsive component behavior.
Modern Angular RxJS TypeScript SSR SSG Hydration OpenAPI
Boundary The Angular/RxJS reference material is not a claim that every current framework pattern was used in each employer system.
Open 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.
Problem Recruiters and technical reviewers need a fast way to map role language to evidence without fake fit percentages or hidden ATS-style scoring.
Constraint Role matching should help recruiters without becoming fake ATS scoring, external tracking, or hidden data collection.
Strategy Keep the matcher optional rather than the dominant homepage surface.
Validation Run JavaScript syntax checks, component QA for menu/tool behavior, and text-extraction scans for concatenated card text.
JavaScript WordPress REST JSON HTML CSS AI memory metadata
Boundary Not an ATS, credential check, hiring guarantee, background check, or external integration.
Open case study
