Papers › Controlling Conditional Language Models without Catastrophic Forgetting

Controlling Conditional Language Models without Catastrophic Forgetting

1 Dec 2021arXiv:2112.00791archive 2025-07-28

Tomasz Korbak, Hady Elsahar, German Kruszewski, Marc Dymetman

Machine learning is shifting towards general-purpose pretrained generative models, trained in a self-supervised manner on large amounts of data, which can then be applied to solve a large number of tasks. However, due to their generic training methodology, these models often fail to meet some of the downstream requirements (e.g., hallucinations in abstractive summarization or style violations in code generation). This raises the important question of how to adapt pre-trained generative models to meet all requirements without destroying their general capabilities ("catastrophic forgetting"). Recent work has proposed to solve this problem by representing task-specific requirements through energy-based models (EBMs) and approximating these EBMs using distributional policy gradients (DPG). Despite its effectiveness, this approach is however limited to unconditional distributions. In this paper, we extend DPG to conditional tasks by proposing Conditional DPG (CDPG). We evaluate CDPG on four different control objectives across three tasks (translation, summarization and code generation) and two pretrained models (T5 and GPT-Neo). Our results show that fine-tuning using CDPG robustly moves these pretrained models closer towards meeting control objectives and -- in contrast with baseline approaches -- does not result in catastrophic forgetting.

PaperPDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

Syntology holds a reference implementation of Conditional DPG (CDPG), generated from the paper text (not the authors' code), at level 3 on Syntology's ladder: V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)”; V3 “paper-derived property tests pass on both of those same two generations.” (quoted from Syntology's server card). No rung compares this code against the authors' implementation. For agents: get_reference_implementation(name='Conditional DPG (CDPG)') (how to connect); the free check have('2112.00791') needs no token.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 8 code samples harvested from 2 repositories linked to this paper: 7 ran (of which 1 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 2 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 4 samples from 1 repository, 3 ran (1 with no instrument failure; 2 where Syntology's instrument failed); community (archive-listed): 4 samples from 1 repository, 4 ran (4 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

naver/gdc officialmentioned in papermentioned on GitHubpytorchSyntology: 4 samples, 3 ran (2 instrument-failed) · 1 unverified report
google/t5patches mentioned on GitHubjaxApache-2.0Syntology: 4 samples, 4 ran (0 instrument-failed) · 0 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

8 samples harvested: 7 ran (of which 1 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 2 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · our draft was wrong
5ran
1unverified

Licence: 4 of the 8 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

naver/gdc official repository 4 samples, 3 ran (2 instrument-failed) · 1 unverified
BaseTrainer in 16 papers cdpg/cdpg/pointwise_gdc.py ran licence not identified · pointer only · 4e11394481ba47b3 · report fixture: returned BaseTrainer · level recorded 2026-09-22
entropy_from_logits in 13 papers cdpg/cdpg/pointwise_gdc.py ran · our draft was wrong fingerprinted licence not identified · pointer only · 499346faba26ea21 · report fixture: signature logits:Tensor/2/float · returned Tensor · level recorded 2026-09-22
logprobs_from_logits cdpg/cdpg/pointwise_gdc.py ran · our draft was wrong licence not identified · pointer only · fdebc86ab591bd34 · report fixture: signature logits:Tensor/3/float, labels:Tensor/2/int, mask:Tensor/2/float · returned Tensor · level recorded 2026-09-22
PointwiseGDCTrainer cdpg/cdpg/pointwise_gdc.py unverified licence not identified · pointer only · da3e3fa9219ccd85 · report
google/t5patches community (archive-listed) 4 samples, 4 ran (0 instrument-failed) · 0 unverified
dot_product_attention in 15 papers t5patches/layers.py ran Apache-2.0 (permissive) · dac0288079ac279f · report fixture: signature query:ArrayImpl/4/float, key:ArrayImpl/4/float, value:ArrayImpl/4/float, bias:ArrayImpl/4/float, dropout_rng:ArrayImpl/1/int, dropout_rate:float/0/float, deterministic:bool/0/bool, dtype:callable/0/?, float32_logits:bool/0/bool · returned ArrayImpl · level recorded 2026-09-25
get_first_diff_mask t5patches/feature_converters_utils.py ran Apache-2.0 (permissive) · 84ee976a4b8362c9 · report fixture: signature seq1:EagerTensor/1/int, seq2:EagerTensor/1/int · returned EagerTensor · level recorded 2026-09-24
make_attention_mask in 6 papers t5patches/layers.py ran Apache-2.0 (permissive) · 1184cae8ca10c644 · report fixture: signature query_input:ArrayImpl/2/float, key_input:ArrayImpl/2/float, pairwise_fn:callable/0/?, extra_batch_dims:int/0/int, dtype:callable/0/? · returned ArrayImpl · level recorded 2026-09-25
make_causal_mask t5patches/layers.py ran Apache-2.0 (permissive) · 94c13ffc5f28dfba · report fixture: signature x:ArrayImpl/2/float, extra_batch_dims:int/0/int, dtype:callable/0/? · returned ArrayImpl · level recorded 2026-09-26

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. For a generated assembly, an independent peer is a second implementation generated separately from the same paper text; neither implementation read the authors' code. At level 2 the two agreed numerically on the fixture's inputs; level 3 is recorded when property tests derived from the paper also passed on both, and each level 3 card prints how many its report lists. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it. A generated assembly's label was set when its code was generated for the method, and no model judged it; its card prints it as "by construction" or "not judged by a model". Where an assembly's phrase has no constructed figure, a brick that ran is not among the harvested samples this build reads, and whether a brick's run only constructed an object is read from that brick's harvested sample, so the figure was not counted; it does not say there were none.

2 assemblies on this paper: 1 harvested, 1 generated.

generated Assembly for Conditional DPG (CDPG) (graph method: Conditional DPG (CDPG)), generated from the paper text, not the repository's code. 1 brick; individually on a fixture: 1 ran (1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. Ran end-to-end against an independent peer (level 3; 5 property tests passed on both).

label matches by construction: the code was generated for this method (not judged by a model)

  1. cdpg_gradient_weight entry · level 3 · ran · honoured contract · 150fd5dafd08a0511e718009d56e79c79be20da8995e294742299bec300fe606

harvested Assembly for Conditional DPG (CDPG) (graph method: Conditional DPG (CDPG)). 6 bricks; individually on a fixture: 4 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 3 where Syntology's instrument failed) · 2 unverified. The assembly has not been run end-to-end.

  1. PointwiseGDCTrainer entry · level 0 · unverified · da3e3fa9219ccd85
  2. BaseTrainer helper · level 1 · ran · 4e11394481ba47b3
  3. entropy_from_logits loss · level 1 · ran · our draft was wrong · 499346faba26ea21
  4. flatten_dict helper · level 0 · unverified · 8826b925c6d6132e
  5. logprobs_from_logits loss · level 1 · ran · our draft was wrong · fdebc86ab591bd34
  6. stack_dicts helper · level 1 · ran · our draft was wrong · c421e6f0c295b7fb

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2112.00791") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Abstractive Text SummarizationCode Generation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

AdafactorAttentionAttention DropoutBPEDPGDense ConnectionsDropoutGPT-NeoGated Linear UnitInverse Square Root ScheduleLayer NormalizationLinear LayerMulti-Head AttentionResidual ConnectionSentencePieceSoftmaxT5

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections