A verification frame structures a consequential decision into three stacked parts: Recognize (what this is and what state the application reports), Verify (the facts, evidence, freshness and unresolved work to check deliberately) and Act (the actions the application or Ordo currently allows). The frame makes the pause for verification visible and puts facts before buttons in both source and visual order. It is presentation only: it never decides that an action is legal, that evidence is sufficient or that a state is certain. Everything inside comes from application or Ordo state.
Use when
A user is about to take an action that is hard to reverse or has consequences for others, such as approving a payment, releasing a build or closing a case.
Specific values must be read deliberately before acting, such as an amount, an account number or a target environment.
The application can supply the facts, their freshness and the currently legal actions.
Avoid when
The action is routine and easily undone: use a plain Button with an Alert or Toast outcome.
The user is only confirming a single sentence: use a Dialog.
The content to check is a rendered document: use Preview surface, optionally inside the Verify part.
Behavior to know
Three padded parts separated by rules: recognize (header), verify (facts grid) and act (footer).
Facts are a dl in an auto-fit grid of columns at least 12rem wide, each fact separated by a thin rule.
Designed to pair with .forma-identifier and .forma-critical-value for low-context values.
At 30rem and below the act area is a one-column grid of full-width, wrapping buttons.
Basic example
The smallest correct markup: the canonical pattern from patterns/verification-frame.html inside its public tag. Copy this first, then adapt labels, names and state.
Canonical
Minimal verification frame
Rendered from the canonical pattern file.
Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.
Recognition
Ready for deliberate verification
The application reports one consequential transition is available. Verify the evidence below before acting.
Verify
Record
INV-1042
Amount
$10,001.00
Evidence
3 sources reviewed
Freshness
Checked 2 minutes ago
Unresolved work: none reported for this transition.
<forma-verification-frame class="forma-component-tag">
<section class="forma-verification-frame" aria-labelledby="verification-title">
<header class="forma-verification-frame__recognize">
<span class="forma-component-kicker">Recognition</span>
<h2 id="verification-title">Ready for deliberate verification</h2>
<p>The application reports one consequential transition is available. Verify the evidence below before acting.</p>
</header>
<section class="forma-verification-frame__verify" aria-labelledby="verify-heading">
<h3 id="verify-heading">Verify</h3>
<dl class="forma-verification-frame__facts">
<div><dt>Record</dt><dd><span class="forma-identifier">INV-1042</span></dd></div>
<div><dt>Amount</dt><dd><span class="forma-critical-value" data-forma-verify="true">$10,001.00</span></dd></div>
<div><dt>Evidence</dt><dd>3 sources reviewed</dd></div>
<div><dt>Freshness</dt><dd>Checked 2 minutes ago</dd></div>
</dl>
<p><strong>Unresolved work:</strong> none reported for this transition.</p>
</section>
<footer class="forma-verification-frame__act">
<p>Actions shown here must come from current application or Ordo capabilities.</p>
<button type="button">Review sources</button>
<button type="button">Approve transition</button>
</footer>
</section>
</forma-verification-frame>
Click or tap the code once to select all of it, then copy.
Examples
Scenario
Production release with stale evidence
The application reports that one piece of evidence is stale. The frame shows it as stale, not as failed or passed, and the act area offers refreshing the evidence first. The target environment and commit are low-context values marked for deliberate reading.
Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.
Recognition
Release 4.2.0 to production
Evidence stale Verify the facts below before releasing.
Verify
Environment
prod-eu-west-1
Commit
9f3c1a7e0b
Integration tests
Passed · 148 of 148
Security scan
Last run 26 hours ago (stale)
Unresolved work: the security scan is older than the 24-hour release policy.
<forma-verification-frame class="forma-component-tag">
<section class="forma-verification-frame" aria-labelledby="verification-frame-production-release-title">
<header class="forma-verification-frame__recognize">
<span class="forma-component-kicker">Recognition</span>
<h2 id="verification-frame-production-release-title">Release 4.2.0 to production</h2>
<p><span class="forma-status-lozenge" data-state="unknown">Evidence stale</span> Verify the facts below before releasing.</p>
</header>
<section class="forma-verification-frame__verify" aria-labelledby="verification-frame-production-release-verify">
<h3 id="verification-frame-production-release-verify">Verify</h3>
<dl class="forma-verification-frame__facts">
<div><dt>Environment</dt><dd><span class="forma-critical-value" data-forma-verify="true">prod-eu-west-1</span></dd></div>
<div><dt>Commit</dt><dd><span class="forma-identifier">9f3c1a7e0b</span></dd></div>
<div><dt>Integration tests</dt><dd>Passed · 148 of 148</dd></div>
<div><dt>Security scan</dt><dd>Last run 26 hours ago (stale)</dd></div>
</dl>
<p><strong>Unresolved work:</strong> the security scan is older than the 24-hour release policy.</p>
</section>
<footer class="forma-verification-frame__act">
<p>Release is available after a current security scan.</p>
<button type="button">Run security scan</button>
</footer>
</section>
</forma-verification-frame>
Click or tap the code once to select all of it, then copy.
Scenario
Payment approval with long identifiers
Content stress: a long IBAN and a long payee name wrap inside their fact cells. The critical amount carries the deliberate-verification cue, and both a review action and the approval come from the application's current capabilities.
Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.
Recognition
Approve outgoing payment
The payee's bank details changed 3 days ago. Check them against the supplier record before approving.
Verify
Payee
Hanseatische Maschinenbau- und Anlagentechnik GmbH
<forma-verification-frame class="forma-component-tag">
<section class="forma-verification-frame" aria-labelledby="verification-frame-payment-approval-title">
<header class="forma-verification-frame__recognize">
<span class="forma-component-kicker">Recognition</span>
<h2 id="verification-frame-payment-approval-title">Approve outgoing payment</h2>
<p>The payee's bank details changed 3 days ago. Check them against the supplier record before approving.</p>
</header>
<section class="forma-verification-frame__verify" aria-labelledby="verification-frame-payment-approval-verify">
<h3 id="verification-frame-payment-approval-verify">Verify</h3>
<dl class="forma-verification-frame__facts">
<div><dt>Payee</dt><dd>Hanseatische Maschinenbau- und Anlagentechnik GmbH</dd></div>
<div><dt>IBAN</dt><dd><span class="forma-identifier">DE89370400440532013000</span></dd></div>
<div><dt>Amount</dt><dd><span class="forma-critical-value" data-forma-verify="true">€148,200.00</span></dd></div>
<div><dt>Bank details changed</dt><dd><time datetime="2026-09-27">27 September 2026</time> by M. Chen</dd></div>
</dl>
</section>
<footer class="forma-verification-frame__act">
<p>You are the second approver for this payment.</p>
<button type="button">Open supplier record</button>
<button type="button">Approve payment</button>
</footer>
</section>
</forma-verification-frame>
Click or tap the code once to select all of it, then copy.
Mobile
Each mobile example renders in its own document inside a real narrow viewport, so Forma's media and container queries run exactly as they would on a phone. Choose a width to compare.
Mobile example
Mobile case closure
At phone width facts stack in one column and the actions become full-width buttons below the facts.
Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.
Frames narrower than the selected width show the component at the width available.
What changes at narrow widths
The facts grid uses minmax(min(100%, 12rem), 1fr), so at 320px each fact takes a full row.
At 30rem and below the act area becomes a one-column grid; each button is full width, wraps long labels and keeps a 2.75rem minimum height.
Headings, facts and buttons wrap anywhere, so long identifiers never cause horizontal scrolling, even at 200% text.
Actions stay after the facts in portrait and landscape, so users meet the facts before the buttons.
Click or tap the code once to select all of it, then copy.
Baseline
Mobile · 320px
The canonical pattern in a true 320px viewport, the minimum width every Forma component must support without page-level horizontal scrolling.
Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.
Frames narrower than the selected width show the component at the width available.
API and configuration
Forma components have no JavaScript API. Their public contract is the markup: native elements and attributes you write, and the CSS hooks below. The CSS hook table is generated from the built stylesheet, so it always matches the shipped implementation.
Native and ARIA attributes
Attribute
On
Values
Default
Description
aria-labelledby
root and verify section
id of a heading
—
Names the frame by its recognition heading and the verify region by its heading.
data-forma-verify
.forma-critical-value
true
absent
Adds a double underline to a value that must be read deliberately. Descriptive presentation only; it does not assert that the value was verified.
data-state
.forma-status-lozenge
ok | attention | blocked | unknown
absent
Adds a symbol to an application-reported state shown in the recognize part.
datetime
time
ISO date or date-time
—
Machine-readable timestamp for freshness facts.
CSS hooks (derived from dist/all.css)
Hook
Kind
Values or default
Description
.forma-verification-frame
Block class
—
Root bordered grid of the three parts.
.forma-verification-frame__act
Element class
—
Footer part with a top rule. A wrapping flex row; a leading p takes the remaining width. One full-width column at 30rem and below.
.forma-verification-frame__facts
Element class
—
A dl laid out as an auto-fit grid of fact cells at least 12rem wide, each with a bottom rule and a small secondary-color dt.
.forma-verification-frame__recognize
Element class
—
Header part with a bottom rule: kicker, heading and the application-reported state.
.forma-verification-frame__verify
Element class
—
The part to read deliberately: heading, facts and unresolved work.
Keyboard interaction
Keys
Result
Tab / Shift+Tab
Reaches the actions only after the facts in source order. No added keyboard behavior.
Enter / Space
Activates the focused native button; the effect is application-owned.
Events
Event
Description
click
Native click on act buttons. The application performs the transition after re-checking legality.
Form behavior
Not a form control. Act buttons may submit an application form that wraps the frame.
States
Verification frame states
State
How it is expressed
Presentation
Reported state
text (and optional .forma-status-lozenge) in the recognize part
Whatever the application reports, such as ready, stale, unknown or reconciling, shown without strengthening it.
Deliberate value
.forma-critical-value[data-forma-verify="true"]
Bold mono value with a double underline.
Stacked actions
@media (max-width: 30rem)
Act area becomes one column of full-width buttons.
Forced colors
@media (forced-colors: active)
Frame border and verified-value underline use CanvasText.
Accessibility
Forma provides
Places facts before actions in source, visual and focus order.
Separates the three parts with rules and headings rather than color.
Wraps every heading, fact and button label anywhere and stacks actions at narrow widths, keeping the frame within 320px at 200% text.
Your application supplies
Render only actions the application or Ordo currently allows, and re-check legality when an action is taken.
Report unknown, stale, partial and reconciling states as themselves; never show them as success or failure.
Label every fact and include units and freshness where they matter.
Use .forma-identifier and .forma-critical-value for codes, amounts and targets that are easy to misread.
Announce the outcome of the action in text after it completes.
Responsive behavior
Root and parts set min-inline-size: 0 and max-inline-size: 100%; headings, paragraphs, facts and buttons wrap anywhere.
Facts: repeat(auto-fit, minmax(min(100%, 12rem), 1fr)), one fact per row on phones.
Act area: wrapping flex row with a flexible leading paragraph; at 30rem and below a single-column grid of full-width, wrapping buttons.
Motion
No animation: the frame is static. Deliberate verification is supported by structure and a pause in the flow, not by motion. Buttons keep only the base perceptual hover and press color change.
Usage guidance
Do
State in the recognize part what the user is about to do, in plain words.
List unresolved work explicitly, even when there is none.
Avoid
Showing an action because the facts look fine; legality comes from application or Ordo state.
Hiding facts behind a disclosure when they are needed to decide.