Registered Strategy A on the T-S01 profile

This is one exploratory measurement of the registered public StrategyPort path through Strategy A, its reachability, terminal minimization, recovery, geometry/conversion providers, and HiGHS LP/convex providers. It is not a Strategy A versus Strategy B comparison, speedup, application-scale result, or scalability claim.

Algorithm source commit: 451d0f7553cd0ab606c4ed07ae142310cb897eb4; harness: 4a3556ba65a75716c00a9ac24f01e04648be5ea5. Profile: ts01_exact_integrator. Assumptions:

Analytic T-S01 relation

For x₀=0, xₜ₊₁=xₜ+uₜ, u₀,u₁∈[0,1] and J(x₂)=(x₂−1)², the complete relation is (x₀,x₁,x₂,u₀,u₁)=(0,s,1,s,1−s), 0≤s≤1. Each timed run required a registry-verified complete-family result and checked the literal canonical H-representation and exact membership/nonmembership points.

Completeness is limited to this exact admitted T-S01 profile under its declared Assurance::numerical evidence path. Each output names the registry-accepted compiled verifier csl.verifier.ts01-analytic@1; no generic strategy coverage or validated-arithmetic assurance is implied.

Each trial constructs the fixed canonical representative (0, 0.25, 1, 0.25, 0.75), checks that it belongs to that trial's registry-accepted relation, then independently checks the original equations x₀=0, x₁=x₀+u₀, x₂=x₁+u₁, control bounds, and J(x₂)=(x₂−1)²=0. This representative is a residual probe, not an optimizer-returned witness and not evidence used to infer completeness. Maximum residuals are 0–0 under absolute and relative tolerances 1e−8; the independent checker ID and coordinates are in every raw event.

Observed timings

Fresh problem construction and resolution, registered Strategy A provider selection, StrategyRegistry preparation, exclusive public StrategyPort workspace creation and run through forward reachability, terminal minimization, recovery and registered HiGHS LP/convex execution, compiled T-S01 verifier acceptance, independent original-trajectory residual checking, and exact canonical H-relation membership/nonmembership validation. Excludes process startup, JSON serialization, build, file persistence, and rendering.

One excluded warmup; seven measured runs. Median 4904700 ns; range 4425000–5543600 ns (width 1118600 ns). Failures: 0.

measured repetition
Raw observations are available in the linked JSONL and CSV files.
RepetitionElapsed (ns)Representative objectiveMax residualResult dispositionValidation
1554360000complete_optimal_familypassed
2497770000complete_optimal_familypassed
3493450000complete_optimal_familypassed
4490470000complete_optimal_familypassed
5452660000complete_optimal_familypassed
6442500000complete_optimal_familypassed
7451260000complete_optimal_familypassed

Performance conclusion: inconclusive. A separate CPU profile was attempted with Windows Performance Recorder, but its system-performance policy setup failed (0xc5585011). Process CPU-time and memory counters are retained, but no trustworthy sampled call-stack/source hot spot was available to identify a limiter.

Evidence limits

Environment and reproduction evidence

Machine, operating system, compiler, Release configuration, dependency pins, provider identity, system load observations, profiling attempt and all unavailable phase counters are retained in the machine-readable sidecars.

Typed report · Raw timing events · Timing CSV · Measurement and host evidence · Build provenance · Scenario · Separate profile attempt

No Strategy A versus Strategy B comparison or performance ranking is made. This result is partial SYN-03 evidence and does not close issue #66.

Publication syn03-strategy-a-ts01-77f669553a7c803b4f061401d5c1f7ffb22ef7f973368cd1b7c3494686fa8e2a; source report syn03-strategy-a-ts01-20261014-451d0f75. Versioned envelope · Publication manifest