Doses AI · Research

Pestle-27B
Ternary

8.2× weight compression with 96.48% median capability retention-
achieved on a single H100 in approximately 40 hours.
96.48%
Measure-level median retention
89.79%
MedQA (full test split)
6.75 GB
Deployed text weights
8.2×
Smaller than FP16 parent
Technical Report V6 · Doses AI · August 2026 · 17-measure matched evaluation record · huggingface.co/Doses-AI/Pestle-27B-Ternary-GGUF
Technical Report · August 2026

Pestle-27B-Ternary

Doses AI Research  ·  London  ·  research@doses.ai
Abstract

Medical language models are most valuable where data is least able to leave the institution. We present Pestle-27B-Ternary, a 27-billion-parameter medical language model produced with Doses AI's proprietary ternary compression algorithm. Its deployed text-weight payload is 6.75 GB - 8.2× smaller than the 55.56 GB FP16 parent - and is packaged as one 8.48 GB runnable GGUF, while achieving a 96.48% measure-level median across a 17-measure matched evaluation record. Pestle reaches 89.79% on the full 1,273-question MedQA test split, 86.89% across MMLU medical subjects, 75.28 token-F1 on BioASQ, and 90.15 MRR on PharmaRAG. The model is also a systems proof: a single-H100 conversion workflow can turn institution-owned medical and pharmaceutical models into smaller artifacts that are acceptance-tested and served locally. We report the included benchmark record, the mortar.cpp runtime, institutional deployment patterns, and measured limitations; the compression recipe remains Doses AI intellectual property.

Release at a glance

ModelPestle-27B-Ternary - a 27B medical language model derived from the Qwen3.6-27B architecture
CompressionDoses AI Ternary Compression Algorithm; served by mortar.cpp
Footprint and retention8.2× smaller deployed text weights - 6.75 GB versus 55.56 GB for the parent - packaged as one 8.48 GB runnable GGUF, with a 96.48% measure-level median across the 17-measure matched evaluation record
Conversion envelopeOne H100-class GPU; private conversion and retention-calibration pipeline with public artifact and evaluation evidence
Headline resultsMedQA 89.79 · MMLU medical 86.89 · BioASQ F1 75.28 · PharmaRAG MRR 90.15
Inferencemortar.cpp - architecture-aware low-bit engine; approximately 39 tok/s single-stream and approximately 916 tok/s aggregate at concurrency 32 on retained accelerator records
ModalityText generation; medical visual QA uses the parent vision encoder with the compressed language core
LicenseApache 2.0 - open weights, open inference engine, retained evaluation evidence

Contributions

1 · Matched evidence accounting. Every measure in the reported 17-measure distribution appears in the tables and retention figure; paired MMLU subjects enter individually.

2 · Capability per deployed byte. Pestle delivers an 8.2× smaller deployed text-weight payload - 55.56 GB to 6.75 GB - with a 96.48% measure-level median across the matched evaluation set. The complete runnable GGUF is 8.48 GB.

3 · A verifiable release. Pinned artifacts, evaluation summaries, and row-level audit ledgers accompany the model, while the conversion recipe remains proprietary.

4 · A repeatable institutional proposition. Pestle demonstrates a private workflow for compressing hospital- and pharma-owned specialist models into locally deployable assets, subject to task-specific acceptance thresholds.

1Why a ternary medical model

Clinical data cannot commute. The records, images, and messages that make medical models valuable are governed by privacy law and institutional policy, yet a matched 27B-class FP16 parent occupies 55.56 GB before runtime cache. At the small batches typical of local serving, decoding is often memory-bandwidth constrained; reducing the weight representation therefore changes where the model can run, not merely how cheaply it can be stored.

Design goal. Pestle applies a ternary operating point to this deployment constraint: maximize retained medical capability per deployed gigabyte, preserve the source architecture, and release the artifact and evidence required to verify the result. It also serves as a reference for compressing hospital- or pharma-owned specialist models against institution-defined acceptance suites, returning locally deployable assets for 8-18 GB accelerators or unified-memory workstations without making patient-data egress structural.

2Model

Pestle retains the Qwen3.6-27B architecture and is produced with Doses AI's proprietary ternary compression algorithm. Its deployed text weights total 6.75 GB; the runtime consumes the released 8.48 GB GGUF package directly, with no external cloud model required in the serving path. Figure 1 shows the conversion and serving path; Figure 2 shows the model structure.

