Contact scheduling solver

Platform

Holds how one deployed scheduling solver actually works — how it prioritises records, selects a contact point, respects capacity, assigns hours, rotates between contact points and labels score tiers — and extends it without inventing a parallel runtime.

Used when

When that solver is being extended, when someone needs the prioritisation and scheduling rules explained, or when a scheduled run is being operated.

Loads first

• The solver skill, whose reference documents are the authority on the business rules.
• The campaign-operation skill, when a run is being started or delivered.

Returns

• Which path it took — build, explain, or operate.
• The business rules relevant to the question: contact-point selection, scoring, capacity, hours, rotation and tiers.
• For a build: architecture notes by layer, and what must stay unchanged.
• For an explanation: the generated document, grounded in the reference rules.
• For a run: the environment, the input contract, the execution identifiers and the verification evidence.
• Any drift between the written rules and the code.