ValueLogics.aiWebROI · Registry Validation
Renewal Bindings · Legacy → Canonical Crosswalk
Montage Fields Resolved Against KV Registry v8.7.3
GP_KV_OBJECT_FIXTURES · object_registry.kv.json · data_dictionary.kv.json · kv_schema_v8_7_3.json
!
Does not match as-is: the montage uses legacy GP/WebROI (VB6-era) field names; the registry is the canonical KV dictionary v8.7.3. Most fields crosswalk cleanly to canonical terms; identity, roll-up, and certification resolve to objects; one real gap flagged.
The leaf names in the earlier manifest (companyname, latbauopex, totalOex…) are legacy — they are not term_ids in this registry. Use the canonical bindings below.
Registry: object_registry v1.0.0 · dictionary v8.7.3 · 352 terms / 12 categories
11 objects: tenant · party · client_member · portal_user · webroi_case · roi_watch · tensor_fact · drift · nba · proof · portal
Clean — maps to a canonical dictionary term
Derived — computed/composed from canonical terms
Object — resolves at the object level, not a merge field
Gap — no canonical term yet; decision needed
Gaps & decisions to close
- Events (BauFollowers / "BAU→Goal Events"): no
event term exists in the dictionary. Decision: add a governed event term, or map events onto an existing Product term. GAP
- Company identity (companyname): resolves at the object level — is the customer the
object.party or the object.client_member? Confirm which is the Renewal "Customer / Company".
- Certification: there is no
certification dictionary term. It resolves to object.proof (proof / proof_id / proof_rule). Confirm certification = the Proof object's issued output.
- Additional Revenue (totaddrev): no dedicated term; derived from
total_annual_revenue (goal − BAU). Confirm the derivation rather than a stored field.
- Enterprise roll-up total: resolves via
object.tensor_fact (fact_type formula_output) on object.webroi_case — the roll-up is a tensor fact, not a merge field.