Input checkpoint
Qwen3.6-27B
Architecture retained
55.56 GB FP16 text weights
Compression procedure
Doses AI ternary compression
Single-H100 production run
Approximately 40 hours; acceptance evaluated after conversion
Released system
Pestle-27B-Ternary
6.75 GB deployed text weights
8.48 GB runnable GGUF; served with mortar.cpp
Figure 1. Summary of the released conversion. The source architecture and serving interface are retained; the public result is an 8.2x reduction in deployed text-weight size with a 96.48% median across the 17 matched evaluation measures.

2.1  Model structure

tokens Embedding compressed 64-block hybrid-attention reasoning core gated linear attention · periodic full attention · SwiGLU Doses AI ternary-compressed decoder Qwen3.6-27B architectural topology retained LM head compressed logits Pestle-27B-Ternary · 6.75 GB weights · 8.48 GB runnable GGUF
Figure 2. Pestle retains the Qwen3.6-27B model structure: token embedding, a 64-layer hybrid-attention core, and language-model head. Doses AI's ternary compression algorithm produces a 6.75 GB deployed text-weight payload, distributed as one 8.48 GB runnable GGUF, without changing that architectural topology.

2.2  Compression training - measured behavior

The Doses AI Ternary Compression Algorithm converts a dense source checkpoint into a compact ternary deployment artifact while preserving the source architecture and serving interface. The production run was monitored throughout compression training with full WikiText-2 perplexity measurements. This public account reports the measured training trajectory, single-H100 compute envelope, final artifact, checksums, and matched task performance; the internal transforms, optimization targets, calibration construction, and schedules remain Doses AI intellectual property.

Perplexity through compression training and the final precision choice
Full WikiText-2 PPL recorded as compression training progressed, paired with the final Block 63 precision decision. Training progress is normalized; implementation-level stage identities are not disclosed. Lower PPL is better.
Figure 3. Left: 64 successive post-stage measurements, beginning at 7.562 PPL and reaching 14.507 at the fully reconstructed ternary endpoint. Right: a magnified paired validation in which the repaired ternary candidate is held fixed and only Block 63 precision changes; matching-parent BF16 reduces full WikiText-2 PPL from 12.677 to 12.302. The training trace documents run behavior; it is not a causal per-stage ablation.

The final deployment decision

Block 63 is retained in BF16 because its measured quality gain outweighed its bounded footprint cost. In a paired full-corpus evaluation, changing only that block's precision lowered PPL by 0.375, or 2.96%. The BF16 block contributes 0.745 GB and 0.221 BPW across the 26.9B text-weight accounting, moving the materialized text payload from 6.002 GB / 1.785 BPW to 6.747 GB / 2.007 BPW. The result remains 8.2× smaller than the 55.56 GB BF16 parent.

Release-stage loop stability. A separate stability repair in the final release reduced pathological repetitive reasoning loops. On 152 held-out cases selected because an earlier candidate had entered a literal token loop, same-seed replay showed 99/152 (65.1%) escaped or avoided the loop. The remaining 53 cases preserve an important boundary: the repair materially reduced looping but did not eliminate it, so production serving still uses an exact-loop guard and explicit output ceiling.

What the public release verifies

The external proof is the shipped operating point: 6.75 GB of deployed text weights, one 8.48 GB runnable GGUF, approximately 40 hours on one H100, deterministic runtime checks, and the matched evaluation ledger reported in Sections 3-4.

Interpretation. Perplexity is a sensitive engineering diagnostic for compression drift; downstream capability is established separately by the frozen benchmark suite. The normalized trace shows how the run was monitored without exposing the proprietary training recipe.

2.3  The ternary model

Pestle is produced from the Qwen3.6-27B architecture with Doses AI's proprietary ternary compression algorithm. It carries 6.75 GB of deployed text weights and ships as one 8.48 GB runnable package executed by mortar.cpp. Weight-payload compression and runnable-package size are reported separately: the 8.2× ratio compares the parent's 55.56 GB of text weights with Pestle's 6.75 GB payload.

The production conversion path is designed for a single H100-class GPU, allowing specialist-model compression without a multi-node training cluster before validation against an institution's own acceptance suite. The conversion process remains Doses AI intellectual property; the released model, runtime, checksums, and benchmark record form the public verification boundary.

2.4  Storage accounting

Artifact viewRoleNominal / effective BPWDeployed text weightsRunnable artifact
Qwen3.6-27B FP16 parentMatched source reference16.00 / 16.0055.56 GB55.56 GB
Pestle-27B-TernaryReleased deployable model1.79 / 2.526.75 GB8.48 GB
Weight-payload ratioMeasured deployment accounting--8.2× smallerreported separately
Table 1. Public storage accounting. Pestle's 6.75 GB deployed text-weight payload is 8.2× smaller than the exact 55.56 GB matched FP16 parent; the complete runnable GGUF is 8.48 GB. Runtime cache and allocator overhead remain workload-dependent.

