Skip to main content

​
See what getbased asks AI

Whenever getbased uses AI, it sends an instruction that describes the job. Chat receives an instruction about answering health and lab questions. A report import receives a different instruction about extracting dates, markers, values, and ranges. Other features have their own focused instructions. This guide lets you start with something you did in the app and answer four questions:
  • What did getbased ask the AI to do?
  • What information was included?
  • Could I review or edit the message first?
  • Where can I read the complete wording?
Want to inspect the wording immediately? Go to Find a prompt by feature, choose the action, and follow its link in the Read column.

​
Start with what you did

I sent a chat message

See what surrounds your message and which profile information can be included.

I clicked Ask AI

See the message getbased prepares and whether you can edit it first.

An AI feature ran

Browse report imports, summaries, Biology Scores, EMF, Light & Sun, and more.

I want to control my data

Review context controls, attachments, chat history, and provider boundaries.

​
A prompt in plain language

A request to an AI usually contains three parts:
The first part is the prompt or instruction. It can set the AI’s role, limits, writing style, and required answer format. The second part is the context—for example, enabled lab results or one Light & Sun session. The final part is the immediate task, such as your chat message or the report that needs to be read. Your AI provider is the outside service or local model you selected to process that request.
A prompt guides a model; it does not guarantee a correct answer. AI text can still be incomplete or wrong. Keep medical decisions with a qualified professional.

​
When you send a chat message

getbased sends the words you typed as your message. It does not silently rewrite them. Around that message, it can add the normal chat instruction, enabled profile information, recent conversation history, and optional tools such as a personality or Knowledge Base. Here is the plain-language shape of a normal request:
If you attach images, the current message also contains the prepared image data. If web search is enabled and supported, search results can be added before the answer is generated.
Read the maintained chat instruction and the optional chat additions. Braces such as {enabled profile context} stand for information filled in when you send.

​
A simple example

Suppose you write: “Why has my ferritin fallen over the last year?” The AI can receive:
  • that exact question;
  • the getbased chat instruction;
  • enabled ferritin values, dates, ranges, and relevant notes;
  • enabled supplement, medication, diet, cycle, or other profile context;
  • recent messages in the same conversation;
  • an optional personality and relevant Knowledge Base passages.
It does not automatically receive every stored item. The request uses the sources enabled for AI and the information selected for that feature.

​
When you use Ask AI

An Ask AI, Discuss, or chat-shortcut button can create the user message for you. This app-written message is separate from the chat instruction, and both are documented. Most feature buttons open chat with the message in the composer. You can read it, change it, or delete it before sending. A small number of explicit shortcuts send their documented message immediately after you click; the full list labels those actions. For example, a marker action starts with a message shaped like:
Other app-written messages cover correlations, Genome findings, recommendations, Biology Score coverage, supplement evidence, Light Audit comparisons, and EMF follow-up.
Read every app-written chat message, including which actions prefill the composer and which send after the click.

​
Find a prompt by feature

Choose the part of getbased you used. The final column opens the complete maintained instruction. Technical values that only exist at send time are shown as readable placeholders.
Seven Light & Sun instructions also include the same fixture and flicker safety rules.

​
Know what happens before sending

A review screen lets you correct AI-extracted results before saving; it does not mean the provider never received the selected file or prepared content. Check the feature’s privacy note before starting an import.

​
Control what information is included

For ordinary chat, open Insight → Manage → Context to choose which stored sources may influence later requests. Turning a source off keeps it stored but excludes it from new in-app AI context. Depending on the action, a request can also include:
  • recent messages from the current conversation;
  • images attached to the current message;
  • the report, product page, measurement, session, room, or assessment you selected;
  • an active personality;
  • selected Knowledge Base passages;
  • web-search results when web search is enabled and supported.
The AI provider selected in Settings → AI receives the assembled request. A local or private connection can change where and how it is transported, but it does not remove information that the selected feature needs for the request. See Privacy and data storage, Connect an AI provider, and Local encryption for the storage and transport boundaries.

​
Understand the wording you see

Read the full prompt blocks in two simple ways: No public documentation can display a future request containing your live private information. Placeholders show where that information would appear without publishing it. The prompt ID and source-file link on the full page are there for reviewers and contributors. You do not need to understand the code to read the instruction block.

​
Understand the result

AI has different responsibilities in different features:
  • Chat and interpretations return model-written explanations. They are not independently fact-checked.
  • Imports return structured candidates that getbased parses, normalizes, and shows for review before saving.
  • Short dots and verdicts accept only known display values and limit output length, but their wording is still AI-generated.
  • Biology Scores, calculated markers, reference ranges, and Light dose calculations come from fixed calculations or stored source data. AI can explain them, but it does not calculate or redefine them.
If an import or verdict response is missing the fields getbased expects, it normally fails, falls back to a neutral state, or stays out of saved data. A valid-looking answer can still be factually wrong, so review important results.

​
Common questions

No. Your current text is sent as the user message. The app adds its instruction and permitted context around it. Image attachments change the technical message format, but not the text you wrote.
No. Chat uses enabled context sources and limited summaries. Feature-specific actions can add the selected marker, finding, or record. Use Insight → Manage → Context to turn sources on or off.
It uses the normal chat instruction plus an app-written user message for that action. Most of those messages are visible and editable in the composer. All current templates are listed under app-written chat messages.
The main extraction and analysis instructions are maintained with the app because changes can affect safety, parsing, and compatibility. You can change your message, enabled context, personality, Knowledge Base, web-search setting, provider, and model.
The health instruction remains the same. The transport can add a short private-mode note and changes how the request reaches the provider. See Privacy and data storage for the exact boundary.
No developer health prompt is added for voice transcription or speech synthesis. Those services receive the recording or text-to-read together with their selected voice settings. They can use a different provider from chat.

​
Report or propose a change

If an instruction looks unclear, biased, unsafe, too broad, or inconsistent with the feature:
1

Name the action

Say what you clicked or what feature ran, such as Ask AI on a marker or Import report photos.
2

Link the prompt

Use the relevant Read link above so reviewers can find the maintained wording quickly.
3

Describe the problem

Explain the behavior you saw, what you expected, and why the wording may have contributed.
4

Remove private information

Replace health values, names, report text, credentials, private Knowledge Base content, and other identifying information with made-up examples.
5

Open a public issue

Use the GitHub issue tracker. Maintainers can follow the technical prompt review workflow.
Never paste an API key, share password, OAuth token, Cashu token, raw health report, or identifiable medical record into a public issue.