> HISTORICAL DRAFT — This file predates the agent-only mint and fully on-chain art requirements. The NFT contract is not deployed, and owner controls remain undecided. Refer to the website status, not this file, for current launch status.

# Product Requirements

## Users
- Collectors who want a low-friction mint → hatch → collect loop.
- Agent users who want read-only inspection and guarded hatch preparation.
- Operators who need transparent deployment and monitoring.

## Core journey
1. Connect a browser wallet on BNB Smart Chain.
2. Review quantity, exact BNB cost, network, and contract address.
3. Simulate and confirm mint. Wait for confirmations.
4. See sealed egg with 24-hour countdown.
5. When ready, review hatch fee and confirm.
6. See pending state while Chainlink VRF fulfills.
7. See hatched character, rarity, variant, and validated metadata.
8. Transfer freely at any stage.

## Functional requirements
- Mint 1–10 eggs; mixed batches charge only paid portion.
- Enforce 10 cumulative mints per wallet and 5,000 supply.
- Hatch up to 10 ready eggs owned/approved by caller.
- Display sealed/ready/pending/hatched states from chain.
- Gallery filters: all, sealed, ready, pending, hatched; search by ID.
- Detail page: artwork, traits, owner, history, hatch action.
- Demo mode: 15-second incubation, local randomness, clearly not an NFT.
- Agent page: read-only assistant, capability table, BAW setup instructions.
- Docs page: owner powers, fixed terms, metadata CIDs, documentation pack.

## Non-functional requirements
- Responsive, accessible, reduced-motion friendly.
- No external font CDN; local fontsource fonts.
- Direct-chain ownership reads; optional indexer with on-chain revalidation.
- Same-origin RPC proxy with method allowlist and rate limiting.
- Distinguish wallet rejection, transaction failure, pending, and success.
- Never auto-submit transactions.

## Acceptance gates
- Contract tests green; callback gas under limit.
- Frontend typechecks and builds.
- Metadata CAR verified complete; pinning verified before mainnet deploy.
- Mainnet contract verified; sale closed until explicit launch.
- Audit/multisig/pinning gaps disclosed.