Motir

Add the clause that governs a customer connecting a domain — to the Acceptable Use Policy and, where the Terms allocate responsibilities, to the Terms — in motir-marketing/content/legal/, where the legal set now lives. Read both documents on origin/main FIRST and quote what is there; the deliverable is an EDIT, and "add X" asserts X is absent — if a clause already covers it, the card closes as verified-no-change with the quote.

What the clause must cover (drafted from the mirrors' terms, cited)

• Control and authority — the customer represents that they control the domain and are authorised to point it at the service and to have certificates obtained for it on their behalf (Notion and Canny each require the customer to own the domain they connect).
• Naming — a tenant subdomain label or a customer domain may not impersonate another person or organisation, infringe a mark, or be misleading; Motir may refuse or reclaim a label in the reserved set or on a substantiated complaint, and may retire a domain that stops resolving to the service.
• What Motir does — obtains and renews a TLS certificate for the hostname through its hosting provider, serves the customer's PUBLIC project content there under the same public-content rules that apply on motir.co, and may suspend an address that violates the policy.
• What it does not change — the content rules, the takedown path and the data-processing terms are unchanged by the address a page is served at; no new subprocessor (Fly already appears on the published list — marketing-site-hosting.md §5).

Materiality: MOTIR-4133 established the guard that a Terms revision is READ before it ships — run the repository's materiality check for the changed documents and record its output on the PR; a new obligation on the customer is material and needs the revision date and re-consent treatment the manifest prescribes (motir-core/lib/legal/reconsentGate.ts reads the manifest motir-marketing publishes — say in the PR whether this revision triggers re-consent, and why).

Acceptance criteria

• The AUP (and the Terms, if the responsibilities section is where the mirrors put it) carries the four points above in Motir's legal voice; the PR body quotes the pre-change text of each touched section to show the gap was real.
• The documents' revision metadata is updated per content/legal/'s own convention, and the materiality check the repository ships is run with its output in the PR body.
• The PR states whether the revision is re-consent-triggering under the manifest rules, with the reasoning, and no code outside content/legal/ (and its manifest, if the convention requires a version bump there) changes.
• No file outside motir-marketing is touched.

Context refs

• motir-marketing/content/legal/acceptable-use.md · the Terms document in the same directory · lib/legal/documents.ts (the manifest and revision fields) · tests/legal/legalMateriality.test.ts
• MOTIR-4133 — the materiality guard; MOTIR-3909 — the configured manifest motir-core reads
• motir-core/docs/decisions/marketing-site-hosting.md §5 — Fly on the subprocessor list already
• the decision — Q4 (ownership proof), Q7 (reserved and impersonation), Q10 (branding)
• Notion terms for Sites custom domains and Canny's terms of service — the customer-owns-the-domain representation, for wording