Host & Listing Management · Documentation
Architecture
Host & Listing Management's pipeline, its owned data, the events it emits/consumes, and what is out of scope.
← Host & Listing ManagementWizard + KYC gate
The flow is a deterministic 7-step wizard. The KYC gate is deterministic per listing id (about 85% pass), emits kyc.decided, and sets whether the listing may go live; the go-live step emits listing.submitted with the resolved live flag. One metered AI-assist stage, listing-autofill, suggests the tagline / facilities / rate tip — Cloud claude-haiku-4-5 (cost-capped, fail-closed) or OSS qwen3:8b recorded on local M4 hardware at $0, prototype default OSS-only. The KYC decision itself is deterministic and $0.
Owned data, events + out of scope
The app owns demo_eco_c6_listing (partner, property, name, city, type, star, rooms, base rate, photos, facilities, wizard step, KYC state, live flag). One listing per shared property; about 78% seeded live, the rest mid-wizard. It emits kyc.decided and listing.submitted. The data invariant holds — owner writes canonical, a viewer's listings are credential-scoped, ephemeral, and reset-clearing (setWhere-guarded). Cost and trace live only in the inspector; no real imagery or PII. Stage-2 swaps the in-memory adapter for the Drizzle repository behind the same surface.