Juvor.ai
Request access
HOW IT WORKS
Counsel sets the engagement. The system stays within it.
Juvor.ai runs inside a written engagement chain that starts with the client, runs through the attorney, and ends in the matter record every litigator would want to hold up in a hearing. Every request is classified before it is answered, and every answer traces back to the counsel who approved it.
THE ENGAGEMENT CHAIN
Three parties. One written retention.
01
The client engages the attorney or firm
Your client engages the attorney or law firm for legal services in the usual way, through the firm’s standard engagement letter. That letter defines the client, the matters, and the attorney relationship that Juvor.ai will support.
02
The attorney or firm retains Juvor.ai under a Kovel style letter
The firm then retains Juvor.ai, Inc. in writing as its technical agent. The retention uses a Kovel letter, associated with the doctrine in United States v. Kovel, which attorneys have long used to bring accountants, translators, and other specialists inside the attorney client relationship. Juvor.ai reports to counsel.
03
In-house or Outside counsel co supervises the deployment
In-house or outside counsel sets the scope inside the client organization, approves the playbook answers employees may receive, reviews escalations, and confirms which matters, jurisdictions, and users the service will cover.
The engagement chain is designed to preserve the elements a privilege or work product claim may depend on. Whether privilege applies to any specific communication is a legal determination made by a court on the facts of that communication.
THE REQUEST LIFECYCLE
Every prompt is classified before it becomes an answer.
01
Intake
The employee submits a question through the counsel controlled interface. The interface captures the participant, the requested purpose, the matter tag when one applies, and the timestamp.
02 Classification
The classification skill labels the request as routine legal, novel or sensitive, mixed purpose, personal interest, or outside scope. The classification is written to the matter record before any model is called.
03 Routing
Policy scoped orchestration selects the approved model for that classification, jurisdiction, and confidentiality level. Requests that require a confidential compute environment are sent to that environment. Requests outside approved scope are refused.
04 Response
Routine legal questions receive attorney approved guidance. Business decisions are refused. Novel or sensitive questions are held and escalated. Mixed purpose questions receive the legal component only, with the business component returned to the employee’s manager.
05 Record
The interaction is logged with the participants, purpose, classification, supervising attorney, engagement document reference, processing attestation identifiers, and hold status. The record is scoped to the matter.
06 Review
The supervising attorney sees the escalation queue and the daily digest of routine answers delivered under the playbook. Counsel may adjust the playbook, expand the scope, or narrow it at any time.
REFUSAL DISCIPLINE
The system says no in three ways.
Refusal is how the service maintains the boundary between legal analysis and business decision making. The refusal itself is written to the matter record.
PERSONAL INTEREST QUESTIONS
Requests about personal legal matters, personal finances, or personal disputes are refused with a note that the service is limited to the client’s business matters.
BUSINESS DECISION QUESTIONS
Requests to decide personnel, pricing, strategy, termination, or settlement are refused. The system may identify the legal risk factors inside a mixed request. The business decision returns to management and counsel.
OUTSIDE SCOPE QUESTIONS
Requests outside the approved matters, jurisdictions, or subject areas are refused, and the participant is directed to raise the question through internal legal channels.
THE MATTER RECORD
The record your litigator would want to hold up.
Juvor.ai keeps a matter scoped record that is designed to support the elements a privilege or work product claim may depend on. When the features are enabled for the engagement, each record includes the following fields.
Timestamp —> When the request was submitted and when the response was delivered.
Participants —> The requesting employee, the supervising attorney, and any other user who reviewed the interaction.
Relationship class —> Whether the participant was acting inside the attorney client relationship for that request.
Purpose classification —> The label the classification skill assigned to the request.
Engagement document reference —> The Kovel engagement letter identifier and the client engagement letter identifier.
Processing attestation identifiers —> For confidential compute inference, the cryptographic attestation captured for that inference call.
Retention or hold status —> The retention rule that applies to the record and whether the record is on legal hold.
The exact fields available depend on the deployment. Counsel of record confirms which fields are enabled for each engagement.
Have an engagement chain for your situation.
A deployment begins with a scoping call between your law firm and ours. Bring the recurring legal questions your business teams already ask. We will map the Kovel engagement, the classification playbook, and the matter record structure.
Request a scoping call