The original historical content below is retained for traceability. It is not the default current-example catalog. Availability statements are superseded by the current status above.
VG1 status · 12 September 2026 (Europe/Istanbul)VG1 has been deployed. Customer scan-to-report acceptance is still pending.
The free first-beta scope is eligible public models up to and including 7B, within the account allowance, for checkpoint comparisons and in-memory quantization simulations. Customer jobs run on RunPod. (Superseded on 22 September 2026: scans run on Tetracta-operated local GPU workers; no cloud GPU is used in this beta.) The service selector defines the supported revisions and scan types. Later Pro access above 7B requires an explicit grant and remains limited to the models and allowance enabled for that account.
The thirteen existing sample reports retain their own dates, versions and recorded evidence. They are not results of the current customer acceptance test. The 7 September sample documentation below is retained as historical context and is superseded in more than its coverage wording. Read it only as a record of what we published on that date. In particular: on 12 September 2026 we corrected the characterization of the unmeasured positions — describing them as lying below an instrument floor was wrong; it was a scanner-coverage limit, and the current report format says "not evaluated" instead. The depth and location wording below, including onset depth and the comparison of a fine-tune with a structural lesion, is not how the current release describes itself, and no claim below is reinstated by its presence here. The standing record is the dated correction page: https://www.tetracta.ai/model-xray/correction/
A report describes its recorded artifacts and measurement conditions; it is not a model-quality ranking, safety certificate or deployment verdict. A quantization simulation does not create a deployable quantized model. Knowledge scans remain unavailable and earlier withdrawn claims remain withdrawn. Hallucination, undertraining and overtraining remain research questions, not measured product features.
Service status · Current scope and report guide · 12 September correction
Historical sample documentation · 7 September 2026
Status. New scans are paused while validation is pending. These thirteen reports are the current sample reports. Earlier sample files were withdrawn on 4 September 2026 and removed from this tree; they remain in repository history as withdrawn material. This update does not announce service reopening or payment activation.
Part 3 — 7 September 2026 (Europe/Istanbul)
When a public model was fine-tuned by us on four consecutive decoder blocks at a known depth (LoRA r=8 on blocks LO..LO+3, merged; three depths), the reported onset matched the first fine-tuned block in 3 of 3 cells (blocks are numbered from 1). This does not establish behaviour on fine-tunes produced by others, whose depth and magnitude are unknown.
Frozen B7 preregistration SHA-256: 1028eedb853fb662aeb85a6d5f0404df1dcf99d367088bc2c94a9000a3243977.
Two controls were run first: one artifact, re-serialized into a different shard layout with identical tensor values, was reported as no difference; a known lesion reported a difference at the expected depth. In 3 controlled micro-fine-tune pairs (single model family), every difference this instrument reported was also visible in the model's output text. We have not yet produced a case where the instrument reports a difference that a plain output comparison would miss. Until we do, we make no claim that it can.
Frozen B8-SD preregistration SHA-256: d2dae32fa361f16a9f660241181b4a5bd19ca44338d284b15dbfc57e0c7a6d9d.
Onset localization works on our controlled fine-tunes; added value over plain output comparison is not yet shown.
The reading tells you where a change first becomes observable. It does not tell you how large the change is, or what kind of change it was: in our controlled tests, a fine-tune and a structural lesion at the same location produced the same reading.
Configuration comparison is limited to the compared fields. Numeric-precision fields are not compared here; any file difference is recorded in the artifact identity.
What changed in Part 2
Reports now show categorical onset depth, a depth map and the extent of the observable difference. For all ten reports the difference is already present at the first evaluable position, so it may begin earlier, below the instrument floor; no starting depth is reported for these pairs.
Calibration: exact onset predicted and observed in 6 of 6 controlled cells on each of three public models (Qwen2.5-0.5B-Instruct, SmolLM2-1.7B, TinyLlama-1.1B-Chat-v1.0); cross-board agreement on onset 4 of 4 cells. These controlled changes do not establish performance on changes that arise naturally. The first four profile positions, the embedding output and the outputs of blocks 1 to 3, are below the instrument floor.
Null control
16 of 16 A = B comparisons completed across four models and two card classes: 0 observed differences and 0 output-text changes; two-sided exact 95% Clopper–Pearson interval 0–20.59%. This describes the tested matrix, not a population error rate.
0 / 16
observed differences in A = B controls
6 / 6
sample pairs with the same categorical result on both card classes
13
published sample reports
Reports
Rows 9–10: numeric precision (torch_dtype) differs; recorded in the artifact identity.
Rows 11–13 are controlled fine-tunes produced for calibration; not for use. Their B identifiers are local checkpoint SHA-256 values, not uploaded model revisions. No checkpoint files are included.
Reading rows 1–10
Rows 1–8 have different output contracts, so output text is withheld. Rows 9–10 share a comparable output contract: the recorded text was compared and differs. The depth maps record a difference at every evaluable position. No weights-only or pure fine-tuning attribution is made. Training claims for rows 9–10 are the authors’ descriptions and were not independently checked.
Rows 9–10 were also run on RTX 4060 with the same difference, output-text status and onset status; their card class and runtime are recorded in the full-revision index. The sample-pair agreement of 6 of 6 pairs is separate from the controlled experiment’s 4 of 4 cells.
TinyLlama configuration comparison is identical in the compared fields; tokenizer semantics differ. Commercial service admission rights review is still pending, separately from this publication. Row 10 uses the SmolLM2-1.7B-Instruct revision of 4 December 2024 to match the derivative’s tokenizer length and chat contract.
Read Scope & Limitations and the correction record. Numerical profiles remain private. No numerical equivalence across card classes or runtimes, quality verdict, or fitness-for-use assessment is claimed.