Go-live checklist

Last updated 2 September 2026.

What we will ask about before issuing a production key.

1. The link

A stable subject that survives renames; never padded, never empty.
A fixed return origin per deployment, registered exactly; a start URL at a path you will keep.
Redeem from a route handler with an immediate redirect; subject sent on every redeem; no retries.
The link cached under your service id; a page never blocks on Trivela.
Status called on render; linked: false clears the cache; a 400 is shown as unavailable, never as unlinked.
The feature disabled cleanly — no broken button — when the key is absent.

Only fields you registered to send, bounds checked locally, failures sent as null.
Your own value, never a value you read from Trivela.
Only from pages the player is on; pushed in the background when they change something.
If a value changes while the player is away: a daily bulk feed, chunked at 500.

One column per field you read, separate from the player’s own; overlay shown over it, none clears it, missing leaves it alone.
Your own field list walked, unknown entries dropped, never a failed call over one bad row.
Every Trivela-sourced column cleared when the link ends.
If you take a webhook: constant-time auth that fails closed, 202 before work, no path from a ping to an unlink.

Questions, registration requests and corrections to these docs go through the GOALS Pro League community, which is where Trivela is run from.