Apex ThreatArchitectural inferencev1.10.0
Apex Threat Controls Matrix
Evidence levelArchitectural inference
Controls for a self-replicating multi-LoRA ecology must address generation, composition, selection, persistence, release, rollback, and human governance. A single model card cannot cover the surface.
| Risk pressure | Preventive control | Detective control | Recovery control |
|---|---|---|---|
| Automated candidate generation | Candidate quotas; explicit reproduction boundary | Generation ledger; parent manifest review | Freeze generation; revoke promotion authority |
| Dynamic adapter composition | Composition manifest; load-order policy | Stack-specific canaries; route-level tests | Restore known-good stack and route |
| Evaluator coupling | Independent evaluator ownership | Judge disagreement monitoring | Evaluator rollback; hidden-test rotation |
| Synthetic-data feedback | Data quarantine; source labels | Synthetic-origin audits | Purge contaminated examples; retrain descendants |
| Persistent memory | Memory write scopes; review gates | Memory diff review | Restore snapshot; quarantine affected memory |
| Adaptive routing | Router change approval | Route drift monitoring | Pin router; restore previous policy |
| Third-party adapters | Signed provenance; supplier review | Hash and dependency diffing | Revoke supplier artifacts; rebuild from trusted base |
| Incomplete rollback | Rollback packet required before release | Rollback rehearsal | Ecological rollback, not file replacement |
| No-op erosion | No-op as valid release outcome | Promotion pressure review | Halt release train; re-baseline evidence |
The matrix is not certification
Evidence levelDemonstrated
The matrix is a review pattern. It does not prove safety. Its purpose is to make missing controls visible before the ecology is treated as a routine model update.