Native
Findings, native skin

Source: c147 Findings, a Common Tongue — Phase 2, the copy of S2 (the composed Findings), 2026-11-13 · rows from /api/findings and /api/policies in useNativeWorld('meridian-day90'), derived from the world's sessions (Phase 1)

mockWorld
loading the world…bake-off →
Qpoint

Safety & SecurityFindings

Open findings, grouped by the policy producing them. Every finding is independently addressable; grouping never merges them. A finding is Enforced when Qpoint blocked it, and then it is resolved in the same moment as prevented; it is Observed when it was only recorded.

data: synthetic · meridian-day90v0.1.0

The copy of S2, replicated first (c147 R2): the listing bar (Outcome · Severity · Status · Framework, Grouped ⇄ Individual), the grouped ledger with its policy-in-context section, and the member table with its card, in the operator's words on purpose; the person's words come in Phase 3. Its defaults follow S2's: Open and, since Phase 4 (Q4 in the prototype's model), every outcome; in Phase 2 they were Open and Enforced (c121 D3), and a machine whose findings were all Observed or all prevented opened on the zero state.

What the fleet → personal rules changed: the Subject column and the card's Subject block left the rows (rule 3), with the harness and the session in their place; the header says once whose machine it is. The policy filter and the team chip are gone (one machine, one person). Decided, not copied: the operator's verbs (Resolve, "Too noisy? Change the policy's mode") are not drawn, since the person never moves a finding's status (finding-shape.md §3); the group header doesn't link to a policy page the native app doesn't have; the Harnesses and Frameworks columns show one pill and a count at this width. The SLA clock is the plane's rubric, carried in the sidecar.

Qpoint Brand Style Guide