Skip to content

Scale-Adjusted Threshold Table

Decision table — instantiates Scaling-Exponent Calibration

Sets the action cutoff a metric must clear as a function of size, so the same rule bites correctly at every scale instead of one flat number.

A single flat threshold, copied across sizes, means one thing to a small entity and something entirely different to a large one. Scale-Adjusted Threshold Table replaces the flat number with a schedule: for each size band, the cutoff the response must clear is set by letting it scale with size according to the exponent. Cross the cutoff for your size and the action triggers; stay under it and it does not. Its defining move is turning the exponent into an action rule — a go/no-go boundary that rises or falls with size — not into a comparability index. It decides; it does not rank. Where a normalization index tells you who is efficient, this table tells you when to act.

Example

A banking regulator wants a capital surcharge that reflects the outsized systemic damage a large bank can do. A flat percentage of assets under-charges the giants, because the harm from failure grows faster than size. The regulator builds a table: for each size band — measured by a consolidated size indicator — the required surcharge is set to rise super-linearly with size, so the largest institutions face a materially higher buffer than a naïve per-asset rule would demand. A mid-size bank reads its band and finds a modest surcharge; a globally systemic one reads a steep one. The table is the enforceable artifact — size in, required buffer out — and it explicitly refuses to set a cutoff for sizes beyond the range the exponent was justified over.[n1]

How it works

  • Import the governing exponent. Adopt the exponent that sets how the cutoff scales with size, and record its source, rather than fitting it inside the table.
  • Derive the schedule. For each size band, compute the cutoff by scaling a base cutoff by size^b, yielding a rising (or falling) boundary rather than a constant.
  • Bind to the trigger. Attach the action — surcharge owed, inspection required, margin added — to crossing the size-appropriate cutoff.
  • Fence the range. Mark the sizes where the schedule is licensed and where it must fall back to case-by-case judgment.

Tuning parameters

  • Governing exponent — the b that shapes the schedule's steepness. A larger exponent makes the cutoff climb faster with size; getting it wrong systematically over- or under-regulates the extremes.
  • Base cutoff — the anchor value the schedule scales from. It sets the overall stringency independent of how the cutoff varies with size.
  • Band granularity — continuous formula versus discrete size brackets. Brackets are auditable and enforceable but create cliffs at band edges; a formula is smooth but harder to administer.
  • Hysteresis — whether an entity that dips just under its cutoff immediately exits the action, or must clear a margin, to stop thrashing near a boundary.

When it helps, and when it misleads

Its strength is that it makes a rule mean the same thing at every size: the same stringency of protection, staffing, or margin applies whether the entity is small or huge, instead of a flat number that is punishing at one end and toothless at the other. It is where the exponent finally changes an action.

Its failure mode is treating the schedule as settled once published: if the underlying exponent drifts or a regime boundary is crossed, a stale table applies confidently wrong cutoffs, and bracket cliffs invite gaming right at the edges.[n1] The classic misuse is exporting the schedule beyond the size range it was built for. The guarding discipline is to fence the valid range explicitly, re-derive the schedule when the exponent is revised, and prefer smooth or hysteretic boundaries where edge-gaming is a risk.

How it implements the components

  • scale_adjusted_decision_rule — it is the size-varying action rule: a cutoff schedule bound to a trigger, which is the table's reason to exist.
  • reference_exponent_source — it imports and records the exponent that shapes how the cutoff scales, rather than estimating one.

It does not produce a size-removal transform or reference size for fair comparison (normalization_baseline) — that comparability artifact is its nearest twin, Allometric Normalization Table; the one-line difference is that the normalization table makes different-sized values comparable, while this table sets the cutoff those values must clear to trigger an action.

Editorial Notes

Form Classification

Form family: Rule, Policy & Commitment

Rationale: Scale Adjusted Threshold Table operates by sets a standing schedule of size-adjusted cutoffs that governs future classification. That concrete deployed or enacted form is Rule, Policy & Commitment under the frozen taxonomy.

Nearest alternative: Analysis, Modeling & Optimization — Although Analysis, Modeling & Optimization can support this mechanism, the frozen evidence makes its operative form the act that sets a standing schedule of size-adjusted cutoffs that governs future classification; the alternative is therefore secondary rather than defining.

Review outcome: Adjudicated after independent review; high confidence.

Origin Attribution

Primary origin: Statistics & Experimental Design

Origin pattern: Cross-disciplinary synthesis

Present-day reach: Multi-domain

Rationale: Size-dependent decision thresholds are statistical normalization and scaling devices.

Related originating lineages:

  • Data Science & Analytics — Data science, analytics, and operational monitoring supplies a parallel or contributing lineage for the mechanism's defining operation: sets the action cutoff a metric must clear as a function of size, so the same rule bites correctly at every scale instead of one flat number.
  • Mathematics — Mathematical modeling, proof, and abstract-structure practice supplies a parallel or contributing lineage for the mechanism's defining operation: sets the action cutoff a metric must clear as a function of size, so the same rule bites correctly at every scale instead of one flat number.
  • Operations Research — Operations research, optimization, and queueing analysis supplies a parallel or contributing lineage for the mechanism's defining operation: sets the action cutoff a metric must clear as a function of size, so the same rule bites correctly at every scale instead of one flat number.
  • Public Administration & Policy — Administrative rules independently operationalize scale-sensitive cutoffs.

Review resolution: Both blind reviewers agree that statistics_experimental_design is the primary historical origin. Explicit reconciliation of alternate_origin_disagreement, origin_mode_disagreement starts from reviewer_a's mechanism-specific evidence: Size-dependent decision thresholds are statistical normalization and scaling devices. Reviewer A proposed alternates=mathematics, public_administration_policy, origin_mode=convergent, domain_reach=multi_domain, and encyclopedia_synthesis=true; reviewer B proposed alternates=data_science, mathematics, operations_research, origin_mode=cross_disciplinary_synthesis, domain_reach=multi_domain, and encyclopedia_synthesis=true. The final record retains every independently supported alternate from either review (mathematics, public_administration_policy, data_science, operations_research) without an arbitrary cap, selects origin_mode=cross_disciplinary_synthesis to represent the combined lineage evidence, and records domain_reach=multi_domain and encyclopedia_synthesis=true. Present-day transfer is recorded as reach and is not treated as proof of historical origin.

Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.

Review outcome: Reconciled after independent review; high confidence.

Notes

[n1] Size-based regulatory surcharges — for instance the higher loss-absorbency buffers required of larger, more systemically important banks under the Basel framework — embody exactly this logic: because the harm from failure scales faster than balance-sheet size, the required buffer is set to rise with size rather than being a flat ratio. The schedule is only as sound as the size-to-risk exponent behind it. ↩a ↩b