Enforcement jobs

An enforcement job is an asynchronous product API object. In the public sandbox it orchestrates synthetic platform fixtures so clients can test polling, partial success, retries, and failure UX.

bash

JOB_ID=$(curl -s -X POST "$PHOSRA_SANDBOX/children/$CHILD_ID/enforce" | jq -r .id)
curl -s "$PHOSRA_SANDBOX/enforcement/jobs/$JOB_ID/results"

Typical states include pending, running, partial, completed, and failed. Result counters such as rules_applied or rules_failed describe the sandbox simulation only.

There is no completion webhook for the job model. Poll the job and result endpoints, use bounded backoff, and make repeated reads idempotent.

A sandbox result does not prove that a third-party platform received, applied, or confirmed a policy. Production adapters, hosted routing, and a receipt rail remain roadmap.

The target design requires platform-specific evidence and a signed confirmation before an outcome can be treated as real. Define that evidence contract explicitly in a design-partner pilot.