@incodetech/prizma-core-screens 0.1.0

package/dist/QualifiedSignatureLayout.css

@@ -0,0 +1,206 @@
+/* Qualified Signature — module layout additions.
+ *
+ * ONLY what the foundation archetypes and Prizma Core do not already own.
+ * NOTHING here re-declares an archetype spacing rule: the content column, the
+ * 24px gutters, the title → fields Spacing/32 (`FormScreen.css`), the title →
+ * list Spacing/24 (`__list`), the review header → stage Spacing/32 and stage →
+ * CTA Spacing/24 (`__review-*`), the CTA-band recipe (`__band`, DEVIATIONS #8)
+ * and the anchored footer (#F-29) all stay the foundation's.
+ *
+ * Every rule below is one of exactly three kinds:
+ *   (a) CONTENT rhythm inside a slot the archetype hands over — the same
+ *       licence §6-G gives a Core card list ("the list keeps its own row
+ *       rhythm; the archetype supplies only the offset above it");
+ *   (b) a RELEASE of a Core/foundation constraint a purple section contradicts
+ *       — the idiom Phone Input's `width: auto` (#PI-1) and CURP's scrolling
+ *       field stack (#CURP-1) established;
+ *   (c) media CONTENT Core has no primitive for, rebuilt from Core's own
+ *       tokens, with the Core request recorded.
+ */
+
+/* ── (b) The consent stack is taller than the screen ─────────────────────────
+ * `QSign.AcceptSign.default` is a 1156-tall frame (the `selectedCheckox` one is
+ * 1160): five consent containers at ~120 each plus the document row push CONTENT
+ * far past the 654 a 390×844 reference gives it. Figma lets the page grow and
+ * the browser scroll; screens are authored at 390×844 and never reflow
+ * (DEVIATIONS #17), and archetype E's `.prizma-form-screen__fields` is
+ * `flex: 1; min-height: 0` with NO overflow behaviour — so the surplus is
+ * clipped by `ScreenShell`'s `overflow: hidden` and first paints over the CTA.
+ *
+ * The stack therefore scrolls INSIDE the column: the title, the CTA, the link
+ * and the anchored tag hold still while the clauses pan. It adds no padding, no
+ * gap and no size of its own. Identical to CURP's `.curp-generate--scroll`
+ * (DEVIATIONS #CURP-1) — this is the SECOND module to need it.
+ *
+ * FOUNDATION REQUEST (restated, now with two consumers): promote this to
+ * `FormScreen.css` as a `.prizma-form-screen__fields--scroll` variant driven by
+ * a `scrollFields` prop on `PrizmaFormScreen`. Every long-form module left in
+ * Wave 3 — eKYC, eKYB, address entry — hits the same wall.
+ */
+/* CLOSED: the scroll is now the archetype's `scrollFields` prop
+ * (`.prizma-form-screen__fields--scroll` in FormScreen.css), which also gives
+ * every row `flex-shrink: 0`. Keeping the rule here re-declared layout in a
+ * module file AND missed that fix, which collapsed the document row to 18px and
+ * clipped its View button (owner-reported 2026-08-19). DEVIATIONS #QS-1. */
+
+/* ── (a) Consent-clause rhythm ───────────────────────────────────────────────
+ * Figma stacks the `Checkbox` (size L / Container) instances at Spacing/4
+ * inside the accept screen's `bottom container`. Core ships the clause card
+ * itself (`PrizmaCheckbox size="L"` — tinted surface, 28px box, inline links)
+ * but no group wrapper, so the row rhythm is supplied here, exactly as a
+ * `PrizmaCardList` supplies its own. One token, no padding, no size.
+ *
+ * CORE REQUEST: a consent-group primitive (`PrizmaCheckboxGroup`) would own
+ * this gap and the group's `role="group"` naming.
+ */
+.qualified-signature-terms {
+  display: flex;
+  flex-direction: column;
+  gap: var(--prizma-spacing-4);
+}
+
+/* ── (c) Uploaded-file preview card ──────────────────────────────────────────
+ * `QSign.reviewDoc.default`'s `Document Container` — a VERTICAL card holding a
+ * page thumbnail over the filename. Core's `PrizmaCardDocumentContainer` shares
+ * the Figma name but is the HORIZONTAL filename + action row (used on the accept
+ * screen, where it IS the right component). Rebuilt here from the same Card
+ * tokens: Surface/Neutral/50 on Border/Neutral/100 at Border/Radius/large,
+ * Spacing/32 block + Spacing/24 inline padding, Spacing/24 thumbnail → name.
+ *
+ * CORE REQUEST (third module to need it — Document Capture's `confirmUpload`
+ * has a byte-equivalent copy, DEVIATIONS #DC-27): promote a
+ * `PrizmaCardFilePreview`. Two identical hand-builds were already one too many;
+ * three is the #DC-29 threshold that got the glyph slot promoted.
+ */
+.qualified-signature-file-card {
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+  gap: var(--prizma-spacing-24);
+  box-sizing: border-box;
+  width: 100%;
+  padding: var(--prizma-spacing-32) var(--prizma-spacing-24);
+  background: var(--prizma-surface-neutral-50);
+  border: var(--prizma-border-width-regular) solid var(--prizma-border-neutral-100);
+  border-radius: var(--prizma-border-radius-large);
+  overflow: hidden;
+}
+
+/* Thumbnail — Figma draws `Artboard 1` at 113.25 × 150, a 3:4 page crop. Sized
+ * by ratio so it scales with the host and capped at the design width. */
+.qualified-signature-file-card__thumb {
+  position: relative;
+  flex: none;
+  width: 113px; /* hardcoded — Figma page-thumbnail width; absent from the token SOT (same class as DEVIATIONS #DC-27) */
+  aspect-ratio: 3 / 4;
+  max-width: 100%;
+  border: var(--prizma-border-width-regular) solid var(--prizma-border-neutral-100);
+  border-radius: var(--prizma-border-radius-small);
+  overflow: hidden;
+  background: var(--prizma-surface-neutral-0);
+}
+
+.qualified-signature-file-card__thumb > img,
+.qualified-signature-file-card__thumb > svg {
+  position: absolute;
+  inset: 0;
+  width: 100%;
+  height: 100%;
+  object-fit: cover;
+}
+
+.qualified-signature-file-card__name {
+  margin: 0;
+  width: 100%;
+  overflow-wrap: break-word;
+  text-align: center;
+  color: var(--prizma-text-body-800-primary);
+  font-family: var(--prizma-headline-family);
+  font-size: var(--prizma-headline-h5-font-size);
+  font-weight: var(--prizma-headline-h5-font-weight);
+  line-height: var(--prizma-headline-h5-line-height);
+  letter-spacing: var(--prizma-headline-h5-letter-spacing);
+}
+
+/* The card is inset inside the media stage — Figma centres the 246-wide
+ * container in the 342 column (48 each side). The spacing scale stops at 40, so
+ * the value is DERIVED from Spacing/24 rather than hardcoded. */
+.qualified-signature-review-file {
+  padding-inline: calc(var(--prizma-spacing-24) * 2);
+}
+
+/* ── (c) Standalone encrypted notice ─────────────────────────────────────────
+ * "All data is encrypted" sits beside the file card, not under a capture frame.
+ * Core owns that building block ONLY as a private part of `PrizmaIdCapture`, so
+ * it is rebuilt from the identical tokens (Spacing/8 block padding, Spacing/4
+ * gap, Body/M Regular, Text/Body/800). One literal: the 16px lock clamp —
+ * `IconLock` is designed at 24 only and the icon-size axis has no 16, the same
+ * clamp Core itself writes in `IdCapture.css`.
+ *
+ * CORE REQUEST (third consumer, DEVIATIONS #DC-26): extract
+ * `PrizmaEncryptedNotice`.
+ */
+.qualified-signature-encrypted {
+  margin: 0;
+  flex-shrink: 0;
+  display: flex;
+  align-items: center;
+  justify-content: center;
+  gap: var(--prizma-spacing-4);
+  padding-block: var(--prizma-spacing-8);
+  color: var(--prizma-text-body-800-primary);
+  font-family: var(--prizma-body-family);
+  font-size: var(--prizma-body-m-regular-font-size);
+  font-weight: var(--prizma-body-m-regular-font-weight);
+  line-height: var(--prizma-body-m-regular-line-height);
+  letter-spacing: var(--prizma-body-m-regular-letter-spacing);
+}
+
+.qualified-signature-encrypted > svg {
+  flex: none;
+  width: 16px; /* hardcoded — Icon/Lock is designed at 24 only and Figma draws 16; same clamp as Core's .prizma-id-capture__encrypted-icon (DEVIATIONS #DC-26) */
+  height: 16px;
+}
+
+/* ── (b) The document body scrolls inside the middle ─────────────────────────
+ * `QSign.AcceptSign.viewdoc` hands the middle a 592-tall contract page and
+ * `QSign.T&C` a 13575-tall block of legal text WITH ITS OWN SCROLL INDICATOR —
+ * Figma is explicit that this surface scrolls. Archetype G's `__list` middle
+ * flexes but does not scroll, so the body would be clipped by the shell.
+ *
+ * This releases that one constraint. It declares no padding, no gap and no size:
+ * the Spacing/24 above it is still the archetype's, the gutters are still the
+ * content column's, and the tag stays anchored. `overscroll-behavior` keeps a
+ * flick inside the document instead of panning the host page.
+ */
+.qualified-signature-document {
+  flex: 1 1 auto;
+  min-height: 0;
+  width: 100%;
+  overflow-y: auto;
+  overscroll-behavior: contain;
+}
+
+/* The contract page is host-supplied media (an <img> / <canvas> of the rendered
+ * PDF, GUIDELINES §10's `cameraSurface` idiom) — it fills the column width and
+ * keeps its own aspect. */
+.qualified-signature-document > img,
+.qualified-signature-document > svg {
+  display: block;
+  width: 100%;
+  height: auto;
+}
+
+/* Legal body copy inside the `terms` variant. Core has no long-form prose
+ * component (Body tokens exist, the block does not), so the paragraph binds the
+ * Body/M Regular scale directly — no new size, no new colour. */
+.qualified-signature-document__prose {
+  margin: 0;
+  color: var(--prizma-text-body-800-primary);
+  font-family: var(--prizma-body-family);
+  font-size: var(--prizma-body-m-regular-font-size);
+  font-weight: var(--prizma-body-m-regular-font-weight);
+  line-height: var(--prizma-body-m-regular-line-height);
+  letter-spacing: var(--prizma-body-m-regular-letter-spacing);
+  text-align: left;
+}

