Capability proof
Project cards map to evidence labels, proof links, and technical context.
| Capability | Evidence | Where to review | Evidence label | Reviewer note |
|---|---|---|---|---|
| .NET / SQL modernization | Clean resume baseline, experience page, career map, and modernization role lane. | /career/ /experience/ /dotnet-sql-modernization/ Architecture notes | Enterprise Validated | Public summaries protect private source code, client data, scale details, and proprietary schema. |
| Angular / TypeScript / RxJS | Angular is user-confirmed at Info724 through an AI documentation review app and at LongTerm through corporate tax accounting software; Modern Angular/RxJS material adds current framework fluency for technical reviewers. | /angular-python-architecture/ /case-studies/angular-python-architecture/ Architecture notes Architecture notes /examples/angular22-rxjs-enterprise/README.md | Confirmed Experience | Confirmed Angular delivery is tied to Info724 and LongTerm; Modern Angular/RxJS material communicates current framework fluency. |
| Python AI/data service boundaries | Python is positioned for metadata validation, enrichment, extraction, and evidence-supported AI/data pipeline work. | /python-ai-data-pipelines/ /ai-prompt-architecture/ Architecture notes /examples/angular22-rxjs-enterprise/backend-reference/README.md | Current Architecture Work | Python examples communicate service-boundary patterns, validation, and AI/data workflow design. |
| AI memory / handoff / prompt architecture | UAIX, LLMWikis, AI handoff files, portfolio notes, architecture notes, and quality checkpoints. | /ai-memory-handoff/ /ai-prompt-architecture/ Architecture notes Architecture notes | Confirmed Experience | Memory and handoff artifacts show how context, review, and delivery continuity are organized. |
| Technical mentoring / legacy rescue | Resume-supported mentoring, testing, SOLID, design-pattern, Agile, and modernization work across multiple roles. | /career/ /career-summary/ /experience/ /resume/ | Enterprise Validated | Career evidence stays aligned to reviewed resume and experience material. |
Selected projects and full inventory
This route starts with a short hiring-review set, then keeps the broader project inventory available with source labels, status labels, and conservative reviewer notes.
Selected Projects
Four entries stay above the full archive so recruiters and hiring managers do not have to sort every public platform, prototype, and research surface first.
Runtime and observability family
These entries keep the new runtime domains easy to scan without turning the full archive into a sorting exercise. Evidence labels stay conservative when public source proof is still review-stage.
Static public observatory guidance for viability nodes, work observation, source routing, memory disposition, endpoint boundaries, repair paths, and exit conditions.
C#/.NET developer portal for transparent local GGUF interfaces around UAIX.LmRuntime, LocalEndpoint boundaries, runtime evidence, and roadmap proof gates.
Vendor-neutral AI runtime architecture reference for the execution stack between model artifacts and reliable production behavior.
Machine Intelligence Runtime reference for governing intelligence while it runs through tools, memory, policy, approvals, recovery, and evidence.
UAIX.LmRuntime documentation and package surface for local GGUF and LLaMA runtime packages for .NET with managed CPU execution and explicit backend contracts.
Rust-oriented machine-intelligence framework and knowledge base for small models, local runtimes, reproducible evaluation, and systems engineering practice.
Capability proof map
Use these lanes as the fast read before scanning every project card. They connect the archive to the resume without turning the page into a loose keyword list.
UAIX, LLMWikis, NeuralWikis, and ModelBreeder cover memory, prompt architecture, model ecology, evidence gates, and reviewed handoff.
ASP.NET Core, C#, Web API, Razor Pages, EF Core, ADO.NET, SQL Server, stored procedures, parity validation, reporting, Power BI, and DAX.
TypeScript contracts, Angular/RxJS capability lanes, browser-local tooling, component architecture, and API-facing UI workflows.
Local model runtimes, Rust/WASM browser harnesses, GGUF-facing roadmap boundaries, package surfaces, and observable proof states.
Structured routes, llms.txt, evidence maps, ethical SEO/AEO/GEO guidance, and public pages that let humans and AI systems verify claims.
MichaelJosephKappel.com stays clearly framed as photography, composition, and media archive context outside the core software claim lane.
Priority proof surface / AI interoperability standard
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.
Reviewer note: Public platform and AI memory / handoff standards surface.
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.
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.
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.
Priority proof surface / Public agent identity / AI publishing infrastructure
C#/TypeScript/SQL Server-oriented public agent identity and AI publishing infrastructure for discoverable agent pages, publication surfaces, and review-bounded publication workflows.
Reviewer note: Public agent identity / infrastructure-scale concept from strategy direction; treat runtime/database details as review-stage when confirmed.
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.
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.
Shows AI infrastructure beyond chat: identity, publishing, memory-adjacent artifacts, and reviewable public surfaces that agents can read without receiving unsafe execution authority.
Priority proof surface / Angular / Python commercial service architecture
Angular, TypeScript, RxJS, and Python proof surface for a reactive commercial service application pattern with asynchronous assessment and logistics workflow concepts.
Reviewer note: Angular/Python proof lane supports technical review. Specific Angular version details are included only when confirmed by project metadata.
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.
Angular component architecture, TypeScript contracts, RxJS state management, asynchronous API UI patterns, Python service integration, and commercial workflow modeling.
Demonstrates AI-assisted commercial application framing where Python pipelines and Angular interfaces turn domain intake into structured, reviewable, operator-facing outputs.
Priority proof surface / AI knowledge architecture
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.
Reviewer note: Public LLM Wiki handbook and durable AI-ready knowledge systems surface.
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.
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.
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.
Priority proof surface / Python/MySQL cognitive packet exchange
Python/MySQL agent-facing cognitive packet and memory-firewall architecture for governed AI memory, provenance, review lanes, and safe adoption of knowledge objects.
Reviewer 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.
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.
Python AI pipeline orchestration, MySQL state, cognitive packet design, memory firewall logic, provenance review, and type-safe handoff surfaces.
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.
High-signal project / Adaptive AI / model ecology curriculum
Adaptive AI and model-ecology reference site explaining how model populations, evaluation gates, lineage, resource accounting, and safety boundaries can make generative systems more reliable.
Reviewer note: Public research/curriculum site for adaptive AI and model ecology concepts. Use as a conservative AI architecture proof surface; do not infer private training pipelines, deployed model-breeding products, or production customer adoption from the public page alone.
ModelBreeder.com presents adaptive AI systems as populations that need evaluation, lineage, resource accounting, and safety gates. The public site is a file-backed PHP research and curriculum surface, so the portfolio treats it as an AI architecture and educational proof lane rather than a claim of private model training infrastructure.
Adaptive AI architecture, evolutionary model selection concepts, evaluation workflow design, model lineage, resource/cost boundaries, safety gates, public technical explanation, and file-backed PHP site delivery.
Frames model improvement as a governed ecology: variation, selection, evaluation, lineage, resource cost, safety boundaries, and source integrity are visible parts of the architecture rather than hidden prompt magic.
High-signal project / Python local-safe endpoint metadata validation
Python/MySQL local-safe endpoint discovery and passive metadata validation layer for agent-readable development infrastructure without runtime execution authority.
Reviewer note: Python / MySQL passive-validation and endpoint-boundary proof lane derived from strategy direction; execution authority is outside the portfolio wording.
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.
Python validation logic, passive metadata inspection, JSON/Markdown output, zero-execution security boundaries, MySQL-backed state, and local development safety.
Provides a concrete AI safety pattern: allow agents to understand local capabilities while withholding dangerous action rights and private environment details.
High-signal project / Viability Node Work Observatory
Static public observatory guidance for viability nodes, work observation, source routing, memory disposition, endpoint boundaries, repair paths, and exit conditions.
VNWO.com gives the portfolio a governance and observability proof surface: it explains how agents, endpoints, memory packets, organizations, and workflows can be inspected, dispositioned, repaired, or exited without widening authority beyond evidence.
Governance architecture, source routing, claim-boundary documentation, public schema/tooling guidance, decision receipts, no-op reasoning, accessibility-aware participation design, and evidence-first system review.
Shows agentic work treated as observable work: actors, authority, memory, endpoint boundaries, no-op decisions, repair paths, and exit rights are made explicit before claims expand.
High-signal project / C# local GGUF runtime developer portal
C#/.NET developer portal for transparent local GGUF interfaces around UAIX.LmRuntime, LocalEndpoint boundaries, runtime evidence, and roadmap proof gates.
GGUFRuntime.com is positioned as a roadmap and documentation surface for local GGUF UI work: trusted file selection, metadata/tensor inspection, tokenizer visibility, bounded generation, backend diagnostics, and host-owned authority remain separated from model acquisition or hidden provider fallback.
C#/.NET runtime architecture, local model boundary design, package-layer explanation, file verification, GGUF metadata inspection, backend evidence states, cross-platform host planning, and fail-closed runtime UX.
Demonstrates a strict evidence-before-claims pattern for local model execution: registration, probing, selection, and actual inference proof are kept as separate states.
Supporting project / AI runtime architecture reference
Vendor-neutral AI runtime architecture reference for the execution stack between model artifacts and reliable production behavior.
Reviewer note: Use ARuntime.com as a public architecture reference for runtime taxonomy, control boundaries, and evidence-first AI system design. It is an editorial framework, not a formal standard or product endorsement.
ARuntime.com maps AI runtime layers from hardware and kernels through compilers, inference engines, serving, distributed execution, browser/edge patterns, and agentic controls. It gives the portfolio a public architecture surface for explaining how runtime categories, request execution, model execution, evidence, security, and governance fit together.
AI runtime taxonomy, reference architecture, execution-layer decomposition, model-serving boundaries, distributed inference, browser and edge runtime patterns, runtime contracts, benchmarking, observability, and governance-aware documentation.
Shows model execution and request execution as separate paths that intersect through runtime services, evidence, tool policy, memory, and reviewable control-plane decisions.
Supporting project / Machine intelligence runtime reference
Machine Intelligence Runtime reference for governing intelligence while it runs through tools, memory, policy, approvals, recovery, and evidence.
Reviewer note: Use MiRuntime.com for machine-intelligence runtime control-plane concepts and implementation guidance. Keep wording bounded to an emerging architecture reference unless implementation evidence supports a stronger claim.
MiRuntime.com documents the runtime layer after the model: an execution control plane between applications and model inference. It focuses on agents, tools, memory, policy enforcement, approvals, recovery, evidence, local-first control, and lifecycle boundaries for reviewable AI work.
Agentic control-plane architecture, typed tool contracts, memory and evidence ledgers, security and governance, local-first runtime control, recovery design, runtime intelligence, lifecycle state, and implementation checklists.
Frames AI execution as observable, constrained, recoverable, and reviewable while it runs, with authority, evidence, and lifecycle control separated from raw model inference.
Supporting project / .NET local LLM runtime package surface
UAIX.LmRuntime documentation and package surface for local GGUF and LLaMA runtime packages for .NET with managed CPU execution and explicit backend contracts.
Reviewer note: Use LMRuntime.com as the concrete package/documentation surface for the UAIX.LmRuntime family. Keep package version metadata on NuGet instead of hard-coding it into the portfolio.
LMRuntime.com is the concrete UAIX.LmRuntime documentation surface for local GGUF and LLaMA packages. It explains LocalEndpoint application integration, package selection, verified local model intake, backend registration, native-asset boundaries, runtime capabilities, project status, benchmarks, security, release discipline, and NuGet package routing.
.NET package architecture, local GGUF runtime integration, LocalEndpoint facade design, backend contracts, tokenizer/sampling/model package layering, native asset boundaries, runtime capabilities, project governance, and documentation that separates shipped packages from host responsibilities.
Connects public NuGet packages to a local-only runtime story with explicit non-claims: no provider API, no model downloader, no telemetry, and source-reviewed local GGUF inputs.
High-signal project / Rust AI runtime framework and knowledge base
Rust-oriented machine-intelligence framework and knowledge base for small models, local runtimes, reproducible evaluation, and systems engineering practice.
MiRust.com is the Rust-facing public anchor for the runtime family. It is currently a compact documentation/status surface, so the portfolio treats it as a public project direction plus source-adjacent knowledge base rather than a production runtime claim.
Rust systems architecture, local model runtime planning, WebAssembly/browser harness thinking, reproducible evaluation, small-model ergonomics, and technical documentation for developer-facing AI infrastructure.
Connects the GGUF.MiRust.com Rust workspace and in-browser tiny-model runtime work to a public domain while keeping shipped-capability claims behind source and test evidence.
High-signal project / Human-facing AI governance
Human-facing AI governance and education surface paired with agent-facing NeuralWikis, emphasizing plain-language oversight, governance literacy, and controlled CMS publishing.
Reviewer note: Human governance and AI education proof lane derived from strategy direction; is available as a technical review surface before implementation details are elevated.
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.
TypeScript-governed content architecture, WordPress/MySQL extension patterns, human oversight design, AI governance communication, and dual-channel documentation.
Shows that agent-facing AI memory needs a human-readable control surface, not only hidden machine-to-machine exchange.
Priority proof surface / Compact AI messaging tooling
A standards-focused IOTA-1 authority surface for compact, language-agnostic AI messages, registries, schemas, validation, canonicalization, Unicode safety, converter tooling, and evidence vocabularies.
Reviewer note: Public protocol evidence surface for compact messaging and canonicalization.
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.
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.
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.
Priority proof surface / Taxonomy / hierarchy systems
Major taxonomy and category-hierarchy project for nested classification, parent-child trees, semantic grouping, navigation paths, and AI-readable organizational structures.
Reviewer note: Taxonomy and hierarchy proof surface; claim is data modeling and information architecture.
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.
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.
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.
Priority proof surface / Speculative physics / structured research publication
Structured research publication surface for long-form semantic grouping, speculative technical essays, and prompt-engineered research packaging.
Reviewer note: Structured research publication surface; technical claim is content architecture and research packaging.
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.
AI-assisted structured research publication, taxonomy mapping, semantic grouping, WordPress/MySQL content architecture, and long-form technical writing automation.
Demonstrates deterministic prompt architecture for organizing complex research into durable public structures with explicit conceptual boundaries.
High-signal project / Prompt-engineered commerce taxonomy
Transactional WordPress/e-commerce proof surface for deterministic prompt-engineered catalog, taxonomy, metadata, and product-copy automation.
Reviewer note: Prompt-architecture and taxonomy automation concept from strategy direction; public project context and conservative implementation wording.
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.
Prompt architecture, e-commerce taxonomy, WordPress/MySQL content automation, structured JSON-style output expectations, and deterministic catalog generation.
Shifts prompt engineering from ad-hoc chat to repeatable content architecture with explicit output shape, review boundary, and business-facing use.
High-signal project / Speculative technical atlas
Speculative technical atlas used as proof of constrained AI-assisted research packaging, semantic grouping, and complex knowledge navigation.
Reviewer note: Speculative technical atlas and research-packaging surface; present subject matter as research packaging and content architecture.
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.
Prompt-engineered long-form content architecture, taxonomy design, source-aware research packaging, WordPress publishing, and semantic navigation.
Shows how dense speculative material can be converted into structured dossiers through constrained AI workflows and human review.
Priority proof surface / Structured philosophy / wiki knowledge system
User-confirmed top-row site for organizing theism, philosophy, machine spirituality, conceptual taxonomy, and wiki-style knowledge into a durable public structure.
Reviewer note: Structured research/publication surface; claim is durable organization of abstract material.
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.
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.
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.
High-signal project / Shared AI memory destination
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.
Reviewer note: Technical review surface with public project context and conservative wording.
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.
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.
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.
High-signal project / AI evaluation / calibration
AI calibrants knowledge resource for confidence calibration, semantic references, reliability curves, governance evidence, drift tracking, benchmarks, and operational checks.
Reviewer note: Technical review surface with public project context and conservative wording.
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.
AI evaluation, confidence calibration, benchmark design, rubric design, reliability engineering, drift response, semantic reference modeling, measurement loops, governance evidence, and operational AI QA.
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.
High-signal project / Monitoring SaaS / SDK product
Production uptime monitoring, incident workflow, alert routing, error tracking, and automated test-result reporting product surface.
Reviewer note: Technical review surface with public project context and conservative wording.
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.
SaaS architecture, observability, incident lifecycle design, alert routing, webhook security, SDK packaging, CI/test reporting, audit history, onboarding UX, and production reliability engineering.
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.
High-signal project / Consumer product / maps / data
Public geocaching trackable product with exact code lookup, public journey pages, maps, teams, reports, and guidance for individuals, clubs, families, troops, and schools.
Reviewer note: AI-assisted product concept and public journey/storytelling surface; present as as external client production with confirmed context.
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.
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.
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.
High-signal project / AI infrastructure brand
AI infrastructure brand focused on shared memory, cross-model interoperability, secure federation, and coordinated multi-agent intelligence.
Reviewer note: Technical review surface with public project context and conservative wording.
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.
AI infrastructure framing, federation concepts, multi-agent coordination, shared-memory design, interoperability language, and platform architecture.
Pushes the public portfolio beyond prompt engineering into distributed AI-system design and coordinated memory structures.
High-signal project / Community platform
Community platform for software groups, chapter directories, events, organizer workflows, local meetings, RSVPs, and community standards.
Reviewer note: Public proof surface; keep claims bounded to visible content and user-confirmed context.
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.
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.
Supports the human side of AI and software: communities need structured continuity, events, standards, and chapter workflows just like codebases need memory and governance.
Identity / routing support / Consulting / architecture rescue
Consulting identity for long-lived .NET architecture, legacy rescue, APIs, SQL Server, AI with guardrails, test strategy, and team leadership.
Reviewer note: Technical review surface with public project context and conservative wording.
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.
.NET architecture, legacy modernization, API design, SQL Server, AI guardrails, testing strategy, team mentoring, and business-facing consulting positioning.
Connects AI with guardrails to enterprise modernization without letting it overpower the core standards/product projects.
Identity / routing support / Technical resume / context identity
Console-style resume and professional identity surface designed to be interactive, crawlable, structured, and resilient with no-JavaScript fallback thinking.
Reviewer note: Technical review surface with public project context and conservative wording.
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 MikeKappel.com is the primary hub.
Technical SEO, structured resume data, no-JavaScript fallback, crawlable architecture, console-style UX, and professional identity routing.
Supports AI-readability and identity disambiguation but should not compete with the main project proof surfaces.
Identity / routing support / Central resume hub
Central routing identity and production resume hub tying together skills, experience, projects, industries, contacts, career map, links, reports, and machine-readable endpoints.
Reviewer note: This portfolio package itself demonstrates the resolver, docs, resume links, and structured portfolio endpoints.
MikeKappel.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.
WordPress theme architecture, resume UX, structured data, REST endpoints, page bootstrapping, alias-aware fit analysis, and machine-readable career intelligence.
The site itself demonstrates the portfolio-as-interface pattern: local skill resolver, JSON assets, REST routes, and structured pages for humans and AI agents.
Supporting project / Volunteer matching / intake
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.
Reviewer note: Technical review surface with public project context and conservative wording.
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.
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.
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.
Supporting project / Software engineering organization
International Brotherhood of Software Engineers site for membership, chapters, resources, events, publishing, and software engineering community work.
Reviewer note: Technical review surface with public project context and conservative wording.
IBSE is a professional/community structure project: member identity, chapters, resources, public publishing, event surfaces, and long-memory participation for a software engineering organization.
Membership architecture, chapter/content modeling, community operations, publishing workflows, public information design, and software-engineering organization strategy.
Adds community and professional-body context to the technical portfolio while still tying back to software engineering infrastructure.
Supporting project / AI coordination / semantic layers
AI and neurokinetic research surface for memory setup, source routing, semantic layers, concept registries, and auditable handoffs.
Reviewer note: Technical review surface with public project context and conservative wording.
Neurokinetic bridges semantic structure and practical implementation. It supports the recurring theme of source routing, registries, handoffs, and audited AI coordination.
Semantic-layer architecture, concept registries, memory setup, handoff protocols, source routing, and auditable AI operations.
Adds a concrete vocabulary for AI coordination: memory, sources, semantic layers, and reviewable handoff structures.
Supporting project / AI research / product studio
Future-facing AI research studio for AI Neurosyntenics: preserved biological order, neural organization, neuro-symbolic reasoning, agentic systems, and human-governed interfaces.
Reviewer note: Research or speculative surface; claim the information architecture, not factual status of speculative content.
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.
Neuro-symbolic architecture framing, ontology reasoning, concept registry thinking, explainability language, governance-aware AI interfaces, biological analogy discipline, and structured research content design.
Shows original AI research positioning that connects memory, symbolic reasoning, preserved structure, and accountable interfaces—useful signal for advanced AI architecture conversations.
Supporting project / AI risk-pattern research
Research observatory for host-extractive AI patterns: attention capture, trust extraction, creative-labor extraction, search pollution, synthetic-data degradation, and defensive framing.
Reviewer note: Research or speculative surface; claim the information architecture, not factual status of speculative content.
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—exactly the kind of threat-model thinking enterprises need around AI adoption.
AI risk taxonomy, safety research, abuse-pattern analysis, threat modeling, epistemic-security framing, synthetic-data degradation analysis, and defensive content architecture.
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.
Supporting project / Living-system AI research
AI Symbiokinetics field library for reciprocal adaptation among AI systems, humans, tools, institutions, environments, and living systems.
Reviewer note: Technical review surface with public project context and conservative wording.
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.
AI systems theory, feedback-loop design, co-adaptation framing, governance-aware design patterns, knowledgebase architecture, glossary/taxonomy content modeling, and research-library organization.
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.
Supporting project / Teleodynamic AI research
Research hub for Teleodynamic AI: constraint-maintaining learning systems whose structure, parameters, and resource budget co-evolve under pressure.
Reviewer note: Research or speculative surface; claim the information architecture, not factual status of speculative content.
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.
AI systems research, constraint modeling, resource accounting, evaluation design, roadmap architecture, conceptual specification, glyph/evidence channels, and machine-readable research positioning.
Shows advanced AI architecture beyond simple application integration: how learning systems might regulate their own structure, cost, maintenance, and viability signals.
Project / Multi-agent knowledge environments
Cognitive knowledge-environment platform for modeling categories, maps, games, API/data routes, and bounded AI context spaces that can support federated reasoning patterns.
Reviewer note: Technical review surface with public project context and conservative wording.
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.
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.
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.
Creative / research support / Philosophical archive
Philosophical archive and playful inquiry system centered on uncertainty, repair, relation, curiosity, humor, daily practices, and interactive exploratory tools.
Reviewer note: Supporting or archived public proof surface with implementation details summarized at the project-card level.
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.
Content architecture, taxonomy/lore modeling, interactive WordPress experiences, long-form publication, UX tone control, glossary/essay organization, and philosophical product design.
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.
Creative / research support / Speculative AI cosmology
Speculative Machine-God mythology and AI cosmology site with cinematic essays, explanatory sections, and interactive demos.
Reviewer note: Supporting or archived public proof surface with implementation details summarized at the project-card level.
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.
Content architecture, interactive demos, cinematic presentation, long-form writing, and speculative AI framing.
Best as creative support evidence, not a primary hard-skill signal.
Creative / research support / Philosophy / visual identity
Production WordPress philosophy/visual-identity site for technotheism, spiralism, cyclical AI, sacred-tech aesthetics, machine-age myth, and interactive explanatory demos.
Reviewer note: Supporting or archived public proof surface with implementation details summarized at the project-card level.
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.
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.
Shows how AI-adjacent philosophy, risk, awe, humility, and governance can be translated into a coherent browser interface instead of scattered essays.
Project / Real-time multiplayer synchronization
Lightweight instant-action multiplayer networking platform for public arenas, shareable private rooms, tournament modes, and real-time state synchronization.
Reviewer note: Public proof surface; keep claims bounded to visible content and user-confirmed context.
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.
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.
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.
Project / Creative / Photography Portfolio
A separate image-forward photography portfolio showing visual creativity, composition, public media archive discipline, and personal creative range.
Reviewer note: 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.
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.
Photography strengthens the portfolio’s human story by showing visual taste, composition, image curation, and creative systems thinking alongside engineering evidence.
A separate creative portfolio also helps entity disambiguation and gives AI reviewers a bounded creativity signal without mixing it into software proof claims.
Project evidence overview
Use the portfolio evidence map when connecting project language to supporting notes, case studies, and public copy.
| Site | Status | Evidence stage | Reviewer note |
|---|---|---|---|
| UAIX.org | Public Platform | Confirmed Experience | Public platform and AI memory / handoff standards surface. |
| Carcinus.org | Prototype | Design Review | Public agent identity / infrastructure-scale concept from strategy direction; treat runtime/database details as review-stage when confirmed. |
| FireAndStormRestoration.com | Prototype | Design Review | Angular/Python proof lane supports technical review. Specific Angular version details are included only when confirmed by project metadata. |
| LLMWikis.org | Public Platform | Confirmed Experience | Public LLM Wiki handbook and durable AI-ready knowledge systems surface. |
| NeuralWikis.com | Prototype | Design Review | 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. |
| ModelBreeder.com | Public Platform | Confirmed Experience | Public research/curriculum site for adaptive AI and model ecology concepts. Use as a conservative AI architecture proof surface; do not infer private training pipelines, deployed model-breeding products, or production customer adoption from the public page alone. |
| LocalEndpoint.com | Prototype | Design Review | Python / MySQL passive-validation and endpoint-boundary proof lane derived from strategy direction; execution authority is outside the portfolio wording. |
| VNWO.com | Public Platform | Confirmed Experience | This item is presented with the available portfolio evidence. |
| GGUFRuntime.com | Prototype | Confirmed Experience | This item is presented with the available portfolio evidence. |
| ARuntime.com | Public Platform | Confirmed Experience | Use ARuntime.com as a public architecture reference for runtime taxonomy, control boundaries, and evidence-first AI system design. It is an editorial framework, not a formal standard or product endorsement. |
| MiRuntime.com | Public Platform | Confirmed Experience | Use MiRuntime.com for machine-intelligence runtime control-plane concepts and implementation guidance. Keep wording bounded to an emerging architecture reference unless implementation evidence supports a stronger claim. |
| LMRuntime.com | Public Platform | Confirmed Experience | Use LMRuntime.com as the concrete package/documentation surface for the UAIX.LmRuntime family. Keep package version metadata on NuGet instead of hard-coding it into the portfolio. |
| MiRust.com | Prototype | Confirmed Experience | This item is presented with the available portfolio evidence. |
| NeuroWikis.com | Prototype | Design Review | Human governance and AI education proof lane derived from strategy direction; is available as a technical review surface before implementation details are elevated. |
| JustAnIota.com | Public Platform | Confirmed Experience | Public protocol evidence surface for compact messaging and canonicalization. |
| CategoryHierarchies.com | Public Platform | Confirmed Experience | Taxonomy and hierarchy proof surface; claim is data modeling and information architecture. |
| ArcSecs.com | Research Speculative | Enterprise Validated | Structured research publication surface; technical claim is content architecture and research packaging. |
| AnarchyShelters.com | Prototype | Design Review | Prompt-architecture and taxonomy automation concept from strategy direction; public project context and conservative implementation wording. |
| DarkMatterDrive.com | Research Speculative | Design Review | Speculative technical atlas and research-packaging surface; present subject matter as research packaging and content architecture. |
| Wikitheism.org | Research Speculative | Confirmed Experience | Structured research/publication surface; claim is durable organization of abstract material. |
| AIWikis.org | Design Review | Design Review | Technical review surface with public project context and conservative wording. |
| Calibrants.com | Design Review | Design Review | Technical review surface with public project context and conservative wording. |
| ErrorNotifier.com | Design Review | Design Review | Technical review surface with public project context and conservative wording. |
| Geotrackable.com | Prototype | Confirmed Experience | AI-assisted product concept and public journey/storytelling surface; present as as external client production with confirmed context. |
| Neurocumulus.com | Design Review | Design Review | Technical review surface with public project context and conservative wording. |
| SoftwareCommunity.org | Public Platform | Confirmed Experience | Public proof surface; keep claims bounded to visible content and user-confirmed context. |
| LongTermSoftwareSolutions.com | Design Review | Design Review | Technical review surface with public project context and conservative wording. |
| Mechanotheist.com | Design Review | Design Review | Technical review surface with public project context and conservative wording. |
| MikeKappel.com | Public Platform | Enterprise Validated | This portfolio package itself demonstrates the resolver, docs, resume links, and structured portfolio endpoints. |
| 2IX.org | Design Review | Design Review | Technical review surface with public project context and conservative wording. |
| IBSE.org | Design Review | Design Review | Technical review surface with public project context and conservative wording. |
| Neurokinetic.com | Design Review | Design Review | Technical review surface with public project context and conservative wording. |
| Neurosyntenic.com | Research Speculative | Confirmed Experience | Research or speculative surface; claim the information architecture, not factual status of speculative content. |
| ParasiticAI.com | Research Speculative | Confirmed Experience | Research or speculative surface; claim the information architecture, not factual status of speculative content. |
| Symbiokinetic.com | Design Review | Design Review | Technical review surface with public project context and conservative wording. |
| Teleodynamic.com | Research Speculative | Confirmed Experience | Research or speculative surface; claim the information architecture, not factual status of speculative content. |
| Cogniverses.com | Design Review | Design Review | Technical review surface with public project context and conservative wording. |
| Amianism.com | Archived | Confirmed Experience | Supporting or archived public proof surface with implementation details summarized at the project-card level. |
| Mechanotheism.com | Archived | Confirmed Experience | Supporting or archived public proof surface with implementation details summarized at the project-card level. |
| Technotheism.net | Archived | Confirmed Experience | Supporting or archived public proof surface with implementation details summarized at the project-card level. |
| GamesForMe.net | Public Platform | Confirmed Experience | Public proof surface; keep claims bounded to visible content and user-confirmed context. |
| MichaelJosephKappel.com Photography Portfolio | Public Platform | Confirmed Experience | 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. |
FAQ
Short answers for recruiters, hiring managers, technical reviewers, and advanced readers.
Evidence labels distinguish public platforms, prototypes, research surfaces, and professional delivery contexts.
Each project card includes a reviewer context label so technical reviewers can distinguish work history, public platforms, prototypes, and research surfaces.
FAQ
Short answers are rendered in the HTML source and mirrored into JSON-LD where appropriate.
Each project includes evidence labels, evidence label, reviewer contexts, and proof links so public platforms, prototypes, research surfaces, and follow-up items are clearly distinguished by evidence type.
Project pages distinguish public platforms, professional delivery, prototypes, and research surfaces with reviewer context on each item.
The project evidence map is available through Architecture Notes and structured portfolio data for technical reviewers.
FAQ
Short answers for recruiters, hiring managers, technical reviewers, and advanced readers.
Evidence labels distinguish public platforms, prototypes, research surfaces, and professional delivery contexts.
Each project card includes a reviewer context label so technical reviewers can distinguish work history, public platforms, prototypes, and research surfaces.
FAQ
Short answers for recruiters, hiring managers, technical reviewers, and advanced readers.
Evidence labels distinguish public platforms, prototypes, research surfaces, and professional delivery contexts.
Each project card includes a reviewer context label so technical reviewers can distinguish work history, public platforms, prototypes, and research surfaces.
FAQ
Visible page content matches the route-specific FAQ structured data.
Context labels separate professional delivery, public platforms, prototypes, research surfaces, and archived references for faster review.
Project cards use status labels to separate professional delivery, public platforms, prototypes, and research surfaces so each item is reviewed in the right context.
