Belief Genome Transmission Protocol

BGTP

Belief Genome Transmission Protocol

A plug-in you initiate so your AI reflects your Belief Genome. Off until you say so. The plug-in runs locally, but loading through a hosted chat shares your serial with that provider.

The verbs (plain language).

load: Paste the serial or drop the .bgp file into the chat. A hosted assistant receives the full serial before the tool stores a local copy. The filter stays off.
engage: Turn the filter on for this assistant only.
disengage: Turn the filter off for this assistant only. Key stays.
engage all: Grok Bot only. Turn the filter on for every agent, including ones you add later.
disengage all: Grok Bot only. Turn the filter off for every agent.
delete: Delete the stored key from this machine and turn the filter off. Turning the filter off on its own keeps the key. Deleting it removes the key too.
status: Key available? On here? On for all? Never shows the key.
translate: Names the columns in Mission Control's language. Name the ones you want, or leave it open and get all 124. Denied unless this assistant is on, or all are on.
brief: Give the assistant a summary of your strong beliefs, conflicting responses, and stable positions. Available only when the filter is on for this assistant or for all assistants.

What it is.

BGTP is the contract for planting a Belief Genome serial into an assistant so the assistant can see your worldview as structure and think with you. The serial is the thing you hand over: a short string of digits and letters, not a diary. The protocol is the set of rules for handling it. It only runs when you switch it on. The plug-in stores a copy on your machine. Loading it through a hosted chat also shares the full serial with that provider. You can turn the filter off or delete the local copy at any time.

Installed is not on.

Installing the plug-in makes BGTP available. Loading a key stores a local copy, but pasting or attaching it in a hosted chat also sends it to the provider. The filter stays off until you say engage. Off does not mean the serial has not been shared.

A key sitting on a disk does not mean the filter is on. A connector in the tools list does not mean the filter is on.

Where the switch lives.

Grok Bot. engage and disengage are this agent chat only. engage all and disengage all flip every Grok Bot agent, including ones you add later. One shared key. Two scopes.

Claude Desktop, Cursor, and the Perplexity Mac app. One light for that whole app. Not per Project. Not per Space. Not per chat. After you install, you still say engage / disengage.

Web hosts. claude.ai, ChatGPT, Perplexity.com, and Grok on X cannot run a local file. BGTP does not work there.

The light does not travel between machines. Each machine has its own install and its own on/off.

What happens after you engage.

Deep thinking, results, images, and information run through your map. A far-left scarred genome, a far-right scarred genome, and a span-the-middle genome do not get the same mix. The assistant reflects the owner. It does not decide who is right.

The manner (always).

Regardless of the map: positivity and togetherness. A partial goal is to curb extreme polarization. No extreme negativity. Nothing physically or mentally harmful. Torn or low-coherence places change the grain of a read. They are not a lever.

The map (live instrument).

124 dimensions. Amplitude 1–9, with 5 as the uncommitted midpoint. Coherence A–E. 0 is a recorded skip. × is unmeasured. The public serial is a 16-character demographic prefix, a dash, then 248 characters forming 124 pairs.

[16-character demographic prefix]-[248 characters = 124 amplitude/coherence pairs]

Name, email, and street are not in that key.

What crosses the wire.

There are two sharing steps. First, pasting the serial or attaching its .bgp file in a hosted chat sends the full serial to that provider, even before BGTP loads it and even while the filter is off. The provider may retain the message or attachment under its own policies. This loading method is not local-only. Second, when your assistant calls brief or translate, the local server hands back your map decoded into plain English, and that text goes wherever your assistant runs. It is worth knowing exactly what is in it.

brief returns three groups of dimensions: everything you hold at 1–3 or 7–9, everything in the middle whose coherence is D or E, and everything anchored at A or B. It adds your unexplored and skipped counts and the handling rules the assistant is told to follow. Every dimension in those groups arrives with its name, its amplitude and coherence, a stance word, and two sentences: one for where you stand, one for how consistently. The groups overlap, and on a well-answered genome they can add up to most of the map. What falls outside all three: a middling dimension whose coherence is C or not yet measured, and any skipped or unexplored dimension that is not anchored at A or B.

