Unknown security effect
SEC-UNK-003
Runtime egress behavior has not been established.
- Consequence
- Release posture cannot be established for the network boundary.
- Evidence needed
- Observed egress policy test against the release artifact.
<forma-security-unknown>
Represents unknown security state explicitly instead of collapsing it into failure or success.
<forma-security-unknown>patterns/security-unknown.htmlA security unknown records a security effect that has not been established: what is unknown, the consequence of not knowing, the evidence needed to resolve it and, where one exists, the obligation to obtain that evidence. It gives unknowns their own first-class record with a stable ID, so they are never quietly counted as passes or folded into failures. Tutela decides that something is unknown and what it blocks; the application or Ordo owns any obligation or task. Forma presents the record.
article with an "Unknown security effect" eyebrow, the stable ID as heading and a plain statement of what is unknown.The smallest correct markup: the canonical pattern from patterns/security-unknown.html inside its public tag. Copy this first, then adapt labels, names and state.
Rendered from the canonical pattern file.
Unknown security effect
Runtime egress behavior has not been established.
<forma-security-unknown class="forma-component-tag">
<article class="forma-security-unknown" id="SEC-UNK-003"><header><p>Unknown security effect</p><h3>SEC-UNK-003</h3></header><p>Runtime egress behavior has not been established.</p>
<dl><div><dt>Consequence</dt><dd>Release posture cannot be established for the network boundary.</dd></div><div><dt>Evidence needed</dt><dd>Observed egress policy test against the release artifact.</dd></div></dl></article>
</forma-security-unknown>
Click or tap the code once to select all of it, then copy.
An unknown that blocks release, with the obligation to obtain the missing evidence linked by ID. The owner and due date come from the application's obligation record.
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.
Unknown security effect
The DNS resolution path used by the release artifact has not been observed.
<forma-security-unknown class="forma-component-tag">
<article class="forma-security-unknown" id="security-unknown-with-obligation-SEC-UNK-004" aria-labelledby="security-unknown-with-obligation-title">
<header><p>Unknown security effect</p><h3 id="security-unknown-with-obligation-title">SEC-UNK-004</h3></header>
<p>The DNS resolution path used by the release artifact has not been observed.</p>
<dl>
<div><dt>Consequence</dt><dd>Blocks release: egress controls cannot be shown to cover name resolution.</dd></div>
<div><dt>Evidence needed</dt><dd>Packet capture from the staging runtime against this artifact.</dd></div>
<div><dt>Obligation</dt><dd><a href="#OBL-118">OBL-118</a>, platform team, due <time datetime="2026-10-03">3 Oct 2026</time></dd></div>
</dl>
</article>
</forma-security-unknown>
Click or tap the code once to select all of it, then copy.
An unknown that Tutela reports as not blocking this release scope. It is still recorded and visible; the consequence states the limit explicitly, and no obligation exists yet.
Unknown security effect
Behavior of the offline export feature on shared devices has not been established.
<forma-security-unknown class="forma-component-tag">
<article class="forma-security-unknown" id="security-unknown-non-blocking-SEC-UNK-009" aria-labelledby="security-unknown-non-blocking-title">
<header><p>Unknown security effect</p><h3 id="security-unknown-non-blocking-title">SEC-UNK-009</h3></header>
<p>Behavior of the offline export feature on shared devices has not been established.</p>
<dl>
<div><dt>Consequence</dt><dd>Does not block this release; offline export is outside the assessed scope.</dd></div>
<div><dt>Evidence needed</dt><dd>Device-sharing test on the supported mobile platforms.</dd></div>
<div><dt>Obligation</dt><dd>None assigned</dd></div>
</dl>
</article>
</forma-security-unknown>
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.
An unknown with long consequence text at phone width.
min(12rem, 100%), so at 320px each term/value pair stacks in one column.<forma-security-unknown class="forma-component-tag">
<article class="forma-security-unknown" id="security-unknown-mobile-SEC-UNK-003" aria-labelledby="security-unknown-mobile-title">
<header><p>Unknown security effect</p><h3 id="security-unknown-mobile-title">SEC-UNK-003</h3></header>
<p>Runtime egress behavior has not been established.</p>
<dl>
<div><dt>Consequence</dt><dd>Release posture cannot be established for the network boundary, including traffic initiated by agent tools and scheduled jobs.</dd></div>
<div><dt>Evidence needed</dt><dd>Observed egress policy test against the release artifact.</dd></div>
</dl>
</article>
</forma-security-unknown>
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 |
|---|---|---|---|---|
id | article | stable unknown ID | — | Deep-link target; use the stable Tutela ID such as SEC-UNK-003. |
aria-labelledby | article | id of the heading | — | Optional. Names the article by its unknown ID. |
href | a | stable record URL or #ID | — | Links to the obligation or related records. |
datetime | time | ISO 8601 date | — | Machine-readable obligation due date. |
| Hook | Kind | Values or default | Description |
|---|---|---|---|
.forma-security-unknown | Block class | — | Root article: bordered, padded primary surface. The header's paragraph is a small uppercase eyebrow; the description list is an auto-fit grid of at least 12rem columns with secondary-colored bold terms and values that wrap anywhere. |
| Keys | Result |
|---|---|
| Tab / Shift+Tab | Moves between links in the record. |
| Enter | Follows the focused link. |
| Event | Description |
|---|---|
— | No events. |
Not a form control.
| State | How it is expressed | Presentation |
|---|---|---|
| Blocking | Consequence text states that it blocks | The unknown prevents a posture or transition for its scope. |
| Non-blocking | Consequence text states the limit | Recorded and visible, but outside the blocking scope. |
| With obligation | Obligation term with a link | Someone owes the evidence; owner and due date shown. |
| Without obligation | Obligation term says None assigned | Explicitly unowned rather than blank. |
min(12rem, 100%), one column on narrow screens.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.