Tier T1 · Config Usage

Configuration: is the platform's config carrying its weight?

Every configured attribute field, measured by how often it actually holds data, so dead and sparse config, mixed representations, and duplicate field names surface as evidence, not opinion.

How to read this page

What this measures

Fill rate of every configured attribute field across the book, plus structural defects (mixed value representations, duplicate field names).

How to read it

Fields bucket by how populated they are: core (well used), moderate, sparse, and dead (never populated). Dead and sparse are highlighted.

Why it matters

Dead and sparse config is friction: it clutters forms, confuses users, and hides the fields that carry the real signal.

Watch for

A field can be legitimately dead (deprecated, or for a work type you do not run). The count is a review queue, not a delete list.

39Domain health / 100

95Dead fields

94Sparse fields

17Core fields

The evidence

Field fill-rate buckets across 287 configured attribute fields (dead/sparse highlighted).

Core Fields · 17Moderately Used Fields · 81Sparse Fields · 94Dead Fields · 95

The same buckets as a share of the whole configured field set.

Read honestly: fill rate is an observed measure. It counts populated rows; it does not judge whether a field should be populated. Treat dead and sparse fields as a configuration-hygiene review queue, not a verdict.

From the live engagement

On the live engagement this pipeline grew from, the attribute store carried exactly these defect shapes: the same concept stored as a literal boolean and an option-set code, duplicate field names, and per-party bespoke fields. Treated as findings rather than noise, they became the configuration clean-up backlog.

Findings

Severity	Finding & evidence	Metric
high	1 attribute stores values two different ways at once (a literal boolean AND a numeric option-set code). Evidence (`config_usage/mixed-representation`) { "fields": [ "matter-active-flag" ] }	1
medium	95 of 287 attribute fields are never populated (0% fill rate). Evidence (`config_usage/dead-fields`) Showing 50 of 95 dead fields. The list is capped so the page stays readable; the count beside it is the whole population, not the length of this list. { "fields": [ "fb-field-008", "fb-field-021", "fb-field-024", "fb-field-027", "fb-field-043", "fb-field-049", "fb-field-051", "fb-field-056", "fb-field-068", "fb-field-072", "fb-field-113", "fb-field-125", "fb-field-134", "fb-field-146", "fb-field-161", "fb-field-170", "fb-field-171", "fb-field-172", "fb-field-173", "fb-field-174", "fb-field-175", "fb-field-176", "fb-field-177", "fb-field-178", "fb-field-179", "fb-field-180", "fb-field-181", "fb-field-182", "fb-field-183", "fb-field-184", "fb-field-185", "fb-field-186", "fb-field-187", "fb-field-188", "fb-field-189", "fb-field-190", "fb-field-191", "fb-field-192", "fb-field-193", "fb-field-194", "fb-field-195", "fb-field-196", "fb-field-197", "fb-field-198", "fb-field-199", "fb-field-200", "fb-field-201", "fb-field-202", "fb-field-203", "fb-field-204" ], "evidence_sample": { "noun": "dead fields", "shown": 50, "total": 95, "truncated": true, "limit": 50, "convention": "evidence-sample-limit" }, "total_fields": 287 }	95
medium	5 logical field names are stored under 10 distinct raw keys. Evidence (`config_usage/duplicate-field-names`) { "groups": { "reserveamount": [ "ReserveAmount", "reserve-amount" ], "claimstatus": [ "ClaimStatus", "claim-status" ], "lossdate": [ "LossDate", "loss-date" ], "solicitorref": [ "SolicitorRef", "solicitor-ref" ], "policynumber": [ "PolicyNumber", "policy-number" ] } }	5
low	94 fields are populated in fewer than 5% of work items. Evidence (`config_usage/sparse-fields`) Showing 50 of 94 sparse fields. The list is capped so the page stays readable; the count beside it is the whole population, not the length of this list. { "fields": [ "fb-field-070", "fb-field-071", "fb-field-073", "fb-field-074", "fb-field-075", "fb-field-076", "fb-field-077", "fb-field-078", "fb-field-079", "fb-field-080", "fb-field-081", "fb-field-082", "fb-field-083", "fb-field-084", "fb-field-085", "fb-field-086", "fb-field-087", "fb-field-088", "fb-field-089", "fb-field-090", "fb-field-091", "fb-field-092", "fb-field-093", "fb-field-094", "fb-field-095", "fb-field-096", "fb-field-097", "fb-field-098", "fb-field-099", "fb-field-100", "fb-field-101", "fb-field-102", "fb-field-103", "fb-field-104", "fb-field-105", "fb-field-106", "fb-field-107", "fb-field-108", "fb-field-109", "fb-field-110", "fb-field-111", "fb-field-112", "fb-field-114", "fb-field-115", "fb-field-116", "fb-field-117", "fb-field-118", "fb-field-119", "fb-field-120", "fb-field-121" ], "evidence_sample": { "noun": "sparse fields", "shown": 50, "total": 94, "truncated": true, "limit": 50, "convention": "evidence-sample-limit" }, "threshold": 0.05 }	94
info	17 fields carry meaningful data (>= 50% fill rate). Evidence (`config_usage/core-fields`) { "fields": [ "fb-field-000", "fb-field-001", "fb-field-002", "fb-field-003", "fb-field-005", "fb-field-006", "fb-field-007", "fb-field-010", "fb-field-011", "fb-field-012", "fb-field-013", "fb-field-014", "fb-field-015", "fb-field-016", "fb-field-017", "fb-field-018", "fb-field-019" ], "evidence_sample": { "noun": "core fields", "shown": 17, "total": 17, "truncated": false, "limit": 50, "convention": "evidence-sample-limit" }, "threshold": 0.5 }	17

Health methodology (disclosed)

Domain score: 38.9/100. A weighted band average (green=1, amber=0.5, red=0), with full inputs below.

Indicator	Value	Band	Green	Amber	Weight
Dead Field Ratio	0.331	amber	0.1	0.4	2.0
Mixed Representation Ratio	0.003	amber	0.0	0.01	1.5
Duplicate Field Name Ratio	0.017	red	0.0	0.015	1.0

Continue the reportNext: Lifecycle →