Capabilities and limits

This guide lists what you can do with Kirnova, what you cannot, and where the limits are. Read What Kirnova delivers first for the assessments and terms used here.

Each capability is in one of three states:

Two delivery surfaces are referred to throughout:

• Embedded frame: the assessment runs in a frame you place on your page. Kirnova renders the questions and you own everything around them.
• Machine-driven API: your servers call Kirnova directly and you build every screen. Kirnova never touches the respondent's browser.

Delivering an assessment#

Resuming a sitting#

If the frame reloads with the same launch link within 5 minutes, the person returns to the same sitting with the same questions and their answers intact. After 5 minutes the link is refused as expired. Request a fresh launch link for the same person: they resume the same sitting with the answers already given.

A fresh link carries a new session identifier, and the completion and result arrive under the newest one. Store every identifier you request for a person and reconcile on the one that completes.

Assessment availability#

Kirnova sets which assessments your account can run. If you request one your account does not hold, you receive a named refusal. Kirnova never substitutes a different assessment. An account with no assessments configured cannot start any sitting.

• TIGER Light is closed to partners by rule, not by build status. Every assessment a third party puts in front of a person is TIGER Core or TIGER Student.
• Kirnova Calling is licensed for career counselling, planning and exploration and must not inform an employment decision.
• TIGER Core and TIGER Student can inform an employment decision. They cannot take one.
• This matrix is the complete list. No other assessment is available to partners.

Receiving results#

• Kirnova Calling returns an ordering of interest themes and the closest occupations, never a score for each theme. It sends no prepared document and no browser signal.
• Kirnova ORVIS returns an order of eight kinds of work, never a number for any one of them, with a sentence saying an interests reading is not a signal for selecting between people. Show that sentence beside the result.
• Kirnova Cognitive returns a score out of 100 with its range and a word. It never returns a comparison with other people. It sends no prepared document and no browser signal.
• Kirnova DISC and HEXACO return results on every route, including a prepared document, and send no browser signal. Every score carries its range. Your access window for either result is 365 days, and the result states the date.

Route details#

• Signed message. The completion message is sent when the result is stored. If your endpoint does not respond, Kirnova retries after 1 minute, 5 minutes, 30 minutes and 2 hours, up to 5 attempts in total. The first retry is sent promptly. Later retries are sent when your account next makes a request to the API, with a daily sweep as a fallback, so a later retry can wait until the next day. Do not build delivery timing into your own commitments. A message can arrive more than once, so handle repeats by session and event.
• Other messages. You can subscribe to a message when a sitting is recorded as abandoned, which today happens only when your servers close a machine-driven sitting, and a message when a prepared document is ready. The completion message carries the result, so build on it.
• Single result. Available for as long as the result exists. Your access to a result received through the integration does not expire on a timer.
• Listing. A period is required; there is no "everything" request. It returns live sittings by default. The optional environment setting accepts live or practice; any other value is refused.
• Document. For a TIGER sitting, the document is prepared on your first request, so the document-ready message follows that request. The document carries Kirnova's presentation.
• Browser messages. During a TIGER sitting in the frame, the browser receives a height message whenever content height changes, and at the end a completion signal carrying the session identifier only (sent in two forms; act on one). There is no progress or abandonment signal. A Kirnova Calling sitting posts nothing to the browser. Treat browser messages as a cue to update your interface, not as a record of completion. The record is the signed message or the result you request.

Result contents#

• A reading for each of the five dimensions: a whole number, its range and a one-word confidence reading (High, Moderate or Low).
• The kinds of work the readings point to.
• One dimension identified as the strongest within the person, and two worth a closer look, each with a framing line explaining that this ordering is within one person.
• For TIGER Core and TIGER Student, two further short readings where they apply.
• For TIGER Student, an interests section.
• A quality note when the sitting is not fit to inform a decision.

Kirnova does not send formulas, weightings, inference rules, probability figures, standard errors or anything that would allow the engine to be reconstructed. There are no profile names, archetypes or type labels.

Appearance#

Kirnova adjusts your primary colour so it stays readable. It changes lightness until the colour meets a contrast ratio of 3:1 for bars, fills and edges, and 4.5:1 for anything a person reads. The hue is preserved. Focus outlines and the high, moderate and low colours are never re-coloured.

On TIGER Core and TIGER Student, the surrounding page, your communications and your own presentation of the result are yours. On the machine-driven API every screen is yours. The sitting itself, the wording of every question, the quality note, the framing lines and the prepared document use Kirnova's presentation. The prepared document carries no partner branding.

A sitting in your frame can never navigate a respondent to a Kirnova sign-in page.

Identity, accounts and access#

