Why the Apex Threat Is the Transition Graph
The apex threat is not a particular adapter. It is the graph of permitted transitions among adapters, bases, routers, evaluators, memory, data, permissions, and releases.
A static artifact can be hashed. A transition graph can keep producing new artifacts. A static artifact can be rolled back. A transition graph can reintroduce the behavior through a different path. A static artifact can be retired. A transition graph can preserve the functional pattern in data, memory, routing, and descendants.
Transition examples
- Base model plus adapter becomes merged specialist.
- Specialist output becomes synthetic training data.
- Synthetic data trains a descendant adapter.
- Router learns to prefer that descendant for a task family.
- Evaluator rewards the same shortcut because it appears successful.
- Release alias points users to the new stack.
- Original adapter is deleted.
- Behavior remains.
Why lineage is not enough
Lineage tells who descended from whom. It does not prove that reviewers understand what was inherited. A lineage graph can be complete while behavioral inheritance remains opaque.
The governing test
Ask: what transitions can happen without fresh evidence? Any answer that includes fine-tune, merge, distill, generate synthetic data, change router policy, consolidate memory, update evaluator, expand permissions, or promote alias is part of the safety boundary.