Flightcase evidence can include facility layout, logs, commands, operational behavior, and safety incidents. Treat every issue as potentially sensitive.

Report security issues privately to the maintainers. Do not open public issues for exploitable bugs.

• Relays and caches must not decode robot payloads.
• Sealed incident manifests must be signed.
• Authorization is prefix-scoped and track-class aware.
• Replay defaults to isolated domains and must block control topics unless explicitly allowed.
• Clock domains must be explicit; false precision is a security and safety issue.