GOVOG Open the platform

11,740 events · no schema · no labels

Government,observed.

GOVOG reads the events a state leaves behind, reconstructs how it really runs, and holds back every finding it cannot prove.

01ReadEvents 11,740

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.

02InferCodes named 39

Order, from the values alone.

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.

03ReconstructCase BUILD-00279

One case, followed.

BUILD-00279, to “Obtain a construction permit”: nine steps across 79.9 days, joined in the order they happened.

04MeasureWork share 0.6%

12.0 hours of work in 79.9 days.

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

What it read, and what it holds back.

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

  • vorgang_nrcase
  • dienst_typeservice
  • aktiwiteitstep
  • begin_tijdstart
  • end_tsend
  • medewerkeractor
  • behoerdeagency
  • eenheidunit
  • quellsystemsystem
  • wijzechannel
  • besluit_kodeoutcome
  • zielgruppesegment
  • subjekt_idperson

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

  • 11 observations, no open blocker
  • 29 held for validation: a hypothesis with an open blocker, never a recommendation

Engines

Eleven engines. One model.

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.

Process9Data7Citizen4Risk4Legal3Resource3Technology3Decision2Financial2Service2Organization1

Ask

Ask it something.

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.

OrchestratorAnswer 1
Why does “Obtain a construction permit” take 97.8 days?
  1. Intentduration/why .*(take|long|slow)/Obtain a construction permit
  2. EnginesProcessDataCitizenRiskLegalResourceTechnologyDecisionFinancialServiceOrganization
  3. Evidence85 items returned

5 engines · 85 evidence items

0.4 days of work. 97 days of waiting for each other.

  • Queueing between agencies87.2 days
  • Handoffs and re-entry3.4 days
  • Rework after incomplete files4.4 days
  • Verifying the same fact twice2.3 days
  • Work the law actually requires0.4 days
  • Fact39.5 days are spent waiting before “Environment Agency assesses impact”event log
  • InferenceEnvironmental assessment is at 118 per cent of its establishment, so arrivals queue rather than clearevent log and establishment data
  • InferenceEstablishment was set independently of the volume the service carriesestablishment snapshot

Open the findingsExplore the process

Turns this answer into a one-page note, ready to print.

Proof

Four cases. Only one should be flagged.

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.

APositive case

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

BControl

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

CJustified negative

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

DTrap

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.

Principles

What GOVOG refuses to do.

Four rules the code enforces, each shown with the behaviour it produces.

01

Invent a number.

With no pay scale, a cost reads "not priced". A blank cannot be quoted; a plausible guess can.

02

Call silence a clean result.

An engine never given its inputs says so, wherever its findings would have been.

03

Recommend what it has not proven.

A finding with an open blocker is held for validation, whatever its severity.

04

Touch a production system.

It reads telemetry and proposes change. Only a human-gated pipeline may ever deploy one.

Standards

Adopted, not invented.

Where a published standard exists, GOVOG profiles it rather than inventing a vocabulary. Each line ends at the code that does it.

  • Event logcases, steps and timesXESgtip/interop/xes.pyOCEL 2.0gtip/interop/ocel.py
  • Lawthe instrument and the provisionELIgtip/standards/eli.py
  • Requirementwhat must be shown, by what evidenceCCCEVgtip/cccev.py
  • Findingwhich engine, from which artefacts, whenPROV-Ogtip/standards/profile.py
  • Entityagencies, people and servicesSEMICnot yet profiled

Not built yet

Said plainly, so nothing here is read as more than it is.

  • Not builtA government's own dataNo government has handed GOVOG its own records. One public log has been read, a Dutch municipality's permits, and every inferred field was wrong. The results shown here are on Verdana, a synthetic state.
  • Not builtA human adjudication panelSo no interpretive claim has a baseline to be measured against.
  • Not builtThe transformation bridgeThe pipeline that would turn a proposal into a deployed change does not exist.

Team

The people behind it.

01

01 · Founder & CEO

Your Name

“A one-line introduction in your own words: why GOVOG has to exist, and what you bring to it.”

The platform

See it run on Verdana.

Open the platform