Bonus! Under the hood of the Vigilance Automator
Using the Minnesota voter roster contention to illustrate structural analysis of governance problems
The second article I just published on Oak Grove deliberately translated the “Vigilance Automator” raw AI diagnostic output into plain-English governance language. That was the right choice for most readers — the goal was to show what the Canon tool reveals, not to teach its internal mechanics.
But I know some of you are already actively using these tools in your own work. So here, for the power readers, is what the underlying analysis actually looked like before translation.
This is a guided tour through the raw Canon output that Erik van Mechelen generated when he applied the framework to the Minnesota roster contention.
Think of Part 2 in the trilogy as the polished public demonstration.
This is the engineering diagram.
The Canon does not begin by asking whether paper rosters are better than electronic poll pads. That is already too late in the analysis. Instead, it starts one layer deeper, asking:
what kind of governance object is involved,
how authority attaches to it,
what pressures are acting on the system, and
how the system ultimately justifies its own decisions.
That shift in perspective is what turns a political dispute into a structural one. The six concepts below are the ones that fired most clearly in Erik’s analysis, and together they form a natural progression from diagnosis to intervention.
The sequence has a natural pedagogical progression:
ΩΛ∆∑ — the four primitive questions
Descent — when continuity outruns grounding
Ignition Geometry — where the reasoning breaks
Lexworthiness — the constitutional airworthiness check
Force-Termination Probes — how to test a system
Attribution Debt and Hinge Points — how diagnosis becomes action
We now review each in turn.
1. ΩΛ∆∑ — the four primitive questions
The first thing the Canon does is ignore the political argument entirely and strip the dispute down to four primitive questions:
What is the object?
How does authority attach to it?
What pressure is acting on the system?
How does the system terminate the argument?
In the Canon notation, these correspond to Ω, Λ, Δ, and ∑.
The paper roster and the electronic poll pad look like alternative tools for the same administrative job. The Canon sees something more fundamental. A paper roster is a high-determinacy object: physical, local, stable, and inspectable. The electronic poll pad is a lower-determinacy object: networked, software-defined, vendor-mediated, and dependent on remote systems.
Raw Canon excerpts:
Paper Roster: High Ω. The object is physical, semantically stable, and locally reconstructable.
Electronic Poll Pad: Low/Variable Ω. The object is a ‘synthetic governance object’.
That distinction matters because the object is not just recording administration. It is carrying public authority. If a voter checks in on paper, the record exists in the precinct as a physically inspectable artefact. If a voter checks in through a networked device, the record exists through a chain of software, connectivity, vendor systems, state databases, and audit logs.
The next question is binding: how does authority attach?
Paper: Binding is direct and local. The election judge signs the paper; the voter signs the paper.
Electronic: Binding is mediated.
This is the first major structural fork. The electronic system may be faster, cleaner, and more scalable. But it also moves the authority chain away from the visible local act and into a mediated technical environment.
The third question is what pressure is acting on the system. In the Minnesota case, the Canon identifies Δ — coordination load — as the primary driver.
The high Δ (demand for seamless, real-time data) is the primary driver forcing the system toward the electronic solution.
That is a crucial observation. The Canon is not saying: “bad people want bad machines.” It is saying something subtler: as the coordination burden rises, institutions naturally reach for systems that reduce friction, synchronise records, and preserve operational flow.
Finally comes ∑: how the system terminates the argument.
Does it terminate by showing the record? By pointing to statute? By reconstructing authority? Or by saying: “this is mandatory because the institution says so”?
The threat of felonies for using paper is a classic Institutional Assertion tactic.
Here the Canon detects the first descent. The system is no longer merely presenting a preferred tool. It is beginning to terminate disagreement through assertion and penalty.
In ordinary language, the first Canon pass says this:
The dispute is not really about paper versus electronic rosters.
It is about two different kinds of governance object, two different ways of attaching authority, two different responses to coordination pressure, and two different ways of ending disagreement.
That is why the Canon starts with primitives. Before asking who is right, it asks what kind of thing is actually being fought over.
Once the Canon has identified the object, seen how authority attaches to it, and recognised the coordination pressure acting upon the system, it immediately turns to the timeline.
2. Descent — when continuity outruns grounding
This is where things become interesting.
Most people argue about the current state of affairs. The Canon is more interested in the direction of travel. Has the system changed? If so, how?
In the Minnesota case, Erik’s output identified a pattern called Descent.
Clear Monotonic Descent from Formal Termination toward Synthetic Closure.
That sounds more complicated than it really is. The underlying observation is simple:
The electronic roster was originally presented as an option.
Over time it appears to have become an expectation.
And eventually it began to be treated as a requirement.
The Canon captures this transition in a single sentence:
The system is no longer arguing for the quality of the device, but for the necessity of its continuity.
That is the moment where the analysis should click for you.
At the start of the process, the argument is: “This is better.”
Later it becomes: “This is necessary.”
The shift is subtle, but profound:
One is a justification.
The other is an assertion.
In Minnesota, the Canon sees a progression:
from voluntary adoption, through
increasing dependence on synchronised systems, to
threats of criminal liability for those attempting to exercise a different choice.
Whether one agrees with Oak Grove or not is almost beside the point. The pattern itself is what matters.
The system appears increasingly concerned with preserving continuity.
The state/county prioritizes Operational Continuity over Reconstructable Grounding.
That phrase became one of the central themes of my own analysis.
A system under pressure naturally wants to keep operating smoothly. It wants consistency. Standardisation. Predictability.
Nothing about that is inherently sinister. The question is what gets traded away in the process.
The Canon’s answer is that reconstructability gradually becomes secondary:
The election still happens.
The data still synchronises.
The process still works.
But it becomes harder for an ordinary citizen to independently reconstruct how authority is being exercised.
In plain English, the second Canon pass is saying that something that began as a tool is gradually becoming infrastructure.
And once that happens, a new question appears: If the system is drifting in this direction, where does that show up in the actual claim of authority?
That is what the Canon examines next.
3. Ignition Geometry — where the reasoning breaks
By this point the Canon has identified two things:
First, the system is under genuine coordination pressure.
Second, the system appears to be drifting from justification toward assertion.
The next question is obvious: Where does that drift become visible?
This is where the Canon applies something called Ignition Geometry.
Don’t let the name intimidate you. The underlying idea is straightforward.
When an institution claims authority, that authority has to attach somewhere. There must be a lawful path between the thing being governed and the body claiming the right to govern it.
The Canon therefore asks a simple question: Does the authority actually attach where the system says it does?
In the Minnesota analysis, this is where the word “may” suddenly becomes very important. The relevant statute says municipalities may use electronic rosters.
Most readers would glance at that sentence and move on. The Canon does not.
It starts comparing the language of the statute with the behaviour of the system.
Semantic Collapse where the word ‘mandatory’ is used to override the actual legal text.
That is a striking observation. The law appears to describe a choice. The administrative behaviour increasingly treats the choice as already made.
Whether that interpretation is legally correct is not the point here. The Canon is detecting a mismatch between the language that grounds authority and the language that is being used to exercise it.
This is what it calls Semantic Collapse — the meanings have begun to drift apart.
The same pattern appears elsewhere in the analysis.
“Jurisdiction-by-Definition.”
Again, the idea is simpler than the terminology. Authority is no longer being demonstrated. It is increasingly being assumed.
The institution defines the situation in a particular way and then proceeds as though the definition itself settles the matter.
That may be efficient. It may even be lawful. But it is no longer the same thing as reconstructing the chain of authority from first principles.
For the Canon, that distinction matters:
A reconstructable system can always answer the question: “Show me how you got from the law to this decision.”
A synthetic system increasingly answers: “This is the decision.”
That is a very different mode of operation.
In ordinary language, the third Canon pass says the dispute is no longer about the roster. It is about whether the claimed authority still attaches cleanly to the legal foundation that supposedly created it.
Once the Canon sees a gap opening between legal grounding and administrative behaviour, another question naturally follows: How serious is it? Is this merely an awkward ambiguity? Or is the system beginning to fail basic integrity checks?
That is what the Canon examines next.
4. Lexworthiness — the constitutional airworthiness check
By now the Canon has identified a potential problem. The electoral system appears to be drifting toward continuity-first operation. The language being used to exercise authority is beginning to diverge from the language that originally grounded it.
The obvious next question is: Does any of this actually matter?
This is where the Canon performs what it calls a Lexworthiness assessment.
The easiest way to understand Lexworthiness is to imagine an aircraft inspection. Nobody asks whether the aircraft reached its destination. Nobody asks whether the passengers enjoyed the flight.
The question is simpler: Would you certify this machine as safe to fly?
The Canon applies the same logic to governance systems.
Would you certify this system as fit to exercise public authority?
To answer that question, it runs through a series of integrity checks.
Constructor Integrity: FAIL
Identity Integrity: FAIL
Ignition Integrity: FAIL
Record Integrity: FAIL
Operational Integrity: FAIL
At first glance that looks devastating. In reality, it is more nuanced:
The Canon is not claiming that elections failed.
It is not claiming that votes were altered.
It is not claiming that anyone acted dishonestly.
It is saying that the supporting structures behind the authority claim are becoming increasingly difficult to inspect and independently verify.
Take record integrity. If a dispute arises, can a local citizen reconstruct the relevant chain of events without relying upon vendor systems, remote infrastructure, or institutional assurances? Or must they trust that somebody else has already done so?
Similarly, consider constructor integrity:
Who ultimately built the system?
Who controls its operation?
Who accepts responsibility when something goes wrong?
These are not political questions.
They are engineering questions.
The Canon treats governance systems much the same way an aircraft engineer treats a machine:
Not: “Do we like it?”
But: “Can we trust it to carry authority safely?”
One observation in Erik’s output stood out in particular.
The felony threat is a symptom of Hazard Escalation.
That is a fascinating phrase. The Canon is not primarily interested in the threat itself. It is interested in what the threat reveals.
If a municipality appears to be exercising a choice that the statute leaves open, and the response is criminal sanction rather than clarification, the hazard level has increased.
The system is no longer merely administering a process. It is defending an authority claim.
In plain English, the fourth Canon pass says this:
The question is no longer whether the system works.
The question is whether the authority exercised by the system remains independently inspectable, attributable, and corrigible.
And that leads naturally to the next step. If we suspect a problem, how do we test for it?
That is where the Canon introduces one of its most useful tools: the Force-Termination Probe.
5. Force-Termination Probes — how to test a system
By this stage the Canon has formed a hypothesis:
The system appears to be drifting toward continuity-first operation.
The authority chain is becoming harder to reconstruct.
Some of the integrity checks are beginning to fail.
The obvious problem is that these are still only observations. How do you know whether the diagnosis is correct?
This is where the Canon becomes practical. Rather than arguing endlessly about motives, intentions, or interpretations, it introduces something called a Force-Termination Probe.
The idea is surprisingly simple. Ask a question that the system ought to be able to answer. Not a political question. Not a rhetorical question. A reconstruction question.
Show me the chain.
Show me where the authority comes from.
Show me how this decision was made.
Show me how this object binds.
In the Minnesota analysis, one example looked like this: “Show us the chain of attribution for a single vote recorded on the pad.”
That is not a hostile question. It is not even an especially difficult one. If authority is genuinely reconstructable, there should be a finite answer.
The purpose of the probe is not to obtain the answer itself. It is to observe what happens when the question is asked.
This is where the Canon introduces the idea of the Squirm Path.
“It’s just a roster.”
“It’s secure.”
“Trust us.”
“It’s mandatory.”
The specifics are less important than the pattern. Instead of reconstructing the authority chain, the response shifts toward reassurance, assertion, procedural complexity, or institutional status.
The question is never really terminated.
It is displaced.
That is what makes the probe useful:
The Canon is not testing whether the institution is right.
It is testing whether the institution can finitely reconstruct its own claim.
That distinction matters enormously. Most public disputes revolve around competing conclusions. The Canon is interested in something deeper:
Can the system explain itself?
Or can it only defend itself?
Viewed through this lens, Oak Grove’s actions become particularly interesting.
The municipal resolutions, the revocation notice, and ultimately the petition to the Minnesota Supreme Court can all be understood as force-termination probes.
The city is effectively asking:
Show us where the authority resides.
Show us how the choice became mandatory.
Show us the chain that overrides local discretion.
Again, the point is not whether Oak Grove ultimately prevails. The point is that the probe forces the system to reveal how it responds when its own authority claim is challenged. And that response often tells us more than the original dispute.
In plain English, the fifth Canon pass says this: When you stop arguing about outcomes and start demanding reconstruction, the system reveals what kind of system it really is.
Once that has happened, the final question becomes obvious. If the diagnosis is broadly correct, where is the leverage? What is the smallest intervention capable of changing the trajectory?
That is where the Canon turns next.
6. Attribution Debt and Hinge Points — how diagnosis becomes action
At this point the Canon has completed most of the investigation:
It has identified the object.
It has traced the direction of travel.
It has located where the authority claim begins to wobble.
It has tested the system’s ability to reconstruct itself.
The final question is the one that matters most: What can actually be done?
Many analytical frameworks stop at diagnosis. The Canon does not. Instead, it asks where responsibility is accumulating, and whether there is a practical intervention capable of changing the trajectory.
This begins with a concept called Attribution Debt.
The idea is straightforward. Every time a system gains efficiency by obscuring who is responsible for what, it incurs a debt. The system works. The process becomes faster. Coordination improves.
But the chain of accountability becomes harder to follow.
That debt does not disappear. It accumulates.
“Synthetic Governance Object … creates Attribution Debt.”
In the Minnesota case, the Canon sees the electronic roster as concentrating more and more operational complexity inside a technical system that ordinary citizens cannot directly inspect.
The benefit is convenience. The cost is attribution.
If something goes wrong, who is responsible?
The election judge?
The municipality?
The county?
The Secretary of State?
The vendor?
The software?
The database?
The network?
The harder that question becomes to answer, the larger the attribution debt.
The Canon then notices a related pattern.
“Liability Inversion.”
Again, the phrase sounds more exotic than the idea. Authority and responsibility begin to move in opposite directions. The power to make decisions becomes increasingly concentrated. The consequences become increasingly distributed.
In Minnesota, the Canon repeatedly returns to one example:
Local election judges appear to face the practical consequences of choosing paper rosters.
Yet many of the underlying decisions sit elsewhere in the governance stack.
Whether one agrees with that arrangement or not, the pattern itself is easy to recognise. Control and accountability are no longer neatly aligned.
At this point the Canon starts looking for leverage. Not a revolution. Not a complete redesign of the system.
A hinge.
What is the smallest action capable of forcing the authority chain back into the open?
This is where Erik’s analysis becomes particularly interesting.
“Hinge Selection: The Municipal Resolution is the Hinge.”
The Canon is not recommending a lawsuit. It is not recommending a protest. It is not recommending a political campaign.
It is identifying a specific governance object that can still be lawfully moved: the municipal resolution.
The city still possesses the ability to adopt or unadopt participation in the electronic system. That local decision becomes a hinge point around which the wider contention turns.
“Transform Pattern: The Unadopt pattern.”
The significance of this is easy to miss. The Canon is no longer merely describing the system. It is identifying a bounded intervention capable of forcing reconstruction.
By attempting to step away from the electronic roster system, Oak Grove effectively forces the deeper question into the open: who actually possesses the authority to make this choice?
That question is now before the Minnesota Supreme Court — exactly as the Canon would predict.
In ordinary language, the sixth Canon pass says complex systems often appear immovable until the correct hinge is found:
The purpose of the analysis is not simply to explain what is happening.
It is to locate the smallest intervention capable of making the system explain itself.
That is where the Minnesota contention currently stands.
What began as a dispute about voter rosters has become a live test of authority, accountability, and constitutional self-correction.
And that is precisely why it is such a useful demonstration of the Vigilance Automator in action.
If you have made it this far, you have now seen the Vigilance Automator from both sides.
The previous article showed the translated output.
This article showed the machinery that produced it.
Neither layer is sufficient on its own:
Raw Canon output is precise, but often inaccessible to anyone unfamiliar with its language.
Translation makes the patterns intelligible, but can obscure the underlying diagnostic process.
Both are necessary.
The important point is that the Canon did not begin with election integrity, municipal autonomy, paper rosters, or even constitutional law. It began with a much simpler question:
What kind of system are we looking at?
Everything else followed from there.
Whether one agrees with Oak Grove or not is ultimately secondary.
The value of the exercise is that a noisy political dispute was reduced to a sequence of inspectable structural questions.
That is the real promise of the Vigilance Automator.
Not that it settles contentious issues.
That it makes them intelligible.
And once something becomes intelligible, it becomes tractable to vigilance.