package/dist/QualifiedSignatureProcessingScreen.d.ts

@@ -0,0 +1,46 @@
+import React from 'react';
+import { type PrizmaProcessingScreenProps } from './ProcessingScreen';
+import type { PrizmaScreenActionHandler, PrizmaScreenOverrides } from './types';
+import type { QualifiedSignatureProcessingVariant, QualifiedSignatureStrings } from './QualifiedSignatureStrings';
+import './ScreenLayout.css';
+export interface QualifiedSignatureProcessingScreenProps extends Omit<PrizmaProcessingScreenProps, 'status' | 'title' | 'subtitle' | 'verifiedLabel' | 'navLabel'> {
+    /** Module copy — this screen reads the `processing` slice its `variant` names. */
+    strings: QualifiedSignatureStrings;
+    /** Which reading of the in-flight frame to render. Default `processing`. */
+    variant?: QualifiedSignatureProcessingVariant;
+    screenId?: string;
+    overrides?: PrizmaScreenOverrides;
+    onAction?: PrizmaScreenActionHandler;
+}
+/**
+ * Qualified Signature — the in-flight screens.
+ *
+ * The two purple parents do NOT draw the same wait, so this is two frames, not
+ * one:
+ *
+ * - `processing` — `QSign.AcceptSign.processing` (10196:67395). The pure
+ *   spinner + H2 case with nothing else on the frame, which is exactly what
+ *   GUIDELINES §6-C reserves for the Processing archetype: the spinner block is
+ *   centred in the middle container, so the archetype's fully-centred column is
+ *   the right template.
+ * - `signing`    — the partner's own 6086:39544. "Creating your signature…"
+ *   under the spinner PLUS a second attribution row, "Signing as …", anchored
+ *   at the BOTTOM of the frame immediately above the verified tag — NOT under
+ *   the title, where a `subtitle` would land it.
+ *
+ * WHY `signing` MOVES TO ARCHETYPE F. Archetype C has no slot between its
+ * centred column and the footer tag, so there is no way to place a
+ * bottom-anchored row without declaring spacing locally — forbidden by §6.
+ * Archetype F is "C with a CTA band", and its `disclaimer` slot is precisely
+ * that row: Core's own `PrizmaDisclaimer`, centred secondary text, sitting in
+ * the band directly above the tag. With no CTA label the band carries only that
+ * row, so the frame keeps C's silhouette and gains the anchored line. The
+ * archetype gap (C has no footer/disclaimer slot) is reported, not patched
+ * here — this screen still declares no layout of its own.
+ *
+ * Both are distinct from the accept screen's `loading` state, which keeps the
+ * signer on the form with the spinner in the CTA — these are the flow's own
+ * waits.
+ */
+export declare const QualifiedSignatureProcessingScreen: React.ForwardRefExoticComponent<QualifiedSignatureProcessingScreenProps & React.RefAttributes<HTMLDivElement>>;
+export default QualifiedSignatureProcessingScreen;