2.5  Release boundary

PUBLIC RELEASE 6.75 GB weights · 8.48 GB Pestle runnable GGUF mortar.cpp runtime and deployment interface Checksums, benchmark summaries, row-audit ledgers Apache 2.0 model and runtime licensing PROPRIETARY CONVERSION PIPELINE Model conversion software Calibration and optimization systems Customer-specific acceptance design Production engineering workflow
Figure 4. Product boundary. The model, runtime, checksums, and evaluation record are public; the conversion pipeline that produces the artifact is Doses AI IP.

2.6  Release artifacts

Release objectPurposeVerification
Pestle-27B-Ternary model package8.48 GB runnable GGUFRepository checksums
mortar.cppLocal CPU, Metal, and CUDA inferenceVersioned source and runtime identity
Evaluation ledgerScores, row IDs, finish states, grading summariesPinned model and protocol metadata
Table 2. Public release objects. Exact file hashes remain in CHECKSUMS.sha256 alongside the model rather than being duplicated in the paper.
Reading the comparisons. Pestle, Qwen FP16, Bonsai, and Qwen IQ2_XXS medical rows are locally measured under the matched protocol. MedGemma and other external values are separately labeled published references and should be interpreted under their source protocols.

3Evaluation

Matched protocol. The local Pestle, Qwen3.6-27B FP16, Bonsai-27B Ternary, and Qwen3.6-27B IQ2_XXS medical runs use deterministic greedy decoding with thinking disabled: temperature 0, top-p 1, top-k 0, no repetition penalty, and seed 20260805. MedQA uses the complete 1,273-row test split. Dataset-specific output allowances, loop stops, completion states, and grading summaries are retained in the evaluation ledger.

BenchmarkMetricPestleRowsInterpretation
Medical knowledge, evidence and retrieval
MedQA (full test)accuracy89.791,2731,143 correct; primary clinical reasoning endpoint
MMLU medical overviewrow-weighted accuracy86.891,784overview value; subject results in Table 4A
BioASQtoken-F1 / exact match75.28 / 55.944,950open-ended biomedical evidence QA
PharmaRAGMRR / nDCG@1090.15 / 84.62400pharmaceutical retrieval ranking
PubMedQAaccuracy / macro-F176.70 / 62.781,000biomedical yes/no/maybe reasoning
MedMCQAaccuracy68.854,183broad medical entrance-exam knowledge
MedXpertQA (text)accuracy32.492,450expert-level, 10-option stress test
ChemBenchaccuracy61.722,785chemistry and laboratory knowledge
Medical visual QA - secondary, parent vision encoder
VQA-RAD (original test)token-F1 / closed acc.53.49 / 67.73451original split; not directly comparable to MedGemma
SLAKE (English)token-F1 / closed acc.54.81 / 74.081,061experimental capability; see Section 5
Broader capability
MMLU-Redux 2.0accuracy83.535,700broad knowledge and reasoning
GSM8K / MuSRaccuracy93.25 / 70.501,319 / 756math and multi-step reasoning
HumanEval / HumanEval+pass@189.02 / 87.20164code generation, greedy
MBPP+ / IFEvalpass@1 / prompt-strict83.33 / 81.70378 / 541coding and instruction following
Table 3. Final validated Pestle results used in this report. A dash means the public summary does not state a row count. Scores are not averaged across unlike metrics. Benchmark values are synchronized to the private model card at revision 14318a1b41e7af25d274c42089740d2846617b40.
Comparison sources. Pestle, Qwen FP16, Bonsai, and Qwen IQ2_XXS medical rows in Table 4 are locally measured under the matched protocol. MedGemma and other external values are published reference points. This report evaluates benchmark capability retention; it does not claim clinical validation.

4Results

4.1  Capability density across the matched evaluation record

The central result is a joint operating point: Pestle delivers an 8.2× smaller deployed text-weight payload - 55.56 GB to 6.75 GB - with a 96.48% measure-level median across 17 matched measures. The complete runnable GGUF is 8.48 GB. Each measure enters once; the MMLU medical overview is reported separately from the subject-level measures used in the matched distribution.

