
Agentic Service Layer
The work is the combination: learn, train, moderate, and load-balance — while occupation experts keep up with the business. Alisha is only the human interface.
How it works
One loop. Experts study specific fields from your data. The control plane checks, caps, and spreads the load. Alisha talks to people.
Work, documents, and queued study land in tenant graphs. Occupation experts keep studying their specialty from that data. Alisha speaks from what is known.

Human interface
A.L.I.S.H.A. — AI Layer Interactive Service Human Agent. One voice per company. The specialists stay behind her.
Alisha is the human interface — the only voice staff hear. Occupation experts study specific fields behind her. Research APIs never talk to people.

Occupation experts
Expert agents keep learning very specific occupations from your data, validate what they find, and deepen without writing new code. They never speak to staff.
Specialties are fields of study (knowledge graphs, tax policy, support operations), not a leftover chat topic. An expert is minted when that field shows up often enough, or when you ask them to study it.
Control plane
Spend, safety, and rules — without handing the company to a vendor console.
See which team, user, and agent spent what — while work is still in flight.

Developers
Headless control plane. Point existing agent apps, MCP clients, and LLM SDKs at ASL — download the client and keep the UI you have.
Python and TypeScript clients — REST, MCP, and wrap helpers. Download and drop into the app you already have.
from asl_sdk import AslClient, AslMiddleware
client = AslClient("http://localhost:8080")
client.login("user", "user")
print(client.query("What changed?")["answer"]["text"])