package/dist/QualifiedSignatureProcessingScreen.js

@@ -0,0 +1,48 @@
+'use client';
+import { jsx as _jsx } from "react/jsx-runtime";
+import { forwardRef } from 'react';
+import { PrizmaProcessingScreen, } from './ProcessingScreen';
+import { PrizmaResultScreen } from './ResultScreen';
+import './ScreenLayout.css';
+/**
+ * Qualified Signature — the in-flight screens.
+ *
+ * The two purple parents do NOT draw the same wait, so this is two frames, not
+ * one:
+ *
+ * - `processing` — `QSign.AcceptSign.processing` (10196:67395). The pure
+ *   spinner + H2 case with nothing else on the frame, which is exactly what
+ *   GUIDELINES §6-C reserves for the Processing archetype: the spinner block is
+ *   centred in the middle container, so the archetype's fully-centred column is
+ *   the right template.
+ * - `signing`    — the partner's own 6086:39544. "Creating your signature…"
+ *   under the spinner PLUS a second attribution row, "Signing as …", anchored
+ *   at the BOTTOM of the frame immediately above the verified tag — NOT under
+ *   the title, where a `subtitle` would land it.
+ *
+ * WHY `signing` MOVES TO ARCHETYPE F. Archetype C has no slot between its
+ * centred column and the footer tag, so there is no way to place a
+ * bottom-anchored row without declaring spacing locally — forbidden by §6.
+ * Archetype F is "C with a CTA band", and its `disclaimer` slot is precisely
+ * that row: Core's own `PrizmaDisclaimer`, centred secondary text, sitting in
+ * the band directly above the tag. With no CTA label the band carries only that
+ * row, so the frame keeps C's silhouette and gains the anchored line. The
+ * archetype gap (C has no footer/disclaimer slot) is reported, not patched
+ * here — this screen still declares no layout of its own.
+ *
+ * Both are distinct from the accept screen's `loading` state, which keeps the
+ * signer on the form with the spinner in the CTA — these are the flow's own
+ * waits.
+ */
+export const QualifiedSignatureProcessingScreen = forwardRef(({ strings, variant = 'processing', screenId = `qualified-signature-processing-${variant}`, overrides, onAction, ...shell }, ref) => {
+    if (variant === 'signing') {
+        const copy = strings.processing.signing;
+        return (_jsx(PrizmaResultScreen, { ref: ref, status: "loading", title: copy.title, subtitle: copy.subtitle, 
+            /* The bottom-anchored "Signing as …" row. */
+            disclaimer: copy.signingAsLabel, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell }));
+    }
+    const copy = strings.processing.processing;
+    return (_jsx(PrizmaProcessingScreen, { ref: ref, status: "loading", title: copy.title, subtitle: copy.subtitle, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell }));
+});
+QualifiedSignatureProcessingScreen.displayName = 'QualifiedSignatureProcessingScreen';
+export default QualifiedSignatureProcessingScreen;

