Security posture

Security invariant result

<forma-security-invariant-result>

Reports invariant evaluation outcomes with explicit state rather than color-only pass/fail cues.

Authoring tag
<forma-security-invariant-result>
Behavior owner
Aegis / application
Canonical source
patterns/security-invariant-result.html

Purpose

An invariant result presents one security invariant as Tutela evaluated it: its stable ID, its state written as a word (Verified, Violated, Unknown, Stale or N/A), the invariant statement, and the related threats, evidence and verification requirements as links and terms. It keeps the outcome explicit and traceable instead of a green or red dot. Tutela evaluates the invariant; Forma displays the supplied state and never recalculates it.

Use when

  • A reviewer opens an invariant from a posture, blocker list or evidence chain.
  • The invariant statement, its state and its evidence must be read together.
  • An invariant is Unknown and the page must explain what is missing.

Avoid when

Behavior to know

  • The header places an eyebrow on its own line, then the stable ID heading and the state word side by side, wrapping when narrow.
  • State is bold text; data-state mirrors it as machine state.
  • Related records are in a description list that auto-fits columns of at least 10rem.
  • The article id is the stable invariant ID for deep links.

Basic example

The smallest correct markup: the canonical pattern from patterns/security-invariant-result.html inside its public tag. Copy this first, then adapt labels, names and state.

Canonical

Minimal security invariant result

Rendered from the canonical pattern file.

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.

Security invariant

SEC-INV-014

Violated

Privileged actions require explicit authorization at the effect boundary.

Evidence
SEC-EVD-042
Independent verification
Required
HTML · Minimal security invariant result Raw HTML for HTML · Minimal security invariant result
<forma-security-invariant-result class="forma-component-tag">
<article class="forma-invariant-result" id="SEC-INV-014" data-state="violated"><header><p>Security invariant</p><h3>SEC-INV-014</h3><strong>Violated</strong></header><p>Privileged actions require explicit authorization at the effect boundary.</p><dl><div><dt>Threats</dt><dd><a href="#SEC-THR-004">SEC-THR-004</a></dd></div><div><dt>Evidence</dt><dd><a href="#SEC-EVD-042">SEC-EVD-042</a></dd></div><div><dt>Independent verification</dt><dd>Required</dd></div></dl></article>
</forma-security-invariant-result>

Click or tap the code once to select all of it, then copy.

Examples

Scenario

Verified invariant

An invariant Tutela reports as Verified, with its current evidence and independent verification recorded.

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.

Security invariant

SEC-INV-003

Verified

Session tokens are bound to the device that created them.

Evidence
SEC-EVD-044 (current)
Independent verification
Completed
HTML · Verified invariant Raw HTML for HTML · Verified invariant
<forma-security-invariant-result class="forma-component-tag">
  <article class="forma-invariant-result" id="security-invariant-result-verified-SEC-INV-003" data-state="verified" aria-labelledby="security-invariant-result-verified-title">
    <header><p>Security invariant</p><h3 id="security-invariant-result-verified-title">SEC-INV-003</h3><strong>Verified</strong></header>
    <p>Session tokens are bound to the device that created them.</p>
    <dl>
      <div><dt>Threats</dt><dd><a href="#SEC-THR-001">SEC-THR-001</a></dd></div>
      <div><dt>Evidence</dt><dd><a href="#SEC-EVD-044">SEC-EVD-044</a> (current)</dd></div>
      <div><dt>Independent verification</dt><dd>Completed <time datetime="2026-09-27">27 Sep 2026</time></dd></div>
    </dl>
  </article>
</forma-security-invariant-result>

Click or tap the code once to select all of it, then copy.

Scenario

Unknown because evidence is missing

An invariant that cannot be evaluated. The Unknown state is written out and the missing evidence is listed as its own term, so it is not mistaken for a pass or a violation.

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.

Security invariant

SEC-INV-021

Unknown

Outbound network traffic is limited to approved destinations.

Evidence
None recorded for this artifact
Unknowns
SEC-UNK-003
Independent verification
Required
HTML · Unknown because evidence is missing Raw HTML for HTML · Unknown because evidence is missing
<forma-security-invariant-result class="forma-component-tag">
  <article class="forma-invariant-result" id="security-invariant-result-unknown-SEC-INV-021" data-state="unknown" aria-labelledby="security-invariant-result-unknown-title">
    <header><p>Security invariant</p><h3 id="security-invariant-result-unknown-title">SEC-INV-021</h3><strong>Unknown</strong></header>
    <p>Outbound network traffic is limited to approved destinations.</p>
    <dl>
      <div><dt>Threats</dt><dd><a href="#SEC-THR-007">SEC-THR-007</a></dd></div>
      <div><dt>Evidence</dt><dd>None recorded for this artifact</dd></div>
      <div><dt>Unknowns</dt><dd><a href="#SEC-UNK-003">SEC-UNK-003</a></dd></div>
      <div><dt>Independent verification</dt><dd>Required</dd></div>
    </dl>
  </article>
