Aim

Do two fixed synthetic metric streams retain their step ordering and run identity after export and comparison?

Compare stored/exported histories with an independently specified event ledger, including duplicate steps and interrupted runs.

What you could produce

• A version-pinned protocol stating inputs, rights, expected behavior, tolerances and resource limits before execution.
• A retained per-case result and failure ledger with an independently controlled comparison, if qualified execution is later authorized.

Before you use it

• Python and tracking/storage dependencies; UI/server deployment and access policy require separate assessment.
• A separately qualified isolated runtime with a reviewed, pinned dependency and input closure.

Limits to keep in view

• No source program, example, build hook, package, dataset, model or generated research code has been executed or downloaded as a payload.
• The documented self-contained Python 3.13, 90-second pilot does not establish support for this package, its compiled dependencies, GPUs, services or agent sandboxes.
• Installation success, scientific outcomes, runtime compatibility, latency, memory use, API costs and security properties are unmeasured.

Source and permission context

Preserve the upstream project name, repository, exact source commit and applicable contributor/notices; resolve upstream citation guidance for any later formal use.

License evidence recorded. Review the scope and upstream conditions before reuse.

Still unresolved

• Only the cited license and README texts were observed; file exceptions, dependency closure, vendored components and submodules are not comprehensively audited.
• Dataset files, task prompts, generated outputs, model weights, tokenizer assets and hosted APIs are not cleared by a root code license.
• README/documentation reuse rights and version-specific citation guidance remain separately unresolved; only links and original descriptions are retained.