package/dist/QualifiedSignatureResultScreen.d.ts

@@ -0,0 +1,65 @@
+import React from 'react';
+import { type PrizmaResultScreenProps } from './ResultScreen';
+import type { PrizmaScreenActionHandler, PrizmaScreenOverrides } from './types';
+import type { QualifiedSignatureResultVariant, QualifiedSignatureStrings } from './QualifiedSignatureStrings';
+import './ScreenLayout.css';
+export interface QualifiedSignatureResultScreenProps extends Omit<PrizmaResultScreenProps, 'status' | 'title' | 'subtitle' | 'glyph' | 'bandContent' | 'disclaimer' | 'ctaLabel' | 'secondaryCtaLabel' | 'verifiedLabel' | 'navLabel'> {
+    /** Module copy — this screen reads the `result` slice its `variant` names. */
+    strings: QualifiedSignatureStrings;
+    /** Which verdict section to render. Default `signed`. */
+    variant?: QualifiedSignatureResultVariant;
+    screenId?: string;
+    overrides?: PrizmaScreenOverrides;
+    onAction?: PrizmaScreenActionHandler;
+}
+/**
+ * Qualified Signature — the five verdicts, built on the Result archetype
+ * (GUIDELINES.md §6-F, `PrizmaResultScreen`).
+ *
+ * ONE screen for five purple frames that share the archetype's skeleton —
+ * nav → centred status mark + title block → CTA band → anchored tag — and differ
+ * in status, copy and which actions exist:
+ * - `signed`        — `QSign.success` (10196:67485): the positive mark over a
+ *   `Button group` 124 tall = the "Continue" primary plus the "Download PDF"
+ *   underlined link.
+ * - `signedPlain`   — `QSign.success` (10196:67494): the SAME mark and line
+ *   with no actions at all, so the band never renders and the screen reads as
+ *   the pure §6-C verdict.
+ * - `signedPartner` — the `x Namirial` parent's own success frame (6086:40135).
+ *   NOT a copy of either generic one: it adds the "Signed by …" attribution row
+ *   and a STACKED pair — "Done" primary above a "Download document" OUTLINED
+ *   secondary. Both ride the archetype's `ctaLabel` + `secondaryCtaLabel`, which
+ *   already fix primary-above-secondary (#GEO-1); the attribution row rides
+ *   `disclaimer`, the band's own centred text row above the buttons.
+ * - `error`         — `QSign.AcceptSign.error` (10196:67436 / 6089:37399): the
+ *   warning mark and "Something went wrong". This frame really does draw no
+ *   button.
+ * - `errorRetry`    — the SECOND error frame both parents draw (10196:67445 and
+ *   the partner's 8363:21429): the same warning mark over "Signature failed"
+ *   plus a full-width "Try again" primary. It is the flow's only recovery
+ *   affordance, so it is a state in its own right rather than an upstream
+ *   concern (QA finding, 2026-08-19).
+ *
+ * Core's outline status marks are used, not Figma's two-tone filled discs — the
+ * icon-outline sweep of 2026-07-28 settled that for every module (DEVIATIONS
+ * #15, #DC-34) and these frames are one sweep behind. Both error frames get the
+ * WARNING mark, not the negative one: Figma draws the amber "!" disc, and the
+ * signature attempt is recoverable rather than refused.
+ *
+ * The generic error frames drop the verified tag; the partner's keeps it.
+ * The owner rule settles the split in favour of keeping it (#PI-8, #F-30) so
+ * nothing shifts between states.
+ *
+ * ONE reported delta: on `signed`, Figma puts "Download PDF" BELOW the primary,
+ * at Core's `PrizmaButtonGroup` Spacing/12. Archetype F has no tertiary-link
+ * slot — its only band opening above the buttons is `bandContent` — so Core's
+ * own `tertiary-link` Button is composed there and lands ABOVE the primary at
+ * the band's Spacing/32 (16 + 16). Ink, semantics and the distinct `secondary`
+ * action are all correct (#PI-10); only the position moves. #GEO-1 fixes the
+ * tertiary link's position PER ARCHETYPE and F has never declared one — the
+ * archetype request is logged instead of a local override. `signedPartner` is
+ * unaffected: its download control is a real outlined secondary Button, which
+ * the archetype already places correctly.
+ */
+export declare const QualifiedSignatureResultScreen: React.ForwardRefExoticComponent<QualifiedSignatureResultScreenProps & React.RefAttributes<HTMLDivElement>>;
+export default QualifiedSignatureResultScreen;

