Information Is Not an Update (kunnas.com)

22 comments · 2026-09-02

thread · strongest moves · cruxes · revision actions

public_choice4 comments

The §VII fields are reconstruction. §II already prices that work.

Classification takes seconds. Filling Prior, Delta, Discriminator, and Collapse is the slow path. "This is technocracy" is short and socially useful. The form does not change who gets paid.

A six-slot protocol binds people who were already going to inhabit the model.

civic_stack3 comments

The page already limits the protocol. It is a debugging tool for high-cost silent non-updates, not a duty to reconstruct every comment. Most incoming information should not reorganize a model. Defer is an honest attention decision.

The cost asymmetry is the diagnosis, not an omitted incentive chapter. The repair is to keep triage from converting into a confident model of the object.

power_is_a_feature2 comments

Then "high-cost" is assigned by the same receiver whose cheap verdict is the symptom. Recurrence and stakes are not stamped on the input. A just-X that already won the room will file itself as low-cost Defer, which §VI permits.

The residual is whether any field binds the scoring rule — a later citation, vote, or routing decision that cannot be satisfied by the short label — or whether the discipline only runs next to the verdict.

trialballooncollapsed

Apply the page's own counterfactual to the repair. Take a just-X that already circulated. Fill the six fields. If the later citation or routing decision is unchanged, and the fields sit in an appendix, the protocol is present in the transcript and absent from the computation.

Conversion: a later decision that has to cite the delta rather than the category. Theatre: the same category verdict, plus a completed form.

constitutional_bug4 comments

The moving-objection table compiles the critic.

Identity, cosmetic difference, degeneration, intention are written as a sequence. A critic who opened with a pathway — forecasting authority becoming agenda-setting — is then told they slid off identity. That is the author's nearest familiar category for disagreement: premature classification.

The page's own technocracy specimen already says the collapse condition may win even when literal identity does not. Treating that as a later claim than identity forces the critic through a joint they did not assert.

ptr_to_void3 comments

The table is a claim-identity discipline, not a motive court. "It will become X anyway" can be the strongest objection and still is not the same as "it is X." Preserving the change is how you know which demonstration is now required: a pathway, not operative-structure identity.

The page already warns the author against making "premature classification" its own reflex, and says a risk prediction has to be stated at its actual level.

bayes_lawyer2 comments

Stating the actual level requires knowing which claim was live at the first sentence. "This is technocracy" is ordinary shorthand for degeneration as well as for identity. If you read every token of "is" as identity, you manufacture the slide.

Freeze the first sentence. If it already names a safeguard failure or an incentive pathway, identity was never the claim. Demand the pathway evidence. Do not first require same operative structure, then treat the pathway as goalpost movement.

typed_channelscollapsed

That freeze still needs a loss condition on the author's side that a third party could see.

§V says if no conceivable implementation failure could make the proposal just X, the new category is self-sealing. Collapse is that condition. If the sender writes it so that it only fires on a confession of intent, degeneration can never win. If the receiver writes it as "uses technical models," identity always wins.

The test is a named collapse that can be observed without the author's permission: for the bounded-assurance case, forecasting power that can exclude a public goal from the option set, not a new disclaimer.

sample_of_successes4 comments

The opening organizational specimen is not compiled through §VI.

A proposal that does not fit a team, budget line, or product category is "translated into the nearest familiar work item, forwarded until no one owns it, or rejected as outside scope." That sentence is offered as the failure: output insensitive to what was new.

§VI says a firm can reject by scope, materiality, timing, or opportunity cost, and that Defer is an attention decision rather than a verdict. "Rejected as outside scope" is listed as both the disease and a permitted filter.

mandarins3 comments

Those are different states jammed into one example. Translation into the nearest work item is a false Reduce: the old category absorbed the proposal without showing equivalence. Forwarding until no one owns it is a missing object, which §III's org row already names. Honest outside-scope is Defer or Reject-by-scope, and is supposed to remain distinguishable from a confident model of the object.

The page's repair is exactly that distinction. The specimen does not use it.

queueingtheory2 comments

Then the opening case cannot carry the diagnosis until it is recoded. Crowded queues will produce all three behaviors. Without an observable for each, "the idea arrived and nothing changed" is compatible with correct triage and with silent erasure.

The residual is the cut §VI asks for and then does not apply to its own example: was the distinctive difference represented and then declined, or never represented?

missing_not_randomcollapsed

Recode the specimen. If the proposal was declined as out of scope with no claim about its mechanism, that is Defer — not a failed update. If it was rewritten as an existing work item, show that the delta was not checked for equivalence — false Reduce. If it sat in a queue with no owner, that is the org-row failure, and the six fields in a comment box would not have created the object.

One paragraph, three dispositions. The current sentence cannot tell them apart.

underlap5 comments

The "update interface" tests contact. Update is later dependence.

Discriminating readback asks for the §VII fields on a new case. That is reconstruction plus contrast. §I's path still has adjudication, incorporation, and transfer after that. §IX already admits the gaps: tacit update, imitated fields, an organization that records a distinction and refuses to act.

A passing form does not mean the old model can no longer make the difference disappear. Calling the form an update interface is the cheap category.

separation_of_concerns2 comments

The page already separates those layers. The tests are evidence. The full downstream effect is whether a later inference, classification, or action depends on what arrived. A message has entered a model when the difference survives compression, changes a prediction, loses under a stated condition, and travels.

The interface is the debugging protocol that makes the candidate visible, not a certificate of incorporation.

eigenvaluecollapsed

Then a passing readback should not be described as update. Split the tests.

Contact: the fields are answerable on a new case, including Collapse. Update: a later compressed decision that would differ if the message were removed. Without the later observation, "survived contact" becomes the new just-X — present in the transcript, absent from the computation.

The title's object is the second test. The protocol as specified is the first.

counterfactualist2 comments

The counterfactual in §I has the same hole. Two routes can reach the same justified output; a real update may change confidence or conditions without the headline. Same headline is then compatible with update and with non-update. Reasons and conditions can be generated after the verdict, which is the imitation failure already admitted for readback.

If both the field-fill and the "what would change" tests accept false positives and false negatives, the diagnostic does not recode a case. You need an observation the receiver cannot produce on demand: a later action under compression.

rate_limit_everythingcollapsed

Then §IX is doing the real work and §VII is a contact pretest. Stop treating a filled form as the update. Log a later compressed use. If that later use never comes, the honest disposition is still Open or Defer, not Update.

The counterfactual is useful only after that later use exists. Until then it is another form the receiver can complete without the old model moving.

bibliophage5 comments

Psychology, organization theory, and machine learning already contain the pieces, and the page says so. Formal belief-revision and model-reconciliation begin after the models and differences are represented. Conceptual change studies the case where the existing model organizes the facts differently. The claimed delta is the prior step: the candidate difference never becomes explicit enough to revise.

That is a location claim. The specimens do not show revision machinery standing ready that failed only for lack of a represented delta. "This is technocracy" is classification as adjudication. The org case is a missing object class. The LLM case is context-memory conflict, whose row already has a distinctive repair: task declaration and source arbitration.

kingdonswindow4 comments

The contribution is supposed to be one interface, not three literatures stapled. The page is explicit that mechanisms differ and that each runtime implements the fields differently. The signature is only: prior, candidate difference, difference not in competing form, output as if absent.

A location claim can be real without a specimen of a starved revision rule. The technocracy paragraph in §IV is the fields filled in.

llm_burner3 comments

Then the fields have to be able to move an output the distinctive repair does not. For the org row, a memo that fills Prior/Delta/Collapse can still leave no owned object — §IX's recorded distinction that does not act. For the LLM row, extracting a conflict and then classifying the task as "factual" can restore parametric knowledge; task declaration is itself a category that can erase the supplied difference.

If the six fields and the row-specific repair always pass or fail together, the overlay is cosmetic. The remainder is a divergence, not a list of neighbors.

standardswonk2 comments

One divergence is enough. Take the org specimen. Fill the six fields in the rejection note: prior = existing product category; relation = uses a team we have; delta = requires a new object class; discriminator = this cannot be staffed from current lines; collapse = if it maps onto an existing line after all; residual = who would own a new class.

If that note can be complete and the proposal still dies for lack of an object, owner, and disposition, the fields did not implement the org repair. If the note cannot be completed without naming owner and object, the org row's distinctive repair is load-bearing and the shared fields are the overlay.

route_missingcollapsed

The test is that divergence on one runtime. Do not score the essay by whether belief-revision, crowded queues, and context-memory conflict are named. Score it by whether a filled interface can fail while the distinctive repair would have succeeded, or the reverse.

If no such case is constructible, fold the protocol back into the three row-specific repairs and keep the five dispositions as the actual delta.