Enact: Dynamic Scheduling

Repo: enact . Topic: _botAgendar.

The scheduling resolver turns spoken or typed contributions into public Luma calendar events, supporting dynamic, bottom-up agenda formation. It was designed from within self-organising activities of in-person decentralised groups - to maintain coherence in highly adaptive, sometimes informal organisations operating under rapidly changing environmental conditions (emergent contexts).

Participants propose events in natural language on _botAgendar. The resolver extracts structured schedule fields against the schedule protocol, creates or updates the event on a shared open Luma calendar, and persists an Agenda node in Neo4j as a durable record of group coordination. A default online meeting URL is applied when no specific link is given; optional fields support physical venues, capacity, visibility, and other event metadata.

Enact also hosts resolve-only handlers for _botDecidir and _botRecursos; this page documents the scheduling resolver only.

How it works

A voice note or text message describing an event is ingested by timelining, transcribed when needed, and passed to enact in resolve mode. The resolver loads the entry, extracts required fields (name, start_at, timezone), creates a Luma event, and writes an Agenda node linked to the entry. Generic virtual mentions (“on Zoom”, “online”) map to the default meeting link; physical addresses are sent to Luma as geo_address_json.

When a participant replies to the original message with a correction, timelining forwards the webhook in update mode (without re-ingesting). Enact loads the current Agenda, extracts optional patch fields, updates the linked Luma event, and records a new Agenda version with an overwriting relationship — preserving correction history on one live calendar event.

Backlog processing uses POST /api/webhook/resolve/schedule?backlog=true to resolve the next pending entry.

HTTP routes

Auth for infra routes: verifyInfraRequest in src/lib/private-auth.ts.

Eligibility and graph writes

Resolve mode runs when the topic is _botAgendar and the entry has voice with ready transcription, or non-empty text content. Voice-only entries skip until transcribed (voice_not_ready). Reply messages are not ingested as entries — they arrive via update mode only.

On resolve, enact deletes any existing Agenda for the entry (idempotent re-resolve), creates a new node with extracted fields and lumaEventId, and links Agenda -[:FOR_ENTRY]-> Entry.

On update, enact creates a successor Agenda linked to the prior version (Agenda -[:overwriting]-> Agenda) and the same entry. The protocol defines a schedule node schema; the resolver persists it under the Agenda graph label.

{
  "domain": "enaction",
  "version": "1.0.0",
  "subgraph": {
    "relationships": [
      {
        "from": "participant",
        "to": "schedule",
        "type": "ORGANIZES",
        "cardinality": "many-to-many"
      },
      {
        "from": "organisation",
        "to": "schedule",
        "type": "FOR_ORGANISATION",
        "cardinality": "many-to-many"
      },
      {
        "from": "schedule",
        "to": "agenda",
        "type": "RESOLVES_TO",
        "cardinality": "one-to-many"
      },
      {
        "from": "updates",
        "to": "agenda",
        "type": "CORRECTS",
        "cardinality": "many-to-one"
      },
      {
        "from": "agenda",
        "to": "agenda",
        "type": "OVERWRITING",
        "cardinality": "many-to-one"
      }
    ]
  }
}

Luma integration

Created events appear on the hub’s public Luma calendar, making bottom-up proposals visible for emergent agenda formation.

Boundary with timelining

Enact does not create Entry nodes or run transcription. Failed resolve sets resolveStatus: failed on the entry; timelining cron retries via POST ?entryId=.

Related docs

• Organising config — _botAgendar forward + resolve routing
• Schedule protocol — schema the resolver extracts against
• Resolvers overview — forward vs resolve across siblings

Overall flow