Feeds

The feeds-indexing engine + cron, the feeds-curator inline node, the slack connector, and the /feeds framework page stay framework-resident; this package is the surface over them.

• Slack Feed. Read the signed-in user's indexed Slack feed — recent messages across their channels and DMs, hottest channels, top voices, counts, and (if enabled) sentiment

1. 01

   You open it, or the assistant does

   Opening ?app=feeds loads its 1 screen into the shared cockpit, starting on feeds-dashboard. The ribbon, the ticket list and the assistant are already there — the app contributes views, not a second application to log into.

2. 02

   Or you just ask

   The assistant classifies what you asked for and hands it to the bot that owns that domain. You do not pick the app, and you do not learn a command — routing is by declared capability, not by keyword matching a menu.

3. 03

   A named bot picks it up

   feeds-curator is accountable for the work. 5 declared capabilities say what it is trusted to do; the tokens and dollars it spends are recorded against that identity, so the cost has a line item rather than disappearing into a monthly bill.

4. 04

   It reads your accounts without ever holding the keys

   The connector call happens in a fixed server operation outside the model. Only the normalized result reaches reasoning — the token stays encrypted and scoped to you.

5. 05

   Longer work becomes a ticket

   Scheduled and swarm-initiated work enters the queue as a feeds ticket. It is durable, it has an owner, you can watch it move through its phases, and if it fails it fails somewhere you can open and read.

6. 06

   The result lands where you can check it

   Back on the app's own screens, as state you own — not as a chat message you have to scroll back to find.

• Routing is by declared capability, not by keyword. feeds-curator advertises what it is accountable for, and the assistant matches against that.
• Asks that land here: anything about feed aggregation, anything about feed summarization, anything about hot area detection, anything about trend analysis, anything about sentiment triage.
• The specialist does the work, not the assistant. Cost, permissions and audit stay attached to the bot above — delegation does not launder accountability.
• It will tell you when it cannot. If a request needs your screen — an approval, a payment, a login — it says which app to open rather than guessing.

• Accounts to connect: slack. Your token is encrypted per user and consumed by a fixed server operation — the model never sees it.

All 11 productivity apps →