Fareeha Saif.

Live demo 1 · Legal intake

Legal Intake Agent

A client writes in about a car that keeps breaking down. The agent works out the language, masks anything sensitive, pulls out the facts a lemon law case needs, checks which documents are in hand and decides: reply on its own, honour an opt-out, or hand the case to a person. Nothing goes out until a release check passes, and an automatic reply still waits for a person to approve it.

detect languageguardrailsextract factsdocument checklistroutereplyrelease check

Client message

English or Spanish. Up to 4,000 characters.

Try a sample

What the agent decided

Run the agent or pick a sample to see the extracted facts, the checklist, the guardrails that fired and the reply.

Evaluation

Run the test suite against the live engine

The same checks run before every release. Guardrail cases are part of the suite, so a safety rule that breaks fails the build.

Part two · Contracts

Clause finder: what a reviewer reads first

The same discipline on a contract. Paste an agreement and it finds the clauses that matter, checks each one against a playbook you can change, and builds a review queue with the riskiest line on top. Every flag quotes its own section. A question gets an answer only when the document holds one, and a planted instruction inside the text is flagged, never followed.

Contract and playbook

Playbook

Contracts here are invented. Not legal advice.

Try a sample

Review queue

Review the contract or pick a sample to see who reads it next, the flagged clauses with their quotes and the answer to your question.

Evaluation

Run the clause finder checks

Fifteen checks on four invented contracts: the right section quoted, a stricter or looser playbook, a clause that is not there, a planted instruction and a request for advice.

Real vs simulated

Real
The pipeline and its rules: language detection, data masking, prompt-injection refusal, opt-out handling, the document checklist and the hand-off rules mirror the production agent I run.
Simulated
The language model step and the send. A rules engine fills the model step so the demo is instant, free and gives the same answer twice. Every message and vehicle is invented. The clause finder uses patterns and a playbook, not a model, on four invented contracts.
Privacy
Nothing you type is stored. The engine runs on the server, so the logic is not shipped to your browser.