(registered 2026-11-18, last updated 2026-11-18) Media type name: application Media subtype name: vnd.codynamicslab.latch Required parameters: N/A Optional parameters: N/A Encoding considerations: binary The format is a binary container. It must be transferred without modification, using base64 or similar where a transport is not 8-bit or binary safe. Security considerations: Active content: The format contains no executable or active content. It holds JSON records and plain text. Readers must not execute or automatically render anything inside a package. Quoted text and answer text may contain instructions aimed at AI models that later read them, so systems that pass package text to a language model should treat it as untrusted data, not as instructions. Privacy and integrity: Packages do not contain source documents, but they do contain short verbatim quotes, query text, and optionally file names, any of which can be confidential (for example legal or medical information). They need both privacy and integrity protection. Services provided by the format: The archive is encrypted with AES-256-GCM. The key is derived from a passphrase or organization key using Argon2id. The GCM tag authenticates the ciphertext and the cleartext header. Each package is signed with Ed25519 by the device that created it. The manifest lists a SHA-256 digest for every member, and readers must check the tag, the signature, and every digest before using any content. The cleartext header holds only format metadata, never quotes, queries, or document content. Anyone with the passphrase or key can read the contents, so keys must be protected and shared separately from the file. Use of existing formats: The header and the archive members are JSON, and the security considerations of RFC 8259, Section 12 apply. Readers should limit header and member sizes, reject duplicate keys and malformed input, and treat all fields as untrusted until the signature and GCM tag have been verified. The format does not use JSON extensibility to carry executable content. Unknown fields must be ignored, not interpreted. Compression: The archive is compressed with Zstandard, and the security considerations of RFC 8878, Section 7 apply. Readers should enforce limits on decompressed size and member count to protect against decompression bombs, and should check sizes listed in the manifest before extracting. Container format: The decrypted payload is a tar archive. Readers must reject absolute paths, ".." path segments, symbolic links, hard links, and device files, so that extraction cannot write outside the target directory or overwrite existing files. Readers must reject any member not listed in the signed manifest, and any member whose SHA-256 digest does not match the manifest. Links: The format does not include links that must be fetched to interpret it. Source documents are referenced by SHA-256 digest, not by URL, and the recipient verifies quotes against their own copy of those documents. Readers must not fetch remote resources while processing a package. Additional note: A verified quote proves the quoted text exists at the stated location. It does not prove that the claim's interpretation of that text is correct. Readers should review each claim against its source. Interoperability considerations: Files begin with the 8-byte magic number "LATCH2" followed by two null bytes, then a 4-byte little-endian header length and a UTF-8 JSON header. The header field package_type is "latch", which distinguishes this type from application/vnd.codynamicslab.latchdoc, which shares the same magic number and envelope. The header carries a spec_version field. Readers must reject files with an unknown major version and must ignore unknown fields. A finding package does not contain source documents. It references them by SHA-256 digest, and quote offsets refer to extracted text that can be supplied by a matching .latchdoc package or by the recipient's own copy. Version 1 files with the .latch extension use the magic number "LATCH1" and are a different, legacy document bundle. They are not compatible with this registration's format, though a reader may support both. Published specification: https://www.codynamicslab.com/docs/formats/latch Applications which use this media: CoDynamics Lab document software, including the LATCH document appliance and its verification tools. The format is used to send the result of a document search, with the query, every hit, the verified quotes, and the audit record, to a partner, co-counsel, expert, or referring physician, who can check each quote against their own copy of the source documents. Fragment identifier considerations: N/A Restrictions on usage: None Additional information: 1. Deprecated alias names for this type: N/A 2. Magic number(s): 4C 41 54 43 48 32 00 00 at offset 0 ("LATCH2" followed by two null bytes). Shared with application/vnd.codynamicslab.latchdoc; the header field package_type distinguishes them. 3. File extension(s): .latch 4. Macintosh file type code: N/A 5. Object Identifiers: N/A General Comments: This is the companion to the application/vnd.codynamicslab.latchdoc registration submitted on November 10, 2026. The two types share an envelope and magic number and are distinguished by the package_type header field. A .latch finding package references source documents by SHA-256 digest and does not contain them. The published specification is version 2.0 (draft); legacy version 1 files use a different magic number ("LATCH1"). Person to contact for further information: 1. Name: Mike Holford 2. Email: mike&codynamicslab.com Intended usage: COMMON Author/Change controller: CoDynamics Lab Corporation