Docs Style Guide

Use the Python application, tests, deployment files, configuration, then existing technical docs as the evidence order. Do not infer behavior from the retained TypeScript MVP. Use TO_BE_CONFIRMED rather than inventing owners, contacts, URLs, controls, or dates.

Every page needs title, owner, SME, audience, tags, and last-updated metadata. Use sentence-case headings, one topic per page, Antora xref: links, source blocks for commands, and admonitions only for meaningful risk. Never publish credentials or Slack message content.

Before review, run npm ci and npm run build from docs, check xrefs, and search for template markers. When parsing, rendering, or redaction behavior changes, update the relevant documentation and application tests.