Capability per runnable-artifact gigabyte
MedQA accuracy against complete runnable-artifact size; filled markers denote locally measured runs.
Figure 5. Pestle reaches 89.79 MedQA in an 8.48 GB runnable GGUF, compared with 93.87 at 55.56 GB for the locally matched parent. This plot uses complete runnable-artifact size so every marker shares one packaging basis; Pestle's underlying deployed text-weight payload is 6.75 GB. The locally measured IQ2_XXS artifact is included as a compact Qwen reference; MedGemma remains a hollow published-reference marker.
Medical retention distribution
Pestle score divided by the locally matched Qwen3.6-27B FP16 score across 17 matched evaluations; each measure contributes once.
Figure 6. Complete measure-level distribution across the 17 matched evaluations. The median is 96.48%; ratios at or above the parent are displayed in the parity band.
Interpretation. Pestle combines a strong medical knowledge, biomedical evidence, and retrieval profile with an 8.2× smaller deployed text-weight payload. The V6 benchmark record is reported in Tables 4A-5.

4.2  Comparative medical profile

Small multiples preserve each benchmark's native scale and show every one of the 17 text-model measures entering the reported medical median. Pestle, Qwen FP16, Bonsai, and Qwen IQ2_XXS are locally measured under the matched protocol and use filled bars. MedGemma uses outlined bars as a published contextual reference. Missing bars indicate that no validated metric-matched value was available.

Figure 7. All 17 text-model measures used in the reported medical median, shown across five 27B-class systems wherever a validated metric-matched value is available. Filled bars denote local matched runs (Pestle, Qwen FP16, Bonsai, and Qwen IQ2_XXS); outlined MedGemma bars denote published contextual references.

4.3.1  Medical comparison matrix - clinical knowledge and reasoning

MMLU medical rows remain inside clinical knowledge and reasoning. The current model-card values are reproduced at subject level, alongside the compact IQ2_XXS reference. Parent retention is a score ratio, not a percentage-point difference.

BenchmarkPestle
local
Qwen FP16
local
RetentionMedGemma 27B
published
Bonsai 27B
local
Qwen IQ2
local
BPW (nominal / deployed)1.79 / 2.5216.00 / 16.00--16.00 / 16.001.71 / 2.132.06 / 2.80
Deployed weights / runnable artifact (GB)6.75 / 8.4855.56 / 55.568.2× smaller weights-- / 54.02-- / 7.17-- / 9.39
Clinical knowledge and reasoning
MedQA89.7993.8795.65%89.8 best-of-5
87.7 zero-shot
78.2489.40
MedXpertQA32.4941.1079.05%25.720.8231.22
MedMCQA68.8573.7093.42%74.258.5968.40
MMLU Anatomy86.6792.5993.61%83.768.1584.44
MMLU Clinical Knowledge90.1992.4597.56%86.084.5390.19
MMLU College Biology96.5397.9298.58%96.594.4497.92
MMLU College Medicine89.6090.1799.37%86.184.3988.44
MMLU Medical Genetics96.0099.0096.97%97.089.0098.00
MMLU Professional Medicine94.8595.9698.84%93.488.9793.38
MMLU Virology56.0256.02100.00%53.650.6056.02
Additional matched evaluations
ChemBench61.7268.7389.80%--61.33--
Table 4A. Final clinical knowledge and reasoning comparison. All locally measured medical runs for Pestle, Qwen FP16, Bonsai, and Qwen IQ2_XXS use greedy, thinking-disabled decoding (temperature 0, seed 20260805). MedGemma values reproduce its officially reported 27B reference results.
Matched retention. The seven paired MMLU medical subjects have a 98.58% median; the complete 17-measure matched evaluation record has a 96.48% measure-level median.

4.3.2  Medical comparison matrix - evidence, retrieval, and vision

This continuation keeps open-ended biomedical extraction, retrieval, and image-conditioned tasks in the same medical evidence record. Vision values are reported as measured capabilities but are not included in the 17-measure text-model retention statistic.

