Fastest written contact route for TinyRustLM project discussion and architecture review.
Contact
Contact Mike Kappel About TinyRustLM
Direct contact page for TinyRustLM project questions, architecture review, Rust/WASM local-model discussion, and software engineering follow-up with Mike Kappel.
Phone
Primary public phone contact from the portfolio and contact hub.
Contact hub
Compact public hub for phone, Signal, personal domains, and social profiles.
Code profile
Public GitHub profile for source and project context.
01
Primary contact route
Use this page for TinyRustLM project questions, browser-local AI runtime review, Rust/WASM architecture discussion, plain PHP site feedback, and collaboration routing. The public contact details mirror Mike Kappel's published portfolio and contact hub information.
- Email: mike@ns12.com
- Phone: (630) 362-7576
- Signal: Mike.7576
- Location: Cicero, IL
02
Professional context
Mike Kappel is presented publicly as a Senior Software Engineer and Software Architect focused on enterprise modernization, .NET and SQL Server systems, TypeScript/Angular front ends, and human-reviewed AI-assisted engineering. TinyRustLM should route technical conversations through that professional engineering context rather than framing the site as a generic AI product contact page.
- Senior Software Engineer / Software Architect
- AI / .NET / SQL / TypeScript
- Legacy modernization and architecture review
- Human-reviewed AI-assisted engineering
03
Public profiles and contact hub
MJK.tel is the compact contact hub for phone, Signal, personal domains, and public profiles. Keep this TinyRustLM page focused on project contact while linking out to the broader contact hub for alternate routes and social profiles.
- Contact hub: MJK.tel
- LinkedIn profile
- GitHub profile
- NuGet package profile
- Photography and public media archive
Plain PHP deployment notes
No WordPress bootstrap, theme system, database requirement, composer package, npm build, CDN script, Bootstrap class dependency, or jQuery dependency.
Routes are handled by index.php and server rewrites. Core content lives in data/pages.php. HTML and Markdown share the same page data.
Upload the package to the subdomain root, point Apache/Nginx to the folder, and keep .htaccess enabled for clean routes on Apache.