ores.scheduler.api

ores.scheduler.api is a header-only library defining the shared contract for the scheduler domain. It provides domain types for job definitions (cron expressions, action types), job instances (execution records), and job status values, together with JSON and table I/O via generated codecs, and the NATS protocol schemas consumed by ores.scheduler.core and any client managing scheduled jobs.

Everything the job-definition entity puts on the wire is generated from modeling/ores.scheduler.job_definition.org: the domain type and its JSON, table and table-I/O companions, the entity protocol, the change event, the generator, and the TypeScript projection. The hand-written types here are cron_expression, which is the entity's one custom column type and carries its own text form and stream operator, and the job-instance and job-status types behind the two operational views.

• Domain entity type definitions: job_definition.hpp (generated), job_instance.hpp, job_status.hpp, cron_expression.hpp.

• C++ headers for scheduler domain types with JSON and table I/O.
• The canonical entity protocol for job definitions, its change event, and the operation protocol for the job-instance and status views.

• include/ores.scheduler.api/domain/ — all domain entity headers.
• include/ores.scheduler.api/messaging/ — the generated entity protocol and the operation protocol.
• include/ores.scheduler.api/eventing/ — the generated change event.
• include/ores.scheduler.api/generators/ — the generated synthetic job-definition generator.

• fort — formatted table rendering.
• croncpp — cron expression validation and next-occurrence computation.

What the shared profile cannot know, declared here rather than hand-edited into the generated build file. Each block is spliced into its generated file after the profile's baseline.

• ores.scheduler — component group overview.
• ores.scheduler.core — business logic, scheduling loop, and NATS handlers.
• ores.scheduler Messaging Reference — full NATS subject and message catalogue.

The suites link what the profile cannot know about.

target_link_libraries(${lib_target_name}
    PUBLIC
        ores.platform.lib
    PRIVATE
        ores.utility.lib
        faker-cxx::faker-cxx
        libfort::fort)

target_link_libraries(${lib_target_name} PRIVATE ores.codec.pch)

target_link_libraries(${tests_target_name}
    PRIVATE
        ores.scheduler.api.lib
        ores.telemetry.core.lib
        ores.utility.lib
        ores.testing.lib
        faker-cxx::faker-cxx
        Catch2::Catch2
        Threads::Threads)