Recombination Risk Register¶
Risk register — instantiates Sequential Local Superiority
Tracks the leading signs that separated segments are beginning to reconnect, coordinate, or regenerate — before they combine faster than the sequence can resolve them.
The whole sequence rests on an assumption that can quietly expire: that the field stays separated long enough to beat one segment at a time. Recombination Risk Register is the standing log that refuses to take that assumption on faith. It enumerates the specific ways the separated parts could recombine — reinforcement, shared infrastructure, procedural aggregation, incident spillback, coalition formation — and tracks observable leading indicators for each, so the moment the field starts knitting itself back together shows up as a logged, owned signal rather than a nasty surprise. Its second half is a running estimate of the recombination window: how much time the current pace of those signals leaves before separation is lost. It is a watch-and-record instrument. It does not decide what to do when the window shortens — it makes the shortening visible and dated.
Example¶
A large e-commerce marketplace is working through a wave of fraudulent-seller clusters. It cannot ban them all at once without freezing legitimate merchants, so it resolves clusters in sequence. The recombination risk register tracks whether the separate clusters are turning into one coordinated ring: shared payout accounts appearing across clusters, identical listing templates propagating, the same appeal-letter language surfacing in different regions, spikes in cross-cluster referral traffic. Each indicator has an owner, a baseline, and a trend. When three of them move together, the register's window estimate — previously "weeks" — is revised to "days," logged with the date and the evidence.[n1] That entry does not itself launch a response; it hands the sequence owners a dated, evidenced warning that the field they were beating in detail is about to become a single adversary, so they can decide whether to accelerate, re-scope, or stop.
How it works¶
- Enumerate recombination pathways, not just events. For this field, list the concrete mechanisms by which parts could re-couple, each as a register line.
- Attach leading indicators with baselines. Every pathway gets observable early signals and a normal range, so a deviation is legible before the combination completes.
- Maintain a live window estimate. Convert the current signal trends into a time-to-recombination figure, revised as indicators move — the register's forward-looking output.
- Date and own every entry. Each signal carries an owner and a timestamp so the record is auditable and no warning dies in a meeting.
Tuning parameters¶
- Indicator sensitivity — how small a deviation trips a log entry. Sensitive settings catch recombination early but cry wolf; dull ones are calm until it is too late.
- Pathway breadth — how many recombination mechanisms are tracked. Broad coverage misses less but dilutes attention; narrow coverage is focused but blind to the pathway you did not list.
- Window-revision cadence — how often the time estimate is recomputed. Frequent revision tracks reality but whipsaws planning; infrequent revision is stable but stale.
- Escalation-vs-log threshold — how strong a combined signal must be before it stops being a log line and becomes a flagged alert handed upward.
When it helps, and when it misleads¶
Its strength is that it makes the sequence's core assumption falsifiable and dated: instead of hoping the field stays split, you watch the seams and get a timestamped warning when they start to close. It directly attacks the failure where partial wins evaporate because unresolved adjacent segments quietly reconnected while attention was elsewhere.
Its failure mode is the register that logs but never bites — a beautifully maintained list of yellowing indicators that no one converts into a decision, so recombination is documented in real time and prevented not at all. Registers also tend to track the pathways that are easy to instrument and miss the one that actually combines the field, breeding false calm. The classic misuse is treating a full, tidy register as evidence of control when it is only evidence of watching. The guarding discipline is that a shortening window estimate is wired to an owner with authority to act, and the register is periodically stress-tested by asking "which unlisted pathway would blindside us?"
How it implements the components¶
recombination_and_escalation_monitor— the register is the monitor: enumerated pathways, owned leading indicators, and dated observations of the field beginning to combine or escalate.recombination_window_model— the running time-to-recombination estimate is the working model of how long separation holds at the current signal pace.
It does not implement isolation_and_scope_boundary — declaring the boundary and closing aggregation channels is Scope Control Order's job; the register only watches whether the field respects it. And though it shares the monitoring signal with Safe-Stop and De-escalation Trigger, it does not implement ethical_legal_and_collateral_boundary: the register records the risk, but the rule that halts the sequence on ethical grounds is the safe-stop trigger's.
Related¶
- Instantiates: Sequential Local Superiority — supplies the early-warning watch that protects the recombination window the whole pattern depends on.
- Consumes: Scope Control Order declares the boundary this register then monitors for leaks.
- Sibling mechanisms: Scope Control Order · Safe-Stop and De-escalation Trigger · Local Overmatch Ratio Dashboard · Phase-Gate Resolution Review
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Recombination Risk Register operates by maintains an accumulating register of recoupling pathways, indicators, baselines, owners, and status. That concrete deployed or enacted form is Record, Log & Register under the frozen taxonomy.
Nearest alternative: Monitoring, Sensing & Alerting — Although Monitoring, Sensing & Alerting can support this mechanism, the frozen evidence makes its operative form the act that maintains an accumulating register of recoupling pathways, indicators, baselines, owners, and status; the alternative is therefore secondary rather than defining.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Military & Strategic Studies
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Specialized
Rationale: Tracking enemy reconstitution and recombination is a military campaign-planning concern.
Related originating lineages:
- Security Studies & Intelligence Analysis — Indicators-and-warning practice materially shapes leading-sign collection and escalation.
Review resolution: Both blind reviewers agree that military_strategic_studies is the primary origin. Explicit reconciliation of domain reach disagreement adopts reviewer_a's classification because tracking enemy reconstitution and recombination is a military campaign-planning concern. The resulting lineage records alternates=security_intelligence, origin_mode=cross_disciplinary_synthesis, and domain_reach=specialized; these describe formative provenance separately from later applicability.
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] In military terms, the danger being watched is the enemy's interior lines — the ability to shift and concentrate reinforcement between separated fronts faster than the attacker can exploit their separation. The register is the sensor that says whether the field's interior lines are getting shorter. ↩