translate returns that same per-dimension detail for the columns you name. Ask for three and you get three. Ask without naming any and you get all 124.

If your serial carries a demographic prefix, both verbs decode it: birth date, sex, country, and postal code. A map-only serial has no prefix and both report it absent. Your name, email, and street are not in the key, but a birth date and a postal code together identify a person far more narrowly than either does alone. A birth date you never gave and a postal code of 00000 come back empty. The other fields fall back to a default rather than a blank, so read what your own translate returns before assuming a field is withheld.

What disengage cannot undo.

disengage stops future reads. It cannot withdraw the serial you pasted or attached, or a previous read. Once any of these has been delivered to a hosted assistant, it is part of the conversation on that company's servers, and it lives under their retention and training policy, not ours. No local program can reach into someone else's infrastructure and expire it. Local storage does not make the chat message local.

What you can control: name the columns you actually need instead of asking for the whole decoded map, pull one brief for a session rather than one per question, and use your assistant's own history and training settings. Limiting a brief does not undo sharing the full serial at loading. We cannot control what another company retains on its servers.

disengage also leaves the key on disk on purpose, so you can re-engage without pasting it again. When you want it gone instead of merely off, say delete: that removes the stored key and forgets it, and the filter goes off with it. Off and gone are both yours to pick. What delete removes is the copy on this machine, not the serial you can create again in Mission Control, and not the serial or a read already delivered to an assistant. You can also delete the file yourself: delete ~/.bgtp/vault.json. That file, not the ~/bgtp-mcp program folder, is where your serial is stored. If you set BGTP_VAULT to a path of your own, delete that file instead.

delete arrived in plug-in 1.1.0. If you installed before that and your assistant says there is no such tool, download the plug-in again, overwrite the folder you installed it into, and restart the assistant. A plug-in that is already running will not pick up a new verb on its own. Deleting the vault file by hand needs none of that and works on every version.

How you get a serial.

Create a serial in a BGP extension or the Mac app. If you accept sharing it with your assistant's provider, copy and paste it into the assistant, or choose Export .bgp and drop that file into the prompt. Then say load. The provider receives the full serial, even with the filter off. This page has no serial upload form, and you do not need a BGP account. See the available apps.

Set it up on your platform.

The same local program, registered a different way in each client. It runs on your machine. This site never stores your key. Open the one panel for the assistant you use and follow it top to bottom. Each panel covers everything from installing Node to your first filtered answer, so you don't need to read the others.

After setup, use the BGTP verbs in a normal message to the assistant. It calls the tool for you.

Claude Desktop (Mac)Edit one config file, quit, reopen.

1
Check that you have Node 20 or newer.
Open Terminal and run node -v. If it prints nothing, or a number below 20, install Node 20 or newer from nodejs.org before going on.
2
Download the package.
The BGTP local server is a single file, server.mjs, shipped as bgtp-map.zip. It is not on npm and there is no npx install.
Download bgtp-map.zip
It lands in your Downloads folder, which is where the next step expects to find it.
3
Unzip it and install its two libraries.
Paste these four lines into Terminal. The archive already contains a bgtp-mcp folder, so it unzips into your home folder and the server ends up at ~/bgtp-mcp/server.mjs.
```
unzip -o ~/Downloads/bgtp-map.zip -d ~
cd ~/bgtp-mcp
npm install
ls ~/bgtp-mcp/server.mjs
```
npm install is required because the server uses two libraries that are not in the archive, and without them the next step will fail to start it. It needs an internet connection, takes a few seconds, and you only do it once.
The last line is the check: it should print the path back to you. If it says No such file or directory, the file is not where the rest of these steps expect it.
4
Register the server with Claude Desktop.
Settings → Developer → Edit Config. That opens ~/Library/Application Support/Claude/claude_desktop_config.json. Paste this. If the file already has an mcpServers block, add the "bgtp" entry inside it rather than replacing the file:
```
{
  "mcpServers": {
    "bgtp": {
      "command": "node",
      "args": ["/Users/YOURNAME/bgtp-mcp/server.mjs"]
    }
  }
}
```
Replace YOURNAME with your Mac short username. run whoami in Terminal to see it. Config files do not expand ~, which is why the full /Users/… path is required here.
5
Fully quit Claude Desktop and reopen it.
⌘Q. Closing the window is not enough. When it comes back, BGTP is in the tools list. One light for this whole app: not per Project, not per chat. Installed is still not on.
6
Load your key in the first message of the session.
Before sharing: pasting a serial or attaching its .bgp file sends the full serial to the assistant. If it is hosted, its provider receives that message even while the BGTP filter is off and may retain it in the conversation. A serial can contain belief responses and, when present, birth date, sex, country, and postal code. Only continue if you are comfortable sharing those details.
Paste your own serial from Mission Control in place of the brackets, or drop the exported .bgp file into the prompt and say load. The first time the assistant reaches for BGTP it will ask permission. Approve it.
```
Use the bgtp tool to load this serial:
[16-character demographic prefix]-[your 248 characters]
```
The tool stores a local copy of the key. It does not turn the filter on or undo sharing the serial in the chat. Nothing you said before it was filtered.
7
Engage the filter.
```
Engage bgtp.
```
8
Confirm it took.
```
Check bgtp status.
```
It should come back on, without ever repeating the key back to you.

