Tutorials

Five short, step-by-step walkthroughs covering how OrionLaw is actually used.

Contents

• Tutorial 1: review a contract in ten minutes
• Tutorial 2: from one sentence to a signable contract
• Tutorial 3: ask questions with the document in hand
• Tutorial 4: connect OrionLaw to your agent
• Tutorial 5: keep an eye on usage and call records

Tutorial 1: review a contract in ten minutes

You end up with: a clause-by-clause risk list and suggested edits you can accept.

1. Open Contract review in the workspace.
2. Upload the contract, or paste the text into the input.
3. State your side (buyer, seller, client, vendor…) and what worries you most — payment milestones, penalties, termination.
4. When parsing finishes, read the high risks first.
5. Work clause by clause: accept the edit, keep editing, or ask for another version.
6. Export the final text and send it on for signature or internal review.

Tip: one contract per run. Put two in and clause references get muddled, which makes the risk list much harder to use.

Tutorial 2: from one sentence to a signable contract

You end up with: a complete first draft with the usual elements in place, exportable to Word.

1. Open Contract drafting and describe the deal in one sentence — "we're hiring an agency to build a mini-program, we're the client".
2. Answer the follow-ups: contract type, parties, amount and payment method, term, and which side you want to favour.
3. Review the outline and add or remove sections — far cheaper now than after the text exists.
4. Generate the document and check the clauses that matter: scope, price, payment milestones, acceptance, liability for breach, termination.
5. Export to Word and fill in the blanks: party names, addresses, signing date.

Tip: decide what happens in the worst case before you write the termination and penalty clauses.

Tutorial 3: ask questions with the document in hand

You end up with: sourced answers you can push back on, plus a saved conversation.

1. Open Legal Q&A and upload the file you want to discuss (or skip it and just ask).
2. Make the first question complete: your role, the structure of the deal, what you are most afraid of.
3. Push on the basis: "which article of which law is that?", "if the other side refuses, what else can we do?"
4. To compare options, ask for the risks and costs of each side by side.
5. Save the conversation so the same question is easy to pick up later.

Tip: the cited statutes and cases can be checked yourself. When something does not match your facts, add the difference and ask again.

Tutorial 4: connect OrionLaw to your agent

You end up with: an agent that reviews contracts and drafts clauses inside your own chat window.

1. Sign in and open the AI access page.
2. Generate the setup prompt — the key is written into it.
3. Paste the prompt into an agent you trust (a client that supports skills).
4. Let the agent finish the setup and check it can see the available capabilities.
5. Go back to your everyday chat window and just ask.

Security note: the prompt contains the key in plain text — never forward it to a group chat or a public repo. Scope it per capability, give it an expiry, and if you suspect a leak rotate it (the old key dies after 24 hours) or revoke it (immediate).

Tutorial 5: keep an eye on usage and call records

You end up with: a clear picture of where quota goes and when to top up.

1. Check the plan, daily quota and weekly cap on the workspace dashboard.
2. Open call records and break usage down by capability: review, drafting, Q&A.
3. If one capability looks unusually heavy, check whether the same document was submitted twice.
4. When quota runs low, buy a top-up pack (points) — no plan change needed.
5. For reimbursement or reconciliation, export the call records and charge details.

Tip: a long document split into a few runs is easier to account for than one giant submission.

Still stuck?

Try the Help Center, or email 867663065@qq.com.