Metadata-Version: 2.4
Name: snodo
Version: 0.8.2
Summary: AI-native Software Development Lifecycle protocol engine
Author-email: The Snodo Authors <noreply@snodo.dev>
License:                                  Apache License
                                   Version 2.0, January 2004
                                http://www.apache.org/licenses/
        
           TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
        
           1. Definitions.
        
              "License" shall mean the terms and conditions for use, reproduction,
              and distribution as defined by Sections 1 through 9 of this document.
        
              "Licensor" shall mean the copyright owner or entity authorized by
              the copyright owner that is granting the License.
        
              "Legal Entity" shall mean the union of the acting entity and all
              other entities that control, are controlled by, or are under common
              control with that entity. For the purposes of this definition,
              "control" means (i) the power, direct or indirect, to cause the
              direction or management of such entity, whether by contract or
              otherwise, or (ii) ownership of fifty percent (50%) or more of the
              outstanding shares, or (iii) beneficial ownership of such entity.
        
              "You" (or "Your") shall mean an individual or Legal Entity
              exercising permissions granted by this License.
        
              "Source" form shall mean the preferred form for making modifications,
              including but not limited to software source code, documentation
              source, and configuration files.
        
              "Object" form shall mean any form resulting from mechanical
              transformation or translation of a Source form, including but
              not limited to compiled object code, generated documentation,
              and conversions to other media types.
        
              "Work" shall mean the work of authorship, whether in Source or
              Object form, made available under the License, as indicated by a
              copyright notice that is included in or attached to the work
              (an example is provided in the Appendix below).
        
              "Derivative Works" shall mean any work, whether in Source or Object
              form, that is based on (or derived from) the Work and for which the
              editorial revisions, annotations, elaborations, or other modifications
              represent, as a whole, an original work of authorship. For the purposes
              of this License, Derivative Works shall not include works that remain
              separable from, or merely link (or bind by name) to the interfaces of,
              the Work and Derivative Works thereof.
        
              "Contribution" shall mean any work of authorship, including
              the original version of the Work and any modifications or additions
              to that Work or Derivative Works thereof, that is intentionally
              submitted to Licensor for inclusion in the Work by the copyright owner
              or by an individual or Legal Entity authorized to submit on behalf of
              the copyright owner. For the purposes of this definition, "submitted"
              means any form of electronic, verbal, or written communication sent
              to the Licensor or its representatives, including but not limited to
              communication on electronic mailing lists, source code control systems,
              and issue tracking systems that are managed by, or on behalf of, the
              Licensor for the purpose of discussing and improving the Work, but
              excluding communication that is conspicuously marked or otherwise
              designated in writing by the copyright owner as "Not a Contribution."
        
              "Contributor" shall mean Licensor and any individual or Legal Entity
              on behalf of whom a Contribution has been received by Licensor and
              subsequently incorporated within the Work.
        
           2. Grant of Copyright License. Subject to the terms and conditions of
              this License, each Contributor hereby grants to You a perpetual,
              worldwide, non-exclusive, no-charge, royalty-free, irrevocable
              copyright license to reproduce, prepare Derivative Works of,
              publicly display, publicly perform, sublicense, and distribute the
              Work and such Derivative Works in Source or Object form.
        
           3. Grant of Patent License. Subject to the terms and conditions of
              this License, each Contributor hereby grants to You a perpetual,
              worldwide, non-exclusive, no-charge, royalty-free, irrevocable
              (except as stated in this section) patent license to make, have made,
              use, offer to sell, sell, import, and otherwise transfer the Work,
              where such license applies only to those patent claims licensable
              by such Contributor that are necessarily infringed by their
              Contribution(s) alone or by combination of their Contribution(s)
              with the Work to which such Contribution(s) was submitted. If You
              institute patent litigation against any entity (including a
              cross-claim or counterclaim in a lawsuit) alleging that the Work
              or a Contribution incorporated within the Work constitutes direct
              or contributory patent infringement, then any patent licenses
              granted to You under this License for that Work shall terminate
              as of the date such litigation is filed.
        
           4. Redistribution. You may reproduce and distribute copies of the
              Work or Derivative Works thereof in any medium, with or without
              modifications, and in Source or Object form, provided that You
              meet the following conditions:
        
              (a) You must give any other recipients of the Work or
                  Derivative Works a copy of this License; and
        
              (b) You must cause any modified files to carry prominent notices
                  stating that You changed the files; and
        
              (c) You must retain, in the Source form of any Derivative Works
                  that You distribute, all copyright, patent, trademark, and
                  attribution notices from the Source form of the Work,
                  excluding those notices that do not pertain to any part of
                  the Derivative Works; and
        
              (d) If the Work includes a "NOTICE" text file as part of its
                  distribution, then any Derivative Works that You distribute must
                  include a readable copy of the attribution notices contained
                  within such NOTICE file, excluding those notices that do not
                  pertain to any part of the Derivative Works, in at least one
                  of the following places: within a NOTICE text file distributed
                  as part of the Derivative Works; within the Source form or
                  documentation, if provided along with the Derivative Works; or,
                  within a display generated by the Derivative Works, if and
                  wherever such third-party notices normally appear. The contents
                  of the NOTICE file are for informational purposes only and
                  do not modify the License. You may add Your own attribution
                  notices within Derivative Works that You distribute, alongside
                  or as an addendum to the NOTICE text from the Work, provided
                  that such additional attribution notices cannot be construed
                  as modifying the License.
        
              You may add Your own copyright statement to Your modifications and
              may provide additional or different license terms and conditions
              for use, reproduction, or distribution of Your modifications, or
              for any such Derivative Works as a whole, provided Your use,
              reproduction, and distribution of the Work otherwise complies with
              the conditions stated in this License.
        
           5. Submission of Contributions. Unless You explicitly state otherwise,
              any Contribution intentionally submitted for inclusion in the Work
              by You to the Licensor shall be under the terms and conditions of
              this License, without any additional terms or conditions.
              Notwithstanding the above, nothing herein shall supersede or modify
              the terms of any separate license agreement you may have executed
              with Licensor regarding such Contributions.
        
           6. Trademarks. This License does not grant permission to use the trade
              names, trademarks, service marks, or product names of the Licensor,
              except as required for reasonable and customary use in describing the
              origin of the Work and reproducing the content of the NOTICE file.
        
           7. Disclaimer of Warranty. Unless required by applicable law or
              agreed to in writing, Licensor provides the Work (and each
              Contributor provides its Contributions) on an "AS IS" BASIS,
              WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
              implied, including, without limitation, any warranties or conditions
              of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
              PARTICULAR PURPOSE. You are solely responsible for determining the
              appropriateness of using or redistributing the Work and assume any
              risks associated with Your exercise of permissions under this License.
        
           8. Limitation of Liability. In no event and under no legal theory,
              whether in tort (including negligence), contract, or otherwise,
              unless required by applicable law (such as deliberate and grossly
              negligent acts) or agreed to in writing, shall any Contributor be
              liable to You for damages, including any direct, indirect, special,
              incidental, or consequential damages of any character arising as a
              result of this License or out of the use or inability to use the
              Work (including but not limited to damages for loss of goodwill,
              work stoppage, computer failure or malfunction, or any and all
              other commercial damages or losses), even if such Contributor
              has been advised of the possibility of such damages.
        
           9. Accepting Warranty or Additional Liability. While redistributing
              the Work or Derivative Works thereof, You may choose to offer,
              and charge a fee for, acceptance of support, warranty, indemnity,
              or other liability obligations and/or rights consistent with this
              License. However, in accepting such obligations, You may act only
              on Your own behalf and on Your sole responsibility, not on behalf
              of any other Contributor, and only if You agree to indemnify,
              defend, and hold each Contributor harmless for any liability
              incurred by, or claims asserted against, such Contributor by reason
              of your accepting any such warranty or additional liability.
        
           END OF TERMS AND CONDITIONS
        
           APPENDIX: How to apply the Apache License to your work.
        
              To apply the Apache License to your work, attach the following
              boilerplate notice, with the fields enclosed by brackets "[]"
              replaced with your own identifying information. (Don't include
              the brackets!)  The text should be enclosed in the appropriate
              comment syntax for the file format. We also recommend that a
              file or class name and description of purpose be included on the
              same "printed page" as the copyright notice for easier
              identification within third-party archives.
        
           Copyright [yyyy] [name of copyright owner]
        
           Licensed under the Apache License, Version 2.0 (the "License");
           you may not use this file except in compliance with the License.
           You may obtain a copy of the License at
        
               http://www.apache.org/licenses/LICENSE-2.0
        
           Unless required by applicable law or agreed to in writing, software
           distributed under the License is distributed on an "AS IS" BASIS,
           WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
           See the License for the specific language governing permissions and
           limitations under the License.
        
        Copyright 2026 The Snodo Authors <https://snodo.dev>
        
        Licensed under the Apache License, Version 2.0 (the "License");
        you may not use this file except in compliance with the License.
        You may obtain a copy of the License at
        
            http://www.apache.org/licenses/LICENSE-2.0
        
        Unless required by applicable law or agreed to in writing, software
        distributed under the License is distributed on an "AS IS" BASIS,
        WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
        See the License for the specific language governing permissions and
        limitations under the License.
        
