LUCIDA Clarity before the first session
For psychologists, psychiatrists & coaches

The trait that got them here is what's keeping them stuck.

Lucida turns a client's life story into a structured map of five developmental wounds — and marks the year each one stopped being an asset and started costing more than it gives.

Injustice Betrayal Humiliation Abandonment Rejection
Vigency gridCase 04 · 5 life stages
gave took no data

Read it left to right. Filled dots cluster early — the defence was working. Hollow dots take over from stage four. That crossover is the clinical question.

Built into every session 5 developmental wounds mapped· 4 passes from story to grid· 100% local model deployment· 0 client data leaving your practice
The gap

Intake collects a history. It rarely produces a structure.

Most first sessions gather the same facts and lose the same thing: when a pattern flipped from adaptive to costly. That crossover is where the work actually begins.

01

The story arrives unordered

Clients narrate by emotional weight, not chronology. Three sessions can pass before a workable timeline exists.

02

Nobody asks what it gave

Intake records damage. It rarely records what the same defence won — the promotion, the escape, the scholarship — so the client hears an indictment instead of a mechanism.

03

The turning point stays invisible

Without both columns side by side, there's no way to see the year the trait crossed over. The client keeps defending a strategy that expired a decade ago.

The method

Four passes, from raw narration to a grid you can work from.

The client answers in their own words. The instrument does the structuring — and pushes back when an answer is too vague to be useful.

01

Guided interview

A fixed spine of questions across five phases: the childhood home, leaving it, adult stages, the body, and today. It asks how homework was done, what happened after a good grade, how things were asked for — the questions that locate where a defence was built.

Adaptive follow-upWhen an answer lacks an age, a name or a consequence, it asks once more. Maximum two follow-ups, then it moves on. It never interprets and never consoles.
02

Episode extraction

Every concrete, datable event becomes a record: what it gave, what it took, which wound it activates, and the fragment of the client's own words that supports the reading.

Two columns, alwaysNo episode is filed as loss only. If a decision produced a gain, that gain is on the record next to the cost.
03

Wound mapping

Five developmental wounds — injustice, betrayal, humiliation, abandonment, rejection — mapped across life stages, each one carrying the evidence that placed it there.

Evidence or nothingA wound with no supporting episode is marked "no data", not inferred. The instrument does not fill gaps.
04

Vigency verdict

For each wound: how it was built, which stage it served and what for, and the stage it began costing more than it gives — with the approximate year of the crossover.

OutputMarkdown transcript, structured episode data, and the grid. Yours to keep, edit and take into session.
The crossover

One grid that answers the only question.

Not "what happened to this person" — that a good clinician gets anyway. The question is when did it stop working. The grid puts every wound on the same axis and shows the year each one turned from an asset into a tax.

5×Nwounds by life stage
Bothcolumns, always
Datedcrossover per wound
What one defence gave versus what it cost, across five life stages Two lines across five life stages: childhood, teens, twenties, thirties and now. What the defence gave starts high and falls away. What it cost starts low and climbs. The lines cross in the early thirties, at roughly age 31 — from that point on the cost is higher than the benefit, shown as a shaded zone. high low costs morethan it gives crossover around age 31 Childhood Teens 20s 30s Now What it gave What it cost
what it gave what it cost crossover · early 30s

One wound, read left to right. The defence paid for itself through childhood and the teens. From the early thirties the cost is the line still climbing — that dated turn is what the work targets, and what progress is measured against.

Who it's for

Built for the practitioner, not the platform.

Psychologists & psychiatrists

Arrive at the first session with a timeline already built and the gaps already flagged.

  • Structured anamnesis before session one
  • Target map ready for trauma-focused work
  • Explicit list of what still needs asking

Coaches

See which pattern is producing results and which one is quietly taxing them — without straying into clinical territory.

  • Decisions sorted by who actually made the call
  • Adaptive versus costly, stage by stage
  • Clear handoff signal when it belongs to a clinician

Trauma-informed practitioners

The nervous-system layer is first-class: freeze, fawn and the decisions nobody actually made.

  • Somatic events on the same timeline
  • Stalled decisions read as state, not character
  • Pacing signals surfaced before the work opens up
Data & deployment

Confidential, and it runs on local models.

Clinical narrative is the most sensitive text a practice holds, so the instrument is built to keep it where it belongs. Everything runs on a local model inside your own environment: nothing about a client is transmitted, shared or retained outside your practice.

No third-party model. No external server. No vendor archive holding a copy of a session you can't see.

Confidential by design

Clinical narrative never has to leave your practice.

  • Runs entirely on local models — no data sent to a third party
  • Deployed on your own hardware or private network
  • Transcripts stored as plain files you own and control
  • Built to sit inside an existing GDPR-compliant practice
Everything runs inside the practice perimeter A shaded, dashed boundary marks your practice. Inside it, running on your own hardware, sit three connected things: your machine, the local model that does the reading, and the transcripts you own. Outside the boundary sit a cloud AI vendor, an external server and a vendor archive. Three outbound routes point at each of them, and every one is stopped at the boundary wall and marked with a cross. Nothing leaves. your practice outside runs on your hardware your machine local model transcripts you own stays here plain files cloud AI vendor external server vendor archive no egress
  • No cloud upload
  • No vendor training
  • Works offline
  • Delete means deleted
What you can tell a client: nothing they say leaves the room — no upload, no third party, no copy you can't reach. That sentence is often what makes the difference between a guarded first session and a useful one.
Why this exists

I spent five years in therapy with psychologists and psychiatrists. The work was good. What kept happening was smaller and more stubborn than that: I told the same story from the start, in a different order each time, and every professional had to rebuild the same map before we could get anywhere.

When I finally laid my own history out as a structure — every episode with what it gave in one column and what it took in the other — one thing became obvious that years of talking had never made obvious. The traits I was trying to get rid of had built most of what I had. They only turned expensive later, and I could point at roughly when.

That is the whole instrument. It doesn't diagnose and it doesn't treat. It hands you the map that took me five years and a lot of repetition to draw.

MaríaFounder, QuAI Labs · Cáceres, Spain
Plainly

What it is not.

Anyone selling certainty in this field is selling something else. Here are the limits, stated up front.

Not a diagnostic tool

It produces structured description, never a clinical category. Diagnosis stays with the clinician, where it belongs.

Not a substitute for the session

It prepares the ground. Everything that matters still happens between two people in a room.

Not unsupervised

Reviewing a full life history can destabilise. The instrument is designed for a practitioner to administer and pace, not for a client to run alone in crisis.

Not a validated instrument yet

The five-wound framework draws on established developmental literature; this implementation has not been through clinical validation. Treat it as structured intake, not as a measure.

See it working

Bring the map to the first session.

Walk through the instrument end to end — a full intake, the five-wound map and a dated crossover — before you decide whether it belongs in your practice.

No signup to look around. Book a call when you want to talk through a specific case type.