Capability Ideator

1. 01

   You open it, or the assistant does

   Opening ?app=capability-ideator loads its 1 screen into the shared cockpit. 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

   capability-ideator is accountable for the work. 3 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

   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. capability-ideator advertises what it is accountable for, and the assistant matches against that.
• Asks that land here: anything about manifest reading, anything about capability composition, anything about proposal generation.
• 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.

All 12 engineering apps →