Use Memory and context files

Every time you start a chat in GitLaw, the Agent loads what it already knows about you - your company details, how you like contracts written, and notes on the counterparties you deal with. This collection of knowledge is called your Memory, and the individual notes it contains are called Context Files.

What GitLaw remembers

Memory is organised into distinct layers:

• Profile - your legal name, trading name, jurisdiction, industry, and registered address. Set during account setup and editable in Settings.
• General Playbook - cross-category drafting defaults: your preferred liability position, standard payment terms, governing law, and similar standing preferences.
• Specific Playbooks - preferences that apply to a particular contract type or situation, for example "for NDAs, always use a mutual structure."
• Contact notes - per-counterparty intelligence: negotiation history, red lines, fallback positions accepted, communication style. One note per contact, built up over time.
• File summaries - a plain-English summary of each contract: the key terms, the negotiation arc, what changed across versions.

The Agent loads whichever layers are relevant to the work in hand. If you open a chat about an NDA with Acme Ltd, it loads your Profile, your general and NDA-specific playbook, and your Acme contact note - not every note you have.

How Memory is updated

GitLaw builds your Memory from several sources:

• Chat - as you talk to the Agent, it picks up preferences, corrections, and decisions. If you say "actually we switched to Net 45" mid-chat, that can update the relevant entry.
• File upload - when you upload an existing contract, GitLaw extracts parties, dates, governing law, category, and status, then generates a file summary and (where relevant) a counterparty note.
• You, directly - you can read and edit any Context File yourself at any time.

Proposed updates that the Agent is less certain about are held in an Outstanding Memory Updates queue for you to review - accept, edit, or dismiss - before they are saved. High-confidence facts (for example, details confirmed by a company registry) are written silently but are always visible and reversible.

Viewing and editing your Context Files

Your Context Files are collected in the Knowledge area of the main menu, under Context Files. From there you can:

• Filter by scope (Profile, General Playbook, Specific Playbook, Contact, File)
• Click any entry to read the full note
• Edit the body inline and save your changes

Contact-specific notes are also accessible from a contact's detail view. File summaries appear on the file detail page alongside the extracted structured fields.

Where Memory shows up in chat

The Agent cites memory at the point it uses it. If it applies your standard liability cap, it will say so - "Using your preferred liability cap of £100k here" - rather than announcing a save during the conversation. This makes it easy to spot when a remembered preference is being applied, and to correct it if circumstances have changed.

Good habits

• Check your Profile is complete. A full profile - especially jurisdiction and industry - means the Agent's first draft is already closer to what you need. See Set up your GitLaw account.
• Upload your existing contracts. The more contracts GitLaw has seen, the more accurate your playbooks and counterparty notes become.
• Add contact notes for frequent counterparties. A few lines on a counterparty's red lines saves you re-explaining them every time. Find contacts under Knowledge → Contacts - see Manage your contacts.
• Review the Outstanding Memory Updates queue. When the Agent proposes a new note, a prompt appears on the Files Overview. Taking a moment to accept or correct keeps your Memory accurate.