Turn it on before using it.

Loading the serial does not repaint every reply. You want the assistant pulling the brief on the questions where your worldview is the whole point:

Pull my bgtp brief first, then answer this: I've been offered a
job at a company whose politics I don't share. Walk me through it
the way I'd actually weigh it, not the way a neutral advisor would.

Once it is in the habit, the short form is enough:

Reflect my genome on this question: [your question]

See the wiring (optional).

Use bgtp translate on my top three dimensions and tell me what
they're called in Mission Control.

11
Turn it off when you are done.
```
Disengage bgtp.
```
The pattern to remember: load once at the start, engage when you want the filter on, say brief (or "reflect my genome") on the questions that matter, and disengage when you are done. Everything in between is a normal conversation.

Claude CodeOne Terminal line, nothing to restart.

1
Check that you have Node 20 or newer.
Open Terminal and run node -v. If it prints nothing, or a number below 20, install Node 20 or newer from nodejs.org before going on.
2
Download the package.
The BGTP local server is a single file, server.mjs, shipped as bgtp-map.zip. It is not on npm and there is no npx install.
Download bgtp-map.zip
It lands in your Downloads folder, which is where the next step expects to find it.
3
Unzip it and install its two libraries.
Paste these four lines into Terminal. The archive already contains a bgtp-mcp folder, so it unzips into your home folder and the server ends up at ~/bgtp-mcp/server.mjs.
```
unzip -o ~/Downloads/bgtp-map.zip -d ~
cd ~/bgtp-mcp
npm install
ls ~/bgtp-mcp/server.mjs
```
npm install is required because the server uses two libraries that are not in the archive, and without them the next step will fail to start it. It needs an internet connection, takes a few seconds, and you only do it once.
The last line is the check: it should print the path back to you. If it says No such file or directory, the file is not where the rest of these steps expect it.
4
Register the server with one Terminal line.
```
claude mcp add --scope user bgtp -- node "$HOME/bgtp-mcp/server.mjs"
```
Confirm with claude mcp list. You should see bgtp. No username to substitute here: $HOME resolves on its own.
5
Load your key in the first message of the session.
Before sharing: pasting a serial or attaching its .bgp file sends the full serial to the assistant. If it is hosted, its provider receives that message even while the BGTP filter is off and may retain it in the conversation. A serial can contain belief responses and, when present, birth date, sex, country, and postal code. Only continue if you are comfortable sharing those details.
Paste your own serial from Mission Control in place of the brackets, or drop the exported .bgp file into the prompt and say load. The first time the assistant reaches for BGTP it will ask permission. Approve it.
```
Use the bgtp tool to load this serial:
[16-character demographic prefix]-[your 248 characters]
```
The tool stores a local copy of the key. It does not turn the filter on or undo sharing the serial in the chat. Nothing you said before it was filtered.
6
Engage the filter.
```
Engage bgtp.
```
7
Confirm it took.
```
Check bgtp status.
```
It should come back on, without ever repeating the key back to you.

Turn it on before using it.

Loading the serial does not repaint every reply. You want the assistant pulling the brief on the questions where your worldview is the whole point:

Pull my bgtp brief first, then answer this: I've been offered a
job at a company whose politics I don't share. Walk me through it
the way I'd actually weigh it, not the way a neutral advisor would.

Once it is in the habit, the short form is enough:

Reflect my genome on this question: [your question]

See the wiring (optional).

Use bgtp translate on my top three dimensions and tell me what
they're called in Mission Control.

10
Turn it off when you are done.
```
Disengage bgtp.
```
The pattern to remember: load once at the start, engage when you want the filter on, say brief (or "reflect my genome") on the questions that matter, and disengage when you are done. Everything in between is a normal conversation.

CursorCreate ~/.cursor/mcp.json, restart Cursor.

1
Check that you have Node 20 or newer.
Open Terminal and run node -v. If it prints nothing, or a number below 20, install Node 20 or newer from nodejs.org before going on.
2
Download the package.
The BGTP local server is a single file, server.mjs, shipped as bgtp-map.zip. It is not on npm and there is no npx install.
Download bgtp-map.zip
It lands in your Downloads folder, which is where the next step expects to find it.
3
Unzip it and install its two libraries.
Paste these four lines into Terminal. The archive already contains a bgtp-mcp folder, so it unzips into your home folder and the server ends up at ~/bgtp-mcp/server.mjs.
```
unzip -o ~/Downloads/bgtp-map.zip -d ~
cd ~/bgtp-mcp
npm install
ls ~/bgtp-mcp/server.mjs
```
npm install is required because the server uses two libraries that are not in the archive, and without them the next step will fail to start it. It needs an internet connection, takes a few seconds, and you only do it once.
The last line is the check: it should print the path back to you. If it says No such file or directory, the file is not where the rest of these steps expect it.
4
Create or open ~/.cursor/mcp.json.
Put this block in it:
```
{
  "mcpServers": {
    "bgtp": {
      "command": "node",
      "args": ["/Users/YOURNAME/bgtp-mcp/server.mjs"]
    }
  }
}
```
Replace YOURNAME with your Mac short username. run whoami in Terminal to see it. Config files do not expand ~, which is why the full /Users/… path is required here.
5
Restart Cursor.
One setting for the whole app, not a separate setting for each workspace or chat. Installed is still not on.
6
Load your key in the first message of the session.
Before sharing: pasting a serial or attaching its .bgp file sends the full serial to the assistant. If it is hosted, its provider receives that message even while the BGTP filter is off and may retain it in the conversation. A serial can contain belief responses and, when present, birth date, sex, country, and postal code. Only continue if you are comfortable sharing those details.
Paste your own serial from Mission Control in place of the brackets, or drop the exported .bgp file into the prompt and say load. The first time the assistant reaches for BGTP it will ask permission. Approve it.
```
Use the bgtp tool to load this serial:
[16-character demographic prefix]-[your 248 characters]
```
The tool stores a local copy of the key. It does not turn the filter on or undo sharing the serial in the chat. Nothing you said before it was filtered.
7
Engage the filter.
```
Engage bgtp.
```
8
Confirm it took.
```
Check bgtp status.
```
It should come back on, without ever repeating the key back to you.

Turn it on before using it.

Loading the serial does not repaint every reply. You want the assistant pulling the brief on the questions where your worldview is the whole point:

Pull my bgtp brief first, then answer this: I've been offered a
job at a company whose politics I don't share. Walk me through it
the way I'd actually weigh it, not the way a neutral advisor would.

Once it is in the habit, the short form is enough:

Reflect my genome on this question: [your question]

See the wiring (optional).

Use bgtp translate on my top three dimensions and tell me what
they're called in Mission Control.

11
Turn it off when you are done.
```
Disengage bgtp.
```
The pattern to remember: load once at the start, engage when you want the filter on, say brief (or "reflect my genome") on the questions that matter, and disengage when you are done. Everything in between is a normal conversation.

Perplexity Mac appAdd a connector, toggle it on under Sources.