BenchmarkPestle
local
Qwen FP16
local
RetentionMedGemma 27B
published
Bonsai 27B
local
Qwen IQ2
local
Biomedical QA and retrieval
PubMedQA accuracy76.7079.5096.48%77.2 multimodal77.7078.30
PubMedQA macro F162.7864.6197.17%--62.1757.74
BioASQ token F175.2876.6598.21%--75.46--
BioASQ exact match55.9459.4994.03%--54.12--
PharmaRAG MRR90.1593.9196.00%--92.60--
PharmaRAG nDCG@1084.6290.8493.15%--89.43--
Medical vision
CXR14 adjudicated macro F134.28----45.3 multimodal----
CheXpert expert validation macro F151.03----49.9 c----
VQA-RAD tokenized F153.4966.6980.21%46.7 multimodal----
SLAKE tokenized F154.8176.6071.55%70.3 multimodal----
Table 4B. Final biomedical and vision comparison. Local Pestle, Qwen FP16, Bonsai, and Qwen IQ2_XXS medical rows use matched greedy, thinking-disabled decoding (temperature 0, seed 20260805). Row-level completion records are published with the evaluation evidence. Vision evaluations use original images. cMedGemma's CheXpert report uses 668 examples; Pestle uses the public 234-image expert-validation set.
Matched medical deltas and one published anchor
Observed percentage-point differences. Solid rows are local matched comparisons; the hollow row is published context.
-5 points0+5 points MedQA vs Qwen · matched-4.08 BioASQ F1 vs Bonsai-0.18 PharmaRAG MRR vs Qwen-3.76 MedQA vs MedGemma · published-0.01
Solid rows show local matched comparisons. The hollow MedGemma row is a published reference under its source protocol.

4.4  General benchmark comparison

The medical specialization does not eliminate broad capability. The general matrix is shown directly after the medical record, using the final values on the release card. These rows provide operating context; different sources and protocols are not blended into the medical retention statistic.

BenchmarkPestleQwen FP16Bonsai ternaryQwen Q4_K_XLQwen IQ2_XXSGemma4-31B
Knowledge and reasoning
MMLU-Redux83.5393.5088.0593.3588.9393.60
MuSR70.5072.8865.8773.0166.9971.03
Math
GSM8K93.2595.3096.0696.6689.9097.57
Coding
HumanEval+87.2095.1293.9095.7391.4696.34
MBPP+83.3383.3381.2283.8678.8984.39
Instruction following
IFEval prompt-strict81.7088.9185.0388.8384.0390.57
Table 5. Final general comparison matrix from the model card. Qwen's MMLU-Redux value is the official Qwen figure; remaining Qwen, Gemma, and Bonsai values reproduce Prism ML's reported evaluations. Pestle uses its disclosed greedy, thinking-disabled evaluation records.
General capability context
Pestle versus the FP16 parent where an aligned headline value is available; score differences are shown in native percentage points.
Figure 8. General capability context against the FP16 parent. Medical retention is reported separately because it is the release's primary specialization.

4.5  Benchmark evidence landscape

The matched medical-text benchmarks used in the V6 retention analysis appear above the general context. Paired rows connect Pestle to Qwen FP16 on a common score scale; rows without a matched parent show a single Pestle marker.

Figure 9. V6 benchmark landscape. Solid connections denote locally paired medical-text comparisons; dashed connections in the general section denote values drawn from the final comparison matrix and may cross protocols. MMLU enters the matched statistic at subject level.

4.6  Compression as institutional infrastructure

Pestle is the public proof point for a broader product: Doses AI can compress specialist models owned or commissioned by hospitals, pharmaceutical companies, regional providers, and clinical software teams. The customer keeps the model already adapted to its terminology, policies, evidence base, or therapeutic area; compression and acceptance testing turn it into a smaller, locally deployable asset.

Private model compression and acceptance path
A customer-specific conversion is defined by a frozen source checkpoint, an acceptance set, explicit thresholds, and a versioned release record.
StagePrimary inputRecorded outputAcceptance condition
1 · SpecifySource checkpoint and intended tasksImmutable source hash; scope statementOwnership, licence, and intended use confirmed
2 · CompressCheckpoint and calibration casesCandidate ternary artifactConversion completes inside the approved environment
3 · EvaluateFrozen task and safety suiteRow-level results and deltasPredefined capability and safety thresholds met
4 · PackageAccepted weights and runtimeVersioned artifact, hashes, runbookReproduction and rollback checks pass
5 · OperateApproved local deploymentMonitoring and review recordUse remains within the validated scope
Figure 10. Institutional conversion and acceptance protocol. The source checkpoint, calibration cases, evaluation evidence, and resulting artifact can remain within a customer-controlled environment. Pestle-27B-Ternary is the measured reference implementation; each customer model requires its own acceptance criteria.

Who gains access when the serving envelope shrinks

