Event rules

Event rules

An event rule is a standing instruction for an agent (module eventrules): when something happens and plain conditions hold, the AI reads it and the rule does exactly one thing at a service. There is no review queue, and the rule has no other tools.

Today a rule is started by new mentions of an X account. The ready-made Dunno ideas rule turns #DunnoIdea mentions into ideas on Dunno's site, and adds the person as a supporter when the idea is already there.

In the sidebar under Automation → Event rules.

What you see

The page has two tabs: Log and Settings.

Log

Every post a rule read, newest first: the Rule, who posted, what They said, the Outcome and Why / reply. An outcome is Saved as new ideas, Merged into an idea already there, Skipped (saying which check it failed), Waiting or failed. Show filters the list. What a post says is a stranger's words, shown as text.

Settings

Each rule with its State, Next read, X reads left today and AI calls left today, and its settings in five parts:

  • Trigger: a new mention of an X account. Each post is handled once.
  • Conditions: plain checks before any AI is used: Hashtags, Who may submit (Every post, Followers of the account or Verified accounts), Account at least (days old), At least (followers), a Blocklist, and Posts per person a day. A post that fails one is logged as skipped.
  • AI step: the AI pulls out the idea's title, summary and category (What counts as an idea) and decides whether it repeats one already at the service (Merge at confidence). It has no tools, and is given the post as a stranger's words.
  • Action: straight to the service: a new idea is created; a repeat adds the person as a supporter, with a link to their post. Service account, Search tool, Create tool and Supporter tool say how.
  • Reply (optional): Reply on X answers the post in your Style guide, within Replies per person a day and Reply at most (characters). It can only answer the post, with text, never a link, another account or money talk.

Guardrails set Read every (minutes) (each read is one paid call to X), X reads a day and AI calls a day. Past a daily limit, nothing more happens until the next UTC day. Your AI budget under Costs also applies.

The rule acts as whoever saved it last, with the Agent chosen on it: only that agent's grants of the accounts are used.

What you can do

Turn #DunnoIdea mentions into Dunno ideas

  1. Make sure the Dunno page has a site with the slug dunno, and give the agent that will run the rule the Dunno module and the Dunno X account (under Connectors).
  2. Press New rule and choose the Dunno ideas preset.
  3. Choose the Agent and the X account, check the conditions and guardrails, and press Save. A new rule is off.
  4. Tick On and press Save again.

Read now

Press Check now to read new mentions at once, whatever the interval. It uses one paid X read from today's allowance.

Who can do what

PermissionLabelLets you
eventrules:readView event rules and what each did with every post it readSee rules and the log.
eventrules:manageSet up event rulesMake and change rules: their trigger, conditions, service, replies and budgets, and switch them on.

What happens on its own

JobWhenWhat it does
sweepEvery 5 minutesReads new mentions for every rule that is on and due, and handles them, each rule acting as its owner. A mention X pushes to Max is handled straight away.

Needs

Nothing switched on, but the Dunno ideas preset needs the Dunno module, an X account under Connectors and an AI connection.

What agents can do

Read-only tools run at once; the rest ask first under the default rules. Tools marked outside change what happens on X or at the service without a person.

  • Read-only: eventrules.rules, eventrules.presets, eventrules.log
  • Change: eventrules.create (made off), eventrules.update (outside), eventrules.enable (outside), eventrules.check (outside; one paid X read), eventrules.retry (outside; handles a failed post again on the next run), eventrules.remove (deletes the rule and its log)

Over MCP the tools are named eventrules__rules and so on.