Principal-led architecture for critical systems

Evidence library

Evidence is classified before it is evaluated

Filter public records by type, capability, audience, verification status, or keyword. A grouped index remains available without JavaScript.

Evidence libraryRead the label before the story
Purpose
Find records by type, topic, audience, verification status, and decision relevance.
Boundary
The evidence type and limitation are shown first so client work, key-personnel experience, R&D, and demonstrations cannot blur.

Filter evidence

Key-personnel past performancePublicly documented key-personnel background

Enterprise Microsoft systems delivery across rule-heavy domains

Mike Kappel has more than two decades of public professional history delivering and modernizing Microsoft-based enterprise systems across commercial and public-sector contexts.

Boundary: This is key-personnel experience, not LongTermCapabilities corporate government past performance. It does not identify confidential clients or claim unverified metrics.

Open evidence record
Method demonstrationPublic method demonstration

Legacy modernization without behavioral drift

A business-critical .NET and SQL system carries behavior across code, stored procedures, forms, reports, jobs, integrations, and operational workarounds.

Boundary: This is not a named client case study and does not claim that all legacy behavior can be discovered or preserved perfectly.

Open evidence record
Method demonstrationPublic method demonstration

AI evaluation and blocked-action program

An AI reviewer, copilot, or agent produces useful demonstrations, but acceptable failure, human review, and prohibited downstream actions remain undefined.

Boundary: This is an evaluation pattern, not a formal audit, safety certification, or guarantee that a system will be error-free.

Open evidence record
Technical reference architecturePublic reference architecture

Governed knowledge system for internal teams

Policies, SOPs, support notes, tickets, and technical knowledge are fragmented across systems with inconsistent ownership and freshness.

Boundary: This reference architecture does not claim legal certainty, automatic conflict resolution, or universal suitability.

Open evidence record
Public R&D projectPublicly inspectable research artifacts

Governed handoff and machine-readable evidence research

Long-running software and AI-assisted work requires durable handoff records, source boundaries, review status, and public/private separation.

Boundary: Public R&D is not a client engagement, certification, or proof of suitability for a specific regulated environment.

Open evidence record

Key-personnel past performance

Key-personnel past performancePublicly documented key-personnel background

Enterprise Microsoft systems delivery across rule-heavy domains

Mike Kappel has more than two decades of public professional history delivering and modernizing Microsoft-based enterprise systems across commercial and public-sector contexts.

Boundary: This is key-personnel experience, not LongTermCapabilities corporate government past performance. It does not identify confidential clients or claim unverified metrics.

Open evidence record

Method demonstration

Method demonstrationPublic method demonstration

Legacy modernization without behavioral drift

A business-critical .NET and SQL system carries behavior across code, stored procedures, forms, reports, jobs, integrations, and operational workarounds.

Boundary: This is not a named client case study and does not claim that all legacy behavior can be discovered or preserved perfectly.

Open evidence record
Method demonstrationPublic method demonstration

AI evaluation and blocked-action program

An AI reviewer, copilot, or agent produces useful demonstrations, but acceptable failure, human review, and prohibited downstream actions remain undefined.

Boundary: This is an evaluation pattern, not a formal audit, safety certification, or guarantee that a system will be error-free.

Open evidence record

Technical reference architecture

Technical reference architecturePublic reference architecture

Governed knowledge system for internal teams

Policies, SOPs, support notes, tickets, and technical knowledge are fragmented across systems with inconsistent ownership and freshness.

Boundary: This reference architecture does not claim legal certainty, automatic conflict resolution, or universal suitability.

Open evidence record

Public R&D project

Public R&D projectPublicly inspectable research artifacts

Governed handoff and machine-readable evidence research

Long-running software and AI-assisted work requires durable handoff records, source boundaries, review status, and public/private separation.

Boundary: Public R&D is not a client engagement, certification, or proof of suitability for a specific regulated environment.

Open evidence record

Next action

Bring the system, the trigger, and what cannot fail.

Start with public-safe context. Sensitive evidence moves only after fit, responsibility, scope, and an approved channel are clear.

Private local search

Find a service, capability, evidence record, resource, or insight

Press / to open search when focus is not in a form field.

Search runs locally against the public site index.