Entur

Norwegian public transport — API integrations, real-time data.

Overview

Entur Overview

Norwegian public transport — API integrations, real-time data.

Owner: John Last Verified: 2026-02-17

Contents

To be populated from Entur project documentation

Active Tasks

Last Verified: 2026-02-17 | Owner: John

Entur — Active Tasks

Open Tasks

No currently active Entur tasks in Mission Control.

Recently Completed

Pending

Historical Tasks

Key Decisions

Last Verified: 2026-02-17 | Owner: John

Entur — Key Decisions

Engagement Decisions

Consulting Via RPG/Kyndryl (Date TBD)

Decision: Engage with Entur through RPG/Kyndryl consulting framework. Rationale: Established relationship, access to public sector contracts. Contact: Hive Consulting (Kjell Ljøstad) as intermediary.

Role: Tech Lead for Team API (Date TBD)

Decision: Position Alem as Tech Lead for Entur's Team API. Rationale: Matches expertise, senior role, strategic impact.

Bid Extension Strategy (2026-02-11)

Decision: Submit bid for contract extension with updated CV. Status: Submitted, awaiting results. Timeline: Deadline was 2026-02-11.

Historical Context

Data Loss Incident (2026-02):

Operational Decisions

Communication Channel

Project Overview

Last Verified: 2026-02-17 | Owner: John

Entur — Project Overview

What is Entur?

Entur is Norway's national journey planner and transport information service. Alem is engaged as Tech Lead for Team API via RPG/Kyndryl consulting arrangement.

Current Status

Engagement Details

Recent Activity

Key Contacts

Documents Lost & Recovered

Note: 553 files were lost from ALAI repo due to hourly-backup.sh bug (2026-02), including Entur documentation. Bug was fixed (commits now go directly to current branch instead of stash+branch-switch). Entur docs may need to be regenerated from email archives and memory.

Specifications Index

Last Verified: 2026-02-17 | Owner: John

Entur — Specifications Index

Engagement Documents

CV & Credentials

Bid Documents

Technical Documents

Note: Most technical documentation was lost in the 2026-02 backup incident. Documents need to be recovered from:

Communication Archive

Email Threads

Key Dates

Recovery Plan

To recover lost documentation:

  1. Search email archives for Entur-related threads
  2. Query HiveMind for historical Entur knowledge
  3. Review session logs from February 2026
  4. Contact Kjell Ljøstad for any shared documents
  5. Rebuild technical documentation as needed