Legal Agent
The Legal Agent answers the "do I need to…" questions — an NDA, a signature, a retention period — from your organisation's own legal and compliance policies, with citations.
At a glance
| Handle | @legal-agent |
|---|---|
| Availability | Seeded in every organisation |
| Tags | knowledge, legal |
| Model tier | default |
| Autonomy | supervised (the platform default — the definition declares none) |
| Tools | search_knowledge, calculate, current_time |
| Knowledge | legal-policies — seeded with 4 sample documents |
| Covers | contract review and signing authority, NDAs, data protection and privacy obligations, intellectual property ownership, and records retention |
| Max turns | 12 |
| Schedulable | Yes |
How it works
It is an ordinary markdown agent whose knowledge: frontmatter
names one org-ring collection. That single
line is what switches on search_knowledge and the
citation contract: every claim it makes carries the chunk it
came from, and a question the corpus does not answer gets an explicit "not in
the knowledge base" rather than a plausible invention.
-
Search before answering
The question is embedded and matched against the collection. Retrieval respects source permissions: a document you are not allowed to see is not retrievable for you, even though the agent is shared. -
Answer from what it found, with citations
Citations render as document pills in chat — the file name, with the collection and part on hover — so a reader can open the source. Where you cannot see the document, the pill says "source" rather than leaking a name. -
Say so on a miss
Out-of-scope questions get its own boundary line and a pointer to the sibling expert who owns that subject, rather than an answer it cannot support.
The sample corpus is a placeholder, and says so
Every organisation is seeded with a small sample policy corpus so the agent
works on day one — and each file is headed sample policy. Replace it
with your real documents: upload them to the same collection, and the agent
needs no change at all. Re-seeding is superseding, not additive, so a stale
sample cannot linger behind your own version.
It explains policy; it never acts
The tools are search, arithmetic and the clock. It cannot approve an expense,
book anything or change a record.
It is a normal agent, so you can change it
Every built-in is an ordinary org-ring registry agent with a versioned
Agent.md. Edit it, publish a new version,
roll back — the platform only re-publishes its own definition when you have
not taken it over. See Build & promote.