End-to-end integration workflows

Job/context → duplex images sharing sheetId/attempt → AIResult/modelVersion → deadline-bound decision → receipt ACK → execution event → observed location → reconciliation → QC. Illustrative REST contracts do not define the full control protocol; vendor validation is required for SDK/adapter and decision windows. Do not retry physical commands with unknown execution outcomes.

POST ingest-packages with manifest and SHA-256 → 202/jobId → GET job through validation/review → correct or quarantine → declare after QC → RecordID/version → preserve. Hash mismatch keeps a package outside the authoritative repository; job success does not replace declaration approval.

Versioned manifest → check QC and recipient authority → accepted/partial/correction → evidence → delivery → accepted/billable usage. Changed versions require reconsidering earlier decisions; disputed items are not automatically billable.

Approved billing decision → payment request → trusted provider confirmation → reconciliation → invoice request → issued/error/correction → retrieval. Duplicate callbacks do not create another invoice. After timeout, query status before creating another request.

User OIDC SSO differs from machine client credentials. Backends bind subject/audience/scope to membership, tenant/project and object permissions. Step-up or maker-checker follows approved configuration; denials are audited without logging tokens.