Nuclear & Waste Systems

SECTION 01

Domain overview and system boundary

The system boundary must follow a hazardous inventory across its lifecycle rather than stop at the installation fence. Production, use, storage, transport, disposal and institutional oversight create linked obligations. A waste-management case should specify the material category, authorized pathway, responsible organizations and time horizon at an appropriate public level. Storage provides managed retention; it is not equivalent to final disposal. Distinguishing these functions prevents a temporary administrative milestone from being described as resolution of the underlying long-term responsibility. [NUC01] [NUC20]

This domain examines civilian nuclear installations, radioactive-source stewardship, radioactive-waste management, decommissioning and long-term environmental responsibilities. Its central problem is the mismatch between the duration of hazardous inventories and the shorter lives of equipment, organizations and political commitments. Assessment must connect physical containment and monitoring with licensing, records, competent institutions, accessible resources and public accountability. A learning case may concern a waste-management pathway, an external-hazard governance review or continuity of institutional control over disused sources. [NUC01] [NUC04]

Safety is not established by a single low estimated frequency. Deterministic analysis, defense in depth, probabilistic assessment, operating experience and independent regulatory review answer complementary questions. An apparently redundant arrangement can remain vulnerable when multiple barriers share the same hazard, maintenance process or supporting infrastructure. The educational focus is on identifying those dependencies and testing the evidence behind a safety claim, without supplying facility-specific operating procedures, material-handling instructions or security-sensitive configurations. [NUC07] [NUC13]

Waste and accident recovery require distinctions between stopping deterioration, restoring a service, remediating contamination and returning a site to an authorized end state. Some changes cannot be reversed within an institutional planning horizon. P, ΔV, σ and Lr must therefore be tied to clearly stated physical and governance observables. A synthetic score does not replace a licensed safety assessment or create authority to modify an installation. Long-term stewardship remains an intergenerational institutional commitment whose credibility depends on traceable evidence and independently reviewed responsibilities. [NUC03] [NUC06]

A domain label is not yet a case boundary. Separate the condition of a resource or asset from the function delivered to users. A nominally available installation may fail to deliver usable service, and a system-wide average can conceal localized loss. Preserve the original physical or institutional unit alongside any normalized representation. The boundary should make it possible to ask what enters, what changes, what leaves and who experiences the consequences.

Section readings [NUC01; NUC20]

SECTION 02

Historical development and changing conditions

Historical development has repeatedly changed the understanding of nuclear and radiological risk. Accident investigations have expanded attention from individual components to organizational conditions, common causes and lifecycle responsibilities. Waste-management history also shows how interim arrangements can persist while institutions and assumptions change. A case timeline should record changes in the assessment basis, oversight and planned end state. Do not treat successive technical proposals as evidence that a disposition pathway is already available. Compare the commitment made at each stage with the independently documented capability existing at that time. [NUC04]

A historical baseline must be examined for changes in exposure, technology, operating practice and observation. Compare episodes using their mechanisms and evidence, rather than treating all events with a similar label as exchangeable observations. A reconstruction should show what was known at each time; later explanations should not be presented as information available to the original decision maker. Recovery and long-term change may require a separate timeline from the initiating incident.

Section readings [NUC04]

SECTION 03

Actors, institutions and decision responsibilities

The institutional map should distinguish the licensee, independent regulator, technical support organizations, waste-management bodies, emergency authorities and affected communities. Responsibilities can change during decommissioning or transfer of custody, making handoffs analytically important. Record who retains records, accepts a waste consignment, verifies a milestone and authorizes a change in status. International standards provide reference requirements but are implemented through jurisdiction-specific arrangements. A Fellowship exercise can scrutinize this allocation of responsibility; it cannot confer a licence or substitute its own score for a competent authority's determination. [NUC13]

Map actors by the function they perform and the responsibility they actually hold in the case. The same organization may observe a condition, supply a service and participate in a decision; those roles should remain distinguishable. Examine information access, resources, expertise, affected users and accountability together. A list of institution names is not an operating governance arrangement. Record the evidence for each responsibility and the process for resolving a disagreement or correcting a record.

Section readings [NUC13; C07]

SECTION 04

Primary systemic risks

