US Brand Signal SLA Checker

Classify a buyer's schedule rows against an explicit UTC timestamp. This Actor is useful for agent workflows that need a small, deterministic answer to: which items met their stated due time, which missed it, and which are still open?

The Actor does not fetch a system clock or an external source. asOf is supplied by the buyer, so the same input always gives the same result. itemId is an opaque identifier supplied by the buyer; it is not resolved to a person, company, account, or real-world identity.

What you send

Send schemaVersion, an explicit asOf UTC timestamp, and 1-100 rows:

{
  "schemaVersion": "1.0",
  "asOf": "2026-08-05T12:00:00Z",
  "rows": [
    {"itemId": "case-001", "openedAt": "2026-08-05T08:00:00Z", "dueAt": "2026-08-05T10:00:00Z", "resolvedAt": "2026-08-05T09:30:00Z"},
    {"itemId": "case-002", "openedAt": "2026-08-05T08:00:00Z", "dueAt": "2026-08-05T09:00:00Z", "resolvedAt": null}
  ]
}

All timestamps must be strict YYYY-MM-DDTHH:mm:ssZ UTC values with real Gregorian dates. Offset timestamps, local times, fractional seconds, leap seconds, invalid dates, and non-canonical spellings are rejected. Each row must satisfy openedAt <= dueAt, openedAt <= asOf, and, when closed, openedAt <= resolvedAt <= asOf.

What you get

The Dataset receives one report row. Rows and IDs are sorted by ASCII itemId. Each row contains:

• classification: on_time, late, open_overdue, or open_within_sla;
• openedToDueSeconds: whole seconds from opening to due time;
• openedToResolvedSeconds: whole seconds from opening to resolution, or opening to the supplied asOf for an open row;
• overdueSeconds: zero unless a closed row resolved after due time or an open row is evaluated at/after due time.

Boundary rules are explicit: resolvedAt <= dueAt is on_time; resolvedAt > dueAt is late; resolvedAt == null and asOf >= dueAt is open_overdue; resolvedAt == null and asOf < dueAt is open_within_sla. A row resolved exactly at its due timestamp is therefore on time, while an unresolved row at its due timestamp is overdue.

The report also returns reconciled counts, sorted IDs, and SHA-256 digests for the canonical input, classified rows, counts, and complete result. JSON Schema checks shape; runtime checks enforce temporal relationships and digest equality.

Run it

1. Open Try for free in the Actor Console.
2. Paste the exact JSON shape shown in the Input section.
3. Start the run and read the one report row from the Dataset.
4. Read the truthful terminal delivery receipt from OUTPUT.

The runnable prefill is in examples/input.json and public-task.json. This is an inline-only Actor: it accepts no Dataset input.

Pricing

Pay per event: $0.005 per run start plus $0.010 per delivered result on the FREE tier. The result event is emitted only after one confirmed Dataset write. The buyer cap must cover both charges.

Tier	Discount	Start	Delivered result
FREE	0%	$0.00500	$0.01000
BRONZE	5%	$0.00475	$0.00950
SILVER	10%	$0.00450	$0.00900
GOLD	15%	$0.00425	$0.00850
PLATINUM	18%	$0.00410	$0.00820
DIAMOND	20%	$0.00400	$0.00800

Invalid input, insufficient cap, uncertain delivery, and an uncharged or multiply charged result are not successful results. The Actor never retries an uncertain paid Dataset push.

Freshness, limits, and safety

• Freshness is buyer-controlled: change asOf or the supplied rows and run again. The Actor never reads the current clock.
• Maximum input is 100 rows; itemId is 1-64 characters from the restricted printable ASCII ID set [A-Za-z0-9._:-].
• Input and report are bounded below 64 KiB. Oversized results fail before any paid Dataset push.
• No network, proxy, BYOK key, LLM, state, child Actor, or Dataset input is used.
• The report is an analysis of buyer-supplied schedule values, not proof that a deadline or identity is true in an external system.

Related public Actors

These Actors can precede or follow this checker in a machine-to-machine workflow. This Actor does not call them.

Actor	Use it for
US Brand Signal Metrics Aggregator	Aggregate signal rows before checking operational deadlines.
US Brand Action Queue	Turn late or overdue IDs into bounded next-action rows.
US Brand Signal Brief Composer	Summarize the resulting SLA counts for an agent or operator.
US Brand Evidence Snapshot Diff	Compare two buyer-supplied snapshots before or after a schedule review.

FAQ

Does this Actor check a live CRM or current time? No. You provide every timestamp, including asOf.

What happens at the due-time boundary? A resolved row at exactly dueAt is on_time; an unresolved row at exactly dueAt is open_overdue.

Can I submit local time or a timezone offset? No. Convert it to canonical UTC with Z before sending.

Can I use real names? The contract accepts opaque IDs only and does not identify people, companies, or accounts.

What happens if delivery is uncertain? The terminal receipt records a non-success state and the Actor does not issue a second Dataset write.

Built by zinin.