User Journey

The owner assembles a brief — property + content-type + voice + language — and runs generation. The pipeline gathers the property context, builds the brief, runs the metered generation stage, then runs QC and brand guardrails deterministically. The result is a draft body, a reading-ease score, and a (hopefully empty) list of brand flags. The owner edits until it reads well and passes the guardrail.

On publish (owner-gated), the approved copy is upserted into the shared core property_content store — the campsite-canon write — keyed by property and language, writing only the published field and leaving the other languages intact. The marketplace detail page then renders it, so the booking funnel and any app that reads property content sees the same published copy. The publish emits a content.published event on the live bus and writes an audit entry; a viewer's drafts stay credential-scoped and reset-clearing.