Scheduler Manifest
Owner: Forge HPC maintainers.
Status: Implemented (Capability 2C).
Plane: Domain.
Purpose: Define the universal scheduler contract and adapter boundary — the abstract shape every scheduler must satisfy to be observed through Forge HPC, expressed exclusively in domain vocabulary.
Contents: scheduler identity, capabilities, version, health, manifest, capability
and version negotiation, observation shapes (windows, cursors, snapshots,
incremental updates, event kinds), the abstract SchedulerContract, mechanical
compliance verification, and the adapter boundary interfaces.
Dependencies: the Forge HPC domain package and the Python standard library
only. No Forge Core runtime imports, no external packages, no instance
knowledge, no scheduler implementation, no runtime execution.
Boundary: contains no concrete scheduler, no command vocabulary, no source formats, no environment variables, no scheduler configuration, and no transport (SSH, REST, files, sockets, databases, message queues). Those belong to adapters and instances.