diff --git a/projects/livestream_video_generation_process.md b/projects/livestream_video_generation_process.md
index 390021c..4ccb963 100644
--- a/projects/livestream_video_generation_process.md
+++ b/projects/livestream_video_generation_process.md
@@ -22,6 +22,183 @@ Prepare for a meeting with a media producer by capturing:
 - Prior AV/media planning from [[kenya_trip_2026]] included multi-camera recording, dedicated internet for streaming, audio interface usage, and livestream quality/reliability concerns.
 - This project should become the central working note for documenting the current process and producer feedback.
 
+## Current Media System Assessment Report Draft - 2026-06-27
+
+### Report Type
+Current-state AV / broadcast media assessment, combining:
+- AV / broadcast current-state assessment.
+- AV system as-built documentation.
+- Site survey / technical discovery report.
+- AVIXA-style performance verification framing.
+
+Reference: AVIXA `Audiovisual Systems Performance Verification` standard, Document 10:2013, describes a framework for determining audiovisual system elements, verification timing, criteria/metrics, and reporting procedures.
+
+### 1. Executive Summary
+_To be drafted after interview._
+
+Capture:
+- What the church currently does for media and livestream.
+- Main platforms used.
+- Current goals: livestream quality, reliability, clips, archiving, volunteer sustainability.
+- Top 3 pain points.
+
+### 2. Ministry / Use Case
+_To be documented._
+
+Questions to answer:
+- What services/events are streamed or recorded?
+- How often does media production happen?
+- Who is the intended audience: in-person overflow, online members, archive viewers, outreach, social media?
+- What outputs are expected: livestream, full sermon archive, short clips, reels, podcasts, thumbnails, announcement videos?
+
+### 3. Current Signal Flow
+_To be documented._
+
+Audio chain:
+`Microphones / instruments → soundboard → livestream audio feed → computer / encoder / OBS → streaming platform → recording / archive → editing / social clips`
+
+Video chain:
+`Cameras → switcher / capture card / OBS → graphics / slides → encoder → Subsplash / YouTube / Facebook`
+
+### 4. Equipment Inventory
+_To be documented._
+
+| Category | Item | Model | Location | Purpose | Notes / Problems |
+| --- | --- | --- | --- | --- | --- |
+| Cameras |  |  |  |  |  |
+| Lenses |  |  |  |  |  |
+| Tripods / mounts |  |  |  |  |  |
+| Audio console |  |  |  |  |  |
+| Microphones |  |  |  |  |  |
+| Audio interface |  |  |  |  |  |
+| Computer / encoder |  |  |  |  |  |
+| Capture cards |  |  |  |  |  |
+| Network gear |  |  |  |  |  |
+| Lighting |  |  |  |  |  |
+| Cables / adapters |  |  |  |  |  |
+| Storage drives |  |  |  |  |  |
+| Software subscriptions |  |  |  |  |  |
+
+### 5. Software / Platforms
+_To be documented._
+
+Include:
+- OBS or other switching / encoding software.
+- Subsplash.
+- YouTube.
+- Facebook.
+- ProPresenter / EasyWorship / slides / lyrics tools.
+- Editing software.
+- AI tools.
+- Transcription tools.
+- Storage / archive tools.
+
+### 6. Internet / Network
+_To be documented._
+
+Capture:
+- Wired or Wi-Fi connection.
+- Upload speed.
+- Backup internet.
+- Dedicated media network or shared church Wi-Fi.
+- Known dropouts.
+- Router / switch location.
+- Whether the stream computer is hardwired.
+
+### 7. Livestream Workflow
+_To be documented._
+
+Before service:
+- Turn on gear.
+- Check audio.
+- Check camera framing.
+- Start OBS / encoder.
+- Confirm stream destination.
+- Test recording.
+
+During service:
+- Monitor audio.
+- Switch cameras / scenes.
+- Watch stream health.
+- Operate slides / lyrics.
+
+After service:
+- Stop stream.
+- Save recording.
+- Upload / archive.
+- Clip sermon.
+- Post to social media.
+
+### 8. Team / Roles
+_To be documented._
+
+Roles to identify:
+- Livestream director.
+- Audio operator.
+- Camera operator(s).
+- Slides / lyrics operator.
+- Stream monitor.
+- Editor.
+- Social media / posting.
+- Backup people.
+
+Note whether roles are volunteer-dependent and whether too much depends on one person.
+
+### 9. Current Quality / Pain Points
+_To be documented._
+
+Audio:
+- Mix quality.
+- Room noise.
+- Vocal clarity.
+- Music balance.
+- Stream mix vs house mix.
+
+Video:
+- Camera angles.
+- Resolution.
+- Lighting.
+- Focus / exposure.
+- Movement / shot variety.
+
+Reliability:
+- Internet.
+- OBS / software stability.
+- Audio sync.
+- Power / cable issues.
+
+Workflow:
+- Manual steps.
+- Lack of checklist.
+- Volunteer training difficulty.
+- Difficulty creating clips afterward.
+
+### 10. Recording / Archive / Post-Production
+_To be documented._
+
+Include:
+- Whether there is a local recording.
+- Recording resolution and audio settings.
+- Where files are stored.
+- Naming convention.
+- Backup process.
+- How sermon clips are made.
+- Captions, thumbnails, titles, descriptions.
+- How long files are kept.
+
+### 11. Desired Future State
+Draft framing:
+> We want a simple, reliable, volunteer-friendly workflow that captures services, streams them consistently, archives them cleanly, and makes it easy to create useful short-form content afterward without overwhelming the team.
+
+### 12. Questions for Ari / Sardius
+- What are the top 3 improvements you would prioritize?
+- Is our biggest bottleneck audio, video, internet, workflow, or staffing?
+- What should we standardize first?
+- What should we avoid buying too early?
+- What would a sustainable small-church media workflow look like?
+- How should we think about archiving and metadata from day one?
+- When is OBS enough, and when should we consider a dedicated encoder/platform?
+
 ## Current Livestream Process
 _To be documented._