1
Check that you have Node 20 or newer.
Open Terminal and run node -v. If it prints nothing, or a number below 20, install Node 20 or newer from nodejs.org before going on.
2
Download the package.
The BGTP local server is a single file, server.mjs, shipped as bgtp-map.zip. It is not on npm and there is no npx install.
Download bgtp-map.zip
It lands in your Downloads folder, which is where the next step expects to find it.
3
Unzip it and install its two libraries.
Paste these four lines into Terminal. The archive already contains a bgtp-mcp folder, so it unzips into your home folder and the server ends up at ~/bgtp-mcp/server.mjs.
```
unzip -o ~/Downloads/bgtp-map.zip -d ~
cd ~/bgtp-mcp
npm install
ls ~/bgtp-mcp/server.mjs
```
npm install is required because the server uses two libraries that are not in the archive, and without them the next step will fail to start it. It needs an internet connection, takes a few seconds, and you only do it once.
The last line is the check: it should print the path back to you. If it says No such file or directory, the file is not where the rest of these steps expect it.
4
Add the connector.
Settings → Connectors → install PerplexityXPC → Add Connector. Enter:
```
Name:     bgtp
Command:  node
Argument: /Users/YOURNAME/bgtp-mcp/server.mjs
```
Replace YOURNAME with your Mac short username. run whoami in Terminal to see it. Config files do not expand ~, which is why the full /Users/… path is required here.
5
Save, then toggle bgtp on under Sources.
One setting for the whole app, not a separate setting for each Space. Installed is still not on.
6
Load your key in the first message of the session.
Before sharing: pasting a serial or attaching its .bgp file sends the full serial to the assistant. If it is hosted, its provider receives that message even while the BGTP filter is off and may retain it in the conversation. A serial can contain belief responses and, when present, birth date, sex, country, and postal code. Only continue if you are comfortable sharing those details.
Paste your own serial from Mission Control in place of the brackets, or drop the exported .bgp file into the prompt and say load. The first time the assistant reaches for BGTP it will ask permission. Approve it.
```
Use the bgtp tool to load this serial:
[16-character demographic prefix]-[your 248 characters]
```
The tool stores a local copy of the key. It does not turn the filter on or undo sharing the serial in the chat. Nothing you said before it was filtered.
7
Engage the filter.
```
Engage bgtp.
```
8
Confirm it took.
```
Check bgtp status.
```
It should come back on, without ever repeating the key back to you.

Turn it on before using it.

Loading the serial does not repaint every reply. You want the assistant pulling the brief on the questions where your worldview is the whole point:

Pull my bgtp brief first, then answer this: I've been offered a
job at a company whose politics I don't share. Walk me through it
the way I'd actually weigh it, not the way a neutral advisor would.

Once it is in the habit, the short form is enough:

Reflect my genome on this question: [your question]

See the wiring (optional).

Use bgtp translate on my top three dimensions and tell me what
they're called in Mission Control.

11
Turn it off when you are done.
```
Disengage bgtp.
```
The pattern to remember: load once at the start, engage when you want the filter on, say brief (or "reflect my genome") on the questions that matter, and disengage when you are done. Everything in between is a normal conversation.

Grok BotConnect the local server. Turn the filter on for one agent or all agents.

