<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>docs/agents/domain.md - fork/gdu @ ignore</title>
<meta name="description" content="docs/agents/domain.md in fork/gdu at ignore.">
<meta property="og:title" content="docs/agents/domain.md - fork/gdu @ ignore">
<meta property="og:description" content="docs/agents/domain.md in fork/gdu at ignore.">
<meta property="og:type" content="website">
<meta property="og:site_name" content="git.julia.blue">
<link rel="stylesheet" href="/css/style.css?v=62">
<script type="module" src="/js/main.js?v=62"></script>
</head>
<body>
<main data-ref="ignore" data-tip="98ee348e421e1e963e3d7978fde02a4b2e14f170">
<noscript>
  <div class="callout">
    <p>
      hey! this is a static git repo viewer. commit diffs, file history,
      older commits and other revisions won't load without javascript.
    </p>
    <p>
      you are still able to view source files on branch/tag tips,
      but the experience is degraded.
    </p>
  </div>
</noscript>
<header class="repo"><div>
<h1>fork/gdu</h1>
</div>
<pre class="clone">git clone https://git.julia.blue/fork/gdu</pre>
</header>
<p class="snapshot-commit"><span class="commit-author">Daniel Milde</span><span class="commit-message" data-commit="5ea284bc365a359eb212fbb75f39c257f31edf4e">docs: for contributors and agents (#626)</span><span class="snapshot-sha sha" data-commit="5ea284bc365a359eb212fbb75f39c257f31edf4e">5ea284b</span><time datetime="2026-08-17T19:58:50+02:00" title="2026-08-17 19:58:50 +0200">2026-08-17</time></p>
<header class="topbar"><details class="switcher"><summary>ignore</summary><div class="menu"><strong>branches</strong><a class="current" href="/fork/gdu/ref/ignore/">ignore</a><a href="/fork/gdu/ref/master/">master</a><a href="/fork/gdu/ref/subvolume/">subvolume</a><a class="all" href="/fork/gdu/refs">all refs →</a></div></details><nav class="crumbs"><a href="/fork/gdu/">gdu</a> / <a href="/fork/gdu/ref/ignore/tree/docs/">docs</a> / <a href="/fork/gdu/ref/ignore/tree/docs/agents/">agents</a> / <span class="cur">domain.md</span></nav>
<span class="view-stats"><span>2.0 KiB</span><span>51 lines</span></span><span class="actions"><a class="raw" href="/fork/gdu/raw/b548c538d606a65bde9bcd4ca3a458ec7c52cd9b/docs/agents/domain.md">raw</a></span></header>
<div class="markdown-view"><input type="radio" name="markdown-view" id="markdown-rendered" checked><label for="markdown-rendered">rendered</label><input type="radio" name="markdown-view" id="markdown-code"><label for="markdown-code">code</label><section class="readme rendered"><h1>Domain Docs</h1>
<p>How the engineering skills should consume this repo's domain documentation when exploring the codebase.</p>
<h2>Before exploring, read these</h2>
<ul>
<li><strong><code>CONTEXT.md</code></strong> at the repo root, or</li>
<li><strong><code>CONTEXT-MAP.md</code></strong> at the repo root if it exists — it points at one <code>CONTEXT.md</code> per context. Read each one relevant to the topic.</li>
<li><strong><code>docs/adr/</code></strong> — read ADRs that touch the area you're about to work in. In multi-context repos, also check <code>src/&lt;context&gt;/docs/adr/</code> for context-scoped decisions.</li>
</ul>
<p>If any of these files don't exist, <strong>proceed silently</strong>. Don't flag their absence; don't suggest creating them upfront. The <code>/domain-modeling</code> skill (reached via <code>/grill-with-docs</code> and <code>/improve-codebase-architecture</code>) creates them lazily when terms or decisions actually get resolved.</p>
<h2>File structure</h2>
<p>Single-context repo (most repos):</p>
<pre>/
├── CONTEXT.md
├── docs/adr/
│   ├── 0001-event-sourced-orders.md
│   └── 0002-postgres-for-write-model.md
└── src/
</pre>
<p>Multi-context repo (presence of <code>CONTEXT-MAP.md</code> at the root):</p>
<pre>/
├── CONTEXT-MAP.md
├── docs/adr/                          ← system-wide decisions
└── src/
    ├── ordering/
    │   ├── CONTEXT.md
    │   └── docs/adr/                  ← context-specific decisions
    └── billing/
        ├── CONTEXT.md
        └── docs/adr/
</pre>
<h2>Use the glossary's vocabulary</h2>
<p>When your output names a domain concept (in an issue title, a refactor proposal, a hypothesis, a test name), use the term as defined in <code>CONTEXT.md</code>. Don't drift to synonyms the glossary explicitly avoids.</p>
<p>If the concept you need isn't in the glossary yet, that's a signal — either you're inventing language the project doesn't use (reconsider) or there's a real gap (note it for <code>/domain-modeling</code>).</p>
<h2>Flag ADR conflicts</h2>
<p>If your output contradicts an existing ADR, surface it explicitly rather than silently overriding:</p>
<blockquote>
<p><em>Contradicts ADR-0007 (event-sourced orders) — but worth reopening because…</em></p>
</blockquote>
</section><div class="code-panel"><pre class="code src language-markdown"><span class="code-line"><a class="ln" id="L1" href="#L1">1</a><span class="code-text"><a-p>#</a-p> <a-tt>Domain Docs</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L2" href="#L2">2</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L3" href="#L3">3</a><span class="code-text">How the engineering skills should consume this repo&#39;s domain documentation when exploring the codebase.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L4" href="#L4">4</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L5" href="#L5">5</a><span class="code-text"><a-p>##</a-p> <a-tt>Before exploring, read these</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L6" href="#L6">6</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L7" href="#L7">7</a><span class="code-text"><a-p>- </a-p>**`CONTEXT.md`** at the repo root, or</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L8" href="#L8">8</a><span class="code-text"><a-p>- </a-p>**`CONTEXT-MAP.md`** at the repo root if it exists — it points at one `CONTEXT.md` per context. Read each one relevant to the topic.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L9" href="#L9">9</a><span class="code-text"><a-p>- </a-p>**`docs/adr/`** — read ADRs that touch the area you&#39;re about to work in. In multi-context repos, also check `src/&lt;context&gt;/docs/adr/` for context-scoped decisions.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L10" href="#L10">10</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L11" href="#L11">11</a><span class="code-text"><a-p>If any of these files don&#39;t exist, **proceed silently**. Don&#39;t flag their absence; don&#39;t suggest creating them upfront. The `/domain-modeling` skill (reached via `/grill-with-docs` and `/improve-codebase-architecture`) creates them lazily when terms or decisions actually get resolved.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L12" href="#L12">12</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L13" href="#L13">13</a><span class="code-text"><a-p>## </a-p><a-tt>File structure</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L14" href="#L14">14</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L15" href="#L15">15</a><span class="code-text"><a-p>Single-context repo (most repos):</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L16" href="#L16">16</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L17" href="#L17">17</a><span class="code-text"><a-p>```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L18" href="#L18">18</a><span class="code-text"><a-p>/</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L19" href="#L19">19</a><span class="code-text"><a-p>├── CONTEXT.md</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L20" href="#L20">20</a><span class="code-text"><a-p>├── docs/adr/</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L21" href="#L21">21</a><span class="code-text"><a-p>│   ├── 0001-event-sourced-orders.md</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L22" href="#L22">22</a><span class="code-text"><a-p>│   └── 0002-postgres-for-write-model.md</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L23" href="#L23">23</a><span class="code-text"><a-p>└── src/</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L24" href="#L24">24</a><span class="code-text"><a-p>```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L25" href="#L25">25</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L26" href="#L26">26</a><span class="code-text"><a-p>Multi-context repo (presence of `CONTEXT-MAP.md` at the root):</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L27" href="#L27">27</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L28" href="#L28">28</a><span class="code-text"><a-p>```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L29" href="#L29">29</a><span class="code-text"><a-p>/</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L30" href="#L30">30</a><span class="code-text"><a-p>├── CONTEXT-MAP.md</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L31" href="#L31">31</a><span class="code-text"><a-p>├── docs/adr/                          ← system-wide decisions</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L32" href="#L32">32</a><span class="code-text"><a-p>└── src/</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L33" href="#L33">33</a><span class="code-text"><a-p>    ├── ordering/</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L34" href="#L34">34</a><span class="code-text"><a-p>    │   ├── CONTEXT.md</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L35" href="#L35">35</a><span class="code-text"><a-p>    │   └── docs/adr/                  ← context-specific decisions</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L36" href="#L36">36</a><span class="code-text"><a-p>    └── billing/</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L37" href="#L37">37</a><span class="code-text"><a-p>        ├── CONTEXT.md</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L38" href="#L38">38</a><span class="code-text"><a-p>        └── docs/adr/</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L39" href="#L39">39</a><span class="code-text"><a-p>```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L40" href="#L40">40</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L41" href="#L41">41</a><span class="code-text"><a-p>## </a-p><a-tt>Use the glossary&#39;s vocabulary</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L42" href="#L42">42</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L43" href="#L43">43</a><span class="code-text"><a-p>When your output names a domain concept (in an issue title, a refactor proposal, a hypothesis, a test name), use the term as defined in `CONTEXT.md`. Don&#39;t drift to synonyms the glossary explicitly avoids.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L44" href="#L44">44</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L45" href="#L45">45</a><span class="code-text"><a-p>If the concept you need isn&#39;t in the glossary yet, that&#39;s a signal — either you&#39;re inventing language the project doesn&#39;t use (reconsider) or there&#39;s a real gap (note it for `/domain-modeling`).</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L46" href="#L46">46</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L47" href="#L47">47</a><span class="code-text"><a-p>## </a-p><a-tt>Flag ADR conflicts</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L48" href="#L48">48</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L49" href="#L49">49</a><span class="code-text"><a-p>If your output contradicts an existing ADR, surface it explicitly rather than silently overriding:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L50" href="#L50">50</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L51" href="#L51">51</a><span class="code-text"><a-p>&gt; </a-p>_Contradicts ADR-0007 (event-sourced orders) — but worth reopening because…_</span></span></pre></div></div>
</main>
</body>
</html>
