Skip to content
#small language model Open access

THE OCCUPATION OPERATOR - Substrate Independence, the Partition Theorem, and Why a Virtue Detector Must Stay Out of the Loop

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research)

Abstract

Abstract Four papers of this programme — on metrics, reward models, constitutions, and schools — reached the same prohibition without noticing they agreed: a virtue detector must never enter the loop that acts on the measured. This paper states the object they were touching from four sides. An agent originates an act. Someone outside takes the origination. The form survives; the possessor changes. Two properties — does the act leave something worth taking, is being seen doing it worth something — fix which of three residues remains: the act redirected, the act hollowed, or the act gone. The partition turns out to be analytic. It sorts every case because it was built to, so sorting cases proves nothing — a form of support this programme has offered five times and now withdraws. What survives is sharper. A detector given a consequence becomes an appropriable output, so the residue relocates to a channel the detector cannot see, and the destination is computable in advance. Each channel is invisible to the audits built for the others: fix your Goodhart problem and you have lost sight of two thirds of the space. The boundary is stated too. No audience, no display value, no Ceremony, no transfer — quantum measurement sits just outside, and taking it inside would mean importing a counterexample as a confirmation. The selection rule has been used five times and never tested against an outcome nobody knew. Six instruments are coded, the codings are fixed, the date is 1 September 2028. A year spent finding out what this programme does not own, now turned on the one structure that survived. It is smaller than advertised, and it has never been at risk. It is at risk now. Keywords: occupation; Inversion Theorem; Capture Law; appropriability; display value; Goodhart’s law; institutional decoupling; multitasking; substrate independence; instantiation condition; underdetermination; mutual information; reward models; audit; virtue detection; ALGUILAS The Operator in Plain Language This is the same content for a reader who wants the shape before the machinery. The situation. You do something worth doing. Somebody outside you has an interest in your doing it, and can see enough of it to have an opinion. That is all the operator needs — an interest and a view. It does not need malice, and it does not need a person: an unattended metric with nobody behind it produces the same result as a tyrant, which is one of the more disquieting things the theory says. What happens. The shape of what you do survives. What you do continues to look exactly like the thing it was. What changes is whose it is — the reason it happens moves from you to them. That is the whole of the operator, and the reason it is hard to see is that the visible part is unchanged. Where it goes. Two questions settle it, and you can ask them about anything. Does what you do leave something behind that they can take and still want? An hour logged, a document filed, a number returned. If yes, then what you do bends toward producing that thing well — Redirection. The activity is still happening, energetically, and it is now aimed at them. This is Goodhart’s law, and it is the failure everyone knows about. If not — is being seen doing it worth something to them? The assembly, the pledge, the signed commitment, the poster in the corridor. If yes, the performance becomes the product and there is nothing behind it — Ceremony. Nobody is cheating here, which is why anti-gaming measures find nothing: the appearance is not concealing the substance, it has replaced it. If neither? Then nobody has a reason to touch it and it simply stops — Withdrawal. The restraint that produces no record, the attention nobody counts, the refusal that leaves no trace. This failure is invisible by construction, because the evidence of the activity and the activity leave together. Why detectors make it worse. Build something to catch one of the three, then attach a consequence to what it reports — a bonus, a gate, a training signal, a published table. Your detector’s output is now itself a thing you produce and they take, which is the first question above, answered yes. So the activity bends toward satisfying the detector, the detector reports clean, and the occupation has moved to a channel the detector was never built to see. This is not a caution about doing it badly. There is no careful version. Any consequence at all is enough, because the operator does not distinguish a training gradient from a bonus from a league table. And the three hide from each other. Anything built to catch Redirection looks for anomalies — clustering at thresholds, distortion around the target. Ceremony produces none: nothing is being gamed, and the data is beautifully clean. Anything built to catch Ceremony looks for a gap between claim and reality. Redirection has no such gap; the redirected work really does produce what is measured. Anything built to catch Withdrawal looks for absence, and both the others produce presence. So an institution that has fixed its metrics problem has fixed one third of the space and has just lost the ability to see the other two. The rule. Measure to understand. Never measure to decide. The moment a virtue score determines anything, it has joined the thing it was built to watch.

View source

Similar papers

#computer vision Open access Jun 2016

Software Development in Startup Companies: The Greenfield Startup Model

The results are packaged in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible, and the need to shorten time-to-market, by speeding up the development through low-precision engineering activities.

Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al. · 178 citations · ⚡14
#computer vision Open access Oct 2016

Software Startups - A Research Agenda

Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models.

M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al. · 157 citations · ⚡17
#machine learning Review Open access Oct 2016

“Failures” to be celebrated: an analysis of major pivots of software startups

This study conducts a case survey study based on the secondary data of the major pivots happened in 49 software startups, and demonstrates that customer need pivot is the most common among all pivot types.

Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al. · 127 citations · ⚡15
#computer vision Review Open access May 2015

A survey study on major technical barriers affecting the decision to adopt cloud services

The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability, which underlines the importance of the technical and security perspectives for research investigating the adoption of technology.

Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al. · 111 citations · ⚡8
#computer vision Open access Feb 2018

Lean Internal Startups for Software Product Innovation in Large Companies: Enablers and Inhibitors

This study investigates how Lean internal startup facilitates software product innovation in large companies and identifies its enablers and inhibitors, and shows the potential of the method-in-action framework to investigate the Lean startup approach in non-startup context.

Henry Edison, Nina M. Smørsgård, Xiaofeng Wang et al. · 78 citations · ⚡6
#computer vision Conference Sep 2010

Exploring the Sources of Waste in Kanban Software Development Projects

The application of agile software methods and more recently the integration of Lean practices contribute to the trend of continuous improvement in the software industry. One such area warranting proper empirical evidence is a project’s operational efficiency when using the Kanban method. This short paper takes a new angle and explores waste in the Kanban-driven software development project context. A preliminary research model is presented for helping the consequent replication of the study. The results from the empirical analysis suggest Kanban can be an effective method in visualizing and organizing the current work, but does not prevent waste from creeping in, although the overall project outcome may be successful.

Marko Ikonen, Petri Kettunen, Nilay V. Oza et al. · 67 citations · ⚡9

Related blog posts

MIT News · Artificial Intelligence Sep 14, 2026

New method enables AI for safety-critical situations

The “HardFlow” algorithm could help generative AI models produce high-quality outputs that obey strict requirements when “pretty close” doesn’t cut it.

GPT-Lab Sep 10, 2026

Responsible AI Must Consider Its Afterlife

AI may appear weightless, but every model depends on physical infrastructure. To understand responsible AI, we need to look beyond algorithms and consider the entire lifecycle of the hardware behind them. The post Responsible AI Must Consider Its Afterlife appeared first on GPT-Lab.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.