Point
Areas are overlapping Map-local questions
Areas route records within one Map through non-exclusive questions without creating hierarchy, ownership, or cross-Map identity.
- Posture
- asserted
- Lifecycle
- active
Each Area asks a narrower placement question inside its containing Map. A Point record can answer several Area questions, and matching Area identifiers in different Maps do not establish a shared Area. The containing Map therefore remains part of an Area’s identity in every consumer.
Membership is an explained semantic edge, not a bare routing tag. Every named Area carries a context sentence stating how or why that record answers, constrains, or materially affects the Area question. That explanation is itself a substantive contribution, so a context record can be bodyless when the Area edge carries all of its local meaning. Processors preserve the explanation; validation can require and resolve it but cannot prove that it is true or useful.
Area membership does not imply geometry, containment, exclusivity, ownership, or directory placement. An Area is justified when its question and explained edges help an author route real contributions or a reader inspect a recurring concern. It should be removed when it merely mirrors a folder or navigation label.
Maps and AreasArea questions subdivide a Map's routing without turning those local scopes into hierarchy or shared identity.