Sample report

Review the sample before sharing anything real.

This sample report helps professionals judge whether the structure feels useful, bounded, and trust-sensitive before anyone shares private relationship details.

Sample report first
Consent and safety stay central
No therapy or diagnosis claims
A careful reviewer reading a printed relationship summary at a warm oak desk with soft daylight and handwritten notes.

Sample report for professional review. Not therapy, diagnosis, or emergency support.

Texting Late Became A Safety-Versus-Autonomy Fight

A recurring texting argument is carrying more meaning than the delay itself. One person experiences delayed replies as loss of priority. The other experiences repeated check-ins as pressure or monitoring.

Professional review mode

Review the sample before sharing anything real.

This sample is meant to show structure, tone, and boundaries. The first reviewer task is to decide whether it feels useful, risky, or incomplete before anyone shares private relationship details.

Useful

Could this help a coach, facilitator, or mentor debrief one repeated pattern without escalating blame?

Risky

Does any wording sound like therapy, diagnosis, motive-reading, pressure, or hidden partner analysis?

Missing

What context would a real professional need before trusting this with one consented case?

Review boundary

Keep the first reaction narrow.

Do not send client data, partner names, transcripts, or private relationship details for this review.
Do not treat the report as advice, diagnosis, mediation, emergency support, or a replacement for professional judgment.
Do send plain feedback on clarity, safety, usefulness, missing context, and whether a bounded next step would make sense.

Private review notes

Turn a review into a clear summary.

Save only the professional reaction to this sample. Notes stay in this browser, and saving only runs dry-run local validation checks. It does not write to Supabase, send outreach, or trigger billing.

Outcome

Local review boundary

Saving keeps the notes in this browser and only runs dry-run local validation checks. It does not write to Supabase, send outreach, or trigger billing.

No review notes have been saved in this browser yet.

Review summary

Notes saved locally in this browser.

These notes help compare what felt useful, risky, or missing before you take any further step.

Saved notes

0

This browser only

Latest outcome

No saved reaction yet

Waiting for a professional review

Privacy

Browser-local notes

Browser-local notes plus dry-run local checks only

Recommendation

Waiting for review

No recommendation until notes exist

Use this space to capture exact friction, trust signals, and missing-boundary notes as you review the sample.

What happened

A late reply triggered a conversation that shifted from logistics into priority, pressure, and whether closeness was being requested or demanded.

Surface issue

Texting back late and expectations for communication during the day.

Deeper issue

Reassurance versus autonomy. One person needs signals of closeness; the other needs room to focus without being read as absent.

Language fracture

'Checking in' appears to mean care and reassurance for one person, but monitoring or pressure for the other.

Pattern

Request for closeness creates pressure. Pressure creates withdrawal. Withdrawal increases fear. Fear increases pressure.

Repair opportunity

Name that care and autonomy are both legitimate needs before debating the texting rule.

Repair language

I think my request for contact came out as pressure. I was trying to feel close, not control you. Can we define what check-in would feel caring without interrupting your day?

Future branch

This is a scenario, not a prediction. If the loop repeats, texting becomes a symbol for trust. If it is named, the couple can design a ritual instead of relitigating each delay.

Confidence and uncertainty

The pattern is a useful hypothesis, not a fact about either person's inner state. The other person's direct consented input would improve confidence.

Reviewer checklist

Use the sample to judge trust, usefulness, and boundaries.

Would this help a professional guide one repeated conflict with more structure and less blame?
Does the report stay clear about uncertainty instead of pretending it knows inner motives?
Does the repair language feel usable without becoming a script that pressures someone?

Reviewer trust layer

The sample only earns trust if the reviewer path is strong too.

These guides keep reviewers centered on the bounded recommendation question: what to screen before trusting the artifact, what to verify after the first no or not yet, and whether a polished report still leaves room to slow down or stop.