How Ailu works
The Studio, area by area: what each screen does, who may do what, what is recorded and signed. And, soon, the API reference, generated with every release.
The Studio, area by area
- Home
What needs your attention
The cockpit for approvers and owners, the conversation for everyone else: gates to decide, runs in progress, blocked drifts.
- Work
Ask, create, act
Ask Ailu about your sources, produce a document, propose an action another member signs.
- Mesh
Your agents and how they connect
The map of local and remote agents, who delegates to whom, the cost and proof layers, the inspector.
- Knowledge
What your agents know
Collections, sources, the facts extracted and where they come from, the contradictions to settle.
- Governance
Decide and prove
Gates with one or two signatures, policies, guardrails, the signed chain of proof.
- Settings
Your organisation
Models and keys, usage and credits, members and teams, developer access.
Who may do what
- ownerEverything: settings, models and their keys, members and teams, cost. Saves agents, revokes a remote agent.
- approverDecides gates, starts and resumes runs, proposes actions from Work that another member signs, requests a remote agent's arrival.
- viewerReads runs, proof and the Mesh, asks questions in Work. Decides, starts and proposes nothing.
Within a team, everyone also holds a team role — lead, approver, member or viewer: a team's approver or lead decides whether a remote agent joins it.
Described by the API itself
It will be generated from the API's OpenAPI document every time the site is built, so that it never drifts from the release that is live. Every request authenticates with a token and the organisation it targets.
From your first agent to your first decided gate
- Sign in, join your organisation
- Add an agent — ready-made, custom or remote
- Start a run, follow it in Activity
- Decide a gate in Approvals, read the proof