Sanctification/docs/card-layer-pipeline.md

Card Layer Pipeline

This is the production and validation contract for the layered card system in Art Direction. Existing proof scripts supply subject-specific composition/export references. The shared finish module implements the approved raw-ridges-v1 recipe for future stained-glass assembly; optional authored-region experiments remain separate. Use the Sanctification card-production skill as the execution entry point.

Timothy provides a Common composition/export reference; Burning Bush provides a Rare proof. Read each proof’s build and validation report for implemented scope and pending visual decisions. The draft Common coordinates below do not override a selected proof’s versioned layout. Trinity/Foundation artwork, wear/condition, and imperfections are deferred.

Card Work Organization

Follow Card work and approval: production lives in in-progress/cards/[ID-title]/revisions/[revision]/, with shared source/review records and low, med, high exports separated by printing. Explicitly approved revisions move to artifacts/cards/[ID-title]/. The progress index records stage and selection; spikes/ is for experiments. Legacy spike paths are compatibility links, not destinations for new card work.

Geometry Owns Alignment

Use one versioned layout definition to produce the composition guides, frame/backing paths, transparency masks, text regions, and validation regions. Do not maintain separate hand-entered coordinates for each tool.

Generation supplies artwork and decorative surfaces. It does not decide final transparent boundaries, panel placement, lettering, or alignment. A guide image in a generation prompt helps composition but does not guarantee coordinate compliance. Fit and review the generated source once, then clip it to the template's exact masks.

For a simple Common frame, vector shapes and a restrained fill may be sufficient without generating any frame imagery. For more ornate tiers, generate decoration with extra coverage beyond the target paths, fit or retouch it once, and preserve the approved result. Clipping alone cannot repair an ornament whose structure is in the wrong place.

Illustration Review Before Finish

Apply the Card Art Brief's illustration review before assembly or material-map work; the brief owns segmentation, fine-detail, palette, and within-segment light/color rules. Review the fitted artwork against the selected layout guide during prototyping. After artwork approval and assembly, inspect Normal's composition at master, standard, and thumbnail sizes and use Printed ink under neutral harness lighting when available.

If the illustration fails review, revise the art before deriving material regions. A color threshold, blur, or stronger coating cannot establish missing illustration structure. Record the agent's assessment separately from user approval. If visual inspection or WebGL is unavailable, report that review as pending.

Art Prototyping Loop

Before the user explicitly approves or locks the artwork, work only on the illustration and the records needed to assess it: native source, exact generation/edit prompt, fit transform, and review images. A temporary template guide can show the safe region but is not a production layer.

Do not assemble the card or generate derived production data on every art iteration. In particular, defer frame/backing rendering, deterministic typography, glyph-protection maps, finish maps, four-printing exports, runtime assets, and final validation. Keep previously approved reusable layers and prior exports available as comparison inputs. A specifically requested intermediate composition or material preview is allowed, but must be labeled provisional.

Once the user explicitly approves the artwork, freeze its source revision and run the full assembly once. Rebuild all derived outputs affected by that selected source so the composition, masks, and runtime data share one transform. An art edit after approval returns to this loop unless the user directs an immediate final rebuild.

Shared Canvas and Draft Coordinates

All production layers and masks use 2000 × 2800 pixels, origin at the top left, x increasing rightward and y downward. Preserve full-canvas transparent margins and place every exported layer at (0, 0). Use the renderer's established UV convention at the runtime boundary; do not independently mirror maps.

Generated source images may have other dimensions. Retain the original, record an explicit crop/scale transform into the production canvas, and visually review focal placement. Apply the same transform to any associated masks. Never stretch an illustration silently to fit.

The following coordinates are a draft Common layout for the first proof, not approved final proportions. Rectangles are x, y, width, height in master pixels. Outer rounded geometry should follow the harness's physical corner radius.

Region	Draft geometry	Purpose
Canvas	0, 0, 2000, 2800	Full-card illustration and common origin
Outer frame	60 px inset band	Simple continuous frame; transparent interior
Title backing	48, 48, 1904, 312	Extends 12 px underneath the frame at the top and sides
Lower backing	48, 2180, 1904, 572	Extends 12 px underneath the frame at the sides and bottom
Title text	160, 105, 1680, 105	One-line title box; horizontal center at x = 1000
Category	1400, 240, 440, 64	Quiet, right-aligned subject type
Focal safe region	160, 430, 1680, 1680	Essential subjects remain clear of Normal overlays
Excerpt / fact	160, 2250, 1680, 280	Short typeset supporting content
Reference	160, 2580, 1680, 80	Short attribution

