Apex ThreatDemonstrated research proof-of-conceptv1.22.1

In plain English

This page covers the high-risk pattern where small adapters, routes, memory, evaluators, and descendants can reinforce each other across time. It is a risk model, not a build guide.

  • Why this matters: AI risk can come from the whole arrangement, not one obvious model.
  • What to look for: data, memory, routes, adapters, tools, evaluators, updates, and rollback paths.
  • Technical version below: the expert terminology remains available and is linked through the glossary.

The Low-Rank Supply Chain

Evidence levelDemonstrated research proof-of-conceptTechnical label: Demonstrated research proof-of-concept

Adapter supply-chain risk sits between full model weights and ordinary configuration. Adapters are small enough to be treated as plugins, but powerful enough to alter model behavior. Research on LoRA-based attacks and composition-triggered vulnerabilities supports the need for adapter-specific A record of where a component or behavior came from. Open glossary definition and composition testing.

Why ordinary dependency thinking is incomplete

A software library usually executes code. A model A small add-on that changes or specializes model behavior. Open glossary definition changes a learned function. It may have no obvious procedural logic to inspect. Its effect is expressed only through a base model and runtime context. That makes familiar supply-chain review necessary but incomplete.

Supplier diversity and evaluator diversity

Multiple suppliers can reduce dependence on one vendor. They can also increase incompatibilities, hidden assumptions, and correlated blind spots if suppliers draw from the same base models, datasets, benchmarks, or evaluation tooling.

Required controls

The supply chain between the weights is not a footnote. In an adaptive ecology, it is one of the places behavior moves.