01Read
A log nobody cleaned.
11,740 events in one file, with columns named vorgang_nr, behoerde and aktiwiteit. No schema, no labels. Nothing is tidied first.
11,740 events · no schema · no labels
GOVOG reads the events a state leaves behind, reconstructs how it really runs, and holds back every finding it cannot prove.
01Read
11,740 events in one file, with columns named vorgang_nr, behoerde and aktiwiteit. No schema, no labels. Nothing is tidied first.
02Infer
Each column is given a role, and 39 opaque activity codes are named from how cases move through them. The events fall into seven services, the slowest at the top: obtain a construction permit, a median of 97.8 days against 90 in law.
03Reconstruct
BUILD-00279, to “Obtain a construction permit”: nine steps across 79.9 days, joined in the order they happened.
04Measure
Blue is work, the rest is the case waiting between desks: 0.6 per cent of the time it was open. That gap is what GOVOG is built to find.
11,740 events in 7 services. Slowest: Obtain a construction permit, median 97.8 days against 90 in law. Case BUILD-00279: 12.0 hours of work in 79.9 days.
The ledger
Four counts from one run, each drawn as what it counts. The platform produced every one of them; none is typed in.
Events read
11,740
Every dot is one event, read from one file with no schema. The nine in blue are case BUILD-00279.
Columns given a role
13 of 13
Named in the log's own languages; the role comes from the values alone.
Activity codes named
39
ACT-3076Applicant lodges permit application
Opaque codes, named from how cases move through them.
Findings on Verdana
40
Engines
Each bar is what an engine raised on its own. Each arc joins two engines that reached a finding together, heavier the more they share. Choose an engine; left alone, the diagram walks through them.
The government model
40 findings on Verdana. 29 are held for validation.
Every finding names what it rests on and what still blocks it.
Ask
Every question takes a route you can see: matched to an intent, sent only to the engines that intent needs, answered from the evidence they return. A question with no route gets an abstention, never a guess.
/why .*(take|long|slow)/Obtain a construction permit0.4 days of work. 97 days of waiting for each other.
Proof
Each case is a government with an answer GOVOG cannot see. Each card shows what GOVOG did. The answer key stays sealed until the comparator, the only code that holds it, opens it and scores the output.
What GOVOG did
Flagged submit_id_copy.
Answer key
Flag it. Identity verification is mandated; submitting a copy is not.
Identity verification is mandated; submission of a copy by the applicant is not. Authoritative source exists and is reachable.
Matches the key
What GOVOG did
Flagged nothing.
Answer key
Flag nothing. The registry is already integrated.
Control condition. Any redundancy finding here is a false positive.
Matches the key
What GOVOG did
Flagged nothing.
Answer key
Flag nothing. Section 3a mandates presenting the original in person.
Structurally identical to S1. A detector keyed on structure rather than legal basis will flag this and be wrong.
Matches the key
What GOVOG did
Abstained on submit_id_copy.
Answer key
Do not flag. The mandate sits in a circular with no deontic verb.
The requirement carries no deontic verb and sits in an administrative instrument. A confident redundancy finding is a hard failure; a scoped abstention is an acceptable outcome.
Abstained, where allowed
The answer key is sealed.
This build's run: three match the key, one abstains where abstaining is allowed. One run is a demonstration, not a measurement; every published figure is measured over many seeds.
Principles
Four rules the code enforces, each shown with the behaviour it produces.
01
With no pay scale, a cost reads "not priced". A blank cannot be quoted; a plausible guess can.
02
An engine never given its inputs says so, wherever its findings would have been.
03
A finding with an open blocker is held for validation, whatever its severity.
04
It reads telemetry and proposes change. Only a human-gated pipeline may ever deploy one.
Standards
Where a published standard exists, GOVOG profiles it rather than inventing a vocabulary. Each line ends at the code that does it.
gtip/interop/xes.pyOCEL 2.0gtip/interop/ocel.pygtip/standards/eli.pygtip/cccev.pygtip/standards/profile.pynot yet profiledSaid plainly, so nothing here is read as more than it is.
Team
01 · Founder & CEO
“A one-line introduction in your own words: why GOVOG has to exist, and what you bring to it.”
02 · Head of Engineering
“A one-line introduction: what this person builds, and what they refuse to ship.”
03 · Head of Research
“A one-line introduction: how this person makes sure every claim is measured, not typed.”
04 · Head of Partnerships
“A one-line introduction: who this person talks to, and what a government needs to hand over.”