Primary risks should be expressed as losses of defined protective or stewardship functions. External flooding, aging or records loss are meaningful only when connected to a pathway of impairment. Keep the initiating hazard distinct from barrier condition, exposure and consequence. A public educational inventory can identify these relationships without revealing sensitive configurations. For each risk, state the relevant time horizon and evidence needed to judge the claim. A barrier described as present must also have a documented basis for the conditions under which its function is being credited. [NUC13]

The inventory is a structured set of research hypotheses. It separates a threatening condition from the mechanism of loss and from its consequences. The proposed TFP association indicates which question to investigate; it is not evidence that a particular indicator predicts the event. Risk importance depends on the defined function, exposure, duration and usable alternatives. Do not infer frequency, severity or priority from the position of a row in the table.

Section readings [NUC13]

SECTION 05

Amplification mechanisms and secondary risks

Amplification occurs when defenses share dependencies or when organizational arrangements allow deterioration to accumulate. Nominal redundancy does not establish independence if units rely on the same external services, contractors or assumptions. A corrective-action system can also amplify risk when closure records document paperwork rather than effective change. Fellows should trace one concern from detection through evaluation, authorization, completion and verification. This reveals where responsibility or information is lost and permits a systems explanation without assuming that every accident can be represented as a simple chain of component failures. [NUC07]

An amplifier changes the consequences of an initiating condition without necessarily causing the initiating event. Useful counterfactuals hold the threat constant and vary concentration, maintenance, access, information or response capacity. Document the mechanism and the observation that would distinguish it from an alternative explanation. Several amplifiers may share the same upstream cause; counting each one as independent evidence exaggerates confidence.

Section readings [NUC07]

SECTION 06

Emerging risks and research horizons

Emerging technologies alter the configuration of uncertainty rather than abolish it. A new reactor concept may produce different waste properties and supporting-service requirements from established designs. Claims about an entire technology class should therefore be tested against specific designs, operating assumptions and management pathways. The relevant educational question is which evidence must exist before a favorable comparison is credible. Separate prospective engineering claims from demonstrated operation, and avoid extrapolating findings for a selected design to all future systems. Waste obligations belong in the comparison from the beginning. [NUC05]

A research horizon is tied to the time needed to investigate, prepare or change a system. It is not a date at which an emerging threat is predicted to occur. Record the reason for concern, the strength of evidence, the exposed function and the observation that would change the priority. Distinguish a newly observed mechanism from a known mechanism whose exposure, scale or institutional context is changing.

Section readings [NUC05]

SECTION 07

Cascades and cross-domain dependencies

Cascades in this domain include common-cause impairment of multiple units, interruption of external support and accumulation of waste when a downstream route becomes unavailable. Represent these as different edge types in a dependency graph. Shared geography can correlate external hazards, while institutional interfaces can correlate information failures. The graph should identify whether evidence supports independence or merely assumes it. A useful scenario asks which resources would be demanded simultaneously and whether their availability remains credible during the regional event. Counting reserve assets without this context can overstate recoverability. [NUC14]

For each directed dependency, specify the function supplied, the destination, the propagation time and the substitute. Shared-cause failure, interacting threats and cascading propagation are different structures. A directed arrow becomes an explanatory claim only when the timing and mechanism are supported. Test apparent redundancy by removing the common access route, platform, energy supply or specialist on which both alternatives depend.

Section readings [NUC14; C01; C02]

SECTION 08

Readiness and response protocols

A governance escalation protocol should define how a verified concern reaches the authorized organization, how acknowledgment is recorded and who decides whether further assessment is required. Public educational materials should focus on these responsibilities rather than facility-specific emergency operating instructions. Distinguish precautionary review from a regulatory declaration and retain the evidence available at the decision time. The protocol should remain usable when ordinary communications are degraded. Its performance can be evaluated through an exercise that tests timely notification, role clarity and reconciliation of conflicting reports without asserting operational authority. [NUC21]

Preparedness connects a signal to a responsible actor, an available measure and a condition of completion. This learning architecture does not grant emergency command or operational authority to the c-ECO Institute or a course participant. A useful protocol distinguishes checking the signal, protecting exposed functions and verifying recovery. A paper plan contributes to usable capacity only when its relevant assumptions have been tested.

Section readings [NUC21]

SECTION 09

Scientific review and decision records

