Compare commits

...

2 Commits

Author SHA1 Message Date
aeroreyna b8e48f1d63 daily auto-sync 2026-07-04 2026-07-04 23:00:01 -04:00
aeroreyna 60efa9dca1 Update completed family reminders and tasks 2026-07-04 08:11:48 -04:00
11 changed files with 112 additions and 47 deletions
@@ -6,13 +6,12 @@ Tags: #marriage #course #cuba
# Marriage Course Index
Ongoing marriage course with brothers from Cuba.
Completed marriage course with brothers from Cuba. Archived 2026-07-04 after Adolfo said the course had been done for some time.
## 📅 Schedule & Status
- **Current Lesson**: [[Lesson 07]]
- **Format**: Weekly videos recorded throughout the week.
- **Meeting**: Saturdays at 10:00 AM.
- **Next Agenda**: Discussion of Lesson 7 and review of Lesson 6 homework.
- **Status**: Completed / no longer active.
- **Archived**: 2026-07-04.
- **Former format**: Weekly videos recorded throughout the week; Saturday 10:00 AM meetings.
## 📚 Lessons
- [[Lesson 06]]: The Power of Faith (Homework Review Today)
+3 -2
View File
@@ -51,7 +51,8 @@ Tags: [areas, maintenance, habits, family, sleep, reading]
- Goal is consistency over perfection.
- If missed, restart the next day without penalty.
- Optional metric: track streak count each Friday.
- Hermes cron job `45acb3a9f639` sends the weekday 8:30 PM reminder to the current WhatsApp chat.
- Hermes cron job `45acb3a9f639` sends the weekday 8:30 PM wind-down reminder to the current WhatsApp chat.
- When the family replies `done`, `partial`, or `missed` with optional notes, update the corresponding row in this tracker.
- Created/verified 2026-05-29 after Adolfo requested integration with the family bot.
- 2026-06-09: Added daily family silent-reading routine, every day until the family says otherwise. At 7:45 PM, reminder is to get snack, brush teeth, put pajamas on, clean rooms, and pick books. At 8:00 PM, family gathers in the living room for 35 chapters of the audio Bible, short discussion, prayer, then quiet reading until bed. Hermes cron jobs `eea936742523` and `c5479f8b4329` send the reminders to the current WhatsApp family chat.
- 2026-06-09: Added daily family silent-reading routine, every day until the family says otherwise. At 7:45 PM, reminder was to get snack, brush teeth, put pajamas on, clean rooms, and pick books. At 8:00 PM, family gathers in the living room for 35 chapters of the audio Bible, short discussion, prayer, then quiet reading until bed.
- 2026-07-04: Adolfo said the family no longer needs silent-reading reminders. Removed Hermes cron jobs `eea936742523` and `c5479f8b4329`; do not include silent-reading nudges in the morning briefing unless asked again.
+2 -2
View File
@@ -19,8 +19,8 @@ Tags: [areas, maintenance, household, admin, tasks]
- [x] Attend financial advisor appointment with James Phillips (Tue, Jun 16, 2026, 11:00 AM1:00 PM ET, RingCentral Meeting ID: 321722788). Went well; follow-up in-person session scheduled. (Captured 2026-05-27, completed/updated 2026-06-16, A Reyna)
- [ ] Attend in-person financial planning session with James Phillips on Saturday, July 11, 2026, 11:00 AM2:00 PM ET (3 hours). Location/details TBD. (Captured 2026-06-16, A Reyna)
- [x] Fridge warranty/service appointment completed Wednesday, June 17, 2026. Whirlpool appliance, model WRS325SDHZ13, serial HRE3403608, service job SWPV64ED5019-1. Provider: Wsvc Brandt's Appliance Serv, 4415 77th St, Vero Beach, FL, +1 (772) 562-5759. Visit covered by warranty. (Captured 2026-06-15; updated 2026-06-17, A Reyna)
- [ ] Follow up on fridge warranty repair part/order from Wsvc Brandt's Appliance Serv. Technician said a part needs to be ordered and added to the warranty coverage/process. (Captured 2026-06-17, A Reyna)
- [ ] Attend confirmed ENT appointment on Thursday, June 18, 2026. Adolfo confirmed the appointment. (Captured 2026-06-17, A Reyna)
- [x] Fridge completely fixed; no further warranty repair follow-up needed. Original provider: Wsvc Brandt's Appliance Serv. (Captured 2026-06-17; completed/updated 2026-07-04, A Reyna)
- [x] Attend confirmed ENT appointment on Thursday, June 18, 2026. Adolfo confirmed the appointment. (Captured 2026-06-17; completed by 2026-06-18)
- [ ] Verify Neptune flood insurance autopay processed for $870.23 and coverage renewed for 220 Emerald after July 22, 2026. Renewal policy TNF4366115; expiring policy TNF4093986; premium notice invoice 1821199; coverage through August 21, 2027. See [[220_emerald_flood_insurance]]. (Captured 2026-06-15, A Reyna)
- [ ] Verify 220 Emerald homeowners insurance renewal is paid before 2026-08-06. Policy OIH0012918 with Orange Insurance Exchange / Cabrillo; full pay $6,703.55; minimum due $2,202.40; bill says FILO Mortgage LLC has been invoiced and renewal does not include flood coverage. See [[220_emerald_homeowners_insurance]]. (Captured 2026-06-23, A Reyna)
- [x] Automate weekday 8:30 PM reminder: read a book, relax, sleep. (Captured 2026-05-27, A Reyna; Hermes cron created 2026-05-29)
+1 -1
View File
@@ -136,7 +136,7 @@ Tags: [areas, maintenance, health, appointments, radiology]
- Phone: (321) 939-3000.
- Hours shown in screenshot: Open; closes 5 PM.
- Location clue shown: AdventHealth Celebration / Hospital Rd area.
- Follow-up: Adolfo was referred by ENT to this doctor; appointment/scheduling status not yet recorded.
- Follow-up: Adolfo was referred by ENT to this doctor. As of 2026-07-04, Adolfo plans to wait some time before scheduling; do not keep this as an active reminder unless he asks again.
## Related
- [[maintenance/index]]
@@ -1,26 +1,24 @@
<!doctype html><html><head><meta charset="utf-8"><title>livestream_media_system_report_for_ari_sardius</title><style>
@page { size: Letter; margin: 0.62in 0.58in; }
* { box-sizing: border-box; }
body { font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; color: #1f2933; line-height: 1.48; font-size: 10.4pt; }
h1 { font-size: 28pt; color: #0f2f4f; margin: 0 0 10px; letter-spacing: -0.03em; padding-bottom: 14px; border-bottom: 5px solid #2f80ed; }
h2 { font-size: 17pt; color: #0f2f4f; margin-top: 27px; padding: 8px 12px; background: linear-gradient(90deg,#eaf3ff,#ffffff); border-left: 5px solid #2f80ed; break-after: avoid; }
h3 { font-size: 13pt; color: #164b7a; margin-top: 18px; border-bottom: 1px solid #d6e4f0; padding-bottom: 4px; break-after: avoid; }
h4 { font-size: 11.5pt; color: #2f5f8f; margin-top: 14px; break-after: avoid; }
p { margin: 7px 0; }
ul, ol { margin-top: 5px; padding-left: 22px; }
li { margin: 3px 0; }
blockquote { margin: 14px 0; padding: 12px 16px; border-left: 5px solid #f2c94c; background: #fff9e6; color: #3d3200; font-size: 11pt; }
code { background: #eef4fa; padding: 1px 4px; border-radius: 4px; color: #0b456f; font-family: "SFMono-Regular", Consolas, monospace; font-size: 8.7pt; }
table { width: 100%; border-collapse: collapse; margin: 12px 0 18px; font-size: 8.2pt; page-break-inside: auto; }
th { background: #0f2f4f; color: white; text-align: left; padding: 7px 6px; }
td { border: 1px solid #d9e2ec; padding: 6px; vertical-align: top; }
tr:nth-child(even) td { background: #f7fbff; }
a { color: #1a73e8; text-decoration: none; }
strong { color: #102a43; }
.cover { border: 1px solid #d6e4f0; border-radius: 16px; padding: 20px; background: linear-gradient(135deg,#f7fbff 0%,#ffffff 55%,#f8fbff 100%); }
.footer-note { margin-top: 24px; font-size: 8.3pt; color: #64748b; border-top: 1px solid #d9e2ec; padding-top: 8px; }
@media print { h2, h3, h4 { break-after: avoid; } table, blockquote { break-inside: avoid; } }
</style></head><body><div class="cover"><h1 id="emi-livestream-and-media-workflow-report-for-ari-sardius">EMI Livestream and Media Workflow Report for Ari / Sardius</h1>
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>EMI Livestream and Media Workflow Report for Ari / Sardius</title>
<style>
body { font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; line-height: 1.55; max-width: 900px; margin: 40px auto; padding: 0 24px; color: #1f2933; }
h1, h2, h3 { color: #111827; line-height: 1.25; }
h1 { border-bottom: 3px solid #1f2937; padding-bottom: 0.35rem; }
h2 { margin-top: 2rem; border-bottom: 1px solid #d1d5db; padding-bottom: 0.2rem; }
blockquote { border-left: 4px solid #6b7280; margin-left: 0; padding-left: 1rem; color: #374151; }
code { background: #f3f4f6; padding: 0.1rem 0.25rem; border-radius: 4px; }
table { border-collapse: collapse; width: 100%; margin: 1rem 0; }
th, td { border: 1px solid #d1d5db; padding: 0.45rem; vertical-align: top; }
th { background: #f3f4f6; }
@media print { body { max-width: none; margin: 0.5in; } }
</style>
</head>
<body>
<h1 id="emi-livestream-and-media-workflow-report-for-ari-sardius">EMI Livestream and Media Workflow Report for Ari / Sardius</h1>
<h2 id="purpose-of-this-first-draft">Purpose of This First Draft</h2>
<p>This report is a first-draft briefing for a conversation with Ari Burt / Sardius Media. It is intended to give enough context for meaningful strategic advice without asking for a simple gear shopping list.</p>
<p>The central question is:</p>
@@ -81,7 +79,8 @@ strong { color: #102a43; }
<li>local ministry website through Subsplash: https://florida.emmint.com/,</li>
<li>The Walking Voice Media YouTube channel: https://www.youtube.com/@TheWalkingVoiceMedia,</li>
<li>KingdomEMI YouTube channel: https://www.youtube.com/@kingdomemi,</li>
<li>Facebook page: https://www.facebook.com/kingdomemi/.</li>
<li>Facebook page: https://www.facebook.com/kingdomemi/,</li>
<li>EMI private social app / website app: an owned private communication platform. This should be included as a strategic ministry platform, not just as a technical side project.</li>
</ul>
<p>Current policy:</p>
<ul>
@@ -90,6 +89,19 @@ strong { color: #102a43; }
<li>When a new YouTube teaching is published, create 35 short clips per week for YouTube and Facebook.</li>
<li>Walking Voice Media target cadence: 12 outreach pieces per month.</li>
</ul>
<h3 id="emi-private-social-app-owned-community-platform">EMI Private Social App / Owned Community Platform</h3>
<p>The report should also account for EMI's private social app / website app. This app is meant to become a secure, invitation-based place for EMI-connected people to communicate globally without depending only on public social platforms.</p>
<p>Current/desired capabilities include:</p>
<ul>
<li>posting and social updates,</li>
<li>open and closed groups,</li>
<li>global chat with automatic translation,</li>
<li>media series,</li>
<li>private/invitation-based access,</li>
<li>an onboarding model where people can be invited by someone already inside the app,</li>
<li>a more secure private place for international communication, discipleship, coordination, and media distribution.</li>
</ul>
<p>Strategically, this changes the media conversation. EMI does not only need a livestream/archive workflow for public platforms; it also needs a workflow for feeding selected, approved content into an owned global community space. Public YouTube/Facebook can serve outreach and discovery, while the private EMI app can support ongoing relationship, closed-group communication, translated discussion, regional coordination, and secure media series for invited participants.</p>
<h2 id="current-local-sunday-workflow">Current Local Sunday Workflow</h2>
<h3 id="current-signal-flow">Current Signal Flow</h3>
<p>Audio path:</p>
@@ -250,6 +262,7 @@ strong { color: #102a43; }
<li>International event playbook for strong internet, weak internet, and hybrid scenarios.</li>
<li>NAS-first archive with metadata and transcript search.</li>
<li>AI-assisted workflow for transcription, clip selection, captions, summaries, translations, and social repurposing.</li>
<li>Publishing pipeline into the EMI private social app, including media series, translated discussions, and open/closed group distribution.</li>
</ul>
<h2 id="decision-areas-where-we-need-expert-help">Decision Areas Where We Need Expert Help</h2>
<h3 id="1-translation-multilingual-experience">1. Translation / Multilingual Experience</h3>
@@ -313,6 +326,15 @@ strong { color: #102a43; }
<li>How should captions, translations, summaries, thumbnails, titles, and descriptions be generated?</li>
<li>What review process should protect quality and theological/message accuracy?</li>
</ul>
<h3 id="7-owned-community-app-private-social-platform">7. Owned Community App / Private Social Platform</h3>
<p>Questions:</p>
<ul>
<li>How should the private EMI social app fit alongside Subsplash, YouTube, Facebook, and Walking Voice Media?</li>
<li>What content should be public outreach versus invitation-only community content?</li>
<li>How should media series be packaged for the app after a livestream or teaching is recorded?</li>
<li>How should automatic translation in global chat and groups connect with the broader livestream translation strategy?</li>
<li>What security, moderation, onboarding, and invitation controls should be considered for a global ministry communication platform?</li>
</ul>
<h2 id="what-we-are-not-asking-for-yet">What We Are Not Asking For Yet</h2>
<p>We are not primarily asking for a shopping list.</p>
<p>Before buying more equipment or software, we want to understand:</p>
@@ -331,9 +353,10 @@ strong { color: #102a43; }
<li>What is the best realistic path for multilingual livestream and in-room translation today?</li>
<li>How would you structure our media archive so it becomes searchable and reusable instead of just stored videos?</li>
<li>What AI workflows are mature enough to use now for captions, metadata, clips, summaries, and translations?</li>
<li>How should we integrate the EMI private social app as an owned, invitation-based global communication and media distribution platform?</li>
<li>At what point does OBS/Zoom/Subsplash stop being enough?</li>
<li>What equipment/software do churches commonly buy too early?</li>
<li>What would you measure to know whether the media workflow is improving: stream health, watch time, engagement, clip performance, volunteer load, archive reuse, or something else?</li>
<li>What would you measure to know whether the media workflow is improving: stream health, watch time, engagement, clip performance, volunteer load, private-app engagement, archive reuse, or something else?</li>
</ol>
<h2 id="recommended-first-priorities">Recommended First Priorities</h2>
<h3 id="priority-1-translation-prototype">Priority 1: Translation Prototype</h3>
@@ -347,6 +370,9 @@ strong { color: #102a43; }
<h3 id="priority-5-ai-post-production-pilot">Priority 5: AI Post-Production Pilot</h3>
<p>Choose one strong teaching and test a full pipeline:</p>
<p><code>recording → transcript → summary → clip candidates → reviewed clips → captions → title/description → YouTube/Facebook/Walking Voice publishing</code></p>
<h3 id="priority-6-private-app-publishing-pilot">Priority 6: Private App Publishing Pilot</h3>
<p>Choose one approved teaching or event series and test how it should live inside the EMI private social app:</p>
<p><code>approved recording → transcript/summary → media series packaging → translated discussion prompts → open/closed group placement → invitation-only access review → engagement/moderation feedback</code></p>
<h2 id="proposed-attachments-examples-to-add-before-sending">Proposed Attachments / Examples to Add Before Sending</h2>
<p>Before sharing this report, add links to:</p>
<ul>
@@ -354,12 +380,15 @@ strong { color: #102a43; }
<li>one strong teaching suitable for public outreach,</li>
<li>one example where lyrics/screen share reduced video quality,</li>
<li>one international gathering example if available,</li>
<li>one short clip or desired example style if available.</li>
<li>one short clip or desired example style if available,</li>
<li>screenshots or a preview link for the EMI private social app if helpful for the conversation.</li>
</ul>
<h2 id="related-working-notes">Related Working Notes</h2>
<ul>
<li>Livestream and Video Generation Process</li>
<li>EMI Media Outreach and YouTube Strategy</li>
<li>kenya trip 2026</li>
<li>Technology for the Kingdom of God</li>
</ul></div><div class="footer-note">Generated from: /home/adolforeyna/brain/projects/livestream_media_system_report_for_ari_sardius.md</div></body></html>
<li>[[Livestream and Video Generation Process]]</li>
<li>[[EMI Media Outreach and YouTube Strategy]]</li>
<li>[[kenya_trip_2026]]</li>
<li>[[Technology for the Kingdom of God]]</li>
</ul>
</body>
</html>
+1 -1
View File
@@ -7,10 +7,10 @@
- [[reMarkable Hermes Communication App]]: Tablet/Hermes communication app over reMarkable Paper Pro.
- [[PARA Brain MCP Server]]: Server-side MCP/search layer for the Reyna family brain.
- **[[Areas]]:** Ongoing responsibilities and household maintenance.
- [[Marriage Course Index]]: Weekly sessions with Cuba.
- **[[Resources]]:** Interests, reference material, and research.
- [[Family Timeline]]: Chronological milestones.
- [[Clawbot Carryover Ideas]]: old OpenClaw ideas worth revisiting.
- **[[Archives]]:** Completed or paused items.
- [[kenya_trip_2026]]
- [[marriage_course]]: Marriage course with Cuba (completed 2026-07-04).
- **[[Inbox]]:** Unprocessed thoughts and quick captures.
@@ -79,7 +79,8 @@ Current channels/platforms:
- local ministry website through Subsplash: https://florida.emmint.com/,
- The Walking Voice Media YouTube channel: https://www.youtube.com/@TheWalkingVoiceMedia,
- KingdomEMI YouTube channel: https://www.youtube.com/@kingdomemi,
- Facebook page: https://www.facebook.com/kingdomemi/.
- Facebook page: https://www.facebook.com/kingdomemi/,
- EMI private social app / website app: an owned private communication platform. This should be included as a strategic ministry platform, not just as a technical side project.
Current policy:
@@ -88,6 +89,22 @@ Current policy:
- When a new YouTube teaching is published, create 35 short clips per week for YouTube and Facebook.
- Walking Voice Media target cadence: 12 outreach pieces per month.
### EMI Private Social App / Owned Community Platform
The report should also account for EMI's private social app / website app. This app is meant to become a secure, invitation-based place for EMI-connected people to communicate globally without depending only on public social platforms.
Current/desired capabilities include:
- posting and social updates,
- open and closed groups,
- global chat with automatic translation,
- media series,
- private/invitation-based access,
- an onboarding model where people can be invited by someone already inside the app,
- a more secure private place for international communication, discipleship, coordination, and media distribution.
Strategically, this changes the media conversation. EMI does not only need a livestream/archive workflow for public platforms; it also needs a workflow for feeding selected, approved content into an owned global community space. Public YouTube/Facebook can serve outreach and discovery, while the private EMI app can support ongoing relationship, closed-group communication, translated discussion, regional coordination, and secure media series for invited participants.
## Current Local Sunday Workflow
### Current Signal Flow
@@ -210,6 +227,7 @@ Desired capabilities:
- International event playbook for strong internet, weak internet, and hybrid scenarios.
- NAS-first archive with metadata and transcript search.
- AI-assisted workflow for transcription, clip selection, captions, summaries, translations, and social repurposing.
- Publishing pipeline into the EMI private social app, including media series, translated discussions, and open/closed group distribution.
## Decision Areas Where We Need Expert Help
@@ -280,6 +298,16 @@ Questions:
- How should captions, translations, summaries, thumbnails, titles, and descriptions be generated?
- What review process should protect quality and theological/message accuracy?
### 7. Owned Community App / Private Social Platform
Questions:
- How should the private EMI social app fit alongside Subsplash, YouTube, Facebook, and Walking Voice Media?
- What content should be public outreach versus invitation-only community content?
- How should media series be packaged for the app after a livestream or teaching is recorded?
- How should automatic translation in global chat and groups connect with the broader livestream translation strategy?
- What security, moderation, onboarding, and invitation controls should be considered for a global ministry communication platform?
## What We Are Not Asking For Yet
We are not primarily asking for a shopping list.
@@ -300,9 +328,10 @@ Before buying more equipment or software, we want to understand:
3. What is the best realistic path for multilingual livestream and in-room translation today?
4. How would you structure our media archive so it becomes searchable and reusable instead of just stored videos?
5. What AI workflows are mature enough to use now for captions, metadata, clips, summaries, and translations?
6. At what point does OBS/Zoom/Subsplash stop being enough?
7. What equipment/software do churches commonly buy too early?
8. What would you measure to know whether the media workflow is improving: stream health, watch time, engagement, clip performance, volunteer load, archive reuse, or something else?
6. How should we integrate the EMI private social app as an owned, invitation-based global communication and media distribution platform?
7. At what point does OBS/Zoom/Subsplash stop being enough?
8. What equipment/software do churches commonly buy too early?
9. What would you measure to know whether the media workflow is improving: stream health, watch time, engagement, clip performance, volunteer load, private-app engagement, archive reuse, or something else?
## Recommended First Priorities
@@ -328,6 +357,12 @@ Choose one strong teaching and test a full pipeline:
`recording → transcript → summary → clip candidates → reviewed clips → captions → title/description → YouTube/Facebook/Walking Voice publishing`
### Priority 6: Private App Publishing Pilot
Choose one approved teaching or event series and test how it should live inside the EMI private social app:
`approved recording → transcript/summary → media series packaging → translated discussion prompts → open/closed group placement → invitation-only access review → engagement/moderation feedback`
## Proposed Attachments / Examples to Add Before Sending
Before sharing this report, add links to:
@@ -336,7 +371,8 @@ Before sharing this report, add links to:
- one strong teaching suitable for public outreach,
- one example where lyrics/screen share reduced video quality,
- one international gathering example if available,
- one short clip or desired example style if available.
- one short clip or desired example style if available,
- screenshots or a preview link for the EMI private social app if helpful for the conversation.
## Related Working Notes