> For the complete documentation index, see [llms.txt](https://docs.genesisconductor.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.genesisconductor.io/documentation/intent-locality-handoff.md).

# Intent locality handoff

User selection on [click.grok.me](https://click.grok.me/) fixes the account. That account fixes the intent constraint on [li.grok.me](https://li.grok.me/). Semantic search retunes a dynamic graphic model on [sos.grok.me](https://sos.grok.me/).

## Surfaces

| Host          | Role                                    | Observed controls                                                                                                                                                                                                     |
| ------------- | --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| li.grok.me    | Intent and locality, one map seen twice | Constraint: Hold, Shear, Blind, Thin. Shape: Smooth, Folded, Cusp, Scan. Views: Intent, Locality, Mirror. Bath restraint 98 percent, waste 2 percent, RMSE 0.02.                                                      |
| click.grok.me | User selection                          | Structure: All, Orthogonal, Symmetric, Opposite, Inverse clique, Names. 50 accounts, star 50, clique 1,225, weight 148.                                                                                               |
| sos.grok.me   | Dynamic field                           | Algorithm, Analysis board, Fruchterman-Reingold weighted and unweighted, Kamada-Kawai, Spectral, Circular, 3D interaction network, Deferential diffusion, and the four constructions. Hub bands at 12, 4-11, and 1-3. |

## Contract

The bridge writes one query string and opens all three hosts with it.

`account`, `structure`, `intent`, `shape`, `view`, `model`, `q`.

Named selection set used by the bridge: holt\_igor, Grok Bot, Skindie 19, Robin Richardson 13, maro, AiofEffect, sierra catalina, Souls. maro and AiofEffect are the weight-12 hubs.

## Semantic customization

A query is scored against each sos model by token overlap, then biased by the selected structure and by hub weight. The top model is the customized feature. Empty search falls back to the selected structure and intent constraint.

## Limit

On 9 October 2026 the three hosts preserve the query string and do not apply it. The bridge is the selection surface until each app reads this contract. Netlify deploy was not run: existing sites are unrelated, and a new site requires confirmation. Cloudflare account mutation is not available on the connected docs surface.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.genesisconductor.io/documentation/intent-locality-handoff.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.