Independent review must examine both the calculation and the basis for crediting functions, resources and assumptions. Reviewers should ask whether the assessment boundary excludes a shared external dependency or a long-term obligation. Conflicts of interest, access to evidence and the handling of unresolved objections belong in the review record. A technically sophisticated model can still be inappropriate for a changed configuration. The learning deliverable should preserve the challenge, response and residual uncertainty, allowing later reviewers to understand why a conclusion was accepted and what new evidence would require reconsideration. [NUC08]

A review record separates observation, inference and decision. Record the data version, methods, alternative explanations, relevant expertise, conflicts of interest and unresolved disagreement. Review should be matched to the question and its consequences. Scientific analysis can inform a competent actor without replacing that actor’s mandate. No membership size, quorum or institutional power is established by this teaching library.

Section readings [NUC08; C05; C07]

SECTION 10

Communication and observation continuity

Communication after a radiological event must connect verified observations, authorized interpretation and the public's practical information needs. Measurement values without units, location, time or uncertainty can mislead; unexplained changes in reporting can undermine trust. Separate confirmed findings, estimates and unresolved questions. Accessible communication also requires routes for affected groups to ask questions and receive documented responses. The Goiânia case illustrates how an issue originating in disused equipment can spread into ordinary community settings. The governance lesson concerns continuity of custody, recognition and communication throughout the lifecycle. [NUC18]

Continuity of observation should be tested alongside continuity of the function itself. Losing data may increase uncertainty before the physical process visibly changes. Redundancy must be demonstrated against common causes, including power, location, communications, credentials and specialist availability. During disconnected operation, preserve the last reliable observation, record the uncertainty that follows and reconcile timestamps and authorship when information paths return.

Section readings [NUC18; C01]

SECTION 11

International instruments and technical references

International nuclear and radiation instruments differ in scope, participation and domestic effect. Safety standards, conventions, technical guides and recommendations should not be presented as interchangeable legal rules. For a case, use the relevant official text and record whether the country is a party, what domestic instrument applies and which authority interprets it. Long-term waste commitments may also involve environmental, land-use and public-participation obligations. The purpose of the legal map is to identify accountable interfaces and review needs, not to provide an unsupported global compliance determination. [NUC20]

Classify each instrument before using it. A scholarly article supports an inference, a technical guide describes a method, a standard has a defined scope, and a legal instrument may create obligations only where applicable. The case record should identify the specific provision or method, its version and the activity to which it relates. A source’s institutional reputation cannot by itself establish applicability or demonstrate compliance.

Section readings [NUC20]

SECTION 12

Jurisdiction-specific responsibilities and requirements

National implementation determines licensing stages, inspection responsibilities, source registration and authorized waste pathways. A change from operation to decommissioning does not by itself extinguish obligations. Map the evidence required for each lifecycle transition, the organization producing it and the authority accepting it. Jurisdictions may use different waste classifications or acceptance criteria, so category labels should not be transferred without checking definitions. Public training can describe the structure of this process while leaving site-specific decisions to qualified and authorized institutions. The record should distinguish planned permissions from permissions actually granted. [NUC13]

The register should cover the actual activity and location, including interfaces between organizations and jurisdictions. Separate responsibility for observing, supervising, deciding and executing. Retain the official source, version consulted and evidence needed to assess a condition. Conflicting definitions and overlapping mandates are analytical findings to investigate. A general library cannot create a universal legal threshold for all settings.

Section readings [NUC13]

SECTION 13

Causation, accountability and cascading consequences

Accountability analysis should reconstruct responsibilities and knowledge at the time of a decision. A later-discovered defect does not establish which actor had which information earlier. The Davis-Besse record is useful for examining inspection, oversight and response to emerging concerns without reducing a complex institutional failure to a single headline. Identify the documented concern, relevant obligation, assessment, decision and corrective action. A learning review can compare these sequences and test governance improvements; legal liability requires a separate jurisdiction-specific process and appropriate standards of proof. [NUC19]

A technical chain of consequences is not automatically a legal allocation of liability. Separate evidence of causation from the duties, control and decisions relevant to each actor. A case may contain direct damage, dependent service interruption and persistent environmental or social consequences on different timescales. The analysis should show which links are documented and which need further investigation, without presuming an institutional restoration fund, mandatory levy or insurance mechanism.

Section readings [NUC19]

SECTION 14

Cross-boundary coordination

