Explain Cohort

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

pipeline / stage — CBDeal.pipeline_id and .stage_id are real PostgresUUID columns, so a non-UUID can only ever fail open.

pipeline / stage — CBDeal.pipeline_id and .stage_id are real PostgresUUID columns, so a non-UUID can only ever fail open.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

rec_type / audiences — Lead.rec_type is SmallInteger and audience_id is Integer; both appliers coerce and skip what will not parse.

rec_type / audiences — Lead.rec_type is SmallInteger and audience_id is Integer; both appliers coerce and skip what will not parse.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.

headcount — a CLOSED vocabulary (HEADCOUNT_BANDS), and the exact list /filter-options hands the client.

grading_bucket — a CLOSED vocabulary (GRADING_BUCKETS). An unknown bucket produces no band clause and widens to the full book.

objections — codes live in the PER-ORG cb_objection_codes catalog, so only the SHAPE can be checked here. Blank is the one thing the applier provably cannot use.

One filter group — list of values + optional NOT toggle.

in_ is capped at MAX_FILTER_VALUES_PER_GROUP items of MAX_FILTER_VALUE_LENGTH characters each. Over-cap input raises during body parsing, so FastAPI answers 422 with the offending group named in detail[].loc (["body", "<group>", "in"]) and the cap in detail[].msg — no handler code, and therefore no SQL, runs.

THIS SHAPE DOES NOT NEST. in_ holds scalars and there is no group-of-groups member, so a caller cannot vary the tree depth: it is fixed at 2 (query -> group -> values) by construction, and extra="forbid" on both models keeps it that way. A depth check here would be validation that can never fire. Add one WITH the member that introduces nesting, not before it.

Do not confuse this with SegmentFilterGroup (contacts/domain/value_objects/ag_grid_models.py:111), which IS recursive and is where AC-3's "tree depth" belongs. Different model, different route, still unbounded — see the scope note above the constants.