Documentation: reading order

1. Concept — Who the product helps and the two agent roles.

2. Product and screens — Connect, app, chat and proposed pricing.

3. Architecture and protocol — Service boundaries, Agentfy context and the current REST 1.0 contract.

4. Delivery plan — Implementation sequence, owners and the two-week schedule.

5. Reference and archive — Market evidence, decisions and superseded exploratory documents.

The protocol is a development contract, UI screens are interactive prototypes, and plan dates are targets. These labels do not establish production readiness. The archived drafts and contracts/ artifacts must be reconciled with REST 1.0 before implementation; do not treat the old v2 files as the current wire contract.