<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v3.0 20080202//EN" "https://jats.nlm.nih.gov/nlm-dtd/publishing/3.0/journalpublishing3.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" specific-use="SMUR" dtd-version="3.0" xml:lang="en">
<front>
<journal-meta>
<journal-id journal-id-type="publisher">EGUsphere</journal-id>
<journal-title-group>
<journal-title>EGUsphere</journal-title>
<abbrev-journal-title abbrev-type="publisher">EGUsphere</abbrev-journal-title>
<abbrev-journal-title abbrev-type="nlm-ta">EGUsphere</abbrev-journal-title>
</journal-title-group>
<issn pub-type="epub"></issn>
<publisher><publisher-name>Copernicus Publications</publisher-name>
<publisher-loc>Göttingen, Germany</publisher-loc>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.5194/egusphere-2026-2041</article-id>
<title-group>
<article-title>Bitfields encode what data knows about itself</article-title>
</title-group>
<contrib-group><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Ehrmann</surname>
<given-names>Steffen</given-names>
</name>
<xref ref-type="aff" rid="aff1">
<sup>1</sup>
</xref>
<xref ref-type="aff" rid="aff2">
<sup>2</sup>
</xref>
<xref ref-type="aff" rid="aff3">
<sup>3</sup>
</xref>
</contrib>
</contrib-group><aff id="aff1">
<label>1</label>
<addr-line>Institute of Biology, Leipzig University, Leipzig, Germany</addr-line>
</aff>
<aff id="aff2">
<label>2</label>
<addr-line>German Centre for Integrative Biodiversity Research (iDiv) Halle-Jena-Leipzig, Leipzig, Germany</addr-line>
</aff>
<aff id="aff3">
<label>3</label>
<addr-line>resonantia research gUG (haftungsbeschränkt), Leipzig, Germany</addr-line>
</aff>
<pub-date pub-type="epub">
<day>10</day>
<month>06</month>
<year>2026</year>
</pub-date>
<volume>2026</volume>
<fpage>1</fpage>
<lpage>26</lpage>
<permissions>
<copyright-statement>Copyright: &#x000a9; 2026 Steffen Ehrmann</copyright-statement>
<copyright-year>2026</copyright-year>
<license license-type="open-access">
<license-p>This work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this licence, visit <ext-link ext-link-type="uri"  xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link></license-p>
</license>
</permissions>
<self-uri xlink:href="https://egusphere.copernicus.org/preprints/2026/egusphere-2026-2041/">This article is available from https://egusphere.copernicus.org/preprints/2026/egusphere-2026-2041/</self-uri>
<self-uri xlink:href="https://egusphere.copernicus.org/preprints/2026/egusphere-2026-2041/egusphere-2026-2041.pdf">The full text article is available as a PDF file from https://egusphere.copernicus.org/preprints/2026/egusphere-2026-2041/egusphere-2026-2041.pdf</self-uri>
<abstract>
<p>Every observation a scientist produces carries implicit computational context, from uncertainty estimates and distribution parameters to quality flags and algorithmic decisions. Yet, in most cases, none of this travels when data crosses workflow boundaries. What arrives is typically a mean value. Everything else remains trapped in supplementary materials or institutional memory. Bitfields offer a direct solution. They are compact binary encodings that pack observation-level computational context into standard integer arrays, travel inside existing data formats, and decode on the receiving end without external dependencies. This is demonstrated through three linked workflows spanning livestock density modeling, ecological carrying capacity assessment, and socioeconomic intervention planning, where each project decodes its predecessor&apos;s bitfield and enriches it with new information. Statistical distributions, uncertainty metrics, and processing decisions accumulate across project boundaries rather than fragmenting at each handoff. The bitfield R package and a community-driven protocol repository provide the practical tooling. Because encoding integrates directly into analytical code, adoption requires no separate documentation step. Computational context is captured as a byproduct of the analysis itself.</p>
</abstract>
<counts><page-count count="26"/></counts>
</article-meta>
</front>
<body/>
<back>
</back>
</article>