Try for 30 days

Manual - Bridge

Bridge manual — working with the AI: what happens in the background, and eight workflows from day start to legal research.

Basics

1. AI chat and bridge — what is the difference?

IRONSTICK gives you two ways to work on your files with an AI. The AI chat is built into the program: you type in an IRONSTICK window, and IRONSTICK itself sends the request to an external AI service, using the API keys your firm has stored in the AI configuration. The bridge works the other way round: you type in the desktop AI app you already use, and that app calls the IRONSTICK tools live through a connector. In both cases the AI reaches your data only through IRONSTICK, through the same tools and behind the same gates.

The built-in AI chat

The bridge

Side by side

AI chat (built in)Bridge (desktop AI app)
Where you typeIn the IRONSTICK chat windowIn your desktop AI app
Who talks to the AI serviceIRONSTICK, with your own API keysYour desktop AI app, with your own account
Costs of the AIBilled per use by the AI service on your API keyCovered by the subscription you already hold for the desktop AI app
IRONSTICK licenceIncluded, no extra licenceBridge licence per user / workstation — one bridge per desktop AI app, or the bundle of all bridges
Data sent to the AIPseudonymised; dates and amounts unchangedReal data, processed under your account with the provider
Your consentBefore the first external request of a chat sessionBefore the first data access by any desktop AI in each program run
Working instructionsSent along with every requestThe AI must read them and confirm a rule word for word before any tool opens
Tools and gatesThe same tool set and the same gates, plus a search in the chat's own historyThe same tool set and the same gates; program control only with its switch
Length of a working sessionRecent conversation plus a short summary; up to eight tool rounds per requestThe conversation of the desktop AI app
PlatformsWindows and Android tabletWindows

Why the bridge suits extensive case work

2. One set of tools — inside the Client App

Every operation an AI can carry out lives in the IRONSTICK Client App on your computer — not in the AI, and not in the bridge program. The AI chat and every connected desktop AI call the very same tools. Each call is executed by the running app against your live database, and only the result goes back to the AI.

3. The gates — what happens in the background

Between the AI and your records sit gates built into the tool layer of the Client App. They are plain program logic — no AI checks another AI. When a gate refuses a call, nothing is written or delivered; the AI receives a message naming what is missing and the call that opens the gate. Most gates work the same for the AI chat and for every desktop AI; the last column shows where each one applies.

