Living Memory

Living Memory is your project’s standing context for the AI: the brief, instructions, quality rules, reference documents, and validated examples it reads before drafting anything. The app introduces it as “Your team’s encoded voice and standards — the project context the AI draws on for every new draft. It grows with each validation, correction, and instruction your team adds.”

Open it from the Living Memory row in the editor sidebar. The page lists five parts, each with its state at a glance.

One page for everything the AI knows about your project. Each row opens its own section.

Everyone on the project can read Living Memory. Editing it needs Maintainer access or above, except the Knowledge base, which Project leads can also manage.

Brief

The brief records who the translation is for, what it must accomplish, and the standards it follows. Its status shows on the card: Not started, Draft, or Complete.

Create brief opens a step-by-step builder, one question per step: Purpose / skopos, Audience / addressees, Intended use & medium, Motive & sponsor, Source & base texts, Target language & variety, Register & naturalness, Level of literalness, Key terms & theological tradition, Constraints & sensitivities, Quality bar, and a closing “Anything else the AI should know?”. Skip any step that does not apply; the builder reopens at the first unanswered question. Help me write this drafts a step for you from what you have already answered, and the builder can also pre-fill every field from an existing document you paste in.

One question per step. Save draft keeps your answers; Help me write this drafts a step from the others.

Finish with Save & generate summary: the full brief is condensed into a short summary that is injected into every AI draft. After edits, the page marks the summary Summary out of date and offers Regenerate summary.

The generated summary is what the AI actually reads on every draft: short, imperative, and current.

Generation needs an AI provider

Generating the summary uses the project’s AI provider. If nothing happens when you ask for one, open Project Settings → AI & completion and save a provider first; the default Frontier option works without an API key. This applies per browser, so a new device may need the same one-time save.

Instructions

Instructions are short, durable directions included in every draft prompt. The app’s guidance: “Tell the AI what this project is about — audience, tone, formality, special handling. These appear in every draft prompt.” Use Add to write one; each entry records who added it and when.

Each entry rides along on every draft. The System prompt row below swaps the default prompt for your own.

Below the entries, the System prompt row shows whether the project runs on the Default prediction prompt or a Custom one. A custom prompt replaces the default wholesale, and Reset to default brings it back.

Translation quality

This section holds the standards and rules that guard the translation. It is where Rules moved: the old project Rules page now lands here.

Standards are written quality decisions, in the same spirit as Instructions but aimed at checking drafts rather than steering them: “Project-wide quality rules the AI checks its drafts against. Capture decisions your team keeps revisiting.”

Standards say what good looks like; the rules below enforce it cell by cell.

Rules run automatically against cells. Three kinds live here:

• Built-in checks: the ten shipped checks (empty translation, identical to source, placeholder integrity, and so on), each with a severity menu and an on/off toggle. Built-in checks covers what each one looks for.
• Project rules you write with Add Rule: name, description, a pattern (regular expression or literal text), whether it is forbidden, required, or must match, which side it applies to, and its severity. A rule can carry an optional autofix. Try to fix all sweeps a rule’s violations; Promote to org offers a good rule to every project in the organization.
• Org rules, inherited from the organization and listed alongside.

A project rule with its controls: fix violations in bulk, or promote the rule to the whole organization.

Import from doc extracts rules from a pasted style guide, and Suggest from edits proposes rules from patterns in your team’s corrections. Both produce drafts for you to review, not finished rules.

Knowledge base

Reference documents the AI can quote from while drafting: style guides, cultural background, commentary. Upload Markdown, TXT, DOCX, or PDF files up to 25 MB each. A fresh upload shows Indexing… and switches to Indexed when it is searchable; a failed document offers Try indexing again.

An uploaded style guide being indexed. The switch above controls whether drafting quotes from these documents.

The Use knowledge base in drafting switch controls whether drafts pull relevant passages from these documents; the hub card reads On or Off to match. Documents shared from the organization’s own knowledge base appear here too, read-only.

Examples

Examples are your project’s human-validated source and target pairs, shown newest first per file. The AI uses them as in-context examples, so every validation your team performs quietly teaches it what approved work looks like. There is nothing to configure here: the list grows through validation, and only validated pairs ever enter it.

Validated pairs, newest first. Approving good work is also how you train the AI's ear.

Living Memory and the agent’s memory

These are neighbours, not the same thing. Living Memory is context your team writes and curates. The AI agent also keeps its own notes about the project, proposed during chat sessions and approved by a person in the workbench’s Project knowledge tab. Agent memory & the project brief covers that side.