Cross-border consequences and cooperation introduce differences in measurement, interpretation and responsibility. Neighboring jurisdictions may use different monitoring networks, reporting schedules and legal thresholds. A shared dashboard should preserve these distinctions rather than merge incompatible categories into a common color. Record the official source, date, medium, unit and uncertainty for each observation. Cooperation arrangements also need authorized notification and a process for resolving inconsistent reports. The analytical objective is a traceable account of the information and obligations connecting jurisdictions, not an implied transfer of regulatory authority to the platform. [NUC21]

Processes and dependencies often cross administrative, organizational or national boundaries. Coordination requires compatible definitions, useful timing, authorized exchange and an identifiable decision interface. Sharing data does not by itself resolve disagreements over objectives, risk allocation or resources. An exercise should expose which decision can be coordinated under existing arrangements and which would require an additional agreement or competent determination.

Section readings [NUC21; C07]

SECTION 15

Position (P): candidate observations

P must identify the object being measured: an environmental margin, verified function availability or a modeled event probability. These quantities are not interchangeable. A probabilistic safety assessment addresses defined scenarios under stated assumptions; it does not summarize every institutional or intergenerational concern. Preserve the event definition, exposure period and model scope beside the estimate. For educational comparison, use transparent observables and test whether an apparently favorable value depends on excluding a shared hazard, assuming perfect detection or crediting a resource whose availability has not been demonstrated. [NUC08]

P represents position relative to a specified loss of function. The raw observation, reference condition, direction of deterioration and boundary of failure must remain explicit. A candidate monotone transformation can help compare states within a defined case, but it does not establish the threshold or validate an aggregate index. Capacity, delivered performance and exposure may require different indicators even when they concern the same installation.

A didactic monotone transformation for an indicator that worsens as it rises is p = clip[(x − x_ref)/(x_failure − x_ref), 0, 1]. Reverse the direction for a reserve that deteriorates as it falls. The expression makes the reference points visible; it does not choose those points, prove comparability or establish an operational aggregate. Retain x in its original unit and justify the function separately for each case.

Section readings [NUC08]

SECTION 16

Velocity (ΔV): rates and trajectory

ΔV links the rate of deterioration or obligation growth to the time available for assessment and response. Relevant rates include condition trends, accumulation of significant findings, storage headroom consumption and disposition schedule slippage. They have different units and cannot be directly combined. A slowly changing inventory can still create urgency if the authorized management route takes years to establish. State the observation interval, measurement reliability and review horizon. Trend extrapolation should be tested against changes in environment, inspection methods and institutional plans rather than assumed to remain stable indefinitely. [NUC01]

ΔV describes direction and rate of change over a declared interval. Two systems at the same apparent position may have different reaction times because their trajectories differ. Compare rates using consistent units, observation windows and reference systems. Check seasonality, missing periods, reporting changes and process acceleration before extrapolating. A time-to-boundary calculation is conditional on its trajectory assumption; it is not a general forecast.

Section readings [NUC01]

SECTION 17

Uncertainty (σ): evidence and model limits

Uncertainty should distinguish random variability, limited knowledge, model structure and institutional contingency. Rare-event data cannot reliably resolve all tail probabilities, and incident databases are shaped by scope and reporting practices. More decimal places do not remove these limitations. Compare alternative plausible models and retain the strength of the supporting knowledge beside any probability estimate. For long-term waste questions, geological and material evolution introduce uncertainties different from near-term operational statistics. A useful register states which uncertainty affects the decision, how it is represented and which observation or review can reduce it. [NUC09] [NUC10]

Uncertainty should be recorded by object and source. Measurement uncertainty, sampling limitations, parameter uncertainty, model structure, future scenarios and institutional ambiguity cannot be replaced by one unsupported percentage. More simulation samples can reduce numerical sampling error without resolving a missing mechanism. Identify which uncertainty changes the decision and which further observation, comparison or test could reduce it.

Section readings [NUC09; NUC10; C06]

SECTION 18

Reversibility liquidity (Lr): usable recovery resources

Lr should describe what can be restored, by whom, within which horizon and under which constraints. Stabilization, remediation and an authorized final end state are distinct objectives. A long-lived inventory may remain after a damaged service is restored, so operational recovery cannot be treated as full reversal of consequences. Record the qualified teams, access routes, monitoring capability, waste pathways and durable institutional resources needed at each stage. Evidence of nominal capacity is insufficient when regional disruption or competing demands could make that capacity unavailable at the necessary time. [NUC14]

