The system_boundary_scope table
The machine-readable includes/excludes of each boundary: one row per (boundary, term) with its disposition, in, out or varies.
Fields#
| field | type | required | example | meaning |
|---|---|---|---|---|
boundary_code |
text | yes | Which boundary this row is about. | |
term_code |
text | yes | Which boundary question this row answers. | |
disposition |
text | yes | in / out / varies ('varies' = genuinely publisher-dependent at this boundary, so the per-factor boundary_profile is the only authority) | |
note |
text | Why we read the definition this way (a standard clause, a methodology page). |
Notes#
These are the defaults, the last layer a factor's answer falls back to. The effective answer for one factor is, most specific first: the factor's own boundary_profile, then publisher_boundary_scope for its sub-category, its category and its whole library, then this table. factors_flat.boundary_scope serves that answer, and boundary_scope_source names the layer that gave it.
varies means the boundary alone cannot say, because publishers draw it differently. It is a statement about the boundary, never about a factor: where no more specific layer settles a varies term, the factor reads not_stated, which names the gap instead of hiding it.