nx_connect_wards_lib.nx

nx_connect_wards_lib.nx -- WARD & BRANCH COMMUNITY groups, extracted as a shared library so the verifying gate (nx_connect_wards) and the LIVE app (nx_connect_serve /community) bind ONE implementation. Before this split the live page merely ASSERTED "this group holds no callings, records, attendance, or donations by construction" -- prose, with no registry actually enforcing it. THE BOUNDARY, enforced as data rather than promised in copy: a group's schema is a FIELD REGISTRY (rule 11) where every field carries a CLASS, and the community layer may carry ONLY class 0. A checker scans the registry and refuses any congregation-administration class. The same checker flags an incumbent-style ward-admin schema, which is what makes the boundary load-bearing rather than decorative. classes: 0=community-safe 1=calling 2=membership-record 3=attendance 4=ordinance 5=donation Joining is faith-revealing, so it requires explicit faith consent (GDPR Art.9 idiom): without consent the join is REFUSED and the person never appears in any roster. Joins are idempotent (rule 10). The youth-channel rule delegates to the ONE two-deep wall rather than re-deriving it here. license_tier: ORIGINAL