Lr examines resources that can preserve, contain or recover the defined function within the relevant time. A resource listed in an inventory is different from a resource that is accessible, compatible, staffed and mobilizable. Record capacity, useful arrival time, duration, dependencies and evidence of testing. Avoid averaging away an essential bottleneck. Recovery of a service does not necessarily restore ecological condition, accumulated losses or public trust.

Section readings [NUC14]

SECTION 19

Stress scenarios and comparative strategies

Scenario design should include common-cause external events, delayed deterioration discovery and interruption of a downstream waste pathway. Each scenario needs an explicit boundary, baseline and time horizon. A physically minor disruption can have long governance consequences if records or custody are lost. Compare scenarios using the same acceptance criteria and identify which assumptions drive the result. Educational analysis should remain at the level of institutional preparedness, environmental interfaces and service continuity. It should not reproduce facility-specific operational sequences or imply that a generic model validates an installation's safety. [NUC07]

A stress scenario states the initiating condition, prior state, time sequence, exposed function, shared dependencies and feasible responses. Its purpose is to reveal when a strategy loses usefulness and why. Compare alternatives across several conditions, including absent substitutes and simultaneous demand. Scenarios should lead to observations, tests and resource questions; assigning a precise event probability requires a separate justified model and evidence.

Section readings [NUC07]

SECTION 20

Reproducible simulation and sensitivity analysis

Simulation can help explore dependence and uncertainty, but it cannot manufacture evidence for poorly specified inputs. Correlated external hazards and shared resources should not be sampled independently without justification. Separate parameter uncertainty from alternative conceptual models and compare simple benchmark cases before adding complexity. Tail estimates are particularly sensitive to the assumed distribution and event inventory. Report the target quantity, sample design, convergence evidence and sensitivity rather than a single probability. Where empirical validation is unavailable, describe the output as a conditional model result and state the limits on its intended use. [NUC08]

Simulation is an explicit transformation of assumptions. Input distributions, dependencies, parameter estimation, output definition and testing must be documented. Numerical convergence does not establish model validity. Examine sensitivity to the function used, the weights selected, dependence assumptions and conditions outside the fitting data. The reproducible laboratory below is a synthetic exercise, separated from SPS and from any claim about real-event frequency.

The factor loadings define association on the latent scale. Correlations after the nonlinear transform should be estimated from the simulated samples. Q is a teaching index and is not SPS. Its exceedance fraction concerns the generated sample under these assumptions; it is not the probability of a real event or a forecast over a stated number of years. A temporal forecast would require a separately specified process and observation model.

from random import Random
from math import log, exp, sqrt
from statistics import mean
rng = Random(2503335601)
m = [.72, .62, .40, .38]
s = [.40, .45, .30, .40]
a = [.65, .55, .35, -.45]
q = []
for _ in range(10000):
    g = rng.gauss(0, 1)
    x = []
    for mj, sj, aj in zip(m, s, a):
        z = aj*g + sqrt(1-aj*aj)*rng.gauss(0, 1)
        x.append(1/(1+exp(-(log(mj/(1-mj))+sj*z))))
    p, v, u, lr = x
    q.append(.35*p+.25*v+.15*u+.25*(1-lr))
q.sort()
print(mean(q), q[499], (q[4999]+q[5000])/2, q[9499])
print(sum(x >= .70 for x in q)/len(q))

Sensitivity exercise: remove the common factor, vary one dispersion, change the weight of recovery resources, and compare the ranking of the selected strategies. Then state which domain observations would be needed to replace each illustrative assumption. Use a suitable estimator when inputs are dependent; the common-factor experiment is a dependence check, not a claim that a particular Sobol estimator applies unchanged.

Section readings [NUC08; C03; C06]

SECTION 21

Restoration and performance verification

Recovery modeling must represent the management burden created by remediation itself. Contaminated material, disrupted records and constrained access can generate new dependencies and extend stewardship obligations. A sequence that restores one facility function may increase demands on waste-management capacity elsewhere. Compare milestones for stabilization, environmental characterization, authorized waste management and long-term monitoring. Each milestone needs acceptance evidence and a responsible organization. The model should also preserve uncertainty about the endpoint rather than assuming that spending a fixed amount or completing a calendar period establishes restoration. [NUC03] [NUC06]

