# Organization Ownership Transfer

## Objective

Hand a workspace to another member without breaking billing or access.

A two-sided transfer flow where the current owner offers ownership and the recipient explicitly accepts it.

## Before You Begin

This feature is being added to an application that already exists and already
works. Do not scaffold a new project, and do not assume a blank slate.

Inspect the codebase first and establish:

- The existing application structure and where code of this kind already lives.
- The framework and version in use.
- The existing design system — colours, spacing, typography, and component conventions.
- Existing UI components you can reuse instead of writing new ones.
- The existing database structure, if this feature needs to persist anything.
- The existing authentication and authorization system, if this feature is user-scoped.
- Dependencies already installed, so you don't add a library that duplicates one.
- The existing test setup and conventions.

Only start writing code once you understand the above. If the application
already implements part of this feature, extend it rather than replacing it.

## Implementation Instructions

1. Make the transfer two-sided: the current owner initiates, the recipient accepts. Ownership must never land on someone who did not agree to it.
2. Require recent re-authentication from the initiating owner, and verify the recipient is an active, verified member of the organization — not an invitee, not a suspended account, not an external guest.
3. List everything that moves before confirmation: billing responsibility, payment method, privileged integrations, API credentials, and any owner-only settings.
4. Handle billing deliberately. Either the recipient supplies a payment method as part of accepting, or the transfer stops short and the old owner stays on the hook until they do — never leave a subscription with no payer.
5. Guarantee the organization always has at least one owner. Block the last owner from leaving, downgrading, or deleting themselves until a successor exists.
6. Do NOT quietly demote the outgoing owner to nothing. Give them a defined role, and tell them what they lost.

## UI and UX Requirements

Match the application's existing design system exactly. Reuse its components,
spacing, and typography. This feature should look like it was always there.

## Responsive Requirements

Works on mobile, tablet, and desktop. Touch targets are large enough to hit on a
phone, and nothing overflows horizontally at 320px.

## Accessibility Requirements

- Fully keyboard navigable.
- Correct semantic elements and ARIA roles.
- Visible focus states.
- Meets WCAG AA contrast.
- Dynamic changes are announced to screen readers.
- Respects prefers-reduced-motion.

## Edge Cases

- A pending transfer must expire, and must be cancellable by the initiating owner until it is accepted.
- If the recipient is removed, suspended, or leaves before accepting, the transfer must void rather than complete against a dead account.
- Integrations and API keys authorised by the old owner will keep working under their identity — either re-authorise them under the new owner or list them as needing attention.
- Two concurrent transfer offers must not both succeed; a single pending transfer per organization is the simplest safe rule.
- The change must be audited and both parties emailed, including a notice to other admins.
- Transfer must be blocked while the organization is mid-deletion or has a failed payment in dispute.

## Testing

Exercise the feature end to end in the running application. Cover every edge case
above, then run the existing test suite and confirm nothing regressed.

## Acceptance Criteria

- [ ] Ownership only changes after the recipient explicitly accepts.
- [ ] The initiating owner re-authenticates and the recipient is verified as an active member.
- [ ] Billing responsibility and privileged integrations are transferred or explicitly flagged, never left ownerless.
- [ ] The organization can never reach a state with zero owners.
- [ ] Pending transfers expire and can be cancelled.
- [ ] The transfer is audited and both parties are notified.
- [ ] The feature matches the existing design system.
- [ ] No existing functionality is broken.

## Adaptation Rules

- Match the existing design system. Do not introduce a new colour palette,
  spacing scale, or component library.
- Reuse existing components and utilities wherever they fit.
- Follow the naming, file layout, and code style already present.
- Do not upgrade, replace, or remove existing dependencies to make this
  feature fit. Adapt the feature to the app, not the app to the feature.
- Do not break existing functionality. If a change is genuinely required in
  existing code, make the smallest one that works and say so.
- If something in these instructions conflicts with how the application is
  built, follow the application and explain the deviation.

## Final Verification

Before you report the work as done:

1. Re-read the acceptance criteria above and check each one against what you
   actually built.
2. Run the application and exercise the feature end to end.
3. Run the existing test suite and confirm you have broken nothing.
4. Check the feature on mobile, tablet, and desktop widths.
5. Check keyboard navigation and focus handling.
6. Summarize what changed: files added, files modified, and anything you
   deliberately did differently because of how this application is built.

If any acceptance criterion is unmet, fix it before reporting completion.