# Michael Kappel Public Contact and Technical Profile Source Notes

Updated UTC: 2026-06-26T00:00:00Z

## Purpose

This source note preserves the public crawl synthesis used to add the ModelBreeder.com footer contact route and the detailed contact/about page for Michael Kappel. It is long-term source memory for the plain PHP site. Active project memory points here from `.uai/contact-source-synthesis.uai` and `.uai/long-term-memory.uai`.

## Source URLs reviewed

- https://mikekappel.com/
- https://mikekappel.com/resume/
- https://mikekappel.com/career/
- https://mikekappel.com/experience/
- https://mikekappel.com/projects/
- https://mikekappel.com/contacts/
- https://mikekappel.com/dotnet-sql-modernization/
- https://mikekappel.com/angular-python-architecture/
- https://mikekappel.com/nuget-packages/
- https://mikekappel.com/ai-memory-handoff/
- https://mjk.tel/
- https://github.com/MichaelKappel
- https://www.nuget.org/profiles/Michael.Kappel
- https://www.flickr.com/photos/m-i-k-e/

## Public contact facts

- Name: Michael Kappel.
- Primary professional identity: Senior Software Engineer / Software Architect.
- Location listed publicly: Cicero, Illinois.
- Primary email listed publicly: mike@ns12.com.
- Primary phone listed publicly: (630) 362-7576.
- Additional mjk.tel phone entries: (215) 808-2023 and (464) 274-1476.
- Signal username listed on mjk.tel: Mike.7576.
- Professional links include LinkedIn, GitHub, NuGet, MikeKappel.com, MichaelKappel.com, MichaelJosephKappel.com, and mjk.tel.
- Social and creative links from mjk.tel include X, Facebook, Flickr, and Instagram.

## Technical profile synthesis

Michael Kappel's public portfolio presents him as a senior enterprise software engineer and software architect with 20+ years of delivery across Microsoft-platform modernization, SQL-heavy business systems, TypeScript/Angular front ends, and human-reviewed AI-assisted engineering.

The strongest technical credibility signals for ModelBreeder.com are:

1. Enterprise modernization under constraints: legacy Web Forms, Classic ASP, stored procedures, undocumented business rules, parity checks, service seams, regression boundaries, and maintainable migration paths.
2. .NET and SQL Server depth: ASP.NET/Core, C#, Web API, Razor Pages, EF Core, ADO.NET, SQL Server, T-SQL, stored procedures, reporting, Power BI, and DAX.
3. TypeScript and Angular delivery: Angular/TypeScript review applications, Angular/RxJS work, typed DTO/API contracts, route rendering, hydration boundaries, and testable front-end stores.
4. AI-assisted engineering discipline: OpenAI-compatible APIs, LM Studio, prompt systems, semantic search, reviewed AI output, structured documentation, handoff memory, and source-governed publication workflows.
5. Package and runtime evidence: public NuGet package family around UAIX, AI memory, project handoff, adaptive interoperability, ErrorNotifier logging, local LLM runtime abstractions, GGUF/runtime packages, tokenization, tensors, sampling, CPU kernels, and acceleration contracts.
6. Technical mentoring: unit testing, integration testing, SOLID, design patterns, code review, Agile practices, peer programming, and technical specification habits.
7. Creative range: photography and visual composition through MichaelJosephKappel.com and Flickr, supporting the visual and editorial side of technical communication.

## Contact-page editorial angle

The ModelBreeder contact/about page should not be a generic biography. It should explain why Michael's background makes him a credible steward for a site about model breeding:

- Model breeding requires versioned artifacts, lineage, contracts, regression tests, and release discipline.
- Legacy modernization requires preserving behavior while changing structure, which is analogous to adaptive model evolution under constraints.
- AI handoff memory and UAI package work demonstrate durable context, review boundaries, and machine-readable project continuity.
- Local runtime and NuGet package work support the site's emphasis on small, local, interoperable AI systems.
- A footer contact link should give visitors a human route to the creator rather than making the site feel anonymous.

## Claim boundary

Use public portfolio language and publicly listed contact data. Do not invent certifications, employment dates, private client metrics, production access, funding claims, or formal standard conformance beyond what public source pages state.