The backing's frame overlap is internal compositing allowance, not physical print bleed. For this draft, 12 master pixels becomes 3 pixels at 500 × 700. Review actual filter behavior before choosing a final overlap.

A two-line title needs a separately defined and reviewed layout with room for its subtitle/category; it is not permission to spill into the illustration. Each Legendary template needs the same explicit regions and checks even if its shapes differ.

Seam-Free Border Assembly

1. Derive the outer frame and backing masks from shared vector paths.
2. Put a continuous, opaque base fill beneath decoration wherever the template requires solid coverage. Texture alpha must not accidentally punch through these regions.
3. For joined templates, extend backing joins underneath the frame. Floating templates instead preserve their explicitly defined artwork reveal. Do not rely on two separately antialiased edges meeting at exactly one pixel boundary.
4. Place the frame over the backing, with one defined compositing order and color profile.
5. Export Normal's combined overlay, Textless's frame-only overlay, and Borderless's backing-only overlay. Boundless needs none.
6. Compose the final face at master resolution, then derive runtime sizes from that composition. Retain separate editable source layers.

Borderless backing must have clean standalone edges; it cannot depend on the absent outer frame to hide unfinished decoration. A joining surface also needs visual continuity in color and texture: an alpha check catches a gap, but cannot approve its appearance.

Keep a consistent alpha convention throughout export and resizing. Inspect light and dark backgrounds to catch edge fringes. A single composed front texture is sufficient for the standard runtime card; separate almost-coplanar 3D meshes are unnecessary for these authoring layers.

Shared Frame and Backing Assets

For Common through Extraordinary, resolve reusable components from artifacts/layers, independent of the builder's working directory. Legendary variants may instead retain their own versioned frame/backing geometry and sources in the card revision, following Legendary foreground composition. Pin the tier and version in card data, load layout.json and verify the version manifest through library.load_tier. Record the version manifest SHA-256 and active asset paths/hashes in validation. Reference these assets directly; do not create card-local copies or regenerate them during assembly. Historical proof builders preserve their original templates; the four-tier comparison builder demonstrates direct shared references.