Hospitals and health systems
Compress internal clinical-language models, specialty assistants, coding systems, or retrieval-grounded tools already adapted to local policies. Deploy beside governed EHR, imaging, and formulary data.
Pharma and life sciences
Compress proprietary medical-information, safety, regulatory, literature, and therapeutic-area models without exporting model IP or private evidence to a per-token inference service.
Community pharmacy and family practice
Run assistive formulary search, guideline retrieval, patient-letter drafting, coding support, and local document QA on workstation-class hardware, with professional review and without making cloud inference structural.
Regional clinics, laboratories, and specialist groups
Build narrow systems around locally governed corpora and acceptance sets even when datacenter accelerators, dedicated ML teams, or stable cloud connectivity are unavailable.

Economic interpretation

The measured proof is an 8.2× smaller deployed text-weight payload - 55.56 GB to 6.75 GB - with a 96.48% measure-level median across the 17-measure matched evaluation record. The complete runnable GGUF is 8.48 GB. Realized serving savings depend on sequence length, batching, cache, and hardware. The product proposition is the repeatable combination of compression, retention calibration, matched evaluation, deployment packaging, and governance evidence.

5Clinical vision, from the benchmark record

For visual QA, images pass through the parent's vision encoder into the compressed language core; the ternary representation applies to the text decoder. On the original 451-row VQA-RAD test split Pestle reaches 53.49 token-F1 / 67.73 closed-question accuracy - above MedGemma 27B's published 46.7 / 67.1, noting MedGemma's figures use a different (balanced, image-disjoint) split - while on SLAKE it trails (54.81 vs 70.3). Every example below is reproduced verbatim from the retained evaluation record: an exact- or near-exact-match row, shown with its original benchmark image and row ID. They illustrate the behavior behind the scores; they are benchmark examples, not clinical validation.

Q · What is the location of the cavitary lesion?
"Right upper lobe" ✓ gold: right upper lobe
vqa_rad:test:71 · chest radiograph · exact match
Q · The condition in which a patient has enlarged ventricles, as seen in this image?
"Hydrocephalus" ✓ gold: hydrocephalus
vqa_rad:test:152 · axial brain MR · exact match
Q · What diseases are included in the picture?
"Pneumonia" ✓ gold: pneumonia
slake:test:116 · chest radiograph · exact match
Q · What diseases are included in the picture?
"Pneumothorax" ✓ gold: pneumothorax
slake:test:136 · chest radiograph · exact match
Q · What major artery of the brain may be affected by the lesion seen in the above image?
"Basilar artery" ✓ gold: basilar artery
vqa_rad:test:136 · localization → vascular territory
Q · Where is the pulmonary nodule located in this image?
"Left lower lobe" gold: lower left lung · F1 0.67
slake:test:439 · anatomically precise phrasing
These are benchmark items, not diagnoses. Images are drawn from the public VQA-RAD and SLAKE test sets (MedPix-sourced, de-identified). Selection shows correctly answered rows; the full record - including the ≈46% of open-ended rows the model does not answer exactly - ships with the release, and the aggregate scores in Table 3 are the honest summary of this capability.

6In use - prompt to answer, verbatim

Every input and output on this spread is reproduced unedited from the retained benchmark record - the same runs behind Table 3.

Clinical reasoning support · MedQA

A USMLE vignette, end to end

Input - medqa:test:61 (abridged vignette; full prompt in release record)
"A 22-year-old female college student is treated with metronidazole for vaginitis. At a party shortly afterward she experiences facial flushing, nausea, tachycardia, dyspnea, headache, and abdominal cramps after consuming alcohol. Serum levels of which of the following are likely elevated?  A. Acetaldehyde · B. Uric acid · C. Cytochrome P-450 enzymes · D. Amylase"
PESTLE · GREEDY · THINKING OFF · 8.48 GB
Output - unedited, graded correct
"The patient is experiencing a disulfiram-like reaction, a well-known adverse effect of metronidazole when combined with alcohol. Metronidazole inhibits the enzyme aldehyde dehydrogenase, which is responsible for converting acetaldehyde into acetate in the metabolic pathway of alcohol breakdown. When this enzyme is inhibited, acetaldehyde accumulates in the blood. The buildup of acetaldehyde causes the symptoms described, including facial flushing, nausea, tachycardia, headache, and abdominal cramps. Therefore, serum levels of acetaldehyde are likely elevated. ANSWER: A"
mechanism identified → enzyme named → symptom chain explained → correct answer · 1 of 1,143 correct MedQA rows
Evidence extraction · BioASQ

Reading the literature, not guessing