Project-URL: Homepage, https://snodo.dev
Project-URL: Repository, https://github.com/snodo-dev/snodo
Project-URL: Issues, https://github.com/snodo-dev/snodo/issues
Keywords: ai,sdlc,agents,protocol,governance,llm
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Classifier: Topic :: Software Development
Classifier: Topic :: Software Development :: Quality Assurance
Requires-Python: >=3.12
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: snodo-core==0.8.2
Requires-Dist: snodo-tools==0.8.2
Requires-Dist: snodo-foundation==0.8.2
Requires-Dist: snodo-engine==0.8.2
Requires-Dist: snodo-mcp==0.8.2
Requires-Dist: pydantic>=2.12.0
Requires-Dist: pyyaml>=6.0
Requires-Dist: typer>=0.9.0
Requires-Dist: textual>=1.0.0
Requires-Dist: httpx>=0.27.0
Requires-Dist: GitPython>=3.1.0
Requires-Dist: litellm<2,>=1.80
Requires-Dist: rich>=13.0.0
Provides-Extra: dev
Requires-Dist: pytest==9.0.3; extra == "dev"
Requires-Dist: pytest-cov==7.1.0; extra == "dev"
Requires-Dist: pytest-timeout==2.4.0; extra == "dev"
Requires-Dist: hypothesis==6.155.2; extra == "dev"
Requires-Dist: ruff==0.15.16; extra == "dev"
Requires-Dist: radon>=6.0.0; extra == "dev"
Requires-Dist: import-linter==2.12; extra == "dev"
Provides-Extra: studies
Requires-Dist: marimo>=0.9.0; extra == "studies"
Requires-Dist: numpy>=1.24.0; extra == "studies"
Requires-Dist: matplotlib>=3.7.0; extra == "studies"
Requires-Dist: pandas>=2.0.0; extra == "studies"
Provides-Extra: docs
Requires-Dist: mkdocs<2,>=1.6.0; extra == "docs"
Requires-Dist: mkdocs-material<10,>=9.5.0; extra == "docs"
Dynamic: license-file

