TETRACTA · MODEL X-RAY

Quantization simulation

Source model compared with its simulated lower-precision state
Verify view · Decision, output status and available verification evidence; depth observations are not included
VG1 · betars-1.7 · rp-1.3
A · SOURCE
Qwen/Qwen2.5-7B
@ d149729398750b98c0af14eb82c78cfe92750796
Reference artifact
→
B · PARTIAL INT8 WEIGHT SIMULATION
Qwen/Qwen2.5-7B
Not a deployed quantized artifact. Derived in memory from A.
≠
VALIDATION-PENDING DESCRIPTIVE RESULT · no calibrated risk or pass/fail grade
Difference observed
The response difference met the versioned instrument decision rule under this exact simulation contract.
Internal response
Observed
Response difference on the evaluated set
Text output
Changed
At least one generated continuation differs under exact token-sequence comparison. The comparison uses the same tokenizer and greedy-generation contract; it is not a semantic-quality judgment.
Repeat check
2 / 2
Matching versioned measurement payloads reported from fresh processes within one allocation.

Included summaries Content and scope, not a quality or risk grade

Record or summaryThis report
Measurement summaryIncluded
Repeat-check summaryIncluded · 2 / 2 matching measurement payloads reported
Same-artifact control summaryIncluded · 2 / 2 comparisons produced no finding
Underlying recordsRetained in the VG1 archive; not included in this copy
Operational receiptNot included · unsigned review copy
Statistical noise envelopeNot certified

Repeat and control details

Repeat checkThis completed allocation was configured for 2 repeat measurements; all 2 completed and their versioned measurement payloads matched byte for byte. The payload contains all versioned measurement fields. Execution identifiers, runtime records and timing metadata are recorded separately; they are not part of this equality claim. Fresh processes and model loads within one allocation; this does not establish agreement across devices or allocations. Counts refer to this allocation, not the full development history. No preregistration claim is made.
Same-artifact controlThe matching same-artifact control allocation was configured for 2 measurements; all 2 completed. 2 / 2 recorded no internal finding and matching token sequences. These are observed controls, not a calibrated noise envelope or an error-rate estimate.
Operational receiptNo customer-verifiable signed receipt is included in this HTML copy. No signature or deletion claim is made.
Noise-floor statusNo model-specific statistical noise envelope is certified by this report.

What this means for you

MeasuredThe internal-response comparison met the instrument decision rule on the fixed input set. Use this as evidence of a recorded change when reviewing the candidate; the report does not rate that change as beneficial or harmful.
Text outputThe output-text comparison also observed a change.
PriorityCheck output stability first. Exact continuations changed with a shared output contract. Review formatting and exact-match workloads first; this scan does not determine whether those changes are improvements or regressions.

How the finding was decided

The reported internal finding uses the fixed, thresholded decision rule recorded for mv-1.4; it is not a test for any non-zero floating-point value. This rule is not, by itself, a measured noise floor for this model.

Text output is evaluated separately under exact greedy token-sequence comparison. The outcome is on the fixed input set, not a population rate or a capability score.

Structural coverage: 24 contributing probes per evaluated position. This is neither the number of output continuations nor a count of independent tasks.

Verify view

This view includes the decision, output status, available verification evidence and context. The finding and output-text status are unchanged; this version makes no statement about internal position.

What A and B represent

A is the source model. B is a partial in-memory block-weight simulation of that same model. B has no separate repository revision or deployable file.

The result describes this simulation only. It cannot establish the memory use, latency, task quality or numerical behavior of a packed inference implementation.

Recommended next checks Guidance, not a measurement

  1. Choose the actual candidateSelect the exact deployable quantized artifact and its inference implementation; retain the source revision with the comparison record.
  2. Check the customer workloadCompare source and deployed candidate on your own prompts. Record answer quality, formatting, latency and memory separately.
  3. Confirm the deployed changeRequest a direct before/after scan of the supported deployed artifact. A simulation result does not transfer automatically to that artifact.

Provenance and record

InstrumentVG1
Measurement contractmv-1.4
Report schema / presentationrs-1.7 / rp-1.3
Simulationqsim-2.0 · simulated int8

No operational receipt is included in this copy. No signing or deletion claim is made.

Recorded context

Pin these fields when you diff this report against a future scan. Matching context is a prerequisite for interpretation, not proof of the cause of a difference. These recorded public identities help identify the input artifacts. This review copy is unsigned; no customer verification receipt is attached.

Run window (UTC)2026-09-08 11:06:37 UTC to 2026-09-08 11:17:30 UTC
Model referenceQwen/Qwen2.5-7B
Artifact evidenceArtifact-identity and measurement records are preserved in the VG1 archive; this HTML contains no model weights
HF revisionA: d149729398750b98c0af14eb82c78cfe92750796 · B: derived simulation from A; no separate repository revision
Probe set / scan configps-1.1 / sc-1.0
Simulation versionqsim-2.0 · in-memory simulation; the deployed artifact was not scanned
Reference setno release reference set; estimator validation pending
Report schemars-1.7
Compute isolationmanaged compute; infrastructure identity is withheld
Runtime envelopefixed release configuration; bitwise equality across device types is not guaranteed

Reading this report alongside another scan

Check the artifact pair, revisions and measurement contract first. The categorical findings describe each recorded comparison; they do not rank different models. A different contract or execution environment needs its own comparability evidence. No numerical severity score is supplied.

Use as a checkpoint reference

For supported checkpoint comparisons, retain the starting revision, this measurement contract and the output settings with your training record. Compare the next checkpoint against that same reference, then retain its task results alongside the scan.

For the next checkpointRecord alongside this scan
Reference and candidateExact repository revisions
Comparable measurementSame instrument, input contract and approved execution profile
Training changeYour fine-tune, merge or pruning record
Adoption decisionYour task acceptance results and deployment revision

A reference record supports change tracking. It does not define an optimal model or a target score for training. Simulation results describe the simulated state; actual checkpoint changes require their own before/after comparison.

Your findings and the protected instrument

Delivered to you

The observation, output-text status, artifact context and, where applicable, metadata comparison, plus provenance and categorical depth detail when included.

Kept private

Raw profiles, per-item records, probe construction, thresholds, transformations and internal traces. The report contains no model weights, credentials or infrastructure identifiers.

Honesty box — scope and limits

This is an in-memory simulation, not a packed kernel or a scan of a deployed quantized artifact. This descriptive result does not identify cause, capability, quality, safety or deployment impact. It is not a task-quality measurement. Do not target a layer or make a shipping decision from this report alone. No calibrated risk or pass/fail grade is assigned. No cross-model ranking or cross-device bitwise-equality claim is made.

Historical results under superseded estimators do not validate this release. The categorical depth view, when included, describes recorded responses; it is not a diagnosis of edited weights.