Livestorm

Build me a focused video meetings and webinars workflow for the personal core of Livestorm. Requirements:

- Use Docker Compose, Jitsi Meet, a small Next.js 15 control panel, PostgreSQL, and TURN. Model rooms, signed invitations, participants, consent state, and optional recordings; keep stable source IDs and timestamps.
- Paid product context: Run a small browser webinar with registrations and a simple replay page. Build only this DIY scope: Run a small browser webinar with registrations, issue signed room links, publish a simple replay page, and keep recordings only when every participant is clearly informed.
- For video meetings and webinars, register attendees and issue signed links for a small self-managed video room.
- Show host controls, attendee join state, and explicit recording consent before any replay capture.
- Publish a replay only after processing finishes and permission is recorded.
- Use a local web page with input, progress, review, and export views. Required input or access: public server with strong bandwidth; domain and TLS.
- Recovery: An expired link cannot join; a failed recording must not create a playable replay or lose consent history.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An expired link cannot join; a failed recording must not create a playable replay or lose consent history.
- Out of scope: global media, email delivery, engagement, integrations, analytics, and reliability; global low-latency media network. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for Livestorm

## Project scope
Run a small browser webinar with registrations, issue signed room links, publish a simple replay page, and keep recordings only when every participant is clearly informed.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Livestorm, run a small browser webinar with registrations and a simple replay page. The hard boundary is global media, email delivery, engagement, integrations, analytics, and reliability, plus real-time media infrastructure and reliability.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- public server with strong bandwidth
- domain and TLS
- TURN server
- Docker
- explicit participant consent for recording

## Stack and architecture
- Use Docker Compose, Jitsi Meet, a small Next.js 15 control panel, PostgreSQL, and TURN.
- Model rooms, signed invitations, participants, consent state, and optional recordings; keep stable source IDs and timestamps.
- Interface for this video meetings and webinars workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- An expired link cannot join; a failed recording must not create a playable replay or lose consent history.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: global media, email delivery, engagement, integrations, analytics, and reliability.

## Agent implementation rules
- Project rule, data: Model rooms, signed invitations, participants, consent state, and optional recordings; keep stable source IDs and timestamps.
- Project rule, behavior: For video meetings and webinars, register attendees and issue signed links for a small self-managed video room.
- Project rule, recovery: An expired link cannot join; a failed recording must not create a playable replay or lose consent history.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this video meetings and webinars operation with sample or user-owned data: For video meetings and webinars, register attendees and issue signed links for a small self-managed video room.
- Show a concrete result or export: Publish a replay only after processing finishes and permission is recorded.
- State the practical limit: global media, email delivery, engagement, integrations, analytics, and reliability.

## Engineering roadmap
1. Phase 1, architecture and data: Use Docker Compose, Jitsi Meet, a small Next.js 15 control panel, PostgreSQL, and TURN. Model rooms, signed invitations, participants, consent state, and optional recordings; keep stable source IDs and timestamps.
2. Phase 2, implement: For video meetings and webinars, register attendees and issue signed links for a small self-managed video room.
3. Phase 3, implement: Show host controls, attendee join state, and explicit recording consent before any replay capture.
4. Phase 4, review and output: Publish a replay only after processing finishes and permission is recorded.
5. Phase 5, recovery and acceptance: Verify this invariant with a saved fixture: An expired link cannot join; a failed recording must not create a playable replay or lose consent history. State the practical limit: global media, email delivery, engagement, integrations, analytics, and reliability.

## Paid-product capabilities outside this build
- global media, email delivery, engagement, integrations, analytics, and reliability
- global low-latency media network
- dial-in and telephony
- large webinars
- transcription, support, and compliance

## Implementation prompt
Build me a focused video meetings and webinars workflow for the personal core of Livestorm. Requirements:

- Use Docker Compose, Jitsi Meet, a small Next.js 15 control panel, PostgreSQL, and TURN. Model rooms, signed invitations, participants, consent state, and optional recordings; keep stable source IDs and timestamps.
- Paid product context: Run a small browser webinar with registrations and a simple replay page. Build only this DIY scope: Run a small browser webinar with registrations, issue signed room links, publish a simple replay page, and keep recordings only when every participant is clearly informed.
- For video meetings and webinars, register attendees and issue signed links for a small self-managed video room.
- Show host controls, attendee join state, and explicit recording consent before any replay capture.
- Publish a replay only after processing finishes and permission is recorded.
- Use a local web page with input, progress, review, and export views. Required input or access: public server with strong bandwidth; domain and TLS.
- Recovery: An expired link cannot join; a failed recording must not create a playable replay or lose consent history.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An expired link cannot join; a failed recording must not create a playable replay or lose consent history.
- Out of scope: global media, email delivery, engagement, integrations, analytics, and reliability; global low-latency media network. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.