Restoration follows prerequisites and verification conditions rather than a universal fixed clock. Tasks may proceed in parallel only where they do not compete for the same people, access, equipment or information. Protect essential functions while the critical path is addressed. Define what is measured before returning service, who can make that determination and which effects require continued observation after a technical restart.

Section readings [NUC03; NUC06]

SECTION 22

Recovery provider capability

Provider qualification depends on task-specific competence, authorization, independence where required and demonstrated availability. A commercial contract alone does not establish that qualified personnel and equipment will be accessible during a common regional event. Check scope, acceptance criteria, evidence custody and handover responsibilities. Independent reviewers need access to the information necessary to challenge the work. Public materials can state these qualification principles without exposing sensitive inventories or configurations. The educational assessment should evaluate the evidence supporting a provider's claimed capability rather than infer competence from institutional reputation. [NUC13]

Capability assessment must be specific to the task, place and stress conditions. A training certificate cannot demonstrate that a team can mobilize and deliver the required function. Inspect competence, safety, compatibility, relevant experience and actual availability. Define the verification method and limits of recognition. This teaching library does not establish a c-ECO provider certification scheme or substitute for professional or regulatory requirements.

Section readings [NUC13]

SECTION 23

Recovery sequencing and time constraints

A restoration sequence should preserve the distinction between immediate stabilization, verified characterization, management of resulting materials and an authorized end state. The order depends on the case and cannot be supplied as a universal operational recipe. For learning, map the dependencies and acceptance decisions between stages. Identify which milestones can be independently verified and which remain conditional on future evidence. The Fukushima assessment shows why post-accident recovery must be treated as a long-term programme with technical and institutional components rather than a single reopening date or completion percentage. [NUC14]

A recovery time objective is a decision criterion to test against real capacity. Distinguish mobilization, work, verification and decision time, and identify dependencies between tasks. Shared resources can prevent apparently parallel activities from proceeding together. Repeating the sequence with unavailable access, a specialist or a verification service reveals where a target relies on an untested assumption.

Section readings [NUC14]

SECTION 24

Equipment, inputs and replenishment

A waste inventory must carry meaningful classification, characterization, location, condition, acceptance and custody information at an authorized level of detail. Volume alone cannot represent hazard or management difficulty. Different material properties and pathways create different resource and institutional requirements. Reconciliation should test whether records correspond to the actual accepted inventory and whether exceptions are resolved. For public learning materials, use aggregated or synthetic records where necessary to protect sensitive information. The analytical objective is to evaluate traceability and completeness without disclosing operationally sensitive details. [NUC02] [NUC20]

Inventory analysis connects each item to a protected function. Use condition, compatibility, accessibility and consumption under stress rather than a nominal stock count alone. Replenishment time must include procurement, transport, installation and verification where relevant. A substitute that depends on the same supplier or platform may disappear in the same event. Keep the last inspection date and the evidence supporting usable availability.

Section readings [NUC02; NUC20]

SECTION 25

Mutual aid and cooperation arrangements

Mutual support arrangements should account for concurrent demand across a region or multi-unit site. The same qualified team, monitoring capability or access route cannot be credited as independently available to several simultaneous incidents without an allocation basis. Record the authorized request process, mobilization assumptions, competing commitments and verification method. Exercise evidence can expose communication and handoff delays that a signed agreement conceals. Recovery credibility therefore depends on demonstrated coordination under the scenario being studied, with a clear distinction between a proposed arrangement and an active, tested capability. [NUC21]

Cooperation contributes to recovery when its scope, activation, resources and practical availability are demonstrated. Record who requests support, who authorizes it, the useful arrival time, responsibility for the work and conditions of return. Consider simultaneous demand across participants. A reference to an organization or network in the literature does not imply that c-ECO or a case partner has joined it or secured a deployment commitment.

Section readings [NUC21]

SECTION 26

Source classification and evidence quality

Source categories should distinguish regulatory determinations, operator records, research models, environmental measurements and community observations. Each has a different evidentiary role. An official publication may establish a requirement without measuring local conditions; a research paper may explore a mechanism without validating a particular site. Record version, purpose, scope, method and limitations for each source. Avoid a single prestige-based hierarchy that treats all products from one institution as equally applicable. Evidence classification should help reviewers understand what supports a claim and what remains an inference requiring additional validation. [NUC08]

