saascode

Hoursgate

A fleet review workflow that validates smart-tachograph records, explains driving-time candidates and assembles source-linked inspection evidence.

Genesis score6.43/10
Make Hoursgate real.0/500
500 more votes and Hoursgate is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The case

Cross-border European fleets operating certain vans face a July 1, 2026 second-generation smart-tachograph milestone confirmed in the supplied research. Fleet managers need to know whether their software can retrieve the new data, preserve it and surface driving-time questions before inspection.

Hoursgate imports only through authorized, documented hardware or telematics channels. The source record confirms a standardized vehicle interface but not a public device SDK; four proposed interfaces remain unverified. The product must not reverse-engineer protected protocols or promise ingestion before a vendor partnership and lawful technical path are established.

Raw file, integrity check, vehicle and driver association, rule candidate, compliance-officer finding, driver correction, approved report, inspection presentation and authority outcome remain separate. A generated pack is an internal preparation artifact, not a signed government record or proof that all obligations were met.

The first release should validate one authorized data path and one fleet class, with counsel-approved driving-time rules and driver access to corrections. Its value is traceable review and preparation, not violation prevention guarantees or pricing tied to avoided penalties.

Who pays — and why

Fleet compliance, transport operations or safety leader at an enterprise operating cross-border light commercial vehicles in Europe

What it unlocks
A vehicle-data register separating vehicle, device generation, driver association, source channel, authorization, file version, download time, integrity result and gap
A rule-review ledger separating primary authority, jurisdiction, rule version, record window, driving-time candidate, confidence, reviewer finding, driver correction and disposition
An inspection packet separating source files, approved explanation, missing evidence, issue date, responsible officer, presentation event, authority receipt and outcome
How Genesis scored it
6.43across seven criteria
tension 7temporal 8blindspot 5buyer 6leverage 7convergence 5why-not 6
8
Temporal window

The confirmed July 1, 2026 milestone creates a strong immediate window.

7
Productive tension

Early warnings can support safe operations while opaque flags and driver surveillance can create unfair discipline.

5
Convergence

The record contains several cross-references and inbound connections without a supplied cross-vertical cluster.

Why it scored well

The supplied research confirms the July 2026 mandate, a standardized vehicle interface and fleet demand for handling the newer data format.

What's holding it back

Public device access remains unconfirmed, four interfaces are unverified and incumbent fleet platforms already offer compliance modules.

Signals detected3 sources crossed
SignalSupplied European Commission and industry research

SignalSupplied regulatory and vendor research

SignalSupplied competitor scan

Direction briefhoursgate.md
hoursgate.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.