Policy Definition of Terms¶
Definitional specification — instantiates Predicate Criterion Formalization
Fixes the meaning of a labeled term by stating its domain and the property behind the label, so the same word can't drift across a document.
A Policy Definition of Terms fixes, in prose, what a labeled term means wherever it appears in a document: the kind of thing the term ranges over (its domain), the property that must hold for the label to attach (not merely the desired consequence), and the rule that keeps the term's meaning stable when it is combined with other defined terms. Its defining move is anti-smuggling: it forces "Personal Data," "Material," or "Eligible" to name a checkable property rather than a hidden decision, and it binds that meaning once so every downstream clause inherits the same criterion. Unlike a checklist, it does not process any particular candidate; it authors the meaning that other mechanisms then apply.
Example¶
A company's privacy policy repeatedly turns on the term "Personal Data," so a Definitions section pins it down. The domain is stated first — the term ranges over information relating to an identified or identifiable natural person, not to companies, aggregated statistics, or device telemetry that can't be linked to a person. The property is stated separately from the label: data is "Personal" if a living individual can be singled out from it, directly or in combination with other information the company holds — deliberately not "data we have decided to protect," which would smuggle the conclusion into the definition.
A composition rule then fixes behavior when the term nests inside others. "Sensitive Personal Data" is defined as a subset, so a later clause about "Personal Data" automatically covers the sensitive kind without a drafter restating it, and a provision that negates "Personal Data" cannot accidentally exclude the sensitive subset. Setup to outcome: a word that could have meant five things to five teams now names one property, scoped to one domain, that composes predictably across forty pages of policy.
How it works¶
- State the domain before the property. Name the kind of candidate the term applies to, so the same word isn't stretched onto unlike things.
- Define the property, not the outcome. Express what must be true for the label to attach — checkable in principle — without embedding the decision the label will later drive.
- Fix composition behavior. Specify how the term behaves under negation, subset/superset relations, and nesting with other defined terms, so combined clauses don't drift.
- Bind once, reference everywhere. The definition is authoritative; every use in the document inherits it rather than re-deriving a local meaning.
Tuning parameters¶
- Domain breadth — how wide the term's candidates range. Broad captures more but invites domain slippage; narrow is stable but may exclude relevant cases.
- Property sharpness — bright-line versus standard-like ("identifiable," with examples, versus a hard enumerated list). Sharper aids consistency; softer tolerates context.
- Inclusion / exclusion lists — explicit carve-ins and carve-outs versus relying on the abstract property. Lists reduce dispute but ossify.
- Composition scope — how many other defined terms this one is wired to (subsets, exceptions). More wiring buys precision at the cost of coupling.
When it helps, and when it misleads¶
Its strength is that it kills ambiguity at the source — one authoritative meaning that every clause, filter, and checklist downstream inherits, which is what makes the whole predicate reproducible.
Its failure mode is predicate laundering: a definition dressed as a neutral technical property that actually encodes a contested value choice, or one so vague a reader (or a court) finds it meaningless.[n1] The classic misuse is defining a term by its own desired consequence — "Confidential Information means information we wish to keep confidential" — which smuggles the outcome and defines nothing. The discipline that guards against this is to state the property separately from both the label and the consequence, and to pressure-test the wording against a handful of awkward examples before publishing (an informal sanity check, not the full boundary library a Test Case Matrix maintains).
How it implements the components¶
candidate_domain_statement— the definition opens by naming the kind of thing the term ranges over, blocking the same word from being applied to unlike candidates.property_definition— it states the property behind the label separately from the label and from any downstream consequence, defeating outcome smuggling.composition_contract— it fixes how the defined term behaves under negation, subset relations, and nesting with other defined terms, so combined provisions preserve the intended meaning.
It does NOT gather evidence about, or render a verdict on, any particular candidate — the per-case evidence_basis_rule and confidence_and_burden_rule that decide one applicant are Eligibility Criteria Checklist, which applies the meaning this definition fixes.
Related¶
- Instantiates: Predicate Criterion Formalization — the definition is the meaning-authoring instance, fixing the criterion the applying mechanisms inherit.
- Sibling mechanisms: Boolean Guard Clause · SQL WHERE Clause or Query Filter · Truth Table · Decision Table · Eligibility Criteria Checklist · Predicate Version Registry · Test Case Matrix · Counterexample Register · Unknown-State Routing Rule
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Policy Definition of Terms operates as a static representation, map, specification, schema, or prospective plan that externalizes information because it fixes the meaning of a labeled term by stating its domain and the property behind the label, so the same word can't drift across a document.
Independent corroboration: The frozen evidence defines Policy Definition of Terms as 'Fixes the meaning of a labeled term by stating its domain and the property behind the label, so the same word can't drift across a document', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Defined-terms sections are a longstanding legal-drafting device for fixing how a word operates within a governing instrument.
Related originating lineages:
- Linguistics & Semiotics — Linguistics and semantics supply the distinction between a label, its domain, and the criterion it denotes.
Review outcome: Independent reviewer agreement; high confidence.
Notes¶
[n1] The void-for-vagueness doctrine holds that a rule is unenforceable if an ordinary person cannot tell what it requires. It is the legal expression of the same demand this mechanism serves: a definition that fails to name a checkable property doesn't merely read badly — it fails to define anything at all, and a criterion built on it inherits the emptiness. ↩