Something happens. Your agendas get to work.
Provence listens for signals — a new release, a burst of comments, Monday at 9:00 — and runs your team’s skills straight from GitHub. Every lead, draft and post lands in one data warehouse, and nothing goes public until you approve.
Signals start the work. Agendas do it. The warehouse keeps it.
Three parts, one loop. Nothing runs on a timer you forgot about or a pipeline nobody can read — every run starts from a signal, writes only where it’s allowed, and leaves a record behind.
Signals
Built-in events, schedules, your accounts, GitHub and any webhook all land on one bus. Agendas listen by mentioning a signal in plain words.
Public Leads
Event BusAgendas
Each agenda is a skill folder in a GitHub repo, pinned to a commit and run on Toscana. You write when it runs, what it gets and which tables it may write.
Data Warehouse
Runs, leads, drafts, posts and signals are records you can search and filter by campaign — each one traced back to the run that wrote it.
Not a pipeline. Runs side by side.
Each card is one run of an agenda. Signals start them in any order, and none waits on another. When a run finds something worth doing, it writes a follow-up run — and you decide.
Started by signals. A release, a comment spike, Monday at 9:00.
Approve where it matters. Nothing runs or publishes on its own.
Redirect any agent mid-run. Just tell it what you want.
Four steps. Then it keeps listening.
Set up a campaign once. From there, signals start the work in the background, and only what needs you comes back.
Describe who it’s for
Write the audience in plain words. Pick where agents may look and which accounts they may publish to. That’s a campaign.
Attach skills from GitHub
Point an agenda at a skill folder in any repo you can read — your own, your team’s, or ours. Provence pins the commit, so a run always uses the version you saw.
Signals start runs on Toscana
When a signal your agenda mentions fires, Provence packs the skill and runs it on Toscana. Results go straight into the tables it may write, and the cost is charged in credits.
You approve. It publishes. The next signal fires.
Publishing waits for your yes. Comments and metrics come back as signals on the Event Bus, and any agenda listening for them picks up from there.
Agents do the work. You decide what goes out.
Approval where it matters, write access only to the tables each agenda needs, and spend you can see before it surprises you.
Approval only where it matters
Research runs freely. Anything that goes public — or spends real money — waits for a person.
Talk to any agent, mid-run
Redirect one agenda without touching the others.
Agendas write only where you say
Each agenda gets write access to the tables it needs. Everything else in the warehouse stays read-only to it.
Spend you can see
Usage alerts and an optional hard stop, so nothing runs past what you planned.
One data warehouse
Every run, lead, draft, post and signal is kept as a record you can search, filter and trace back to the run that wrote it.
Start small. Pay for what runs.
Every run is charged in credits for what it actually cost to run on Toscana. Plans include monthly credits; Unlimited is metered with no run cap.
- Included monthly usage
- Draft-only publishing
- Data Warehouse and metrics
- Larger included usage
- Publish to every connected account
- Members and shared library
- Everything in Team
- Metered agent and media usage
- Spend alerts and optional stop