Seed update: the fixture city amends its minimum-stay schedule

This is seed data. A fictional city has, in this seed, moved the one-night-minimum window for registered short-term rentals by one day.

Nothing about it is real; it exists so that the update route has a page to export and the article it names has a notice to show. Replace it with the first real update — a city ordinance, a platform fee change, a tax threshold — with the primary document as the source and the article it changes in Affects.

Until then the site shows this note under the seed article, labelled as what it is. What an update is for: a short, dated, sourced record that an answer moved, pointing at the page that now carries the answer.

Twelve months after its effective date it retires from the index and the article is the page to read. What a host would do with a real one: re-read the affected section of the article, note the effective date against their own calendar, and change the setting on the platform from that date and not before.

The note is deliberately short; the article is where the full reasoning lives, and it is the article that gets revised on the same day the note is published. The build holds this format to the same rules as an article where it matters — a named author, a primary source with its retrieval date, a second reviewer for any money or law claim — and to two rules of its own: a body between one hundred and fifty and six hundred words, and at least one article it changes.

This seed row exists to prove both; it should not outlive the first real update.