Security posture

Security blockers

<forma-security-blockers>

Presents security conditions that block a transition without inventing remediation authority.

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

Purpose

Security blockers lists the conditions Tutela reports as blocking a transition such as a release: violated invariants, unknown security effects, stale evidence and expired exceptions. Each entry links its stable ID to the record and states the condition in text. The list is presentation only. It does not decide what blocks, rank blockers by risk, or offer remediation actions; any action such as requesting an exception belongs to the application and to Ordo, which decide whether it is legal.

Use when

  • A release or deployment page must show why a transition is blocked.
  • Violations and unknowns must be listed together with equal prominence.
  • Each blocker needs a deep link to its stable record.

Avoid when

Behavior to know

  • A bordered section with a thick start border and a heading that names the list.
  • Each entry is a stable-ID link followed by a text explanation on its own line.
  • The blocker kind is carried as data-kind for machine state and must also be written in text.
  • No buttons: the component never implies that a blocker can be dismissed or bypassed.

Basic example

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

Canonical

Minimal security blockers

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.

Release blockers

HTML · Minimal security blockers Raw HTML for HTML · Minimal security blockers
<forma-security-blockers class="forma-component-tag">
<section class="forma-security-blockers" aria-labelledby="security-blockers-title"><h2 id="security-blockers-title">Release blockers</h2>
<ul><li data-kind="violation"><a href="#SEC-INV-014">SEC-INV-014</a><span>Authorization invariant violated.</span></li>
<li data-kind="unknown"><a href="#SEC-UNK-003">SEC-UNK-003</a><span>Runtime egress behavior has not been established.</span></li></ul></section>
</forma-security-blockers>

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

Examples

Scenario

Every kind of release blocker

One entry for each kind Tutela reports. The kind is written as the first words of each explanation so it does not depend on data-kind, color or position.

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.

4 release blockers

  • SEC-INV-014Violated invariant: privileged actions are not authorized at the effect boundary.
  • SEC-UNK-003Unknown effect: runtime egress behavior has not been established.
  • SEC-EVD-031Stale evidence: invalidated by the session-store boundary change.
  • SEC-EXC-001Expired exception: ended and has not been renewed.
HTML · Every kind of release blocker Raw HTML for HTML · Every kind of release blocker
<forma-security-blockers class="forma-component-tag">
  <section class="forma-security-blockers" aria-labelledby="security-blockers-four-kinds-title">
    <h2 id="security-blockers-four-kinds-title">4 release blockers</h2>
    <ul>
      <li data-kind="violation"><a href="#SEC-INV-014">SEC-INV-014</a><span>Violated invariant: privileged actions are not authorized at the effect boundary.</span></li>
      <li data-kind="unknown"><a href="#SEC-UNK-003">SEC-UNK-003</a><span>Unknown effect: runtime egress behavior has not been established.</span></li>
      <li data-kind="stale"><a href="#SEC-EVD-031">SEC-EVD-031</a><span>Stale evidence: invalidated by the session-store boundary change.</span></li>
      <li data-kind="expired-exception"><a href="#SEC-EXC-001">SEC-EXC-001</a><span>Expired exception: ended <time datetime="2026-09-15">15 Sep 2026</time> and has not been renewed.</span></li>
    </ul>
  </section>
</forma-security-blockers>

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

Scenario

No blockers for this scope

When Tutela reports no blockers, the section stays in place with an explicit statement, so a missing list is never mistaken for a rendering failure or for unknown state.

Release blockers

Tutela reports no blockers for the assessed scope of artifact 7f3c9a21b4e05d88.

HTML · No blockers for this scope Raw HTML for HTML · No blockers for this scope
<forma-security-blockers class="forma-component-tag">
  <section class="forma-security-blockers" aria-labelledby="security-blockers-none-title">
    <h2 id="security-blockers-none-title">Release blockers</h2>
    <p>Tutela reports no blockers for the assessed scope of artifact <code>7f3c9a21b4e05d88</code>.</p>
  </section>
</forma-security-blockers>

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

Blockers on a phone

Long IDs and explanations 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 list is a single-column grid at every width; each entry's explanation is a block under its ID link.
  • Long IDs and explanations wrap; the section has zero minimum inline size, so nothing scrolls horizontally at 320px.
  • Entries are separated by a 0.75rem gap, keeping adjacent ID links distinct touch targets.
  • Orientation changes only reflow text; order stays as supplied by Tutela.
HTML · Blockers on a phone Raw HTML for HTML · Blockers on a phone
<forma-security-blockers class="forma-component-tag">
  <section class="forma-security-blockers" aria-labelledby="security-blockers-mobile-long-title">
    <h2 id="security-blockers-mobile-long-title">Release blockers</h2>
    <ul>
      <li data-kind="violation"><a href="#SEC-INV-014">SEC-INV-014</a><span>Violated invariant: tenant isolation is not enforced for imported organizations during background synchronization.</span></li>
      <li data-kind="unknown"><a href="#SEC-UNK-003">SEC-UNK-003</a><span>Unknown effect: runtime egress behavior has not been established.</span></li>
    </ul>
  </section>
</forma-security-blockers>

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
aria-labelledbysection.forma-security-blockersid of the heading—Names the region by its heading.
data-kindliviolation | unknown | stale | expired-exception—The Tutela blocker kind as machine state. Not styled by Forma CSS; write the kind in the entry text as well.
hrefastable record URL or #ID—Deep link to the blocking record.
datetimetimeISO 8601 date—Machine-readable date, for example when an exception expired.
CSS hooks (derived from dist/all.css)
HookKindValues or defaultDescription
.forma-security-blockersBlock class—Root section: bordered and padded, with a 0.35rem start border in the current text color (CanvasText in forced colors). Its list is a grid with a 0.75rem gap and each entry's span is displayed as a block.
Keyboard interaction
KeysResult
Tab / Shift+TabMoves between blocker links.
EnterFollows the focused link to the record.
Events
EventDescription
—No events. The list is re-rendered when Tutela's result changes.

Form behavior

Not a form control.

States

Security blockers states
StateHow it is expressedPresentation
Blockers presentul of li entriesEach blocker shows its stable ID and a text explanation.
No blockersa paragraph instead of the listAn explicit statement that nothing blocks the assessed scope.
Kinddata-kind plus textviolation, unknown, stale or expired-exception; the text states the kind.

Accessibility

Forma provides

  • Uses a named region with a heading and a real list, so the number of blockers is announced.
  • Keeps the start border visible in forced-colors mode as a structural cue.
  • Wraps all content at 320px without horizontal scrolling.

Your application supplies

  • Write the blocker kind and count in text; do not rely on data-kind or position.
  • Link every entry to a stable record ID.
  • Keep unknowns in the same list as violations, never behind a separate toggle.
  • Do not add dismiss or override controls; route any legal remediation through application actions governed by Ordo.

Responsive behavior

  • The section has zero minimum inline size; the list is a single-column grid at every width.
  • Each explanation is a block under its link, so long text wraps predictably.
  • No breakpoints are needed.

Motion

  • No animation: blockers are static content and appear or disappear with the render.

Usage guidance

Do

  • Put the count in the heading ("4 release blockers").
  • Keep the order Tutela supplies.

Avoid

  • Sorting unknowns below violations so they look less important.
  • Using red text or icons as the only way to show that something blocks.

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.