The 020_17–020_20 TCs create temporal data via `POST /temporal/entities` and then exercise current-state / scope operations. Two distinct questions surfaced in review: - **Does a temporal POST materialise a current-state entity?** Consensus (Discord / API calls): **no** — temporal and current state are independent; current state is created only via Create Entity / Batch Create / Upsert. The TCs assume the opposite. @orihuelab: pairing a current-state POST into setup is *"a hack to get a green light, not a real fix"* — setup should create a regular entity where a current-state entity is genuinely needed. *(from !279)* - **Deleted-scope representation + duplicate timestamps** (020_19/020_20): is a deleted `scope` an NGSI-LD Null or an empty array? And @thomas.bousselin: two attribute instances at the **same** `observedAt` are ambiguous (Stellio replaces the instance; spec is silent) — the fixtures should avoid duplicate-timestamp instances. *(from !292)* **Files to consider:** - `…/RetrieveTemporalEvolutionOfEntity/020_17.robot` … `020_20.robot` - `data/entities/vehicle-different-attribute-types.jsonld`, `vehicle-with-scope.jsonld` - `data/temporalEntities/expectations/vehicle-temporal-representation-property-020-19.jsonld`, `…-020-20.jsonld`, `vehicle-temporal-representation-update.jsonld` _Originated from !279 + !292 (closed in favour of this issue)._