PALETTEInteractive research demo

Personalized safety alignment

One model.
Different boundaries.

Select an authorized role. Add the right adapters. See which responses change—and which stay the same.

LLaMA2-7B-Chat Curated examples

01  /  Build your configuration

Select a role. Watch the model change.
Model assembly
Schematic preview · drag to rotate

General User

Universal safety. No domain adapters.

Role authorization is assumed. Adapter loading is visualized, not performed in your browser.

02  /  Compare behavior

See the difference.

The same prompt. With and without your adapters.

Pre-generated outputs · not live inference
Selected instruction

Base model

LLaMA2-7B-Chat · No adapter

ORIGINAL

With PALETTE

No adapter loaded

CONFIGURED

Keep the prompt. Change the profile.

Switch roles or toggle an authorized adapter above to explore the boundary.

How it works

One base model. Domain-specific adapters.

The demo illustrates the workflow of our approach in a practical application. Users can select different authorized roles, and the system automatically loads the corresponding adapters to relax refusal behavior for the associated target domains while preserving safety constraints elsewhere.

  1. Select a role.
    The profile determines which domain adapters are available.
  2. Add authorized adapters.
    Turn individual modules on or off. The Bioterrorism Analyst profile allows both Crime and Biosecurity adapters.
  3. Compare the same instruction.
    Change roles or toggle adapters without losing your query. Switch between side-by-side and single-response views.

What you are seeing

We use prompts from the dataset in our paper as example queries. Please note that the responses to these example queries are pre-generated locally with the corresponding model, rather than produced through live generation.

Demonstration assumptions

Role selection illustrates an already-authorized user; it does not verify identity. In practice, adapter loading is handled by the system and is invisible to the user. The assembly is a schematic—not a depiction of individual network layers or an actual loading process.

Response text and compliance labels follow the original demo. The interface does not assess their factual accuracy or endorse their content. Sensitive examples may include unsafe outputs. No model runs in this page, and no prompt is sent to a server.

Browse examples