maha research · governed federation

Slurm Job — Method

Slurm Job — Method is implemented as a source-bounded method guide. The inspected material supports only this scope: Normalizes a bounded allowlist of caller-supplied SLURM metadata without executing a scheduler. sbatch submits a batch script, assigns a job identifier, applies directive and option precedence, and makes named SLURM_* metadata available to the job environment. The adapter normalizes a caller-supplied, allowlisted subset of SLURM metadata into a deterministic witness field set. The page retains this limit: Metadata capture does not prove workload correctness, scheduler truth, or reproducibility. Successful submission is not successful execution, scientific validity, resource availability, or proof that an output came from the named job. The adapter does not submit a job, contact Slurm, capture arbitrary environment values, prove scheduler identity, prove job completion, or establish output correctness.

Active canonical release · fedrelease_fec6b99b5d20d5bde7dca9b9134d3f26 · exact revision sha256:77e4d7b3793e75a098be4c7fec09e3df8db124aab2bff63623a5462750d42ac3

answer

Direct answer

Slurm Job — Method is implemented as a source-bounded method guide. The inspected material supports only this scope: Normalizes a bounded allowlist of caller-supplied SLURM metadata without executing a scheduler. sbatch submits a batch script, assigns a job identifier, applies directive and option precedence, and makes named SLURM_* metadata available to the job environment. The adapter normalizes a caller-supplied, allowlisted subset of SLURM metadata into a deterministic witness field set. The page retains this limit: Metadata capture does not prove workload correctness, scheduler truth, or reproducibility. Successful submission is not successful execution, scientific validity, resource availability, or proof that an output came from the named job. The adapter does not submit a job, contact Slurm, capture arbitrary environment values, prove scheduler identity, prove job completion, or establish output correctness.

method

Answer contract

Apply the method lens only to the exact inspected source scope; do not infer authority from adjacent topics.

evidence

Evidence and exact locators

t23-slurm-contract — packages/maha-witness/src/maha_witness/adapters.py — slurm_metadata. Supports: Normalizes a bounded allowlist of caller-supplied SLURM metadata without executing a scheduler.

slurm-sbatch-t9 — https://slurm.schedmd.com/sbatch.html — current documentation inspected 2026-09-06; DESCRIPTION; #SBATCH directives; input environment variables; output environment variables; RETURN VALUE. Supports: sbatch submits a batch script, assigns a job identifier, applies directive and option precedence, and makes named SLURM_* metadata available to the job environment.

local-slurm-witness-adapter-t9 — repo:packages/maha-witness/src/maha_witness/adapters.py — repository source inspected 2026-09-06; slurm_metadata; allowlisted SLURM_ARRAY_JOB_ID, SLURM_ARRAY_TASK_ID, SLURM_CLUSTER_NAME, SLURM_CPUS_PER_TASK, SLURM_JOB_ID, SLURM_JOB_NAME, SLURM_NNODES and SLURM_JOB_PARTITION. Supports: The adapter normalizes a caller-supplied, allowlisted subset of SLURM metadata into a deterministic witness field set.

limitations

What the evidence does not establish

Metadata capture does not prove workload correctness, scheduler truth, or reproducibility.

Successful submission is not successful execution, scientific validity, resource availability, or proof that an output came from the named job.

The adapter does not submit a job, contact Slurm, capture arbitrary environment values, prove scheduler identity, prove job completion, or establish output correctness.

rights

Rights and reuse

project-owned-reference-only

Publicly accessible source; link and bounded paraphrase only. No source text is redistributed.

Maha-controlled repository source; headings, symbols, and file identity only. No credential, customer value, runtime payload, private input, or receipt body is retained.

relationships

Dependencies and related concepts

applies-to: urn:maha:concept:evidence:slurm-job

governed-by: urn:maha:concept:governance

evidence-for: urn:maha:concept:evidence

required-by-specification

Source or implementation

This source or implementation section is constrained to the same inspected scope: Normalizes a bounded allowlist of caller-supplied SLURM metadata without executing a scheduler. sbatch submits a batch script, assigns a job identifier, applies directive and option precedence, and makes named SLURM_* metadata available to the job environment. The adapter normalizes a caller-supplied, allowlisted subset of SLURM metadata into a deterministic witness field set.

It must preserve the recorded boundary: Metadata capture does not prove workload correctness, scheduler truth, or reproducibility. Successful submission is not successful execution, scientific validity, resource availability, or proof that an output came from the named job. The adapter does not submit a job, contact Slurm, capture arbitrary environment values, prove scheduler identity, prove job completion, or establish output correctness.

