Skip to content

Interface: SchedulingFeasibilityRequest

@kortexya/reasoninglayer


@kortexya/reasoninglayer / Scheduling / SchedulingFeasibilityRequest

Interface: SchedulingFeasibilityRequest

Defined in: src/types/scheduling.ts:122

Input to SchedulingClient.feasibility.

Remarks

Agents are identified by opaque caller-chosen string IDs so the response can be joined back to whatever identity the caller maintains (employee numbers, user IDs, UUIDs, display names, …).

Properties

agents

agents: AgentSpec[]

Defined in: src/types/scheduling.ts:124

All agents that may be assigned to slots.


days

days: number

Defined in: src/types/scheduling.ts:126

Number of days in the scheduling horizon. Valid day indices are 0..days.


demands

demands: ShiftDemand[]

Defined in: src/types/scheduling.ts:130

Per-slot demand. At most one entry per (day, shift) pair.


pins?

optional pins: Pin[]

Defined in: src/types/scheduling.ts:132

Pre-assigned (agent, day, shift) triples. Defaults to empty.


shiftsPerDay

shiftsPerDay: number

Defined in: src/types/scheduling.ts:128

Number of shifts per day. Valid shift indices are 0..shiftsPerDay.