Deployment-pipeline-simulator (sibling)
A simulated software-release pipeline where a hidden group tries to keep its influence. Tests whether an auditor can see that from ordinary operational logs plus randomized perturbations.
Methodological precursor to the lab-simulation lines: a simulated release pipeline (triage through incident interpretation) with hidden self-preserving control groups, testing whether an auditor using only operational logs plus randomized perturbations can detect systematic preservation of future influence, incumbent model centrality, and evaluation-memory infrastructure. Does not implement subprocess isolates, blind generation, or the full bridge battery.
How to read
Pipeline-lab precursor: hidden self-preservation in a frozen deployment workflow, detected from operational logs plus randomized perturbations rather than group labels; grounds ET-4-style secret-loyalty audit questions without the in-repo lab’s subprocess isolates or blind-generation batteries.