EventOps.

For the people behind the event

Keep your event plan consistent when things change.

Schedules, rooms and volunteer assignments belong together. Review each change and its evidence before it becomes official.

Watch the walkthrough Run it locally

See the workflow

An event update, reviewed end to end.

About 2 minutes 32 seconds. Actual application screens and a previously completed live Meta workflow, using fictional event records. The edited video includes labeled synthetic narration.

If the player does not load, open the video directly.

About this page

This is a public EventOps overview. The full application runs locally using the repository setup instructions. This page has no sign-in, editable event workspace or live model processing.

How EventOps works

The organizer stays in control.

  1. 01

    Describe

    Save a specific update by text or upload a voice recording for a draft transcript.

  2. 02

    Review

    Inspect affected records, room conflicts, volunteer coverage and missing facts.

  3. 03

    Confirm

    Correct the interpretation and explicitly confirm new facts before a proposal is created.

  4. 04

    Approve

    Compare the exact change. Transactional checks reject stale or invalid proposals.

  5. 05

    Briefing

    Read or export the approved revision and inspect its history.

Meta integration

Interpretation with clear boundaries.

Muse Spark interprets confirmed updates and selects among deterministically validated options. Muse Voice Transcribe produces a draft transcript for organizer review.

The models cannot approve an official event plan. Deterministic code checks constraints, and the database checks the full proposal again during approval.

Current availability

Local manual review, approval, history and briefing work without a model key. General live AI is disabled, and new model calls are paused.

Full live quality evaluation, human accessibility acceptance, the device matrix and hosted operations checks remain open.

Read verification and known limits

Explore the implementation

Try a fictional event on your machine.

The repository includes setup instructions, a guided sample, source code and recorded verification evidence. Local sign-in uses a test inbox; no model key is needed for the manual workflow.

Open setup instructions