Jadpo is experimental and not ready for production. These docs follow the compiler's main branch as of 30 Oct 2026. What's built · Install 0.1.0
jadpo
Reference: Jobs and events

Jobs and events · rule

subscriber.event_invalid

Subscriber's on: doesn't name an event type.

Area 12, Jobs and events; not declinable; the next step is usually the agent's.

on: names an event, not an entity:

example
type Note = Text {    max_length: 200}entity Reminder {    id: Uuid    note: Note    sent: Bool    policy: {        create: [Access.authenticated]        read: [Access.system]        update: [Access.system]    }}type ReminderDue = Event {    reminder_id: Reminder.id}action send_reminder(reminder_id: Reminder.id) fails ReminderNotFound -> Unit {    attempt Reminder.update(reminder_id) {        set: {            sent: true        }    }}subscriber send_due {    on: Reminder    run: send_reminder(event.reminder_id)}
text
error: `on: Reminder` isn't an event --> main.jadpo:30:9   |30 |     on: Reminder   |         ^^^^^^^^ not an event  reason: A subscriber listens for one event, a type with the `Event` base that an action emits.  next: Name an event, declared as `type <Name> = Event { ... }` in a domain's `events/` folder (agent)  rule: subscriber.event_invalid  help: https://jadpo.dev/docs/errors/subscriber.event_invalidcheck failed: 1 error, 1 file

Markdown for agents: /docs/errors/subscriber.event_invalid.md.Built from Jadpo main at a707efb.