TEDLad documentation

Create an account, verify your email, complete organization and workspace onboarding, then create an AI employee from the builder.

Every application request resolves the active organization and workspace from current database state. Role permissions and PostgreSQL row-level policies enforce the boundary.

Create a knowledge base, upload an approved file through a signed intent, scan and extract it in the worker, build an index, then assign it to an employee version.

Workflows and provider writes enter durable queues with idempotency, retry evidence, and fail-closed production gates. Only verified active connections are selectable.

Secrets and payloads use authenticated encryption, API keys are hash-only, public channels use bounded sessions and replay controls, and production capabilities require explicit launch acceptance.