clmSpace
Documentation
Concepts

Scope dimensions

A standard position for liability under a US-NY MSA you sell is not the same as one for an EU DPA you buy. Scope is how the playbook keeps those straight.

The scope keys

Every entry in your playbook, whether a standard position or a clause, carries a scope object. None of the dimensions are required; missing dimensions are wildcards.

KeyValuesNotes
agreement_typeMSA · SOW · NDA · DPA · OrderForm · OnlineTerms · Variation · OtherMirrors the extractor’s recognised types.
party_rolevendor (you sell) · customer (you buy) · mutualDerived from agreement direction.
jurisdictionEW · UK · EU · US-CA · US-NY · US · …ISO-style codes; freeform, but stick to a consistent list.
deal_size_band<25k · 25k-250k · 250k-1M · >1MSizes a position to the value of the deal; the scorer reads it like any other key.
data_sensitivitynone · personal_data · sensitive_personal_data · regulatedTunes a position to the kind of data in scope.

How resolution works

When clmSpace needs to know “what is the standard liability position for thisdeal?”, it scores every candidate entry by specificity (number of scope dimensions that match the context) and picks the winner. Ties break by tier authority: User > AI > Market.

Example

text
context = { agreement_type: "MSA", party_role: "vendor", jurisdiction: "US-NY" }

candidates:
  - {} (wildcard)                          → score 0
  - { agreement_type: "MSA" }              → score 1
  - { agreement_type: "MSA", jurisdiction: "US-NY" } → score 2  ← winner
  - { agreement_type: "DPA" }              → 0 (rejected: doesn't match)
Missing context kills a constrained entry
If an entry constrains jurisdiction = US-NY but the current context has no jurisdiction, that entry is rejected (the platform refuses to guess). Wildcard entries are the safe fallback. This is why a sparsely-scoped playbook still works.

Sizing and sensitivity dimensions

deal_size_band and data_sensitivity let you tune a position to the value of the deal and the kind of data in scope. The scorer treats them like any other scope key, so a Tier 1 liability position for a high-value, regulated-data deal wins over a broader wildcard the moment you set them.

Related