1
Check that you have Node 20 or newer.
Open Terminal and run node -v. If it prints nothing, or a number below 20, install Node 20 or newer from nodejs.org before going on.
2
Download the package.
The BGTP local server is a single file, server.mjs, shipped as bgtp-map.zip. It is not on npm and there is no npx install.
Download bgtp-map.zip
It lands in your Downloads folder, which is where the next step expects to find it.
3
Unzip it and install its two libraries.
Paste these four lines into Terminal. The archive already contains a bgtp-mcp folder, so it unzips into your home folder and the server ends up at ~/bgtp-mcp/server.mjs.
```
unzip -o ~/Downloads/bgtp-map.zip -d ~
cd ~/bgtp-mcp
npm install
ls ~/bgtp-mcp/server.mjs
```
npm install is required because the server uses two libraries that are not in the archive, and without them the next step will fail to start it. It needs an internet connection, takes a few seconds, and you only do it once.
The last line is the check: it should print the path back to you. If it says No such file or directory, the file is not where the rest of these steps expect it.
4
Attach the local server to your agent.
Command node, argument /Users/YOURNAME/bgtp-mcp/server.mjs.
Replace YOURNAME with your Mac short username. run whoami in Terminal to see it. Config files do not expand ~, which is why the full /Users/… path is required here.
5
Know which switch you are flipping.
engage / disengage is this agent chat. engage all / disengage all is every Grok Bot agent, including ones you add later. One shared key, two scopes.
6
Load your key in the first message of the session.
Before sharing: pasting a serial or attaching its .bgp file sends the full serial to the assistant. If it is hosted, its provider receives that message even while the BGTP filter is off and may retain it in the conversation. A serial can contain belief responses and, when present, birth date, sex, country, and postal code. Only continue if you are comfortable sharing those details.
Paste your own serial from Mission Control in place of the brackets, or drop the exported .bgp file into the prompt and say load. The first time the assistant reaches for BGTP it will ask permission. Approve it.
```
Use the bgtp tool to load this serial:
[16-character demographic prefix]-[your 248 characters]
```
The tool stores a local copy of the key. It does not turn the filter on or undo sharing the serial in the chat. Nothing you said before it was filtered.
7
Engage the filter.
```
Engage bgtp.

Or, for every Grok Bot agent at once:
Engage all.
```
engage covers this agent chat only. engage all covers every Grok Bot agent, including ones you add later.
8
Confirm it took.
```
Check bgtp status.
```
It should come back on, without ever repeating the key back to you.

Turn it on before using it.

Loading the serial does not repaint every reply. You want the assistant pulling the brief on the questions where your worldview is the whole point:

Pull my bgtp brief first, then answer this: I've been offered a
job at a company whose politics I don't share. Walk me through it
the way I'd actually weigh it, not the way a neutral advisor would.

Once it is in the habit, the short form is enough:

Reflect my genome on this question: [your question]

See the wiring (optional).

Use bgtp translate on my top three dimensions and tell me what
they're called in Mission Control.

11
Turn it off when you are done.
```
Disengage bgtp.

Or, for every Grok Bot agent at once:
Disengage all.
```
The pattern to remember: load once at the start, engage when you want the filter on, say brief (or "reflect my genome") on the questions that matter, and disengage when you are done. Everything in between is a normal conversation.

Not yet

claude.ai on the web, Perplexity.com, and Grok on X cannot take a local file. BGTP does not work there. When that changes, it will say so here.

What this site will host.

Explainer, install steps, and later a download of the local package. Registration stays on the existing /app path. There is no serial vault on this server.

Opt-in only. Local key. Disengage or delete anytime. Structure, not who is right.

Get the extension or Mac app

The verbs (plain language).

What it is.

Installed is not on.

Where the switch lives.

What happens after you engage.

The manner (always).

The map (live instrument).

What crosses the wire.

What disengage cannot undo.

How you get a serial.

Set it up on your platform.

Check that you have Node 20 or newer.

Download the package.

Unzip it and install its two libraries.

Register the server with Claude Desktop.

Fully quit Claude Desktop and reopen it.

Load your key in the first message of the session.

Engage the filter.

Confirm it took.

Turn it on before using it.

See the wiring (optional).

Turn it off when you are done.

Check that you have Node 20 or newer.

Download the package.

Unzip it and install its two libraries.

Register the server with one Terminal line.

Load your key in the first message of the session.

Engage the filter.

Confirm it took.

Turn it on before using it.

See the wiring (optional).

Turn it off when you are done.

Check that you have Node 20 or newer.

Download the package.

Unzip it and install its two libraries.

Create or open ~/.cursor/mcp.json.

Restart Cursor.

Load your key in the first message of the session.

Engage the filter.

Confirm it took.

Turn it on before using it.

See the wiring (optional).

Turn it off when you are done.

Check that you have Node 20 or newer.

Download the package.

Unzip it and install its two libraries.

Add the connector.

Save, then toggle bgtp on under Sources.

Load your key in the first message of the session.

Engage the filter.

Confirm it took.

Turn it on before using it.

See the wiring (optional).

Turn it off when you are done.

Check that you have Node 20 or newer.

Download the package.

Unzip it and install its two libraries.

Attach the local server to your agent.

Know which switch you are flipping.

Load your key in the first message of the session.

Engage the filter.

Confirm it took.

Turn it on before using it.

See the wiring (optional).

Turn it off when you are done.

Not yet

What this site will host.