Supports
Claim: deployment is ready
Evidence: Required checks passed.
Source: CI run 1042
Scope: commit abc123
<forma-evidence-relationship>
Makes claim-to-evidence relationship type and scope explicit rather than relying on proximity alone.
<forma-evidence-relationship>patterns/evidence-relationship.htmlAn evidence relationship states, in one article, a claim, the type of relationship the evidence has to it (supports, contradicts, partially supports), the evidence itself, its source and the scope it covers, plus its current standing. Placing evidence next to a claim does not say how they relate; this component makes the relationship type a visible label. Forma lays out the header, body and footer; the relationship type, scope and status are application facts and Forma never infers them.
.forma-component-kicker.The smallest correct markup: the canonical pattern from patterns/evidence-relationship.html inside its public tag. Copy this first, then adapt labels, names and state.
Rendered from the canonical pattern file.
Supports
Evidence: Required checks passed.
Source: CI run 1042
Scope: commit abc123
<forma-evidence-relationship class="forma-component-tag">
<article class="forma-evidence-relationship" aria-labelledby="relationship-claim"><header><p class="forma-component-kicker">Supports</p><h2 id="relationship-claim">Claim: deployment is ready</h2></header><div class="forma-evidence-relationship__body"><p><strong>Evidence:</strong> Required checks passed.</p><p><strong>Source:</strong> CI run 1042</p><p><strong>Scope:</strong> commit abc123</p></div><footer><span class="forma-status-lozenge">Current</span></footer></article>
</forma-evidence-relationship>
Click or tap the code once to select all of it, then copy.
A load test contradicts the claim that the service meets its latency target. The relationship type Contradicts is the first thing read, and the footer states the evidence is current.
Contradicts
Evidence: Load test measured 612 ms p95 at 2,000 requests per second.
Source: Performance run PR-5520
Scope: EU West, release candidate rel-2026.10-rc2
<forma-evidence-relationship class="forma-component-tag">
<article class="forma-evidence-relationship" aria-labelledby="evidence-relationship-contradicting-evidence-claim">
<header>
<p class="forma-component-kicker">Contradicts</p>
<h2 id="evidence-relationship-contradicting-evidence-claim">Claim: checkout meets the 400 ms p95 latency target</h2>
</header>
<div class="forma-evidence-relationship__body">
<p><strong>Evidence:</strong> Load test measured 612 ms p95 at 2,000 requests per second.</p>
<p><strong>Source:</strong> Performance run PR-5520</p>
<p><strong>Scope:</strong> EU West, release candidate rel-2026.10-rc2</p>
</div>
<footer><span class="forma-status-lozenge">Current</span></footer>
</article>
</forma-evidence-relationship>
Click or tap the code once to select all of it, then copy.
Tests passed, but only for one of the two platforms the claim covers. The relationship is Partially supports, the scope line names what is covered, and the footer says the evidence is stale because a newer commit exists.
Partially supports
Evidence: UI regression suite passed, 412 of 412 tests.
Source: CI run 1187
Scope: Android only, commit a41c9e0. iOS has no run for this commit.
<forma-evidence-relationship class="forma-component-tag">
<article class="forma-evidence-relationship" aria-labelledby="evidence-relationship-partial-scope-claim">
<header>
<p class="forma-component-kicker">Partially supports</p>
<h2 id="evidence-relationship-partial-scope-claim">Claim: the mobile app is ready for release</h2>
</header>
<div class="forma-evidence-relationship__body">
<p><strong>Evidence:</strong> UI regression suite passed, 412 of 412 tests.</p>
<p><strong>Source:</strong> CI run 1187</p>
<p><strong>Scope:</strong> Android only, commit <span class="forma-identifier">a41c9e0</span>. iOS has no run for this commit.</p>
</div>
<footer><span class="forma-status-lozenge" data-state="unknown">Stale: 3 newer commits</span></footer>
</article>
</forma-evidence-relationship>
Click or tap the code once to select all of it, then copy.
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.
A supporting relationship at phone width. The single-column layout is unchanged; long claims and scope lines wrap.
Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.
<forma-evidence-relationship class="forma-component-tag">
<article class="forma-evidence-relationship" aria-labelledby="evidence-relationship-mobile-evidence-claim">
<header>
<p class="forma-component-kicker">Supports</p>
<h2 id="evidence-relationship-mobile-evidence-claim">Claim: backups are restorable</h2>
</header>
<div class="forma-evidence-relationship__body">
<p><strong>Evidence:</strong> Monthly restore drill completed in 38 minutes.</p>
<p><strong>Source:</strong> <a href="#evidence-relationship-mobile-evidence-drill">Restore drill record DR-0926</a></p>
<p><strong>Scope:</strong> Production database, snapshot of 26 Sep 2026</p>
</div>
<footer><span class="forma-status-lozenge" data-state="ok">Current</span></footer>
</article>
</forma-evidence-relationship>
Click or tap the code once to select all of it, then copy.
The canonical pattern in a true 320px viewport, the minimum width every Forma component must support without page-level horizontal scrolling.
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.
| Attribute | On | Values | Default | Description |
|---|---|---|---|---|
aria-labelledby | article.forma-evidence-relationship | id of the claim heading | — | Names the article by its claim. |
| Hook | Kind | Values or default | Description |
|---|---|---|---|
.forma-evidence-relationship | Block class | — | Root article; a grid of header, body and footer with 0.75rem gaps. Removes the trailing margin of the header's last child. |
.forma-evidence-relationship__body | Element class | — | Grid of labelled evidence statements with 0.5rem gaps; its last child has no bottom margin. |
| Keys | Result |
|---|---|
| None | Static content; links inside the body are reached with Tab. |
Not a form control.
| State | How it is expressed | Presentation |
|---|---|---|
| Relationship type | text in the header (Supports, Contradicts, Partially supports) | Supplied by the application; Forma applies no type-specific styling. |
| Evidence standing | Status lozenge text in the footer | Current, Stale, Superseded and so on, stated in words. |
Generated fault-injection specimens expose content, spacing, color-cue, and reduced-effective-contrast risks. They screen presentation robustness as engineering screens without claiming human-subject validation.