Contact / About Michael Kappel
Michael Kappel is the technical steward behind Cognivirus.com. This page connects the research site to a named, reachable software architect with public evidence of enterprise modernization, .NET and SQL Server delivery, TypeScript/Angular work, AI-assisted engineering governance, package publishing, and source-bounded technical documentation.
Public identity, engineering history, and evidence routes are kept linked.
This contact page connects the public author profile to the technical evidence surfaces behind Cognivirus: career history, project artifacts, package registries, AI memory work, and public-safe source boundaries.
Kappel contact hub.NET / SQLTypeScript / AngularAI memoryNuGet packagesruntime architectureresearch boundariesvisual systems
Direct contact
Use the concise contact hub when a short list of live contact methods is preferred: mjk.tel.
| Channel | Public detail | Use |
|---|---|---|
| mike@ns12.com | Technical, research, architecture, collaboration, and professional inquiries. | |
| Primary phone | (630) 362-7576 | Direct voice or mobile contact. |
| Alternate phone | (215) 808-2023 | Alternate phone listed by the public contact hub. |
| Additional phone | (464) 274-1476 | Additional phone listed by the public contact hub. |
| Signal | Mike.7576 | Signal username listed by the public contact hub. |
| Location | Cicero, Illinois | Public location shown on the professional portfolio. |
Public profile links
| Surface | Link | What it establishes |
|---|---|---|
| Professional portfolio | MikeKappel.com | Resume-first portfolio, career summary, selected projects, case studies, Architecture Notes, and contact routes. |
| Contact hub | mjk.tel | Concise phone, Signal, personal-domain, and public-profile routing. |
| linkedin.com/in/michaelkappel | Professional profile route. | |
| GitHub | github.com/MichaelKappel | Public code and repository identity route. |
| NuGet | nuget.org/profiles/Michael.Kappel | Public .NET package registry identity. |
| Creative portfolio | MichaelJosephKappel.com | Image-forward photography portfolio and visual composition signal. |
| Personal domain | MichaelKappel.com | Personal-domain routing surface. |
| Flickr | flickr.com/photos/m-i-k-e | Public photo archive and creative systems history. |
| X | x.com/MichaelKappel | Public social profile route listed from the contact hub. |
Why this author page belongs on Cognivirus
Cognivirus.com argues that AI safety has to be evaluated at the level of systems: artifacts, transitions, evidence records, release controls, memory, and rollback paths. That argument benefits from an author who has spent a career working around the same engineering problems in ordinary software systems: preserving behavior while changing implementations, separating public claims from private implementation detail, keeping evidence reviewable, and designing interfaces that operators can actually use.
This page is not an academic credential claim, a standards certification, or a substitute for peer review. It is an accountability surface: visitors can see who is publishing the site, how to reach him, which public professional materials support the technical posture, and where claims are bounded.
Technical position
Michael is presented publicly as a Senior Software Engineer / Software Architect focused on enterprise modernization. His professional portfolio emphasizes business-critical .NET and SQL Server systems, legacy modernization, TypeScript/Angular front ends, and human-reviewed AI-assisted engineering workflows.
The useful signal for Cognivirus is not one tool or framework. It is the pattern across the work:
- Preserve legacy behavior before rewriting visible surfaces.
- Translate undocumented business rules into maintainable service and data boundaries.
- Use tests, comparison screens, generated scenarios, and review checkpoints to avoid regression.
- Keep private client code, proprietary data, production metrics, and confidential workflows out of public claims.
- Treat AI assistance as a reviewed engineering workflow, not autonomous authority.
- Publish machine-readable artifacts only when their boundaries and non-claims remain clear.
Core engineering strengths
| Area | Publicly supported detail | Relevance to this site |
|---|---|---|
| Enterprise modernization | ASP.NET/Core, C#, Web API, Razor Pages, EF Core, ADO.NET, Classic ASP, VB.NET Web Forms, and migration toward maintainable C# MVC/API architecture. | Cognivirus depends on clear distinctions between old behavior, new artifacts, and transition evidence. |
| SQL-heavy systems | SQL Server, stored procedures, transactions, reporting, DAX/Power BI, parity validation, and business-rule translation. | Ecology risk often lives in state transitions and hidden assumptions; SQL modernization builds the same habit of evidence-first change. |
| TypeScript and Angular | Angular/TypeScript AI documentation review work, Angular/RxJS corporate-tax software work, typed UI/API contracts, and current Angular/RxJS architecture patterns. | The site uses browser-side tools and public HTML-first interaction rather than opaque client-only applications. |
| AI-assisted engineering | Prompt contracts, semantic search, machine-readable handoff, AI memory package patterns, and explicit review checkpoints. | Cognivirus is strongest when AI output is treated as evidence to inspect, not authority to obey. |
| Package and protocol thinking | Public NuGet packages for UAI message contracts, memory stores, build support, adaptive interoperability, agent clients, and ASP.NET Core hub patterns. | The site’s .uai memory and source manifests are intentionally dogfooded as inspectable package/handoff artifacts. |
| Visual systems | Public photography archive and image-forward portfolio. | The Cognivirus interface uses schematics and visual flow maps to explain system relationships, not spectacle. |
Public proof surfaces
The professional portfolio identifies several public architecture and project surfaces that are useful context for Cognivirus reviewers:
| Surface | Public framing | Why it matters here |
|---|---|---|
| UAIX.org | UAI-1, AI Memory, Project Handoff, Agent File Handoff, JSON schema discipline, validators, conformance packets, and governance. | Directly relevant to the .uai package memory, source-intake ledger, and handoff design used in this Cognivirus package. |
| LLMWikis.org | Trust-labeled knowledge, metadata, source policy, agent rules, and reviewed knowledge systems. | Supports the site’s source-bound research style and evidence-label discipline. |
| Carcinus.org | Public agent identity, route discovery, publication surfaces, REST-style interfaces, token-protected writes, and SQL-backed state concepts. | Relevant to agent-readable publication boundaries without granting unsafe execution authority. |
| NeuralWikis.com | Python/MySQL cognitive packet exchange, memory firewall, provenance review, quarantine-first handling, and review gates. | Connects to Cognivirus concepts around memory, persistence, behavioral residue, and review before adoption. |
| LocalEndpoint.com | Passive metadata validation and endpoint discovery without runtime execution authority. | Matches the site’s boundary-first model: describe capabilities without exposing uncontrolled action. |
| GGUFRuntime.com | C#/.NET local GGUF runtime roadmap, file verification, model metadata, tokenizer visibility, and runtime evidence states. | Relevant to local model execution, artifact boundaries, and evidence-before-claims runtime design. |
| ARuntime.com | Vendor-neutral AI runtime architecture reference across hardware, kernels, inference engines, serving, browser/edge patterns, and agentic controls. | Gives a public vocabulary for the execution layer between model artifacts and system behavior. |
| MiRuntime.com | Agentic runtime control plane, tools, memory, policy enforcement, approvals, recovery, evidence, and lifecycle boundaries. | Closely parallels Cognivirus’s control-plane paradox and rollback completeness themes. |
| MiRust.com | Rust-oriented machine-intelligence framework and knowledge base for small models, local runtimes, reproducible evaluation, and systems engineering practice. | Relevant to modular small-model and browser/edge execution discussions. |
Work history signal
Public experience material shows a long enterprise delivery timeline across healthcare/dental-insurance systems, market-research collaboration workflows, managed IT/cloud services, logistics and transportation-management systems, fintech savings platforms, financial trading systems, enterprise consulting, ERP/fulfillment systems, public-sector/aviation systems, and early commercial web work.
Important examples include:
- AI-assisted legacy modernization, dental insurance contract-management functionality, claims behavior validation, AWS/MySQL/SQL Server workflows, brokerage commissions, reporting, and mentoring.
- Microsoft Graph API and TypeScript collaboration workflows.
- Azure DevOps, Agile delivery, unit-testability, dependency injection, and TypeScript/QUnit front-end testing.
- Angular/RxJS corporate tax accounting workflows, CI/CD pipeline usage, and automated integration testing generated from stored procedures.
- Transportation management systems, logistics workflows, authorization/security components, SQL Server-backed reliability, RESTful ASP.NET services, MVC controllers, and mentoring.
- Enterprise logistics with ASP.NET MVC, EF, TDD, BDD/Gherkin-style thinking, peer programming, code review, SOLID architecture, and design patterns.
- Migration of a fintech savings platform from VB.NET Web Forms to multi-tier C# MVC architecture on Windows Azure with SQL Azure.
- Trading application work using C#, SQL, XAML/WPF, Prism, Unity Framework, Scrum, and performance-sensitive UI/data patterns.
- Public-sector and aviation-related ASP.NET, JavaScript, XML, SQL Server, Oracle, secure XML-processing, and sensitive-data workflows.
Editorial stance
The author posture for Cognivirus is deliberately conservative:
- Evidence before spectacle.
- System architecture before anthropomorphic language.
- Contactable human stewardship before anonymous authority.
- Public source routes before unsupported claims.
- Clear boundaries around speculation, preprints, private implementation detail, and unverified metrics.
That stance is the credibility argument: Cognivirus is not trying to sound frightening by exaggeration. It is trying to make distributed AI-system risk easier to inspect.
Source basis and limits
This page was synthesized from public Michael Kappel contact and portfolio surfaces. Source notes for this package update are preserved in the local source-review note, while live links remain the current source of truth.
The page does not claim academic affiliation, formal standards approval, security certification, peer-reviewed publication status, or access to private client systems. It presents public profile facts and a bounded technical interpretation of why Michael’s engineering background is relevant to Cognivirus.com.