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>
116 lines
5.2 KiB
TypeScript
116 lines
5.2 KiB
TypeScript
"use client";
|
|
|
|
import { useState } from "react";
|
|
import type { ReactNode } from "react";
|
|
import { Badge } from "@/components/ui/Badge";
|
|
import { LinkButton } from "@/components/ui/Button";
|
|
import { UnbuiltMarker } from "@/components/ui/UnbuiltMarker";
|
|
import { MachineOutputNotice } from "@/components/ui/MachineOutputNotice";
|
|
|
|
const FAQS: { q: string; a: ReactNode }[] = [
|
|
{
|
|
q: "What hardware do I need to run a node?",
|
|
a: "A node is a small field SDR device running our edge-node software — it needs an SDR dongle capable of receiving your local P25 or analog trunked system, and a network connection to reach your DRB account. Full setup instructions are provided once you add a node.",
|
|
},
|
|
{
|
|
q: "What's the difference between a 'call' and an 'incident'?",
|
|
a: "A call is a single radio transmission. An incident is the thing you actually care about — a pursuit, a fire, an accident — built by correlating related calls together, sometimes across multiple talkgroups or nodes. Incidents are the primary view; calls are the evidence behind them.",
|
|
},
|
|
{
|
|
q: "Does DRB do the transcription and AI work itself, or is that a separate cost?",
|
|
a: (
|
|
<>
|
|
Transcription and incident correlation run automatically on every recorded call and are
|
|
included — they are not billed as an add-on.
|
|
{/* Gate A / A2 (server-26#46) — qualified on the same screen as the claim. */}
|
|
<MachineOutputNotice className="mt-3 not-italic" />
|
|
</>
|
|
),
|
|
},
|
|
{
|
|
q: "Can I listen to live radio traffic without opening the dashboard?",
|
|
a: "Yes — the Discord bot can join a voice channel and relay live audio from any of your nodes, so your team can listen without a separate scanner app.",
|
|
},
|
|
{
|
|
q: "How does node ownership and team access work?",
|
|
a: "Admins have full access. Operators are scoped to a specific list of nodes they own — they see and manage only those. Viewers get read-only access to everything the org exposes. You manage all of this from Settings → Members.",
|
|
},
|
|
{
|
|
q: "What happens if I go over my plan's node or seat limit?",
|
|
a: "You'll see a plan-limit notice in Settings → Billing before anything is blocked. In this demo build there's no live enforcement wired up yet — see the Billing settings page for what's stubbed vs. real.",
|
|
},
|
|
{
|
|
// Gate A / A1 (server-26#46): plan-tiered retention windows are an unbuilt
|
|
// entitlement — there is no TTL and no deletion sweep anywhere in the
|
|
// product (server-26#44). The claim is marked unbuilt inline, on this
|
|
// screen, rather than quietly dropped.
|
|
q: "How long is call and incident history kept?",
|
|
a: (
|
|
<>
|
|
<UnbuiltMarker>Retention limits — not yet available</UnbuiltMarker>
|
|
<p className="mt-2">
|
|
Today nothing is deleted automatically: calls, recordings and incidents stay searchable and
|
|
linked to their incidents for as long as your account is open. Per-plan retention windows and
|
|
automatic deletion are not built yet, so we make no commitment about how long anything is kept
|
|
or when it goes away. If you need data removed, ask us and we will remove it by hand.
|
|
</p>
|
|
</>
|
|
),
|
|
},
|
|
{
|
|
q: "Is DMR supported?",
|
|
a: "Not yet — DMR is on the roadmap but the current release only decodes P25 and analog trunked systems.",
|
|
},
|
|
];
|
|
|
|
function ChevronIcon({ open }: { open: boolean }) {
|
|
return (
|
|
<svg
|
|
width="18" height="18" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="2"
|
|
strokeLinecap="round" strokeLinejoin="round"
|
|
className={`text-gray-500 shrink-0 transition-transform ${open ? "rotate-180" : ""}`}
|
|
>
|
|
<polyline points="6 9 12 15 18 9" />
|
|
</svg>
|
|
);
|
|
}
|
|
|
|
export default function FaqPage() {
|
|
const [openIndex, setOpenIndex] = useState<number | null>(0);
|
|
|
|
return (
|
|
<div className="max-w-screen-md mx-auto px-4 md:px-6 py-16 md:py-20">
|
|
<div className="text-center">
|
|
<Badge tone="brand">FAQ</Badge>
|
|
<h1 className="text-display-sm md:text-display text-white mt-5">Frequently asked questions</h1>
|
|
<p className="text-gray-400 mt-4">Can't find what you're looking for? Sign in and reach out from your account.</p>
|
|
</div>
|
|
|
|
<div className="mt-12 divide-y divide-gray-800 border-t border-b border-gray-800">
|
|
{FAQS.map((item, i) => {
|
|
const open = openIndex === i;
|
|
return (
|
|
<div key={i}>
|
|
<button
|
|
onClick={() => setOpenIndex(open ? null : i)}
|
|
className="w-full flex items-center justify-between gap-4 py-5 text-left focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-indigo-500 rounded-lg"
|
|
aria-expanded={open}
|
|
>
|
|
<span className="text-white font-semibold text-sm md:text-base">{item.q}</span>
|
|
<ChevronIcon open={open} />
|
|
</button>
|
|
{open && (
|
|
<div className="text-gray-400 text-sm leading-relaxed pb-5 pr-8 animate-fade-in">{item.a}</div>
|
|
)}
|
|
</div>
|
|
);
|
|
})}
|
|
</div>
|
|
|
|
<div className="text-center mt-16">
|
|
<LinkButton href="/login" size="lg">Get started</LinkButton>
|
|
</div>
|
|
</div>
|
|
);
|
|
}
|