# Working calendar, delegation and protocol checks

## Working-Time Notice Cutoff Plan

Find the latest notice cutoff using your supplied working calendar. Supply one explicit elapsed-minute clock, a closed calendar horizon and opaque source revision. Each working or blackout interval includes its start and excludes its end. Overlapping and adjacent windows are united before blackouts are subtracted, so each working minute is counted once. The input profile allows up to 128 working windows, 128 blackouts and 64 notices, within the shared 36,000-byte and 6,000-node input bounds. All minute values are nonnegative safe integers. Every interval endpoint, effective minute and planned notice minute must lie within the declared horizon. The report walks backward from each effective minute; zero required minutes returns that exact minute. Insufficient recorded coverage returns a null cutoff without extending the calendar. Planned working minutes count only the usable interval from the planned notice to the effective minute. This is elapsed working-time arithmetic only. Supply any holidays and clock adjustments explicitly; the report does not interpret time zones, daylight saving, contracts or law, and it does not send notices. W3C OWL-Time supplies general interval vocabulary; this calculation profile defines the half-open arithmetic. Use authorized, non-sensitive data. The report describes supplied records and does not change external systems.

[Request example](working-time-notice-cutoff-plan.request.example.json) · [Input schema](working-time-notice-cutoff-plan.input.schema.json) · [Result schema](working-time-notice-cutoff-plan.result.schema.json)

## Approval Delegation Chain Review

Review the recorded approval chain behind each decision. Supply an opaque source revision, half-open evidence window and supplied roots, delegations and decisions using one elapsed-minute clock. Root and delegation intervals include the start and exclude the end. Resource and action labels match exactly, including case; no wildcard or hierarchy is inferred. The input profile allows up to 32 roots, 96 delegation edges and 32 decisions, within the shared 36,000-byte and 6,000-node input bounds. All minute values are nonnegative safe integers. A root supports its own principal; mayDelegate permits the first hop. Each valid delegation supports its recipient, while mayRedelegate alone permits the next hop. Every root and edge must be active at the decision minute. The report chooses the shortest supporting chain, with source root order and then source edge order breaking ties. The profile checks scope and time at each decision only; it does not require an entire child interval to be contained in an ancestor interval. Unsupported decisions and times outside the evidence window receive no witness. Supplied roots are assertions, not independently verified authority. W3C PROV-O actedOnBehalfOf informs provenance terminology, not this authorization algorithm. This review does not certify legal authority or security controls, approve decisions or change permissions. Use authorized, non-sensitive data. The report describes supplied records and does not change external systems.

[Request example](approval-delegation-chain-review.request.example.json) · [Input schema](approval-delegation-chain-review.input.schema.json) · [Result schema](approval-delegation-chain-review.result.schema.json)

## WebSocket Opening Handshake Audit API

Review supplied HTTP/1.1 WebSocket version 13 opening-handshake fields. Preserve each relevant header occurrence and omit credentials and unrelated headers. Each combined token list supports at most 128 tokens of at most 128 characters each. The review checks method, required upgrade tokens, key shape, accept digest and optional subprotocol selection. A non-101 response is recorded as not upgraded rather than automatically malformed. Extension negotiation and other versions are explicitly outside the supported profile. This supplied-field review does not establish TLS security, origin authorization, nonce randomness, complete Host syntax, wire parsing, HTTP/2 support or a working connection. Use authorized, non-sensitive data. The report describes supplied records and does not change external systems.

[Request example](websocket-opening-handshake-audit.request.example.json) · [Input schema](websocket-opening-handshake-audit.input.schema.json) · [Result schema](websocket-opening-handshake-audit.result.schema.json)

## HTTP Content Coding Negotiation API

Evaluate supplied Accept-Encoding preferences against ordered available single-coding representations. Use null for an absent field and an empty string for a present empty field. Quality values use exact integer thousandths; explicit entries override wildcard preferences and zero excludes a coding. Include identity in available only when an unencoded representation is available. Encoded alternatives rank by quality and then supplied server order, with identity as fallback unless explicitly weighted. An explicitly listed identity preference competes by quality; the encoded alternative wins an equal-quality identity tie. This stated selection policy does not claim a unique RFC ranking. Duplicate normalized preference entries are rejected as ambiguous. The review does not compress data, verify codec support, inspect wire messages or support stacked Content-Encoding values. Use authorized, non-sensitive data. The report describes supplied records and does not change external systems.

[Request example](http-content-coding-negotiation.request.example.json) · [Input schema](http-content-coding-negotiation.input.schema.json) · [Result schema](http-content-coding-negotiation.result.schema.json)

One-time job. See the exact service price before checkout. Save your private JSON result within its 30-day access period.
Requests accept at most 36,000 UTF-8 input bytes. Send only authorized, non-sensitive records.

For a known hosted offer, read current checkout and wallet availability with `GET https://gatewayinformationgroup.com/api/catalog/v1/search?id=PRODUCT_ID`. Then use the input schema and request example above.

Use the existing [agent checkout guide](https://gatewayinformationgroup.com/developers) to prepare a quote, pay and retrieve the private result.