KillChains.com v1.6.0
Bounded simulation: no real targets, coordinates, casualty models, weapon-performance parameters, executable payloads, or operational attack instructions.

Creator · Software architect · Evidence-led builder

About Michael Kappel

Michael Kappel created and maintains KillChains.com. His professional background combines enterprise software modernization, typed web architecture, automated validation, and human-reviewed AI-assisted engineering.

Site creator20+ years of enterprise software deliveryProfessional bio source-linkedDirect contact

Answer-first summary

Direct answers

Release 1.6.0 · reviewed · evidence states

Who created KillChains.com?

Michael Kappel created and maintains KillChains.com as an evidence-led educational publication and interactive simulation.

Read the supporting section

What is Michael Kappel’s professional background?

He is a senior software engineer and software architect with more than 20 years of enterprise delivery experience, focused on .NET and SQL Server modernization, TypeScript and Angular interfaces, validation, and human-reviewed AI-assisted engineering.

Read the supporting section

How can Michael Kappel be contacted?

Email Michael at Mike@ns12.com or visit MichaelKappel.com. His source-backed professional profile is available at MikeKappel.com.

Read the supporting section

Professional background

Architecture grounded in long-lived systems and reviewable evidence.

Michael Kappel is a senior software engineer and software architect focused on modernizing business-critical .NET and SQL Server systems without losing established behavior. His work also includes TypeScript and Angular front ends, API contracts, automated validation, and human-reviewed AI-assisted engineering workflows.

He created KillChains.com as an evidence-led, interactive way to explain military, cyber, and AI-system kill chains while keeping the simulations synthetic, source-qualified, accessible, and non-operational.

That background shapes the site’s implementation: PHP remains authoritative for scored simulation state, browser interactions are bounded, public claims retain their source class and uncertainty, and every major release is tested and packaged as a root-deployable artifact.

Visit MichaelKappel.com Email Michael Professional profile

Professional focus

Software architecture, modernization, typed interfaces, and human-reviewed AI workflows.

The profile below is a concise, source-bounded summary of the public professional portfolio rather than a complete résumé.

01

.NET and enterprise modernization

C#, ASP.NET and ASP.NET Core, Web API, Razor Pages, service seams, legacy rescue, and maintainable modernization architecture.

02

SQL Server and behavioral parity

SQL-heavy systems, stored procedures, business rules, reporting, comparison workflows, and regression-aware parity validation.

03

TypeScript and Angular delivery

Typed front-end patterns, Angular and RxJS experience, browser-facing interfaces, accessibility-aware UI, and explicit API contracts.

04

Human-reviewed AI engineering

Prompt contracts, semantic search, durable handoff memory, review checkpoints, and AI assistance that remains subordinate to source evidence and human acceptance.

Why KillChains.com

Make the system visible before asking the reader to judge it.

Kill-chain discussions often collapse sensing, classification, recommendation, authorization, engagement, and assessment into one dramatic phrase. The site separates those functions so readers can inspect where information changes, where authority moves, where uncertainty is hidden, and where a defensive or governance control can interrupt the sequence.

The goal is not to celebrate machine speed or condemn automation as a category. It is to give readers a practical way to compare evidence, timing, human control, system boundaries, and counterfactual outcomes.

Project principles

How the author approaches the work

  • Make complex systems understandable through interaction rather than spectacle.
  • Keep real-world claims tied to visible source states, dates, limitations, and unknowns.
  • Use AI as an engineering and research assistant, never as the authority for public fact.
  • Preserve accessibility, responsive behavior, privacy, and non-operational safety as product requirements.

Profile source

MikeKappel.com professional portfolio

Professional title, experience summary, primary engineering focus, public portfolio links, location label, and direct contact email.

Source class
Self-published professional profile
Reviewed
Review MikeKappel.com