package/dist/QualifiedSignatureResultScreen.js

@@ -0,0 +1,76 @@
+'use client';
+import { jsx as _jsx } from "react/jsx-runtime";
+import { forwardRef } from 'react';
+import { PrizmaButton } from '@incodetech/prizma-core-web/button';
+import { PrizmaResultScreen } from './ResultScreen';
+import './ScreenLayout.css';
+/**
+ * Qualified Signature — the five verdicts, built on the Result archetype
+ * (GUIDELINES.md §6-F, `PrizmaResultScreen`).
+ *
+ * ONE screen for five purple frames that share the archetype's skeleton —
+ * nav → centred status mark + title block → CTA band → anchored tag — and differ
+ * in status, copy and which actions exist:
+ * - `signed`        — `QSign.success` (10196:67485): the positive mark over a
+ *   `Button group` 124 tall = the "Continue" primary plus the "Download PDF"
+ *   underlined link.
+ * - `signedPlain`   — `QSign.success` (10196:67494): the SAME mark and line
+ *   with no actions at all, so the band never renders and the screen reads as
+ *   the pure §6-C verdict.
+ * - `signedPartner` — the `x Namirial` parent's own success frame (6086:40135).
+ *   NOT a copy of either generic one: it adds the "Signed by …" attribution row
+ *   and a STACKED pair — "Done" primary above a "Download document" OUTLINED
+ *   secondary. Both ride the archetype's `ctaLabel` + `secondaryCtaLabel`, which
+ *   already fix primary-above-secondary (#GEO-1); the attribution row rides
+ *   `disclaimer`, the band's own centred text row above the buttons.
+ * - `error`         — `QSign.AcceptSign.error` (10196:67436 / 6089:37399): the
+ *   warning mark and "Something went wrong". This frame really does draw no
+ *   button.
+ * - `errorRetry`    — the SECOND error frame both parents draw (10196:67445 and
+ *   the partner's 8363:21429): the same warning mark over "Signature failed"
+ *   plus a full-width "Try again" primary. It is the flow's only recovery
+ *   affordance, so it is a state in its own right rather than an upstream
+ *   concern (QA finding, 2026-08-19).
+ *
+ * Core's outline status marks are used, not Figma's two-tone filled discs — the
+ * icon-outline sweep of 2026-07-28 settled that for every module (DEVIATIONS
+ * #15, #DC-34) and these frames are one sweep behind. Both error frames get the
+ * WARNING mark, not the negative one: Figma draws the amber "!" disc, and the
+ * signature attempt is recoverable rather than refused.
+ *
+ * The generic error frames drop the verified tag; the partner's keeps it.
+ * The owner rule settles the split in favour of keeping it (#PI-8, #F-30) so
+ * nothing shifts between states.
+ *
+ * ONE reported delta: on `signed`, Figma puts "Download PDF" BELOW the primary,
+ * at Core's `PrizmaButtonGroup` Spacing/12. Archetype F has no tertiary-link
+ * slot — its only band opening above the buttons is `bandContent` — so Core's
+ * own `tertiary-link` Button is composed there and lands ABOVE the primary at
+ * the band's Spacing/32 (16 + 16). Ink, semantics and the distinct `secondary`
+ * action are all correct (#PI-10); only the position moves. #GEO-1 fixes the
+ * tertiary link's position PER ARCHETYPE and F has never declared one — the
+ * archetype request is logged instead of a local override. `signedPartner` is
+ * unaffected: its download control is a real outlined secondary Button, which
+ * the archetype already places correctly.
+ */
+export const QualifiedSignatureResultScreen = forwardRef(({ strings, variant = 'signed', screenId = `qualified-signature-result-${variant}`, overrides, onAction, ...shell }, ref) => {
+    // One slice per frame — nothing is shared between variants, so the frames
+    // can never collapse into each other visually.
+    const signedCopy = variant === 'signed' ? strings.result.signed : undefined;
+    const partnerCopy = variant === 'signedPartner' ? strings.result.signedPartner : undefined;
+    const retryCopy = variant === 'errorRetry' ? strings.result.errorRetry : undefined;
+    const copy = signedCopy ??
+        partnerCopy ??
+        retryCopy ??
+        (variant === 'error' ? strings.result.error : strings.result.signedPlain);
+    return (_jsx(PrizmaResultScreen, { ref: ref, status: variant === 'error' || variant === 'errorRetry' ? 'warning' : 'success', title: copy.title, subtitle: copy.subtitle, 
+        /* "Continue" · "Done" · "Try again" — the archetype's own primary. */
+        ctaLabel: signedCopy?.ctaLabel ?? partnerCopy?.ctaLabel ?? retryCopy?.ctaLabel, 
+        /* The partner's outlined "Download document", below the primary. */
+        secondaryCtaLabel: partnerCopy?.secondaryCtaLabel, 
+        /* The partner's "Signed by …" row — the band's centred text slot, which
+           puts it above the button pair exactly as Figma draws it. */
+        disclaimer: partnerCopy?.signedByLabel, bandContent: signedCopy?.downloadLabel ? (_jsx(PrizmaButton, { variant: "tertiary-link", size: "L", onClick: () => onAction?.({ type: 'secondary', screenId }), children: signedCopy.downloadLabel })) : undefined, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell }));
+});
+QualifiedSignatureResultScreen.displayName = 'QualifiedSignatureResultScreen';
+export default QualifiedSignatureResultScreen;

