Portfolio guide

How to review this portfolio from resume summary to technical evidence.

Start with the human-facing career path, then move into proof only as needed. The primary stack is AI / .NET / SQL / TypeScript. Angular experience, Python service-layer work, Architecture Notes, structured data, and the Research Library remain available for deeper review.

Download 2-page resume Career path Experience Case studies

Runtime parity

Confirm the deployed package before treating live pages as current.

The ZIP package, static JSON files, and deployed WordPress runtime can drift if the package has not been installed yet. Use these checks before citing live behavior.

Version proofOpen /route-qa-contract.json, /research-dashboard.json, or the runtime health endpoint and confirm the current package version.
Human routesAfter version proof, review Career, Experience, Case Studies, Evidence Map, Resume, and Contact in the installed WordPress runtime.
REST routesValidate WordPress REST JSON separately from static files so deployed endpoint behavior is not inferred from package-local validation.
BoundaryIf production reports an older version, document deployment drift and do not claim current-package live QA.
Route QA JSONRuntime health JSONResearch dashboard JSON

Recommended order

Review in five passes.

This keeps the portfolio easy to scan while preserving deeper technical evidence for architecture review.

01Read the resume first

Use the two-page resume as the concise career and stack baseline.

Resume page
02Check career and experience

Confirm chronology, roles, mentoring, Microsoft-stack depth, Angular experience, and CI/CD context.

Experience
03Open target role paths

Use role lanes for .NET / SQL modernization, Angular/RxJS, Python AI/data boundaries, and AI-assisted engineering.

Role paths
04Inspect case studies

Use case studies when a hiring manager or architect needs technical substance behind the resume.

Case studies
05Use evidence and structured data last

Architecture Notes, structured data, and the Research Library are deeper reviewer tools after the resume and experience path.

Structured Profile

Stack priority

Primary stack first, supporting lanes clearly visible.

The site states the center of gravity plainly before deeper project metadata.

Primary stack AI / .NET / SQL / TypeScript
Angular evidence Info724 AI documentation review app and LongTerm corporate tax accounting software.
Python lane AI/data pipeline boundaries, metadata validation, extraction, and service-layer reference patterns.
Architecture proof Projects, case studies, Architecture Notes, and structured portfolio data.

Evidence labels

Plain-English labels used across the site.

Internal verification values remain available in the technical appendix, but human-facing pages use these labels.

Public labelMeaning for reviewersWhere to verify
Enterprise ValidatedStable professional or curated portfolio evidence.Resume, experience, projects, case studies.
Experience ConfirmedDirectly confirmed by Mike or supported by the clean resume baseline.Career, experience, Angular page, resume page.
Current Architecture WorkReference work that shows current architecture thinking and future-facing technical exploration.Architecture Notes, Portfolio Notes, Research Library.
Research LibraryBackground research retained for search, comparison, and deeper review.Research Library and Research Library Search.

Reviewer shortcut

Use the right page for the right question.

Recruiter or hiring manager Resume, Career, Experience, and Target Roles.
Senior technical reviewer Case Studies, Portfolio Evidence, and Architecture Notes.
Angular reviewer Experience, Angular/RxJS Architecture, and Angular case study.
AI architecture reviewer AI Architecture, AI Knowledge Architecture, and reviewed handoff notes.
Research reviewer Research Library Search and Portfolio Notes with clear labels.

Confidentiality and professional presentation

Business-safe proof with private details protected.

The site demonstrates capability through public summaries, selected project surfaces, architecture notes, and structured portfolio data while keeping private source code, client data, credentials, production connection details, proprietary schema, and scale-sensitive details out of the public view.

Structured appendix for ATS, AI-assisted review, and technical screening

These references preserve exact structured data while the page above uses human-facing labels.

Evidence graph data Resume data Research Library Search Portfolio Notes Structured guide data

FAQ

Common review questions.

Short answers are rendered in the HTML source and mirrored into JSON-LD where appropriate.

Where should a recruiter start?

Start with the two-page resume, then use the career and experience pages for context. Projects, case studies, architecture notes, and structured data are available for deeper review.

What is the main technology stack?

The public stack hierarchy is AI, .NET, SQL, and TypeScript. Angular/RxJS and Python remain visible capability lanes with scoped evidence.

How should the Research Library be used?

Research archive material is background context and can inform curated architecture notes after review.

REST contract

v9.0.7 aligns OpenAPI with the fourteen WordPress REST endpoints.

Use these links only after the runtime reports version 9.0.7. Package-local OpenAPI parity does not prove deployed endpoint behavior.

/wp-json/mk/v1/runtime-healthValidate JSON after version proof. /wp-json/mk/v1/route-qa-contractValidate JSON after version proof. /wp-json/mk/v1/report-searchValidate JSON after version proof. /wp-json/mk/v1/reports-searchValidate JSON after version proof. /wp-json/mk/v1/reportsValidate JSON after version proof. /wp-json/mk/v1/report-reader-indexValidate JSON after version proof. /wp-json/mk/v1/report-stale-indexValidate JSON after version proof. /wp-json/mk/v1/research-searchValidate JSON after version proof. /wp-json/mk/v1/research-dashboardValidate JSON after version proof. /wp-json/mk/v1/research-search-performanceValidate JSON after version proof. /wp-json/mk/v1/research-search-shardsValidate JSON after version proof. /wp-json/mk/v1/profileValidate JSON after version proof. /wp-json/mk/v1/resumeValidate JSON after version proof. /wp-json/mk/v1/evidence-mapValidate JSON after version proof.

Reviewer note

Recommended review order.

Start with the resume, career, and experience pages; move into role paths, case studies, Architecture Notes, and research only when deeper technical proof is needed.

Enterprise Validated