Document a solution.
Make it verifiable.

Enter a concise, distinctive title that identifies the historical cipher or solved document. This title will be used in the cumulative overview article if the solution is accepted.

Identify the original source precisely enough for an independent researcher to locate it. Include the holding institution or collection, shelf mark or catalogue identifier, folio or page numbers, and any relevant date, provenance, or document title. Explain if the source is privately held or otherwise restricted. Example: Swedish National Archives, Diplomatica Collection, SE/RA/0101/A/42, fols. 3r–5v, letter dated 14 May 1623.

Provide one complete, stable HTTP or HTTPS URL through which reviewers can inspect the images used for the transcription and solution. Link directly to the digitised manuscript, archive record, or image set whenever possible, and confirm that access does not require your personal login. Example: https://archive.example.org/records/SE-RA-0101-A-42

Give one complete bibliographic reference per line for prior publications, catalogue descriptions, earlier transcriptions or solution attempts, language resources, cryptographic methods, software, datasets, and other scholarly material used. Use one consistent citation format and include persistent links or identifiers where available. Example: Doe, J. (2025). Historical Ciphers. Stockholm University Press. https://doi.org/10.0000/example

Enter the complete, machine-readable transcription used in the analysis. Preserve the document's order and line divisions. State the notation used for illegible, damaged, deleted, inserted, or uncertain characters. Do not silently normalise ambiguous signs. Example convention: [?] = one illegible symbol, [ABC?] = uncertain reading, ⟦ABC⟧ = deleted text. Example lines: 001 | 17 42 09 [?] 31

Enter the complete deciphered text in the same line order as the ciphertext. Mark uncertain readings, editorial expansions, restorations, omissions, and unresolved passages consistently. Example convention: [word?] = uncertain reading, […] = unresolved passage, messag[e] = editorial expansion.

Use one row per aligned unit with three pipe-separated columns in the order ciphertext | key or operation | plaintext. Keep line identifiers where applicable. The alignment must allow reviewers to reproduce each transformation. Example: 001.01 | 17 | T

Use one mapping or rule per line. Provide the complete key, nomenclator, substitution table, codebook entries, transposition rule, algorithm, or other decoding procedure reconstructed from the evidence. Mark inferred or unresolved values explicitly. Examples: 17 = T [confirmed], 42 = H [inferred], 104 = THE, 58 = [?].

If an original historical key, codebook, nomenclator, or contemporary description survives, give its precise archival reference followed by a stable URL where available, then explain its relation to the reconstruction. Example: French National Archives, K 1234, fol. 7r; https://archives.example.org/K1234 — entries 17–42 correspond to the reconstructed table above. Leave this field empty only when no original key material is known.

Describe the complete decipherment workflow in a way that another researcher can reproduce. Include preparation and normalisation steps, assumptions, hypothesis generation, model or algorithm use, relevant parameters, intermediate checks, rejection criteria, and human validation. Explain how the evidence supports the proposed solution. The limit is 6,000 characters including spaces, used as a reproducible approximation of two A4 pages in a normal 12-point type size with standard margins.

List one system or tool per paragraph using the format Name and version; provider; access date; settings; role; human verification. Name all models, software, scripts, datasets, dictionaries, and external services used. Example: ExampleModel 2.1; Example AI Ltd.; accessed 2026-10-13; temperature 0; proposed candidate word divisions; every output checked against the ciphertext alignment by N. Researcher. Artificial Intelligence systems cannot be listed as authors or solvers.

Provide one complete HTTP or HTTPS URL for a public repository containing all material needed to inspect and independently verify the solution. Include the machine-readable transcription, plaintext, alignment, reconstructed key, method documentation, code or prompts, relied-upon tool outputs, and permitted derivative files. The URL must use one of the repository services approved by the Program Committee. Example: https://zenodo.org/records/12345678

List each unresolved issue separately using an identifier, its location, the uncertainty, and its effect on the interpretation. Example: U-01 | fol. 4r, line 7, symbol 12 | reading may be E or F | does not affect the sentence meaning. If nothing remains unresolved, enter exactly: No unresolved or ambiguous elements remain.

Use this optional field only for relevant historical, linguistic, technical, ethical, access, or licensing information that does not fit the required sections. Do not use it as a substitute for any required evidence or repository material.