Your agents,
as a hierarchy of light.
Layan orchestrates. Leads own a domain. Workers do the repetitive work. Click any wisp to talk to it, read its contract, or change who it reports to. Build a new one under any parent.
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 a contract.
An agent is not a prompt. It is a name, an objective, a trigger, context, memory, tools, permissions, a budget, constraints, approval rules, an output, an evaluation and an audit trail. The panel shows all of it. Nothing runs outside it.
- Permissions are explicit. Read, create, update, execute are ordinary. Pay, delete, export, deploy and publish are gated and 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 separate scopes. A wisp reads only what its scope allows.
- Objective
- Qualify inbound agency requests and prepare replies for a person to send.
- Trigger
- 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
- Constraints
- No outbound message without approval. No pricing statements. English and Arabic only.
- Approval
- Every reply. Every CRM write to an existing record.
- Output
- Draft reply, draft CRM record, qualification score with reasons.
- Evaluation
- Weekly sample of 20 drafts scored by a person. Below 90% agreement pauses the wisp.
- Audit
- Who, what, when, tool, input class, result, approver. Secrets never logged.
Wisps hand work to each other. People sit at the gates.
A handoff is a typed message through the tool gateway, not a shared brain. Every arrow below is logged, and the amber gate is where a person decides.