# Integrating ThetaHerd

The infrastructure host follows Theta AMM's independent frontend and shared
service pattern. Cow and Cattle are distinct protocols; branding does not make
their contracts interchangeable.

## Product choices

1. Cow or Bull is the strategy decision.
2. Choose the assets and chain.
3. Cow can use fully funded or Aave collateral when that exact pair is supported.
   Bull currently uses Aave collateral only.
4. Choose the price, amount and schedule.
5. For Cattle, create and fund before offering optional borrowing.

The first study uses sample wstETH / USDC on Base to show Aave availability,
plus WETH / USDC to demonstrate an unsupported Aave choice. These are design
examples, not a new market admission list. Live availability must come from
configured deployments and current reserve checks.

## Preserve what works

From Cow: holding-first inputs, an explicit user strike and date, token identity
by address and chain, direct access to positions, and clear sample mode.
From Cattle: external wallets, separate creation and funding, optional debt,
repay/withdraw/roll actions, actual supplied assets, and health against price.

Read each generation's current deployed interface and fee rules. Never infer
the fee recipient from the position owner. The current Cattle protocol fee is
paid to the protocol. Old contracts retain their original immutable settings.

Cow does not support an in-place switch into a Cattle position. A future guided
move must close and reconcile the actual token mix, then create and fund a new
position with a fresh review. Cattle rollTo is a different contract action with
eligibility, debt preparation and activation requirements.

## Domain direction

- herd.thetanuts.finance: infrastructure and this published design study.
- thetaherd.com: proposed consumer home and unified selector.
- cow.thetaherd.com and cattle.thetaherd.com: optional future deep links.
- bull.thetaherd.com: reserved proposal, not a released fully funded Bull.

The user's spelling thetahard.com is treated as a naming typo in this study.
No consumer domain or subdomain is configured by this infrastructure release.
Separate subdomains do not share localStorage or an automatic wallet connection.
Prefer one origin for the eventual app; aliases can link to a preselected route.

## Implementation status

The pasture and builder are interactive design prototypes. All amounts are
labelled sample inputs; no wallet, live quote, order, creation or borrowing
transaction is wired. The gateway reads existing sources and does not change
their databases, cron, cache, routes or frontend clients.