Source classes organize origin and function; they do not form an automatic hierarchy of evidential strength. An official statistic, an operational record and a causal study answer different questions. Classify the product, not only the organization. Detect shared data origins so that a dashboard, article and secondary report based on one observation are not counted as three independent confirmations.

Section readings [NUC08; C04; C05]

SECTION 27

Institutional, regulatory and technical sources

Intergovernmental and regulatory documents provide the principal public framework for safety requirements, accident assessments and lifecycle responsibilities. Their authority depends on the instrument and jurisdiction, while their empirical scope depends on the assessment performed. The IAEA safety-assessment standard supports questions about graded assessment and defense in depth; an accident investigation supports claims about the investigated event. Keep those uses separate. Preserve document editions and identify superseded versions so a historical case is interpreted under its original context while a current governance proposal uses the applicable present reference. [NUC13] [NUC16]

Institutional sources should be selected by product, method and scale. Record whether the source defines a requirement, observes a condition, reports an investigation or synthesizes a literature. A current portal may contain several editions and methods; cite the actual version used. Public access does not establish accuracy for a different question, and a restricted source can still be used only under its authorized conditions.

Section readings [NUC13; NUC16]

SECTION 28

Operational observations and monitoring products

Operational sources include inspection findings, maintenance records, accepted inventory documentation and environmental monitoring results. These records require context: detection limits, inspection coverage, changes in procedure and unresolved exceptions can affect interpretation. A quiet incident log may reflect low reporting rather than absence of concerns. Compare records through authorized independent review and preserve revision history. Public reporting should communicate the mechanism and evidence quality without exposing sensitive technical configurations. A provider's declaration that work is complete should be linked to the acceptance criterion and verification that support that statement. [NUC19]

Operational observations should show what the system delivered, not merely that an asset was declared available. Inspect the acquisition process, sensor or reporting changes, gaps, coverage and quality controls. Compare records with independent observations where feasible. Aggregated performance, a status dashboard and user experience can diverge because they concern different units, locations, periods or definitions of availability.

Section readings [NUC19]

SECTION 29

Academic research and independent evidence

Academic literature helps explain material persistence, institutional duration and limits of statistical inference. Its findings still require careful transfer to the case. A selected reactor comparison does not establish the performance of every proposed design; a general geological argument does not validate a particular location. Community perspectives contribute evidence about access, trust and the legitimacy of long-term commitments. Treat disagreement as an analytical object rather than evidence to be removed. The review should identify where disagreement concerns facts, model assumptions, distribution of burdens or the decision process itself. [NUC04] [NUC05]

Read the research design before transferring a conclusion. Identify the question, unit of analysis, method, comparison, result, limitations and conditions that matter for the case. Foundational concepts, empirical studies, critical replications and technical syntheses serve different functions. A literature-supported mechanism may justify a hypothesis without validating a local threshold, forecasting performance or a complete TFP application.

Section readings [NUC04; NUC05]

SECTION 30

Source–variable correspondence

A source-to-variable map must identify the transformation from a record to the construct being assessed. An inspection count measures activity, while coverage and defect-detection capability determine what can be inferred about condition. A financial provision measures a documented resource, while the obligation model determines whether it is adequate. Preserve units, definitions, time support and missingness for each step. If several indicators depend on the same inspection record, they are not independent corroboration. This mapping exposes where a numerical summary depends more on an institutional assumption than on an observation. [NUC01]

The source–variable matrix exposes the path from an observation to an analytical representation. Preserve the raw unit, time, location, method, transformation and uncertainty. Multiple derived variables may share one observation and therefore share its limitations. Record the code or reproducible procedure, authorized access and version. A score should remain inspectable through its originating evidence rather than replacing that evidence.

Section readings [NUC01; C04; C05]

SECTION 31

Source–risk correspondence

A source-to-risk map should connect each mechanism with an observation capable of detecting it. Material-condition trends address different risks from custody reconciliation or corrective-action records. For each risk, identify a leading observation, a consequence measure and a verification route where feasible. State the limits: an environmental sample may characterize a medium at a location but cannot by itself establish the cause of a change. The map should also show risks for which evidence is absent or inaccessible, ensuring that the dashboard does not silently convert non-observation into reassurance. [NUC18]

