How Event Magi works

What Event Magi does at your event — and what's live today.

From the moment a delegate signs in to the ROI report you hand a sponsor, here is the full picture — with an honest status on what's running in production versus what's rolling out next.

  • 4reusable @mogos engines
  • 7shell components
  • 7Event Magi mini-apps
  • 1deployed surface

Reusable engines (@mogos/*)

Standalone, receipt-emitting engines Event Magi composes — each usable by any other Magi app.

4
  • Gate-greenengine

    matchmaking-engine

    Concord V2 market solver (solveMatchMarket) ranks counterparts by complementarity and mutual fit.

    Deterministic, pure ranking — same inputs return the same result, with an rcp_ receipt per match.

  • Gate-greenengine

    enrichment-engine

    Turns a sparse identity into a match-ready profile from public web and company data.

    Pre-fills the match inputs so an agent onboards a delegate with one identity handle, not a form.

  • Gate-greenengine

    agent-surface

    Auto-generates the API, CLI, and MCP surface for an engine from one definition.

    This is why every Magi app is agent-native by construction: the MCP/OpenAPI/CLI are generated, not hand-written.

  • Gate-greenplatform

    starconnect

    Integration platform with 4 connectors (SMTP, Eventbrite, LinkedIn, Stripe), OAuth2 + webhooks, vaulted secrets and SSRF guards.

    Outbound integrations run through a guarded boundary (vault + SSRF protection), so agent-initiated actions stay inside policy.

Magi shell components (@mogos/magistar)

The shared interface kit every Magi app wears — the same shell, themed per vertical.

7
  • Gate-greencomponent

    MagiRail

    The icon rail and primary navigation that gives every Magi app one identity.

  • Gate-greencomponent

    MagiVoice

    Voice-input affordance with a recording pulse and reduced-motion fallback.

  • Gate-greencomponent

    MagiSearch

    Command-palette search over sections and entities (⌘K).

  • Gate-greencomponent

    MagiChat

    Streaming concierge chat surface with typed message lifecycle.

  • Gate-greencomponent

    MagiTable

    Dense, accessible data table for delegates, matches, and introductions.

    A notes panel built from the Starlight component system
    Real capture · Starlight panel/table component capture
  • Gate-greencomponent

    MagiForm

    Form primitives with labels-above-inputs and full error/disabled/loading states.

  • Gate-greencomponent

    MagiChecklistRow

    Onboarding checklist row used to drive the profile-completeness flow.

    An onboarding checklist built from the Starlight component system
    Real capture · Starlight onboarding-checklist component capture

Starlight design language

The token system and component catalog the Magi shell is built on. Still being formalised.

2
  • In progressdesign-system

    Primitives & tokens

    The buttons, inputs, badges, and color/space tokens that compose every Magi surface.

    A catalog of Starlight UI primitives
    Real capture · Starlight primitives capture
  • In progressdesign-system

    Data & usage components

    Higher-order components — usage meters, panels — for analytics and account surfaces.

    A credit-usage meter built from the Starlight component system
    Real capture · Starlight credit-usage component capture (design reference, not a live Event Magi screen)

Event Magi pack (eventmagi/web)

The vertical mini-apps that make up the product. Pushed to the repo; app screens not yet captured.

7
  • Shippedmini-app

    Onboarding

    LinkedIn sign-in → enrichment → a confirmed, match-ready profile.

  • Shippedmini-app

    Matches

    Engine-backed match feed — the ranked five with reasons, each carrying a receipt.

    Reads directly from matchmaking-engine output; every row exposes its rcp_ receipt id.

  • Shippedmini-app

    Introductions

    Identity-bound, consented introduction loop tracked from interested to met.

  • Shippedmini-app

    Concierge

    A MagiChat-driven concierge that finds matches and requests introductions through guarded tools.

  • In progressmini-app

    Agenda

    Per-delegate personalized agenda over the event programme.

  • In progressmini-app

    Organizer CRM

    The organizer console — room health, curation, and sponsor relationships.

  • In progressmini-app

    Analytics

    Relationship movement and meeting outcomes — ROI the organizer can show a sponsor.

Platform, distribution & proof

The substrate that makes the above reusable, discoverable, and auditable.

3
  • Gate-greentemplate

    @mogos/magi-landing

    This template — one config drives a GEO + agent-first landing for any Magi app.

    Emits llms.txt, a JSON-LD graph, and a /.well-known product manifest from the same config as the page.

  • Deployedsurface

    catalyst.mogos.ch

    The Davos Catalyst customer skin — live, with people-matching running in production.

  • Shippeddoctrine

    Auditable outcome record

    Every match, introduction, and outcome is kept as a replayable record — the proof layer behind sponsor ROI.

    The audit layer — an integrating agent verifies outcomes instead of trusting them.