GateWhen it triggersWhat it doesApplies to
Consent before external AIThe first time in a chat session that a request has to go to an external AI serviceA dialog asks whether the external AI may be used. If you decline, nothing is sent, and the chat does not ask again in that session.AI chat
PseudonymisationEvery request of the AI chat to an external AI serviceNames, companies, case and court file numbers, identification numbers, IBANs, phone numbers, e-mail addresses and party addresses leave as placeholders and are translated back on your computer. Dates and amounts stay unchanged. If the placeholder list cannot be built completely, the request is not sent.AI chat
Data-access consentThe first tool call by any desktop AI after program startOne confirmation dialog appears for all desktop AIs. Approved: open for the rest of the program run. Declined: every call is refused for 10 minutes, then you are asked again.Bridge
Start-up lockEvery tool call while the six-digit security code has not been enteredThe call is answered with the notice that the application is locked; no data is returned.Bridge
Instruction lockEvery tool call of a desktop AIAll tools except reading the instructions, confirming them and asking for the system language stay closed until the AI has read the instructions and returned the rule against invented facts word for word. The confirmation lapses 60 minutes after it was given, after 2 hours without a call, at midnight, on every new connection and, where IRONSTICK can see the conversation record, when the desktop AI condenses its conversation; then the AI must read again and return a randomly chosen rule word for word. In the AI chat the instructions are sent along with every request instead.Bridge
Date gateTools that write dated content — chronicle, calendar, daily notes, daily log, memory, statute reports and othersThe call is refused unless the AI fetched the real current date and time within the last 30 minutes.Both
Read the case firstTools that read case content (chronicle, timeline, searches, full texts and more) and tools that write on a case (notes, chronicle entries, pleading check, export, hand-over to another AI)Tools that read the content of a case are refused until the AI has read that case's digest. A note or chronicle entry also needs the case profile, the jurisdiction and the newest chronicle entries. A pleading check, export or hand-over also needs the newest documents of the case read in full. The refusal lists what is still unread.Both
Write only from what was readMemory entries, changes to a snake, work on drafts, the pleading check and delivery on a caseA memory entry for a case is accepted only when the digest has been read and every document cited in it has been read completely in this session. Every search result in a scratch file carries the notice that search hits are not reading, with the documents behind the hits that are still unread. Once the AI has opened a document of the opposing party or of an authority in a case, nothing more is written on that case until that document has been read completely.Both
Nucleu firstWriting, checking and delivering a pleadingRefused until every current nucleu of the case — the case nucleu and the nucleu of each matter the case belongs to — has been read in its current version. The last round of the pleading check compares the document with the nucleu.Both
Snake gateIn the pleading check, just before the nucleu round, when the case or another case of its matters has a snakeThe AI must ask you whether to run the snake round and continues only after your answer — or at once, if you asked for it when you gave the order. If you say yes, every snake entry has to be settled as adopted, rejected or not relevant, with a reason.Both
Legal library firstA web search or web page request that concerns a statute (article or paragraph numbers, code names, law numbers, law portals)Refused until the AI has searched your legal library for that norm. If the library has it, the web stays closed for that norm and the AI cites from the library. Only when the library has no match is the web opened for that norm, for 15 minutes.Both
Report statute sources — opened, not snippetsA statute-related web search or an opened law-portal page that yields a statute source, and every report of a new statute sourceEvery further tool answer starts with the reminder to report the source, until it is reported (for up to 15 minutes). A report is accepted only for a page the AI has itself opened with the IRONSTICK page tool within the last 24 hours. Reported sources wait in one consent dialog: ticked sources are fetched, checked and stored in the library, unticked ones are declined.Both
Memory only with your approvalThe AI stores, changes or deletes a memory entryA dialog shows you the entry. It is stored, changed or deleted only when you allow it; declined entries are discarded. While the dialog is open, every other call of that session is refused. Apart from hand-over tasks between AIs and your own notes, the AI reads only the memory entries you have approved.Both
Proposals instead of writesThe AI wants to change master data, add a person or institution, add a relation, fill a person analysis, merge duplicates or delete a recordThe tool writes nothing into your records. It places a proposal in the Data Consistency Monitor, where you accept or reject it.Both
Secret documents left outEvery AI tool that reads documents, media, deadlines or a whole case, and the background services that use external AI (Data Consistency Monitor, situation report)Entries marked secret are filtered out of every AI tool and service and are not passed to the AI.Both
Prospects only from the court fileThe AI case assessment, started in the app or by a desktop AIThe estimate of the prospects of success is based only on the case profile and the documents of the case that went to or came from the court or authority addressed in the initiating document — from both sides, without annexes. Without an initiating document or a recognised court or authority, the prospects are marked as not estimable and the gauge stays empty.Both
Check before deliveryDelivery of a formal document such as a pleadingDelivery is refused without a fresh positive result of the deterministic pleading check for exactly this state of the file; every edit voids it. What leaves the system is a submission-ready template for you to review and sign.Both

Workflows

Workflow 1 — Starting the day

Starting the day answers three questions before you begin: what is due, what has come in, and where you left off. One step produces the start-of-session summary with the date, reminders, deadlines and appointments of the next three days and open tasks. After that the AI fetches the complete deadline list, today's appointments and what was captured today or yesterday. Use it every morning, and whenever you start a new conversation with a desktop AI.

Start, agenda and heatmap
Start, agenda and heatmap: the day's deadlines, appointments and new entries at a glance.

Step 0 — set the context

What you say — step by step

  1. Start the session.

    The AI reads and confirms its instructions, fixes today's date and loads the start-of-session summary: reminders, deadlines and appointments of the next three days, open tasks.
  2. What is due today and in the next three days?

    You get deadlines, court hearings and appointments in date order, each with its case.
  3. What has come in since yesterday?

    New e-mails and newly captured documents, each with the case it was assigned to.
  4. Read the new e-mail in case [case number] and tell me what it asks of me.

    The full text is read first; you get the content, the open points and a suggestion for the next step.
  5. Write today's phone call with [person] about [subject] into the daily log.

    The entry is added to today's daily log with date and time.

What happens in the background

