EDITORIAL / A4
REPRODUCIBLE DOCUMENT ENGINE SHOWCASE
One pinned Fullbleed 2.3.1 runtime, tested across editorial design, transactional output, PDF profiles, accessibility, compiled VDP, parallel batches, and the official .NET binding.
Built August 17, 2026 · catalog SHA b8dbb77a90ca
01 / VISUAL RANGE
Every card below is a Fullbleed-rendered PDF with a retained source, preview, inspection record, and deterministic build path.
EDITORIAL / A4
TRANSACTIONAL / LETTER
DISPLAY / A3 FULL BLEED
ACCESSIBILITY / PDF-UA SEEDS

02 / OUTPUT CONTRACTS
The Output Lab renders one document through three profiles. The evidence records claims, output intents, embedded fonts, warnings, and seed blockers.
These are Fullbleed inspector and seed-gate results, not independent conformance certifications.
03 / COMPILED VOLUME
Measured on this Windows host. The rates describe these fixtures and this machine; they are not cross-library comparisons.
records / second
500 custom-font passes in 31.6 msrecords / second
100 records · 191 pagesrecords / second
5.74% fewer bytes in this runserial median speed
1,854 distinct records / second04 / OFFICIAL .NET BINDING
The showcase pins the official fullbleed-dotnet repository as a submodule at 2c179f6, builds its dependency-free net8.0 project, and runs the typed FullBleedCliClient against Fullbleed 2.3.1.
Binding 0.1.0 · commit 2c179f6 · artifact a8c3595fbdb5

05 / REGRESSION CLOSED
Two silent 2.3.0 failures were replayed unchanged under 2.3.1: corrupted synthetic-weight previews and unbound custom-font fixed VDP slots.
The generated PDF hash is identical across versions. Fullbleed's finalized-PDF PNG changed from corrupt 700/800 painting to readable text, localizing the observed fix to the preview/raster path.


2.3.0 discovered the Lato slots but left their literal placeholders. 2.3.1 binds all five values; extracted text contains every expected value and no {{ token.


06 / PROOF, NOT PROMISES
The build keeps its own receipts: inspections, profile signals, timing, hashes, deterministic reruns, capability snapshots, and runnable regression fixtures.
Complete machine-readable result and system context.
JSON ↗ OUTPUT CONTRACTSClaims, intents, embedded fonts, and blockers.
JSON ↗ SEMANTICSVerifier, structure, reading order, and PMR evidence.
JSON ↗ REGRESSIONAutomated placeholder, slot, hash, and control assertions.
JSON ↗ LANGUAGE BINDINGCommit, runtime, schema, render, inspect, and rerun checks.
JSON ↗ PUBLICATIONPublished artifact paths, sizes, and SHA-256 values.
JSON ↗START WITH THE BENCHMARK BOOK