- Step 1
Each person writes a private reflection
- Step 2
Paste the shared conversation
- Step 3
Contextual compares reflection vs evidence
- Step 4
Review the gap analysis and repair starters
See the product flow in one pass.
Contextual is easiest to understand when you follow the same path the agent follows: private reflections, shared evidence, comparison, then a repair readout grounded in citations.
B stepping in meant B did not trust A to finish the work.
B thought they were helping and had not realized A saw the work as settled.
The thread shows a direct ownership/help mismatch, followed by a defensive reply.
The conversation drifted from process into perceived intent before either person checked the other meaning.
Bring in the two inputs Contextual compares.
Start with two private reflections and one shared conversation record. The reflections stay private. The shared conversation is treated as evidence.
Run the mediation read against the current inputs.
This step compares the reflections against the shared evidence, decides whether external facts matter, and returns a traceable readout.
Person A private reflection
Used as private context only. Not quoted back as shared evidence.
Person B private reflection
Used as private context only. Not quoted back as shared evidence.
Add both private reflections and shared evidence above before you run the agent.
Review the repair output before going deeper.
Read the concise repair summary first: what the evidence supports, where the conversation drifted, and the draft repair starters for each side.
After you run Contextual, this section will summarize what the shared record supports, where meaning likely drifted, and two neutral repair starters to review.
Open the interpretation gap only after the summary makes sense.
This is the deeper read. It separates what was said from what was likely heard, then shows the bridge language that could restart the exchange.
This deeper read stays empty until the agent finishes. After the trace completes, cited interpretation gaps from the API response render here.
Keep the privacy boundary legible.
Contextual is useful only if the boundary between private context and shared evidence remains clear. This section makes that boundary explicit.
- Each private reflection is context for the agent, not shared content.
- Working notes and discarded drafts stay on the private side of the boundary.
- The agent should not quote a private reflection back as if it were evidence.
- The shared conversation is treated as evidence and cited by line.
- Repair starters are drafts to review, not verdicts to enforce.
- Nothing should leave as a final repair message without clear participant consent.
Use public context only for external facts.
Public context is not a general enrichment layer. It should only enter the run when the disagreement depends on a fact that can be checked outside the conversation itself.
The disagreement depends on policies, pricing, availability, delays, reviews, or another external fact.
The conflict is mainly about tone, implication, wording, or what each person inferred from the same exchange.
Public context is off by default until you explicitly enable it for a run.
Keep the log, but move it to the end.
The session log is still part of the system language, but it should follow the main task flow rather than compete with it.
- Artifacts
- 1 transcript · 2 reflections · 1 repair readout
- Output
- Gap analysis · repair starters · trace
- Export
- session-01.read.signed
- Shared evidence stays cited and line-addressable.
- Private reflections stay on the private side unless a participant chooses otherwise.
- Repair language remains reviewable and does not decide who was right.