package/dist/QualifiedSignatureReviewScreen.d.ts

@@ -0,0 +1,49 @@
+import React, { type ReactNode } from 'react';
+import { type PrizmaReviewScreenProps } from './ReviewScreen';
+import type { PrizmaScreenActionHandler, PrizmaScreenOverrides } from './types';
+import type { QualifiedSignatureStrings } from './QualifiedSignatureStrings';
+import './ScreenLayout.css';
+import './QualifiedSignatureLayout.css';
+export interface QualifiedSignatureReviewScreenProps extends Omit<PrizmaReviewScreenProps, 'stage' | 'title' | 'subtitle' | 'successTitle' | 'analyzingLabel' | 'analyzingState' | 'primaryLabel' | 'secondaryLabel' | 'verifiedLabel' | 'children' | 'stageClassName'> {
+    /** Module copy — this screen reads the `review` slice. */
+    strings: QualifiedSignatureStrings;
+    /** The uploaded file's name. Not copy — runtime data from the picker. */
+    filename?: string;
+    /** Page-preview thumbnail (an `<img>`) rendered inside the card. */
+    thumbnail?: ReactNode;
+    screenId?: string;
+    overrides?: PrizmaScreenOverrides;
+    onAction?: PrizmaScreenActionHandler;
+}
+/**
+ * Qualified Signature — the uploaded document confirmed before signing, built on
+ * the Review archetype (GUIDELINES.md §6-H, `PrizmaReviewScreen`).
+ *
+ * Figma: purple section `QSign.reviewDoc.default` (10196:67138). It is archetype
+ * H and not F for exactly the reason §6-H draws the line: the header is
+ * TOP-aligned (`top container` starts at CONTENT y=24 with the Title, no logo
+ * row) over a media `Container` that fills the middle (109→450 of a 654 frame),
+ * with the actions anchored at the bottom — F would centre the title and the
+ * card together as one block. Measured against the archetype: Title → stage 32
+ * (Figma 109 − 77 = 32), stage → actions 24 (482 − 450 − 8 rounding). Every one
+ * of those offsets is the archetype's; this file declares none.
+ *
+ * TWO deltas from the frame, both reported rather than worked around:
+ * 1. Figma stacks `Continue` over `Replace` (a `Button group` 124 tall = 56 + 12
+ *    + 56). Archetype H hardcodes Core's `PrizmaButtonGroup
+ *    orientation="horizontal-v1"`, so they pair side by side. A screen never
+ *    picks its own button order (#GEO-1), and H has no orientation slot — the
+ *    archetype request is logged instead of overridden here.
+ * 2. The frame draws no verified tag. The owner rule wins over Figma for
+ *    attribution chrome — every non-capture screen keeps header and footer
+ *    (#PI-8, #F-30, #F-34) — so `showFooter` keeps its default.
+ *
+ * What stays module-side is the MEDIA, which Core has no primitive for: the
+ * vertical file-preview card (`PrizmaCardDocumentContainer` is the horizontal
+ * filename + action row this module uses on the accept screen instead) and the
+ * standalone encrypted notice (Core owns it only inside `PrizmaIdCapture`).
+ * Both are rebuilt from Core's own tokens in `QualifiedSignatureLayout.css`,
+ * with the Core requests recorded there — DEVIATIONS #DC-26, #DC-27.
+ */
+export declare const QualifiedSignatureReviewScreen: React.ForwardRefExoticComponent<QualifiedSignatureReviewScreenProps & React.RefAttributes<HTMLDivElement>>;
+export default QualifiedSignatureReviewScreen;

