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

instrument implementation / implementation-contract

Network Speed Test Result Interpreter implementation

A source-bound implementation contract for Network Speed Test Result Interpreter; 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
t7-057
Effect
Computation or source lookup only

Input and validation requirements

A zero download rate causes transfer-time division by zero and requires rejection or an explicit undefined result. The lookup results also depend on exact threshold inclusivity, and throughput and ping unit ambiguity can change the reported transfer time or video-call assessment.

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": {
    "download_mbps": 25,
    "upload_mbps": 10,
    "ping_ms": 20,
    "file_size_gb": 1
  },
  "expected_outputs": {
    "supported_use_cases": {
      "streaming": [
        "SD",
        "HD",
        "4K/UHD"
      ],
      "video_call": "HD",
      "ping_quality": "excellent"
    },
    "transfer_time_seconds": 320,
    "transfer_time_human": "5 min 20 s"
  },
  "reference_data": {
    "streaming_thresholds_mbps": {
      "SD": {
        "download_mbps": 3,
        "source_convention": "widely tabulated standard value; Netflix-published minimum guidance, bundled snapshot required"
      },
      "HD": {
        "download_mbps": 5,
        "source_convention": "widely tabulated standard value; Netflix-published minimum guidance, bundled snapshot required"
      },
      "4K/UHD": {
        "download_mbps": 15,
        "source_convention": "widely tabulated standard value; Netflix-published minimum guidance, bundled snapshot required"
      }
    },
    "video_call_thresholds_mbps": {
      "standard": {
        "download_mbps": 1.5,
        "upload_mbps": 1.5,
        "source_convention": "widely tabulated standard value; published video-conferencing guidance, bundled snapshot required"
      },
      "HD": {
        "download_mbps": 3,
        "upload_mbps": 3,
        "source_convention": "widely tabulated standard value; published video-conferencing guidance, bundled snapshot required"
      }
    },
    "ping_bands_ms": {
      "excellent_max": 50,
      "source_convention": "widely tabulated standard value; general latency guideline"
    },
    "table_comparison": "greater than or equal to threshold"
  },
  "working": "Streaming: 25>=3, so SD is supported; 25>=5, so HD is supported; 25>=15, so 4K/UHD is supported. Video call: min(25,10)=10 Mbps; 10>=3, so HD is supported. Ping: 20<=50 ms, so ping quality is excellent. Transfer: 1 GB*8,000=8,000 megabits; 8,000/25 Mbps=320 s; 320 s=5 min 20 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-tranche7/tranche7-results.json