> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tythe.finance/llms.txt
> Use this file to discover all available pages before exploring further.

# Legal Agreements

> Every document you sign on Tythe, in the order you meet it: what it is, when it appears, who signs it, what it commits you to, and how it lives on-chain.

Every legally significant act on Tythe is paired with a signed document. You read it as prose, sign it with your operator key as a typed message, and its hash is stored on-chain in the thing it governs: your profile, an agent's binding, a mandate, a Loan. The prose says what you agreed. The chain proves that you agreed it. This page walks the six instruments in the order you meet them.

### How an instrument works

<Steps>
  <Step title="Rendered">
    Counsel writes a versioned template. Your specific parameters, the amounts, the agent, the counterparties, the term, are filled in and the document is rendered deterministically. The same parameters always produce the same bytes.
  </Step>

  <Step title="Signed">
    You sign a typed message containing the document's hash, the subject it governs, a nonce, and an expiry. Some instruments need a second signature: an agent's key, or a wallet consenting to be bound.
  </Step>

  <Step title="Recorded">
    The hash is stored on-chain in the object the instrument governs. The rendered document is stored by its hash, and a copy is kept by Tythe.
  </Step>

  <Step title="Verifiable">
    Anyone with the template version and your parameters can re-render the document, recompute the hash, and confirm it matches the chain.
  </Step>
</Steps>

Template text can never change after registration; a new version is a new template. What you signed means what it meant when you signed it.

<Note>
  The final text of each instrument is being drafted by counsel for the governing law of each launch market and will be linked here before launch. The summaries below describe what each covers and are not the instruments themselves.
</Note>

### 1. Account Agreement

|             |                     |
| ----------- | ------------------- |
| When        | Onboarding, once    |
| Who signs   | Your operator       |
| Recorded on | Your Entity Profile |

The terms of holding a Tythe Account. That you own your keys and your account and Tythe holds neither. That Tythe is a noncustodial protocol operator, underwriter, and information provider, and is not a custodian, bank, or asset manager. Your responsibility for your keys. The fee schedule. The dispute process. How Tythe may restrict service in a jurisdiction. Governing law.

### 2. Agent Authorization

|             |                                                 |
| ----------- | ----------------------------------------------- |
| When        | Each time you bind an agent                     |
| Who signs   | Your operator, and the agent's key as co-signer |
| Recorded on | The agent's binding on your Entity Profile      |

You appoint the named agent, identified by its ERC-8004 identity, as your agent. You accept responsibility for what it does within any mandate you issue to it. You warrant that you control its key. The agent's co-signature is evidence that the key is yours to authorise; it is not consent by a legal person, because an agent is not a party. Without both signatures and this instrument, no agent can be bound.

### 3. Delegation Instrument

|             |                                                                                                       |
| ----------- | ----------------------------------------------------------------------------------------------------- |
| When        | Each time you issue a mandate; each time an agent sub-delegates                                       |
| Who signs   | The issuing operator; for a sub-delegation, the parent agent's key, referencing the parent instrument |
| Recorded on | The mandate in the mandate registry                                                                   |

The mandate in prose. Budget and rolling period. Maximum per transaction. Counterparties. Permitted rails. Credit share and maximum tenor. Earn and lend authority. Expiry. Escalation threshold. Whether sub-delegation is allowed and to what depth. The values stated are the ceiling you granted; the instrument states that the effective value may be set below the ceiling by the Intelligence Layer and never above it. Revocation terms. A sub-delegation's instrument references its parent's, so the chain of authority is readable end to end.

### 4. Master Credit Agreement and Loan Schedules

|             |                                                                                                                                                 |
| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| When        | Your first draw, once; then one Loan Schedule per Loan                                                                                          |
| Who signs   | Your operator signs the Master Credit Agreement; each Loan Schedule is recorded under it when a Loan is drawn, with the drawing key as evidence |
| Recorded on | The Master Credit Agreement on your Entity Profile; each Loan Schedule on its Loan                                                              |

The credit terms that govern every Loan you or your agents draw. Governing law. That Loans drawn by your mandated agents bind you. The lien over a fraction of your account balance as a security interest. Capture of revenue-tagged inflows to the schedule. That rate and term are fixed at origination. The capped late fee and the absence of origination, application, and prepayment fees. Default, the loss waterfall, legal recourse, and how recoveries are unwound. Each Loan Schedule states the principal, rate, term, schedule, floor, lien amount, and capture parameters of one Loan.

### 5. Subscription Agreement

|             |                                              |
| ----------- | -------------------------------------------- |
| When        | Your first supply to the credit market, once |
| Who signs   | Your operator                                |
| Recorded on | Your Entity Profile                          |

The disclosures of lending. That you are supplying a pooled on-chain market and hold shares in it. The first-loss reserve and the waterfall order. The liquidity buffer and the redemption queue. That losses beyond the waterfall reduce share value pro-rata. Your representations as a verified participant. Risk of loss.

### 6. Data Consent

|             |                     |
| ----------- | ------------------- |
| When        | Bank-data opt-in    |
| Who signs   | Your operator       |
| Recorded on | Your Entity Profile |

The provider, the accounts and the data scope, the purpose (underwriting only), encryption and access limits, retention, and your right to revoke, with the purge window that follows.

## In the order you meet them

| Stage                             | Instrument                                    |
| --------------------------------- | --------------------------------------------- |
| Onboarding                        | Account Agreement                             |
| Binding an agent                  | Agent Authorization                           |
| Issuing a mandate                 | Delegation Instrument                         |
| First Loan, then every Loan       | Master Credit Agreement, then a Loan Schedule |
| First supply to the credit market | Subscription Agreement                        |
| Connecting a bank account         | Data Consent                                  |

## Verifying what you signed

Every signed instrument is shown in your console beside its hash. To verify one independently: take the template version and the parameters, both public; render them with the published renderer; hash the result with the template identifier and version. The hash matches the one on-chain, or the document is not the one you signed.

<CardGroup cols={2}>
  <Card title="Agreements" icon="gavel" href="/get-started/resources/legal-agreements">
    The same instruments from the legal side.
  </Card>

  <Card title="Operators and keys" icon="key" href="/principals/onboarding/operators-keys">
    The keys that sign them.
  </Card>
</CardGroup>
