Weekly Signal Archive

FOUR SIGNALS FROM THE NOTEBOOK

Short analyses on insurance, AI and enterprise systems—each with the operating question behind the headline.

Paid weekly editions and working notes: https://robtyrie.substack.com

========================================

SIGNAL NOTE • SEPTEMBER 29, 2026

Small Models and Decision APIs

Not every AI service needs to hold a conversation.

Generative models are useful when the work involves language, exploration or explanation. Many operational questions are narrower: Is this submission complete? Does it fit appetite? Which queue should receive it? Is confidence high enough to proceed? A smaller decision service can answer quickly, cheaply and in a typed form that software knows how to use.

Specialization does not automatically make the answer correct. A probability still depends on the question, evidence, calibration and population on which it was tested. But the constrained output can make evaluation and integration clearer than asking a large model to write a persuasive paragraph.

SEPARATE FOUR JOBS

Design the workflow as four components:

1. extract facts from messy material;

2. make a bounded decision or score;

3. explain the evidence and uncertainty;

4. send consequential or ambiguous cases to a person.

Use the right model or rule for each component. Test them independently. This reduces cost, but more importantly it makes failure easier to locate.

The future enterprise stack will not contain one intelligence. It will contain several forms of intelligence connected by explicit responsibilities.

Original LinkedIn note: https://www.linkedin.com/feed/update/urn:li:activity:7510852899648741377/

========================================

SIGNAL NOTE • SEPTEMBER 5, 2026

AI and Canada's Life-Insurance Coverage Gap

A large insurance coverage gap makes an attractive AI headline. It also hides several different problems inside one number.

People can be underinsured because they do not understand the risk, cannot afford the product, distrust the seller, find the process difficult or have been offered coverage that does not fit their lives. AI may help with some of those conditions. It can explain options, identify likely gaps, reduce application friction and help an advisor prepare for a more useful conversation. It cannot make an unaffordable product affordable or repair trust through a better chatbot.

There is also a danger in treating the gap only as unclaimed revenue. Insurance exists to create resilience. A recommendation system should be judged by whether a person ends up with suitable, understood and sustainable coverage—not merely whether a policy was sold.

FOLLOW THE GAP TO ITS CAUSE

Choose one customer segment and separate the coverage gap into awareness, affordability, eligibility, product fit, trust and process friction. Apply AI only where the obstacle is informational or operational. Track completed coverage, customer understanding, early lapse and complaints—not just leads and conversion.

The useful signal is not that AI can close 42 percent of anything. It is that we can now investigate and address specific causes at a much more personal scale. The design must remain as careful as the promise.

Original LinkedIn note: https://www.linkedin.com/feed/update/urn:li:activity:7502021397469085696/

========================================

SIGNAL NOTE • JUNE 12, 2026

Straight-Through E&S Underwriting

Straight-through underwriting is often described as if autonomy were a switch: the person is either in the loop or out of it. In practice, autonomy should be a ladder.

An agent can begin by assembling evidence. Then it can recommend appetite, identify missing information, produce a quote-ready package and suggest terms. Only after the carrier understands performance by segment should it consider allowing narrowly defined cases to proceed further without intervention.

E&S is an important test because speed matters and the work is heterogeneous. It is also where the exception can be the whole point. A system that performs the majority of analysis may still need a person to recognize the one exposure that changes the decision.

DEFINE THE AUTONOMY LADDER

Set explicit levels for each class of business:

1. summarize only;

2. prepare and route;

3. recommend with evidence;

4. produce quote-ready output;

5. proceed within a tightly bounded authority.

Name the evidence required to move up a level, the conditions that force a step down and the underwriter accountable for the design. Audit by class, broker, exposure and confidence band.

“Straight through” should describe a governed path, not the absence of people.

Original LinkedIn note: https://www.linkedin.com/feed/update/urn:li:activity:7471289031788609536/

========================================

SIGNAL NOTE • JUNE 11, 2026

Frontier Models Inside Regulated Core Systems

A large technology provider integrating a frontier model into systems used by banks, airlines and insurers is more than another partnership announcement. It is a new dependency entering old, consequential machinery.

The attraction is clear. An established provider understands legacy integration, contracts, operations and regulated customers. The model company supplies capability that would be difficult for each institution to reproduce. Together they can make adoption faster.

The risk is that layers of convenience make the real architecture harder to see. Which organization controls the prompt, retrieval, model version, logs and safety settings? Can the customer identify when behaviour changed? What continues to work during a model, network or vendor outage? Who can investigate an incident across organizational boundaries?

REHEARSE THE DEPENDENCY

Before treating the integration as core, run three exercises:

- the model is withdrawn or materially changed;

- the integration is unavailable during a critical business period;

- a regulator or customer asks for the evidence behind one output six months later.

Document the fallback, data boundary, version control, logs, support path and contractual responsibility. A strong partner can reduce implementation risk. It cannot eliminate the institution's responsibility to understand the system it has placed in the flow of work.

Original LinkedIn note: https://www.linkedin.com/feed/update/urn:li:activity:7470953062384168960/