Positioning scan
Confirm the headline role, strongest proof answer, and exact claim boundary before reading the broader archive.
Portfolio evidence
Human-readable evidence path for resume language, projects, case studies, technical notes, and structured portfolio data.
The evidence map connects resume language to projects, case studies, architecture notes, and structured proof. Reviewers can start with confirmed experience and continue into deeper technical material when needed.
How to review Michael
Choose the right depth before opening the archive.
Use this path to translate claims into routes, data, notes, and explicit non-claims.
Recruiter path
Use the concise resume, current contact path, and role-level experience timeline to qualify fit quickly.
Hiring-manager path
Move from role fit into selected projects and case studies, then inspect the Evidence Map if a claim needs traceability.
Technical architecture path
Inspect Multi-Agent Memory, persistent AI memory, local LLM infrastructure, package evidence, validation, and non-claims.
Machine-readable review path
Use this path for AI agents, answer engines, ATS tools, and structured review without treating hidden files as public claims.
Machine-intelligence claim path
Answer the core proof question directly, then branch into multi-agent systems, AI memory, LLM infrastructure, and Intelligence724 boundaries.
Azure / .NET / SQL path
Confirm the enterprise engineering foundation with role-level Azure usage, .NET/SQL modernization, and conservative evidence boundaries.
Claim to proof matrix
What each major claim proves - and what it does not prove.
This matrix keeps SEO, AEO, GEO, recruiter review, and technical review aligned to the same conservative evidence boundaries.
Machine Intelligence Engineer / Software Architect
Proof: Machine Intelligence overview, proof brief, resume, case studies, and Evidence Map.
Boundary: Does not claim foundation-model training, novel ML research, benchmark leadership, or autonomous systems without human governance.
Multi-agent systems and coordination architecture
Proof: Multi-Agent Systems page, Multi-Agent Memory case study, public repository, companion docs, and evidence brief.
Boundary: Does not claim hosted SaaS, OSI-approved open source, production scale, distributed consensus, model hosting, or automatic conflict-free merging.
Persistent AI memory and handoff
Proof: AI Memory page, AI memory handoff route, persistent memory evidence brief, and .uai handoff records.
Boundary: Does not claim automatic sync, automatic memory promotion, private repository writes, credential access, or runtime orchestration authority.
LLM infrastructure and local runtime tooling
Proof: LLM Infrastructure page, NuGet package profile, package map, and LLM infrastructure evidence brief.
Boundary: Does not claim foundation-model training, public GPU inference benchmarks, or unverified production inference scale.
Azure / .NET / SQL enterprise architecture
Proof: Experience timeline, resume, .NET/SQL modernization route, and Azure evidence brief.
Boundary: Does not infer unconfirmed scale, private infrastructure, certifications, client names, or business outcomes.
Code intelligence and AI-assisted modernization
Proof: Experience page, Intelligence724 public capability surface, and code-intelligence boundary brief.
Boundary: Does not disclose confidential Info724/client systems or claim that Intelligence724 and Info724 are the same legal entity.
Research reports as supporting context
Proof: Reports archive, research search, docs manifest, and curated Architecture Notes promoted after review.
Boundary: Raw reports are not resume claims; sensitive/search-only records stay out of navigation and sitemaps unless searched for.
Plain-language purpose
Use this when a resume claim needs a proof trail.
The page connects a claim to a route, a case study, a note, or a JSON record. Code-like resources stay behind collapsible sections so the human path remains readable.
Human reviewer Start with the resume, experience, and selected case studies.
Technical reviewer Use capability lanes, Architecture Notes, and case-study validation fields.
AI evaluator Use llms-full.txt and public route JSON after reviewing the human pages.
Boundary Research drafts and private helper indexes are not promoted into public proof.
Evidence dashboard
Choose the evidence type before opening dense records.
This responds to the review request for a single coherent evidence entry point while keeping raw reports and private helper data out of public claims.
Review route
Use this page as a guided reviewer map.
Hiring managers can stay on the resume, career, experience, and case-study pages. Technical reviewers can continue into architecture notes and structured data only when they need traceability.
Resume baseline summary
Experience confirmed work history
Projects public proof surfaces
Case studies technical reviewer path
Architecture notes curated detail
Technical appendix structured data
Machine-readable review path
Homepage → Case Studies → Evidence Map → llms-full.txt → route JSON.
This path lets a human reviewer and an AI evaluator move from short public claims to source-backed details without touching private helper files.
Homepage identity, CTAs, skills, case-study entry
Case Studies problem, strategy, evidence, validation, boundary
Evidence Map resume language connected to proof routes
llms-full.txt AI-readable review order and term boundaries
Route JSON public route index and QA contract
Runtime parity
Treat live evidence as current only after version proof.
The evidence map is package-aligned to the current package. A deployed site may lag; confirm route QA or runtime health before citing live pages as current-package proof.
Capability proof
Five major capability lanes.
Each lane has evidence, proof links, display label, and an explicit implementation context.
| Capability | Evidence | Where to review | Evidence label | Reviewer note |
|---|---|---|---|---|
| .NET / SQL modernization | Clean resume baseline, experience page, career map, and modernization role lane. | /career/ /experience/ /dotnet-sql-modernization/ Architecture notes | Enterprise Validated | Public summaries protect private source code, client data, scale details, and proprietary schema. |
| Angular / TypeScript / RxJS | Angular is user-confirmed at Info724 through an AI documentation review app and at LongTerm through corporate tax accounting software; Modern Angular/RxJS material adds current framework fluency for technical reviewers. | /angular-python-architecture/ /case-studies/angular-python-architecture/ Architecture notes Architecture notes /examples/angular22-rxjs-enterprise/README.md | Confirmed Experience | Confirmed Angular delivery is tied to Info724 and LongTerm; Modern Angular/RxJS material communicates current framework fluency. |
| Python AI/data service boundaries | Python is positioned for metadata validation, enrichment, extraction, and evidence-supported AI/data pipeline work. | /python-ai-data-pipelines/ /ai-prompt-architecture/ Architecture notes /examples/angular22-rxjs-enterprise/backend-reference/README.md | Current Architecture Work | Python examples communicate service-boundary patterns, validation, and AI/data workflow design. |
| AI memory / handoff / prompt architecture | UAIX, LLMWikis, AI handoff files, portfolio notes, architecture notes, and quality checkpoints. | /ai-memory-handoff/ /ai-prompt-architecture/ Architecture notes Architecture notes | Confirmed Experience | Memory and handoff artifacts show how context, review, and delivery continuity are organized. |
| Technical mentoring / legacy rescue | Resume-supported mentoring, testing, SOLID, design-pattern, Agile, and modernization work across multiple roles. | /career/ /career-summary/ /experience/ /resume/ | Enterprise Validated | Career evidence stays aligned to reviewed resume and experience material. |
Graph nodes
32 resume, capability, project, docs, structured data and API nodesGraph edges
31 links between resume language and proof surfacesPortfolio notes
19 items awaiting confirmation before stronger wordingPublic routes
29 server-rendered reviewer paths and static data routesEvidence sample
Representative evidence nodes.
The complete graph remains available through structured data and APIs; this route gives reviewers the readable version.
Portfolio Notes
Draft wording and research briefs organized for follow-up.
Technical Exploration means useful direction, not reviewed public fact. Keep these scoped until confirmed.
Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Keep Angular wording tied to confirmed experience and current Angular/RxJS architecture context. Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Research briefs
Research briefs supporting future Architecture Notes.
These briefs keep background research separate from the resume and primary project pages.
Reviewer route appendix
Reviewer route appendix
Primary public routes.
These routes support the site map and link-integrity check.
| Route | Audience | Priority |
|---|---|---|
| Home | all reviewers | 1.0 |
| Career | recruiters and hiring managers | 0.96 |
| AI Resume Guide | resume builders, recruiters, answer engines, and AI evaluators | 0.95 |
| Resume SEO Guide | resume builders and search reviewers | 0.90 |
| Resume AEO Guide | resume builders and answer-engine reviewers | 0.90 |
| Resume GEO Guide | resume builders and generative AI reviewers | 0.90 |
| Portfolio Guide | recruiters, hiring managers, and technical reviewers | 0.90 |
| Resume | recruiters and ATS readers | 0.94 |
| Experience | hiring managers | 0.92 |
| Projects | technical reviewers | 0.90 |
| Case Studies | senior technical reviewers | 0.88 |
| Evidence Map | reviewers and structured screening tools | 0.88 |
| Target Roles | role reviewers | 0.86 |
| Role Guides | recruiters | 0.84 |
| Career Summary | recruiters | 0.82 |
| Role Fit | role reviewers | 0.80 |
| Presentations | public talks reviewers | 0.62 |
| .NET / SQL Modernization | modernization leads | 0.86 |
| Angular / RxJS | front-end reviewers | 0.86 |
| Python AI/Data Pipelines | AI/data reviewers | 0.82 |
| AI Memory / Handoff | AI workflow reviewers | 0.82 |
| AI Architecture | AI architecture reviewers | 0.82 |
| Architecture Notes | technical and agent reviewers | 0.78 |
| Structured Profile | structured screening tools | 0.74 |
| Portfolio Notes | site owner and technical reviewers | 0.66 |
| Career Map | recruiters | 0.70 |
| Industries | domain reviewers | 0.68 |
| Links | ecosystem reviewers | 0.54 |
| Contacts | contact verification | 0.52 |
Reviewer note
How to read this evidence map.
The map connects resume language to proof pages, Architecture Notes, reviewer labels, and structured data so reviewers can trace each claim without treating research drafts as approval.
Enterprise ValidatedFAQ
Common review questions.
Short answers are rendered in the HTML source and mirrored into JSON-LD where appropriate.
What is the portfolio evidence map?
The portfolio evidence map connects public resume language to experience, projects, case studies, Architecture Notes, structured data, and reviewer checkpoints.
What does an evidence or review label mean?
Labels identify the source and review state so a reader can distinguish approved resume facts, public project evidence, technical context, and wording that still requires review.
AI handoff guide
Guiding-principles and safety follow-up packets are copyable.
Mike said the values look good; use the decision page to copy an exact approval, edit, narrowing, replacement, or keep-as-draft decision packet.