# Nova Reserva

> Short-term rental operations in Rio de Janeiro: property owners find verified cleaning
> professionals, and the turnover between one booking and the next is organised, tracked and
> evidenced in one place. Bilingual, pt-BR and en.

## Read this first

The product runs on real accounts against a real database. Demo mode is off. What is still example
data, and labelled as such wherever it appears: the product screenshots on the marketing pages, and
the cleaner profiles a visitor sees before signing in. There are no customer testimonials on the
site at all — the section exists in code and renders nothing until real reviews with consent are
collected, because the product has not earned them yet. No rating, review count or completed-job
figure is published anywhere.

Everything below describes what the software does today. Where something is not built, it says so.

## How a job works

1. A host says where, when and what kind of cleaning. She sees profiles with an identity that has
   been checked and reviews that can only come from completed jobs.
2. She sends a request. **It becomes a booking only when the cleaner accepts, and declining costs
   the cleaner nothing.** This is requirement J2 in the PRD — a legal requirement rather than a
   design choice — and it holds on every path: automatic and direct assignment offer the job, they
   never accept it on her behalf. `lib/core/j2-guard.test.ts` guards that.
3. The full address appears only after the cleaner has accepted. Before that she sees the
   neighbourhood and the property type.
4. The cleaner checks in and works through a mandatory checklist. On a turnover she photographs
   four named rooms; on a recurring clean four photographs are required without fixed rooms. The
   delivery does not close until the list and the photographs are complete.
5. The host approves by looking at the photographs. If she does not, a reminder goes out at 24
   hours and the delivery approves itself at 72 (`lib/core/approvals.ts`), so a cleaner is never
   left waiting on a host who has stopped answering.

## What the platform does and does not decide

- The cleaner sets her own price, from a floor per property category. The platform never sets it
  for her and never takes a percentage from her.
- A platform fee exists in the code — 5 percent of the amount with a minimum of R$ 8, charged to
  the host, in `lib/pricing.ts`. **The pricing model is being decided and nothing about it is
  published.** The pricing page and the payments feature page both return 404 on purpose, and no
  marketing page states a fee. Treat the number in the code as the current implementation, not as
  an announced commercial term.
- Payments are simulated end to end. There is no payment provider behind them yet.

## Beyond a single job

Own checklists per property, an inventory the cleaner counts during the job, issues and maintenance
logged against the booking, a primary and a backup cleaner per property, messages tied to a property
or a job, and reports a host can download as CSV or JSON.

## The pages a visitor can open

Bilingual under `/pt` and `/en`.

- `/` is a fork: one screen, two doors, one for a property owner and one for a cleaner.
- `/anfitrioes` and `/diaristas` carry the whole argument for one side each.
- `/encontrar-profissionais`, `/administradoras`, `/recursos/<feature>`, `/sobre`, `/casos`,
  `/guias`, `/integracoes`, `/ajuda` and `/contato` are the rest of the marketing site.
- `/summit` is a standalone event page: a sixty-second film, the argument in three cards, and a
  waitlist form. It is `noindex` and not in the sitemap — it exists to be reached from a QR code
  at a specific event, not from search.
- `/login` is the way in, by one-time code with no password; `/cleaner/onboard` is where a cleaner
  signs herself up, behind that login.

Held back on purpose, and answering 404 rather than redirecting: `/precos` and
`/recursos/pagamentos`. Both describe a pricing model that is under review.

## Where it runs

Rio de Janeiro, Zona Sul. The search covers Copacabana, Ipanema, Leblon, Botafogo, Flamengo and
Leme. The launch plan puts Copacabana and Ipanema in phase 1 and the other four in phase 2
(PRD 4.3).

## Not built yet

Real payments through a provider, identity verification by a third party rather than by an admin
reading a document, and WhatsApp communication with guests. Linen, supplies, maintenance, access
and payments as services in their own right are a direction rather than a roadmap: nothing about
them is built, and the marketing pages no longer mention them.

## Pages

- /pt and /en: choose your side, host or cleaner
- /pt/anfitrioes and /en/anfitrioes: everything the product does for a host
- /pt/diaristas and /en/diaristas: everything it does for a cleaner
- /pt/encontrar-profissionais: search the published profiles without an account
- /pt/summit and /en/summit: the event page, with the film and the waitlist
- /pt/login: sign in with a one-time code, no password
- /pt/cleaner/onboard: where a cleaner creates her profile