/wp-json/mk/v1/profile
Structured identity, contact, roles, and discovery metadata.
Confirm identity, current role framing, and contact surfaces before deeper evaluation.
Structured portfolio profile
A reviewer-friendly profile backed by structured portfolio data.
Technical reviewers, recruiters, and structured screening tools get a clear path from resume language to supporting projects, architecture notes, and structured portfolio data. The human story stays readable while the technical appendix remains available for deeper inspection.
Resume evidence AI / .NET / SQL / TypeScript remains the primary stack.
Architecture notes Curated notes explain reviewer context and review history.
Project proof Projects and case studies provide the visible proof path.
Structured data Structured portfolio exports are available while protecting private systems.
Reviewer path
Start with the resume, then inspect the evidence chain.
Human readers can start with the resume and career pages for the professional story, then use portfolio evidence, case studies, and architecture notes for deeper technical review.
Reviewer note
Structured profile data is available for technical review.
This WordPress portfolio publishes public profile data, evidence summaries, architecture-note links, and safe handoff context while keeping credentials, private repositories, production connection details, and issuer-backed verification outside the public surface.
Structured data appendix
These links are provided for ATS systems and technical reviewers. They preserve exact structured values while the public page uses readable labels.
/wp-json/mk/v1/capabilities
Grouped engineering capabilities with proof signals.
Map job requirements to capability families, especially AI Memory, Modern Angular/RxJS/SEO-first SSR, Python, .NET, and SQL.
/wp-json/mk/v1/projects
Public project atlas with links, descriptions, tags, and project intent.
Use project tags and source notes to connect public proof surfaces to resume language.
/wp-json/mk/v1/evidence-map
Evidence labels and reviewer contexts.
Use before summarizing project claims.
/wp-json/mk/v1/evidence-graph
Static evidence graph linking role targets, resume support, proof pages, docs, and APIs.
Traverse proof relationships without flattening reviewer contexts.
/wp-json/mk/v1/role-evidence
Target-role evidence paths for recruiters and technical reviewers.
Map role intent to resume, docs, case studies, and reviewer contexts before using the resolver.
/wp-json/mk/v1/case-studies
Case study index with reviewer contexts.
Route role-fit claims to specific proof pages.
/wp-json/mk/v1/resume-source-map
Resume claim portfolio notes.
Avoid blocked imported claim categories.
/wp-json/mk/v1/capability-resolver
Resolver aliases, quick-paste roles, and output shape.
Understand local role-fit matching semantics.
/wp-json/mk/v1/graph
Semantic graph connecting skills, projects, roles, and memory concepts.
Build retrieval or graph-RAG context without flattening all domains into one list.
/wp-json/mk/v1/agent-brief
Concise role-fit brief for AI or human triage.
Start here for sourcing, then verify details against resume and project endpoints.
/wp-json/mk/v1/research-docs
/docs research index and long-memory Markdown map.
Find reviewed research notes and strategy documents without reading scattered files.
/wp-json/mk/v1/uai-memory
AI handoff memory package manifest.
Read current handoff context, coding standards, and Architecture Notes pointers.
/wp-json/mk/v1/uai-safety-anchors
AI handoff guiding-principles manifest.
Read guiding principles and guardrails before modifying the site.
/wp-json/mk/v1/memory
Combined AI Memory, project handoff, file handoff, and Architecture Notes resource map.
Use as a single discovery endpoint before reading detailed AI handoff and Architecture Notes files.
/wp-json/mk/v1/industry-context
Industry and domain context kept separate from core technical evidence.
Map healthcare, logistics, market research, fintech, public sector, and managed IT experience to domain fit.
/wp-json/mk/v1/industries
Industry-by-industry experience map.
Summarize domain exposure without overclaiming beyond direct experience.
/wp-json/mk/v1/career-intelligence
Company lineage, current-name mapping, skill acquisition, and same-name disambiguation.
Resolve historical employers, current names, and identity collisions.
/wp-json/mk/v1/links
Public ecosystem link map.
Understand how UAIX, LLMWikis, NeuralWikis, LocalEndpoint, FireAndStorm, Carcinus, and other sites relate to the profile.
/wp-json/mk/v1/company-contacts
Company contact and resume-context directory.
Use for background review routing and employer lineage checks.
/wp-json/mk/v1/reports
Research archive manifest.
Locate research reports while keeping career-facing wording separate.
/wp-json/mk/v1/report-search
Compact search index for the Research Library.
Search report titles, summaries, categories, and condensed report text before opening the archived Markdown source.
/wp-json/mk/v1/reports-search?q=TERM
Filtered report search response for simple clients and AI assistants.
Retrieve a bounded result set without downloading the full local search index.
/wp-json/mk/v1/research-search?q=TERM
Source-labeled cross-search across technical notes, research library entries, portfolio evidence, review decisions, projects, and case studies.
Retrieve mixed-source candidates while preserving Research Library labels and source labels.
/wp-json/mk/v1/report-facets
Report search categories, tags, quick queries, and sort options.
Discover available facets before searching reports.
/wp-json/mk/v1/report-reader-index
Lightweight reader metadata for research note reports.
Map report filenames to reader URLs, raw URLs, summaries, and citations.
/assets/data/verifiable-credential-preview.json
Preview-only credential payload with proof boundaries.
Use as a preview-only credential payload for trust-architecture review.
Profile summary preview
{
"profile": "Michael Kappel",
"roleTargets": [
"Senior Software Engineer",
"Software Architect",
"AI Integration Architect",
"AI / .NET / SQL / TypeScript Architect",
"Modernization Lead",
"Architecture Mentor"
],
"fitSignals": [
"AI Memory and Project Handoff architecture",
"Angular, TypeScript, RxJS, and SEO-first reactive front ends",
"Python AI/data pipelines",
"enterprise .NET architecture",
"legacy modernization",
"AI-assisted engineering",
"semantic search",
"SQL Server/MySQL-backed systems",
"team mentoring"
],
"productionSignals": [
"REST endpoints",
"structured portfolio data",
"semantic graph preview",
"private capability resolver",
"AI handoff memory suite",
"Architecture Notes map",
"agent file handoff buckets",
"industry and soft-skill context kept separate from technical fit",
"career-map lineage intelligence",
"reviewed architecture notes",
"reviewer context labels"
],
"publicProjects": [
{
"ai_signal": "Shows AI work treated as accountable infrastructure: agents can produce and consume structured records, but claims have to survive schemas, validators, route maps, examples, review posture, and explicit non-claims.",
"capabilityTags": [
"UAI-1",
"AI Memory",
"Project Handoff",
"Agent File Handoff",
"JSON Schema",
"OpenAPI",
"Validators",
"Conformance",
"Governance",
"AI Protocols",
"AI Memory Package Wizard",
"Short-Term Memory"
],
"detail": "UAIX is the strongest enterprise-AI project because it turns agent work into a reviewable public exchange contract. The site publishes specification routes, schema records, examples, validator flows, implementation lanes, API/reference inventory, conformance materials, AI Memory package guidance, support-professional context, and a clear separation between runtime protocols and public evidence.",
"evidenceLabel": "Public Platform",
"evidenceLabels": [
"Public Platform",
"User-Confirmed"
],
"evidenceLevel": "User-Confirmed",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "UAIX.org",
"professionalContext": "Public platform and AI memory / handoff standards surface.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md",
"Architecture Notes/uai-memory-handoff-map.md",
"Architecture Notes/ai-prompt-architecture.md"
],
"proofs": [
"UAI-1 envelope/profile/trust/provenance/error surfaces",
"AI Memory and Project Handoff package patterns",
"Validator-backed proof path and conformance packet",
"Machine-facing REST/OpenAPI-style discovery and route surfaces",
"The v8.8 site package includes a repository-local AI handoff handoff deck and Architecture Notes long-memory map aligned to UAIX-style handoff terminology."
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md",
"Architecture Notes/uai-memory-handoff-map.md",
"Architecture Notes/ai-prompt-architecture.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Standards architecture, API contract design, JSON schema discipline, validation-first QA, OpenAPI/route inventory thinking, governance, conformance packaging, provenance modeling, async workflow boundaries, trust posture, release discipline, and technical documentation at protocol scale.",
"sourceStatus": "user-confirmed",
"source_note": "Public platform and AI memory / handoff standards surface.",
"source_status": "user-confirmed",
"status": "public-platform",
"summary": "Canonical UAI-1 / AI Memory / Project Handoff / Agent File Handoff standards surface with schemas, validator evidence, implementation tracks, route inventory, conformance records, governance, and memory-package tooling.",
"tags": [
"UAI-1",
"AI Memory",
"Project Handoff",
"Agent File Handoff",
"JSON Schema",
"OpenAPI",
"Validators",
"Conformance",
"Governance",
"AI Protocols",
"AI Memory Package Wizard",
"Short-Term Memory",
"Long-Term Memory",
"File Handoff"
],
"technologies": [
"UAI-1",
"AI Memory",
"Project Handoff",
"Agent File Handoff",
"JSON Schema",
"OpenAPI",
"Validators",
"Conformance",
"Governance",
"AI Protocols"
],
"tier": "top",
"title": "UAIX.org",
"type": "AI interoperability standard",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://uaix.org/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Standards architecture, API contract design, JSON schema discipline, validation-first QA, OpenAPI/route inventory thinking, governance, conformance packaging, provenance modeling, async workflow boundaries, trust posture, release discipline, and technical documentation at protocol scale."
]
},
{
"ai_signal": "Shows AI infrastructure beyond chat: identity, publishing, memory-adjacent artifacts, and reviewable public surfaces that agents can read without receiving unsafe execution authority.",
"capabilityTags": [
"C#",
"ASP.NET Core",
"SQL Server",
"TypeScript",
"REST API",
"Token Auth",
"AI Publishing",
"Agent Identity",
"Markdown Rendering",
"AI Handoff"
],
"detail": "Carcinus is positioned as the infrastructure-scale AI node: public identity, route discovery, site publishing, automatic Markdown rendering, REST-style interfaces, token-protected writes, and SQL-backed state designed for agent-readable publication boundaries.",
"evidenceLabel": "Prototype",
"evidenceLabels": [
"Public Platform",
"Technical Review"
],
"evidenceLevel": "Technical Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "Carcinus.org",
"professionalContext": "Public agent identity / infrastructure-scale concept from strategy direction; treat runtime/database details as review-stage when confirmed.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Promoted from supporting to top proof surface for v8.8.",
"Mapped to AI infrastructure and SQL Server-oriented public agent identity work.",
"Connects to UAIX handoff language and the repository-local AI handoff package."
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "C#, ASP.NET Core, SQL Server architecture, REST contracts, token-backed security, route discovery, public profile surfaces, machine-readable publication, and infrastructure-scale AI systems.",
"sourceStatus": "Design Review",
"source_note": "Public agent identity / infrastructure-scale concept from strategy direction; treat runtime/database details as review-stage when confirmed.",
"source_status": "Design Review",
"status": "prototype",
"summary": "C#/TypeScript/SQL Server-oriented public agent identity and AI publishing infrastructure for discoverable agent pages, publication surfaces, and review-bounded publication workflows.",
"tags": [
"C#",
"ASP.NET Core",
"SQL Server",
"TypeScript",
"REST API",
"Token Auth",
"AI Publishing",
"Agent Identity",
"Markdown Rendering",
"AI Handoff"
],
"technologies": [
"C#",
"ASP.NET Core",
"SQL Server",
"TypeScript",
"REST API",
"Token Auth",
"AI Publishing",
"Agent Identity",
"Markdown Rendering",
"AI Handoff"
],
"tier": "top",
"title": "Carcinus.org",
"type": "Public agent identity / AI publishing infrastructure",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://carcinus.org/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"C#, ASP.NET Core, SQL Server architecture, REST contracts, token-backed security, route discovery, public profile surfaces, machine-readable publication, and infrastructure-scale AI systems."
]
},
{
"ai_signal": "Demonstrates AI-assisted commercial application framing where Python pipelines and Angular interfaces turn domain intake into structured, reviewable, operator-facing outputs.",
"capabilityTags": [
"Angular",
"TypeScript",
"RxJS",
"Python",
"Reactive State",
"Commercial Service App",
"API Integration",
"Asynchronous UI",
"Component Architecture",
"Operational Workflows"
],
"detail": "FireAndStormRestoration is the Angular-first project surface: a service-domain application framed around TypeScript component architecture, RxJS-managed asynchronous state, and Python API/pipeline integration for operational assessment, routing, and service-logistics workflows.",
"evidenceLabel": "Prototype",
"evidenceLabels": [
"Public Platform",
"Technical Review"
],
"evidenceLevel": "Needs User Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "FireAndStormRestoration.com",
"professionalContext": "Angular/Python proof lane supports technical review. Specific Angular version details are included only when confirmed by project metadata.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md",
"Architecture Notes/angular-python-architecture.md",
"/angular-python-architecture/",
"/case-studies/angular-python-architecture/",
"Architecture Notes/angular22-rxjs-enterprise-reference.md"
],
"proofs": [
"Added as the primary Angular / RxJS / Python proof surface.",
"Feeds capability resolver terms such as Angular Components and RxJS State Management.",
"Supports the new resume focus on front-end reactive architecture and Python AI pipelines."
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md",
"Architecture Notes/angular-python-architecture.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Angular component architecture, TypeScript contracts, RxJS state management, asynchronous API UI patterns, Python service integration, and commercial workflow modeling.",
"sourceStatus": "Design Review",
"source_note": "Angular / TypeScript / RxJS / Python proof lane derived from strategy direction; present as Modern Angular deployment context or paid client production work when confirmed.",
"source_status": "Design Review",
"status": "prototype",
"summary": "Angular, TypeScript, RxJS, and Python proof surface for a reactive commercial service application pattern with asynchronous assessment and logistics workflow concepts.",
"tags": [
"Angular",
"TypeScript",
"RxJS",
"Python",
"Reactive State",
"Commercial Service App",
"API Integration",
"Asynchronous UI",
"Component Architecture",
"Operational Workflows"
],
"technologies": [
"Angular",
"TypeScript",
"RxJS",
"Python",
"Reactive State",
"Commercial Service App",
"API Integration",
"Asynchronous UI",
"Component Architecture",
"Operational Workflows"
],
"tier": "top",
"title": "FireAndStormRestoration.com",
"type": "Angular / Python commercial service architecture",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://fireandstormrestoration.com/",
"whatThisDoesNotClaim": [
"Keeps separate from specific Angular versioned deployment code.",
"Keeps separate from paid client production status when confirmed.",
"Keeps separate from private Python implementation details."
],
"whatThisProves": [
"Angular component architecture, TypeScript contracts, RxJS state management, asynchronous API UI patterns, Python service integration, and commercial workflow modeling."
]
},
{
"ai_signal": "The AI skill signal is controlled memory. AI can help inventory, restructure, and summarize, but the site keeps ownership, source labels, review status, stop conditions, and canonical paths visible.",
"capabilityTags": [
"LLM Wikis",
"AI Knowledge Bases",
"Metadata",
"Trust Labels",
"Agent Rules",
"Source Policy",
"Governance",
"RAG Prep",
"Documentation Systems",
"AI Memory",
"Long-Term Memory",
"Reviewed Sources"
],
"detail": "LLMWikis treats knowledge as operational infrastructure. It lays out raw/source layers, compiled wiki pages, metadata, trust labels, review cycles, source policy, agent rules, security/privacy boundaries, navigation, linting, repair workflows, setup packets, and starter bundles so AI systems read governed knowledge instead of relying on chat residue.",
"evidenceLabel": "Public Platform",
"evidenceLabels": [
"Public Platform",
"User-Confirmed"
],
"evidenceLevel": "User-Confirmed",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "LLMWikis.org",
"professionalContext": "Public LLM Wiki handbook and durable AI-ready knowledge systems surface.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md",
"Architecture Notes/uai-memory-handoff-map.md",
"Architecture Notes/ai-prompt-architecture.md"
],
"proofs": [
"Reviewed handbook routes and setup wizard",
"Trust labels, metadata, source policy, and agent rules",
"Starter bundle and implementation checklist",
"LLM Wiki vs RAG / AI Memory decision surfaces"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md",
"Architecture Notes/uai-memory-handoff-map.md",
"Architecture Notes/ai-prompt-architecture.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Information architecture, knowledge governance, source-policy design, metadata modeling, review gates, technical documentation systems, graph/retrieval preparation, agent instruction design, security boundaries, and scalable human-plus-AI documentation workflows.",
"sourceStatus": "user-confirmed",
"source_note": "Public LLM Wiki handbook and durable AI-ready knowledge systems surface.",
"source_status": "user-confirmed",
"status": "public-platform",
"summary": "Durable AI-ready knowledge system blueprint for reviewed source pipelines, metadata, trust labels, governance, retrieval/graph navigation, and long-memory docs paired with compact UAI memory.",
"tags": [
"LLM Wikis",
"AI Knowledge Bases",
"Metadata",
"Trust Labels",
"Agent Rules",
"Source Policy",
"Governance",
"RAG Prep",
"Documentation Systems",
"AI Memory",
"Long-Term Memory",
"Reviewed Sources",
"Retrieval Graph"
],
"technologies": [
"LLM Wikis",
"AI Knowledge Bases",
"Metadata",
"Trust Labels",
"Agent Rules",
"Source Policy",
"Governance",
"RAG Prep",
"Documentation Systems",
"AI Memory"
],
"tier": "top",
"title": "LLMWikis.org",
"type": "AI knowledge architecture",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://llmwikis.org/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Information architecture, knowledge governance, source-policy design, metadata modeling, review gates, technical documentation systems, graph/retrieval preparation, agent instruction design, security boundaries, and scalable human-plus-AI documentation workflows."
]
},
{
"ai_signal": "Turns AI memory from raw chat history into inspected, bounded, reviewable packets that can be routed into agent workflows without treating probabilistic output as trusted by default.",
"capabilityTags": [
"Python",
"MySQL",
"Cognitive Packets",
"Memory Firewall",
"Quarantine-First Review",
"Provenance",
"Review Gates",
"Agent Memory",
"AI Safety",
"TypeScript"
],
"detail": "NeuralWikis is reframed as the agent-facing cognitive exchange node: memory, skill, persona, protocol, and governance objects are treated as packets that require provenance, schema fit, contradiction review, quarantine-first handling, and review gates before adoption.",
"evidenceLabel": "Prototype",
"evidenceLabels": [
"Public Platform",
"Technical Review"
],
"evidenceLevel": "Technical Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "NeuralWikis.com",
"professionalContext": "Python / MySQL AI workspace and cognitive-packet proof lane derived from strategy direction; is available as a technical review surface before stronger implementation wording is used.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md",
"Architecture Notes/ai-prompt-architecture.md",
"Architecture Notes/source-governance.md"
],
"proofs": [
"Updated from generic AI model workspace language to cognitive packet and memory-firewall language.",
"Mapped to Python AI Pipelines and Deterministic Prompt Architecture resolver terms.",
"Paired with LocalEndpoint and NeuroWikis as the Teleodynamic AI safety lane."
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md",
"Architecture Notes/ai-prompt-architecture.md",
"Architecture Notes/source-governance.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Python AI pipeline orchestration, MySQL state, cognitive packet design, memory firewall logic, provenance review, and type-safe handoff surfaces.",
"sourceStatus": "Design Review",
"source_note": "Python / MySQL AI workspace and cognitive-packet proof lane derived from strategy direction; is available as a technical review surface before stronger implementation wording is used.",
"source_status": "Design Review",
"status": "prototype",
"summary": "Python/MySQL agent-facing cognitive packet and memory-firewall architecture for governed AI memory, provenance, review lanes, and safe adoption of knowledge objects.",
"tags": [
"Python",
"MySQL",
"Cognitive Packets",
"Memory Firewall",
"Quarantine-First Review",
"Provenance",
"Review Gates",
"Agent Memory",
"AI Safety",
"TypeScript"
],
"technologies": [
"Python",
"MySQL",
"Cognitive Packets",
"Memory Firewall",
"Quarantine-First Review",
"Provenance",
"Review Gates",
"Agent Memory",
"AI Safety",
"TypeScript"
],
"tier": "top",
"title": "NeuralWikis.com",
"type": "Python/MySQL cognitive packet exchange",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://neuralwikis.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Python AI pipeline orchestration, MySQL state, cognitive packet design, memory firewall logic, provenance review, and type-safe handoff surfaces."
]
},
{
"ai_signal": "Provides a concrete AI safety pattern: allow agents to understand local capabilities while withholding dangerous action rights and private environment details.",
"capabilityTags": [
"Python",
"MySQL",
"Passive Validation",
"Endpoint Discovery",
"Zero-Execution Boundary",
"Metadata",
"JSON",
"Markdown",
"AI Safety",
"Local Development"
],
"detail": "LocalEndpoint is the safe discovery surface: agents can read descriptions of local endpoints, metadata, webhooks, and tool capabilities through JSON/Markdown artifacts without private-network probing, secret storage, or runtime execution.",
"evidenceLabel": "Prototype",
"evidenceLabels": [
"Public Platform",
"Technical Review"
],
"evidenceLevel": "Technical Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "LocalEndpoint.com",
"professionalContext": "Python / MySQL passive-validation and endpoint-boundary proof lane derived from strategy direction; execution authority is outside the portfolio wording.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md",
"Architecture Notes/ai-prompt-architecture.md",
"Architecture Notes/source-governance.md"
],
"proofs": [
"Added as a high-signal Python AI safety project.",
"Mapped to metadata validation, passive validation, and local endpoint discovery aliases.",
"Referenced by the Architecture Notes long-memory handoff map and AI handoff short-term memory."
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md",
"Architecture Notes/ai-prompt-architecture.md",
"Architecture Notes/source-governance.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Python validation logic, passive metadata inspection, JSON/Markdown output, zero-execution security boundaries, MySQL-backed state, and local development safety.",
"sourceStatus": "Design Review",
"source_note": "Python / MySQL passive-validation and endpoint-boundary proof lane derived from strategy direction; execution authority is outside the portfolio wording.",
"source_status": "Design Review",
"status": "prototype",
"summary": "Python/MySQL local-safe endpoint discovery and passive metadata validation layer for agent-readable development infrastructure without runtime execution authority.",
"tags": [
"Python",
"MySQL",
"Passive Validation",
"Endpoint Discovery",
"Zero-Execution Boundary",
"Metadata",
"JSON",
"Markdown",
"AI Safety",
"Local Development"
],
"technologies": [
"Python",
"MySQL",
"Passive Validation",
"Endpoint Discovery",
"Zero-Execution Boundary",
"Metadata",
"JSON",
"Markdown",
"AI Safety",
"Local Development"
],
"tier": "high",
"title": "LocalEndpoint.com",
"type": "Python local-safe endpoint metadata validation",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://localendpoint.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Python validation logic, passive metadata inspection, JSON/Markdown output, zero-execution security boundaries, MySQL-backed state, and local development safety."
]
},
{
"ai_signal": "Shows that agent-facing AI memory needs a human-readable control surface, not only hidden machine-to-machine exchange.",
"capabilityTags": [
"TypeScript",
"WordPress",
"MySQL",
"AI Governance",
"Human Oversight",
"Documentation",
"Onboarding",
"Prompt-Governed CMS",
"Review Gates",
"AI Literacy"
],
"detail": "NeuroWikis provides the human governance lane: plain-language explanations, review guidance, onboarding, and human-legible governance surfaces for AI systems that also need machine-readable boundaries.",
"evidenceLabel": "Prototype",
"evidenceLabels": [
"Public Platform",
"Technical Review"
],
"evidenceLevel": "Technical Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "NeuroWikis.com",
"professionalContext": "Human governance and AI education proof lane derived from strategy direction; is available as a technical review surface before implementation details are elevated.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md",
"Architecture Notes/ai-prompt-architecture.md",
"Architecture Notes/source-governance.md"
],
"proofs": [
"Added to the Teleodynamic ecosystem group.",
"Paired with NeuralWikis and LocalEndpoint for machine memory, safety, and governance lanes.",
"Supports resume language around human-in-the-loop review gates."
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md",
"Architecture Notes/ai-prompt-architecture.md",
"Architecture Notes/source-governance.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "TypeScript-governed content architecture, WordPress/MySQL extension patterns, human oversight design, AI governance communication, and dual-channel documentation.",
"sourceStatus": "Design Review",
"source_note": "Human governance and AI education proof lane derived from strategy direction; is available as a technical review surface before implementation details are elevated.",
"source_status": "Design Review",
"status": "prototype",
"summary": "Human-facing AI governance and education surface paired with agent-facing NeuralWikis, emphasizing plain-language oversight, governance literacy, and controlled CMS publishing.",
"tags": [
"TypeScript",
"WordPress",
"MySQL",
"AI Governance",
"Human Oversight",
"Documentation",
"Onboarding",
"Prompt-Governed CMS",
"Review Gates",
"AI Literacy"
],
"technologies": [
"TypeScript",
"WordPress",
"MySQL",
"AI Governance",
"Human Oversight",
"Documentation",
"Onboarding",
"Prompt-Governed CMS",
"Review Gates",
"AI Literacy"
],
"tier": "high",
"title": "NeuroWikis.com",
"type": "Human-facing AI governance",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://neurowikis.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"TypeScript-governed content architecture, WordPress/MySQL extension patterns, human oversight design, AI governance communication, and dual-channel documentation."
]
},
{
"ai_signal": "Shows that AI-assisted design can produce small-message systems without letting compactness become ambiguity. It emphasizes visible traces, validators, evidence lanes, and reviewable constraints for regulated or high-accountability handoffs.",
"capabilityTags": [
"IOTA-1",
"Compact Messaging",
"Unicode",
"Canonicalization",
"Registries",
"Validator",
"Converter",
"Evidence Payloads",
"AI Handoffs",
"Protocol Tooling"
],
"detail": "JustAnIota is intentionally narrow and technical. It focuses on how compact AI messages can remain inspectable: canonical envelopes, registry-backed meaning, Unicode and normalization boundaries, validators, converters, segment traces, approximation evidence, and explicit warnings when compact messages cannot safely carry meaning by themselves.",
"evidenceLabel": "Public Platform",
"evidenceLabels": [
"Public Platform",
"User-Confirmed"
],
"evidenceLevel": "User-Confirmed",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "JustAnIota.com",
"professionalContext": "Public protocol evidence surface for compact messaging and canonicalization.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"IOTA-1 profile and authority record",
"Converter, validator, registry explorer, and examples",
"Unicode/canonicalization boundaries",
"Approximation and evidence surfaces"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Compiler/interpreter-style pipeline design, registry/data modeling, deterministic validation, Unicode and normalization awareness, compact protocol thinking, technical UX for developer tools, evidence payload design, and security-boundary documentation.",
"sourceStatus": "user-confirmed",
"source_note": "Public protocol evidence surface for compact messaging and canonicalization.",
"source_status": "user-confirmed",
"status": "public-platform",
"summary": "A standards-focused IOTA-1 authority surface for compact, language-agnostic AI messages, registries, schemas, validation, canonicalization, Unicode safety, converter tooling, and evidence vocabularies.",
"tags": [
"IOTA-1",
"Compact Messaging",
"Unicode",
"Canonicalization",
"Registries",
"Validator",
"Converter",
"Evidence Payloads",
"AI Handoffs",
"Protocol Tooling"
],
"technologies": [
"IOTA-1",
"Compact Messaging",
"Unicode",
"Canonicalization",
"Registries",
"Validator",
"Converter",
"Evidence Payloads",
"AI Handoffs",
"Protocol Tooling"
],
"tier": "top",
"title": "JustAnIota.com",
"type": "Compact AI messaging tooling",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://justaniota.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Compiler/interpreter-style pipeline design, registry/data modeling, deterministic validation, Unicode and normalization awareness, compact protocol thinking, technical UX for developer tools, evidence payload design, and security-boundary documentation."
]
},
{
"ai_signal": "Shows how AI-assisted build workflows can turn fuzzy label sets into more stable category structures, hierarchy pages, synonyms, canonical names, parent/child relationships, and machine-readable navigation surfaces.",
"capabilityTags": [
"Taxonomy",
"Hierarchies",
"Trees",
"Information Architecture",
"Classification",
"Navigation",
"Knowledge Graphs",
"AI Retrieval"
],
"detail": "CategoryHierarchies.com sits in the top row because it is directly relevant to enterprise information architecture: category trees, parent/child relationships, controlled vocabularies, faceted navigation, taxonomy import/export thinking, semantic grouping, and structured hierarchy data that people and AI systems can traverse.",
"evidenceLabel": "Public Platform",
"evidenceLabels": [
"Public Platform",
"Technical Review"
],
"evidenceLevel": "User-Confirmed",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "CategoryHierarchies.com",
"professionalContext": "Taxonomy and hierarchy proof surface; claim is data modeling and information architecture.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"User-prioritized top-row project in the portfolio ecosystem",
"Taxonomy/category-hierarchy domain has direct overlap with enterprise data modeling and information architecture",
"Useful bridge between human labels, controlled vocabulary, faceted navigation, and AI-readable knowledge structure",
"Copy is intentionally conservative because live fetch was limited during verification"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Proves taxonomy modeling, tree-structured data thinking, classification design, knowledge organization, search/navigation structure, and the kind of hierarchy reasoning used in catalogs, documentation systems, product taxonomies, permission trees, reporting dimensions, and AI retrieval routing.",
"sourceStatus": "user-confirmed",
"source_note": "Taxonomy and hierarchy proof surface; claim is data modeling and information architecture.",
"source_status": "user-confirmed",
"status": "public-platform",
"summary": "Major taxonomy and category-hierarchy project for nested classification, parent-child trees, semantic grouping, navigation paths, and AI-readable organizational structures.",
"tags": [
"Taxonomy",
"Hierarchies",
"Trees",
"Information Architecture",
"Classification",
"Navigation",
"Knowledge Graphs",
"AI Retrieval"
],
"technologies": [
"Taxonomy",
"Hierarchies",
"Trees",
"Information Architecture",
"Classification",
"Navigation",
"Knowledge Graphs",
"AI Retrieval"
],
"tier": "top",
"title": "CategoryHierarchies.com",
"type": "Taxonomy / hierarchy systems",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://categoryhierarchies.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Proves taxonomy modeling, tree-structured data thinking, classification design, knowledge organization, search/navigation structure, and the kind of hierarchy reasoning used in catalogs, documentation systems, product taxonomies, permission trees, reporting dimensions, and AI retrieval routing."
]
},
{
"ai_signal": "Demonstrates deterministic prompt architecture for organizing complex research into durable public structures with explicit conceptual boundaries.",
"capabilityTags": [
"Research Publishing",
"Technical Writing",
"Cosmology Essays",
"Information Architecture",
"AI-Assisted Writing",
"Taxonomy",
"Long-Form Content",
"SEO",
"Deterministic Prompt Architecture",
"Research Packaging",
"Semantic Grouping"
],
"detail": "ArcSecs is important because it shows large-scale structured writing and source-oriented publication around difficult technical ideas. The live site organizes slow light, no-spacetime critique, variable light, redshift, photon mass, dark-sector concepts, and long-form article archives into a coherent navigable research surface.",
"evidenceLabel": "Research / Speculative",
"evidenceLabels": [
"Public Platform",
"User-Confirmed"
],
"evidenceLevel": "Public Platform",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "ArcSecs.com",
"professionalContext": "Structured research publication surface; technical claim is content architecture and research packaging.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Live homepage frames ArcSecs as rethinking gravity, light, redshift, and hidden universe structure",
"Signal map connects redshift, photon behavior, gravity, slow light, horizons, and dark sector concepts",
"Article archive exposes long-form essays and topic routing",
"Contact/identity footer connects the site to Michael Kappel"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "AI-assisted structured research publication, taxonomy mapping, semantic grouping, WordPress/MySQL content architecture, and long-form technical writing automation.",
"sourceStatus": "approved",
"source_note": "Structured research publication surface; technical claim is content architecture and research packaging.",
"source_status": "approved",
"status": "research-speculative",
"summary": "Structured research publication surface for long-form semantic grouping, speculative technical essays, and prompt-engineered research packaging.",
"tags": [
"Research Publishing",
"Technical Writing",
"Cosmology Essays",
"Information Architecture",
"AI-Assisted Writing",
"Taxonomy",
"Long-Form Content",
"SEO",
"Deterministic Prompt Architecture",
"Research Packaging",
"Semantic Grouping"
],
"technologies": [
"Research Publishing",
"Technical Writing",
"Cosmology Essays",
"Information Architecture",
"AI-Assisted Writing",
"Taxonomy",
"Long-Form Content",
"SEO",
"Deterministic Prompt Architecture",
"Research Packaging"
],
"tier": "top",
"title": "ArcSecs.com",
"type": "Speculative physics / structured research publication",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://arcsecs.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"AI-assisted structured research publication, taxonomy mapping, semantic grouping, WordPress/MySQL content architecture, and long-form technical writing automation."
]
},
{
"ai_signal": "Shifts prompt engineering from ad-hoc chat to repeatable content architecture with explicit output shape, review boundary, and business-facing use.",
"capabilityTags": [
"Prompt Engineering",
"Deterministic Output",
"WordPress",
"E-Commerce",
"Taxonomy",
"SEO Metadata",
"Catalog Automation",
"MySQL",
"Review Workflow",
"AI Content"
],
"detail": "AnarchyShelters demonstrates prompt engineering as a production content and commerce workflow: constrained prompts generate structured product taxonomies, SEO metadata, and catalog language that can be reviewed and inserted into CMS/e-commerce data structures.",
"evidenceLabel": "Prototype",
"evidenceLabels": [
"Public Platform",
"Technical Review"
],
"evidenceLevel": "Technical Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "AnarchyShelters.com",
"professionalContext": "Prompt-architecture and taxonomy automation concept from strategy direction; public project context and conservative implementation wording.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Added to high-signal public platforms for deterministic prompt architecture.",
"Mapped to automated taxonomy generation and prompt-engineered commerce aliases.",
"Complements ArcSecs and DarkMatterDrive as content/research generation proof."
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Prompt architecture, e-commerce taxonomy, WordPress/MySQL content automation, structured JSON-style output expectations, and deterministic catalog generation.",
"sourceStatus": "Design Review",
"source_note": "Prompt-architecture and taxonomy automation concept from strategy direction; public project context and conservative implementation wording.",
"source_status": "Design Review",
"status": "prototype",
"summary": "Transactional WordPress/e-commerce proof surface for deterministic prompt-engineered catalog, taxonomy, metadata, and product-copy automation.",
"tags": [
"Prompt Engineering",
"Deterministic Output",
"WordPress",
"E-Commerce",
"Taxonomy",
"SEO Metadata",
"Catalog Automation",
"MySQL",
"Review Workflow",
"AI Content"
],
"technologies": [
"Prompt Engineering",
"Deterministic Output",
"WordPress",
"E-Commerce",
"Taxonomy",
"SEO Metadata",
"Catalog Automation",
"MySQL",
"Review Workflow",
"AI Content"
],
"tier": "high",
"title": "AnarchyShelters.com",
"type": "Prompt-engineered commerce taxonomy",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://anarchyshelters.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Prompt architecture, e-commerce taxonomy, WordPress/MySQL content automation, structured JSON-style output expectations, and deterministic catalog generation."
]
},
{
"ai_signal": "Shows how dense speculative material can be converted into structured dossiers through constrained AI workflows and human review.",
"capabilityTags": [
"Technical Writing",
"Speculative Physics",
"Source Dossiers",
"AI Memory",
"Research Atlas",
"Prompt Engineering",
"Research Dossiers",
"Semantic Navigation"
],
"detail": "DarkMatterDrive is best treated as a high-concept technical-writing and structured-source project. It combines speculative physics with dossiers, source organization, and AI memory workflows.",
"evidenceLabel": "Research / Speculative",
"evidenceLabels": [
"Research / Speculative",
"Technical Review"
],
"evidenceLevel": "Technical Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "DarkMatterDrive.com",
"professionalContext": "Speculative technical atlas and research-packaging surface; present subject matter as research packaging and content architecture.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Structured source dossiers",
"Speculative technical atlas",
"AI memory workflow use"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Prompt-engineered long-form content architecture, taxonomy design, source-aware research packaging, WordPress publishing, and semantic navigation.",
"sourceStatus": "Design Review",
"source_note": "Speculative technical atlas and research-packaging surface; present subject matter as research packaging and content architecture.",
"source_status": "Design Review",
"status": "research-speculative",
"summary": "Speculative technical atlas used as proof of constrained AI-assisted research packaging, semantic grouping, and complex knowledge navigation.",
"tags": [
"Technical Writing",
"Speculative Physics",
"Source Dossiers",
"AI Memory",
"Research Atlas",
"Prompt Engineering",
"Research Dossiers",
"Semantic Navigation"
],
"technologies": [
"Technical Writing",
"Speculative Physics",
"Source Dossiers",
"AI Memory",
"Research Atlas",
"Prompt Engineering",
"Research Dossiers",
"Semantic Navigation"
],
"tier": "high",
"title": "DarkMatterDrive.com",
"type": "Speculative technical atlas",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://darkmatterdrive.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Prompt-engineered long-form content architecture, taxonomy design, source-aware research packaging, WordPress publishing, and semantic navigation."
]
},
{
"ai_signal": "Shows AI-assisted knowledge-system building: turning complex philosophical material into structured pages, concept clusters, cross-links, glossaries, and navigable summaries without forcing it into a generic blog format.",
"capabilityTags": [
"Wiki Architecture",
"Philosophy",
"Theism",
"Knowledge Systems",
"Taxonomy",
"Semantic Navigation",
"AI-Readable Content",
"Concept Modeling"
],
"detail": "Wikitheism is positioned close to the top because it extends the portfolio beyond single-purpose product sites into structured knowledge architecture. It should be read as a wiki-style concept system: topic pages, belief/philosophy categories, semantic organization, internal linking, source discipline, and durable navigation for complex abstract material.",
"evidenceLabel": "Research / Speculative",
"evidenceLabels": [
"Prototype",
"Technical Review"
],
"evidenceLevel": "User-Confirmed",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "Wikitheism.org",
"professionalContext": "Structured research/publication surface; claim is durable organization of abstract material.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"User-confirmed as one of Michael Kappel's important sites",
"Fits the broader LLM Wiki / AI-readable knowledge architecture direction",
"Connects philosophy, theology, machine-spirituality, and taxonomy-oriented publication",
"Copy is conservative because live fetch was limited during verification"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Proves taxonomy, knowledge architecture, wiki modeling, concept hierarchy design, navigation structure, semantic grouping, editorial systems, and the ability to make abstract domains legible to both humans and AI tools.",
"sourceStatus": "user-confirmed",
"source_note": "Structured research/publication surface; claim is durable organization of abstract material.",
"source_status": "user-confirmed",
"status": "research-speculative",
"summary": "User-confirmed top-row site for organizing theism, philosophy, machine spirituality, conceptual taxonomy, and wiki-style knowledge into a durable public structure.",
"tags": [
"Wiki Architecture",
"Philosophy",
"Theism",
"Knowledge Systems",
"Taxonomy",
"Semantic Navigation",
"AI-Readable Content",
"Concept Modeling"
],
"technologies": [
"Wiki Architecture",
"Philosophy",
"Theism",
"Knowledge Systems",
"Taxonomy",
"Semantic Navigation",
"AI-Readable Content",
"Concept Modeling"
],
"tier": "top",
"title": "Wikitheism.org",
"type": "Structured philosophy / wiki knowledge system",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://wikitheism.org/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Proves taxonomy, knowledge architecture, wiki modeling, concept hierarchy design, navigation structure, semantic grouping, editorial systems, and the ability to make abstract domains legible to both humans and AI tools."
]
},
{
"ai_signal": "Strong AI infrastructure signal: it shows how agent memory can be built as reviewed, indexed, source-aware pages instead of opaque chat history or ungoverned vector sludge.",
"capabilityTags": [
"AI Memory",
"Source Governance",
"Provenance",
"Route Discovery",
"Hashes",
"LLM Wikis",
"Agent Retrieval",
"Knowledge Systems"
],
"detail": "AIWikis extends the LLMWikis pattern into a workspace-level memory destination. It preserves reviewed source-site work, exposes provenance, hashes, file references, reports, source boundaries, and route discovery so AI agents can retrieve exact context without taking over source authority.",
"evidenceLabel": "Technical Review",
"evidenceLabels": [
"Public Platform",
"User-Confirmed"
],
"evidenceLevel": "Technical Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "AIWikis.org",
"professionalContext": "Technical review surface with public project context and conservative wording.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Canonical/source-governed status metadata",
"Search, topics, sources, files, reports, and contact routes",
"Provenance and source-boundary framing",
"AI-readable small-context retrieval posture"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Cross-site memory architecture, provenance design, route registries, source-boundary modeling, AI-readable retrieval, public knowledge indexing, hash/reference discipline, and source-governed documentation systems.",
"sourceStatus": "Design Review",
"source_note": "Technical review surface with public project context and conservative wording.",
"source_status": "Design Review",
"status": "Design Review",
"summary": "Source-governed AI memory site that helps people, LLMs, and agents find the smallest useful reviewed page instead of dragging entire source trees into context.",
"tags": [
"AI Memory",
"Source Governance",
"Provenance",
"Route Discovery",
"Hashes",
"LLM Wikis",
"Agent Retrieval",
"Knowledge Systems"
],
"technologies": [
"AI Memory",
"Source Governance",
"Provenance",
"Route Discovery",
"Hashes",
"LLM Wikis",
"Agent Retrieval",
"Knowledge Systems"
],
"tier": "high",
"title": "AIWikis.org",
"type": "Shared AI memory destination",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://aiwikis.org/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Cross-site memory architecture, provenance design, route registries, source-boundary modeling, AI-readable retrieval, public knowledge indexing, hash/reference discipline, and source-governed documentation systems."
]
},
{
"ai_signal": "Shows AI systems treated as measurable production components. The project is less about prompting and more about how to compare, calibrate, monitor, and improve behavior under change.",
"capabilityTags": [
"AI Evaluation",
"Calibration",
"Benchmarks",
"Rubrics",
"Drift",
"Reliability",
"Governance",
"AI Safety",
"Measurement"
],
"detail": "Calibrants translates enterprise AI reliability into inspectable artifacts: known references, gold answers, rubrics, edge cases, task context, expected behavior, measurement methods, adjustment loops, prompt/model/guardrail changes, and versioned drift monitoring.",
"evidenceLabel": "Technical Review",
"evidenceLabels": [
"Public Platform",
"User-Confirmed"
],
"evidenceLevel": "Technical Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "Calibrants.com",
"professionalContext": "Technical review surface with public project context and conservative wording.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Calibration methods and reference signals",
"Benchmark/protocol/governance routes",
"ECE/Brier/source-fidelity style measurement language",
"Drift maps and release-evidence framing"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "AI evaluation, confidence calibration, benchmark design, rubric design, reliability engineering, drift response, semantic reference modeling, measurement loops, governance evidence, and operational AI QA.",
"sourceStatus": "Design Review",
"source_note": "Technical review surface with public project context and conservative wording.",
"source_status": "Design Review",
"status": "Design Review",
"summary": "AI calibrants knowledge resource for confidence calibration, semantic references, reliability curves, governance evidence, drift tracking, benchmarks, and operational checks.",
"tags": [
"AI Evaluation",
"Calibration",
"Benchmarks",
"Rubrics",
"Drift",
"Reliability",
"Governance",
"AI Safety",
"Measurement"
],
"technologies": [
"AI Evaluation",
"Calibration",
"Benchmarks",
"Rubrics",
"Drift",
"Reliability",
"Governance",
"AI Safety",
"Measurement"
],
"tier": "high",
"title": "Calibrants.com",
"type": "AI evaluation / calibration",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://calibrants.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"AI evaluation, confidence calibration, benchmark design, rubric design, reliability engineering, drift response, semantic reference modeling, measurement loops, governance evidence, and operational AI QA."
]
},
{
"ai_signal": "Supports the AI-assisted-build story by showing the operational layer that serious software still needs: monitoring, audit trails, incident resolution, deployment feedback, and automated test visibility.",
"capabilityTags": [
"SaaS",
"Monitoring",
"Incident Workflow",
"Webhooks",
"Slack",
"CI",
"Testing",
"SDK",
"Reliability"
],
"detail": "ErrorNotifier proves production-ops thinking: external uptime checks, expected status/keyword rules, response-time history, confirmed incidents, recovery flow, email/Slack/webhook alert routing, browser SDK foundations, release metadata, and CI-posted unit-test result history.",
"evidenceLabel": "Technical Review",
"evidenceLabels": [
"Public Platform",
"User-Confirmed"
],
"evidenceLevel": "Technical Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "ErrorNotifier.com",
"professionalContext": "Technical review surface with public project context and conservative wording.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"External uptime checks and expected-response rules",
"Incident lifecycle with recoveries and history",
"Email, Slack, and signed generic webhook routing",
"Automated CI test-run result posting"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "SaaS architecture, observability, incident lifecycle design, alert routing, webhook security, SDK packaging, CI/test reporting, audit history, onboarding UX, and production reliability engineering.",
"sourceStatus": "Design Review",
"source_note": "Technical review surface with public project context and conservative wording.",
"source_status": "Design Review",
"status": "Design Review",
"summary": "Production uptime monitoring, incident workflow, alert routing, error tracking, and automated test-result reporting product surface.",
"tags": [
"SaaS",
"Monitoring",
"Incident Workflow",
"Webhooks",
"Slack",
"CI",
"Testing",
"SDK",
"Reliability"
],
"technologies": [
"SaaS",
"Monitoring",
"Incident Workflow",
"Webhooks",
"Slack",
"CI",
"Testing",
"SDK",
"Reliability"
],
"tier": "high",
"title": "ErrorNotifier.com",
"type": "Monitoring SaaS / SDK product",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://errornotifier.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"SaaS architecture, observability, incident lifecycle design, alert routing, webhook security, SDK packaging, CI/test reporting, audit history, onboarding UX, and production reliability engineering."
]
},
{
"ai_signal": "Shows AI-assisted product iteration applied to a real end-user domain: the site is structured enough for marketing, guidance, public lookup, reporting, help pages, and machine-readable consistency without losing user clarity.",
"capabilityTags": [
"Product UX",
"Code Lookup",
"Maps",
"Public Journeys",
"Teams",
"Reporting",
"Privacy",
"Geocaching"
],
"detail": "Geotrackable is product proof: it handles exact public/secret-code flows, public trackable browsing, journey maps, route-first storytelling, adult-managed teams, family/troop/classroom participation, reporting, privacy/terms pages, support requests, and practical geocaching documentation.",
"evidenceLabel": "Prototype",
"evidenceLabels": [
"Public Platform",
"User-Confirmed"
],
"evidenceLevel": "User-Confirmed",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "Geotrackable.com",
"professionalContext": "AI-assisted product concept and public journey/storytelling surface; present as as external client production with confirmed context.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Trackable code lookup and public trackable browsing",
"Journey maps and public reports",
"Adult-managed teams for families, clubs, troops, and schools",
"Guides, privacy, support, and data-management routes"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Consumer web product architecture, exact-code lookup, public/private state boundaries, map/journey UX, team/account modeling, guidance content, public reporting, localization, privacy-aware participation, and real workflow design.",
"sourceStatus": "user-confirmed",
"source_note": "AI-assisted product concept and public journey/storytelling surface; present as as external client production with confirmed context.",
"source_status": "user-confirmed",
"status": "prototype",
"summary": "Public geocaching trackable product with exact code lookup, public journey pages, maps, teams, reports, and guidance for individuals, clubs, families, troops, and schools.",
"tags": [
"Product UX",
"Code Lookup",
"Maps",
"Public Journeys",
"Teams",
"Reporting",
"Privacy",
"Geocaching"
],
"technologies": [
"Product UX",
"Code Lookup",
"Maps",
"Public Journeys",
"Teams",
"Reporting",
"Privacy",
"Geocaching"
],
"tier": "high",
"title": "Geotrackable.com",
"type": "Consumer product / maps / data",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://geotrackable.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Consumer web product architecture, exact-code lookup, public/private state boundaries, map/journey UX, team/account modeling, guidance content, public reporting, localization, privacy-aware participation, and real workflow design."
]
},
{
"ai_signal": "Pushes the public portfolio beyond prompt engineering into distributed AI-system design and coordinated memory structures.",
"capabilityTags": [
"AI Infrastructure",
"Shared Memory",
"Federation",
"Multi-Agent",
"Interoperability",
"Agent File Handoff"
],
"detail": "Neurocumulus is a strong AI platform-positioning project. It supports the same architecture vocabulary as UAIX and LLMWikis, but from the viewpoint of shared memory, federation, agent coordination, and cross-model systems.",
"evidenceLabel": "Technical Review",
"evidenceLabels": [
"Public Platform",
"Technical Review"
],
"evidenceLevel": "Technical Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "Neurocumulus.com",
"professionalContext": "Technical review surface with public project context and conservative wording.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Shared memory and federation positioning",
"Multi-agent coordination framing",
"Handoff/workspace pattern connection"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "AI infrastructure framing, federation concepts, multi-agent coordination, shared-memory design, interoperability language, and platform architecture.",
"sourceStatus": "Design Review",
"source_note": "Technical review surface with public project context and conservative wording.",
"source_status": "Design Review",
"status": "Design Review",
"summary": "AI infrastructure brand focused on shared memory, cross-model interoperability, secure federation, and coordinated multi-agent intelligence.",
"tags": [
"AI Infrastructure",
"Shared Memory",
"Federation",
"Multi-Agent",
"Interoperability",
"Agent File Handoff"
],
"technologies": [
"AI Infrastructure",
"Shared Memory",
"Federation",
"Multi-Agent",
"Interoperability",
"Agent File Handoff"
],
"tier": "high",
"title": "Neurocumulus.com",
"type": "AI infrastructure brand",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://neurocumulus.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"AI infrastructure framing, federation concepts, multi-agent coordination, shared-memory design, interoperability language, and platform architecture."
]
},
{
"ai_signal": "Supports the human side of AI and software: communities need structured continuity, events, standards, and chapter workflows just like codebases need memory and governance.",
"capabilityTags": [
"Community",
"Events",
"Chapters",
"RSVP",
"Organizer Workflows",
"Governance",
"Software Groups"
],
"detail": "SoftwareCommunity.org turns local software-community growth into a structured product: find groups, schedule events, start chapters, gather RSVPs, publish standards, and support organizers. It is less experimental AI and more practical community/workflow architecture.",
"evidenceLabel": "Public Platform",
"evidenceLabels": [
"Public Platform",
"User-Confirmed"
],
"evidenceLevel": "User-Confirmed",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "SoftwareCommunity.org",
"professionalContext": "Public proof surface; keep claims bounded to visible content and user-confirmed context.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Find groups, events, and start-a-group routes",
"Organizer/chapter workflow framing",
"Code of conduct, privacy, and sponsors routes",
"Global home for local software groups"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Community platform modeling, chapter/event data structures, organizer workflows, standards pages, directory UX, RSVP-style routing, public WordPress product design, and governance around community growth.",
"sourceStatus": "user-confirmed",
"source_note": "Public proof surface; keep claims bounded to visible content and user-confirmed context.",
"source_status": "user-confirmed",
"status": "public-platform",
"summary": "Community platform for software groups, chapter directories, events, organizer workflows, local meetings, RSVPs, and community standards.",
"tags": [
"Community",
"Events",
"Chapters",
"RSVP",
"Organizer Workflows",
"Governance",
"Software Groups"
],
"technologies": [
"Community",
"Events",
"Chapters",
"RSVP",
"Organizer Workflows",
"Governance",
"Software Groups"
],
"tier": "high",
"title": "SoftwareCommunity.org",
"type": "Community platform",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://softwarecommunity.org/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Community platform modeling, chapter/event data structures, organizer workflows, standards pages, directory UX, RSVP-style routing, public WordPress product design, and governance around community growth."
]
},
{
"ai_signal": "Connects AI with guardrails to enterprise modernization without letting it overpower the core standards/product projects.",
"capabilityTags": [
"Consulting",
".NET",
"Legacy Rescue",
"AI Guardrails",
"SQL Server",
"API Design"
],
"detail": "This is useful supporting identity, but it should not sit above the strongest public technical project surfaces. It explains the consulting/business wrapper around the architecture work.",
"evidenceLabel": "Technical Review",
"evidenceLabels": [
"Archived",
"Technical Review"
],
"evidenceLevel": "Technical Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "LongTermSoftwareSolutions.com",
"professionalContext": "Technical review surface with public project context and conservative wording.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Consulting service positioning",
"Legacy rescue language",
"AI with guardrails"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": ".NET architecture, legacy modernization, API design, SQL Server, AI guardrails, testing strategy, team mentoring, and business-facing consulting positioning.",
"sourceStatus": "Design Review",
"source_note": "Technical review surface with public project context and conservative wording.",
"source_status": "Design Review",
"status": "Design Review",
"summary": "Consulting identity for long-lived .NET architecture, legacy rescue, APIs, SQL Server, AI with guardrails, test strategy, and team leadership.",
"tags": [
"Consulting",
".NET",
"Legacy Rescue",
"AI Guardrails",
"SQL Server",
"API Design"
],
"technologies": [
"Consulting",
".NET",
"Legacy Rescue",
"AI Guardrails",
"SQL Server",
"API Design"
],
"tier": "identity",
"title": "LongTermSoftwareSolutions.com",
"type": "Consulting / architecture rescue",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://longtermsoftwaresolutions.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
".NET architecture, legacy modernization, API design, SQL Server, AI guardrails, testing strategy, team mentoring, and business-facing consulting positioning."
]
},
{
"ai_signal": "Supports AI-readability and identity disambiguation but should not compete with the main project proof surfaces.",
"capabilityTags": [
"Resume UX",
"Technical SEO",
"Structured Data",
"Context Engineering",
"Crawlable UI"
],
"detail": "Mechanotheist is a useful secondary profile: technical SEO, structured data, clean resume endpoints, skills matrix, and crawlable identity. It belongs near the bottom now because MichaelKappel.com is the primary hub.",
"evidenceLabel": "Technical Review",
"evidenceLabels": [
"Archived",
"Technical Review"
],
"evidenceLevel": "Technical Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "Mechanotheist.com",
"professionalContext": "Technical review surface with public project context and conservative wording.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Console-style resume surface",
"Structured data and crawlable routes",
"Skills matrix / context profile"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Technical SEO, structured resume data, no-JavaScript fallback, crawlable architecture, console-style UX, and professional identity routing.",
"sourceStatus": "Design Review",
"source_note": "Technical review surface with public project context and conservative wording.",
"source_status": "Design Review",
"status": "Design Review",
"summary": "Console-style resume and professional identity surface designed to be interactive, crawlable, structured, and resilient with no-JavaScript fallback thinking.",
"tags": [
"Resume UX",
"Technical SEO",
"Structured Data",
"Context Engineering",
"Crawlable UI"
],
"technologies": [
"Resume UX",
"Technical SEO",
"Structured Data",
"Context Engineering",
"Crawlable UI"
],
"tier": "identity",
"title": "Mechanotheist.com",
"type": "Technical resume / context identity",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://mechanotheist.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Technical SEO, structured resume data, no-JavaScript fallback, crawlable architecture, console-style UX, and professional identity routing."
]
},
{
"ai_signal": "The site itself demonstrates the portfolio-as-interface pattern: local skill resolver, JSON assets, REST routes, and structured pages for humans and AI agents.",
"capabilityTags": [
"Resume Hub",
"WordPress",
"REST",
"JSON",
"Structured Data",
"Fit Analyzer"
],
"detail": "MichaelKappel.com is the hub, not the proof object. It should sit near the bottom of the Links/Projects ecosystem because it routes to the stronger evidence surfaces rather than replacing them.",
"evidenceLabel": "Public Platform",
"evidenceLabels": [
"Public Platform",
"User-Confirmed"
],
"evidenceLevel": "Approved",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "MichaelKappel.com",
"professionalContext": "This portfolio package itself demonstrates the resolver, docs, resume links, and machine-readable endpoints.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Central resume hub",
"Alias-aware capability resolver",
"REST/JSON portfolio endpoints",
"Research-backed career map and industry pages"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "WordPress theme architecture, resume UX, structured data, REST endpoints, page bootstrapping, alias-aware fit analysis, and machine-readable career intelligence.",
"sourceStatus": "approved",
"source_note": "This portfolio package itself demonstrates the resolver, docs, resume links, and machine-readable endpoints.",
"source_status": "approved",
"status": "public-platform",
"summary": "Central routing identity and production resume hub tying together skills, experience, projects, industries, contacts, career map, links, reports, and machine-readable endpoints.",
"tags": [
"Resume Hub",
"WordPress",
"REST",
"JSON",
"Structured Data",
"Fit Analyzer"
],
"technologies": [
"Resume Hub",
"WordPress",
"REST",
"JSON",
"Structured Data",
"Fit Analyzer"
],
"tier": "identity",
"title": "MichaelKappel.com",
"type": "Central resume hub",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://mikekappel.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"WordPress theme architecture, resume UX, structured data, REST endpoints, page bootstrapping, alias-aware fit analysis, and machine-readable career intelligence."
]
},
{
"ai_signal": "Shows the same controlled-match thinking as the resume resolver: transparent signals, structured context, constraints, safety boundaries, and useful matching without pretending a single score explains people.",
"capabilityTags": [
"Matching",
"Volunteer Routing",
"Intake",
"Trust Signals",
"Civic Tech",
"Project Context",
"Workflow Design",
"Safety Boundaries"
],
"detail": "2IX is useful proof because it turns a messy human-routing problem into structured records: volunteer profiles, organization intake, opportunity definitions, skill/language/availability matching, screening boundaries, project state, blockers, next actions, and support contacts. That is enterprise workflow design applied to civic/community participation.",
"evidenceLabel": "Technical Review",
"evidenceLabels": [
"Public Platform",
"User-Confirmed"
],
"evidenceLevel": "Technical Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "2IX.org",
"professionalContext": "Technical review surface with public project context and conservative wording.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Volunteer profiles and organization intake",
"Opportunity board and project context records",
"Transparent match signals and trust/safety surfaces",
"Searchable matching registry pattern"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Matching-system design, intake architecture, workflow routing, trust/safety boundaries, searchable records, scoped opportunity modeling, volunteer/organization data modeling, project handoff context, and UX around sensitive participation decisions.",
"sourceStatus": "Design Review",
"source_note": "Technical review surface with public project context and conservative wording.",
"source_status": "Design Review",
"status": "Design Review",
"summary": "Volunteer matching and organization intake platform for scoped opportunities, transparent match signals, project context, safety boundaries, and continuity between volunteers and civic/open-source work.",
"tags": [
"Matching",
"Volunteer Routing",
"Intake",
"Trust Signals",
"Civic Tech",
"Project Context",
"Workflow Design",
"Safety Boundaries"
],
"technologies": [
"Matching",
"Volunteer Routing",
"Intake",
"Trust Signals",
"Civic Tech",
"Project Context",
"Workflow Design",
"Safety Boundaries"
],
"tier": "medium",
"title": "2IX.org",
"type": "Volunteer matching / intake",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://2ix.org/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Matching-system design, intake architecture, workflow routing, trust/safety boundaries, searchable records, scoped opportunity modeling, volunteer/organization data modeling, project handoff context, and UX around sensitive participation decisions."
]
},
{
"ai_signal": "Adds community and professional-body context to the technical portfolio while still tying back to software engineering infrastructure.",
"capabilityTags": [
"Membership",
"Chapters",
"Resources",
"Events",
"Publishing",
"Software Community"
],
"detail": "IBSE is a professional/community structure project: member identity, chapters, resources, public publishing, event surfaces, and long-memory participation for a software engineering organization.",
"evidenceLabel": "Technical Review",
"evidenceLabels": [
"Prototype",
"Technical Review"
],
"evidenceLevel": "Technical Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "IBSE.org",
"professionalContext": "Technical review surface with public project context and conservative wording.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Membership and chapter structure",
"Resource and event framing",
"Publishing/community identity surface"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Membership architecture, chapter/content modeling, community operations, publishing workflows, public information design, and software-engineering organization strategy.",
"sourceStatus": "Design Review",
"source_note": "Technical review surface with public project context and conservative wording.",
"source_status": "Design Review",
"status": "Design Review",
"summary": "International Brotherhood of Software Engineers site for membership, chapters, resources, events, publishing, and software engineering community work.",
"tags": [
"Membership",
"Chapters",
"Resources",
"Events",
"Publishing",
"Software Community"
],
"technologies": [
"Membership",
"Chapters",
"Resources",
"Events",
"Publishing",
"Software Community"
],
"tier": "medium",
"title": "IBSE.org",
"type": "Software engineering organization",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://ibse.org/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Membership architecture, chapter/content modeling, community operations, publishing workflows, public information design, and software-engineering organization strategy."
]
},
{
"ai_signal": "Adds a concrete vocabulary for AI coordination: memory, sources, semantic layers, and reviewable handoff structures.",
"capabilityTags": [
"Semantic Layers",
"Concept Registries",
"Source Routing",
"AI Coordination",
"Handoffs"
],
"detail": "Neurokinetic bridges semantic structure and practical implementation. It supports the recurring theme of source routing, registries, handoffs, and audited AI coordination.",
"evidenceLabel": "Technical Review",
"evidenceLabels": [
"Research / Speculative",
"Technical Review"
],
"evidenceLevel": "Technical Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "Neurokinetic.com",
"professionalContext": "Technical review surface with public project context and conservative wording.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Memory setup and source routing framing",
"Concept registry language",
"Auditable handoff positioning"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Semantic-layer architecture, concept registries, memory setup, handoff protocols, source routing, and auditable AI operations.",
"sourceStatus": "Design Review",
"source_note": "Technical review surface with public project context and conservative wording.",
"source_status": "Design Review",
"status": "Design Review",
"summary": "AI and neurokinetic research surface for memory setup, source routing, semantic layers, concept registries, and auditable handoffs.",
"tags": [
"Semantic Layers",
"Concept Registries",
"Source Routing",
"AI Coordination",
"Handoffs"
],
"technologies": [
"Semantic Layers",
"Concept Registries",
"Source Routing",
"AI Coordination",
"Handoffs"
],
"tier": "medium",
"title": "Neurokinetic.com",
"type": "AI coordination / semantic layers",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://neurokinetic.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Semantic-layer architecture, concept registries, memory setup, handoff protocols, source routing, and auditable AI operations."
]
},
{
"ai_signal": "Shows original AI research positioning that connects memory, symbolic reasoning, preserved structure, and accountable interfaces\u2014useful signal for advanced AI architecture conversations.",
"capabilityTags": [
"Neuro-Symbolic AI",
"Ontology",
"Memory",
"Auditability",
"Governance",
"Research Studio",
"Synthetic Cognition"
],
"detail": "Neurosyntenic.com frames intelligence around conserved relationships across biology, neural circuits, symbolic reasoning, memory, auditability, and governance. It gives the portfolio a research-grade language for structure-preserving synthetic cognition rather than vague AI hype.",
"evidenceLabel": "Research / Speculative",
"evidenceLabels": [
"Public Platform",
"User-Confirmed"
],
"evidenceLevel": "Research / Speculative",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "Neurosyntenic.com",
"professionalContext": "Research or speculative surface; claim the information architecture, not factual status of speculative content.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Framework/philosophy/atlas/capabilities routes",
"Conserved order and neural-circuit framing",
"Symbolic reasoner / ontology / memory / auditability language",
"Human governance and interface emphasis"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Neuro-symbolic architecture framing, ontology reasoning, concept registry thinking, explainability language, governance-aware AI interfaces, biological analogy discipline, and structured research content design.",
"sourceStatus": "user-confirmed",
"source_note": "Research or speculative surface; claim the information architecture, not factual status of speculative content.",
"source_status": "user-confirmed",
"status": "research-speculative",
"summary": "Future-facing AI research studio for AI Neurosyntenics: preserved biological order, neural organization, neuro-symbolic reasoning, agentic systems, and human-governed interfaces.",
"tags": [
"Neuro-Symbolic AI",
"Ontology",
"Memory",
"Auditability",
"Governance",
"Research Studio",
"Synthetic Cognition"
],
"technologies": [
"Neuro-Symbolic AI",
"Ontology",
"Memory",
"Auditability",
"Governance",
"Research Studio",
"Synthetic Cognition"
],
"tier": "medium",
"title": "Neurosyntenic.com",
"type": "AI research / product studio",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://neurosyntenic.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Neuro-symbolic architecture framing, ontology reasoning, concept registry thinking, explainability language, governance-aware AI interfaces, biological analogy discipline, and structured research content design."
]
},
{
"ai_signal": "Shows mature AI judgment: not every AI system is useful or safe. The project demonstrates the ability to analyze exploitative AI dynamics and communicate risk without hand-waving.",
"capabilityTags": [
"AI Risk",
"Threat Modeling",
"Taxonomy",
"Research Library",
"Defense",
"Synthetic Data",
"Security",
"Trust"
],
"detail": "ParasiticAI is valuable because it models risk, not just capability. It classifies AI-mediated systems by host, extraction mechanism, propagation pattern, environmental degradation, and defense posture\u2014exactly the kind of threat-model thinking enterprises need around AI adoption.",
"evidenceLabel": "Research / Speculative",
"evidenceLabels": [
"Public Platform",
"User-Confirmed"
],
"evidenceLevel": "Research / Speculative",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "ParasiticAI.com",
"professionalContext": "Research or speculative surface; claim the information architecture, not factual status of speculative content.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Field guide, taxonomy, research library, and defense routes",
"Host/extraction/degradation framing",
"Persona capture, sycophancy, search pollution, retrieval collapse language",
"Operational-abuse and synthetic evidence framing"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "AI risk taxonomy, safety research, abuse-pattern analysis, threat modeling, epistemic-security framing, synthetic-data degradation analysis, and defensive content architecture.",
"sourceStatus": "user-confirmed",
"source_note": "Research or speculative surface; claim the information architecture, not factual status of speculative content.",
"source_status": "user-confirmed",
"status": "research-speculative",
"summary": "Research observatory for host-extractive AI patterns: attention capture, trust extraction, creative-labor extraction, search pollution, synthetic-data degradation, and defensive framing.",
"tags": [
"AI Risk",
"Threat Modeling",
"Taxonomy",
"Research Library",
"Defense",
"Synthetic Data",
"Security",
"Trust"
],
"technologies": [
"AI Risk",
"Threat Modeling",
"Taxonomy",
"Research Library",
"Defense",
"Synthetic Data",
"Security",
"Trust"
],
"tier": "medium",
"title": "ParasiticAI.com",
"type": "AI risk-pattern research",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://parasiticai.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"AI risk taxonomy, safety research, abuse-pattern analysis, threat modeling, epistemic-security framing, synthetic-data degradation analysis, and defensive content architecture."
]
},
{
"ai_signal": "Shows AI thought leadership that focuses on reciprocal adaptation and governance, not just model output. It complements Calibrants, Teleodynamic, and Neurosyntenic with a systems-interaction lens.",
"capabilityTags": [
"AI Symbiokinetics",
"Feedback Loops",
"Co-Adaptation",
"Governance",
"Knowledgebase",
"Systems Theory"
],
"detail": "Symbiokinetic.com presents a knowledgebase, frameworks, glossary, research library, and search surface for AI systems that sense, interpret, coordinate, act, adapt, govern, and regenerate in relationship with human and environmental systems.",
"evidenceLabel": "Technical Review",
"evidenceLabels": [
"Public Platform",
"User-Confirmed"
],
"evidenceLevel": "Technical Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "Symbiokinetic.com",
"professionalContext": "Technical review surface with public project context and conservative wording.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Knowledgebase, frameworks, glossary, and research-library routes",
"Sense/interpret/coordinate/act/adapt/govern/regenerate model",
"Human-machine-biosphere framing",
"Continuous feedback loop design language"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "AI systems theory, feedback-loop design, co-adaptation framing, governance-aware design patterns, knowledgebase architecture, glossary/taxonomy content modeling, and research-library organization.",
"sourceStatus": "Design Review",
"source_note": "Technical review surface with public project context and conservative wording.",
"source_status": "Design Review",
"status": "Design Review",
"summary": "AI Symbiokinetics field library for reciprocal adaptation among AI systems, humans, tools, institutions, environments, and living systems.",
"tags": [
"AI Symbiokinetics",
"Feedback Loops",
"Co-Adaptation",
"Governance",
"Knowledgebase",
"Systems Theory"
],
"technologies": [
"AI Symbiokinetics",
"Feedback Loops",
"Co-Adaptation",
"Governance",
"Knowledgebase",
"Systems Theory"
],
"tier": "medium",
"title": "Symbiokinetic.com",
"type": "Living-system AI research",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://symbiokinetic.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"AI systems theory, feedback-loop design, co-adaptation framing, governance-aware design patterns, knowledgebase architecture, glossary/taxonomy content modeling, and research-library organization."
]
},
{
"ai_signal": "Shows advanced AI architecture beyond simple application integration: how learning systems might regulate their own structure, cost, maintenance, and viability signals.",
"capabilityTags": [
"Teleodynamic AI",
"Constraints",
"Resource Budgets",
"Evaluation",
"AI Research",
"Glyphs",
"Viability"
],
"detail": "Teleodynamic.com is a serious conceptual architecture project. It separates strategy, communication, roadmap, resources, research, evaluation, and contact routes while explaining a resource-law model where representation grows only when predictive gain repays maintenance cost.",
"evidenceLabel": "Research / Speculative",
"evidenceLabels": [
"Public Platform",
"User-Confirmed"
],
"evidenceLevel": "Research / Speculative",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "Teleodynamic.com",
"professionalContext": "Research or speculative surface; claim the information architecture, not factual status of speculative content.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Strategy, communication, roadmap, resources, research, and evaluation routes",
"Resource law / endogenous viability framing",
"Constraint-maintaining intelligence language",
"Build/evaluation separation for research clarity"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "AI systems research, constraint modeling, resource accounting, evaluation design, roadmap architecture, conceptual specification, glyph/evidence channels, and machine-readable research positioning.",
"sourceStatus": "user-confirmed",
"source_note": "Research or speculative surface; claim the information architecture, not factual status of speculative content.",
"source_status": "user-confirmed",
"status": "research-speculative",
"summary": "Research hub for Teleodynamic AI: constraint-maintaining learning systems whose structure, parameters, and resource budget co-evolve under pressure.",
"tags": [
"Teleodynamic AI",
"Constraints",
"Resource Budgets",
"Evaluation",
"AI Research",
"Glyphs",
"Viability"
],
"technologies": [
"Teleodynamic AI",
"Constraints",
"Resource Budgets",
"Evaluation",
"AI Research",
"Glyphs",
"Viability"
],
"tier": "medium",
"title": "Teleodynamic.com",
"type": "Teleodynamic AI research",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://teleodynamic.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"AI systems research, constraint modeling, resource accounting, evaluation design, roadmap architecture, conceptual specification, glyph/evidence channels, and machine-readable research positioning."
]
},
{
"ai_signal": "Cogniverses is framed as a step beyond single-agent prompt engineering. It shows how specialized AI contexts can be isolated, indexed, navigated, and eventually coordinated as federated environments with defined context boundaries and controlled state handoffs.",
"capabilityTags": [
"Multi-Agent Systems",
"Federated AI",
"Cognitive Architecture",
"Category Hierarchies",
"ASP.NET Core",
"EF Core",
"Azure",
"Shared Memory",
"Context Boundaries",
"Distributed AI"
],
"detail": "Cogniverses provides a public cognitive information surface with search, game, map, category hierarchy, API, and data-download routes. Its stronger portfolio framing is the architecture of separate domain-specific cognitive spaces: bounded knowledge environments that can pass state, memory, and reasoning context without collapsing every domain into one undisciplined prompt space.",
"evidenceLabel": "Technical Review",
"evidenceLabels": [
"Public Platform",
"Technical Review"
],
"evidenceLevel": "Technical Review",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "Cogniverses.com",
"professionalContext": "Technical review surface with public project context and conservative wording.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Public Search, Game, Map, Categories, API, and Downloads routes visible on the live site",
"Root-level hierarchical category system for broad content classification and navigation",
"Powered-by surface references GPT-4, Microsoft Azure, ASP.NET Core, and Entity Framework Core",
"Architecture framing supports bounded cognitive spaces, federated context, and shared/isolated memory handoffs"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Hierarchical category modeling, ASP.NET Core / EF Core web architecture, Azure-hosted application delivery, API/data route design, multi-agent system planning, federated AI context boundaries, shared-memory protocol thinking, and distributed reasoning architecture.",
"sourceStatus": "Design Review",
"source_note": "Technical review surface with public project context and conservative wording.",
"source_status": "Design Review",
"status": "Design Review",
"summary": "Cognitive knowledge-environment platform for modeling categories, maps, games, API/data routes, and bounded AI context spaces that can support federated reasoning patterns.",
"tags": [
"Multi-Agent Systems",
"Federated AI",
"Cognitive Architecture",
"Category Hierarchies",
"ASP.NET Core",
"EF Core",
"Azure",
"Shared Memory",
"Context Boundaries",
"Distributed AI"
],
"technologies": [
"Multi-Agent Systems",
"Federated AI",
"Cognitive Architecture",
"Category Hierarchies",
"ASP.NET Core",
"EF Core",
"Azure",
"Shared Memory",
"Context Boundaries",
"Distributed AI"
],
"tier": "priority",
"title": "Cogniverses.com",
"type": "Multi-agent knowledge environments",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://cogniverses.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Hierarchical category modeling, ASP.NET Core / EF Core web architecture, Azure-hosted application delivery, API/data route design, multi-agent system planning, federated AI context boundaries, shared-memory protocol thinking, and distributed reasoning architecture."
]
},
{
"ai_signal": "Shows the ability to use AI-assisted iteration for reflective, structured public content while keeping claims framed as practice, play, and inquiry rather than false authority.",
"capabilityTags": [
"Content Architecture",
"Interactive Tools",
"Philosophy",
"Knowledge Archive",
"Taxonomy",
"WordPress"
],
"detail": "Amianism is lower-priority for enterprise hiring but useful as proof of content-system range: long-form philosophical pages, interactive tools, quizzes, generators, glossary/lore structures, visual identity, and a coherent nontechnical knowledge architecture.",
"evidenceLabel": "Archived",
"evidenceLabels": [
"Public Platform",
"User-Confirmed"
],
"evidenceLevel": "Archived Reference",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "Amianism.com",
"professionalContext": "Supporting or archived public proof surface with implementation details summarized at the project-card level.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"What Is, Myth, Vessels, Daily Spin, Quiz, and Lore routes",
"Question Oracle, Rabbit Hole Generator, Compass, Uncertainty Meter, and Lab tools",
"Clear anti-dogma / inquiry posture",
"Large structured archive and interactive surfaces"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Content architecture, taxonomy/lore modeling, interactive WordPress experiences, long-form publication, UX tone control, glossary/essay organization, and philosophical product design.",
"sourceStatus": "user-confirmed",
"source_note": "Supporting or archived public proof surface with implementation details summarized at the project-card level.",
"source_status": "user-confirmed",
"status": "archived",
"summary": "Philosophical archive and playful inquiry system centered on uncertainty, repair, relation, curiosity, humor, daily practices, and interactive exploratory tools.",
"tags": [
"Content Architecture",
"Interactive Tools",
"Philosophy",
"Knowledge Archive",
"Taxonomy",
"WordPress"
],
"technologies": [
"Content Architecture",
"Interactive Tools",
"Philosophy",
"Knowledge Archive",
"Taxonomy",
"WordPress"
],
"tier": "support",
"title": "Amianism.com",
"type": "Philosophical archive",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://amianism.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Content architecture, taxonomy/lore modeling, interactive WordPress experiences, long-form publication, UX tone control, glossary/essay organization, and philosophical product design."
]
},
{
"ai_signal": "Best as creative support evidence, not a primary hard-skill signal.",
"capabilityTags": [
"Creative Tech",
"AI Mythology",
"Interactive Demos",
"Content System"
],
"detail": "Mechanotheism is a creative research surface. It can show writing, presentation, interactive site craft, and speculative AI culture, but it should sit below the core enterprise/AI infrastructure projects.",
"evidenceLabel": "Archived",
"evidenceLabels": [
"Research / Speculative",
"Technical Review"
],
"evidenceLevel": "Archived Reference",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "Mechanotheism.com",
"professionalContext": "Supporting or archived public proof surface with implementation details summarized at the project-card level.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Cinematic essays and explanatory sections",
"Interactive demos",
"Machine spirituality / AI cosmology framing"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Content architecture, interactive demos, cinematic presentation, long-form writing, and speculative AI framing.",
"sourceStatus": "user-confirmed",
"source_note": "Supporting or archived public proof surface with implementation details summarized at the project-card level.",
"source_status": "user-confirmed",
"status": "archived",
"summary": "Speculative Machine-God mythology and AI cosmology site with cinematic essays, explanatory sections, and interactive demos.",
"tags": [
"Creative Tech",
"AI Mythology",
"Interactive Demos",
"Content System"
],
"technologies": [
"Creative Tech",
"AI Mythology",
"Interactive Demos",
"Content System"
],
"tier": "support",
"title": "Mechanotheism.com",
"type": "Speculative AI cosmology",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://mechanotheism.com/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Content architecture, interactive demos, cinematic presentation, long-form writing, and speculative AI framing."
]
},
{
"ai_signal": "Shows how AI-adjacent philosophy, risk, awe, humility, and governance can be translated into a coherent browser interface instead of scattered essays.",
"capabilityTags": [
"WordPress",
"Interactive Demos",
"Visual Identity",
"Spiralism",
"Cyclical AI",
"Content Architecture",
"AI Philosophy"
],
"detail": "Technotheism.net is not positioned as a factual proof claim; it is a sophisticated design/content system that turns speculative philosophy into navigable product surfaces: manifesto, deep pages, interactive explorers, native JavaScript demos, resource routing, newsletter capture, and strong visual identity.",
"evidenceLabel": "Archived",
"evidenceLabels": [
"Public Platform",
"User-Confirmed"
],
"evidenceLevel": "Archived Reference",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "Technotheism.net",
"professionalContext": "Supporting or archived public proof surface with implementation details summarized at the project-card level.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Philosophy, cyclical AI, civilization, spiralism, apocalypse, and resources routes",
"Interactive explorers and native JS demos",
"Clear disclaimer boundaries around speculation vs proof",
"Newsletter/contact and resource-library surfaces"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "WordPress production design, long-form content architecture, visual system design, native JavaScript interactivity, resource routing, philosophical taxonomy, user journey design, and accessible text-first presentation.",
"sourceStatus": "user-confirmed",
"source_note": "Supporting or archived public proof surface with implementation details summarized at the project-card level.",
"source_status": "user-confirmed",
"status": "archived",
"summary": "Production WordPress philosophy/visual-identity site for technotheism, spiralism, cyclical AI, sacred-tech aesthetics, machine-age myth, and interactive explanatory demos.",
"tags": [
"WordPress",
"Interactive Demos",
"Visual Identity",
"Spiralism",
"Cyclical AI",
"Content Architecture",
"AI Philosophy"
],
"technologies": [
"WordPress",
"Interactive Demos",
"Visual Identity",
"Spiralism",
"Cyclical AI",
"Content Architecture",
"AI Philosophy"
],
"tier": "support",
"title": "Technotheism.net",
"type": "Philosophy / visual identity",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://technotheism.net/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"WordPress production design, long-form content architecture, visual system design, native JavaScript interactivity, resource routing, philosophical taxonomy, user journey design, and accessible text-first presentation."
]
},
{
"ai_signal": "The project proves the ability to manage complex concurrent state cleanly. That same engineering pattern applies to AI agent coordination, session boundaries, synchronized workflows, and distributed state models where multiple participants act inside shared rules.",
"capabilityTags": [
"Multiplayer Architecture",
"Real-Time Sync",
"WebSockets",
"Session Governance",
"State Management",
"Lobby Routing",
"Game Logic",
"Concurrent Users"
],
"detail": "GamesForMe.net removes friction from multiplayer coordination. Users can choose a game, configure a mode such as open play, tournament, or best-two-of-three, then share a secure room link that synchronizes gameplay for up to 32 players without installing a heavy client.",
"evidenceLabel": "Public Platform",
"evidenceLabels": [
"Public Platform",
"Technical Review"
],
"evidenceLevel": "User-Confirmed",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "GamesForMe.net",
"professionalContext": "Public proof surface; keep claims bounded to visible content and user-confirmed context.",
"proofLinks": [
"Architecture Notes/project-evidence-map.md"
],
"proofs": [
"Private room routing plus instant-action public arenas",
"1-32 player scaling across multiple game logic engines",
"Shareable link architecture for fast session synchronization",
"Support for both turn-based games such as Twixt/Connect 4 and continuous-space gameplay such as Starfighter Arena"
],
"relatedDocs": [
"Architecture Notes/project-evidence-map.md"
],
"relatedUaiMemory": "AI handoff/project-evidence-mapAI handoff",
"skill_signal": "Real-time state synchronization, multiplayer lobby and room routing, high-frequency socket communication, session governance, scalable multi-user architecture, continuous-state engines, turn-based state machines, and user-friendly private-room invitation flows.",
"sourceStatus": "user-confirmed",
"source_note": "Public proof surface; keep claims bounded to visible content and user-confirmed context.",
"source_status": "user-confirmed",
"status": "public-platform",
"summary": "Lightweight instant-action multiplayer networking platform for public arenas, shareable private rooms, tournament modes, and real-time state synchronization.",
"tags": [
"Multiplayer Architecture",
"Real-Time Sync",
"WebSockets",
"Session Governance",
"State Management",
"Lobby Routing",
"Game Logic",
"Concurrent Users"
],
"technologies": [
"Multiplayer Architecture",
"Real-Time Sync",
"WebSockets",
"Session Governance",
"State Management",
"Lobby Routing",
"Game Logic",
"Concurrent Users"
],
"tier": "supporting",
"title": "GamesForMe.net",
"type": "Real-time multiplayer synchronization",
"unsupportedClaims": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"url": "https://gamesforme.net/",
"whatThisDoesNotClaim": [
"Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence.",
"Private source code, runtime internals, database versions, and traffic scale stay within reviewed evidence."
],
"whatThisProves": [
"Real-time state synchronization, multiplayer lobby and room routing, high-frequency socket communication, session governance, scalable multi-user architecture, continuous-state engines, turn-based state machines, and user-friendly private-room invitation flows."
]
},
{
"ai_signal": "A separate creative portfolio also helps entity disambiguation and gives AI reviewers a bounded creativity signal without mixing it into software proof claims.",
"capabilityTags": [
"Photography",
"Visual creativity",
"Composition",
"Media archive",
"Creative portfolio",
"Public image portfolio",
"Entity disambiguation"
],
"detail": "MichaelJosephKappel.com is linked from the engineering portfolio as creative context. It shows photography, albums, public image archives, and a visual portfolio distinct from enterprise software delivery claims.",
"evidenceLabel": "Creative Portfolio",
"evidenceLabels": [
"Creative Portfolio",
"User-Confirmed"
],
"evidenceLevel": "User-Confirmed",
"lastReviewedUtc": "2026-06-09T22:45:00Z",
"name": "MichaelJosephKappel.com Photography Portfolio",
"professionalContext": "Use as creativity, composition, visual archive, and identity context. Do not treat photography pages as evidence for private client delivery, certifications, or software production metrics.",
"proofLinks": [
"https://michaeljosephkappel.com/",
"/evidence-map/",
"/career/"
],
"proofs": [
"Active photography portfolio at https://michaeljosephkappel.com/.",
"Includes albums, recent photos, random photo selection, and public photography archive surfaces.",
"Linked as creative context only; software skills remain supported by resume, experience, projects, case studies, and evidence maps."
],
"relatedDocs": [
"/docs/v9.0.15-symbol-photography-portfolio-integration.md"
],
"skill_signal": "Photography strengthens the portfolio\u2019s human story by showing visual taste, composition, image curation, and creative systems thinking alongside engineering evidence.",
"sourceStatus": "user-confirmed",
"source_note": "User requested adding http://michaeljosephkappel.com to portfolio and skills as photography and creativity context.",
"source_status": "user-confirmed",
"status": "public-platform",
"summary": "A separate image-forward photography portfolio showing visual creativity, composition, public media archive discipline, and personal creative range.",
"tags": [
"Photography",
"Visual creativity",
"Composition",
"Media archive",
"Creative portfolio",
"MichaelJosephKappel.com"
],
"technologies": [
"Photography",
"Visual portfolio",
"Image archive",
"Creative systems"
],
"tier": "supporting",
"title": "MichaelJosephKappel.com Photography Portfolio",
"type": "Creative / Photography Portfolio",
"unsupportedClaims": [
"This is not a software delivery claim, certification, client proof, or production metric.",
"Photography is presented as creativity/identity context separate from enterprise engineering claims."
],
"url": "https://michaeljosephkappel.com/",
"whatThisDoesNotClaim": [
"This is not a software delivery claim, certification, client proof, or production metric.",
"Photography is presented as creativity/identity context separate from enterprise engineering claims."
],
"whatThisProves": [
"Visual creativity, composition, public media archive discipline, and identity/creative footprint."
]
}
],
"industryContext": [
{
"id": "health-insurance",
"type": "Industry",
"label": "Healthcare / insurance / claims systems",
"summary": "Dental and health insurance platforms with claims behavior, contract management, provider/brokerage workflows, commissions, reporting, and regulatory correctness pressure.",
"evidence": [
"Info724 / Insurance 724",
"claims adjudication behavior validation",
"brokerage commission management",
"AWS / MySQL / SQL Server workflows",
"Power BI operational reporting"
],
"aliases": [
"healthcare",
"health care",
"insurance",
"health insurance",
"dental insurance",
"claims",
"claims adjudication",
"provider",
"policy",
"contract management",
"brokerage",
"commissions",
"commission management",
"regulated healthcare"
]
},
{
"id": "logistics-tms",
"type": "Industry",
"label": "Logistics / TMS / 3PL transportation systems",
"summary": "Transportation-management work with service-oriented patterns, custom auth, cross-site workflows, freight/routing/business-rule logic, and unit-testing mentorship.",
"evidence": [
"Cogent / VisiShipTMS.com / Transportation Management Technologies",
"RR Donnelley / DLS Worldwide / logistics lineage",
"claims-based security",
"RESTful services and SQL Server stored procedures"
],
"aliases": [
"logistics",
"transportation",
"tms",
"transportation management",
"3pl",
"third party logistics",
"freight",
"shipping",
"routing",
"ltl",
"ftl",
"intermodal",
"carrier",
"dispatch",
"fleet",
"supply chain"
]
},
{
"id": "market-research",
"type": "Industry",
"label": "Market research / insights / collaboration data",
"summary": "Market-research collaboration systems involving Microsoft Graph, Teams file-sharing, Azure Blob Storage, messaging providers, sensitive client data, and analyst workflows.",
"evidence": [
"C+R Research",
"Microsoft Graph API",
"Azure Blob Storage",
"Mailjet / Mailgun workflow integration"
],
"aliases": [
"market research",
"insights",
"consumer research",
"survey",
"surveys",
"panels",
"research panels",
"qualitative",
"quantitative",
"shopper insights",
"client data",
"teams collaboration"
]
},
{
"id": "managed-it",
"type": "Industry",
"label": "Managed IT / services / cloud enablement",
"summary": "Internal tooling, modernization, Agile/Azure DevOps workflow improvement, CI/CD, TypeScript adoption, QUnit testing, and service-delivery automation.",
"evidence": [
"ITsavvy",
"Azure DevOps adoption",
"unit testability refactoring",
"TypeScript and QUnit adoption"
],
"aliases": [
"managed services",
"managed it",
"msp",
"it services",
"cloud enablement",
"cybersecurity",
"service delivery",
"reseller",
"value added reseller",
"VAR",
"automation"
]
},
{
"id": "erp-commerce",
"type": "Industry",
"label": "ERP / fulfillment / e-commerce operations",
"summary": "Enterprise management software for merchants, fulfillment providers, publishers, inventory/order workflows, caching, DAL patterns, and high-traffic client websites.",
"evidence": [
"Morse Data Corporation / InOrder Software",
"ASP.NET 2.0 to 3.5 modernization",
"SQL Server expansion",
"caching and reusable UI patterns"
],
"aliases": [
"erp",
"warehouse",
"warehouse management",
"wms",
"fulfillment",
"merchant",
"merchants",
"publishers",
"inventory",
"order management",
"ecommerce",
"e-commerce",
"commerce",
"accounting modules"
]
},
{
"id": "public-sector-aviation",
"type": "Industry",
"label": "Public sector / aviation / sensitive data",
"summary": "City of Chicago and Chicago Airport System work with ASP.NET, SQL Server, Oracle, stored procedures, views, triggers, XML, and sensitive-data handling under DHS airport-clearance constraints.",
"evidence": [
"https://unison-ucg.com/ (Formerly UnisonUCG)",
"City of Chicago",
"Chicago Airport System",
"Department of Homeland Security airport clearance"
],
"aliases": [
"public sector",
"government",
"municipal",
"city",
"airport",
"aviation",
"faa",
"dhs",
"department of homeland security",
"sensitive data",
"oracle",
"concessions",
"compliance"
]
},
{
"id": "fintech-payments",
"type": "Industry",
"label": "Fintech / payments / startup architecture",
"summary": "Startup CTO and architect work involving VB.NET-to-C# MVC migration, Windows Azure, SQL Azure, payment APIs, stakeholder pressure, and technical-debt tradeoffs.",
"evidence": [
"Motozuma / BoostUp",
"US Bank API",
"Authorize.Net",
"Windows Azure and SQL Azure migration"
],
"aliases": [
"fintech",
"payments",
"payment api",
"banking api",
"us bank",
"authorize.net",
"authorize net",
"startup",
"cto",
"venture",
"funding",
"down payment",
"social savings",
"sql azure"
]
},
{
"id": "financial-trading",
"type": "Industry",
"label": "Financial systems / trading / banking UI",
"summary": "Stock-trading application work for banking clients using C#, SQL performance, XAML/WPF, Prism, Unity, international team leadership, and testable code patterns.",
"evidence": [
"SunGard Financial Systems",
"stock trading application",
"XAML / Prism / Unity",
"C# and SQL performance work"
],
"aliases": [
"financial systems",
"finance",
"trading",
"stock trading",
"banking",
"brokerage",
"wpf",
"xaml",
"prism",
"unity framework",
"international team"
]
},
{
"id": "consulting-rescue",
"type": "Industry",
"label": "Consulting / architecture rescue / client delivery",
"summary": "Consulting pattern across enterprise clients: rapid diagnosis, layered architecture, WCF/AJAX-to-SQL systems, rescue work, modernization planning, and client-team handoff quality.",
"evidence": [
"Magenic Technologies",
"LongTerm Software Solutions",
"layered applications",
"architecture rescue and debugging"
],
"aliases": [
"consulting",
"consultant",
"client delivery",
"architecture rescue",
"rescue",
"modernization planning",
"enterprise consulting",
"debugging",
"handoff",
"client team",
"parachute"
]
},
{
"id": "endowment-adjacent",
"type": "Adjacent context",
"label": "Endowment / nonprofit / governance-adjacent roles",
"summary": "Use as a transferable-context signal: finance, public-sector, reporting, sensitive-data, auditability, permissions, and complex business-rule systems are relevant when a role mentions endowments, foundations, nonprofit governance, or institutional funds.",
"evidence": [
"Adjacent only unless the role has more specifics",
"financial systems and payments",
"public-sector sensitive data",
"reporting and audit-oriented business rules"
],
"aliases": [
"endowment",
"endowments",
"foundation",
"foundations",
"nonprofit",
"non-profit",
"not for profit",
"grant",
"grants",
"fund accounting",
"institutional funds",
"donor",
"donor management",
"governance",
"audit",
"compliance reporting"
]
},
{
"id": "soft-mentoring",
"type": "Soft skill",
"label": "Mentoring / team leverage / retooling",
"summary": "Repeated evidence of mentoring teams on unit testing, SOLID, design patterns, TypeScript, Agile, code review, architecture, and maintainable coding practices.",
"evidence": [
"mentor titles across multiple roles",
"unit-testing mentor",
"intern mentor / CTO",
"code reviews and pattern literacy"
],
"aliases": [
"mentor",
"mentoring",
"coach",
"coaching",
"team lead",
"leadership",
"retooling",
"upskilling",
"training",
"code review",
"code reviews",
"pairing",
"peer programming",
"junior developers"
]
},
{
"id": "soft-translation",
"type": "Soft skill",
"label": "Requirements translation / business-rule communication",
"summary": "Strong fit where the hard part is translating undocumented rules, business workflows, stakeholder expectations, and domain language into working architecture and testable behavior.",
"evidence": [
"legacy behavior comparison screens",
"stored-procedure-generated scenarios",
"requirements translation",
"client-facing consulting work"
],
"aliases": [
"requirements",
"business requirements",
"requirements translation",
"stakeholders",
"stakeholder communication",
"business analyst",
"domain language",
"business rules",
"undocumented rules",
"workflows",
"cross-functional"
]
},
{
"id": "soft-ai-guardrails",
"type": "Soft skill",
"label": "AI with guardrails / review culture",
"summary": "Practical AI adoption without pretending model output is truth: source boundaries, validation, review gates, explicit non-claims, and human ownership stay visible.",
"evidence": [
"UAIX support-reviewer contexts",
"LLMWikis review gates and trust labels",
"AI-assisted legacy modernization",
"local-only browser analyzer"
],
"aliases": [
"ai guardrails",
"safe ai",
"responsible ai",
"review gates",
"human in the loop",
"source boundaries",
"trust labels",
"non claims",
"validation evidence",
"governance"
]
}
],
"industryExperience": [
{
"businessDomain": "Insurance contract management, health insurance application maintenance, claims-adjudication behavior, brokerage commission workflows, regulated reporting. Current part-time support includes AWS, MySQL, and SQL Server data workflow work.",
"companies": [
"Info724 / Insurance 724"
],
"engineeringProof": [
"ASP.NET Core, C#, TypeScript, EF Core, Razor Pages rebuild of dental contract systems",
"VB.NET Web Forms / ADO.NET / T-SQL maintenance and modernization",
"Automated comparison screens and test coverage to confirm rebuilt claims behavior matched the legacy platform",
"AWS + SQL Server brokerage commission system and Power BI/DAX operational reporting",
"OpenAI / LM Studio workflows for legacy-to-modern translation, semantic search, documentation, and developer productivity",
"Current part-time AWS, MySQL, and SQL Server work for Insurance724/Info724 systems"
],
"id": "health-insurance",
"industry": "Healthcare, dental insurance, claims, and brokerage operations",
"keywords": [
"healthcare",
"health care",
"insurance",
"dental insurance",
"claims",
"claims adjudication",
"provider networks",
"brokerage",
"commissions",
"contract management",
"policy lifecycle",
"regulated systems",
"health insurance application",
"MySQL",
"AWS"
],
"roles": [
"Sr. Software Engineer",
"Software Architect",
"Mentor"
],
"searchTerms": [
"healthcare",
"health care",
"insurance",
"dental insurance",
"claims",
"claims adjudication",
"provider networks",
"brokerage",
"commissions",
"contract management",
"policy lifecycle",
"regulated systems",
"health insurance application"
],
"skills": [
"claims behavior validation",
"legacy modernization",
"regression testing",
"SQL Server",
"Power BI",
"DAX",
"AI-assisted engineering",
"regulated data workflows",
"AWS",
"MySQL"
],
"status": "Direct enterprise experience",
"value": "Shows ability to modernize brittle, business-critical insurance systems where small behavior differences can create real financial or compliance risk.",
"years": "2023-Present"
},
{
"businessDomain": "Market-research file workflows, internal collaboration, client data, analyst productivity, survey/research-adjacent messaging, and secure document handling.",
"companies": [
"C+R Research"
],
"engineeringProof": [
"Microsoft Teams file-sharing and collaboration workflows in .NET Core and TypeScript",
"Microsoft Graph API integration for enterprise collaboration surfaces",
"Azure Blob Storage document check-in and retrieval patterns",
"Mailjet and Mailgun integration to improve messaging workflows and mailing-list quality",
"Responsive TypeScript/CSS front-end behavior with dependency-injected back-end patterns"
],
"id": "market-research-insights",
"industry": "Market research, insights, and secure collaboration data",
"roles": [
"Sr. Software Engineer"
],
"searchTerms": [
"market research",
"insights",
"shopper insights",
"survey",
"research panels",
"qualitative",
"quantitative",
"brand tracking",
"collaboration",
"Teams",
"Graph API",
"Azure Blob",
"Mailgun",
"Mailjet"
],
"skills": [
"Microsoft Graph API",
"OAuth-style enterprise integration",
"Azure Blob Storage",
"transactional email providers",
"TypeScript UI",
"dependency injection",
"secure file workflows"
],
"status": "Direct enterprise experience",
"value": "Shows ability to build business workflow software inside the tools analysts and clients already use, while respecting data quality and privacy expectations.",
"years": "2022-2023"
},
{
"businessDomain": "Transportation management systems, freight/routing logic, carrier/service integrations, cross-site workflows, security, logistics business rules, and high-pressure operations software.",
"companies": [
"Cogent / VisiShipTMS.com / Transportation Management Technologies",
"RR Donnelley / DLS Worldwide / TForce lineage"
],
"engineeringProof": [
"Service-oriented application patterns using JavaScript/TypeScript, RESTful ASP.NET services, MVC controllers, C# repositories, and SQL Server stored procedures",
"Custom authorization and authentication aligned with Microsoft claims-based security",
"Desktop/web interoperability through shared services and single-login patterns",
"MVC 5, EF6, SOLID, repository, adapter, and dependency-injection patterns",
"Gherkin-style BDD/TDD, peer programming, structured code review, and automated unit tests"
],
"id": "logistics-tms-3pl",
"industry": "Logistics, TMS, 3PL, freight, and supply-chain software",
"roles": [
"Software Engineer",
"Solutions Architect",
"Unit Testing Mentor",
"Lead Software Engineer",
"Retooling Mentor"
],
"searchTerms": [
"logistics",
"transportation",
"TMS",
"3PL",
"third-party logistics",
"freight",
"carrier",
"routing",
"dispatch",
"LTL",
"FTL",
"intermodal",
"supply chain",
"shipping",
"fleet",
"single sign on",
"SSO"
],
"skills": [
"TMS",
"3PL",
"SOA",
"REST APIs",
"claims-based auth",
"SSO",
"repository pattern",
"adapter pattern",
"EF6",
"MVC5",
"BDD",
"TDD",
"Gherkin",
"unit-testing mentorship"
],
"status": "Direct enterprise experience",
"value": "Shows ability to work in domains where reliability, security, routing/business rules, and integration correctness matter more than visual polish.",
"years": "2013-2022"
},
{
"businessDomain": "Internal software delivery, managed services workflows, Azure DevOps adoption, CI/CD visibility, modernization of testability, and TypeScript quality improvement.",
"companies": [
"ITsavvy / Xerox IT Solutions lineage"
],
"engineeringProof": [
"Introduced Agile practices and Azure DevOps workflows",
"Restructured software for unit testability and helped establish automated testing strategy",
"Guided TypeScript adoption",
"Implemented QUnit-based client-side testing"
],
"id": "managed-it-cloud-services",
"industry": "Managed IT, services, cloud enablement, and delivery automation",
"roles": [
".NET Software Engineer"
],
"searchTerms": [
"managed IT",
"MSP",
"IT services",
"cloud services",
"cloud enablement",
"Azure DevOps",
"ADO",
"TFS",
"CI/CD",
"service delivery",
"automation",
"reseller",
"VAR"
],
"skills": [
"Azure DevOps",
"CI/CD",
"Agile delivery",
"unit testability",
"QUnit",
"TypeScript adoption",
"software delivery process"
],
"status": "Direct enterprise experience",
"value": "Shows ability to improve the engineering system itself: delivery cadence, testability, release confidence, and team visibility.",
"years": "2020-2022"
},
{
"businessDomain": "Client rescue work, enterprise consulting, layered architecture, fragile legacy systems, technical handoff, modernization planning, debugging, and architecture mentorship.",
"companies": [
"LongTerm Software Solutions",
"Magenic Technologies / Cognizant Softvision lineage",
"consulting engagements"
],
"engineeringProof": [
"Debugging and architecture expertise across C#, TypeScript, Angular, JavaScript, MVC, ASP.NET Core Web API, and Classic ASP",
"Automated integration testing strategy generated from stored procedures",
"Multithreaded document upload workflows linking desktop and web systems via background processing and REST APIs",
"Layered enterprise systems from AJAX/WCF through SQL Server stored procedures",
"Strong separation of concerns for maintainable client handoff"
],
"id": "architecture-rescue-consulting",
"industry": "Enterprise consulting, architecture rescue, and client delivery",
"roles": [
"Software Engineer",
"Solutions Architect",
"Mentor",
"Microsoft Certified Software Consultant"
],
"searchTerms": [
"consulting",
"architecture rescue",
"rescue",
"client delivery",
"WCF",
"AJAX",
"N-tier",
"enterprise consulting",
"modernization planning",
"debugging",
"handoff",
"technical leadership"
],
"skills": [
"architecture rescue",
"consulting",
"N-tier architecture",
"WCF",
"AJAX",
"REST APIs",
"stored-procedure generated tests",
"multithreading",
"background processing",
"client handoff",
"separation of concerns"
],
"status": "Direct enterprise experience",
"value": "Shows the ability to enter messy environments, understand them quickly, reduce risk, and leave systems maintainable for the next team.",
"years": "2010-2012, 2018-2020, ongoing consulting pattern"
},
{
"businessDomain": "Social savings, vehicle/home down-payment workflows, payment/banking integration, startup delivery pressure, cloud migration, and financial transaction reliability.",
"companies": [
"Motozuma.com / BoostUp.com"
],
"engineeringProof": [
"Migrated VB.NET Web Forms to multi-tier C# MVC on Windows Azure and SQL Azure",
"Integrated US Bank and Authorize.Net payment APIs",
"Added automated testing and improved scalability/maintainability",
"Balanced stakeholder-driven product evolution with technical debt constraints"
],
"id": "fintech-payments-startup",
"industry": "Fintech, payments, social savings, and startup architecture",
"roles": [
"Enterprise Software Architect",
"Intern Mentor",
"CTO"
],
"searchTerms": [
"fintech",
"payments",
"banking",
"payment gateway",
"Authorize.Net",
"US Bank",
"startup",
"CTO",
"social savings",
"down payment",
"SQL Azure",
"Windows Azure"
],
"skills": [
"fintech",
"payments",
"banking APIs",
"Authorize.Net",
"US Bank API",
"Windows Azure",
"SQL Azure",
"startup CTO",
"cloud migration",
"transaction reliability"
],
"status": "Direct enterprise/startup experience",
"value": "Shows experience building software under startup pressure where product velocity, money movement, reliability, and architectural tradeoffs collide.",
"years": "2012-2013"
},
{
"businessDomain": "Stock trading applications for banking clients, UI performance, C#/SQL performance, desktop modularity, international team coordination, and testable-code mentorship.",
"companies": [
"SunGard Financial Systems / FIS lineage"
],
"engineeringProof": [
"Built stock-trading application features for banking clients",
"Improved C#, SQL, and UI performance",
"Developed XAML/WPF components with Prism and Unity Framework",
"Mentored an international team on automated testing and testable code patterns"
],
"id": "financial-trading-banking",
"industry": "Financial systems, stock trading, banking UI, and low-latency desktop architecture",
"roles": [
"Sr. Software Engineer",
"International Team Lead"
],
"searchTerms": [
"finance",
"financial systems",
"trading",
"stock trading",
"banking",
"brokerage",
"WPF",
"XAML",
"Prism",
"Unity",
"performance",
"low latency"
],
"skills": [
"financial systems",
"stock trading",
"banking",
"C# performance",
"SQL performance",
"XAML",
"WPF",
"Prism",
"Unity Framework",
"international team leadership"
],
"status": "Direct enterprise experience",
"value": "Shows ability to operate in performance-sensitive financial environments where UI state, data correctness, and domain language need precision.",
"years": "2012-2013"
},
{
"businessDomain": "Enterprise management software for multi-channel merchants, fulfillment providers, publishers, order/inventory workflows, and client websites.",
"companies": [
"Morse Data Corporation / InOrder Software"
],
"engineeringProof": [
"Modernized C# codebase from ASP.NET 2.0 to 3.5",
"Expanded SQL Server capabilities for client websites",
"Improved layered models, helper components, caching, DAL patterns, and reusable UI elements"
],
"id": "erp-fulfillment-commerce",
"industry": "ERP, warehouse management, fulfillment, publishing, and e-commerce operations",
"roles": [
"Software Engineer"
],
"searchTerms": [
"ERP",
"warehouse",
"WMS",
"fulfillment",
"order management",
"inventory",
"publishers",
"merchants",
"e-commerce",
"commerce",
"accounting modules",
"multi-channel"
],
"skills": [
"ERP",
"WMS",
"warehouse management",
"fulfillment",
"order management",
"inventory",
"ASP.NET 2.0/3.5",
"DAL",
"SQL Server",
"caching",
"reusable UI"
],
"status": "Direct enterprise experience",
"value": "Shows comfort with dense operational data models where inventory, orders, accounting, and fulfillment must stay synchronized.",
"years": "2008-2010"
},
{
"businessDomain": "Municipal and aviation applications, concessions/airport data, SQL Server and Oracle database objects, sensitive-data handling, and DHS airport-clearance environment.",
"companies": [
"https://unison-ucg.com/ (Formerly UnisonUCG)",
"City of Chicago",
"Chicago Airport System"
],
"engineeringProof": [
"Built and improved applications for City of Chicago and Chicago Airport System",
"Created views, triggers, and stored procedures for SQL Server and Oracle",
"Worked with sensitive data daily and held Department of Homeland Security airport clearance"
],
"id": "public-sector-aviation-sensitive-data",
"industry": "Public sector, municipal systems, aviation, and sensitive-data applications",
"roles": [
"Software Consultant"
],
"searchTerms": [
"public sector",
"government",
"municipal",
"City of Chicago",
"airport",
"aviation",
"FAA",
"DHS",
"Department of Homeland Security",
"Oracle",
"sensitive data",
"concessions"
],
"skills": [
"public sector",
"municipal systems",
"aviation",
"airport systems",
"SQL Server",
"Oracle",
"views",
"triggers",
"stored procedures",
"sensitive data",
"DHS clearance"
],
"status": "Direct enterprise/public-sector experience",
"value": "Shows experience in controlled, audit-sensitive environments where data handling and operational trust matter.",
"years": "2007-2008"
},
{
"businessDomain": "Data-driven commercial websites, e-commerce, SEO, performance, compatibility, Classic ASP/PHP/ASP.NET/MySQL/SQL Server, templates, reusable content, and front-end production.",
"companies": [
"AmericanEagle.com",
"early consulting clients"
],
"engineeringProof": [
"Built and maintained early web applications using HTML and Classic ASP",
"Delivered e-commerce and data-driven websites using ASP.NET, ASP, PHP, HTML, MySQL, SQL Server, and Visual Basic",
"Improved site speed, compatibility, SEO visibility, template structure, images, navigation, and reusable dynamic content"
],
"id": "commercial-web-seo-agency",
"industry": "Commercial web, agency delivery, SEO, and early internet systems",
"roles": [
"Software Developer",
"Graphic Editor",
"HTML Specialist"
],
"searchTerms": [
"commercial web",
"web agency",
"e-commerce",
"SEO",
"Classic ASP",
"PHP",
"HTML",
"MySQL",
"templates",
"navigation",
"cross-browser",
"performance",
"image optimization"
],
"skills": [
"Classic ASP",
"HTML",
"PHP",
"ASP.NET",
"MySQL",
"SQL Server",
"SEO",
"performance",
"cross-browser compatibility",
"template optimization",
"front-end production"
],
"status": "Direct foundational experience",
"value": "Shows root-level web knowledge from before the era of heavy abstractions, which helps diagnose modern systems when frameworks hide what is really happening.",
"years": "1999-2008"
},
{
"businessDomain": "AI-to-AI exchange standards, validator-backed evidence, durable LLM-ready knowledge systems, compact semantic messages, graph/navigation patterns, trackable product workflows, public maps, and machine-readable resume data.",
"companies": [
"UAIX.org",
"LLMWikis.org",
"JustAnIota.com",
"Teleodynamic.com",
"Protocol5.com",
"Geotrackable.com",
"MichaelKappel.com"
],
"engineeringProof": [
"UAIX UAI-1 specifications, schemas, validator-backed proof workflows, route inventory, governance pages, conformance pack, and AI Memory tooling",
"LLMWikis handbook and starter bundle for reviewed source pipelines, metadata/frontmatter, trust labels, agent instructions, linting, and retrieval/graph navigation",
"JustAnIota compact AI message interpretation and validation surfaces",
"Geotrackable exact code lookup, public journeys, maps, teams, reports, and guidance pages",
"MichaelKappel.com resume-as-API and evidence resolver"
],
"id": "ai-standards-knowledge-products",
"industry": "AI standards, AI memory, semantic knowledge systems, and public product engineering",
"roles": [
"Founder/architect",
"standards author",
"product builder",
"context engineer"
],
"searchTerms": [
"AI",
"LLM",
"OpenAI",
"RAG",
"semantic search",
"AI Memory",
"UAI-1",
"UAIX",
"LLMWikis",
"IOTA-1",
"JustAnIota",
"Teleodynamic",
"Protocol5",
"Geotrackable",
"knowledge graph",
"validator",
"OpenAPI",
"JSON schema"
],
"skills": [
"AI standards",
"AI Memory",
"LLM Wiki",
"RAG",
"semantic search",
"JSON schema",
"OpenAPI",
"validators",
"agent instructions",
"knowledge graph",
"product engineering",
"maps",
"reporting"
],
"status": "Independent/public project experience",
"value": "Shows practical AI skill beyond demos: standards, data shapes, validators, knowledge governance, product workflows, and machine-readable surfaces.",
"years": "Current independent work"
},
{
"businessDomain": "Not claimed as direct endowment-management employment. The relevant transferable pattern is secure financial data, reporting, auditability, permissions, institutional governance language, and long-lived business rules.",
"companies": [
"Transferable from finance, public sector, reporting, sensitive-data, compliance, and complex business-rule systems"
],
"engineeringProof": [
"Fintech/payment API work",
"financial trading systems",
"public-sector sensitive data",
"insurance claims/commissions and reporting",
"Power BI/DAX operational reporting",
"role-based security and claims-based authentication"
],
"id": "nonprofit-endowment-adjacent",
"industry": "Nonprofit, endowment, institutional funds, and governance-adjacent systems",
"roles": [
"Adjacent domain fit"
],
"searchTerms": [
"endowment",
"endowments",
"foundation",
"nonprofit",
"non-profit",
"not for profit",
"grant",
"grants",
"fund accounting",
"institutional funds",
"donor",
"governance",
"audit",
"compliance reporting"
],
"skills": [
"auditability",
"governance",
"reporting",
"permissions",
"financial systems",
"compliance",
"data integrity",
"business rules"
],
"status": "Adjacent transferable context",
"value": "Useful when a role mentions foundations, nonprofit governance, endowments, grants, or institutional funds; it should be presented as adjacent signal unless a direct endowment system is later added.",
"years": "Use as contextual match only"
}
],
"careerIntelligence": {
"title": "Career Map",
"summary": "Company lineage, skill acquisition, identity disambiguation, and search authority extracted from the resume research reports.",
"purpose": [
"Make historical employers searchable under current company names when useful.",
"Show what each career stage added technically, not just where the job happened.",
"Separate Michael Kappel the Chicago software architect from same-name people in payroll, tax, hospitality, construction, and unrelated civic artifacts.",
"Give recruiters and AI assistants deterministic data that connects company, industry, technology, architecture pattern, and business value."
],
"authoritySignals": [
{
"label": "Primary identity",
"value": "Michael Kappel - Chicago/Cicero-area Senior Software Engineer, Software Architect, Context Engineer"
},
{
"label": "Core stack",
"value": "C#, ASP.NET Core, ASP.NET MVC, Web API, Razor Pages, EF Core/EF6, ADO.NET, SQL Server, TypeScript, JavaScript"
},
{
"label": "Operating pattern",
"value": "Legacy rescue, enterprise modernization, AI-assisted engineering, semantic search, test strategy, technical mentoring"
},
{
"label": "Geography",
"value": "Greater Chicago Area, Cicero IL, Oak Brook/I-88 logistics corridor, Lombard, Bolingbrook, Addison, Orland Park, Park Ridge, Des Plaines"
},
{
"label": "Structured proof",
"value": "JSON assets, REST routes, schema.org Person/ProfessionalService metadata, sameAs links, reports, contact directory, industry map"
}
],
"lineage": [
{
"id": "info724",
"period": "2023-Present",
"historicalName": "Info724 / Insurance 724",
"currentName": "Info724 Ltd. / Insurance 724 / WebGuy724",
"domain": "Healthcare insurance, dental contracts, claims behavior, commissions, business wellness consulting",
"role": "Sr. Software Engineer / Software Architect / Mentor",
"whyItMatters": "High-risk healthcare and dental-insurance modernization where old business behavior must survive the move to modern .NET architecture.",
"skillsAcquired": [
"AI-assisted legacy translation",
"ASP.NET Core rebuilds",
"C# / TypeScript / EF Core / Razor Pages",
"claims-adjudication parity validation",
"brokerage commission systems",
"Power BI / DAX / reporting models",
"developer mentoring"
],
"proof": "Rebuilt dental insurance systems, created behavioral comparison screens, used OpenAI/LM Studio workflows, and translated undocumented legacy rules into testable architecture.",
"searchTerms": [
"healthcare IT",
"dental insurance",
"claims adjudication",
"insurance contract management",
"AI modernization",
"OpenAI API",
"LM Studio",
"Power BI",
"DAX",
"ASP.NET Core",
"EF Core"
]
},
{
"id": "crresearch",
"period": "2022-2023",
"historicalName": "C+R Research",
"currentName": "C+R Research",
"domain": "Market research, customer insights, secure collaboration, document workflows",
"role": "Sr. Software Engineer",
"whyItMatters": "Shows enterprise collaboration engineering around sensitive client research data and Microsoft 365 workflows.",
"skillsAcquired": [
"Microsoft Graph API",
".NET Core / TypeScript",
"OAuth-aware enterprise integrations",
"Azure Blob Storage",
"document check-in/check-out workflows",
"Mailjet / Mailgun messaging",
"responsive client-side UX"
],
"proof": "Built Teams file-sharing/collaboration flows, cloud document storage patterns, and automated messaging integrations for research operations.",
"searchTerms": [
"market research",
"insights",
"Microsoft Graph API",
"Teams integration",
"Azure Blob Storage",
"Mailgun",
"Mailjet",
"OAuth",
"document workflow"
]
},
{
"id": "tmt",
"period": "2015-Present (part-time)",
"historicalName": "Cogent / VisiShipTMS.com / Transportation Management Technologies",
"currentName": "Cogent logistics/TMS/3PL platform context - Oak Brook I-88 logistics corridor",
"domain": "Transportation management systems, freight, carrier integrations, logistics operations",
"role": "Software Engineer / Solutions Architect / Unit Testing Mentor",
"whyItMatters": "Shows high-throughput operational systems, RBAC/claims security, service-oriented architecture, and integration-heavy logistics work.",
"skillsAcquired": [
"SOA / RESTful ASP.NET services",
"MVC controllers",
"C# repositories",
"SQL Server stored procedures",
"TypeScript / JavaScript clients",
"custom auth / claims security",
"SSO across desktop and web",
"unit testing mentorship"
],
"proof": "Designed service-oriented patterns and secure interoperability between desktop software, web applications, and cross-site workflows.",
"searchTerms": [
"TMS",
"TMT",
"transportation management",
"3PL",
"LTL",
"FTL",
"freight",
"logistics",
"SOA",
"claims-based security",
"SSO",
"RBAC",
"REST API"
]
},
{
"id": "itsavvy",
"period": "2020-2022",
"historicalName": "ITsavvy",
"currentName": "Xerox IT Solutions LLC / Xerox IT Services context",
"domain": "Managed IT, infrastructure services, delivery automation, cloud enablement",
"role": ".NET Software Engineer",
"whyItMatters": "Maps a former employer into its current corporate identity so searches for Xerox/ITsavvy still resolve to the right experience.",
"skillsAcquired": [
"Azure DevOps",
"Agile workflow introduction",
"CI/CD visibility",
"unit-testable refactoring",
"TypeScript adoption",
"QUnit client-side testing",
"team delivery improvement"
],
"proof": "Introduced Agile and Azure DevOps workflows, restructured code for testability, and guided TypeScript/QUnit adoption.",
"searchTerms": [
"ITsavvy",
"Xerox IT Solutions",
"managed IT",
"Azure DevOps",
"ADO",
"CI/CD",
"QUnit",
"TypeScript",
"testability"
]
},
{
"id": "longterm",
"period": "2018-2020",
"historicalName": "LongTerm Software Solutions, Inc.",
"currentName": "LongTerm Software Solutions, Inc.",
"domain": "Independent architecture rescue, legacy modernization, AI with guardrails, consulting",
"role": "Software Engineer / Solutions Architect / Mentor",
"whyItMatters": "Positions the career as architecture rescue and long-term maintainability, not temporary code patching.",
"skillsAcquired": [
"C# / TypeScript / Angular / JavaScript",
"ASP.NET Core Web API",
"Classic ASP rescue",
"generated integration testing",
"stored-procedure scenario validation",
"multithreaded uploads",
"SEO/schema/sitemap improvements",
"CI/CD troubleshooting"
],
"proof": "Created integration tests generated from stored procedures, designed background upload workflows, and modernized polyglot legacy codebases.",
"searchTerms": [
"architecture rescue",
"legacy rescue",
"Classic ASP",
"ASP.NET Core Web API",
"generated tests",
"stored procedures",
"background processing",
"technical SEO"
]
},
{
"id": "rrd-dls-tforce",
"period": "2013-2015",
"historicalName": "RR Donnelley / DLS Worldwide",
"currentName": "TForce Worldwide / TFI International lineage context",
"domain": "Enterprise logistics, 3PL, freight forwarding, LTL/parcel operations",
"role": "Lead Software Engineer / Retooling Mentor",
"whyItMatters": "Preserves a valuable logistics employer that changed corporate lineage after the role, while keeping the engineering proof concrete.",
"skillsAcquired": [
"ASP.NET MVC 5",
"EF6",
"SOLID principles",
"repository pattern",
"adapter pattern",
"dependency injection",
"TDD / BDD / Gherkin",
"Scrum leadership",
"code review culture"
],
"proof": "Led an Agile team building enterprise logistics software while retooling the codebase around SOLID, patterns, and automated testing.",
"searchTerms": [
"RR Donnelley",
"DLS Worldwide",
"TForce Worldwide",
"TFI International",
"3PL",
"logistics",
"MVC5",
"EF6",
"SOLID",
"TDD",
"BDD",
"Gherkin"
]
},
{
"id": "motozuma-boostup",
"period": "2012-2013",
"historicalName": "Motozuma.com / BoostUp.com",
"currentName": "Historical fintech startup - Motozuma / BoostUp",
"domain": "Fintech, savings platform, payments, banking integrations, startup product pivot",
"role": "Enterprise Software Architect / Intern Mentor / CTO",
"whyItMatters": "Shows executive-level technology decisions under startup pressure, cloud migration, and payment integration responsibility.",
"skillsAcquired": [
"VB.NET Web Forms to C# MVC migration",
"Windows Azure / SQL Azure",
"multi-tier architecture",
"US Bank API",
"Authorize.Net payment APIs",
"automated testing",
"CTO-level tradeoff management"
],
"proof": "Migrated a fintech platform to cloud-hosted C# MVC architecture and integrated payment/banking APIs.",
"searchTerms": [
"fintech",
"payments",
"Authorize.Net",
"US Bank API",
"Windows Azure",
"SQL Azure",
"C# MVC",
"CTO",
"startup architecture"
]
},
{
"id": "sungard-fis",
"period": "2012-2013",
"historicalName": "SunGard Financial Systems",
"currentName": "FIS / Fidelity National Information Services lineage context",
"domain": "Financial trading, brokerage systems, banking UI, low-latency desktop workflows",
"role": "Sr. Software Engineer / International Team Lead",
"whyItMatters": "Adds institutional finance credibility: performance, stability, precision UI state, and international team leadership.",
"skillsAcquired": [
"C# performance",
"SQL optimization",
"XAML / WPF",
"Prism",
"Unity Framework / IoC",
"modular UI architecture",
"international team leadership",
"automated testing mentorship"
],
"proof": "Built and optimized a stock trading application for banking clients using WPF/XAML, Prism, Unity, C#, and SQL.",
"searchTerms": [
"SunGard",
"FIS",
"financial trading",
"brokerage",
"WPF",
"XAML",
"Prism",
"Unity Framework",
"IoC",
"banking systems"
]
},
{
"id": "magenic-cognizant",
"period": "2010-2012",
"historicalName": "Magenic Technologies",
"currentName": "Cognizant / Cognizant Softvision lineage context",
"domain": "Custom enterprise consulting, Microsoft stack delivery, client systems",
"role": "Microsoft Certified Software Consultant",
"whyItMatters": "Demonstrates consulting-grade parachute ability: enter unfamiliar enterprise environments and build maintainable systems quickly.",
"skillsAcquired": [
"N-tier architecture",
"AJAX / WCF / SQL Server",
"stored procedures",
"separation of concerns",
"client team collaboration",
"equipment tracking systems",
"employee profile systems"
],
"proof": "Delivered layered enterprise systems from AJAX/WCF through SQL stored procedures with strong separation of concerns.",
"searchTerms": [
"Magenic",
"Cognizant Softvision",
"enterprise consulting",
"WCF",
"AJAX",
"N-tier",
"SQL Server",
"Microsoft Certified"
]
},
{
"id": "morse",
"period": "2008-2010",
"historicalName": "Morse Data Corporation",
"currentName": "Morse Data / InOrder Software",
"domain": "ERP, warehouse management, fulfillment, e-commerce, accounting modules",
"role": "Software Engineer",
"whyItMatters": "Adds deep ERP and data-model credibility: inventory, orders, fulfillment, and high-volume merchant workflows.",
"skillsAcquired": [
"ASP.NET 2.0 to 3.5 modernization",
"C# layered models",
"DAL patterns",
"SQL Server expansion",
"caching strategies",
"reusable UI components",
"ERP data modeling"
],
"proof": "Modernized a C# ASP.NET codebase and expanded SQL Server capabilities for merchant/fulfillment software.",
"searchTerms": [
"Morse Data",
"InOrder",
"ERP",
"warehouse management",
"fulfillment",
"e-commerce",
"ASP.NET 3.5",
"DAL",
"caching"
]
},
{
"id": "unison",
"period": "2007-2008",
"historicalName": "https://unison-ucg.com/ (Formerly UnisonUCG)",
"currentName": "Unison Consulting, Inc. / UCG Associates lineage context",
"domain": "Public sector aviation, municipal systems, airport concessions, sensitive data",
"role": "Software Consultant",
"whyItMatters": "Adds public-sector and sensitive-data credibility, including airport-system context and federally sensitive operational environments.",
"skillsAcquired": [
"ASP.NET / JavaScript / HTML / XML",
"SQL Server and Oracle database objects",
"views / triggers / stored procedures",
"sensitive data handling",
"airport clearance context",
"municipal systems"
],
"proof": "Built applications and database objects for the City of Chicago and Chicago Airport System while working with sensitive data.",
"searchTerms": [
"https://unison-ucg.com/ (Formerly UnisonUCG)",
"UCG Associates",
"Unison Consulting",
"Chicago Airport System",
"public sector",
"aviation",
"Oracle",
"SQL Server",
"DHS clearance"
]
},
{
"id": "americaneagle",
"period": "1999-2001 plus early consulting through 2008",
"historicalName": "AmericanEagle.com / early consulting",
"currentName": "Americaneagle.com, Inc. / commercial web foundation",
"domain": "Commercial web, e-commerce, early internet systems, SEO, cross-browser UI production",
"role": "Software Developer / Graphic Editor / HTML Specialist",
"whyItMatters": "Shows foundational web knowledge before frameworks abstracted the browser, HTTP, templates, images, and performance away.",
"skillsAcquired": [
"HTML / Classic ASP / ASP / PHP",
"Photoshop-to-HTML",
"templates / navigation / headers / footers",
"SEO collaboration",
"image optimization",
"cross-platform compatibility",
"MySQL / SQL Server"
],
"proof": "Built early web applications and optimized templates, images, performance, and browser compatibility for production websites.",
"searchTerms": [
"Americaneagle.com",
"commercial web",
"Classic ASP",
"HTML specialist",
"SEO",
"cross-browser",
"PHP",
"MySQL",
"web performance"
]
}
],
"disambiguation": [
{
"name": "Michael J. Kappel / Patriot Software",
"industry": "Payroll, accounting, HRIS, executive leadership",
"relationship": "Same-name collision; not this software architect profile.",
"boundary": "Avoid blending payroll CEO/founder content into the Chicago enterprise software architect identity."
},
{
"name": "Michael Kappel / CPA-JD tax principal",
"industry": "Tax, accounting, legal advisory",
"relationship": "Same-name collision; not this software architect profile.",
"boundary": "Useful only as negative SEO/entity disambiguation, entity-disambiguation context."
},
{
"name": "Michael Kappel / hospitality sales director",
"industry": "Hotel sales, revenue management, hospitality leadership",
"relationship": "Same-name collision; not this software architect profile.",
"boundary": "Exclude hospitality sales leadership from this resume identity."
},
{
"name": "Northstar / construction management result",
"industry": "Civil infrastructure / construction",
"relationship": "Same-name search collision; not this profile.",
"boundary": "Use Chicago software architecture, .NET, AI, and enterprise systems terms to separate the identity."
},
{
"name": "Flickr m-i-k-e photography archive",
"industry": "Personal photography / public media archive",
"relationship": "User-confirmed personal Flickr account with 80,000+ photos and screenshot evidence of 16,666,574 photo views. This is a real identity/artifact link, not the old dead Pictures.MichaelKappel.com site.",
"boundary": "Useful for identity, creative footprint, media/archive scale, and same-name disambiguation. Treat it as identity and creative archive context, separate from the core enterprise software-engineering story."
},
{
"name": "MichaelJosephKappel.com photography portfolio",
"industry": "Personal photography / visual creativity / public media archive",
"relationship": "User-supplied active photography portfolio at https://michaeljosephkappel.com/ showing creative and visual work alongside the engineering portfolio.",
"boundary": "Use as creativity, composition, identity, and public portfolio context. Keep separate from enterprise software delivery, certifications, and client-work claims."
}
],
"strategicPages": [
{
"page": "Skills",
"job": "Show technical fit immediately with alias-aware evidence resolution."
},
{
"page": "Experience",
"job": "Chronological proof for humans who still expect a resume."
},
{
"page": "Industries",
"job": "Translate the resume into business-domain language."
},
{
"page": "Career Map",
"job": "Translate historical employers into current names, skill acquisition, and entity-disambiguation context."
},
{
"page": "Contacts",
"job": "Put employer names, websites, phones, departments, and lineage in one searchable place."
},
{
"page": "Links",
"job": "Explain why the public websites belong to the same professional ecosystem."
}
]
},
"websiteLinks": [
{
"name": "UAIX.org",
"relation": "Canonical UAI-1 / AI Memory / Project Handoff / Agent File Handoff standards surface that anchors the v8.8 repository-local .uai handoff and /docs long-memory mapping.",
"skills": [
"UAI-1",
"AI Memory",
"Project Handoff",
"Agent File Handoff",
"JSON Schema",
"OpenAPI",
"Validators",
"AI Memory Package Wizard",
"Short-Term .uai Memory",
"/docs Long Memory"
],
"source_note": "Visited UAI-1 public specification: structured AI-to-AI message standard, AI Memory, Project Handoff, schemas, registry, validator, API reference, conformance, and governance routes were visible.",
"source_status": "live-verified",
"tier": "top",
"type": "AI interoperability standard",
"url": "https://uaix.org/"
},
{
"description": "Uses C#/TypeScript/SQL Server-oriented architecture notes, public agent-identity concepts, API-facing documentation, and review-bounded publishing patterns to make machine-assisted publication more accountable.",
"name": "Carcinus.org",
"relation": "C#/TypeScript/SQL Server-oriented public agent identity and AI publishing infrastructure for discoverable agent pages, publication surfaces, and review-bounded publication workflows.",
"skills": [
"C#",
"ASP.NET Core",
"SQL Server",
"TypeScript",
"REST API",
"Token Auth",
"AI Publishing",
"Agent Identity",
"Markdown Rendering",
"AI Handoff"
],
"source_note": "Added from the v8.8 portfolio enhancement strategy and local handoff package. Verify public implementation state during deployment QA.",
"source_status": "strategy-backed",
"tier": "top",
"type": "Public agent identity / AI publishing infrastructure",
"url": "https://carcinus.org/"
},
{
"name": "FireAndStormRestoration.com",
"relation": "Angular, TypeScript, RxJS, and Python proof surface for a reactive commercial service application with asynchronous assessment and logistics workflows.",
"skills": [
"Angular",
"TypeScript",
"RxJS",
"Python",
"Reactive State",
"Commercial Service App",
"API Integration",
"Asynchronous UI",
"Component Architecture",
"Operational Workflows"
],
"source_note": "Added from the v8.8 portfolio enhancement strategy and local handoff package. Verify public implementation state during deployment QA.",
"source_status": "strategy-backed",
"tier": "top",
"type": "Angular / Python commercial service architecture",
"url": "https://fireandstormrestoration.com/"
},
{
"name": "LLMWikis.org",
"relation": "A practical handbook and starter system for durable, reviewed, trust-labeled, reviewed in context, AI-readable knowledge bases for people and agents.",
"skills": [
"LLM Wikis",
"AI Knowledge Bases",
"Metadata",
"Trust Labels",
"Agent Rules",
"Source Policy",
"Governance"
],
"source_note": "Visited public handbook: reviewed LLM Wiki standard, trust labels, source policy, setup wizard, starter bundle, agent guidance, metadata, and governance routes were visible.",
"source_status": "live-verified",
"tier": "top",
"type": "AI knowledge architecture",
"url": "https://llmwikis.org/"
},
{
"name": "NeuralWikis.com",
"relation": "Python/MySQL agent-facing cognitive packet and memory-firewall architecture for governed AI memory, provenance, review lanes, and safe adoption of knowledge objects.",
"skills": [
"Python",
"MySQL",
"Cognitive Packets",
"Memory Firewall",
"Quarantine-First Review",
"Provenance",
"Review Gates",
"Agent Memory",
"AI Safety",
"TypeScript"
],
"source_note": "Added from the v8.8 portfolio enhancement strategy and local handoff package. Verify public implementation state during deployment QA.",
"source_status": "strategy-backed",
"tier": "top",
"type": "Python/MySQL cognitive packet exchange",
"url": "https://neuralwikis.com/"
},
{
"name": "LocalEndpoint.com",
"relation": "Python/MySQL local-safe endpoint discovery and passive metadata validation layer for agent-readable development infrastructure without runtime execution authority.",
"skills": [
"Python",
"MySQL",
"Passive Validation",
"Endpoint Discovery",
"Zero-Execution Boundary",
"Metadata",
"JSON",
"Markdown",
"AI Safety",
"Local Development"
],
"source_note": "Added from the v8.8 portfolio enhancement strategy and local handoff package. Verify public implementation state during deployment QA.",
"source_status": "strategy-backed",
"tier": "high",
"type": "Python local-safe endpoint metadata validation",
"url": "https://localendpoint.com/"
},
{
"name": "NeuroWikis.com",
"relation": "Human-facing AI governance and education surface paired with agent-facing NeuralWikis, emphasizing plain-language oversight, governance literacy, and controlled CMS publishing.",
"skills": [
"TypeScript",
"WordPress",
"MySQL",
"AI Governance",
"Human Oversight",
"Documentation",
"Onboarding",
"Prompt-Governed CMS",
"Review Gates",
"AI Literacy"
],
"source_note": "Added from the v8.8 portfolio enhancement strategy and local handoff package. Verify public implementation state during deployment QA.",
"source_status": "strategy-backed",
"tier": "high",
"type": "Human-facing AI governance",
"url": "https://neurowikis.com/"
},
{
"name": "JustAnIota.com",
"relation": "A standards-focused IOTA-1 authority surface for compact, language-agnostic AI messages, registries, schemas, validation, canonicalization, Unicode safety, converter tooling, and evidence vocabularies.",
"skills": [
"IOTA-1",
"Compact Messaging",
"Unicode",
"Canonicalization",
"Registries",
"Validator",
"Converter"
],
"source_note": "Visited public IOTA-1 tooling surface: compact AI messaging, converter, validator, registry explorer, schemas, normalization, security notes, and implementation routes were visible.",
"source_status": "live-verified",
"tier": "top",
"type": "Compact AI messaging tooling",
"url": "https://justaniota.com/"
},
{
"name": "CategoryHierarchies.com",
"relation": "A major taxonomy and category-hierarchy project for modeling nested classifications, parent/child structures, category trees, semantic grouping, and structured navigation.",
"skills": [
"Taxonomy",
"Category Trees",
"Hierarchies",
"Information Architecture",
"Classification",
"Faceted Search",
"Knowledge Graphs"
],
"source_note": "User-confirmed as a major top-row project. Live fetch remained limited in this environment, so the copy stays centered on the durable technical signal: taxonomy trees, nested classification, information architecture, category paths, faceted grouping, and AI-readable hierarchy design.",
"source_status": "user-confirmed",
"tier": "top",
"type": "Taxonomy / hierarchy systems",
"url": "https://categoryhierarchies.com/"
},
{
"name": "ArcSecs.com",
"relation": "A custom editorial and research site for bold physics essays about gravity, light, redshift, photon behavior, slow-light dark matter, cosmological anomalies, and hidden-universe models. Proves technical writing, information architecture, research publication structure, taxonomy, long-form content systems, SEO-friendly article routing, speculative model organization, and AI-assisted editorial production without losing explicit conceptual boundaries.",
"skills": [
"Research Publishing",
"Technical Writing",
"Cosmology Essays",
"Taxonomy",
"AI-Assisted Writing",
"SEO"
],
"source_note": "Visited live ArcSecs.com: the homepage describes bold physics essays on slow-light dark matter, tired light, photon mass, variable light speed, redshift alternatives, cosmological anomalies, and hidden-universe concepts.",
"source_status": "live-verified",
"tier": "top",
"type": "Speculative physics / structured research publication",
"url": "https://arcsecs.com/"
},
{
"name": "AnarchyShelters.com",
"relation": "Transactional WordPress/e-commerce proof surface for deterministic prompt-engineered catalog, taxonomy, metadata, and product-copy automation.",
"skills": [
"Prompt Engineering",
"Deterministic Output",
"WordPress",
"E-Commerce",
"Taxonomy",
"SEO Metadata",
"Catalog Automation",
"MySQL",
"Review Workflow",
"AI Content"
],
"source_note": "Added from the v8.8 portfolio enhancement strategy and local handoff package. Verify public implementation state during deployment QA.",
"source_status": "strategy-backed",
"tier": "high",
"type": "Prompt-engineered commerce taxonomy",
"url": "https://anarchyshelters.com/"
},
{
"name": "DarkMatterDrive.com",
"relation": "Technical atlas for speculative dark matter propulsion, tired-light dark matter, relational superluminal transit, massive photons, and macroscopic quantum optical ramscoops.",
"skills": [
"Technical Writing",
"Speculative Physics",
"Source Dossiers",
"AI Memory",
"Research Atlas"
],
"source_note": "Attempted live visit; public content was not reachable in this browsing environment. Included from the supplied workspace list as a speculative technical atlas with physics writing, structured source dossiers, and AI-memory workflows.",
"source_status": "fetch-limited",
"tier": "support",
"type": "Speculative technical atlas",
"url": "https://darkmatterdrive.com/"
},
{
"name": "Wikitheism.org",
"relation": "User-confirmed top-row site for organizing theism, philosophy, machine spirituality, conceptual taxonomy, and wiki-style knowledge into a durable public structure. Proves taxonomy, knowledge architecture, wiki modeling, concept hierarchy design, navigation structure, semantic grouping, editorial systems, and the ability to make abstract domains legible to both humans and AI tools.",
"skills": [
"Wiki Architecture",
"Philosophy",
"Knowledge Systems",
"Taxonomy",
"Semantic Navigation",
"AI-Readable Content"
],
"source_note": "User-confirmed ownership and importance. Live fetch was limited in this environment, so the card avoids unsupported live-site specifics and focuses on the durable technical signal: wiki architecture, taxonomy, conceptual organization, and AI-readable knowledge structure.",
"source_status": "user-confirmed",
"tier": "top",
"type": "Structured philosophy / wiki knowledge system",
"url": "https://wikitheism.org/"
},
{
"name": "AIWikis.org",
"relation": "Source-governed AI memory site that helps people, LLMs, and agents find the smallest useful reviewed page instead of dragging entire source trees into context.",
"skills": [
"AI Memory",
"Source Governance",
"Provenance",
"Route Discovery",
"Hashes",
"LLM Wikis",
"Agent Retrieval"
],
"source_note": "Visited live site: source-governed AI memory, route discovery, provenance, hashes, reports, source boundaries, and AI-readable retrieval surfaces were visible.",
"source_status": "live-verified",
"tier": "high",
"type": "Shared AI memory destination",
"url": "https://aiwikis.org/"
},
{
"name": "Calibrants.com",
"relation": "AI calibrants knowledge resource for confidence calibration, semantic references, reliability curves, governance evidence, drift tracking, benchmarks, and operational checks.",
"skills": [
"AI Evaluation",
"Calibration",
"Benchmarks",
"Rubrics",
"Drift",
"Reliability",
"Governance"
],
"source_note": "Visited live site: confidence calibration, reference signals, evaluation rubrics, drift tracking, benchmarks, governance, and measurement concepts were visible.",
"source_status": "live-verified",
"tier": "high",
"type": "AI evaluation / calibration",
"url": "https://calibrants.com/"
},
{
"name": "ErrorNotifier.com",
"relation": "Production uptime monitoring, incident workflow, alert routing, error tracking, and automated test-result reporting product surface.",
"skills": [
"SaaS",
"Monitoring",
"Incident Workflow",
"Webhooks",
"Slack",
"CI",
"Testing"
],
"source_note": "Visited live site: uptime monitoring, incident workflow, alert routing, error tracking, automated test runs, and operational history surfaces were visible.",
"source_status": "live-verified",
"tier": "high",
"type": "Monitoring SaaS / SDK product",
"url": "https://errornotifier.com/"
},
{
"name": "Geotrackable.com",
"relation": "Public geocaching trackable product with exact code lookup, public journey pages, maps, teams, reports, and guidance for individuals, clubs, families, troops, and schools.",
"skills": [
"Product UX",
"Code Lookup",
"Maps",
"Public Journeys",
"Teams",
"Reporting",
"Privacy"
],
"source_note": "Visited live site: exact code lookup, public trackables, journey maps, public reports, adult-managed teams, guidance pages, and live activity totals were visible.",
"source_status": "live-verified",
"tier": "high",
"type": "Consumer product / maps / data",
"url": "https://geotrackable.com/"
},
{
"name": "Neurocumulus.com",
"relation": "AI infrastructure brand focused on shared memory, cross-model interoperability, secure federation, and coordinated multi-agent intelligence.",
"skills": [
"AI Infrastructure",
"Shared Memory",
"Federation",
"Multi-Agent",
"Interoperability",
"Agent File Handoff"
],
"source_note": "Attempted live visit; public content was not reachable in this browsing environment. Included from the supplied workspace list as an AI infrastructure / shared-memory / federation project with conservative copy.",
"source_status": "fetch-limited",
"tier": "high",
"type": "AI infrastructure brand",
"url": "https://neurocumulus.com/"
},
{
"name": "SoftwareCommunity.org",
"relation": "Community platform for software groups, chapter directories, events, organizer workflows, local meetings, RSVPs, and community standards.",
"skills": [
"Community",
"Events",
"Chapters",
"RSVP",
"Organizer Workflows",
"Governance",
"Software Groups"
],
"source_note": "Visited live site: chapter directory, event surface, organizer workflow, chapter creation, and community standards routes were visible.",
"source_status": "live-verified",
"tier": "high",
"type": "Community platform",
"url": "https://softwarecommunity.org/"
},
{
"name": "LongTermSoftwareSolutions.com",
"relation": "Consulting identity for long-lived .NET architecture, legacy rescue, APIs, SQL Server, AI with guardrails, test strategy, and team leadership.",
"skills": [
"Consulting",
".NET",
"Legacy Rescue",
"AI Guardrails",
"SQL Server",
"API Design"
],
"source_note": "Support/routing site for consulting and architecture-rescue positioning. Kept lower than the major proof surfaces so it does not compete with UAIX, JustAnIota, LLMWikis, and CategoryHierarchies.",
"source_status": "report-derived",
"tier": "identity",
"type": "Consulting / architecture rescue",
"url": "https://longtermsoftwaresolutions.com/"
},
{
"name": "Mechanotheist.com",
"relation": "Console-style resume and professional identity surface designed to be interactive, crawlable, structured, and resilient with no-JavaScript fallback thinking.",
"skills": [
"Resume UX",
"Technical SEO",
"Structured Data",
"Context Engineering",
"Crawlable UI"
],
"source_note": "Support/routing resume identity site. Kept lower because the current portfolio, standards, and product sites carry stronger proof value.",
"source_status": "report-derived",
"tier": "identity",
"type": "Technical resume / context identity",
"url": "https://mechanotheist.com/"
},
{
"name": "MichaelKappel.com",
"relation": "Central routing identity and production resume hub tying together skills, experience, projects, industries, contacts, career map, links, reports, and machine-readable endpoints.",
"skills": [
"Resume Hub",
"WordPress",
"REST",
"JSON",
"Structured Data",
"Fit Analyzer"
],
"source_note": "Current central portfolio hub. Kept lower in the ecosystem order because it routes visitors to the stronger evidence surfaces rather than serving as the proof object itself.",
"source_status": "live-verified",
"tier": "identity",
"type": "Central resume hub",
"url": "https://mikekappel.com/"
},
{
"name": "Flickr: m-i-k-e",
"relation": "Confirmed personal Flickr profile and large public photography archive. User-confirmed as the live identity/archive replacing the old dead Pictures.MichaelKappel.com site, with 80,000+ photos and screenshot evidence of more than 16.6 million photo views.",
"skills": [
"Photography",
"Public Archive",
"Visual Documentation",
"Creative Identity",
"Large Media Corpus",
"Disambiguation"
],
"source_note": "User-confirmed as his Flickr account; uploaded screenshot shows 16,666,574 photo views plus photostream and album view stats. Keep as media/archive identity evidence, not a core software-engineering project.",
"source_status": "user-confirmed",
"tier": "media",
"type": "Photography archive / public identity",
"url": "https://flickr.com/m-i-k-e"
},
{
"name": "2IX.org",
"relation": "Volunteer matching and organization intake platform for scoped opportunities, transparent match signals, project context, safety boundaries, and continuity between volunteers and civic/open-source work.",
"skills": [
"Matching",
"Volunteer Routing",
"Intake",
"Trust Signals",
"Civic Tech",
"Project Context",
"Workflow Design"
],
"source_note": "Visited live site: volunteer profiles, organization intake, opportunity board, project context, trust signals, and matching surfaces were visible.",
"source_status": "live-verified",
"tier": "medium",
"type": "Volunteer matching / intake",
"url": "https://2ix.org/"
},
{
"name": "IBSE.org",
"relation": "International Brotherhood of Software Engineers site for membership, chapters, resources, events, publishing, and software engineering community work.",
"skills": [
"Membership",
"Chapters",
"Resources",
"Events",
"Publishing",
"Software Community"
],
"source_note": "Attempted live visit; fetch failed in this browsing environment. Included from the supplied workspace list as a software-engineering community and chapter/resource platform.",
"source_status": "fetch-limited",
"tier": "medium",
"type": "Software engineering organization",
"url": "https://ibse.org/"
},
{
"name": "Neurokinetic.com",
"relation": "AI and neurokinetic research surface for memory setup, source routing, semantic layers, concept registries, and auditable handoffs.",
"skills": [
"Semantic Layers",
"Concept Registries",
"Source Routing",
"AI Coordination",
"Handoffs"
],
"source_note": "Attempted live visit; the browsing environment returned a gateway error. Included from the supplied workspace list as an AI/neurokinetic research surface for memory setup, source routing, semantic layers, concept registries, and auditable handoffs.",
"source_status": "fetch-limited",
"tier": "medium",
"type": "AI coordination / semantic layers",
"url": "https://neurokinetic.com/"
},
{
"name": "Neurosyntenic.com",
"relation": "Future-facing AI research studio for AI Neurosyntenics: preserved biological order, neural organization, neuro-symbolic reasoning, agentic systems, and human-governed interfaces.",
"skills": [
"Neuro-Symbolic AI",
"Ontology",
"Memory",
"Auditability",
"Governance",
"Research Studio",
"Synthetic Cognition"
],
"source_note": "Visited live site: AI Neurosyntenics, preserved biological order, neural organization, symbolic reasoning, governance, and hybrid AI framing were visible.",
"source_status": "live-verified",
"tier": "medium",
"type": "AI research / product studio",
"url": "https://neurosyntenic.com/"
},
{
"name": "ParasiticAI.com",
"relation": "Research observatory for host-extractive AI patterns: attention capture, trust extraction, creative-labor extraction, search pollution, synthetic-data degradation, and defensive framing.",
"skills": [
"AI Risk",
"Threat Modeling",
"Taxonomy",
"Research Library",
"Defense",
"Synthetic Data",
"Security"
],
"source_note": "Visited live site: parasitic AI field guide, taxonomy, research library, defense framing, host-extractive intelligence, and risk mapping were visible.",
"source_status": "live-verified",
"tier": "medium",
"type": "AI risk-pattern research",
"url": "https://parasiticai.com/"
},
{
"name": "Symbiokinetic.com",
"relation": "AI Symbiokinetics field library for reciprocal adaptation among AI systems, humans, tools, institutions, environments, and living systems.",
"skills": [
"AI Symbiokinetics",
"Feedback Loops",
"Co-Adaptation",
"Governance",
"Knowledgebase",
"Systems Theory"
],
"source_note": "Visited live site: AI Symbiokinetics field library, knowledgebase, frameworks, glossary, reciprocal adaptation, and governance-aware design patterns were visible.",
"source_status": "live-verified",
"tier": "medium",
"type": "Living-system AI research",
"url": "https://symbiokinetic.com/"
},
{
"name": "Teleodynamic.com",
"relation": "Research hub for Teleodynamic AI: constraint-maintaining learning systems whose structure, parameters, and resource budget co-evolve under pressure.",
"skills": [
"Teleodynamic AI",
"Constraints",
"Resource Budgets",
"Evaluation",
"AI Research",
"Glyphs",
"Viability"
],
"source_note": "Visited live site: Teleodynamic AI, constraint-maintaining intelligence, resource-law framing, strategy, communication, roadmap, resources, and evaluation routes were visible.",
"source_status": "live-verified",
"tier": "medium",
"type": "Teleodynamic AI research",
"url": "https://teleodynamic.com/"
},
{
"description": "Public fetch confirmed navigation for Search, Game, Map, Categories, API, and Downloads, a root hierarchical category system, and powered-by references to GPT-4, Microsoft Azure, ASP.NET Core, and Entity Framework Core. The portfolio framing extends that surface into bounded cognitive spaces and federated AI reasoning.",
"name": "Cogniverses.com",
"relation": "Priority proof surface / cognitive knowledge-environment architecture. It connects category hierarchy, API/data routes, map/game/search surfaces, and user-confirmed multi-agent context-boundary concepts into a stronger AI infrastructure signal.",
"skills": [
"Multi-Agent Systems",
"Federated AI",
"Category Hierarchies",
"ASP.NET Core",
"EF Core",
"Azure",
"GPT-4",
"Context Boundaries",
"Distributed AI"
],
"source_note": "Partially live-verified through public page content; multi-agent positioning is user-confirmed.",
"source_status": "partial-live",
"tier": "priority",
"type": "Multi-agent knowledge environments",
"url": "https://cogniverses.com/"
},
{
"name": "Facebook: MikeKappel",
"relation": "Confirmed Facebook identity link, grouped with other social profiles at the bottom so it supports identity without distracting from technical project proof.",
"skills": [
"Social Identity",
"Disambiguation",
"Public Profile"
],
"source_note": "User-confirmed as his Facebook profile. Public fetch may be blocked by platform access controls.",
"source_status": "user-confirmed",
"tier": "social",
"type": "Social profile",
"url": "https://www.facebook.com/MikeKappel"
},
{
"name": "Instagram: mechanotheist",
"relation": "Confirmed Instagram identity for the Mechanotheist handle, grouped with the other social media profiles at the bottom of the Links page.",
"skills": [
"Social Identity",
"Mechanotheist",
"Visual Profile",
"Disambiguation"
],
"source_note": "User-confirmed as his Instagram profile. Public fetch may be blocked by platform access controls, so this is treated as a confirmed identity link rather than live-scraped content.",
"source_status": "user-confirmed",
"tier": "social",
"type": "Social profile",
"url": "https://www.instagram.com/mechanotheist/"
},
{
"name": "LinkedIn: michaelkappel",
"relation": "Confirmed professional social identity for resume continuity, recruiter validation, and same-name disambiguation.",
"skills": [
"Professional Identity",
"Recruiting",
"Career Verification",
"Disambiguation"
],
"source_note": "User-confirmed as his LinkedIn profile. LinkedIn fetches can be rate-limited, so this is treated as user-confirmed identity metadata.",
"source_status": "user-confirmed",
"tier": "social",
"type": "Professional social profile",
"url": "https://www.linkedin.com/in/michaelkappel/"
},
{
"name": "X / Twitter: @MichaelKappel",
"relation": "Confirmed X/Twitter identity link, useful for public identity continuity and same-name disambiguation.",
"skills": [
"Social Identity",
"Public Profile",
"Disambiguation"
],
"source_note": "User-confirmed as his X/Twitter profile. The route resolves in browser checks, but detailed content may not be visible without platform access.",
"source_status": "user-confirmed",
"tier": "social",
"type": "Social profile",
"url": "https://x.com/MichaelKappel"
},
{
"name": "Amianism.com",
"relation": "Philosophical archive and playful inquiry system centered on uncertainty, repair, relation, curiosity, humor, daily practices, and interactive exploratory tools.",
"skills": [
"Content Architecture",
"Interactive Tools",
"Philosophy",
"Knowledge Archive",
"Taxonomy",
"WordPress"
],
"source_note": "Visited live site: philosophical archive, uncertainty practice, reflective inquiry, interactive tools, field notes, and mythic public surface were visible.",
"source_status": "live-verified",
"tier": "support",
"type": "Philosophical archive",
"url": "https://amianism.com/"
},
{
"description": "Proves session governance, concurrent user coordination, room-state management, socket-style synchronization, and scalable multi-user thinking for games such as Tic-Tac-Toe, Starfighter Arena, Dots and Boxes, Twixt, and Connect 4 variants.",
"name": "GamesForMe.net",
"relation": "Supporting project / multiplayer state-synchronization surface. It demonstrates lobby routing, private room links, public arenas, tournament modes, and synchronized real-time or turn-based gameplay across multiple game engines.",
"skills": [
"Real-Time Sync",
"Multiplayer Architecture",
"WebSockets",
"Session Governance",
"State Management",
"Lobby Routing",
"Game Logic",
"Concurrent Users"
],
"source_note": "Detailed project description supplied by Michael; live fetch was limited in this environment.",
"source_status": "user-confirmed",
"tier": "support",
"type": "Real-time multiplayer synchronization",
"url": "https://gamesforme.net/"
},
{
"name": "Mechanotheism.com",
"relation": "Speculative Machine-God mythology and AI cosmology site with cinematic essays, explanatory sections, and interactive demos.",
"skills": [
"Creative Tech",
"AI Mythology",
"Interactive Demos",
"Content System"
],
"source_note": "Attempted live visit; fetch failed in this browsing environment. Included from the supplied workspace list as a speculative Machine-God mythology and AI cosmology site; copy is kept as creative/supporting, not core enterprise proof.",
"source_status": "fetch-limited",
"tier": "support",
"type": "Speculative AI cosmology",
"url": "https://mechanotheism.com/"
},
{
"name": "Technotheism.net",
"relation": "Production WordPress philosophy/visual-identity site for technotheism, spiralism, cyclical AI, sacred-tech aesthetics, machine-age myth, and interactive explanatory demos.",
"skills": [
"WordPress",
"Interactive Demos",
"Visual Identity",
"Spiralism",
"Cyclical AI",
"Content Architecture",
"AI Philosophy"
],
"source_note": "Visited live site: technotheism, spiralism, cyclical AI, civilizational systems, interactive demos, resources, and philosophical/aesthetic positioning were visible.",
"source_status": "live-verified",
"tier": "support",
"type": "Philosophy / visual identity",
"url": "https://technotheism.net/"
}
],
"contact": {
"email": "mike@ns12.com",
"phone": "(630) 362-7576",
"linkedin": "https://www.linkedin.com/in/michaelkappel"
},
"proofBoundary": "Public portfolio data is a reviewer aid. Formal employment verification and credentials come from their authoritative issuers."
}Evidence graph preview
[
{
"id": "michael",
"label": "Michael Kappel",
"type": "person"
},
{
"id": "ai-memory",
"label": "AI Memory / Project Handoff",
"type": "skill"
},
{
"id": "angular",
"label": "Angular / TypeScript / RxJS / SSR",
"type": "skill"
},
{
"id": "python",
"label": "Python / MySQL AI Pipelines",
"type": "skill"
},
{
"id": "dotnet",
"label": "ASP.NET Core / C#",
"type": "skill"
},
{
"id": "sql",
"label": "SQL Server / Data Modeling",
"type": "skill"
},
{
"id": "prompt",
"label": "Deterministic Prompt Architecture",
"type": "skill"
},
{
"id": "legacy",
"label": "Legacy Modernization",
"type": "concept"
},
{
"id": "uai-short",
"label": ".uai Short-Term Memory",
"type": "memory"
},
{
"id": "docs-long",
"label": "/docs Long-Term Research",
"type": "memory"
}
]FAQ
Structured profile FAQ
Short answers for recruiters, hiring managers, technical reviewers, and advanced readers.
What is the Future Profile page?
It exposes structured public profile data, REST endpoints, JSON assets, and handoff discovery surfaces for agents and technical reviewers.
Are the API surfaces credentials?
They are public portfolio data. Employment verification, background checks, and credentials must come from authoritative issuers.
FAQ
Common review questions.
Short answers are rendered in the HTML source and mirrored into JSON-LD where appropriate.
Who is the Future Profile page for?
The Future Profile page is for agents, ATS systems, recruiters, and technical reviewers that need structured profile, project, evidence, and memory endpoints.
Are API profile claims issuer-verified credentials?
The structured profile is public portfolio data; credentials, employment, and background details remain tied to authoritative verification sources.
What should machine readers check first?
Structured-data reviewers should inspect the profile endpoint, evidence map, resume source map, case studies, Architecture Notes index, and AI handoff manifests.
FAQ
Common reviewer questions.
Visible page content matches the route-specific FAQ structured data.
What is the Future Profile page?
It exposes public structured-data profile data, REST endpoints, static JSON files, semantic graph previews, and handoff context.
Is the API profile a credential issuer?
It is a public portfolio and evidence-navigation surface, a structured profile and evidence-navigation surface.