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 effective answer for a factor is this table overridden by that factor's boundary_profile, which is what factors_flat.boundary_scope already serves.