Skip to content

AI Infrastructure

Ambiguous DNA Letters Preserve Alternatives, Not Resolved AI Bases

For a genomics AI consumer that requires a resolved A, C, G or T at each position, a DNA ambiguity letter leaves that required base unresolved. An ambiguity-aware consumer may instead require the alternatives themselves. Under the declared DNA alphabet, R permits A or G, Y permits C or T, and N permits any of A, C, G or T. A compatible concrete string fits those sets; that fit alone supplies neither a resolved biological identity nor a probability.

Technical contentPublished Updated

01

Declare whether the consumer needs resolved bases or alternatives

Begin with the selected consumer's input requirement. Does it need one resolved DNA base at each position, or can it preserve and use a set of alternatives? A handoff that faithfully retains ambiguity can satisfy the second representation requirement while leaving the first unanswered. Calling both deliveries complete sequences does not settle that difference.

Here the alphabet is explicitly ordinary DNA, and the examples are unaligned fictional strings compared in their stated position order. NCBI's Entrez Sequences Quick Start, updated July 5, 2024, gives R as A or G, Y as C or T, and N as A, C, G or T. These letters identify permitted alternatives. The same chapter has a separate amino-acid table, where N means asparagine; applying that table to the stipulated DNA input would change the meaning.

NCBI's nucleotide FASTA submission guidance, updated June 18, 2025, uses IUPAC sequence symbols and identifies N for ambiguous characters. That supports the nucleotide-format context. It does not establish that a particular AI consumer accepts ambiguity, nor explain how that consumer represents it.

An ambiguity letter therefore needs to travel with its alphabet and position association. The receiving owner's declared input definition determines whether retaining the alternatives is sufficient or whether a separate resolution remains necessary.

References: [NCBI-CODES] [NCBI-FASTA]

02

DNA3: one three-position record permits 16 concrete strings

DNA3 is an original fictional handoff example. Its consumer expressly requires resolved DNA bases at three positions. The supplied record is RYN. Stipulate only the per-position code meanings: no additional restrictions connecting the positions, observations, frequencies or probability model are supplied.

Position 1 permits A or G. Position 2 permits C or T. Position 3 permits A, C, G or T. The position-by-position construction therefore permits 2 × 2 × 4 = 16 distinct concrete strings under these symbols alone.

The complete construction is small enough to inspect. With prefix AC, the strings are ACA, ACC, ACG and ACT. With prefix AT, they are ATA, ATC, ATG and ATT. With prefix GC, they are GCA, GCC, GCG and GCT. With prefix GT, they are GTA, GTC, GTG and GTT.

ACA is included because A fits R, C fits Y and A fits N. GTC is included because G fits R, T fits Y and C fits N. CCA is excluded because its first C is outside R's set, even though its other two positions fit.

The handoff still contains one record with three sequence positions. Sixteen counts the concrete strings not excluded by this representation. It does not count sixteen delivered observations, sixteen specimens or sixteen actual haplotypes. The construction describes what the symbols permit; no observed biological population has been specified.

References: [NCBI-CODES]

03

A permitted alternative has no assigned probability

Knowing that ACA belongs to the permitted set answers a membership question. It does not answer how likely ACA is. DNA3 supplies no weights for the sixteen strings, so assigning each a probability of 1/16 would add a uniform distribution that the handoff never supplied.

The multiplication in the construction is a count of combinations allowed by the stated position sets. It makes no claim that biological positions are statistically independent. Dependence, phase and the frequencies of real sequences cannot be inferred from the fact that every permitted combination can be written down.

Supplying ACA in place of RYN selects one of the sixteen possibilities and excludes the other fifteen from that delivered representation. The code table cannot justify that selection. A claim that ACA is the resolved input needs separate evidence identifying the resolution and its relationship to this record. If the base remains unresolved, retaining that state makes the outstanding requirement visible.

Likewise, a request for probabilities needs a defined probabilistic quantity and supporting model or evidence. Replacing the ambiguity letters with numerical weights does not make those weights source-supported merely because they sum to one.

04

Compatibility does not carry identity through a chain

For this explanation, two equal-length strings are position-by-position compatible when their permitted base sets overlap at every corresponding position. This is a declared set comparison, rather than a report of any particular search tool's behavior.

