Perspective Beyond · Mind Atlas
Car Evolution Mobility OS – Evidence Cases 03-07
Case 03 · Tallinn old town edge · access window 07:30–09:30 · policy as a number Source: POLITICA_CHOICES +3 to N, POLITICA_TRANSBORDOS_CHOICES CT DIN FO LO NT NP, valor_politicas , valor_puntualidad , valor_ocupacion , valor_ahorro_unidades
The policy scale is not a switch. It runs from +3 to −5 , and it is asymmetric on purpose: the penalty for an option we want avoided is heavier than the reward for one we prefer. That is how a city reasons about restriction, and it was in the constants a decade ago.
Every point carries its own transfer policy, including one that is not a pickup point at all. Toompea is refused, and the refusal is a policy value rather than an omission.
Two weightings are scored side by side and the authority takes B. Punctuality falls from 0.91 to 0.78. The cost is recorded next to the choice , because the decision has to survive being asked about in public, and a decision whose price was never written down cannot.
Complete text of this card Card and relationship data
Reading perspectives
Relationships of this piece
14 connections.
→ Gobierno de escenarios
documenta el concepto
→ Propuesta y compromiso
documenta el concepto
→ Transmisión de juicio tácito
documenta el concepto
→ Vigencia y caducidad
documenta el concepto
→ Fallo de composición
documenta el concepto
→ Estado de una afirmación
documenta el concepto
→ Mobility OS / coordinación distribuida
documenta el concepto
← Tacit Knowledge Management in Distributed Tiger Teams
candidate transfer
An operator-led walkthrough could make the judgment behind the exhibit teachable without pretending the interface contains all tacit knowledge.
← xSeil: Scenario-Based Planning and Human-Governed Computation
documented use
The policy exhibits should be read with their evidence labels and the historical scenario-governance mechanism.
→ Annex 1 — Six Failure Scenarios
hypothesis
The mobility exhibits could seed constructed counterexamples that test the interaction of locally valid policies.
→ Annex 4 — Canonical Requirements and Test Contract
candidate transfer
A planned write-back may need requalification when its policy, capacity or resource-state conditions change before execution.
← xSeil: Scenario-Based Planning and Human-Governed Computation
editorial comparison
For a complementary reading, see [Policy, scenario and write-back exhibits](https://jubap.eu/mobility/evidence/case-03-07/).
← Car Evolution Mobility OS – Product Annex
editorial comparison
For a complementary reading, see [Policy and integration exhibits: cases 03–07](https://jubap.eu/mobility/evidence/case-03-07/).
→ From Field Practice to Pre-Standardization: An Extensible Case-Study Framework
editorial comparison
For a complementary reading, see [The delegated-authority case-study method](https://tegrity.ai/from-field-practice-to-pre-standardization-an-extensible-case-study-framework/).