Dominant Balance Table¶
Template — instantiates Dominant-Term Regime Modeling
A table that compares candidate terms, order classes, crossover points, retained status, and residual caveats.
Dominant Balance Table is a synthesis artifact, not an analysis engine: it is a fixed table layout — one row per candidate term, columns for order class, retained-or-dropped status, crossover, and residual caveat — that gathers a dominance judgment into a single reviewable page. Its distinctive discipline is bookkeeping. Every term that gets dropped must be written into the residual column rather than silently deleted, so the act of simplification leaves a visible audit trail: what was kept, what was set aside, and under what condition the set-aside item would have to come back. The table does not decide any of these things; it forces them all to be stated together, side by side, where an inconsistency (a term marked "negligible" that carries a safety flag) becomes obvious. It converts a scattered set of asymptotic judgments into one legible, defensible object.
Example¶
An operations lead is planning to scale a customer-support organization tenfold. She lays out the cost drivers as rows: front-line staffing (roughly linear in ticket volume), cross-team coordination and handoffs (superlinear as the number of teams multiplies), rare escalation handling (small in volume but severe per case), and tooling (largely fixed with occasional step upgrades). The columns force each row to declare its growth order, whether it is retained for the 10x decision, its crossover scale, and any residual caveat. Filled in, the table makes the governing story unmistakable: coordination — not the headline staffing line everyone worries about — dominates at 10x, while escalation handling is genuinely lower-order in volume yet is flagged in the residual column as a protected safety obligation that must not be dropped. The single page becomes the capacity plan's backbone.
How it works¶
- Enter one row per candidate term or cost driver.
- Fill the columns: candidate | order class | retained? | crossover | residual caveat.
- Require every dropped term to earn a residual-column entry, with a severity or protected-status tag where relevant.
- Cite, per order-class cell, the mechanism that produced it — so the table records evidence rather than assertion.
Tuning parameters¶
- Column set — which fields are mandatory; adding a "reintroduce-when" column strengthens the audit trail but raises the filling cost.
- Row granularity — lumping versus splitting drivers; finer rows expose hidden terms but invite false precision.
- Residual severity tags — whether the residual column carries plain notes or graded flags (routine / safety / rights); grading catches ethical elision but demands judgment.
- Sign-off field — whether a reviewer must initial the table; a gate raises accountability at the cost of speed.
When it helps, and when it misleads¶
Its strength is completeness under review: nothing is dropped off the record, and a second reader can check the whole simplification at a glance — the tabular form of the classical method of dominant balance[n1]. It is the natural place ethical residue gets caught before it disappears.
Its failure mode is garbage-in authority. A neatly filled table looks rigorous even when the order classes were guessed and the crossovers left blank; the format lends false precision to unsupported cells. The classic misuse is writing "retained / negligible" without any backing analysis. The guarding discipline is the citation rule — every order-class and crossover cell must name the ratio test, benchmark, or calculation that produced it, so the table stays a ledger of evidence rather than a ledger of opinions.
How it implements the components¶
dominant_term_candidate_set— the rows are the enumerated candidate set, held in one place.order_comparison_frame— the order-class column records each term's growth ranking.lower_order_elision_rule— the retained/dropped column is the elision rule made explicit, per term.residual_risk_register— the residual-caveat column is the register of what was discarded and why it may need to return.
It does not measure or prove any of the orders or crossovers it records — those numbers come from Ratio Limit Test and Scale-Sweep Benchmark; the table only tabulates their outputs.
Related¶
- Instantiates: Dominant-Term Regime Modeling — the artifact that makes a dominance judgment reviewable in one place.
- Consumes: Ratio Limit Test supplies the order classes; Scale-Sweep Benchmark supplies the crossover evidence.
- Sibling mechanisms: Big-O / Landau Notation · Ratio Limit Test · Log-Log Scaling Plot · Scale-Sweep Benchmark · Crossover-Point Calculation · Finite-Size Correction Check · Asymptotic Claim Review
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Dominant Balance Table operates as a non-executable information artifact that externalizes static or prospective structure because it a table that compares candidate terms, order classes, crossover points, retained status, and residual caveats.
Independent corroboration: The frozen evidence defines Dominant Balance Table as 'A table that compares candidate terms, order classes, crossover points, retained status, and residual caveats', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Mathematics
Origin pattern: Single lineage
Present-day reach: Specialized
Rationale: Asymptotic analysis cohered dominant balance: hypothesize which terms balance in a regime, drop smaller terms, and verify the neglected residual remains subordinate.
Related originating lineages:
- Engineering & Design — Perturbation methods use dominant balances to simplify engineering models by operating regime.
- Physics — Applied physics supplied canonical scaling and asymptotic uses of term-balance analysis.
Review resolution: Asymptotic mathematics cohered dominant-balance reasoning, with physics and engineering supplying canonical regime analyses; the table is an encyclopedia synthesis of that method.
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] The method of dominant balance is a classical technique in asymptotic analysis: to simplify a governing relation, one hypothesizes which terms balance in the regime of interest, drops the rest, and then checks the dropped terms are consistently smaller — the analytic practice this table operationalizes as an auditable layout. ↩