Bounded answer
For SLURM job agent, decide entitlement to a scheduled HPC job from the active principal, exact offer or resource, granted scope, expiry, revocation state, and remaining quota. Discovery, prior access, or possession of an identifier is never sufficient.
Input contract
What must be fixed first
Authenticated principal
Exact offer or resource identifier
Active grant and policy version
Expiry, revocation, and quota state
Procedure
Work the decision in order
- 1
Resolve identity without trusting caller-supplied ownership.
- 2
Load the exact grant and current policy.
- 3
Match resource, operation, audience, and endpoint.
- 4
Check time, revocation, and quota atomically.
- 5
Return a bounded decision without exposing credential material.
Expected outputs
- Entitled or refused state
- Stable refusal code
- Decision fingerprint and policy version
Refuse when
- A nearby offer or predecessor revision is substituted.
- Identity and grant belong to different principals.
- Policy or grant cannot be read at decision time.
- Scheduler acceptance is not evidence that the intended binary or inputs executed.
Questions this guide answers
What is the minimum safe entitlement decision for a SLURM job agent?
For SLURM job agent, decide entitlement to a scheduled HPC job from the active principal, exact offer or resource, granted scope, expiry, revocation state, and remaining quota. Discovery, prior access, or possession of an identifier is never sufficient.
Which identity fields must remain bound for a SLURM job agent?
Preserve cluster, allocation, job, executable, environment, inputs, and receipt; refuse the operation when any edge is missing or belongs to another lifecycle.
What should happen on an exact replay?
Return the original bounded decision or result without consuming quota, delivering, or acknowledging a second time.
What role does the linked book play?
It contributes a conceptual framing for boundaries, resilience, or governance. It is not evidence that the technical control exists or works.
What does this guide not establish about a SLURM job agent?
Scheduler acceptance is not evidence that the intended binary or inputs executed.
Limits
- Scheduler acceptance is not evidence that the intended binary or inputs executed.
- The linked book supplies a conceptual lens only; the operational contract and implementation remain the authority for machine behavior.
- This guide does not authorize production mutation, payment, deployment, or access to a private evidence corpus.