</forma-security-invariant-result>

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

Violated invariant on a phone

A violated invariant with a long statement at phone width.

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.

Viewport width

Frames narrower than the selected width show the component at the width available.

What changes at narrow widths

  • The header wraps: the eyebrow takes a full line, then the ID and the state word share a line or wrap onto two when space runs out.
  • The related-records list auto-fits columns of at least min(10rem, 100%), so it becomes one column at 320px.
  • The statement and values wrap; long IDs break anywhere without horizontal scrolling.
  • Reading order is identical in portrait and landscape.
HTML · Violated invariant on a phone Raw HTML for HTML · Violated invariant on a phone
<forma-security-invariant-result class="forma-component-tag">
  <article class="forma-invariant-result" id="security-invariant-result-mobile-SEC-INV-014" data-state="violated" aria-labelledby="security-invariant-result-mobile-title">
    <header><p>Security invariant</p><h3 id="security-invariant-result-mobile-title">SEC-INV-014</h3><strong>Violated</strong></header>
    <p>Privileged actions require explicit authorization at the effect boundary, including actions started by agent tools on behalf of a user.</p>
    <dl>
      <div><dt>Threats</dt><dd><a href="#SEC-THR-004">SEC-THR-004</a></dd></div>
      <div><dt>Evidence</dt><dd><a href="#SEC-EVD-042">SEC-EVD-042</a></dd></div>
      <div><dt>Independent verification</dt><dd>Required</dd></div>
    </dl>
  </article>
</forma-security-invariant-result>

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 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.

Viewport width

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
AttributeOnValuesDefaultDescription
idarticlestable invariant ID—Deep-link target; use the stable Tutela ID such as SEC-INV-014.
data-statearticleverified | violated | unknown | stale | na—Tutela's evaluation as machine state. Not styled by Forma CSS; the bold state word is the visible cue.
aria-labelledbyarticleid of the heading—Optional. Names the article by its invariant ID.
hrefastable record URL or #ID—Links to threats, evidence and unknowns.
datetimetimeISO 8601 date—Machine-readable verification date.
CSS hooks (derived from dist/all.css)
HookKindValues or defaultDescription
.forma-invariant-resultBlock class—Root article: bordered, padded primary surface. The header is a wrapping flex row whose first paragraph is a full-width uppercase eyebrow; the description list is an auto-fit grid of at least 10rem columns with secondary-colored bold terms and values that wrap anywhere.
Keyboard interaction
KeysResult
Tab / Shift+TabMoves between related-record links.
EnterFollows the focused link.
Events
EventDescription
—No events.

Form behavior

Not a form control.

States

Security invariant result states
StateHow it is expressedPresentation
Verifieddata-state="verified" + text VerifiedCurrent evidence supports the invariant.
Violateddata-state="violated" + text ViolatedEvidence shows the invariant does not hold.
Unknowndata-state="unknown" + text UnknownThe invariant cannot be evaluated; missing evidence or unknowns are listed.
Staledata-state="stale" + text StaleThe supporting evidence has been invalidated.
N/Adata-state="na" + text Not applicableThe invariant does not apply to this scope.

Accessibility

Forma provides

  • Shows the state as a bold word next to the ID; no color-only cue is used.
  • Uses a description list for related records so terms and values are paired.
  • Reflows to one column at 320px.

Your application supplies

  • Render the state exactly as Tutela supplied it, as text.
  • Write "Not applicable" or "N/A" explicitly; do not hide inapplicable invariants when counts elsewhere include them.
  • List missing evidence and unknowns as terms rather than leaving values empty.
  • Use the stable ID as article id and heading.

Responsive behavior

  • The header is a wrapping flex row; the eyebrow always takes a full line.
  • Related records auto-fit into columns of at least min(10rem, 100%), one column on phones.
  • Values wrap anywhere. No breakpoints are needed.

Motion

  • No animation: the result is static and a re-evaluation replaces the text.

Usage guidance

Do

  • Keep the invariant statement visible; the ID alone is not meaningful to most readers.
  • Link current evidence and note its freshness.

Avoid

  • Using check marks or colored dots without the state word.
  • Showing Verified when evidence is stale; show Stale as Tutela reports it.

Verification specimens

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.