# Operating-handoff marketing extension

Version 0.26.0+20261122T183400Z

A Forest Zen practice card, coordinated social sequence and editable operating register. The five prompts are Observed outcomes, Accepted ownership, Open commitments, Usable response routes, and Handoff confirmation. An accepted handoff can include open commitments with accepted owners and review points. Ending extra launch observation does not end required monitoring, incident response or continuing controls. These are original practitioner coordination prompts, not a PCI SSC-prescribed handoff template or evidence of compliance. Exactly one PDF is included.

## Print

handoff-practice-card.pdf is one flat 5 x 7 inch trim page. Media/BleedBox is 5.25 x 7.25 inches; TrimBox is inset 0.125 inch. Important text is at least 0.25 inch inside trim. Print at actual size. Ask the local printer to confirm stock, RGB conversion, finishing and a physical proof. Scan the physical proof before a batch; this template is not printer certified.

## Editable operating register

handoff-operating-register.csv is UTF-8 with LF line endings, fourteen columns and three wholly invented examples. It connects observed outcomes and supporting references to continuing owners, backup cover, acceptance, access checks, runbooks, open exceptions, actions, review points, escalation conditions, source context and handoff confirmation. Keep identifier and reference columns as text when importing into a spreadsheet. No executable formulas are included.

Use one continuing commitment or operating decision per row. A technical finding can be understood while an associated action remains open; keep that distinction visible. Record actual acceptance by the receiving owner, not an assumption based on a name in a document. Confirm that access, backup cover and response guidance are usable through the approved process. Ask the receiving owner to walk one signal, explain the next decision and locate the response route. If that confirmation is pending, leave it pending. Acceptance in the example rows is fictional practice, not an approval of any real handoff.

Choose review points and escalation conditions for the actual service and applicable procedures. No example interval replaces a required PCI DSS frequency or an incident-response obligation. Do not enter PAN, SAD, credentials or customer records. Keep operational identifiers, internal contacts, evidence and confidential details out of public sharing. Use approved internal locations for the actual working register. The example source date is a placeholder, not a mandatory evidence interval.

## Social

Portrait canvases are 1200 x 1500 pixels; landscape is 1200 x 627. These are design choices, not current platform-specification claims. Use portrait panels in order. Editable captions, alt text and T+0/2/5 calendar-day suggestions from actual social-sequence publication are included. They are editorial suggestions, not control intervals. Review exact copy and destination before sharing. Nothing is scheduled or posted.

All QR codes and readable URLs lead to:
https://thrivepci.com/training/free/program-maintenance/

Finished PDF and both QR-bearing social PNGs decode to that URL. handoff-qr-validation.json records payloads, rendered hashes, PDF boxes, safe text bounds and four embedded fonts. Preserve four white quiet-zone modules without overlays or feathering. Digital decoding does not replace a physical proof.

## Edit and rebuild

Editable SVGs embed ASCII Poppins subsets; the canonical About-reference Arial wordmark is outlined without distributing an Arial font. handoff-Poppins-OFL.txt accompanies the subset. Preserve Forest, Sage, River, Sand and paper, readable contrast, quiet bamboo and organic waves. Keep QR geometry intact.

Rebuild with tools/build_marketing_handoff.py; render tools/render_marketing_handoff.mjs; render the PDF to temporary handoff-card.png; run tools/finalize_marketing_handoff.py proof; render with --contact; finalize with tools/finalize_marketing_handoff.py package. Use bundled Python/Node runtime and fontTools. Earlier kit files remain unchanged. The ZIP contains only this extension and an internal hash manifest.
