{ "allowedSourceStatusValues": [ "approved", "user-confirmed", "Design Review", "imported-needs-review", "quarantined" ], "allowedStatusValues": [ "production-work", "public-platform", "prototype", "research-speculative", "archived", "user-confirmed", "Design Review" ], "evidenceTaxonomy": { "professionalContextRule": "Projects marked review-stage or imported-needs-review are proof surfaces or prototypes with conservative implementation wording after review.", "sourceStatus": [ "approved", "user-confirmed", "Design Review", "imported-needs-review", "quarantined" ], "status": [ "production-work", "public-platform", "prototype", "research-speculative", "archived", "user-confirmed", "Design Review" ] }, "generatedUtc": "2026-06-18T21:30:00Z", "generated_utc": "2026-06-18T21:30:00Z", "metadataConversionQaPolish": { "installedRuntimeQaClaimed": false, "preserved": [ "human-first primary navigation", "modernization-first homepage", "selected-project anchor", "direct contact first", "secondary research utilities", "noindex report boundary" ], "runtimeBoundary": "Do not claim runtime QA until the installed WordPress runtime reports v3.126.0 on static, REST, MCP, HTTPS, and root-file surfaces.", "scope": "v3.126.0 production QA remediation: HTTPS root support, root deployment manifest, missing page fallbacks, REST research context, and stale metadata cleanup.", "version": "3.126.0" }, "orderingNote": "v8.8.6 preserves evidence labels and adds SEO-first Angular/RxJS source-boundary metadata. Strategy-backed entries stay review after review.", "projects": [ { "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", "Model Context Protocol (MCP)", "MCP Endpoint Contracts", "Capability-Adaptive Fallbacks", "Agent Executability Matrix" ], "detail": "UAIX turns agent work into a reviewable public exchange contract. The Agent Executability Matrix defines capability-sensitive routing, MCP-aware endpoint selection, lowest-safe fallback behavior, and explicit no-op outcomes when a model or host cannot execute a richer path.", "evidenceLabel": "Public Platform", "evidenceLabels": [ "Public Platform", "User-Confirmed" ], "evidenceLevel": "User-Confirmed", "lastReviewedUtc": "2026-06-18T00:00:00Z", "name": "UAIX.org", "professionalContext": "Public AI interoperability, Model Context Protocol, memory/handoff, and capability-routing standards surface.", "proofLinks": [ "https://uaix.org/en-us/spec/agent-executability-matrix/", "https://www.nuget.org/profiles/Michael.Kappel", "/mcp", "Architecture Notes/project-evidence-map.md", "Architecture Notes/uai-memory-handoff-map.md" ], "proofs": [ "UAI-1 envelope, profile, trust, provenance, and error surfaces", "Agent Executability Matrix with MCP-aware routes, lowest-safe fallbacks, and no-op behavior", "AI Memory, Project Handoff, and Agent File Handoff package patterns", "Validator-backed proof paths, OpenAPI route inventories, conformance packets, and governance material", "Capability-adaptive endpoint abstraction for clients ranging from MCP to REST, static retrieval, and safe no-op" ], "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": "Model Context Protocol, Streamable HTTP, JSON-RPC, MCP tools/resources/prompts, standards architecture, endpoint abstraction, capability negotiation, lowest-safe fallback design, no-op behavior, JSON schema, OpenAPI, validation-first QA, governance, conformance, provenance, and technical documentation at protocol scale.", "sourceStatus": "user-confirmed", "source_note": "Public AI interoperability, Model Context Protocol, memory/handoff, and capability-routing standards surface.", "source_status": "user-confirmed", "status": "public-platform", "summary": "Canonical UAI-1, Model Context Protocol, AI Memory, Project Handoff, and Agent File Handoff standards surface with schemas, validator evidence, Agent Executability Matrix routing, implementation tracks, conformance records, governance, and capability-adaptive fallback guidance.", "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", "Model Context Protocol (MCP)", "MCP Endpoint Contracts", "Capability-Adaptive Fallbacks", "Agent Executability Matrix" ], "technologies": [ "UAI-1", "AI Memory", "Project Handoff", "Agent File Handoff", "JSON Schema", "OpenAPI", "Validators", "Conformance", "Governance", "AI Protocols", "Model Context Protocol (MCP)", "MCP Endpoint Contracts", "Capability-Adaptive Fallbacks", "Agent Executability Matrix" ], "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": [ "Model Context Protocol, Streamable HTTP, JSON-RPC, MCP tools/resources/prompts, standards architecture, endpoint abstraction, capability negotiation, lowest-safe fallback design, no-op behavior, JSON schema, OpenAPI, validation-first QA, governance, conformance, provenance, and technical documentation at protocol scale." ] }, { "name": "Michael.Kappel NuGet Packages", "title": "Michael.Kappel NuGet Packages", "url": "https://www.nuget.org/profiles/Michael.Kappel", "type": ".NET AI interoperability and endpoint packages", "status": "public-platform", "tier": "top", "summary": "Published .NET packages supporting UAIX/UAI abstractions, memory and handoff workflows, agent clients, ecosystem management, logging, endpoint abstraction, and capability-adaptive MCP integration.", "detail": "The public NuGet publisher profile is the registry-backed package surface for reusable .NET abstractions used to connect MCP-capable clients while retaining simpler REST, static, and safe no-op paths for less-capable hosts or models.", "technologies": [ "C#", ".NET", "NuGet", "Model Context Protocol (MCP)", "JSON-RPC", "Endpoint Abstractions", "AI Memory", "Agent Handoff", "Capability-Adaptive Fallbacks", "Safe No-Op" ], "tags": [ "C#", ".NET", "NuGet", "MCP", "UAIX", "UAI", "AI Memory", "Agent Client", "Endpoint Abstraction", "Fallback Design" ], "capabilityTags": [ "Model Context Protocol (MCP)", "C#", ".NET", "NuGet", "Endpoint Abstractions", "Capability-Adaptive Fallbacks", "AI Memory", "Agent Handoff" ], "evidenceLabel": "Public Package Registry", "evidenceLabels": [ "Public Package Registry", "User-Confirmed" ], "evidenceLevel": "User-Confirmed", "sourceStatus": "user-confirmed", "source_status": "user-confirmed", "professionalContext": "Public NuGet publisher profile and user-confirmed MCP/endpoint package engineering.", "source_note": "Public NuGet publisher profile and user-confirmed MCP/endpoint package engineering.", "proofLinks": [ "https://www.nuget.org/profiles/Michael.Kappel", "https://uaix.org/en-us/spec/agent-executability-matrix/", "/mcp" ], "proofs": [ "Public Michael.Kappel NuGet publisher profile", "Reusable .NET endpoint, abstraction, memory, handoff, and agent-client packages", "MCP-capable path with lower-capability REST/static/no-op abstraction" ], "whatThisProves": [ "C#/.NET package design, public package release discipline, MCP endpoint abstraction, AI memory/handoff integration, and capability-adaptive fallback engineering." ], "whatThisDoesNotClaim": [ "Package registry presence does not independently verify private production deployments, client usage, traffic scale, or confidential implementation details." ], "unsupportedClaims": [ "Package registry presence does not independently verify private production deployments, client usage, traffic scale, or confidential implementation details." ], "ai_signal": "Shows reusable MCP and agent-integration engineering packaged for .NET consumers rather than confined to one website implementation.", "skill_signal": "C#/.NET library design, NuGet publishing, Model Context Protocol, JSON-RPC, endpoint abstraction, AI memory/handoff, agent clients, logging integration, capability fallback, and safe no-op behavior.", "lastReviewedUtc": "2026-06-18T00:00:00Z" }, { "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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 MikeKappel.com is the primary hub.", "evidenceLabel": "Technical Review", "evidenceLabels": [ "Archived", "Technical Review" ], "evidenceLevel": "Technical Review", "lastReviewedUtc": "2026-06-10T17:27:13Z", "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": "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.", "evidenceLabel": "Public Platform", "evidenceLabels": [ "Public Platform", "User-Confirmed" ], "evidenceLevel": "Approved", "lastReviewedUtc": "2026-06-10T17:27:13Z", "name": "MikeKappel.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": "MikeKappel.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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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—useful 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-10T17:27:13Z", "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—exactly 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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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-10T17:27:13Z", "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.11-symbol-photography-portfolio-integration.md" ], "skill_signal": "Photography strengthens the portfolio’s 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." ], "previewImages": [ "/assets/img/photography/storm-clouds-over-field.jpg", "/assets/img/photography/public-art-sculpture.jpg", "/assets/img/photography/squirrel-tree-portrait.jpg", "/assets/img/photography/transit-light-lines.jpg" ], "previewImageBoundary": "Preview images are used as visual creativity context only, not software-delivery proof." } ], "relatedEvidence": { "evidenceGraph": "/evidence-graph.json", "targetRoles": "/target-roles.json" }, "sourceStatusValues": [ "approved", "user-confirmed", "Design Review", "imported-needs-review", "quarantined" ], "source_governance": "Projects carry status, evidenceLevel, evidenceStage, professionalContext, technologies, capabilityTags, proofLinks, and review dates.", "statusValues": [ "production-work", "public-platform", "prototype", "research-speculative", "archived", "user-confirmed", "Design Review" ], "updatedUtc": "2026-06-18T21:30:00Z", "updated_utc": "2026-06-10T17:27:13Z", "v8820": { "summary": "Human-facing browser QA and presentation polish pass." }, "v887Routes": { "career": "/career/", "evidenceMap": "/evidence-map/", "reviewQueue": "/review-queue/", "sitemap": "/sitemap.xml" }, "version": "3.126.0", "photographyRowPolish": { "version": "3.126.0", "installedRuntimeQaClaimed": false, "scope": "small homepage photography row polish only", "change": "Photography / visual creativity skill card spans the full desktop skill grid and displays four supplied preview images below the text.", "assets": [ "/assets/img/photography/storm-clouds-over-field.jpg", "/assets/img/photography/public-art-sculpture.jpg", "/assets/img/photography/squirrel-tree-portrait.jpg", "/assets/img/photography/transit-light-lines.jpg" ], "boundary": "Photography remains visual creativity and public-image context only, not software-delivery proof." } }