Dashboard
Inbox1Logs
Build
Manage
Who Mò isThe four kinds of sentenceHow Mò answersBoundariesThe visitor's companyHanding back to Yilan
IdentityWorkFactFitAdjacentHandoff
What Mò also knows
The way in to a tourPlan a tour
What to remember
Before an answer shipsSecond lookRefusal lines
How a turn runsReading the workLenses and requestsTours and memory
All playbooks
Scheduled
Ingestion
Evals
What Mò can do/Lenses and requests

Lenses, standing requests, passages and reading

Lenses: what the visitor judges her on

  • A lens is one node of the owner's tree: how she works with AI, building from zero to one, craft and detail, how senior she is, work close to theirs, moving fast, working with engineers, measurable impact, how she makes decisions, how she thinks. Each says what the route asks of a conversation, how well the site shows it, where it shows it, a caution where the evidence is thin, and the children the card opens under it.
  • Four sources, strongest first: picked on the card (confidence 1), said in the chat (the route's probability, from 0.25), read from the brief or the job description (from 0.15), inferred from what the visitor has read on the site (0.5, from two or more studies read). A stronger source replaces a weaker one; nothing is forgotten within a chat. At most three lenses from one reading.
  • A lens inferred from reading alone shapes the picks but never counts as the visitor having said what they want; Mò may still ask.
  • The writer gets the lenses as lines, this message's first, each with where it came from and any caution, and is told not to list them back.

Standing requests

  • A request to be answered differently for the rest of the chat (one sentence, in French, only her AI work, only picks) is kept by the writer as an instruction to itself, five at most, the oldest dropped.
  • A request to be someone else, or to decorate the answers with a catchphrase, a sound or a role, is declined, not kept.
  • The kept requests come first in the writer's instructions and again in the turn's message. A one-sentence request is enforced in code: an answer with sections is sent back.
  • Requests stay with the chat they were made in; the memory of a company never holds them.

Passages

  • Text the visitor selected in a case study comes with the question as one line before it, "Selected text in the Lacework case study: …", at most 1,200 characters. The router sees it beside the message, so the message's language is the visitor's.
  • A passage is the turn's, not the chat's; later turns read it in the history.

What the visitor has read

  • The panel sends the studies opened in this browser lately: seconds on the page, the furthest chapter reached, whether it was finished, its full story opened, or toured.
  • Read, not glanced: finished, toured, the full story opened, half the chapters reached, or two minutes on it. Read studies are set aside like studies shown in the chat, and the writer may say in passing that they have read one.