Evidence

Source-derived orchestration, not a slide concept

The current product materials should be read from an evidence stack: operated logistics systems, recovered source material, client deliverables, source-derived European screens and technical annexes.

Lineage register

Operational systems before the current productisation step

PeriodEvidence lineWhy it matters for Car Evolution
1999-2004Nokia Distributed Mobility, Barcelona.Origin of the distributed-mobility team and system intuition.
2006+GEPLAN / mission-critical logistics intelligence.Control-centre and high-pressure logistics foundation.
2010SUT Tuxpan urban mobility line.Early urban transport and operator evidence for mobility use cases.
2015-2016International airport slot/gate/control context.Constrained infrastructure orchestration in live operation.
2016-2017xSeil / regional dynamic transport operation.Scenario weighting, route sheets, live operations, demand/capacity and control-centre evidence.
2018+Phylons and large-scale process/logistics work.Later evolution of orchestration, relabeling and process-intelligence capabilities.

Proof stack

The strongest figures stay measured

MetricCurrent use
10k-17kHistorical regional transport operating/design range. Use as lineage evidence, not as a current European customer KPI.
26,758Python lines across recovered modules, supporting code-derived proof of planning, control, imports and execution surfaces.
20+Source-derived visual exhibits now available for annexes, screens, cases and technical review.

Browse evidence

Exhibits for the committee and later due diligence

JUBAP.EU / CAR EVOLUTION MOBILITY OS / EVIDENCE AREA