package/dist/QualifiedSignatureReviewScreen.js

@@ -0,0 +1,40 @@
+'use client';
+import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
+import { forwardRef } from 'react';
+import { IconLock } from '@incodetech/prizma-core-icons';
+import { PrizmaReviewScreen } from './ReviewScreen';
+import './ScreenLayout.css';
+import './QualifiedSignatureLayout.css';
+/**
+ * Qualified Signature — the uploaded document confirmed before signing, built on
+ * the Review archetype (GUIDELINES.md §6-H, `PrizmaReviewScreen`).
+ *
+ * Figma: purple section `QSign.reviewDoc.default` (10196:67138). It is archetype
+ * H and not F for exactly the reason §6-H draws the line: the header is
+ * TOP-aligned (`top container` starts at CONTENT y=24 with the Title, no logo
+ * row) over a media `Container` that fills the middle (109→450 of a 654 frame),
+ * with the actions anchored at the bottom — F would centre the title and the
+ * card together as one block. Measured against the archetype: Title → stage 32
+ * (Figma 109 − 77 = 32), stage → actions 24 (482 − 450 − 8 rounding). Every one
+ * of those offsets is the archetype's; this file declares none.
+ *
+ * TWO deltas from the frame, both reported rather than worked around:
+ * 1. Figma stacks `Continue` over `Replace` (a `Button group` 124 tall = 56 + 12
+ *    + 56). Archetype H hardcodes Core's `PrizmaButtonGroup
+ *    orientation="horizontal-v1"`, so they pair side by side. A screen never
+ *    picks its own button order (#GEO-1), and H has no orientation slot — the
+ *    archetype request is logged instead of overridden here.
+ * 2. The frame draws no verified tag. The owner rule wins over Figma for
+ *    attribution chrome — every non-capture screen keeps header and footer
+ *    (#PI-8, #F-30, #F-34) — so `showFooter` keeps its default.
+ *
+ * What stays module-side is the MEDIA, which Core has no primitive for: the
+ * vertical file-preview card (`PrizmaCardDocumentContainer` is the horizontal
+ * filename + action row this module uses on the accept screen instead) and the
+ * standalone encrypted notice (Core owns it only inside `PrizmaIdCapture`).
+ * Both are rebuilt from Core's own tokens in `QualifiedSignatureLayout.css`,
+ * with the Core requests recorded there — DEVIATIONS #DC-26, #DC-27.
+ */
+export const QualifiedSignatureReviewScreen = forwardRef(({ strings, filename, thumbnail, screenId = 'qualified-signature-review', overrides, onAction, ...shell }, ref) => (_jsxs(PrizmaReviewScreen, { ref: ref, stage: "review", title: strings.review.title, subtitle: strings.review.subtitle, stageClassName: "qualified-signature-review-file", primaryLabel: strings.review.ctaLabel, secondaryLabel: strings.review.replaceLabel, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell, children: [_jsxs("div", { className: "qualified-signature-file-card", children: [_jsx("span", { className: "qualified-signature-file-card__thumb", children: thumbnail }), filename ? (_jsx("p", { className: "qualified-signature-file-card__name", children: filename })) : null] }), strings.review.encryptedLabel ? (_jsxs("p", { className: "qualified-signature-encrypted", children: [_jsx(IconLock, { size: "m" }), _jsx("span", { children: strings.review.encryptedLabel })] })) : null] })));
+QualifiedSignatureReviewScreen.displayName = 'QualifiedSignatureReviewScreen';
+export default QualifiedSignatureReviewScreen;