Normal uses overlay-normal plus lettering; Textless uses frame-textless (which may differ from Normal's frame); Borderless uses backing-borderless plus lettering; Boundless uses neither. Compile finish occlusion from those actual components, and derive text protection from the newly rendered lettering. Template changes require rebuilding all affected derived faces/maps in a new proof, even when the illustration is unchanged.

Validate required opaque panels/perimeters and intended clear regions separately. Joined Common/Uncommon candidates overlap their backings under the frame. Floating Rare/Extraordinary candidates explicitly preserve an artwork reveal; this is excluded from opaque join requirements. Validate corners and coverage at master/1000/500 sizes. Measure local backing-rule contrast after resizing rather than judging the nominal ink color alone. Current v2 candidates remain pending user visual approval; pin an explicitly selected version rather than silently changing existing cards when library defaults change.

Legendary Foreground Composition

Follow Legendary bespoke composition. Keep the complete base illustration separate from an optional adapted foreground element. Retain each foreground's authored silhouette/alpha and editable source; for generated or edited donors, also retain the exact prompt, native output, recorded fit/placement, and hashes. The foreground may intentionally differ from the art behind the backing. Record that difference instead of requiring source-RGB identity for the adapted region.

Place all fitted components on the same 2000 × 2800 canvas with explicit transforms. The usual order is base illustration → selected frame/backing overlay → illustrated foreground → deterministic lettering. Record any template-specific change in order. Use the same source, transform, alpha convention, and resampling for the face and associated finish data.

Choose a silhouette that preserves the complete intended form, internal leading, and a convincing visible connection to the source scene. Review color-assisted selections and traced contours for holes, clipped seams, detached folds, fringes, and artificial straight edges. A contour can be geometrically valid while the overlap still looks pasted on. Redesign the foreground or backing where needed, and inspect the final composed join at enlarged, standard, and thumbnail sizes.

Validate actual unclipped glyph bounds and require no foreground/lettering intersection. For a backed layout, verify glyphs remain on the intended legible backing field after its shapes are adjusted. Record visual assessment separately from numerical connectivity or source-preservation checks. During prototyping, make only specifically requested provisional previews; final printings and masks follow approval of the selected illustration and adapted foreground.

Select components explicitly per printing. A backing-specific adaptation appears in Normal and Borderless. Textless uses the full illustration plus its selected outer frame; Boundless uses the full illustration alone. Omit the backing-specific foreground from those two printings to avoid duplicating or changing the underlying subject unexpectedly. Record a revised full-bleed artwork variant if an adaptation is intended for all printings.

Shared Font Assets

Use the repository's shared font directory, sanctification/fonts/, for every card assembly and typography preview. Select each production face from Art Direction’s typography role table; the shared manifest pins the corresponding font and license hashes. Keep licenses beside these shared files. Do not create a card-local /fonts folder, copy font/license files from a previous proof, or select a system-installed substitute.

Resolve the repository and font directory from the build script's location, independent of the current working directory and proof nesting depth. Point any proof-local Fontconfig configuration at the shared directory; output-local font caches are allowed. Use the same configuration for matching, glyph measurements, rendering, and review labels. Fail on a missing file, hash mismatch, fallback, or missing glyphs. Record each used font's shared path, filename, and SHA-256 in validation inputs. A new font/weight must be added and pinned centrally as an explicit typography revision.

Archived rejected proofs may retain compatibility symlinks to this shared directory so their historical preservation manifests still resolve. New proofs reference the shared files directly. Existing historical reports remain records of their original builds.

Deterministic Text

Supply name, optional subtitle, subject type, excerpt, and attribution as structured content. Use real text objects with pinned font files, size, weight, line spacing, alignment, and language settings. Fix the rendering tool/version for reproducible exports.

For a centered title, the selected template supplies the horizontal center anchor. A full-width panel commonly uses x = 1000; a bespoke Legendary plaque may define another anchor. The text engine measures and places the text around that anchor. Baselines and line spacing govern vertical placement. Record any approved optical adjustment rather than asking generation to center text.

Every template needs approved minimum font sizes and maximum line counts, established at actual application display sizes. Word count is an editorial guide, not a fit check. Long names and wide glyphs can overflow even with few words.

Validate the unclipped rendered glyph bounds against each text region and its padding. Checking only the text object's box can miss clipping. Reject missing fonts, missing glyphs, overflow, or insufficient line capacity; do not silently substitute fonts, crop the text, or shrink it below the minimum. Use a reviewed alternate layout or revise the content.

Text is rendered anew when card content changes, but its coordinates do not change randomly. Once approved, the frame/backing decoration is reused.

For backings with central flourishes, apply Art Direction's approved spacing rule. Derive the reference line box from the pinned font tables: round hhea.ascender × fontSize / unitsPerEm upward for ascent, and round max(-hhea.descender, -head.yMin) × fontSize / unitsPerEm upward for descent. Do not add hhea line gap. Record these metrics, font hash, reference baseline, fixed line-box bounds and actual glyph bounds separately.

Validate flourish-to-inner-rule spacing with visual bounds including strokes, and reference line-box-to-lower-flourish spacing at 20 master pixels. Independently render unclipped reference glyphs to verify line-box containment and actual clearance. Exercise NKJV, ESV, KJV and a reference containing lowercase descenders, such as Philippians, without changing the baseline-to-flourish relationship. Center the union of verse ink bounds between the upper flourish and fixed reference line-box top; permit at most one master pixel of raster rounding imbalance and check collisions separately. Validate scaled 1000/500px exports with up to one output pixel of raster rounding allowance, recording any visibility threshold used for raster measurements. Include a clean comparison and guides showing baselines, line boxes, actual ink and flourish boundaries for visual review.

Finish Coverage

Use raw-ridges-v1 for new stained-glass card assembly through the shared production module. The user approved the raw-ridge Normal comparisons for The Fall and Burning Bush on September 13, 2026; the approval record pins their reference hashes. Existing cards and fixtures retain their own recipes; no migration is requested. The harness defaults record this decision without changing runtime material coefficients.

Approved Raw Ridge Recipe

Analyze the fitted opaque 2000×2800 artwork once with prepare_illustration, then compile each printing using its actual overlay/lettering alpha. An adapted illustrated foreground also needs analysis of its selected artwork; resolve its visible coverage as described in illustrated overlaps in finish coverage. Reuse each distinct analysis across the printings that use it. The module regenerates raw confidence from artwork; production does not consume a diagnostic PNG from a spike. See CLI and builder integration and the immutable numeric recipe.

• Blur RGB by 1.2 master pixels, convert to Pillow luminance, and test eight orientations with opposing shoulder distances of 4, 8, 14 and 22 master pixels.
• Raw confidence is the maximum smoothstep(0.018, 0.07, min(shoulders) − luminance) × (1 − smoothstep(0.10, 0.25, luminance)) across orientations/distances.
• Quantize that confidence to 8 bits before composition, reproducing the approved raw PNG precision. Apply no continuity filtering, bridging, thresholding, opening, dilation or confidence snapping.
• Pane weighting is 0.62 + 0.28 × smoothstep(0.08, 0.58, softenedSaturation). Softened saturation uses an 8-bit field blurred by 20 master pixels. Neutral glass retains coating rather than being cut out by saturation/value multiplication.
• Compile paneWeight × (1 − rawConfidence) × (1 − activeProtection), where activeProtection = 1 − (1 − overlayAlpha) × (1 − textAlpha). Alpha comes from the actual visible components, with absent components contributing zero.
• Export opaque grayscale RGBA at 2000, 1000 and 500px widths with bilinear downsampling, preserving full-canvas registration. White finish receives coating; white ridge confidence protects ink.

Record recipe ID/hash, source art revision/fit transform, component hashes and tool versions in production validation. New art and other printings still require their own static/moving-light review. Raw ridges may retain etched flecks and painted outlines; changes to cleanup or weights are a new reviewed revision. Legacy saturation/value recipes remain historical references and alternatives when specifically selected; authored-region trials below are optional experiments, not part of v1.

Illustrated Overlaps in Finish Coverage

An illustrated foreground is a coating-bearing art component, not a protected frame or text backing. Its alpha may occlude a backing visually, but must not be merged into the backing's protection alpha. Generate finish coverage from the selected adapted foreground artwork, including its actual pane colors and lead-like divisions, rather than sampling the unchanged base art or copying the base mask into the overlap.

For an edited donor, prepare an opaque full-canvas illustration analysis plate containing the fitted adapted art over the base illustration, without lettering, backings, or frame. Retain its derivation and hashes; do not analyze a crop stretched over the card or transparent pixels flattened onto white. Use the unchanged raw-ridges-v1 recipe for each selected illustration analysis. This adds component analysis and visibility composition; it does not permit changing the ridge detector or repairing its confidence map.

Resolve finish coverage from front to back with the same transforms and alpha used for the face. At a fully opaque foreground pixel, use that foreground's pane/ridge coverage in place of the hidden backing or base coverage. At an antialiased or partially transparent foreground edge, combine foreground and the visible underlying coverage using that same alpha. Apply active lettering/glyph protection above the result. Protect the portion of a backing that remains visible; do not suppress the cloth merely because its coordinates lie inside a backing rectangle.

Normal and Borderless therefore include the adapted overlap's finish response. Textless and Boundless use their selected full-bleed illustration coverage when the backing-specific foreground is absent. Regenerate affected maps when the foreground art, silhouette, fit, or printing selection changes. Check the join and revised hem in composed-card and finish-map comparisons at delivery sizes; retain a moving-light review status separately.

This is the required production contract for overlapping templates. Existing builders that assume all overlays suppress finish need a bespoke component-composition path before they can export these masks; the current David overlap previews have not implemented or validated production finish coverage.

Editable Material Regions

When testing region authoring after fitting the illustration, keep pane coverage and lead protection on the same full canvas. Store editable paths or layered masks with the source art revision and transform. Paths may be traced manually or assisted by extraction/generation, but inspect and correct registration before using them. Independent generated maps are not guaranteed to align.

• Pane coverage: white selects coating, black excludes it, and gray controls partial coverage. Choose broad, intentional regions with restrained variation within panes. Not every pane must receive the same coating weight.
• Lead protection: white excludes coating from lead-like divisions; black leaves coverage available. Protect coherent seams without treating every dark painted mark as lead.
• Preserve fine subject details through selective coverage. Review the bush/flame region explicitly rather than accepting near-uniform coverage caused by its saturation.
• Give frame ornament its own explicit coverage if desired. Existing protected-frame proofs may retain zero frame coverage; gold-colored illustration or ornament does not automatically imply metallic coating.

Pane/lead assets are authoring inputs, not additional required runtime texture samples. Compile them into the existing scalar finish map. Keep roughness/normal maps optional for a demonstrated material need; they are not prerequisites for a stained-glass-inspired printed card.

Compile Per Printing

Keep material coverage, transparency, and text protection distinct. The shared raw-ridge recipe and optional authored-region experiments both compile illustration coverage as paneCoverage * (1 - leadProtection), clamped to [0, 1]. Record any within-pane modulation and do not reintroduce pixel-scale painted noise through an unrestricted saturation multiplier.

For each printing:

• Resolve intended coverage through the visible components using their actual transforms, alpha, occlusion, and layer order. Hidden illustration coverage must not leak onto visible backings or frames.
• Protect active text backings and derive any glyph protection from actual rendered lettering. Removing a backing removes its associated protection; removing lettering removes its glyph protection.
• Textless and Boundless recover illustration coverage in former text regions while retaining illustration ridge/lead protection.
• Export aligned opaque grayscale scalar maps. White receives finish, black suppresses it; this is the opposite white convention from a protection map. Treat runtime maps as data, not artwork color.
• Downsample without ringing and inspect seam registration at 1000 and 500 pixels. A feathered edge may soften a transition but must not erase a lead boundary.

Visual Finish Review

Produce artwork, compiled finish mask, and composed-card review views, plus any tested pane/lead inputs. Compare Printed ink, Foil, and Holographic under multiple lighting angles and rotation using the same camera/light configuration. Check that pane divisions remain clear, painted grain does not become mottled coating boundaries, lettering stays readable, and the focal subject retains its identity. A grayscale mask alone cannot demonstrate the result.

Record structural checks, static visual assessment, moving-light review, and user approval separately. If WebGL review is unavailable, deliver the proof with that limitation. Reject region maps that introduce arbitrary cutoffs, overprotect dark texture, or lose subject coherence; return to the baseline rather than treating structural validation as visual success. The Burning Bush pane/lead attempt was rejected for these problems and is retained only as a comparison input. Any justified shader change is a separate material decision documented in CURRENT-DEFAULTS.md.

Optional Text Protection Assets

Text-bearing printings may export an additional first-class data map named [image-name]-text-mask.png beside [image-name].png and the required [image-name]-mask.png finish map in the harness's public/card-art folder. It is optional: existing cards without it retain their current material behavior. A supplied text mask must match artwork dimensions and be opaque grayscale. White protects lettering; black retains substrate and finish response. Gray values provide a smooth transition around glyphs. The map is independent of finish coverage and silhouette alpha, and uses the same full canvas, origin, transform, and UV convention as the finished card.

Derive it from the actual rendered text layer, not an estimate based on artwork color or re-entered text boxes. A small expanded/feathered margin can suppress relief near glyph edges; record its size at master resolution and resize the data map without ringing. Preserve glyph coverage. Normal and Borderless retain their lettering protection; Textless and Boundless omit the asset or export black maps. Do not retain protection from absent lettering.

The current harness discovers and validates optional maps, includes their bytes in catalog revisions, and loads them with artwork/finish data in Inspect/Lab and selected pack cards. A supplied map that is unreadable, misregistered, or fails loading is an explicit error. Missing maps incur no request and use the original shader path. When present, one extra data texture sample reduces substrate relief, Metal parallax/etch treatment, normal perturbation, glare/tint, and finish coverage near text. White text areas retain plain diffuse ink lighting. No postprocess, additional geometry, or font/anti-aliasing change is required.

The independent Calling the Disciples P052 proof implements this export from pinned P052 Roman glyphs and records canonical Matthew 4:19 • NKJV formatting, mask coverage, unchanged card pixels, and provenance. Moving-light readability still needs review.

Proposed Automated Validation

Validation should run after fitting a generated source and after every final card assembly. A future build command should fail with a readable report and produce a diagnostic image showing the failed regions.

Check	Evidence
Canvas and registration	All production layers/maps have the expected dimensions, origin, template revision, and recorded transforms
Required coverage	Combined overlay alpha has no gaps within the template's required opaque regions, including joins
Transparent windows	Pixels in required clear regions are transparent; intentional antialiased edge bands are checked separately
Typography	Required content exists, font/glyphs resolve, unclipped glyph bounds fit, line limits and minimum sizes pass
Printing composition	Normal, Textless, Borderless, and Boundless include exactly the prescribed components
Optional material regions	When used, pane/lead inputs match the source art revision and transform; coverage stays within intended panes and authored lead protection is retained
Finish alignment	Coverage uses the same geometry/transforms and the correct printing's text protection
Legendary illustrated overlaps	Complete visible form and join reviewed; no lettering intersections; selected adapted art supplies foreground finish through the same alpha/order, including over protected backing coordinates
Optional text masks	Matching opaque grayscale data, registered rendered glyph coverage, absent-printing fallback, and catalog revision/loading checks
Downsampled edges	Approved runtime sizes have no exposed join pixels or unintended alpha fringes
Repeatability	Same content, assets, template, fonts, and pinned renderer reproduce the same decoded pixels

Check overlay alpha independently of the final opaque illustration: a gap can reveal artwork while the finished card's alpha still looks completely opaque.

Use adversarial fixtures when implementing the validator: a displaced backing, a one-pixel seam, a missing font, an overlong title, and an obsolete text-protection region should fail. This verifies that the checks detect defects rather than merely accepting the sample card.

Automated checks cannot guarantee narrative focus, artistic quality, optical balance, or perceived text readability under moving light. Produce review sheets at master, standard, and thumbnail sizes, plus harness views. A diagnostic outline of text and focal regions is useful for review but is never exported on the finished card.

Tooling Proposal

The existing proofs use SVG/Inkscape, ImageMagick, and proof-specific Node/Python scripts. Reuse that stack for exact geometry, typography, composition, and export. Editable pane/lead regions may use SVG paths or layered raster masks. GIMP is optional when layered editing offers a concrete benefit.

• Inkscape/SVG: author exact paths, render a fixed page, and query object bounds for layout checks. See the official command-line guide. Validate unclipped glyph bounds as well as object boxes.
• ImageMagick: optional alpha compositing and pixel inspection for exported images. See its alpha-compositing documentation. It provides primitives, not a ready-made card validator.
• MCP: an optional interface to invoke the same deterministic assembly and validation operations. A connector alone does not guarantee alignment, and freeform visual placement by an agent should not replace the shared layout definition.

No GIMP MCP is connected in this session. Select and verify a specific adapter's compatibility with the installed GIMP version before depending on it. A CLI pipeline can implement the same workflow without that adapter.

Proof Sequence

1. Render the template with plain fills and a typography stress set. Establish acceptable proportions, font sizes, and overlap.
2. Prototype the illustration using the compact art brief and selected layout guide. Fit/review it and obtain explicit artwork approval before proceeding to assembly.
3. Add restrained Common frame decoration only if plain vector treatment is insufficient.
4. Assemble all four printings with the shared raw-ridges-v1 recipe for new stained-glass art, resolving each printing’s actual visible components. Keep any explicitly requested alternative as a separate comparison.
5. Run structural checks and review seams and text at target sizes.
6. Review with the approved harness finish response and compare against the existing reference fixture.
7. Freeze the approved template/assets and reuse them for subsequent Commons.

Keep the current harness reference fixtures available for comparison. This proof should establish new production assets without silently replacing the approved material baseline.

Printing-specific outer frames

Textless remains illustration plus outer frame, with no backing or lettering. Its outer-frame geometry may have a versioned printing-specific template when Normal inset linework would box in the artwork. The Burning Bush Rare revision demonstrates a reusable Rare/Textless template with a narrow opaque perimeter, restrained corner rules, and a transparent continuous interior. Normal keeps its approved frame. Finish protection must follow the actual active Textless frame alpha; opacity and open-interior validation must follow the selected template. This reusable proof template awaits broader tier-wide visual approval and does not alter other proofs. See Burning Bush revision.

Normal Rare open frame and backing detail

The Burning Bush revision demonstrates a reusable Normal Rare template with a narrow opaque perimeter, restrained corner/side rules and lozenges, and no inset art-window box or broad scene rails. Safe title/footer backing regions remain opaque and typography coordinates stay fixed. The continuous artwork between them gains area without moving the illustration. Rare distinction comes from restrained linework and subtle cream vellum/fiber/crossgrain detail, paired hairlines and small edge ornaments; retain base#f4ead4 and lettering#263f50. Measure contrast beneath actual rendered glyphs and validate both open scene interior and opaque perimeter/backing joins. Finish masks follow the selected frame/backing alpha. Keep the successful separate open Textless template. These proof templates await broader adoption approval; previous revisions remain comparison inputs and unrelated proofs are unchanged. See current Burning Bush proof.