Atlas project production

Board Meeting Livestream AV Workflow

Runs board-meeting and district-event AV production using a Linux laptop and OBS for multi-camera switching, room-audio ingest, local recording, and YouTube livestream output.

Internal-only entry. Do not publish externally without review.
Type
System
Lifecycle
Active
Last touched
2026-03-26
Visibility
Internal

Purpose

Provide a repeatable district AV production workflow for board meetings and similar public-facing events.

Current state

Registry evidence supports this as an active district operational workflow. Current practice centers on Linux laptop + OBS production control, multi-camera switching, USB room-audio ingest, local recording, and livestream distribution.

Next step

Document current runbook location, channel-credential custodianship, and standardized portable/offsite kit procedure.

Interfaces

Inputs
  • board and podium camera feeds
  • USB audio ingest from room mixer
  • event run-of-show and operator cues
Outputs
  • live YouTube stream
  • local meeting recording
  • operator-routed display/program outputs

Reality to Action trace

Reality Ingestion

Not in scope.

Canonical Storage

Not in scope.

Automation Engines

Not in scope.

Human Interfaces

Contributes in this stage.

Operational Adoption

Contributes in this stage.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Data integrity and contracts

Source of truth rules

  • Event-day operator workflow and validated AV routing state are authoritative for live production execution.
  • Recording and stream outputs should be reconciled against event timeline notes for post-event quality checks.

Safe handling

  • Restrict streaming credentials and channel administration access.
  • Use preflight checks for room AV, capture paths, and network continuity before go-live.

Operational notes

Reliability posture

High operational significance; failures are visible to public audiences and require immediate manual recovery steps.

Observability

  • OBS scene and recording state
  • stream health in YouTube control surface
  • operator checklist and event notes

Security and privacy

Primarily public-meeting media content with internal operational controls for credentials and channel administration.

Dependencies

Upstream
  • room AV readiness
  • capture hardware availability
  • network continuity
Downstream
  • public meeting transparency
  • district communication archives

Ownership

Owners

Technology Services

Users

Technology Services, district communications stakeholders

Board Meeting Livestream AV Workflow

Operational Notes

  • Production control point is a Linux laptop running OBS.
  • Typical input model includes multiple camera sources (board/cabinet and podium views where available) and USB audio ingest from the room mixer.
  • Runtime output includes both local recording and YouTube livestream delivery, with operator-managed scene switching and room/display routing.
  • Workflow supports portable/offsite meeting configurations when district event logistics require it.

Registry Alignment

  • Registry context: former INT-035 is no longer counted as a standalone integration in the BOUSD registry.
  • Registry clarified: Atlas keeps this as a supported district operational workflow with clear runtime shape rather than as an integration record.
  • Validation gaps: current runbook location, credential custodianship, and standardized offsite-kit procedures still need explicit documentation.