Policies and activities
Lisa separates policy definition from session evidence so observed agent behavior never becomes an approved rule without owner confirmation.
Policy lifecycle
- Policies live in the
lisa.policiestable (id,scope,target_agent_name,name,criteria,approved). - Workspace vs. agent scope: Workspace rules apply across all agents in the deployment; an approved agent-scoped rule overrides an approved workspace rule of the same name.
- Approval requirement: New or updated policies start as unapproved (
approved: no). Only owner-approved policies (LISA_OWNER_USER_IDS) can drive evaluation verdicts.
Evaluation flow
- A telemetry producer pushes an OTLP JSON bundle to
POST /internal/v1/session-traces. - Lisa validates
sp.session.id(falling back togen_ai.conversation.id, then trace ID) andsp.agent.name(falling back toservice.name), writesotlp.json+manifest.json, and enqueues a PGMQ job. - The evaluation worker loads approved policies for the resolved agent, triages candidate session-policy pairs, runs LLM judgment on escalated items, and records the outcome.
Activities and Slack
- Each evaluation creates an activity entry for inspection in the Lisa UI.
- Optional
LISA_SLACK_*settings connect Lisa to Slack workspaces to post verified policy failures and handle monitor threads.