FamReynaBrain/projects/business_ideas.md

Date, Author, Tags

Date	Author	Tags
2026-04-26	Antigravity

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.