Read an association as a going concern
One card per owners association on the project -- membership as recorded, the current governing document, staged turnover, and what it maintains.
An association's own facts lived in the schema with nothing to read them: which lots belong to it, which covenants and rules are current, how far turnover has gone, and what it maintains. This page is that read, one card per association, master before its subs.
A card's lot count is exactly what is on record -- a lot in a sub and its master is two rows, and both counts include it. This page never walks the hierarchy to reconcile that down to one membership; expanding a card lists every member lot, with any other association it also belongs to, so the two-row shape is visible rather than something a reader has to trust the count on.
The current covenants and rules are the latest effective document not after today. A document dated in the future, or one a later document has superseded, is never shown as current.
Why it also lives here
Nothing else in the product reads this module. It was built with its schema, its RLS and its seed rows well ahead of a screen -- this page is that screen.
Who can
- Documents at view or better: anyone who can read documents.
How to
- One card per association, master before its subs. Membership is exactly what is recorded -- a lot in a sub and its master counts in both.
- Turnover happens in stages, sometimes years apart -- completed and pending are both listed, never inferred from one another.
Related pages
Known limits
Nothing here can be edited: no membership, no document, no turnover stage. Reading comes before forms, per the brief that shipped this page.