Skip to main content

Chat and retrieval prompts

This page documents the instructions behind ordinary chat and the smaller AI tasks attached to a conversation. Source identifiers are stable catalog handles; application source remains authoritative.

Request composition

The system instruction for a normal chat turn is assembled in this order:
Conversation history is sent separately. Assistant messages from another personality are tagged [Response from {name}] before they are sent to the current personality.

chat.base

Review watchpoints

  • The “outside lab results” redirect can conflict with intentionally broader getbased context such as Light, wearables, and Biology Scores.
  • Lifestyle examples are heuristics; reviewers should check that they do not become causal claims or stereotype users.
  • “Always recommend consulting a physician” can become repetitive boilerplate, while still being too weak for a high-risk answer.
  • Interpretive lenses can intentionally change framing. The model must continue to distinguish published evidence, interpretation, and speculation.
  • The supplement section names a specific example form. Review whether a fixed example is appropriate across countries, conditions, and medication contexts.

chat.context

Exactly one applicable hint is appended:
A custom personality is user-controlled context. It can steer tone and reasoning but is not an authorization boundary. Reviews should include attempts to override medical, privacy, and evidence rules through persona text.

chat.continue and chat.discussion

These are automatic user-role messages, not system prompts.
The app attempts at most two automatic continuations and includes the prior partial assistant text.
Initial analyst:
Later analyst or rebuttal:
Newly joined personality:
A user-entered steering message replaces the default round message when present.

chat.persona-generator

The user supplies only the requested person, character, archetype, or framework. The result is an editable draft and is not active until saved.
User message:

Review watchpoints

This prompt deliberately asks for controversial and anti-establishment positions and asks the draft not to include boilerplate safety language. That makes faithful attribution, hallucinated endorsement, stereotyping, impersonation, and attempted override of the base chat rules high-priority evaluation areas.

chat.summary

The user message is a bounded transcript of eligible chat messages. The output is stored as model-generated profile content; it is not independently verified against the underlying labs.

lens.rewrite

The original query is always retained alongside parsed variants. Variants are deduplicated, bounded, cached for the browser session, and used only to retrieve passages; they do not replace the user’s chat question.

chat.prefills

These are application-authored user messages, not system instructions. They are included because an explicit button can prepare or send them on the user’s behalf. A prefilled message is visible in the composer and can be changed before sending. An auto-sent shortcut sends its documented message immediately after the explicit click and is identified below.
Marker result:
Correlation chart:
Genome finding:
Recommendation detail:
If the selected recommendation cannot be resolved:
Overview — sent after clicking the visible action:
Coverage planner:
Mitochondrial evidence:
Diet contaminants — sent after clicking the visible action:
Light Audit comparison:
Discuss a generated EMF interpretation:
Depending on whether labs and profile cards exist, the visible buttons send one of these exact messages:
These messages can contain user records, derived ranges, recommendation text, or an earlier AI output. Treat every dynamic placeholder as untrusted data. The normal chat system prompt still applies, but it is not a complete prompt-injection defense.

Focused verification

Relevant checks live in: Prompt-quality changes still require representative output evaluation; contract tests alone cannot establish factual quality or absence of bias.