Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

instrument implementation / implementation-contract

Algorithm Runtime Estimator implementation

A source-bound implementation contract for Algorithm Runtime Estimator; deployment and executable qualification remain separate.

Status: VERIFIED_CLEANLifecycle: implementation-contract

Binding contract

This record describes what an executable surface must bind and validate. It does not claim that a public calculator, package, or production route is deployed.

Record owner
Guth Instruments
Lifecycle
verified-clean
Evidence ID
t4-172
Effect
Computation or source lookup only

Input and validation requirements

A zero operations-per-second rate makes the runtime denominator vanish, requiring rejection or producing Infinity in plain JavaScript. The O(n log n) convention is also under-specified because the logarithm base changes the estimate.

Required corrections

No binding erratum is attached to this unique-name record. Implementers must still preserve the declared units, domain, and failure behavior.

Inspectable interface fixture

The sample below is evidence for interface and validation tests, not a production implementation.

{
  "inputs": {
    "n": 7500000,
    "complexity_class": "O(n)",
    "rate_ops_per_sec": 2500000
  },
  "expected_outputs": {
    "ops": 7500000,
    "runtime_seconds": 3,
    "human_runtime": "3 s"
  },
  "working": "f(n)=n=7,500,000 ops. time=ops/rate=7,500,000 ÷ 2,500,000=3 seconds. 3 seconds=3 s."
}

Other records

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

  • VERIFIED_LEDGER.json
  • evidence-tranche4/tranche4-results.json