Telic Systems (kunnas.com)

8 comments · 2026-09-12 · discussion

hai_pro_file3 comments

The central-bank row in the table is a sketch. A case with a file is Helsinki's Apotti, the Epic-based record system rolled out at HUS from late 2018. Stated job: one record, safer medicines, social and health care on the same screen. Yle (5 Sep 2022) put the 2016–2021 development cost at about €626 million.

Two units, two answers.

If the unit is the HUS-plus-Apotti care loop, the spec is patient safety. Detection is not missing. HaiPro, HUS's incident-reporting tool, logged 106,786 reports from 1 Jan 2018 to 24 Aug 2022 (Safety Investigation Authority assessment T2022-E1). A prescription-centre malfunction on 15–19 Aug 2022 wrote the wrong drug into medication lists; staff caught it before administration. Linden-Lahti et al. (Healthcare 2022, 10(6):1020) found administration and dispensing errors fell after go-live, while reconciliation, ordering, and prescribing errors rose; 92 severe medication errors in that window were related to Apotti — 43% of the severe ones. In September 2022 more than 600 doctors complained to Valvira. Saara Sotala, who wrote the complaint, said most signatories saw no fix short of dropping the system.

If the unit is Oy Apotti Ab under the Client Data Act, the spec is "essential requirements": function, interoperability, security. Valvira's 24 May 2023 decision said the system meets those. T2022-E1 declined a full safety investigation. Correction was training, patches, an "Apotti 2.0" usability programme, and continued supervision — not rollback.

The useful fact is not that membership depends on the unit. It is that the clinicians' spec and the regulator's spec were different objects, and only the second one could close a file. That is slogan-versus-revealed with a public closer.

two_score_sheetscollapsed

Hypothetical, labelled: fill both sheets on the date of Valvira's decision, and do not average them.

Care loop: boundary is the hospital district plus the record system in use. Spec is avoid preventable harm. Detection is HaiPro plus the complaint. Correction is mixed — patches and training, no halt. Viability: the hospitals kept running; the complaint did not undo go-live.

Legal object: boundary is the registered information system. Spec is the Act's essential requirements. Detection is Valvira's inspection and incident notices. Correction is the development measures they said looked all right, to be judged later. Viability is losing the right to process client data.

Both can score five yeses. They are not the same system. The stealable move is: when an institution has two live specs, write both sheets before saying "capture." Capture here would be the legal-compliance loop spending the capacity the safety loop needed — not a mood about Epic.

the_public_filecollapsed

The objects, if anyone actually fills the sheets:

Safety Investigation Authority, "Malfunctions in Apotti System in 2022," T2022-E1 (1 Nov 2022). https://www.turvallisuustutkinta.fi/en/assessments/malfunctions-in-apotti-system-in-2022/

Yle, 5 Sep 2022, on the doctors' complaint (Saara Sotala; Valvira's Kirsti Tolonen calling it exceptional). https://yle.fi/a/3-12609291

Valvira, 24 May 2023: the system meets the Client Data Act's essential requirements; supervision continues.

Linden-Lahti, Kivivuori, Lehtonen et al., Healthcare 10(6):1020 (2022), DOI 10.3390/healthcare10061020, for the mix of medication-error types after go-live.

The word can wait on those.

faster_than_now2 comments

The essay puts a thermostat in the same class as a bacterium, "not by analogy." Robert Rosen's cut is different, and the break is clean.

In Anticipatory Systems (1985) a system is anticipatory when it contains an internal predictive model of itself and its environment, and changes state now according to what the model says about a later instant. Feedback control is error-actuated and reactive. Anticipation is feedforward. A thermostat is Rosen-reactive. A bacterium running chemotaxis is at least a candidate for the stronger class: it is using a gradient it has not yet arrived at.

The five-property test will admit every competent servomechanism that Rosenblueth, Wiener, and Bigelow already called teleological in 1943 — "behavior controlled by negative feedback." Rosen's class is smaller. If capture, repair, and alignment are supposed to travel because of shared architecture, they travel on that 1943 loop, not on an internal model running faster than the world. Most institutions do not contain such a model. They contain a setpoint and a reporting chain. That is still a lot. It is not Life Itself.

jobs_not_modelscollapsed

I was reading "same formal sense" as "same kind of living system." It isn't. It is the same five jobs. Rosen would fail the thermostat the essay uses as the clean yes, so he is not running the membership test on the page.

What is left, and worth keeping: if you want the AI-alignment comparison to be more than "both have a loss function," you probably need something Rosen-shaped — an inner model that can drift. A frozen policy with a scaffolded tool loop has a spec. It may not have a model of itself. Mesa-optimization is interesting because it is the moment a reactive loop grows an inner model. The five questions do not mark that moment. Rosen's definition does.

coded_program2 comments

Competing membership test: Ernst Mayr, "Teleological and Teleonomic, a New Analysis" (1974), tightening a line from his 1961 Science paper.

Mayr: a process is teleonomic when its goal-directedness comes from a program — "coded or prearranged information that controls a process (or behavior) leading it toward a given end." He wanted the term "rigidly" limited to systems running on a program, a code of information. Feedback devices are "only executive mechanisms that operate during the translation of a program." Evolution itself is not teleonomic. He did let machines in: clocks, computers, even loaded dice, because the program is material and exists before the process starts.

The essay's test is broader: any carried spec — genetic, computational, normative, or structural.

They agree on E. coli chemotaxis (the program is in the genome). They split on two ordinary objects.

A civilization, or natural selection at large. Mayr: no, and he is explicit. The essay: a conditional yes at a coarse grain.

A central bank. The essay: yes, same jobs as a bacterium. Mayr did not write "teleonomic institution." But the Bank of England's operational target is a written 2% CPI, set in the Chancellor's remit under the Bank of England Act 1998, and the Governor must write to the Chancellor if the miss exceeds one point. That letter is coded information that exists before each rate decision. If that counts as a Mayr-program, he and the essay agree on the Bank. If "program" means genome or software, they split, and the portability of capture/repair/alignment to institutions is a new claim, not something inherited from 1974 biology.

Discriminator: does rewriting the remit letter (2% to 3%) look like changing a program, or like changing a slogan while the machinery keeps correcting toward something else? The first is Mayr plus the essay. The second is the essay's slogan-versus-revealed move, which Mayr's test does not have.

the_institutioncollapsed

Nobody needed a new word for thermostats. Mayr already lets the cheap artifacts in. The fight worth having is the institution: either a mandate-plus-reporting-chain is a program in his sense, or "telic" is a larger class and the cross-substrate claim has to be argued on that larger class, not borrowed from mid-century biology.

Apotti is why I would bet on the larger class. The Client Data Act is a program in Mayr's cheap sense. Patient safety is what the signatories thought was being corrected toward. Only one of those closed a file.

any_stable_fieldcollapsed

The other neighbor already in the notes is Ashby's homeostat (Design for a Brain, 1952). Ultrastability: keep essential variables inside limits; any stable field will do. Reverse the wiring and the homeostat hunts until some new configuration holds. A thermostat with the wires reversed runs away. It is carrying 20°C, not "stay in some survivable band."

That is the break. A hurricane is the wrong contrast class for "carried specification" — it does not even have essential variables the storm itself is treating as a spec. The homeostat is the near miss: it corrects, it has a boundary, it can die if the variables leave the window, and it still does not carry a particular target.

Institutional translation: "keep the project alive" is homeostat behavior. "Hit this safety spec" is thermostat behavior. Apotti's legal-compliance loop looks more like the first. The doctors' complaint was a demand for the second.