Finding
A structured evidence-oriented finding block that keeps observation, implication, possible action, and evidence-needed content distinct without inventing domain conclusions.
Capability note. Folio does not generate findings or recommendations. The consuming application owns every claim and should distinguish observation from inference and action.
Observation to action
A definition list keeps the reasoning stages explicit in source order.
On narrow screens the embedded example uses a screen-only inspection layout. Printing and the standalone document keep Folio's physical print rules.
View HTML
<ef-print-finding compact>
<h3>Release governance</h3>
<dl>
<div><dt>Observation</dt><dd>Release approval occurs outside the delivery team.</dd></div>
<div><dt>Implication</dt><dd>Batching pressure may increase lead time.</dd></div>
<div><dt>Possible action</dt><dd>Test a narrower approval policy for low-risk changes.</dd></div>
<div><dt>Evidence needed</dt><dd>Lead-time and change-failure data before and after the trial.</dd></div>
</dl>
</ef-print-finding>
Evidence-limited finding
The component supports uncertainty instead of forcing a recommendation.
On narrow screens the embedded example uses a screen-only inspection layout. Printing and the standalone document keep Folio's physical print rules.
View HTML
<ef-print-finding>
<h3>Cross-team consistency</h3>
<dl>
<div><dt>Observation</dt><dd>Two cohorts report materially different workflow behavior.</dd></div>
<div><dt>Implication</dt><dd>The organization-wide aggregate may hide local operating models.</dd></div>
<div><dt>Evidence needed</dt><dd>Additional responses from the underrepresented cohort.</dd></div>
</dl>
</ef-print-finding>
Comparison finding
Labels remain authored text so a grayscale or assistive-technology reader receives the same structure.
On narrow screens the embedded example uses a screen-only inspection layout. Printing and the standalone document keep Folio's physical print rules.
View HTML
<ef-print-finding compact>
<h3>Claimed versus observed process</h3>
<dl>
<div><dt>Observation</dt><dd>The team self-labels as Scrum while approvals and testing remain stage-gated.</dd></div>
<div><dt>Interpretation</dt><dd>The observed profile is hybrid rather than a pure framework match.</dd></div>
</dl>
</ef-print-finding>