# snodo
[![CI](https://github.com/snodo-dev/snodo/actions/workflows/ci.yml/badge.svg)](https://github.com/snodo-dev/snodo/actions/workflows/ci.yml)
[![OpenSSF Scorecard](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fapi.scorecard.dev%2Fprojects%2Fgithub.com%2Fsnodo-dev%2Fsnodo&query=%24.score&label=openssf%20scorecard&suffix=%2F10&color=brightgreen)](https://scorecard.dev/viewer/?uri=github.com/snodo-dev/snodo)
[![OpenSSF Best Practices](https://www.bestpractices.dev/projects/14420/badge)](https://www.bestpractices.dev/projects/14420)
[![PyPI](https://img.shields.io/pypi/v/snodo)](https://pypi.org/project/snodo/)
[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue)](LICENSE)
[![Docs](https://img.shields.io/badge/docs-snodo.dev-2DD4BF)](https://docs.snodo.dev)
[![arXiv](https://img.shields.io/badge/arXiv-2606.20615-b31b1b)](https://arxiv.org/abs/2606.20615)
[![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.21967946.svg)](https://doi.org/10.5281/zenodo.21967946)
[![Coverage](https://codecov.io/gh/snodo-dev/snodo/branch/main/graph/badge.svg)](https://codecov.io/gh/snodo-dev/snodo)
[![Security Policy](https://img.shields.io/badge/security-policy-brightgreen)](SECURITY.md)

**AI-SDLC Protocol Engine** — a governance layer for AI-assisted software development.

![Three coder mechanisms — an in-process LLM client, a host CLI subprocess, and an opencode server in a Docker container — write into the same task worktree and converge on one identical gate and merge path.](https://raw.githubusercontent.com/snodo-dev/snodo/main/docs/assets/coder-paths.svg)

You define a *protocol* — a YAML specification of operational modes, validators
and constraints — and snodo executes tasks through it. Every task passes
validation gates before and after execution; a disagreement policy decides
whether the work proceeds, escalates to a human, or halts. What lands is what
your standards admitted, and the hash-chained audit log says why.

The coder is interchangeable and separate from the judge. An in-process LLM
client, a host CLI running on your own subscription, or a containerised server
all converge on the same gate and the same merge path.

**Preprint:** [*Specifying AI-SDLC Processes: A Protocol Language for Human-Agent Boundaries*](https://arxiv.org/abs/2606.20615) — arXiv:2606.20615.

## Project status

Actively-developed research implementation (beta).

| | |
|---|---|
| Code | ~39,400 lines across 5 packages (`snodo-core`, `snodo-tools`, `snodo-foundation`, `snodo-engine`, `snodo-mcp`) |
| Complexity | average cyclomatic complexity **A (4.9)** |
| Lint / architecture | `ruff` clean; package layering enforced in CI by `import-linter` |
| Python | 3.12 and 3.13 (CI matrix) |

The enforcement invariants — token integrity, capability boundaries,
non-overridable blockers, audit completeness — are verified by property-based
tests over randomized inputs.

## Install

```bash
pip install snodo
```

From source (a [`uv`](https://docs.astral.sh/uv/) workspace):

```bash
git clone https://github.com/snodo-dev/snodo.git
cd snodo
uv sync --all-extras
```

You need Python 3.12+, a model for the **validators** (always routed through
LiteLLM), and a **coder**, which need not be the same thing. Anthropic, OpenAI,
Google, OpenRouter, DeepSeek and Cloudflare Workers AI have built-in provider
configuration; any other OpenAI-compatible endpoint works by declaring a
provider block with `base_url` and `litellm_provider: openai` — Ollama, vLLM,
LM Studio, `llama.cpp`, self-hosted gateways. A local endpoint that needs no
key is not asked for one. `--coder opencode-cli` and `--coder agy` delegate
code generation to a CLI authenticated against your own subscription, so no
provider key is spent writing code. `--mock` needs nothing at all.

## Quickstart

```bash
snodo init --template solo                              # writes .snodo/protocol.yml
snodo config add anthropic sk-ant-...                   # store a provider key
snodo config set model claude-sonnet-4                  # default model
snodo ready                                             # is this project set up for the protocol?
snodo run "implement a hello world function"
```

A key already exported in your environment (`ANTHROPIC_API_KEY` and friends) is
auto-detected. To try the loop without spending anything, add `--mock`.

`snodo ready` is worth running first on an existing repository: it checks,
deterministically and without an LLM, whether every artefact the protocol
demands is **committed** — decision records, a resolvable test command, coder
configs, paths cited in criteria — and scores what is missing by how cheap it
is to fix. Task worktrees only see `HEAD`, so "present on disk" is not enough.

## Protocol language

| Concept | Description |
|---|---|
| **Mode** | An operational stage with a declared set of tools and validators. Disjoint tool sets enforce separation of duties — a producer cannot merge, a reviewer cannot edit. |
| **Validator** | An evaluation applied to a task. Has a `validator_type` (security, architecture, quality, conventions, planning…), an `evaluation_phase` (`pre_execute` or `post_execute`), and criteria — LLM prompt strings, or tooling config for deterministic checks. |
| **Disagreement policy** | How validator results combine: `unanimous`, `majority`, `quorum` (default 2/3), or `any`. |
| **Severity** | A result is `pass`, `warn` or `blocker`. A blocker halts regardless of policy. |
| **Constraint** | A rule enforced over execution artifacts through a predicate framework — deterministic, not judged. |
| **Transition** | A declarative event-to-mode mapping documenting intended handoffs. |

Seven templates ship with snodo:

| Template | Modes | For |
|---|---|---|
| `solo` | producer | A single developer with full access |
| `team` | producer, reviewer, planner | Three-mode team workflow |
| `2+n` | producer, reviewer | Paper reference configuration |
| `greenfield` | plan, decide, scaffold, build | A new project, from decisions to first code |
| `intent` | producer | Intent-driven authoring |
| `feature-warden` | producer | Feature development with a strict review gate |
| `bugfix-surgeon` | producer | Narrow, surgical defect work |

## Coders

The coder writes; snodo governs, gates, and records. Which one you pick does
not change what is enforced.

| `--coder` | Mechanism | Needs | Auth |
|---|---|---|---|
| `litellm` *(default)* | In-process completions via LiteLLM | built-in | provider API keys |
| `opencode-cli` | Host `opencode run` | `opencode` on PATH | `opencode auth login` |
| `agy` | Antigravity CLI (`agy -p`) | `agy` on PATH | `agy login` |
| `opencode` | OpenCode server in Docker over HTTP | Docker, `opencode:latest` | container env |
| `mock` | Deterministic stub | nothing | none |

Three things about them are worth knowing up front:

- **`-m` sets the *judging* model, not the coder's.** Validators and the
  classifier run on it. Host CLIs keep their own model catalogs; to pin a
  coder's model, namespace it — `--coder agy --model agy/gemini-2.5-pro`.
- **In-place coders own their commit.** `opencode`, `opencode-cli` and `agy`
  edit the worktree directly and commit, so post-execute validators judge the
  exact change. Any attempt to touch `.snodo/` halts as a blocker (ADR 027).
- **Selection order:** `--mock`, then `--coder`, then a mode's `coder:` field,
  then a model prefix (`agy/`, `opencode-cli/`, `claude`, `gpt`…), then
  `litellm`.

To add one, subclass `SubprocessCoderAdapter`, set `binary`, `model_prefix` and
`install_hint`, implement `_build_argv`, and register it in `CODER_REGISTRY`
(`snodo/coders/__init__.py`) — that alone exposes it to `--coder`, enables
prefix routing, and enrolls it in the adapter conformance suite.

## Commands

`snodo <command> --help` is authoritative; full reference at
[docs.snodo.dev](https://docs.snodo.dev).

| | |
|---|---|
| `init` | Scaffold `.snodo/` from a template |
| `run` | Execute a task, a plan (`--plan`), or a single wave (`--wave`). `--background`, `--resume`, `--retry`, `--from-pr`, `--interactive`, `--no-isolation` |
| `ready` | Score method-scaffolding readiness against the protocol |
| `plan` | `list`, `status`, `create`, `validate`, `add-wave`, `add-task`, `run`, `delete` |
| `status` / `mode` | Active session and mode; `mode change` to switch |
| `session` | `list`, `show`, `new`, `switch`, `delete`, `prune` |
| `authorize` | Adjudicate escalated disagreements and `set_model` proposals |
| `validate` | Check the protocol against the well-formedness rules |
| `audit verify` | Verify the hash chain |
| `job` / `logs` / `meta` | Background jobs: `list`, `status`, `logs`, `wait`, `cancel`; log streaming; usage |
| `task` / `worktree` | Task branches and the git worktrees used for isolation |
| `recon` | Fan out read-only agents to answer a question about the codebase |
| `models` / `config` | Model discovery; keys and settings |
| `serve` | Run the protocol as an MCP server (stdio or SSE) |
| `cloud` | `connect`, `disconnect`, `status` for audit sync |
| `dashboard` | TUI (`snop`) |
| `agent` / `sandbox` / `install` / `uninstall` | Agent memory; Docker sandbox; Claude Desktop MCP entries |

Plans are authored, not generated: `plan create` scaffolds one empty wave, and
you add waves and tasks (ids are `<wave>.<seq>_<name>`, e.g. `1.1_models`) or
edit `plan.yml` directly. A plan is re-verified on every load. See
[docs/runbooks/hand-authored-plan.md](docs/runbooks/hand-authored-plan.md).

## Architecture

- **Mode-based capability separation.** Each mode declares its tools. WF1
  well-formedness forbids an approval-conferring tool from appearing in two
  modes, so separation of duties is structural rather than advisory.
- **Validator gates with disagreement policies.** `pre_execute` validators run
  before the coder, `post_execute` after. Results combine under the declared
  policy; a blocker halts immediately and cannot be overridden.
- **JWT validation tokens.** Agreement issues a signed token, and mutating MCP
  tools require a valid one — validation is non-overridable at the capability
  boundary, not just in the engine.
- **Hash-chained audit log.** Append-only, tamper-evident, and the record of
  every governance decision and verification. Optionally synced to snodo cloud.
- **Session resumability.** State is checkpointed under `$SNODO_HOME/sessions/`.
  Resume with `snodo run --resume <session_id>`; escalations are adjudicated
  with `snodo authorize` and the session continues.
- **Coder adapter pattern.** The backend sits behind a `CoderAdapter`
  interface, so a new one plugs in without touching the engine.
- **LangGraph execution engine.** The protocol compiles to a `StateGraph` built
  dynamically from the YAML — any arrangement of modes and validators.
- **Modular packages.** `snodo-core` (kernel: config, predicates, sandbox) →
  `snodo-tools` (workspace, git, shell, code hosts) → `snodo-foundation`
  (infrastructure, compiler, protocols) → `snodo-engine` (engine, validators,
  coders) → `snodo-mcp` (MCP servers, recon, jobs), with the root `snodo`
  package as CLI and dashboard. Layering is enforced in CI by `import-linter`.

## Configuration

Configuration lives in `~/.snodo/config.yml` (`$SNODO_HOME` overrides the
location). Manage it with `snodo config` rather than editing by hand:

```bash
snodo config add anthropic sk-ant-...
snodo config set model deepseek/deepseek-v4
snodo config show
```

```yaml
model: deepseek/deepseek-v4                   # default for all roles

llm:
  coder:
    max_tokens: 64000
    temperature: 0.1
  validator:
    model: openai/@cf/google/gemma-4          # role-specific override
    max_tokens: 25000
  recon:
    num_agents: 2

engine:
  max_subtask_depth: 3
  max_session_age_days: 30
  token_ttl_seconds: 1200

providers:
  anthropic:
    api_key: sk-ant-...
    api_key_env: ANTHROPIC_API_KEY            # injected at runtime when a matching model runs
  ollama:
    base_url: https://ollama.com/v1
    api_key_env: OLLAMA_API_KEY
    litellm_provider: openai                  # route ollama/<model> through the OpenAI protocol

cloud:
  api_url: https://api.snodo.dev
  sync_enabled: true
```

`litellm_provider: openai` is what makes an arbitrary compatible endpoint work:
snodo rewrites `ollama/<model>` to `openai/<model>` and sends it to `base_url`.
Omit `api_key_env` for a local server that needs no key.

Read from the environment, never stored in the config file: `SNODO_HOME`,
`SNODO_TOKEN_SECRET` (HMAC secret for token signing; random per process by
default), `GITHUB_TOKEN` (for `--from-pr`), and any `<PROVIDER>_API_KEY`.

## Research

> Prifti, Y. (2026). *Specifying AI-SDLC Processes: A Protocol Language for
> Human-Agent Boundaries.* arXiv:2606.20615.
> <https://doi.org/10.48550/arXiv.2606.20615>

```bibtex
@misc{prifti2026snodo,
  title         = {Specifying AI-SDLC Processes: A Protocol Language for Human-Agent Boundaries},
  author        = {Prifti, Ylli},
  year          = {2026},
  eprint        = {2606.20615},
  archivePrefix = {arXiv},
  doi           = {10.48550/arXiv.2606.20615},
  url           = {https://arxiv.org/abs/2606.20615}
}
```

Empirical studies live in `studies/`:

```bash
uv sync --extra studies
make studies
```

Architecture decisions are recorded in
[docs/decisions/](docs/decisions/README.md).

## Contributing

See [CONTRIBUTING.md](CONTRIBUTING.md).

## License

Copyright (C) 2026 The snodo Authors. Licensed under the Apache License,
Version 2.0 — see [LICENSE](LICENSE).
