Operating Band Specification¶
Document — instantiates Selectivity-Window Calibration
Translates the discovered window into a formal allowable range, setpoint, tiered table, or escalation rule.
A response curve on a chemist's laptop is a finding; it is not yet something a night-shift operator can act on. Operating Band Specification is the artifact that closes that gap: it freezes the discovered window into an authoritative, governed document — a nominal allowable range, a setpoint with tolerances, a tiered table of contexts, and the warning/stop actions that attach to each band — stamped with a version and a link to the evidence that justifies it. Its defining feature is not the numbers but the governance around the numbers: the specification is a controlled document, so the band can only change through change control, and every change leaves a dated, evidenced trace. It turns "we found the window here" into "this is the window of record, revision 4, and here is who may act outside it."
Example¶
A municipal water utility has to hold free chlorine residual inside a real window. Too low and disinfection fails — pathogens can break through the distribution system. Too high and residents complain about taste and odor, and regulated disinfection by-products (trihalomethanes) climb toward their legal ceiling. The specification codifies this as a governed document. The nominal band is 0.8–1.5 mg/L leaving the plant; a warning band opens at 0.6 and 1.8, prompting an operator check; above 2.0 or below 0.5 the plant must hold and notify the shift supervisor. A stratified table sets different targets for winter versus summer (temperature changes chlorine demand) and for far points of the distribution grid where residual decays. Each revision carries an entry in the version register: the effective date, the sampling study behind the change, and the approver. When a regulator asks "why 1.5 and not 1.8?", the answer is a document, not a memory.
How it works¶
- Choose the expression. Decide whether the window is best stated as a single allowable range, a setpoint with tolerances, a tiered table, or a decision escalation — matched to how the operators actually work.
- Set guard margins inside the raw bounds. Pull the nominal band in from the discovered edges so normal variation does not push operation past the true limits.
- Stratify by context. Where the valid window differs by season, subgroup, or location, publish a table rather than pretend one band fits all.
- Attach an action to each band. Nominal, warning, and stop/hold zones each get a defined operator response and an exception authority.
- Version and evidence-stamp. Every band and revision is dated, linked to its justifying study, and routed through change control.
Tuning parameters¶
- Guard-margin width — how far inside the raw bounds the nominal band sits. Wider margins are safer but sacrifice usable range and throughput.
- Expression form — single range vs. tiered table vs. setpoint. Richer forms fit heterogeneous contexts but are harder to follow and audit.
- Stratification granularity — how many context-specific rows the table carries. More rows protect edge contexts but raise governance burden.
- Change-control strictness — how much evidence and sign-off a revision needs. Strict control prevents casual drift but slows legitimate updates.
When it helps, and when it misleads¶
Its strength is turning a finding into one authoritative rule that many hands can follow and an auditor can trace — the difference between a band that is known and a band that is merely remembered. It is what makes accountability and consistent operation possible at all.
Its failure mode is the paper pretending to be evidence: a specification ossifies, and a band justified by a study three years stale is cited as if the world had not moved — or, conversely, production pressure quietly widens the operative band while the document stays put, so real practice creeps outside the validated critical process parameter.[n1] The classic misuse is invoking the spec as proof of safety long after the source water, feedstock, or population changed. The guarding discipline is to bind the document to live drift monitoring and honest change control, so the register reflects reality rather than merely outliving it.
How it implements the components¶
operating_window_rule— its core content: the nominal/warning/stop bands and the action each triggers.stratified_window_table— the per-context rows (season, location, subgroup) when one band cannot cover all conditions.window_version_register— the dated, evidence-linked revision history that makes each band traceable.
It records the band but does not discover it — selectivity_response_map, lower_selectivity_bound, and upper_selectivity_bound_and_reversal_guard come from Selectivity Curve Sweep — and it does not apply the band case-by-case with a route-to-review path, which is Selective Admission Band Protocol's fallback_or_nonselective_mode_guard.
Related¶
- Instantiates: Selectivity-Window Calibration — this document is where a discovered window becomes an operating standard.
- Consumes: Selectivity Curve Sweep supplies the response map and bounds this specification formalizes.
- Sibling mechanisms: Selectivity Curve Sweep · Challenge-Panel Cross-Reactivity Test · ROC or Precision–Recall Surface Review · Bycatch Audit · Window Drift Control Chart · Selective Admission Band Protocol
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Operating Band Specification operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it translates the discovered window into a formal allowable range, setpoint, tiered table, or escalation rule.
Independent corroboration: The frozen evidence defines Operating Band Specification as 'Translates the discovered window into a formal allowable range, setpoint, tiered table, or escalation rule', so its operative form is Rule, Policy & Commitment.
Nearest alternative: Representation, Specification & Plan — Operating Band Specification includes features of a static representation, map, specification, schema, or prospective plan that externalizes information, but its defining operation is a standing rule, threshold, contractual commitment, or policy constraint governing future conduct.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Operating Band Specification is most directly rooted in engineering and design's traditions of specification, testing, reliability, control, and physical-system construction. The lineage fits its defining practice: Translates the discovered window into a formal allowable range, setpoint, tiered table, or escalation rule.
Related originating lineages:
- Statistics & Experimental Design — Statistical process control materially shapes how bands are estimated, monitored, and justified.
Review resolution: Both independent reviews agree on primary origin engineering_design; reconciliation resolves alternate_origin_disagreement, origin_mode_disagreement. Formative alternate lineages retained: statistics_experimental_design. The broader reach of later applications is kept separate as domain_reach=multi_domain; origin_mode=cross_disciplinary_synthesis records how the formative lineages relate. Confidence is conservatively reconciled to high, and encyclopedia_synthesis=false preserves the reviewers' boundary judgment.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] A critical process parameter is one whose variation must be held within a stated range to keep output within specification; the discipline of documenting, justifying, and change-controlling that range is exactly what separates a governed band from an anecdote. ↩