Review article · supplied in-context, verbatim · BioASQ evidence set
Safety and tolerability of injectable lipid-lowering drugs: a review of available clinical data
"INTRODUCTION: To answer the need of a better low-density lipoprotein (LDL) cholesterol control in statin-treated patients at high risk for cardiovascular disease, new injectable lipid-lowering drugs with innovative mechanisms of action are in advanced phase of development or have just been approved. AREAS COVERED: Evolocumab and alirocumab are fully human monoclonal antibodies inhibiting the proprotein convertase subtilisin/kexin type 9 (PCSK9) that binds to hepatic LDL receptor and prevents it from… …messenger RNA, blocking the translation of the gene product. Phase II (for evolocumab and alirocumab) and III (for evolocumab) trials show that PCSK9 inhibitors are equally well tolerated, with adverse events mainly limited to mild-to-moderate nasopharyngitis, injection-site pain, arthralgia and back pain. Mipomersen use is mainly associated to hepatosteatosis, increased transaminases (> 3 times the upper limit of normal), mild-to-moderate injection-site reactions and flu-like symptoms. EXPERT OPINION: PCSK9 inhibitors have demonstrated their good safety and tolerability in a large number of subjects with different clinical conditions, including statin-intolerance, enlarging their potential use in a broader range of patients. Further data on long-term mipomersen safety are required."
Question · Which enzyme is targeted by evolocumab? - answer format constrained to a single line
GROUNDED SPAN EXTRACTION
Output - exact match
"PCSK9"
proprotein convertase subtilisin/kexin type 9
The context names four competing therapies; the question asks for a target the text states only in passing. The model returns the enzyme, exactly.
bioasq · 75.28 token-F1 across 4,950 open-ended questions · validated run

7Mortar and systems evidence

mortar.cpp executes the released Pestle-27B-Ternary model directly in one decode loop. The engine is evaluated as part of the release, rather than treated as an implementation footnote.

Measured inference behavior and deterministic agreement
Single-stream rates and aggregate throughput are separated; memory bars show resident weights only, not peak runtime VRAM.
Figure 11. Systems evidence from retained local and accelerator records. Single-stream measurements: approximately 10 tok/s on an 18 GB M3 MacBook Pro, 30.38 tok/s on a 512-token H100 diagnostic, and approximately 39 tok/s median on an A100-class 256-token parity suite. The A100 MedQA run reached approximately 916 aggregate tok/s at concurrency 32; aggregate and single-stream rates are not interchangeable. The deployed text weights are 8.2× smaller - 55.56 GB to 6.75 GB - while the complete runnable GGUF is 8.48 GB. Cache, recurrent state, allocator, and runtime overhead are excluded from the weight bars.

7.1  What parity means here

Same-checkpoint dense materialization vs packed Mortar path
Greedy token-sequence agreement; first divergence follows the matched prefix.
153 tokens
Metal vs CUDA
Identical deterministic output sequence using the release engine.
180 tokens

This is not a claim of full-logit parity and not a comparison to the Qwen parent. The 153-token check compares Mortar with a dense materialization of the same Pestle checkpoint - the same compressed factors represented densely for validation. The Metal/CUDA check verifies cross-backend token identity under one deterministic prompt. Both checks are useful engineering evidence, but neither substitutes for the benchmark suite.

Operational reading. Pestle carries 6.75 GB of deployed text weights inside an 8.48 GB runnable GGUF package. Peak device memory remains workload-dependent because context length, concurrency, KV cache, recurrent state, and server allocation change the runtime envelope. This report therefore separates weight payload, package size, and workload-dependent runtime memory.

8Local deployment patterns

The smaller model changes who can build around a 27B-class medical system. An accelerator room is no longer the only viable serving environment: a hospital can keep inference beside governed data, while a community pharmacy, family practice, regional laboratory, or specialty clinic can place assistive retrieval and drafting on workstation-class hardware.

Deployment settings and governance boundary
The model API, retrieval sources, prompts, and outputs remain under site control; an external inference service is not required.
SettingRepresentative hardwareLocal resourcesRequired controls
Workstation18 GB unified-memory systemModel runtime; approved documents or formularyUser authentication, local logs, professional review
Clinical serverSingle acceleratorInternal model API; retrieval index; audit storeNetwork isolation, access control, monitoring, rollback
Private clusterHospital, pharma, or health-system infrastructureGoverned model service; approved clinical or research dataInstitutional validation, security review, change control
Figure 12. Representative local deployment settings for Pestle-27B-Ternary or an institution-owned model compressed through the same workflow. Retrieval stores and clinical systems remain governed independently of the model; external APIs may be integrated where approved, but are not structural to inference.

8.1  Deployment responsibilities