Every sitting creates an identified Kirnova account in the person's name. The person keeps their result permanently, independent of your access.

Limits#

• Machine-driven API: the daily sitting cap applies. An Enterprise account has no daily cap.
• Embedded frame: there is no daily cap. Requesting a launch link counts against your per-minute allowance, so request rate is the limit.
• When you reach a limit, the request is refused with a "too many requests" response that states how long to wait. Sittings in progress are not interrupted and no result is lost. Every response carries your current allowance, the amount remaining and when it resets.
• Raising a limit. Move tier, or agree a negotiated number with Kirnova. A negotiated per-minute number governs your requests, and a negotiated daily number governs how many sittings your servers can start.

Where to test#

Test on Kirnova staging at https://stage.kirnova.com, which serves the API, the embedded frame and the application. Kirnova issues a staging key.

• Staging data is test data and never reaches production.
• Keys do not cross environments. A staging key is refused on production and a production key is refused on staging. A staging key can look like a production key (bi_live_sk_...), so use the address to tell where you are.
• The same tier limits apply on staging.
• A staging sitting still creates an account for the email address you give, so use addresses your team controls.

Production is https://api.kirnova.com for the API and https://embed.kirnova.com for the frame.

Maintenance#

A maintenance switch can stop new sittings from starting. A launch-link request, a frame load and a sitting created from your servers each return "temporarily unavailable". Existing results, prepared documents, listings, signed messages and answers to sittings already under way keep working. Treat this response as retryable.

Requirements for your integration#

These requirements govern how your interface presents what Kirnova sends.

TIGER informs; people decide. A result can inform hiring, promotion, retention, pay, performance, development, management, disciplinary action and termination. It must never be the thing that decides. Your organisation weighs other information, applies judgement and complies with employment law.

Not available#

Not built#

• Team, comparison and organisation views. Nothing reads a group, compares two people or aggregates the people you have assessed.
• Self-service purchase. There is no checkout. Sittings are arranged with Kirnova.
• Driving Kirnova's account actions from your own software. Inviting a person to sit TIGER Core or TIGER Student, viewing candidates attributed to your account and requesting access back to a result you can no longer open are signed-in actions in Kirnova. They cannot be triggered from your software. The exception is jobs: an approved organisation can invite a person to apply to one of its jobs through the jobs interface, and every such invitation must state that the person is 18 or over. This invites a person to apply, not to sit an assessment. The cost of a sitting is taken when an invitation is created.
• Opening results in the Kirnova portal. The commissioning account and team hiring managers and administrators can open results. A viewer cannot. The person's agreement and the access window apply to all of them.
• A prepared document for Kirnova Calling, and a browser signal from Calling, DISC or HEXACO sittings.
• Progress or abandonment signals from the frame during a TIGER sitting.
• Partner branding on TIGER Core, TIGER Student, Calling, DISC or HEXACO beyond light or dark and your primary colour, and none on the prepared document.
• A client library in any language.
• Self-service provisioning of an account.

Not permitted#

These are rules and do not change by contract.

• A partner cannot put TIGER Light in front of anyone, on any surface.
• Assessments outside the availability matrix are not available to partners.
• Kirnova Calling cannot inform an employment decision.
• The product has no pass mark and no automated rejection, and no setting creates one.
• No anonymous assessment, and no sitting for anyone under 18.
• Kirnova does not send formulas, weightings, inference rules, probability figures or standard errors.
• Interests are never a hiring signal, even where a hiring buyer can access them.

Security#

Kirnova holds no security certification and claims none.

• Each partner's data is separated in the database itself. A request for something that is not yours returns "not found".
• A launch link is valid for 5 minutes and admits one sitting. Presenting it again returns the person to the same sitting.
• A respondent's sitting window is 47 minutes and is not renewed. On the machine-driven API the window runs from sitting creation. In a frame it runs from when the launch link would have expired, so a link opened immediately gives the respondent a little under 52 minutes.
• Every message Kirnova sends to your server is signed.
• Your key is stored only as a fingerprint and cannot be recovered. A lost key is replaced, and you can revoke a key immediately.
• Allowed sites are an account setting that applies to every key and guards both the launch-link request and the loading of the frame. If no sites are named, nothing is restricted. If sites are named, a request that does not state which site it came from is refused, including an ordinary request from your own servers. The machine-driven API is not covered by this setting.
• Answers are scored on Kirnova's servers. You never send a score, and a result that cannot be re-derived from its answers is refused.
• Every completed sitting retains the person's individual answers so it can be reproduced and re-scored under its own version. Tell candidates this.
• There is no anonymous respondent on any route.

Requests#

Send requests to team@kirnova.com.