A source–risk matrix should cover the threat, the observed state, the mechanism and the consequences separately. Evidence that an event occurred does not alone show why a function failed or who was affected. Use a chronology and alternative explanations to test the chain. A citation becomes useful when the specific part of the claim it supports and its limits are visible.

Section readings [NUC18]

SECTION 32

Monitoring gaps and research priorities

Monitoring gaps can concern physical coverage, institutional continuity, missing history or an unresolved conceptual model. Prioritize them by their effect on a decision rather than the ease of collecting another data stream. Long-lived obligations make records preservation and interpretability particularly important: a technically intact archive may become unusable if definitions, custody and formats are lost. Test retrieval and interpretation as part of the evidence system. Record who is responsible for closing each gap, how the evidence will be reviewed and which conclusion remains provisional until that work is complete. [NUC06]

Prioritize a gap by its consequence for the decision. The next observation may be a targeted measurement, an independent comparison, a capability test or a correction of incompatible definitions. More data of the same kind may not resolve structural uncertainty. Specify the question, required observation, responsible custodian, time of collection and condition under which the gap is considered sufficiently addressed.

Section readings [NUC06; C03]

SECTION 33

Dependency matrix and propagation tests

The cross-domain matrix should capture direction and mechanism rather than generic connectedness. Water temperature affects cooling-related constraints; energy supports monitoring; transport affects access; finance and governance sustain long-term custody. Dependencies may change over the lifecycle, so a graph appropriate to operation may be inappropriate to decommissioning or disposal. Mark observed, inferred and hypothetical links and retain the associated timescale. Climate-related assessment is especially sensitive to changing environmental baselines and compound hazards. Use the matrix to identify review priorities, not to imply a calibrated systemic probability from arbitrary edge weights. [NUC11] [NUC12]

A dependency matrix should be directional and time-specific. Record the supplying function, receiving function, mechanism, useful delay, substitute and evidence. Test the destination when the origin becomes unavailable for different periods. Then remove a common prerequisite of the substitute. The resulting structure describes the case; it does not establish all connections in a global architecture or validate an edge weight.

For each relationship, add the measured delay, duration of tolerable interruption, substitute and observation supporting the directed edge. Repeat the test for short, intermediate and extended unavailability. A generic list of linked sectors is not an estimated network, and no edge weight is validated by inclusion in this table.

Section readings [NUC11; NUC12; C01; C02]

SECTION 34

Documented cases, near misses and recovery

Historical cases illustrate distinct mechanisms and should not be collapsed into an unqualified accident count. Three Mile Island concerns interacting equipment and information; Chernobyl requires attention to updated design and organizational analysis; Fukushima emphasizes shared external hazards; WIPP highlights waste-management interfaces; Goiânia highlights custody after use; Davis-Besse highlights degradation and oversight. Compare what each investigation actually establishes and what remains contested or outside scope. Avoid unsupported consequence figures and hindsight simplifications. A common comparison matrix should record evidence provenance, responsibility and the change made after the event. [NUC15] [NUC16] [NUC17]

Historical analysis distinguishes observed loss, protective response, near miss and recovery. Several records can concern one event without becoming independent events. Preserve what the source actually investigated and avoid adding unsupported casualty, cost or restoration-time estimates. Compare cases by mechanism and evidence quality; the fact that one response was associated with an outcome does not alone establish a general causal effect.

Section readings [NUC15; NUC16; NUC17]

SECTION 35

Integrated review, transfer and learning portfolio

Cross-domain synthesis should connect environmental change, infrastructure reliability and institutional durability to a defined stewardship decision. A water-stress paper may support the plausibility of changing environmental constraints without estimating the risk of a specific installation. A finance model may reveal resource sensitivity without establishing regulatory adequacy. The final learning product should state these inferential boundaries and identify the qualified review needed for implementation. Its contribution is a transparent account of dependencies, uncertainty and recoverability across time, preserving the distinction between a scientific argument and an authorized safety determination. [NUC11] [NUC12]

The integrated portfolio should allow a reviewer to move from the question to observations, transformations, mechanism tests, scenarios and proposed monitoring. Make the strongest competing explanation and the most consequential unresolved gap visible. Transfer requires checking mechanisms, exposure and recovery resources in the new setting. Formation, optional credentialing, submission permission and licensing remain distinct processes; no case or data contribution enters the SIL without an associated fellow and applicable review.

Section readings [NUC11; NUC12; C04; C05]