DarkMatterDrive.com — ArcSecs Relational Propulsion Atlas DarkMatterDrive.com — ArcSecs Relational Propulsion Atlas

Contact / project credibility

Contact Michael Kappel

DarkMatterDrive.com is published by Michael Kappel, a senior software engineer and software architect with 27 years of production engineering experience. Reach out for questions about the site, ArcSecs-linked research presentation, schema contracts, source maps, technical review, or related software work.

Direct contact

Michael Kappel

Senior Software Engineer / Software Architect

Email
mike@ns12.com
Phone
(630) 362-7576
Location
Cicero, IL
Portfolio
MikeKappel.com

Experience signal

27 years building production software

The contact page intentionally leaves off company names and focuses on durable technical credibility, engineering domains, and public proof surfaces.

Core stack

Microsoft-platform depth

C#, ASP.NET Core, MVC, Razor Pages, Web API, EF Core, ADO.NET, SQL Server, MySQL, SQL Azure, stored procedures, transactions, indexing, and reporting systems.

Delivery

Modernization and validation

Legacy-to-modern translation, zero-regression behavior checks, generated scenario coverage, automated testing, unit testing strategy, and maintainable architecture.

Frontend / contracts

TypeScript and web systems

Strict TypeScript, JavaScript, HTML, CSS, API-backed front ends, public route inventories, JSON contracts, schema surfaces, and reviewer-friendly technical UX.

AI / search

Practical AI integration

OpenAI-compatible APIs, local model workflows, semantic search, prompt systems, source-bound validation, agent workflows, and AI-assisted engineering with review gates.

Why this matters here

Why that background belongs on DarkMatterDrive.com

The project mixes technical publishing, schema contracts, research navigation, visual systems, and validation-first claims. The contact page makes the human owner easier to evaluate without turning the public site into a resume dump.

Site systems

Architecture literacy

The site depends on route discipline, reusable templates, JSON endpoints, public/private content separation, and stable machine-readable contracts.

Evidence surfaces

Data-heavy judgment

The research and evidence pages benefit from SQL-heavy, reporting-heavy, and validation-heavy experience: claims need traceability, not vibes.

Trust posture

AI with guardrails

The project uses AI-assisted iteration, but public claims are kept bounded by source maps, caveats, falsification paths, and validation checks.

Domain background

Business domains without company-name clutter

These are context signals only. They show the kinds of production environments behind the software experience without naming employers or clients on this page.

Insurance, claims, contracts, reporting, provider and brokerage workflows
Logistics, transportation management, routing, shipment lifecycle, and 3PL operations
Market-research collaboration, document workflows, messaging providers, and Microsoft Graph integrations
Managed services, cloud enablement, CI/CD, internal tools, TypeScript adoption, and testing culture
ERP, fulfillment, e-commerce operations, inventory, orders, caching, and high-traffic web systems
Public-sector aviation, sensitive data, permissions, auditability, and regulatory correctness pressure
Fintech, payments, migration planning, cloud-aware architecture, and stakeholder pressure
Financial/trading user interfaces, SQL performance, WPF/XAML, and testable code patterns
Consulting, architecture rescue, legacy system diagnosis, and client-team handoff quality