Engineering record / access by scope
A diligence room with visible limits
Start with dated public records and exact source links. Source code, private health telemetry, customer data and confidential annexes require controlled access and are not exposed here.
Public records available now
| Record | What it supports | Limit |
|---|---|---|
| Index edition manifest and corrections | Frozen 2026.7 score bytes, method version and claim changes. | Public-evidence rubric; not a product code audit. |
| 98-cell evidence explorer | Archived assessment, cited source, access state and review adjustment. | Source access and documentation are distinct from behavior. |
| Signed own-API sample package | Offline digest, signature and tamper checks on a dated vendor sample. | No scan-bound customer inventory or independent key authority. |
| Benchmark protocol and vendor inputs | Dated corpus, Pulse and workflow boundaries; preregistration requirements. | No equal-access peer product result. |
QScout's currently deployed source identity and hard-green production parity must be checked in a controlled release record before they can be listed as verified deployment facts. This page intentionally does not publish private operational endpoints, secrets or an unverified green badge. An open PR is not a released build.
Independent evaluation packet
Status: ready to scope; no outside conclusion published. A credible assessor receives a frozen build digest, allowed test estate, seed cases, raw output format, failure criteria, source access terms, time budget and publication rights before running tests. The assessor controls its methods and reports adverse findings. Record affiliation, funding and reviewer independence alongside the final report. Internal QQ-SWARM work is disclosed as internal review and never presented as outside certification.
A disputed finding should be reproducible under the same build and input manifest. An evaluator may report that QScout fails a task; that result remains part of the record.
Permissioned pilot outcome protocol
Status: protocol ready; no customer outcome published. Before a pilot, agree in writing on assets in scope, baseline denominators, task definitions, expected benefits, error review, exact build, follow-up period, customer verification and publication rights. Measure completion and rework as well as detection. A permissioned pilot requires the customer's written consent; a prepared protocol cannot be counted as a testimonial or validated outcome.
Do not infer customer identities or production coverage from Qtonic Quantum Corp's own dogfood Pulse export.
Request a scoped evaluation
Use the research challenge channel to identify a concrete disputed claim or proposed test scope. Do not include credentials, source code or customer data in that message. Private access, commercial terms and any external assessor engagement are handled separately with written authorization.