Task context model

1. Overview

The task context owns the flight-task vocabulary and recovery input used by rule checking, bunch generation, and bunch compilation. The current Kotlin FlightTaskContext is a data context; it does not register an optimization variable family.

1. Dependent Contexts

None. Downstream contexts consume its task values.

2. Concepts / Entities

1. Flight task

$i d_{t}$ : stable task identifier; $d e p_{t}, a r r_{t}$ : departure and arrival airports; $t i m e_{t}$ : scheduled/actual time range; $a i r c r a f t_{t}$ : assigned or enabled aircraft; $s t a t u s_{t}$ : recovery permissions and hard-limit flags.

2. Flight leg and recovery assignment

$l e g_{t}$ : flight-leg plan and route; $r e c o v e r y_{t}$ : optional aircraft, time, or route change; $d u r a t i o n_{t}$ : task duration.

3. Flight-task bunch

An ordered sequence assigned to one aircraft. $B_{b}$ is its task sequence, $a i r c r a f t_{b}$ its executor, and $c o s t_{b}$ its calculated cost.

3. Variables

1. Decision Variables

None. Task and recovery values are inputs to generated columns.

2. Auxiliary Variables

None.

4. Predicates

isFlight(t): task t is a flight-type task. recoveryNeeded(t): the task is in the recovery set. aircraftChangeEnabled(t), delayEnabled(t), and routeChangeEnabled(t) classify allowed recovery operations.

5. Sets

$T$ : all flight tasks; $T^{F}$ : flight-type tasks; $T^{R}$ : tasks requiring recovery; $A$ : aircraft; $B$ : candidate task bunches. $A d j_{b}$ : ordered adjacent task pairs in candidate task bunch b.

6. Intermediate Values

For consecutive tasks in a bunch, the transition time is calculated from the predecessor's end and successor's start:

c o n n e c t i o n T i m e (t, t^{'}) = s t a r t_{t^{'}} - e n d_{t}

7. Assertions

Every flight task has a nonblank identifier, valid airports, and a consistent time range. For every adjacent pair in Adj_b, airport continuity holds:

\forall (t, t^{'}) \in A d j_{b} : a r r_{t} = d e p_{t^{'}}

8. Constraints

This context contributes no solver constraints by itself. Its status and time values are consumed by the rule and bunch-generation feasibility services.

9. Objective Function (if applicable)

None. Cost is calculated for a generated bunch and consumed by compilation.

10. Algorithm References

No independent algorithm document.

11. Ubiquitous Language

Term	Symbol	Definition
flight task	`t`	schedulable flight/recovery unit
flight leg	`leg_t`	task plan with airports and time
recovery assignment	`recovery_t`	optional change applied to a task
bunch	`b`	ordered tasks assigned to one aircraft

12. Design Decisions

Decision	Alternative	Rationale
keep task data separate from compilation	register task variables globally	permits multiple generation/compilation policies

13. Change Log

Version	Change	Reason
1.0	Documented the data-only task boundary	Avoid presenting task entities as a solved model

Task context model ​

1. Overview ​

1. Dependent Contexts ​

2. Concepts / Entities ​

1. Flight task ​

2. Flight leg and recovery assignment ​

3. Flight-task bunch ​

3. Variables ​

1. Decision Variables ​

2. Auxiliary Variables ​

4. Predicates ​

5. Sets ​

6. Intermediate Values ​

7. Assertions ​

8. Constraints ​

9. Objective Function (if applicable) ​

10. Algorithm References ​

11. Ubiquitous Language ​

12. Design Decisions ​

13. Change Log ​