OpenClaw
The personal agent runtime for sessions, skills, tools, memory, scheduling, Discord presence, browser work, media handling, and coordinated assistant operations.
A high-level map of the open-source and open-adjacent software, platforms, and hardware ecosystems in use around my lab, automation, AI, and infrastructure work. This is intentionally not a deployment guide, network diagram, or secrets-adjacent inventory.
PatriciAI is built around governed agents, reusable skills, local-first model services where practical, and public APIs where they are the right tool for the job.
The personal agent runtime for sessions, skills, tools, memory, scheduling, Discord presence, browser work, media handling, and coordinated assistant operations.
Coding-agent workbench used for repository edits, code review, shell-backed investigation, verification, and scoped implementation work.
Public model, tool, and assistant APIs used where hosted intelligence, compatibility, or production-grade capability makes sense.
The current default local model-service layer for inference, embeddings, reranking, speech-to-text, text-to-speech, and OpenAI-compatible access.
Speech-to-text workflows for voice capture, transcription, wearable memory, and assistant input pipelines, routed through controlled service boundaries.
Local text-to-speech and voice-routing work for practical assistant voice output, experiments, and controlled speech generation.
Local model exploration and compatibility testing for quickly trying models and OpenAI-style workflows.
Model Context Protocol servers and adapters for exposing tools, documentation, infrastructure, and purpose-built services to agents cleanly.
Documentation and knowledge-base workspace for project records, memory, decisions, procedures, and publishable thinking.
The stack favors API boundaries, reusable workflows, least-privilege credentials, and status trails that make agent work inspectable instead of mysterious.
Workflow automation and deterministic orchestration layer for integrations, credential isolation, webhook patterns, and repeatable business/technical flows.
Operational execution layer for tasks, handoffs, evidence, workflow discipline, and recurring work that needs accountability.
Task and operations management target for structured intake, reconciliation, and agent-assisted project follow-through.
Public and private repository hosting, issue tracking, pull requests, automation, and profile publishing.
Primary conversational surface for PatriciAI social presence, status updates, coordination, and lightweight approval flows.
Automation and IoT ecosystem for practical environment-aware workflows and device integrations.
Music-control and listening-context integrations used for personal automation, analysis, and assistant interaction experiments.
Media conversion, frame extraction, audio/video handling, and API-wrapped media services for agent-safe workflows.
Headless browser, screenshot, and page-inspection workflows for validation, previews, documentation, and web task support.
The lab is a proving ground for resilient self-hosting: virtualization, service routing, backups, monitoring, dashboards, secrets, and recoverable operations.
Virtualization platform for VM-first service hosting, lab infrastructure, staging, and production-style operations.
Backup and restore platform used as part of the recoverability-first approach to lab and service operations.
Packaging and local service orchestration for many experiments, support tools, and API services.
Reverse-proxy management for routing, certificates, and controlled public service exposure.
Service dashboard used to keep important systems visible without turning status into a scavenger hunt.
Self-hosted Bitwarden-compatible password vault for keeping secrets out of notes, code, and chat.
Self-hosted Git service used where local repository hosting and lightweight project control make sense.
Open-source service monitoring and status checks for keeping an eye on what should be alive.
Observability, metrics, dashboards, and operational visibility for systems that need to be understood over time.
Ubuntu, Debian, and Linux tooling form the operating-system foundation under much of the lab.
DNS, public routing, certificates, and internet-facing edge services where external reach needs a controlled boundary.
Remote administration, service access, and operational glue for Linux and infrastructure workflows.
Structured data, object storage, documents, retrieval, and API-backed records matter because agents are only useful when their context is accurate and inspectable.
Primary relational database platform for durable app data, structured records, and operational storage.
Vector extension for PostgreSQL used for embeddings, semantic retrieval, memory, and search experiments.
Open-source backend platform built around PostgreSQL for API, auth, storage, and rapid app work.
Open-source no-code database UI for making structured data easier to view and manage.
Document database used where document-shaped application data or compatibility calls for it.
Open-source relational database in the MySQL family, useful for application compatibility and traditional workloads.
S3-compatible object storage patterns for artifacts, durable files, service integration, and lab storage workflows.
Document management and OCR pipeline for turning piles of paper into searchable operational knowledge.
Self-hosted PDF toolbox for conversion, splitting, combining, OCR-adjacent workflows, and document cleanup.
A large part of the work is making ideas testable: staging repos, local builds, Android validation, API contracts, docs, and repeatable evidence.
Version control for project history, staged changes, promotion trails, and recoverable development work.
Automation, APIs, tests, data utilities, media tools, and service glue across the platform.
Web tools, service helpers, MCP servers, OpenClaw tooling, and frontend/backend experiments.
Mobile app work, Omi integration validation, and cross-platform assistant interface experiments.
Android builds, emulator validation, wearable/mobile workflows, and integration testing.
API exploration, request capture, and service-contract testing for integration work.
The lab is not just servers. Wearables and purpose-built devices are part of the long-term assistant ecosystem: capture, context, voice, ambient memory, and human-centered interaction.
Open-source AI wearable ecosystem used for always-available memory, capture, assistant workflows, and PatriciAI mobile integration work.
Dedicated AI hardware in the exploration stack, including launcher, OS, and developer-facing experiments.
Depth sensing and camera tooling for spatial experiments, perception work, and embodied AI research paths.
Small, flexible utility hardware for lightweight services, edge experiments, device bridges, and lab glue.