FE pipeline: Write an agenda for your oracles

Web app as of 2026-11-02

API layer: API pipeline: Write an agenda for your oracles

Goal: write an agenda — the instructions and persona your oracles and campaigns run on — in the web app or the Telegram Mini App.

Steps

1. Write the instructions as articles first: FE pipeline: Write articles and posts
2. Open Cabinet → My Agendas → New.
3. Fill the form:
   • Title and Content (what the agenda is for).
   • Kind: Firmware or Swappable (what each one is: Cabi.Chat Ignite — Agendas). Kind is fixed after creation.
   • Firmware only: Swappable agenda — the default task; "None (firmware only)" leaves it empty.
   • Instructions (articles), API endpoints, Secrets: pick your cards. Tools: FE pipeline: Give your oracle tools
   • Outreach prequalification: the cards used when your campaign picks whom to write to first; only these are used for that choice, on the agenda's model. A new agenda starts with the Cabi.Chat default; empty uses it too.
   • Project, Visibility as for any card.
4. Tap Create.
5. Open the agenda again and set LLM model (a model id) and Reasoning (off / low / medium / high), then Save.
6. Assign the agenda in the Agenda field of an oracle or a campaign.

What you see

• Next to Instructions, API endpoints, Secrets and Outreach prequalification the form shows how many cards each list holds.
• Routes: the agenda's routes add instructions only in conversations marked with the rubrics you name (API: API pipeline: Write an agenda for your oracles, step 10). Only the agenda's owner changes them; the agenda's Content is plain text and holds no routes.
  • On the agenda's Canvas: draw an arrow from the agenda to a card and pick Route, set the Route condition (rubric chips joined with + all of, + or, + not) and Save route. A route needs at least one rubric: cards that always load belong in the agenda's Core. Each route arrow carries a chip per branch; tap it for Branches of this route: Edit, Remove from this branch, or take the card out of every branch. Undo and Redo ask first, since live oracles read the routes. Changes show up live for everyone who has the agenda open; when the agenda changed meanwhile, the scene re-reads it and asks you to try again.
  • In the agenda's form, tab Routes: one rule per line, «- condition → blocks», each with its full condition (older text nested under a header line is turned into such rules); Save routes. Lines that do not pass are listed under «## Routes: fix these lines», each with how to fix it.
  • On the scene and on boards, the agenda's instructions show as Core. Its outreach prequalification cards show in a column of their own. Your own notes, shapes and arrows around the routes are saved with the agenda (editing needs write on the agenda); Expand opens the scene larger, Ladder switches to the read-only Instruction tree.
• The agenda lists the cards attached in each slot.
• A card you may not use in a slot is refused on save with the reason (for example someone else's private card).
• Only you and those you share an agenda with for running (an access link with execute: FE pipeline: Share cards through access links) can run it; the agenda's own permissions let no one else run it.
• What your agenda holds (cards shared with it, live or ended): through the API: API pipeline: Write an agenda for your oracles