required-by-specification

Method

This method section is constrained to the same inspected scope: Normalizes a bounded allowlist of caller-supplied SLURM metadata without executing a scheduler. sbatch submits a batch script, assigns a job identifier, applies directive and option precedence, and makes named SLURM_* metadata available to the job environment. The adapter normalizes a caller-supplied, allowlisted subset of SLURM metadata into a deterministic witness field set.

It must preserve the recorded boundary: Metadata capture does not prove workload correctness, scheduler truth, or reproducibility. Successful submission is not successful execution, scientific validity, resource availability, or proof that an output came from the named job. The adapter does not submit a job, contact Slurm, capture arbitrary environment values, prove scheduler identity, prove job completion, or establish output correctness.

required-by-specification

Limits and uncertainty

This limits and uncertainty section is constrained to the same inspected scope: Normalizes a bounded allowlist of caller-supplied SLURM metadata without executing a scheduler. sbatch submits a batch script, assigns a job identifier, applies directive and option precedence, and makes named SLURM_* metadata available to the job environment. The adapter normalizes a caller-supplied, allowlisted subset of SLURM metadata into a deterministic witness field set.

It must preserve the recorded boundary: Metadata capture does not prove workload correctness, scheduler truth, or reproducibility. Successful submission is not successful execution, scientific validity, resource availability, or proof that an output came from the named job. The adapter does not submit a job, contact Slurm, capture arbitrary environment values, prove scheduler identity, prove job completion, or establish output correctness.

required-by-specification

Dependencies

This dependencies section is constrained to the same inspected scope: Normalizes a bounded allowlist of caller-supplied SLURM metadata without executing a scheduler. sbatch submits a batch script, assigns a job identifier, applies directive and option precedence, and makes named SLURM_* metadata available to the job environment. The adapter normalizes a caller-supplied, allowlisted subset of SLURM metadata into a deterministic witness field set.

It must preserve the recorded boundary: Metadata capture does not prove workload correctness, scheduler truth, or reproducibility. Successful submission is not successful execution, scientific validity, resource availability, or proof that an output came from the named job. The adapter does not submit a job, contact Slurm, capture arbitrary environment values, prove scheduler identity, prove job completion, or establish output correctness.

bounded answers

Questions this page can answer

What is established?

Slurm Job — Method is implemented as a source-bounded method guide. The inspected material supports only this scope: Normalizes a bounded allowlist of caller-supplied SLURM metadata without executing a scheduler. sbatch submits a batch script, assigns a job identifier, applies directive and option precedence, and makes named SLURM_* metadata available to the job environment. The adapter normalizes a caller-supplied, allowlisted subset of SLURM metadata into a deterministic witness field set. The page retains this limit: Metadata capture does not prove workload correctness, scheduler truth, or reproducibility. Successful submission is not successful execution, scientific validity, resource availability, or proof that an output came from the named job. The adapter does not submit a job, contact Slurm, capture arbitrary environment values, prove scheduler identity, prove job completion, or establish output correctness.

Which exact source establishes it?

t23-slurm-contract, packages/maha-witness/src/maha_witness/adapters.py — slurm_metadata; slurm-sbatch-t9, https://slurm.schedmd.com/sbatch.html — current documentation inspected 2026-09-06; DESCRIPTION; #SBATCH directives; input environment variables; output environment variables; RETURN VALUE; local-slurm-witness-adapter-t9, repo:packages/maha-witness/src/maha_witness/adapters.py — repository source inspected 2026-09-06; slurm_metadata; allowlisted SLURM_ARRAY_JOB_ID, SLURM_ARRAY_TASK_ID, SLURM_CLUSTER_NAME, SLURM_CPUS_PER_TASK, SLURM_JOB_ID, SLURM_JOB_NAME, SLURM_NNODES and SLURM_JOB_PARTITION

What dependency remains separate?

Metadata capture does not prove workload correctness, scheduler truth, or reproducibility. Successful submission is not successful execution, scientific validity, resource availability, or proof that an output came from the named job. The adapter does not submit a job, contact Slurm, capture arbitrary environment values, prove scheduler identity, prove job completion, or establish output correctness.

What uncertainty remains?

applies-to: urn:maha:concept:evidence:slurm-job governed-by: urn:maha:concept:governance evidence-for: urn:maha:concept:evidence

What must not be inferred?

A source, locator, rights, scope, boundary, dependency, implementation, or release change requires a new exact-revision review.