Workflow 2 — General conversation rules

These rules apply to every conversation with the AI, in the built-in chat and through the bridge: how a session starts, which language the AI speaks, where its facts may come from, and how you check its sources. Each rule comes with the sentence you use to apply it: instructions read and confirmed, answers that name their sources, full texts read to the end before an answer. Read this before your first real work session; the same rules carry every other workflow.

Guided path: read first, then answer
A grounded conversation: the AI reads what it needs to read before it answers — and you check the sources yourself.

Step 0 — set the context

Start the session. Then read the digest and the case memory of case [case number] and tell me what is open.

The rules — and what you say to use them

  1. Start the session.

    Rule 1 — the AI reads and confirms its instructions before it touches any case data, and answers in your system language.
  2. Quote rule [number] of your instructions.

    Rule 2 — every rule can be shown word for word, so you can hold the AI to it.
  3. Which document says that? Give me the evidence number.

    Rule 3 — every statement carries its source; a click on the number opens the document.
  4. Read [#evidence number] in full before you answer.

    Rule 4 — titles and short descriptions are not facts; the answer rests on the full text.
  5. Separate what is proven from what is only suspected.

    Rule 5 — the AI marks assessments and suspicions as such and states only what the sources document.
  6. Read the whole document, not only the search hits.

    Rule 6 — long documents are read to the end; the AI reports when every line has been read.

What happens in the background

Workflow 3 — Case assessment

The case assessment is the AI's senior-analyst view of a case, saved in IRONSTICK and shown on the case's AI assessment tab. The prospects of success are estimated only from the court file: what went to, or came from, the court or authority addressed in the initiating document. The descriptive sections draw on the whole IRONSTICK file and on the client's neighbouring cases. Use it when a case has moved on, when the last assessment is old, or when you want a desktop AI to make a new assessment by the same criteria as the app.

AI case assessment with prospects of success
The case assessment reads the case file and shows the prospects of success with the state of the evidence, the main claim and further claims.

Step 0 — set the context

What you say — step by step

  1. Open case [case number] and give me the state of the last assessment.

    The AI loads the case and summarises the saved assessment, including its date.
  2. Make a new assessment of case [case number].

    The court file is assembled, the documents are read and the assessment is written in fixed stages; the result appears in the AI assessment tab.
  3. Why are the prospects of success not higher?

    You get the points in the court file that weigh against you, each with its evidence number.
  4. Which documents in my file would help but are not yet before the court?

    The AI compares your whole file with the court file and names what is still missing there.
  5. Take [#evidence number] into account and assess again.

    Your comment is passed on and the assessment is renewed with it.

What happens in the background

Workflow 4 — Creating a nucleu

A nucleu is the binding direction of a case: the core line of argument, the guiding facts and evidence, what must be said and what must never be said. It exists on two levels — once for a whole matter, applying to every case in it, and once for the single case — and every document the AI writes for the case is subordinate to it. The best moment to create it is right after a case assessment, while the whole case is still in the AI's working context. The AI drafts it, IRONSTICK shows you every change, and only your approval stores it as a new version.

Case tabs with nucleu (atom icon) and snake (snake icon)
The nucleu in the tab with the atom icon: the AI drafts and proposes, you accept; every accepted change becomes a new version that steers every later pleading.

Step 0 — set the context

What you say — step by step

  1. Create the nucleu for case [case number] from this assessment.

    The AI distils the direction from the case it has just read and opens its proposal in the Case nucleu tab, where you accept or reject it.
  2. Create a nucleu for matter [matter]: the core line that applies to every case in it.

    The AI drafts the matter nucleu and shows it in the matter window; once accepted, it applies to every case of the matter and appears read-only in each of them.
  3. How long is each nucleu of case [case number], and what could move to the matter nucleu?

    The AI reads the case nucleu and every matter nucleu of the case and measures each against the limit of 20,000 characters.
  4. Update the nucleu of case [case number]: we no longer argue [point].

    The AI explains in the chat what it wants to change and why, then proposes only the changed passages; you see them in red bold, and an accepted change becomes the next version.
  5. Read me the current nucleu of case [case number], with the nucleu of each matter.

    The AI loads the complete set in its current versions, each with its identifier, for example #KI00041 · v3.
  6. Does this draft contradict the nucleu?

    The AI compares the draft point by point with every nucleu that applies to the case and names each deviation; in a pleading, this comparison is the final round of the review chain.

What happens in the background

Workflow 5 — Building the snake

The snake is the internal working register of the opposing side's statements in a case that the evidence in the case file contradicts. Every entry pins the place of the statement — document, date, case and page — and lists every document that refutes it. You build it in two ways: by targeted research in one or several cases, or in documents you name; or in the middle of any conversation, the moment a contradiction between the opposing side and the case file shows up. IRONSTICK checks every line against your records, you approve each version, and in every later pleading the snake entries are offered as arguments against the opposing side.

Nucleu and snake on the way to the pleading
The snake records the opposing side's contradictions with the case file: every line checked against the records, your approval for every version.

Step 0 — set the context

The entry format. Entries are separated by one empty line. The first line is the place of the statement; then the description; then every connected document on its own line, starting with an arrow:

#0004417 · 12.10.2026 · CaseID 19 · p. 2 top
Statement of defence on appeal, Opponent B: the courts have already decided ownership of the installations with final effect. Against this, the case file: both judgments expressly leave ownership to the main proceedings, and Opponent B said the same at the earlier hearing.
→ #0003304 · 18.07.2026 · CaseID 19 · p. 5 middle
→ #0000586 · 25.04.2026 · CaseID 8 · p. 9 top
→ #0001127 · 24.06.2026 · CaseID 8 · p. 15 bottom

Each reference line reads: evidence number with seven digits · the document date as IRONSTICK records it (DD.MM.YYYY) · the CaseID of that document · the page and the position on it (top, middle or bottom, in any of the system languages), or a dash for evidence without pages. When a contradiction is spread over several documents, every one of them gets its own reference line: the statement, the counter-statement and every piece of evidence in between. You can also type or correct entries yourself in the tab and press Save; every save is a new version.

What you say — step by step

  1. Build the snake of case [case number] from the complete file.

    The AI reads the case and every document that refutes the opposing side, then proposes the snake in the Case snake tab, with every line checked against your records.
  2. Search documents [evidence numbers] for statements of the opposing side that the case file contradicts, and add them to the snake of case [case number].

    The AI reads exactly these documents in full and enters only the statements that your records refute, each with its refuting documents.
  3. Build the snakes of all cases in matter [matter]. Cast the net wide.

    The AI works case by case, one snake per case; the matter window then shows all of them in the order of the case list.
  4. Is this contradiction already in the snake of case [case number]?

    The AI reads the current snake and tells you whether the point is already registered, and in which entry.
  5. Add this contradiction of the opposing side to the snake if it is not there yet.

    The AI reads the current snake, extends the existing entry or writes a new one with every refuting document as its own line, and shows you the change to accept.
  6. Which snakes do we have for client [client]?

    The AI lists every snake of the client's cases with its identifier, version and number of entries.

What happens in the background

Workflow 6 — Writing a pleading

This workflow takes you from a request in plain words to a submission-ready template in the word processor: a pleading, a request to a court or authority, or a letter. The AI reads the case before it writes, builds the document in its encrypted scratch store, has every fact, quote, norm and party checked against your records, works through a fixed review chain, and asks you at each decision point. Use it whenever something is to leave your office in writing. What leaves IRONSTICK is always a template for you to review, sign and send yourself.

Guided path with checks up to the finished pleading
From your order to the template in the word processor: the AI reads, drafts and verifies, guided by checks up to the tick mark; you decide at every step.

Step 0 — set the context

Draft the reply to the statement of defence #0004127 in case [case number], base it on #0003310 and #0003318, short and factual, addressed like the appeal of 12 May, with snake gate.

What you say — step by step

  1. Write a reply to [#evidence number] in case [case number]. Goal: [goal].

    The AI reads the case, the nucleu of the matter and of the case, and the document you answer, then drafts in its scratch store.
  2. Use [#evidence numbers] as evidence. Tone: [factual / firm].

    Your instructions are taken into the draft; every cited document is read in full.
  3. No corrections — continue.

    The review chain runs: read again, compared with your earlier filings, attacked from the opposing side, snake round, nucleu check.
  4. Change point [number]: [your correction].

    The draft is corrected and checked again before it goes on.
  5. Deliver it.

    The document appears in the download window; take it into the word processor, sign it and send it yourself.

What happens in the background

Workflow 7 — OSINT: researching a person or company

Use this workflow when you want to know who a party is: an opponent, a witness, a company behind an address, the people around a firm. The AI runs a fixed research procedure through your own records and the open internet, opens and reads the sources, and enters what it can verify as proposals into the Data Consistency Monitor. Nothing becomes part of your records until you accept it there. The research needs no case: a party can be researched on its own.

Person and company research through the bridge
One party at a time: search, read, verify, propose — and you decide in the Data Consistency Monitor.

Step 0 — set the context

What you say — step by step

  1. Research [full name], [city], [country] — natural person.

    Your own records are checked first; then the sources on the internet are opened and read.
  2. Research the company [name], [city], [country].

    The same procedure for a company, including its tax number and registered office.
  3. Is there a connection between [person] and [person]?

    Existing relations are shown; new ones are searched for in your records and the sources.
  4. Show me the source for [finding].

    You get the link or the evidence number behind the finding.
  5. Enter the verified findings as proposals.

    The findings land in the Data Consistency Monitor; nothing is stored until you accept it there.

What happens in the background

Workflow 8 — Legal research: statutes from the library first

Use this workflow whenever a statute, a code article or a regulation matters: to answer a legal question, to check a citation or to ground a pleading. The AI reads norms from your own legal library, word for word, and goes to the internet only when the library has nothing on that norm. A statute found online is opened, read, cited with its URL and reported back, so that after your approval it enters the library. The library is what the pleading check holds every cited article against.

The statute library
Library first, web only on a miss, and every web source back into the library with your approval.

Step 0 — set the context

What you say — step by step

  1. What does art. [number] of [statute] say? Quote it.

    The article is read word for word from your legal library and quoted with its source.
  2. Is [question] regulated in [statute]? Give me the articles.

    The library is searched; you get the relevant articles with their exact wording.
  3. Check the norms cited in my draft against the library.

    Every cited article is compared with the full text in the library.
  4. [statute] is not in the library — look it up on the official portal.

    The web is opened only for a norm the library does not hold; the page is read, cited with its link and proposed for your library.

What happens in the background

Working with the AI — your assistant in the file

In principle, a chat with an AI that is connected to IRONSTICK through the bridge is an enormously powerful tool. Think of it as a paralegal or a fellow lawyer. Through the bridge, the AI can not only search documents, individual text passages or pieces of evidence — it can also view stored images, view and check PDF files on request, start new OCR scans and much more.

When you work with the AI, work with it as you would with a paralegal or a lawyer. Simply give clear instructions on exactly what you want. The AI makes the necessary queries in the background through the bridge, directly in IRONSTICK — that is, in your files.

As a rule: without your consent, the AI can do little more in IRONSTICK than read. Changes to master data, chronicle, calendar, memory, full texts and the legal library take effect only after you approve them: either you get a form or dialog in IRONSTICK for it, or the AI's change request appears in the Data Consistency Monitor. Without such a dialog, the AI writes only to its own work areas — the encrypted scratch store, the daily log at your request, and its own case assessment after the deterministic checks. Tags and messages in the office chat need your confirmation in the chat.

Full transparency: every desktop AI app shows its tool calls — you can see at any time which information the AI has retrieved from IRONSTICK.

Be strict in your questions and instructions, and tell the AI where and how to research. You do not need to name the search tool — the AI knows it itself — but tell it clearly to fetch the information from IRONSTICK: in client XY, in case XY, in evidence XY. You can simply name clients by their name — the AI resolves the client ID itself — or copy the client number (@C0000000) from IRONSTICK and give it to the AI. The same works, for example, with an evidence number (#0000000).
The AI covers what deterministic program logic cannot, or only with extreme effort — understanding and writing natural language. Everything else — access to your files, the selection of the court file, the checks against your records, the rule that your records change only with your approval — is done by IRONSTICK itself, deterministically. The AI never becomes the source of the facts; IRONSTICK is. This is what sets the IRONSTICK approach so fundamentally apart from the conventional use of AI.

For you as the user, however, IRONSTICK presents itself in the familiar form — as the graphical interface or as a dialog.