B08 displayed-data exact reference

Descriptive single-checker Python measurements. This is the printed rounded linear model, not the historical MATLAB run, nonlinear plant or a complete optimal-control family. No comparator, speedup or source-mapped limiter was measured; performance interpretation is inconclusive.

Source commit 78212b21d42ec3f136f0e1c72b2b0861d306792c; harness commit 5748952af0ce9fca7aee625e7c62f20cff1d713f; report b08-exact-b0d0e85d4d338f56.

Exact worst-case squared norm: 112730080707/25000000, or about 67.1506011014 as a norm. Three plans tie exactly under printed rational inputs. The article reports 67.12 separately.

7 measured fresh child processes and one excluded warmup. parent perf_counter_ns immediately before child process spawn through child exit and captured stdout/stderr return; includes CPython startup, 625x256 exact rational enumeration, literal checks and record comparison; excludes parent validation, CSV/JSON persistence, HTML rendering and ZIP creation. Interpreter startup and output capture are included, so these are process-level times.

Fresh-process latency, nanoseconds
MedianMinimumMaximumSuccessful trials
1651407800162676180016833024007
Fresh-process durations for all B08 attempts One excluded warmup and seven measured checker runs. Horizontal position is duration in seconds; the dotted line marks the measured median. Exact nanoseconds are in the trial CSV. 1.600 s 1.700 s Measured median: 1.651 s Warmup Warmup: 1619303200 ns 1.619 s Trial 1 Trial 1: 1658595900 ns 1.659 s Trial 2 Trial 2: 1658341800 ns 1.658 s Trial 3 Trial 3: 1651407800 ns 1.651 s Trial 4 Trial 4: 1632298200 ns 1.632 s Trial 5 Trial 5: 1683302400 ns 1.683 s Trial 6 Trial 6: 1644345600 ns 1.644 s Trial 7 Trial 7: 1626761800 ns 1.627 s
Individual fresh-process times. The gray warmup is excluded from the median; displayed seconds are rounded to 0.001 s. Exact nanoseconds remain in the CSV.

All attempts, including the excluded warmup, are retained in the raw records. Peak memory, child CPU time and interpreter internal phase timings are unavailable. The host activity note and actual Python executable identity are in the saved record.

Saved JSON · Trial CSV · Raw process output and attempts · File hashes

Environment

{
  "os": "Windows-11-10.0.22631-SP0",
  "processor": "Intel64 Family 6 Model 151 Stepping 5, GenuineIntel",
  "logical_cores": 12,
  "python_version": "3.13.5 (tags/v3.13.5:6cb20a2, Jun 11 2025, 16:15:46) [MSC v.1943 64 bit (AMD64)]",
  "python_executable": "python.exe",
  "python_executable_sha256": "5341746f92483a93e44c313de830f2fba2956f0759094404a16b2fed06c9a2ed",
  "optimization": "CPython -O; -B disables bytecode writes",
  "arithmetic": "fractions.Fraction exact rational on printed decimal inputs",
  "configured_workers": 1,
  "observed_threads": {
    "available": false,
    "reason": "not measured"
  },
  "peak_memory": {
    "available": false,
    "reason": "not measured"
  },
  "child_cpu_time": {
    "available": false,
    "reason": "not measured"
  },
  "cache_policy": "new interpreter each attempt; OS file and instruction caches may be warm",
  "host_activity": "At 2026-10-16T12:10:55Z UTC, the coordinator reserved the local host for the reviewed B08 exact run. No cl, cmake, ctest, msbuild, or ninja process was active; only idle Python service processes appeared. Other agents deferred local builds, tests, and measurements during this window. This note is point-in-time host activity evidence, not continuous instrumentation.",
  "clock": "parent time.perf_counter_ns"
}

Versioned publication b08-displayed-exact-5db00478351f310ecece0eae0187ace7de79b8c0850c958568232dd0bc779116; native report b08-exact-b0d0e85d4d338f56. Report envelope · Publication manifest.