Projects explicit authoritative states with text and structural cues so unknown, stale, partial and unavailable do not collapse into one generic status.
State survivability is a list of authoritative states, each rendered as a Status lozenge beside a sentence explaining what that state means for the user. It exists so that distinct conditions, such as unknown, stale, partial, pending and unavailable, stay distinct on screen and survive the loss of any single visual cue (color, icon, border or motion). The application or Ordo supplies each state and its explanation; Forma only lays out the rows and never merges, ranks or reinterprets them.
Use when
Several facets of one object or result have different states that must each be read correctly (for example scope complete, evidence stale, one capability unavailable).
A consequential decision depends on distinguishing unknown from failed, partial from complete, or stale from current.
An audit or verification view must remain correct in grayscale, forced colors and without icons.
Avoid when
There is a single operation with one outcome and recovery actions: use Operation status.
The rows are prerequisites for a transition that the user works through: use Readiness checklist.
Each row pairs a named state with a sentence of consequence; the explanation is never optional.
Rows are separated by rules and laid out in a two-column grid that collapses to one column on narrow screens.
States are not reordered, summarized or color-coded by Forma.
Basic example
The smallest correct markup: the canonical pattern from patterns/state-survivability.html inside its public tag. Copy this first, then adapt labels, names and state.
Canonical
Minimal state survivability
Rendered from the canonical pattern file.
Authoritative state projection
Unknown
Outcome has not been confirmed. Reconcile before retrying.
Stale
The displayed evidence is older than the application freshness policy permits.
Partial
Only the stated scope is complete. Omitted scope remains unresolved.
Unavailable
The application reports this capability is currently unavailable.
<forma-state-survivability class="forma-component-tag">
<section class="forma-state-survivability" aria-labelledby="state-survivability-title">
<h3 id="state-survivability-title">Authoritative state projection</h3>
<div class="forma-state-survivability__state">
<span class="forma-status-lozenge" data-state="unknown">Unknown</span>
<p>Outcome has not been confirmed. Reconcile before retrying.</p>
</div>
<div class="forma-state-survivability__state">
<span class="forma-status-lozenge" data-state="attention">Stale</span>
<p>The displayed evidence is older than the application freshness policy permits.</p>
</div>
<div class="forma-state-survivability__state">
<span class="forma-status-lozenge" data-state="attention">Partial</span>
<p>Only the stated scope is complete. Omitted scope remains unresolved.</p>
</div>
<div class="forma-state-survivability__state">
<span class="forma-status-lozenge" data-state="blocked">Unavailable</span>
<p>The application reports this capability is currently unavailable.</p>
</div>
</section>
</forma-state-survivability>
Click or tap the code once to select all of it, then copy.
Examples
Scenario
Import with scoped completeness
The result of a data import where different parts ended in different states. Confirmed, partial and pending stay separate, so a reader cannot conclude the whole import succeeded.
Customer import, 30 September
Confirmed
8,000 customer records were written and verified.
Partial
Contacts were imported for 7,640 customers. 360 customers have no contacts yet; they are listed in the import report.
Pending
Credit limits are queued for approval and are not yet in effect.
<forma-state-survivability class="forma-component-tag">
<section class="forma-state-survivability" aria-labelledby="state-survivability-import-scope-title">
<h3 id="state-survivability-import-scope-title">Customer import, 30 September</h3>
<div class="forma-state-survivability__state">
<span class="forma-status-lozenge" data-state="ok">Confirmed</span>
<p>8,000 customer records were written and verified.</p>
</div>
<div class="forma-state-survivability__state">
<span class="forma-status-lozenge" data-state="attention">Partial</span>
<p>Contacts were imported for 7,640 customers. 360 customers have no contacts yet; they are listed in the import report.</p>
</div>
<div class="forma-state-survivability__state">
<span class="forma-status-lozenge" data-state="attention">Pending</span>
<p>Credit limits are queued for approval and are not yet in effect.</p>
</div>
</section>
</forma-state-survivability>
Click or tap the code once to select all of it, then copy.
Scenario
Control verification with insufficient data
A verification view for one security control. Insufficient data and not applicable are shown as their own states rather than being counted as passes or failures.
Access review control
Passed
Quarterly reviews were completed for all production systems.
Insufficient data
Only 2 of 5 required review records were supplied for the finance systems. No conclusion is drawn.
Not applicable
The legacy HR system was retired before this review period.
<forma-state-survivability class="forma-component-tag">
<section class="forma-state-survivability" aria-labelledby="state-survivability-control-verification-title">
<h3 id="state-survivability-control-verification-title">Access review control</h3>
<div class="forma-state-survivability__state">
<span class="forma-status-lozenge" data-state="ok">Passed</span>
<p>Quarterly reviews were completed for all production systems.</p>
</div>
<div class="forma-state-survivability__state">
<span class="forma-status-lozenge" data-state="unknown">Insufficient data</span>
<p>Only 2 of 5 required review records were supplied for the finance systems. No conclusion is drawn.</p>
</div>
<div class="forma-state-survivability__state">
<span class="forma-status-lozenge">Not applicable</span>
<p>The legacy HR system was retired before this review period.</p>
</div>
</section>
</forma-state-survivability>
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 sync states
Sync states for a mobile device list at phone width.
Frames narrower than the selected width show the component at the width available.
What changes at narrow widths
Below 30rem each row becomes a single column: the lozenge sits above its explanation.
Explanations wrap in the full width; nothing scrolls horizontally at 320px.
Row dividers remain, so each state and its explanation still read as one unit.
There are no touch targets in the rows; if a state needs action, pair the list with Recovery actions or a button below it.
<forma-state-survivability class="forma-component-tag">
<section class="forma-state-survivability" aria-labelledby="state-survivability-mobile-sync-states-title">
<h3 id="state-survivability-mobile-sync-states-title">Field tablet sync</h3>
<div class="forma-state-survivability__state">
<span class="forma-status-lozenge" data-state="unknown">Unknown</span>
<p>The last upload from tablet 14 has not been acknowledged by the server.</p>
</div>
<div class="forma-state-survivability__state">
<span class="forma-status-lozenge" data-state="attention">Stale</span>
<p>Tablet 9 last synced 3 days ago; its inspections are not in today's report.</p>
</div>
<div class="forma-state-survivability__state">
<span class="forma-status-lozenge" data-state="blocked">Unavailable</span>
<p>Tablet 2 is locked by device management and cannot sync.</p>
</div>
</section>
</forma-state-survivability>
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.
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
section.forma-state-survivability
id of the heading
—
Names the region from its heading.
data-state
.forma-status-lozenge
ok | attention | unknown | blocked
absent (neutral)
Glyph for each state's lozenge. The lozenge text must name the exact state.
CSS hooks (derived from dist/all.css)
Hook
Kind
Values or default
Description
.forma-state-survivability
Block class
—
Root grid stacking the heading and state rows with a consistent gap.
.forma-state-survivability__state
Element class
—
One state row: a two-column grid (lozenge, explanation) with a bottom rule. Single column below 30rem.
Keyboard interaction
Keys
Result
—
No interactive content by default. Any links inside explanations follow native link behavior.
Events
Event
Description
—
None.
Form behavior
Not a form control.
States
State survivability states
State
How it is expressed
Presentation
Confirmed / passed
lozenge with data-state="ok"
The authority confirmed this facet.
Stale / partial / pending
lozenge with data-state="attention" and the exact word
Each keeps its own word; they are not merged into "Warning".
Unknown / insufficient
lozenge with data-state="unknown"
No conclusion is available. Unknown is not failure.
Blocked / unavailable
lozenge with data-state="blocked"
The facet cannot be used or completed.
Neutral
lozenge without data-state
States such as Not applicable that imply no attention.
Accessibility
Forma provides
Carries each state in text, glyph shape and row structure, so the meaning survives removal of color, icons, borders or motion.
Keeps states in document order as supplied, with no visual reordering.
Your application supplies
Use the exact state word from the domain model in each lozenge.
Write an explanation that states the consequence and scope for every row.
Do not summarize mixed states into one overall status unless the authority provides that summary.
Responsive behavior
Rows are minmax(8rem, auto) minmax(0, 1fr) grids; the explanation column wraps.
Below 30rem each row becomes one column with the lozenge above its explanation.
The list grows vertically with the number of states; there is no truncation.
Motion
No animation: rows change when the application re-renders them.
Usage guidance
Do
Keep distinct states distinct, even when they share a glyph.
Order rows as the domain model orders them, not by severity.
Avoid
Collapsing unknown, stale and partial into one "Attention" row.
Omitting the explanation because the lozenge seems self-explanatory.