Files
server-26/drb-frontend/components/ui/MachineOutputNotice.tsx
Logan CusanoandClaude Opus 5 b7222230bd
Build & Deploy / Build & push images (push) Successful in 4m25s
Build & Deploy / Deploy to VM (push) Successful in 1m55s
Build & Deploy / Report a failed deploy (push) Skipped
frontend: label machine-generated output and unbuilt entitlements (Gate A)
Gate A (BUSINESS_MODEL.md, board minutes #42, dated to today by minutes #79
decision 14) blocks putting a price or an unbuilt entitlement claim on a
surface a reader can see, and requires that unverified machine assertions be
labelled as such on the same screen as the assertion.

The pricing leg was already met — /pricing and both homepage CTAs stopped
quoting the invented catalog. Condition A2 was not: a search of the whole
frontend for a "machine-generated" or "unverified" qualifier returned zero
hits. Every transcript, summary, title, location, unit list and vehicle list
is pipeline output that no human reviews, and entity-name accuracy in those
transcripts has never been measured (server-26#48) — yet all of it was
rendered to the reader as plain fact. Unqualified machine assertions about
real incidents and real people is the exposure Gate A exists to stop.

A2 — one reusable element, components/ui/MachineOutputNotice.tsx, rendered on
the same screen as the output (a footnote elsewhere does not satisfy A1's
"same screen" standard). Three variants for three shapes of surface, all
saying the same thing; the "popup" variant uses fixed grays because a Leaflet
popup is stock-white in both themes. Covered:

  - incident detail: under the summary (covers summary, title, location,
    units on scene/cleared, vehicles, tags) and above the call spine
  - incident list: above the timeline groups
  - Archive (/calls): above the transcript rows
  - node detail: above the Recent Calls table
  - Watch//alerts: above the events table, whose Snippet column is transcript
    text and whose keyword match was made against it
  - Live map: the desktop incident rail, pinned above the scroll area so it
    cannot be scrolled off the screen it qualifies; the mobile drawer; the
    incident marker popup; the incident-path stop popup
  - /systems: the source-call transcript preview
  - /features: the two marketing sections that describe the AI pipeline

A1 — components/ui/UnbuiltMarker.tsx marks a claim unbuilt inline:

  - /faq: the retention answer promised 7/90/365-day windows. There is no TTL
    and no deletion sweep anywhere in the product (server-26#44), so the
    answer now states plainly that nothing is deleted automatically and marks
    per-plan retention as not yet available.
  - /settings/billing: the plan cards' claims — custom retention, SSO/SAML,
    uptime SLA, data residency — are marked not-yet-available next to the plan
    that makes them.

Labelling only. No retention, SSO, SLA or residency was built; no billing,
Stripe or checkout code was touched (Gate B still bars charging anyone); no
price was added anywhere; no Python was touched. Both themes verified against
the light-mode !important overrides in globals.css, which are untouched.

tsc --noEmit clean.

Refs: server-26#46, server-26#44, server-26#48

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-31 02:47:40 -04:00

113 lines
3.6 KiB
TypeScript

import type { ReactNode } from "react";
/**
* Gate A, condition A2 (board minutes #42 / #79, tracked at server-26#46).
*
* Transcripts, incident summaries, titles, locations and extracted entities are
* all produced by the AI pipeline (transcription -> scene/entity extraction ->
* correlation -> summary). None of it is reviewed by a human before a reader
* sees it, and entity-name accuracy has never been measured (server-26#48).
*
* Gate A therefore requires that machine-generated content is labelled as
* machine-generated and unverified ON THE SAME SCREEN as the content itself —
* a note on another page does not satisfy the condition. This is the single
* element that does that; render it beside every AI-derived surface.
*
* Copy rules (do not "improve" these away):
* - the words "machine-generated" and "unverified" must both appear
* - it must not promise accuracy
* - it must not name a model or a vendor
* - it must not state or imply a price
*
* Variants exist only because the surfaces differ in space, not because the
* claim differs. All three say the same thing.
* block — full-width strip above/below a body of AI output (default)
* inline — one compact line, for dense list headers and table captions
* popup — for a Leaflet popup, which is stock-white in BOTH themes, so it
* uses fixed grays instead of the ink/surface tokens
*/
type Variant = "block" | "inline" | "popup";
function InfoGlyph({ className }: { className?: string }) {
return (
<svg
width="13"
height="13"
viewBox="0 0 16 16"
fill="none"
stroke="currentColor"
strokeWidth="1.5"
strokeLinecap="round"
aria-hidden="true"
className={className}
>
<circle cx="8" cy="8" r="6.5" />
<path d="M8 7.25v4" />
<path d="M8 4.75h.01" />
</svg>
);
}
const LEAD = "Machine-generated and unverified";
interface Props {
variant?: Variant;
/** Overrides the trailing sentence. The lead ("Machine-generated and unverified") is fixed. */
detail?: ReactNode;
className?: string;
}
export function MachineOutputNotice({ variant = "block", detail, className }: Props) {
const body =
detail ??
"transcripts, summaries and extracted details are automated output and may contain errors. Check the recording before acting on them.";
const shortBody = detail ?? "automated output, may contain errors.";
if (variant === "popup") {
// Leaflet popups render on a white wrapper regardless of theme, so this
// deliberately does not use the ink/surface tokens.
return (
<p
role="note"
className={["text-[10px] leading-snug text-gray-500 mt-1.5 pt-1.5 border-t border-gray-200", className ?? ""]
.filter(Boolean)
.join(" ")}
>
{LEAD} — {shortBody}
</p>
);
}
if (variant === "inline") {
return (
<p
role="note"
className={["flex items-center gap-1.5 text-xs text-ink-muted", className ?? ""].filter(Boolean).join(" ")}
>
<InfoGlyph className="shrink-0" />
<span>
<span className="text-ink-2 font-medium">{LEAD}</span> — {shortBody}
</span>
</p>
);
}
return (
<div
role="note"
className={[
"flex items-start gap-2 rounded-lg border border-line bg-raised/60 px-3 py-2",
className ?? "",
]
.filter(Boolean)
.join(" ")}
>
<InfoGlyph className="mt-0.5 shrink-0 text-ink-muted" />
<p className="text-xs leading-relaxed text-ink-muted">
<span className="text-ink-2 font-medium">{LEAD}</span> — {body}
</p>
</div>
);
}