Your agents,
as a hierarchy of light.
Layan coordinates. Leads own an area. Workers do the repetitive work. Click any wisp to talk to it, read its rules, or change who it reports to. Build a new one under any agent.
Hover a wisp to name it. Click to open it.
The light is the status.
You should never have to read a log to know what an agent is doing. A wisp breathes when idle, tightens when thinking, throws sparks when acting, and wears an amber ring when it is waiting for you.
Every wisp has written rules.
An agent is more than an instruction. It has a name, a goal, what starts it, context, memory, tools, permissions, a budget, limits, approval rules, what it delivers, how it is reviewed and a log of what it did. The panel shows all of it. Nothing runs outside it.
- Permissions are explicit. Read, create, update and run are ordinary. Pay, delete, export, go live and publish need your OK and are always shown in amber.
- Budgets are visible. Credits per run and per month. A wisp that runs out goes red. It does not keep spending.
- Memory has boundaries. Company, operational, customer, task, decision and research memory are kept apart. A wisp reads only the memory it is given.
- Objective
- Qualify inbound agency requests and prepare replies for a person to send.
- Starts when
- New message in the shared sales inbox.
- Context
- Company brain, qualification rules, agency licence registry.
- Memory
- companyoperationaltaskcustomer
- Tools
- inbox.readregistry.lookupcrm.draftreply.draft
- Permissions
- readcreatepublish
- Budget
- 1 credit per lead · 120 per month · 38 used
- Limits
- No outbound message without approval. No pricing statements. English and Arabic only.
- Approval
- Every reply. Every CRM write to an existing record.
- Delivers
- Draft reply, draft CRM record, qualification score with reasons.
- Review
- Weekly sample of 20 drafts scored by a person. Below 90% agreement pauses the wisp.
- Logged
- Who, what, when, which tool, what kind of input, the result and who approved. Passwords and keys are never logged.
Wisps hand work to each other. People approve the big steps.
A handoff is a set message passed through Layan's approved tools, not a shared brain. Every arrow below is logged, and the amber step is where a person decides.