Consider RCA, ACA and GCA. RCA permits exactly ACA and GCA: its first position allows A or G, while its second and third positions are fixed at C and A.

RCA is compatible with ACA because the two permit ACA in common. RCA is also compatible with GCA because they permit GCA in common. But ACA and GCA conflict at the first position: one requires A and the other requires G. They have no concrete string in common.

Thus compatibility is not transitive. A chain connecting ACA to RCA and RCA to GCA cannot establish that all three identify one resolved sequence. The middle record preserves alternatives broad enough to overlap both endpoints; it does not remove the disagreement between those endpoints.

Literal text agreement is a separate comparison. Two records both written RYN retain the same symbolic alternatives under the same alphabet, but their identical text still does not select one of the sixteen strings or establish a shared biological origin. State whether a claimed match concerns identical text, equal alternative sets, overlapping sets or resolved identity.

References: [NCBI-CODES]

05

Compare what the handoff preserves for the selected input

Return to DNA3's resolved-base requirement. Offer A preserves RYN and its record and position associations. It preserves the supplied alternatives, but the required resolved bases remain unanswered. Offer B returns ACA and describes that output as resolved. B's extra specificity needs evidence of how the selection was established; writing only A, C, G and T does not provide that evidence.

Now change the declared requirement: the consumer expressly needs the original per-position alternative sets. Under that requirement, A retains the relevant distinctions. B's ACA loses them unless the delivery separately preserves them. The same two offers therefore answer different input requirements, and greater apparent specificity is not sufficient grounds to prefer B.

Identical letters are not the only way to preserve set meaning. An explicitly mapped representation containing {A,G}, then {C,T}, then {A,C,G,T}, associated with the same three positions, preserves DNA3's stipulated alternatives. That is a semantic comparison, not a recommendation for an encoder or a claim about installed model support. The actual consumer must have a declared interpretation for the supplied representation.

Transformations also need to account for lost distinctions. Replacing R with N broadens the first-position set from two alternatives to four. Keeping the record identifier and length would not repair that change. Conversely, an alternative-preserving transformation can change the literal text without changing the stipulated sets.

For the handoff decision, establish the required quantity, declared alphabet, record identity and position order, together with the meaning of any transformation or unresolved state. Connect the offer's description to evidence of what the receiving input actually retains. If resolution or probabilities are claimed, identify the separate support for those claims.

The related FASTQ guide addresses base-quality encoding, the SAM mapping-quality guide addresses a different error event, and the VCF guide distinguishes genotype calls from likelihood information. Those owners supply their own definitions; none turns DNA3's ambiguity letters into a resolved choice. This article resolves the representation question without asserting a downstream model-accuracy result.

06

Connect a separately needed physical cabling project

If the selected compute and storage equipment also needs physical cabling installation, Leviathan's Structured Cabling & Fiber Installation service provides a route to discuss agreed fiber and copper connections, endpoint labels and physical connection records.

Use the related service and project inquiry with a nonconfidential equipment outline, approved endpoints and routes, material responsibilities and required handoff records to establish scope and availability. That inquiry concerns physical installation. Bioinformatics, ambiguity resolution, data preparation and AI input acceptance remain with the appointed data and software specialists.

References: [L1]

07Sources

Primary sources

  1. [NCBI-CODES]
    NCBI Entrez Sequences Quick Start: nucleotide and amino-acid code tables, chapter updated July 5, 2024Checked 2026-10-21. Defines nucleotide R, Y and N and distinguishes the protein alphabet. DNA3 and the compatibility comparisons are original set constructions under those meanings, without biological observations or assigned probabilities.
  2. [NCBI-FASTA]
    NCBI GenBank: FASTA Format for Nucleotide Sequences, updated June 18, 2025Checked 2026-10-21. Nucleotide submission guidance supplies IUPAC and ambiguous-N format context. It does not define every parser's accepted input or a selected AI consumer's treatment of ambiguity.
  3. [L1]
    Leviathan Systems: Structured Cabling & Fiber InstallationChecked 2026-10-21. Agreed physical fiber and copper installation, endpoint labels and connection records support an equipment-cabling inquiry.

Contact

Does the selected equipment need physical cabling installation?

Share a nonconfidential equipment, endpoint, route and physical handoff outline to discuss installation scope, material responsibilities and availability.