import statusData from './tool-status.json'; /** * Where each tool does its work, for the status line beside the breadcrumbs. * Kept apart from tool-catalog.json because it ships on every page: the * search words, summaries and file types load only where they are used. * * Every processing claim was checked against the component's code, not its * copy: the site's privacy promise rests on it. A test keeps "server" in step * with the components that call /api. */ export interface ToolStatus { /** * local: the user's data stays in the browser. * server: it is sent to johnmcm.com (serverNote says what and why). * download: a program to download, nothing runs in the page. */ processing: 'local' | 'server' | 'download'; serverNote?: string; /** A large one-time download, such as an AI model. */ firstUse?: string; /** Any other request that says something about the user's data, such as map tiles. */ network?: string; /** * Outside services a server tool also sends the user's input to, as a clause * for llms.txt: its privacy line otherwise says only "this site's own server". */ thirdParty?: string; device: 'any' | 'desktop'; deviceNote?: string; /** No status line: a page that takes no input, such as a list of links. */ noStatus?: boolean; } const STATUS = statusData as Record; export function toolStatus(path: string): ToolStatus | undefined { return STATUS[path]; }