daily auto-sync 2026-07-04

projects/livestream_media_system_report_for_ari_sardius.md

@@ -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 3–5 short clips per week for YouTube and Facebook.
 - Walking Voice Media target cadence: 1–2 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