Operationalization Template for GTCS-Informed Safety Evaluation

This technical specification provides a target-specific measurement architecture for GTCS-informed AI-safety evaluation. Its central methodological boundary is strict: formal target, observation, proxy, estimator, validation result, and protocol decision are different objects. A proxy, learned estimator, threshold crossing, composite score, or classifier output does not become a GTCS, Inter-System Conflict, identity-continuity, WGWP, or AIS02 status merely because it predicts or correlates with that target. Each measurement interface begins from an exact target bookkeeping record identifying the owner, target, version, carrier, prerequisites, readiness conditions, codomain, scope, context, claim ceiling, and provenance. Observation frames, proxy specifications, measurement models, estimators, uncertainty, calibration, thresholds, validation, and missingness are then declared separately. The specification distinguishes four interface modes: exact-owner status measurement, exact-owner scalar/state estimation, target-tethered local diagnostics, and protocol-evidence measurement. Definedness is layered. Owner non-instantiation, owner non-applicability, owner undefinedness, missing observation, model non-applicability, estimator undefinedness, and unresolved validation are not interchangeable and must not be silently serialized as negative results. Thirteen historical test families are reconstructed as target-specific interfaces covering admission and restricted accessibility, representation sensitivity, retained overload and trajectory dependence, structural transformation, exact locking, compensability, burden asymmetry, identity continuity, Inter-System Conflict owner surfaces, transformation occurrence, independent-review evidence, protected-protocol-constraint evidence, and technical-continuity substitution / exact capture. Numerical thresholds, composite indices, and learned estimators are permitted only as local, versioned, calibrated, and validated operational tools. They are not theory constants and do not become universal owner variables. The specification also defines provenance-bearing evidence packets for AIS02. These packets may support applicability, review, wider-continuity, trigger, escalation, independence, or compliance assessment, but they do not themselves issue protocol decisions. The document therefore operationalizes measurement without collapsing theory into instrumentation and supports quantitative testing while preserving owner boundaries, uncertainty, validation scope, and evidence provenance.