Find your next learning step
A permanent authority cap is an operating boundary, not a label placed on a rule and forgotten. The cap must be monitored against the topology, evidence lineage and decisions that justified it. A breach can occur when the rule is used outside the permitted manifold, when repeated promotion attempts leak higher authority or when shared evidence contaminates several descendants. Escalation then asks whether one deployment should stop or the whole rule family has lost a defensible boundary.
Open the chapter contents · Topology root · Gold Standard of Education · How X Works
Chapter contents
Choose the route closest to the decision, or read from Chapter 1. The chapters remain open; these grouped routes are a navigable index.
Route 1 · Define the decision
Route 2 · Work the ledgers
Route 3 · Transfer the method
Route 4 · Check limits and evidence
Route 5 · Ask and continue
CHAPTER 1 OF 12 · DEFINE THE DECISION
1. Write the permanent cap as an enforceable boundary
Name the eligible problem class, topology assumptions, evidence lineage, maximum decision role, prohibited uses, monitoring statistics and stop conditions. A phrase such as “advisory only” is too weak unless the interface and operating procedure prevent automatic action.
Version the cap with the rule. Any change to neighbourhood construction, feature scaling, active-manifold detection or evidence source should trigger a review of whether the former boundary still applies.
CHAPTER 2 OF 12 · DEFINE THE DECISION
2. Define a cap breach before it occurs
A breach may be technical, operational or evidential. Examples include issuing an automatic switch when only an alert is authorised, applying the rule beyond the validated stratum or reusing quarantined evidence in a descendant rule.
Set severity levels and clocks. A critical automatic-action breach stops the rule immediately; a low-consequence logging defect may permit bounded continuation while it is repaired and independently checked.
CHAPTER 3 OF 12 · WORK THE LEDGERS
3. Build an authority-cap monitoring register
A solver uses rule family R7 to recommend when an active manifold appears stable. Permanent authority is capped at advisory recommendations after prior recurrence.
| Monitor | Boundary | Observed event | Classification | Immediate action |
|---|---|---|---|---|
| Decision role | Advisory output only | One workflow auto-applies switch | Critical cap breach | Disable integration |
| Topology support | Validated strata A and B | Use in unvalidated stratum C | Scope breach | Quarantine results |
| Lineage | Fresh post-retirement evidence | Old wealth record imported | Evidence breach | Freeze family |
| Alert rate | At most 3 per 1,000 runs | 2.2 per 1,000 | Within cap | Continue |
| Rollback | Restore base solver in 5 minutes | Drill completes in 3 minutes | Pass | Fallback ready |
The low alert rate does not offset the authority breach. Metrics answer different questions and cannot be averaged into a global pass.
CHAPTER 4 OF 12 · WORK THE LEDGERS
4. Decide between local rollback and family retirement
The review traces the auto-apply integration and imported evidence across R7 descendants.
| Gate | Evidence | Local-rule result | Family result | Decision |
|---|---|---|---|---|
| Shared implementation | Auto-apply code used by one branch | Local | Contained | Rollback branch |
| Shared evidence lineage | Quarantined wealth imported by four descendants | Broad | Failed | Escalate family |
| Independent clean descendant | One rule uses separate evidence | Pass | Preservable | Keep frozen pending audit |
| Safe lower authority | Logs only, no recommendation | Available | Available | Permit diagnostic replay |
| Fresh restart feasibility | New family can use independent capital | Yes | Yes | Retire R7; commission R8 |
The clean descendant is preserved for historical comparison but does not inherit operational permission. Any successor must establish its own evidence and cap.
CHAPTER 5 OF 12 · WORK THE LEDGERS
5. Separate cap monitoring from repeated promotion
A capped rule can perform well within its boundary without becoming eligible for promotion. Monitoring asks whether bounded use remains safe; promotion requires a separate prospective claim, fresh evidence and an authorised decision.
Repeated requests to expand authority are not themselves evidence. Record them so organisational pressure does not gradually turn an explicit cap into an informal higher stage.
CHAPTER 6 OF 12 · TRANSFER THE METHOD
6. Retire the family and preserve its topology
Disable operational descendants, integration paths and promotion workflows. Preserve the rule graph, configuration, evidence parentage, cap versions, breaches, rollbacks and retirement decision so later reviewers can reconstruct how authority propagated.
Allow diagnostic replay only under a visibly separate historical mode. Outputs should carry the retired family identifier and must not feed the successor’s live decision path.
CHAPTER 7 OF 12 · TRANSFER THE METHOD
7. Changed-context transfer: change-point routing controller
Transfer the method to a routing controller that uses topological regime labels to suggest network rerouting. It is capped at advisory alerts after earlier false switches.
A deployment script begins applying one alert automatically, while three descendants share a formerly quarantined evidence window. The operator rolls back the script, freezes the family and commissions a new lineage rather than arguing that most alerts were accurate.
CHAPTER 8 OF 12 · TRANSFER THE METHOD
8. Connect re-promotion, stopping rules and retirement
Begin with re-promotion monitoring and permanent authority caps. Use restart-family limits and global evidence budgets when recurrence crosses repaired lineages.
Continue to family-wide stopping rules and claim retirement for the independent audit and retirement architecture.
CHAPTER 9 OF 12 · CHECK LIMITS AND EVIDENCE
9. Limits and common misconceptions
A permanent cap does not guarantee that users will respect it, and technical performance inside the cap does not justify authority beyond it. One local integration error does not require family retirement unless lineage, implementation or governance evidence connects it more broadly.
Retirement is not mathematical proof that every rule in the family is false. It withdraws an operational claim whose evidence boundary is no longer defensible. Historical replay must not be confused with live permission.
CHAPTER 10 OF 12 · CHECK LIMITS AND EVIDENCE
10. Practical evidence and escalation checks
Retain the rule-family graph, cap statement, eligible strata, evidence IDs, wealth or test lineage, monitoring code, event clocks, interfaces, alerts, user actions, deviations, rollback drills and independent review. Link each breach to every affected descendant.
The retirement record should name disabled paths, preserved historical uses, successor independence requirements, notice recipients, unresolved questions and the authority that may approve any future diagnostic access.
CHAPTER 11 OF 12 · ASK AND CONTINUE
11. Frequently asked questions
Can strong monitoring results lift a permanent cap?
No. They support continued bounded use. Higher authority needs a separately defined prospective claim and approval process.
Does every cap breach retire the family?
No. Contain the event and trace implementation, topology and evidence lineage. Retire the family when the credible boundary cannot be restored without a new claim.
May a retired rule be used for research?
Yes, if historical or research mode is clearly separated, lineage is preserved and outputs cannot silently re-enter operational decisions.
CHAPTER 12 OF 12 · ASK AND CONTINUE
12. Sources and next reading
The primary research article Game-Theoretic Statistics and Safe Anytime-Valid Inference develops evidence processes for optional continuation and stopping. The W3C PROV data model provides a standard language for entities, activities and agents in provenance. These sources inform evidence control and lineage; R7, R8 and the routing controller are original teaching examples.
Continue through the Topology root, the Gold Standard of Education and How X Works.
Top · Contents · Previous · How X Works