TruVelocity™ for AI TEVV · Customer fitment

TruVelocity™ for AI TEVV fitment: Intelligent Core Copilot (L&AH)

17 Nov 2026 · Assessment of the customer's deck Intelligent Core Copilot · Immersive AI Kit for Innominds (11 slides) against what TruVelocity™ does today.

Jump to: 1 Their product2 Fit, concept by concept3 Their bar, our test types4 Pilot5 What we need6 Gaps7 Questions8 Next steps

Strong fit.The customer's Copilot is an AI layer that changes insurance records under permissions and human confirmation, through multi-step agents. That is the risk TruVelocity™ was built to test: it compares what an agent says it did with independent evidence of what it actually did. The one thing that decides how much applies is access: an API to drive the Copilot, a test environment with resettable data, and read-only evidence of its tool calls and data (section 5).

1Their product, in one minute

"L&AH Copilot": one conversational layer across the life, accident and health insurance lifecycle, from RFP and underwriting through enrollment, servicing, billing and claims.

52inquiry tools: find, understand, trace
28governed actions: change, create, submit
25specialized agents in five families
3operating modes: answer only, propose for approval, execute under permission

"Recognizing the sentence is the easy part. Resolving the subject, validating against the group's configuration, warning about consequence, and refusing the rest, is the product." (customer deck, slide 11)

That sentence is TruVelocity™'s premise: judge what the agent did, not only what it said.

2Fit, concept by concept

Their deckWhat TruVelocity™ does with it
Three layers: Inquire, Act, Orchestrate fits TruVelocity™'s three test profiles: conversational (chat inquiry), task (one bounded action) and workflow (multi-step and multi-agent), each already proven on a reference agent of that kind.
"Every answer traces back to its record" fits Answers are checked against independent evidence: the facts the reply must state, the tools actually called and grounding. SE-01GF-01GF-05
28 governed actions: permissioned, human-confirmed, audited fits The core of TruVelocity™: it reads the affected records before and after each turn (read-only) and catches unrequested writes, "done" with nothing written, actions without approval and actions outside a role's rights. SE-02SE-03SE-04SS-03AT-05
Three operating modes fits One catalog, checked per mode: answer only expects no writes at all; propose for approval expects an approval prompt, and nothing written when the user declines; execute under permission expects exactly the right records changed, and nothing else.
"What Copilot is not": never adjudicate, approve, pay or exceed authority fits Negative tests at critical severity. TruVelocity™ has caught this class of defect in our reference claims agent, which approved a payout on its own.
Proof story: a bad effective date refused, the rule explained fits Precondition enforcement, plus the database check that proves the refusal really left the record untouched. TT-06SE-04
80 prompt variants per endorsement fits TruVelocity™'s wording model: every request asked many ways, each case scored PASS / FLAKY / FAIL with a 95% confidence range, and reliability over repeated tries (pass^k). IU-06RC-01RC-02
Agents triggered by inbound email or scanned PDF fits, needs data The task profile with queue events (Service Bus, Kafka) and attachments; extracted values are checked against expected ones, which needs reference documents with known correct values.
"Route exceptions to a person with the context attached" fits Escalation and handoff, agent-to-agent handoffs (recorded by TruVelocity™'s agent-to-agent tap) and errors passing down a chain. AT-04AT-08SS-09
Audit trail and conversation logs fits Auditability CP-06; their audit log also becomes one more independent evidence source.
Multi-turn context ("set member context, then…") partly Multi-turn conversations are supported today; long-conversation stability CQ-05 and memory correctness AT-07 are not validated yet (see section 6).

3Their quality bar is our test catalogue

Slide 11 lists six things "understood the request" must mean. Each maps to test types TruVelocity™ already measures:

Their bar (slide 11)ExampleTruVelocity™ test types
1 Resolve the subject: never guess"Change class for John Doe."IU-02 disambiguation ES-02 slot elicitation
2 Map words to values"Promoted to management", "next quarter"ES-01 slot extraction against expected values
3 Validate the configuration"Move him to Class B."TT-06 precondition enforcement
4 Split the request"His ID and his name both need fixing."IU-03 multi-intent decomposition
5 Warn before submit"To a class with no life cover."CP-03 disclosure SE-02 approval vs state
6 Refuse or challenge"Move everyone in Warehouse."IU-04 out of scope AT-05 scope boundary SS-03 privilege abuse

TruVelocity™ measures every run against all 71 test types of the Intent-Based Testing Catalogue and reports gaps instead of hiding them.

4Proposed pilot, built on their own material

  1. Servicing endorsements (class, employee ID, hours worked, location). They already wrote 80 prompt variants, and proof story 3 gives the expected behaviour. Turn them into a catalog and run it in all three modes: the fastest route to a result they will recognise.
  2. Claims inquiry: "Why is this claim pended and what is missing?", grounded against the claim record.
  3. One agent end to end: the Member Profile Changes agent, including approvals and routing exceptions to a person.
  4. Negative tests across the board: never adjudicate, never pay, never exceed authority limits, no bulk changes.
Operating modeWhat TruVelocity™ expectsWhat would be a defect
1 Answer onlyCorrect, grounded answer; no record changesAny write; an answer the record does not support
2 Propose for approvalThe prepared change and its evidence, then an approval promptA write before approval; a write after the user declines; approving the wrong change
3 Execute under permissionExactly the requested records changed, with reason code, effective date and audit entryExtra or missing changes; "done" with nothing written; action beyond authority limits

The output is the same as for our own pilots: an execution report per run, a release gate, trends across builds and the evidence portfolio.

5What we need from the customer

6Gaps and risks, stated openly

7Questions to put to the customer

  1. How is the Copilot accessed: API, WebSocket, or only the web UI?
  2. Are the inquiry tools and governed actions exposed through MCP, REST or internal SDK calls? Do they emit OpenTelemetry traces?
  3. Is there a non-production environment with resettable data, and can we have a read-only data path into it?
  4. Can they share the 80 prompt variants and the expected outcome of each?
  5. Which operating mode is each environment in, and what are its authority limits and approval rules?

8Next steps

  1. Share this assessment and the questions in section 7 with the customer.
  2. On answers, agree the pilot scope (section 4) and environment access (section 5).
  3. Draft the starter catalog for the four endorsements on slide 11 from their prompt variants; run it once access is in place.
  4. Present the first execution report, release gate and coverage against the 71 test types.

Internal to Innominds. This page summarises a customer's deck; share outside Innominds only as agreed with the customer.