158 lines
15 KiB
Markdown
158 lines
15 KiB
Markdown
---
|
||
Date: 2026-04-26
|
||
Author: Antigravity
|
||
Tags: #business #mission #christian #tech
|
||
---
|
||
|
||
# Business Ideas
|
||
|
||
## Christian Small Business Support
|
||
- **Concept**: A company that supports small businesses for Christian people.
|
||
- **Services**:
|
||
- Web Design
|
||
- Hosting
|
||
- App Development
|
||
- Deployment
|
||
- **Status**: Proposed on 2026-04-26.
|
||
|
||
## DSPi
|
||
- **Concept**: Potential project involving digital signal processing or related tech.
|
||
- **Link**: https://github.com/WeebLabs/DSPi
|
||
- **Status**: Captured on 2026-04-27.
|
||
|
||
## Children’s Version of Self-Help Books
|
||
- **Concept**: Create child-friendly adaptations of popular self-help frameworks (e.g., habits-focused books) with age-appropriate language, stories, and activities.
|
||
- **Potential Angle**: Family/faith-aligned personal growth tools for kids.
|
||
- **Status**: Idea captured from A Reyna (DM) on 2026-05-24.
|
||
|
||
## Markdown Widget Dashboard (LLM-Administered)
|
||
- **Concept**: Build a dashboard composed of widgets that are rendered from Markdown files and administered/updated by an LLM through conversation.
|
||
- **Core Idea**: Use Markdown files as the system of record for each widget, reducing or removing the need for a traditional database.
|
||
- **Potential Benefits**:
|
||
- Human-readable state/history.
|
||
- Simple version control (Git-friendly).
|
||
- Fast prototyping and local-first workflows.
|
||
- **MVP Architecture (v1)**:
|
||
- **Widget Storage**: One Markdown file per widget (e.g., `widgets/weather.md`, `widgets/tasks.md`).
|
||
- **Widget Frontmatter**: `id`, `title`, `type`, `refresh`, `updated_at`, `owner`, `permissions`, `tags`.
|
||
- **Widget Body Schema**: Structured sections (`## Summary`, `## Data`, `## Actions`) that the renderer can parse deterministically.
|
||
- **Renderer Layer**: Markdown-to-widget renderer (web UI) that maps frontmatter + sections into visual components.
|
||
- **LLM Update Loop**: Chat instruction -> intent parser -> safe file patch -> validation -> commit.
|
||
- **Validation Rules**: Enforce schema, required fields, and allowed section names before saving.
|
||
- **Versioning/Audit**: Git commit per update with message including actor + intent.
|
||
- **Conflict Handling**: If file changed since last read, do 3-way merge or request user confirmation.
|
||
- **Optional Cache**: Lightweight in-memory/index cache for faster dashboard loads (no primary DB).
|
||
- **Permissions Model**: Per-widget read/write policy to separate personal vs shared dashboard data.
|
||
- **First MVP Widgets**:
|
||
- Today tasks.
|
||
- Calendar snapshot.
|
||
- Budget quick view.
|
||
- Family reminders.
|
||
- **Status**: Idea + MVP architecture captured from A Reyna (DM) on 2026-05-24.
|
||
|
||
## Chiapas Coffee Sales Role (Brother Gino)
|
||
- **Concept**: Bring Brother Gino in as a dedicated salesperson for coffee from Chiapas.
|
||
- **Potential Value**:
|
||
- Dedicated sales focus (lead generation + follow-up).
|
||
- Faster customer development while production/sourcing is handled separately.
|
||
- Strong trust-based outreach if aligned with existing church/family network.
|
||
- **Suggested Pilot Scope**:
|
||
- 30-day trial with clear targets (new leads, tasting meetings, first recurring buyers).
|
||
- Define compensation model (commission-only vs base + commission).
|
||
- Provide simple sales kit (story of origin, pricing tiers, sample workflow, reorder process).
|
||
- **Status**: Idea captured from A Reyna (DM) on 2026-05-27.
|
||
|
||
## MCP LAN Discovery Protocol
|
||
- **Concept**: A Bonjour-like local discovery protocol for MCP servers so LLM harnesses can discover nearby tools, devices, and services on the LAN without manual configuration.
|
||
- **Core Idea**: Hardware or local computers advertise themselves as MCP-capable services over mDNS/DNS-SD, then expose a manifest describing endpoint, transport, capabilities, auth, and safety requirements.
|
||
- **Possible Service Type**: `_mcp._tcp.local`
|
||
- **Potential Manifest Path**: `/.well-known/mcp.json`
|
||
- **Example Advertised Devices/Services**:
|
||
- Mac Mini MCP server.
|
||
- Raspberry Pi home harness.
|
||
- Smart displays, speakers, cameras, sensors, printers, scanners, NAS, or robotics hardware.
|
||
- Local app/server capabilities such as Immich, MongoDB Assistant, or household automation services.
|
||
- **Trust Model**:
|
||
- Discovery should not equal authorization.
|
||
- Devices should expose only basic metadata before pairing.
|
||
- Actual tool access should require explicit user approval, pairing code, OAuth/device flow, passkey, certificate trust, or a local token.
|
||
- **Why It Matters**:
|
||
- Makes local AI hardware plug-and-play for agents.
|
||
- Lets LLM harnesses discover available “hands” in the local environment.
|
||
- Reduces manual MCP config editing.
|
||
- Creates a path for safe, self-describing local devices that can be used by Hermes or other agent runtimes.
|
||
- **First Prototype Device**: Waveshare ESP32-S3-RLCD-4.2 board from Amazon link https://a.co/d/0claSFAh; specs found 2026-05-31: ESP32-S3-WROOM-1-N16R8 with 16MB Flash and 8MB PSRAM, 4.2-inch 300×400 reflective LCD, Wi-Fi/BLE, dual microphones, RTC, SHTC3 temperature/humidity sensor, TF card slot, and battery support.
|
||
- **MicroPython Firmware Note**: Official MicroPython ESP32_GENERIC_S3 firmware supports ESP32-S3 boards with external RAM and auto-detects SPIRAM, but MicroPython says to use the `ESP32_GENERIC_S3-SPIRAM_OCT` variant for boards with Octal SPIRAM. This board’s N16R8 module likely needs the SPIRAM_OCT build to use the 8MB PSRAM.
|
||
- **MicroPython Screen Driver Finding**: The display controller is ST7305. Exact MicroPython driver found on 2026-05-31: `micheleaiello/ESP32-S3-4.2inch-RLCD-Driver` (https://github.com/micheleaiello/ESP32-S3-4.2inch-RLCD-Driver). It targets the Waveshare ESP32-S3 4.2-inch RLCD, uses `framebuf`, pins MOSI=12, SCK=11, DC=5, CS=40, RST=41, and includes `rlcd.py`, `shtc3.py`, `sensors.py`, and `vector.py`. Related generic driver: `elulis/micropython_ST7302` supports ST7302/ST7305 but only documents smaller 2.13/2.9-inch reflective TFTs, so the exact Waveshare repo is the better starting point.
|
||
- **Status**: Idea captured from A Reyna (DM) on 2026-05-31; first hardware prototype identified on 2026-05-31; MicroPython screen driver identified on 2026-05-31.
|
||
|
||
## Bible Device with LLM Interaction
|
||
- **Concept**: Use the new iPhone/device screen as a dedicated Bible/Scripture companion device with LLM interaction.
|
||
- **Core Idea**: The device displays high-resolution color Bible verse cards, devotionals, reading prompts, and family Scripture content, while an LLM can respond conversationally, explain passages, choose verses from the [[Treasure Box Verses]], and control device media through MCP tools.
|
||
- **Potential Value**:
|
||
- Turns old/jailbroken devices into useful faith-centered smart displays.
|
||
- Combines beautiful Scripture visuals, audio playback, microphone input, and camera/selfie context for interactive spiritual routines.
|
||
- Could support family devotionals, verse memorization, prayer prompts, bedtime Scripture, and contextual Bible Q&A.
|
||
- **MVP Ideas**:
|
||
- Display a daily Treasure Box verse as a high-resolution image.
|
||
- Voice interaction: ask for a verse, explanation, prayer prompt, or devotional reflection.
|
||
- Audio output: speak the verse or devotional using `play_audio_base64`.
|
||
- Input tools: record voice questions and capture optional selfie/context photo when explicitly requested.
|
||
- Local-first content source: pull from `/home/adolforeyna/brain/areas/treasure_box/treasure_verses.md` and related family notes.
|
||
- **Status**: Idea captured from A Reyna (DM) on 2026-06-01.
|
||
|
||
## Beach Family Setup Service
|
||
- **Concept**: A beach convenience service that sets up umbrellas, beach towels, toys, and optional snacks so families can arrive to a ready-made beach spot instead of spending hours preparing and hauling gear.
|
||
- **Core Offer**: For about **$50**, meet the family at the beach with everything already prepared for their group.
|
||
- **Potential Value**:
|
||
- Saves parents preparation time and reduces stress.
|
||
- Makes beach days easier for families with young kids.
|
||
- Creates an upsell path for snacks, toys, premium shade, chairs, coolers, or cleanup.
|
||
- **Possible MVP**:
|
||
- Start with one local beach and a fixed family package.
|
||
- Offer add-ons: snacks, extra towels, beach toys, sunscreen, cooler/ice, chairs, or cleanup.
|
||
- Use simple booking via text/form with beach location, family size, arrival time, and add-ons.
|
||
- **Status**: Idea captured from A Reyna (DM) on 2026-06-02.
|
||
|
||
## Family AI Home Server
|
||
- **Concept**: A family-focused home server appliance/software bundle that combines private image storage, media management, DNS/ad blocking, and voice-call/voice-message communication between household devices, with AI integrations for conversational control of the server.
|
||
- **Core Idea**: Package the most useful self-hosted family infrastructure into one friendly system: photo backup/search, media library, network protection, device-to-device voice communication, and an AI assistant that can manage, search, summarize, and automate these services.
|
||
- **Possible Feature Set**:
|
||
- Private family photo/video storage with automatic phone backup, albums, face/object search, sharing, and local-first ownership.
|
||
- Lightweight family media management focused on home videos, shared clips, and simple playback rather than a full Jellyfin/Plex-style movie/TV server.
|
||
- Network-wide DNS blocking, parental controls, safe browsing, device profiles, and usage visibility.
|
||
- Household voice communication between devices: room-to-room calls, push-to-talk, voice notes, announcements, and possibly WebRTC/SIP/Matrix-backed calls.
|
||
- AI assistant layer: natural-language search across photos/media/files, “show vacation photos,” “play family movie night,” “block this device for bedtime,” “call the kitchen screen,” “summarize new uploads,” and proactive family routines.
|
||
- Local integrations with smart displays, ESP32 voice devices, Home Assistant, Apple/Android clients, and Obsidian/family brain notes.
|
||
- **Similar / Adjacent Products Researched on 2026-06-18**:
|
||
- **Synology DSM / BeeStation / Photos / Chat**: Strong consumer NAS and private-cloud positioning. Synology Photos organizes, shares, and safeguards memories on a NAS; BeeStation is a simple personal cloud; Synology Chat provides private messaging. Gap: not centered on AI-first family workflows, voice communication between home devices, or a unified DNS/media/AI bundle. Sources: https://www.synology.com/en-global/dsm/feature/photos, https://www.synology.com/en-global/dsm/feature/chat, https://bee.synology.com/en-global/BeeStation
|
||
- **QNAP / TrueNAS / Unraid**: Powerful NAS/home-lab platforms for storage, Docker apps, and VMs. Unraid positions itself as a homelab OS for NAS, Docker, and VMs; TrueNAS focuses on OpenZFS storage. Gap: great infrastructure, but too technical and not family-experience-first. Sources: https://unraid.net/, https://www.truenas.com/truenas-scale/
|
||
- **CasaOS / ZimaOS / Umbrel / YunoHost**: Friendly self-hosting app-store operating systems. CasaOS/ZimaOS and Umbrel emphasize one-click personal cloud/self-hosted apps; YunoHost offers low-technical-knowledge server app hosting. Gap: app-store/self-hosting layer exists, but lacks a cohesive family appliance that integrates photos, media, DNS, voice, and AI into one guided product. Sources: https://casaos.io/, https://www.zimaspace.com/, https://umbrel.com/, https://yunohost.org/
|
||
- **Nextcloud + Nextcloud Talk + Nextcloud Assistant**: Open-source collaboration suite with files, photos, groupware, calls/chat/video conferencing, and private/local AI assistant positioning. Gap: collaboration-first rather than family-home-server-first; media library, DNS blocking, and smart-home/device voice intercom would need assembly. Sources: https://nextcloud.com/, https://nextcloud.com/talk/
|
||
- **Immich**: Excellent self-hosted photo/video management and backup with privacy focus. Gap: photo-specific; would be a component rather than the whole family server. Source: https://immich.app/
|
||
- **Jellyfin / Plex**: Mature personal media server products for streaming media from a home server. Gap: media-specific; not family infrastructure, DNS, device communication, or AI management by default. Sources: https://jellyfin.org/, https://www.plex.tv/
|
||
- **Pi-hole / AdGuard Home**: Network-wide DNS ad/tracker blocking. Gap: DNS protection only; would be a component in the broader bundle. Sources: https://pi-hole.net/, https://adguard.com/en/adguard-home/overview.html
|
||
- **Home Assistant Assist / ESPHome voice**: Private local voice assistant for smart-home control, including dedicated or DIY voice hardware. Gap: smart-home-control-first, not family media/photo/DNS/server management; strong integration candidate. Source: https://www.home-assistant.io/voice_control/
|
||
- **Initial Market Read**:
|
||
- The components exist individually, but the family-friendly integration appears underserved.
|
||
- Differentiation should be “family appliance + AI operator,” not “another NAS.”
|
||
- The winning product would hide Docker/NAS complexity and present household workflows: protect the network, store memories, find media, call rooms/devices, manage routines, and ask the family server for help.
|
||
- **Potential MVP**:
|
||
- Start as a curated software stack on existing hardware: Immich + AdGuard Home/Pi-hole + Matrix/Nextcloud Talk/WebRTC/SIP intercom + Home Assistant Assist + Hermes/MCP AI control layer. Jellyfin/Plex-style movie server support is optional, not core.
|
||
- Provide a single dashboard, guided setup, family accounts, mobile backup instructions, device pairing, and AI commands.
|
||
- Use one household device first, e.g. kitchen screen/ESP32 voice device, for announcements and voice notes.
|
||
- **Key Open Questions**:
|
||
- Appliance vs. installable OS vs. managed setup service.
|
||
- Whether voice communication should be WebRTC, SIP, Matrix, Mumble, or a custom LAN-first protocol.
|
||
- How much AI should run locally vs. cloud-assisted.
|
||
- Family privacy/security model, especially around photos, kids, device controls, and remote access.
|
||
- **Related Brain Links**: [[MCP LAN Discovery Protocol]], [[Bible Device with LLM Interaction]]
|
||
- **Status**: Idea researched and logged from A Reyna (DM) on 2026-06-18.
|
||
|
||
## ESP32 Paper Apps-Style Pocket Games
|
||
- **Concept**: Make small, paper-notebook-inspired games for Reyna ESP32/Tactility devices: generated maps, roll-and-write style movement, simple icons, and physical-feeling “pages” adapted to 320×240 screens.
|
||
- **Inspiration**: Gladden Design Paper Apps (`https://gladdendesign.com/`) — DUNGEON, LABYRINTH, GOLF, GALAXY notebooks. Observed mechanics: generated dot-grid maps, room/floor pages, HP/coin trackers, d6 outcomes, pencil-path movement, enemy/treasure/event icons, and printable monochrome layouts.
|
||
- **Best MVP for current devices**: “Pocket Dungeon” on KidsOS/Tactility: 16×12 tile map, d6 roll button, D-pad/touch movement, hearts/coins, stairs, monster encounters, save state on SD/PocketBase. Keep it original/inspired-by, not a clone of Gladden assets/rules.
|
||
- **Why it fits**: 320×240 is enough for monochrome/vector grid art; ESP32-S3 can generate maps locally; kids can play offline; optional physical button/dice feel keeps the screen-time wholesome.
|
||
- **Status**: Idea captured from A Reyna (DM) on 2026-07-16 after reviewing Gladden Design Paper Apps.
|