> For the complete documentation index, see [llms.txt](https://docs.builtbydao.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.builtbydao.com/housing-loyalty/portability.md).

# Portability

Housing Loyalty credits are portable because they stay soul-bound to the member rather than to one lease or property.

## What follows the member

* the confirmed Housing Loyalty credit balance;
* its provenance and transaction history; and
* eligibility to use an enabled lane when that lane's rules are satisfied.

## What does not transfer automatically

* a lease or right to occupy another property;
* an application, income review, deposit, or underwriting decision;
* the old property's Housing Loyalty rate;
* a place in a purchase or financing program; or
* Contributor-house voting power.

A new property has its own availability, application, signed lease, qualifying amount, and 5–15% rate. Existing credits remain with the member, while new Housing Loyalty issuance uses the new lease's stamped rate.

Leaving the network does not convert the balance to cash. The member can use it later only through then-available approved lanes.

{% content-ref url="/pages/OiWYwch32aM3GCGK7BHh" %}
[Housing Loyalty](/housing-loyalty/equity-leases.md)
{% endcontent-ref %}

{% content-ref url="/pages/NZzCduUn7eUsIO6NlvkJ" %}
[What Credits Represent](/housing-loyalty/ownership.md)
{% endcontent-ref %}


---

# 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.builtbydao.com/housing-loyalty/portability.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.