Health-system deployment. Validate prospectively on representative local workflows; isolate the service; pin model and engine checksums; control access to PHI; test subgroups and foreseeable harms; monitor drift, latency, refusals, loops, and human override; retain rollback artifacts.

Small-provider deployment. Keep the scope assistive and narrow: formulary and guideline retrieval, document QA, draft letters, coding support, or staff-facing summaries. Use approved local corpora, keep a professional in the review path, and avoid autonomous diagnosis, prescribing, treatment, or triage.

9Responsible use

Pestle is a research model, not a medical device. It must not directly determine diagnosis, treatment, prescribing, triage, or any other clinical decision. Outputs can be inaccurate, incomplete, biased, repetitive, or confidently wrong; every output is preliminary and requires qualified professional review. Benchmark performance does not establish clinical safety, efficacy, or population-level generalization.

Before any healthcare deployment, developers are responsible for task-specific adaptation and prospective validation; privacy, security, and data-governance review; subgroup and foreseeable-harm evaluation; human-oversight design; monitoring; and compliance with applicable medical-device, health-information, and AI regulation. Do not submit identifiable patient information to an environment not approved to process it.

10Limitations

Looping and long-form generation
The release-stage stability repair reduced literal repetitive loops in held-out replay but did not eliminate them. A minority of generations can still repeat or continue without converging; production serving should enforce an exact-loop guard, output ceiling, visible truncation state, and task-specific long-horizon acceptance tests.
Specialization boundary
Retention is strongest on medical knowledge, biomedical evidence, retrieval, and compact reasoning. General long-horizon, multimodal, and expert stress tasks require separate validation rather than inference from the headline medical results.
Medical vision
The compressed language core can consume the parent vision encoder, but image-conditioned results are uneven and require modality-specific validation.
Clinical reliability and transfer
Benchmark performance does not establish clinical safety, calibrated confidence, or population-level generalization. Every deployment - and every customer model compressed through the workflow - requires its own prospective acceptance, monitoring, and governance process.

11Conclusion

Pestle-27B-Ternary demonstrates a valuable operating point: an 8.2× smaller deployed text-weight payload - 55.56 GB to 6.75 GB - with a 96.48% measure-level median across the complete 17-measure matched evaluation record. The model is packaged as one 8.48 GB runnable GGUF. Pestle is both an open model and a proof of process. The same compression, matched evaluation, and deployment packaging can be applied to institution-owned medical and pharmaceutical models, with customer-specific acceptance criteria and without making external inference a structural requirement. The released weights, engine, and evidence establish the measured operating point; the repeatable compression and validation workflow is the product.

References

[1] Doses AI. Pestle-27B-Ternary model card and evaluation evidence. Commit 1bcd51a8d74a7e4ff1384192f82ea2d358f9ce24, 2026.

[2] Doses AI. mortar.cpp: architecture-aware low-bit inference. github.com/DosesAI/mortar.cpp, 2026.

[3] Sellergren et al. MedGemma Technical Report. arXiv:2507.05201, 2025.

[4] Google Research. Next-generation medical image interpretation with MedGemma 1.5. research.google/blog, 2026.

[5] Prism ML. Bonsai 27B: full 27B-class reasoning in binary and ternary transformer weights. Whitepaper, July 2026.

[6] Ma et al. The Era of 1-bit LLMs: All Large Language Models are in 1.58 Bits. arXiv:2402.17764, 2024.

[7] Qwen Team. Qwen3.6-27B model card. Hugging Face, 2026.

[8] Jin et al. What Disease Does This Patient Have? MedQA. Applied Sciences, 2021; GBaker/MedQA-USMLE-4-options.

[9] Lau et al. VQA-RAD: a dataset of clinically generated visual questions about radiology images. Scientific Data, 2018.

[10] Liu et al. SLAKE: a semantically-labeled knowledge-enhanced dataset for medical VQA. ISBI, 2021.

[11] Liu et al. EvalPlus: rigorous evaluation of LLM-synthesized code. NeurIPS, 2023.

[12] Zhou et al. IFEval: instruction-following evaluation for LLMs. arXiv:2311.07911, 2023.

[13] Zuo et al. MedXpertQA: benchmarking expert-level medical reasoning. arXiv, 2025.

[14] Tsatsaronis et al. BioASQ. BMC Bioinformatics, 2015.   [15] Gao et al. lm-evaluation-harness v0.4.12. EleutherAI, 2026.

[16] U.S. FDA, Health Canada, MHRA. Good Machine Learning Practice for Medical Device Development. Guiding principles.

Doses AI · doses.ai · malik@doses.ai