TENIR Labs · Portfolio

AI Exposure X-Ray

X-Ray perspective · illustrative examples

AI in an everyday task.

Open an example and see what is worth asking. No sign-up and no data to provide.

An automatically summarized meeting

In this fictional example, an assistant turns a recording into meeting notes. Who can access the audio? Where is it stored? Does someone check the decisions before sharing the summary?

A suggested customer reply

In this fictional example, a tool drafts a reply using the conversation history. Which information does it use? Does the reply stay a draft? Who checks any commitments before sending?

An automatically sorted document

In this fictional example, an invoice is read and routed to a folder. What if it is misclassified? Can someone find the original, understand the choice and correct it?

These examples offer a way to look at a situation. They do not analyze any of your tools; the X-Ray prototype status is described below.

Product or instrument

Is AI already part of the everyday tools?

An AI feature can arrive in a familiar tool before its uses, affected data and influence on decisions have been recorded.

What you receive
Exploratory exposure view and prioritized verification questions.

Contact page · prepare a message to review before sending.

AVAILABLE RESOURCEExplore three examples

Editorial examples, not the X-Ray v0.2 engine

Open resource ↗

See whether it fits your situation

This may help when…
When preparing an inventory of AI uses, an AI policy or the scope of a diagnostic.
What you need to start
Attributed interviews/surveys, tool inventory, processes, system owners and known unknowns.
What is examined
Reported AI use, possible exposure, owners and unknown safeguards.
The starting question
An AI feature can arrive in a familiar tool before its uses, affected data and influence on decisions have been recorded.
How it connects to other approaches
Can frame a Diagnostic or Prevent/Prepare; not the same as REG Discovery.
Availability and maturity
v0.2 favorably evaluated in project context; the public page contains editorial examples, not a connected prototype. Source revision and runtime deployment remain unverified.
Limits to keep in mind
Self-reports do not prove actual use or its absence, compliance or control coverage.
A possible next step
Select one process, then verify reported exposure against independent sources.
Read sources and version references

Availability and limits above reflect the cited sources. Unverified artifact revisions remain identified.