dagr-cli 2026.9.0__tar.gz

dagr_cli-2026.9.0/LICENSE

@@ -0,0 +1,287 @@
+
+                                 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 Maxim Zaks
+
+Licensed under the Apache License, Version 2.0 (the "License"); you may not use
+this software 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.
+
+
+---------------------------------------------------------------------------
+                     DAGR GENERATED OUTPUT EXCEPTION
+                              Version 1.0
+---------------------------------------------------------------------------
+
+In plain language: Dagr is a code generator. Code it emits for you is yours to
+use however you like. You do not have to ship this license with it, credit
+Dagr in it, or take on any other obligation because of it.
+
+The formal terms follow.
+
+1. Definitions.
+
+   "Generators" means the Dagr code generators, schema DSL, command-line tools
+   and supporting tooling distributed in this repository.
+
+   "Generated Output" means source code, data files, schemas, test fixtures and
+   documentation produced by running the Generators, including any portion of
+   the runtime source embedded in the Generators that the Generators copy,
+   verbatim or with substitution, into their output.
+
+2. Grant of exception.
+
+   As an exception to the conditions stated in Section 4 of the License, the
+   copyright holder grants You permission to reproduce, prepare derivative
+   works of, publicly display, publicly perform, sublicense and distribute
+   Generated Output, in Source or Object form, with or without modification,
+   for any purpose, without complying with any of the conditions in Section 4
+   of the License. In particular, You are not required to:
+
+     (a) include a copy of the License with Generated Output;
+     (b) reproduce the contents of any NOTICE file in Generated Output or in
+         any work incorporating it;
+     (c) carry prominent notices stating that You changed Generated Output; or
+     (d) attribute Dagr or the copyright holder in Generated Output, in any
+         work incorporating it, or in any documentation accompanying either.
+
+   Generated Output may be combined with works under any license, including
+   proprietary licenses, and may be distributed under terms of Your choosing.
+
+3. Patent grant preserved.
+
+   Nothing in this exception limits or revokes the grant of patent license in
+   Section 3 of the License. That grant continues to apply to the Generators
+   and to Generated Output, together with the termination conditions stated in
+   that Section.
+
+4. Warranty and liability.
+
+   Sections 7 and 8 of the License (Disclaimer of Warranty; Limitation of
+   Liability) apply to Generated Output as they apply to the Generators.
+
+5. Scope.
+
+   This exception applies only to Generated Output. The Generators themselves
+   remain licensed under the Apache License, Version 2.0 without exception;
+   copying, modifying and distributing the Generators is governed solely by
+   that License.
+
+6. Marking.
+
+   No marking of Generated Output is required. This exception is not a
+   registered SPDX License Exception, so there is no standard SPDX expression
+   for it; where a machine-readable marker is wanted, referencing this file by
+   name is sufficient.
+
+---------------------------------------------------------------------------

dagr_cli-2026.9.0/PKG-INFO

@@ -0,0 +1,140 @@
+Metadata-Version: 2.4
+Name: dagr-cli
+Version: 2026.9.0
+Summary: Dagr — data-graph binary serialization: schema DSL, code generators for Swift, Rust, TypeScript, Go, Mojo, Odin and Python, and receipt/compatibility tooling
+Author: Maxim Zaks
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://codeberg.org/mzaks/dagr
+Project-URL: Repository, https://codeberg.org/mzaks/dagr
+Project-URL: Changelog, https://codeberg.org/mzaks/dagr/src/branch/main/CHANGELOG.md
+Keywords: serialization,binary-format,code-generation,arena,graph,zero-copy
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Rust
+Classifier: Programming Language :: JavaScript
+Classifier: Programming Language :: Go
+Classifier: Topic :: Software Development :: Code Generators
+Classifier: Topic :: System :: Archiving
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: asn1
+Requires-Dist: asn1tools; extra == "asn1"
+Dynamic: license-file
+
+# Dagr
+
+**Dagr** ("Data Graph") is a binary serialization format for **data graphs** — object graphs
+with cycles and shared nodes — and a set of **code generators** that emit a complete,
+self-contained implementation of your schema for Swift, Rust, TypeScript, Go, Mojo, Odin and
+Python.
+
+You describe a graph once, in a small Python DSL:
+
+```python
+from dagr.dsl import DataGraph, Node, Enum, t, required
+from dagr.config import Library, Swift, Rust
+
+address_book = DataGraph("AddressBook", root_type=t.ref("Book"), node_types=[
+    Node("Book", fields=["people" >> t.ref("Person").array]),
+    Node("Person", fields=[
+        "name"    >> t.utf8 >> required,
+        "age"     >> t.u8,
+        "friends" >> t.ref("Person").array,      # cycles and shared nodes are fine
+        "status"  >> t.ref("Status"),
+    ]),
+    Enum("Status", ["single", "married", "widowed"]),
+])
+
+library = Library("AddressBook", schemas=[address_book], targets=[
+    Swift(out="gen/swift", features=["lazy", "path_query", "explain"]),
+    Rust(out="gen/rust", features=["lazy", "path_query"]),
+], wire_format_version=1)
+```
+
+`dagr build` then generates, per language, an **arena**-backed typed API (no reference
+cycles to leak, value-type handles), byte-exact serialization and restore, and optionally
+zero-allocation **lazy accessors**, **path queries** that read one field straight out of a
+buffer, and an **explain** tool that annotates every byte. The generated code has no runtime
+dependency — the runtime is emitted alongside it.
+
+## Why Dagr
+
+- **Graphs, not trees.** Cycles, back-references and shared nodes serialize naturally; the
+  arena model is what makes that safe in every target language.
+- **One schema, seven languages, identical bytes.** Swift, Rust, TypeScript, Go, Mojo, Odin
+  and Python read and write the same buffers; a cross-language test corpus of ~1000 fixture
+  permutations gates every change byte-for-byte.
+- **Four node layouts to choose from.** Regular (vtable, evolvable), packed (compact),
+  frozen (fixed-offset, O(1) reads) and frozen+packed — per node type, per schema
+  (`spec/16-choosing-a-node-layout.md`).
+- **More than graphs.** `DataSink` is an append-only record stream with the same type system
+  (logs, event streams, attestable audit trails); `SharedBuffer` is a fixed-layout overlay for
+  IPC, GPU and no-allocation embedded use, with seqlock, ring and double-buffer strategies.
+- **Tooling around the format.** Schema import from `.proto`, FlatBuffers, JSON Schema and
+  ASN.1; generation receipts and compatibility checks (`dagr check`); a browser schema editor
+  (`dagr ui`); self-contained HTML explorers for any buffer; git diff and three-way merge
+  drivers; an ImHex pattern exporter; a fuzzer; Arrow producers.
+
+## Install
+
+The tool is pure Python 3.9+ with no dependencies.
+
+```bash
+pip install dagr-cli            # or: uv tool install dagr-cli;  from a checkout: pip install -e .
+dagr init --name my_schema      # scaffolds schema.py + pyproject.toml
+dagr build                      # generates every target in Library.targets, writes dagr.lock.json
+dagr check                      # diffs the schema against the committed receipt
+```
+
+Compiling and running the generated code needs the respective toolchain (Swift 6.2, Rust
+1.85+, Node 20+, Go 1.22+, Mojo 1.0 via pixi, Odin). Generating never does.
+
+## Targets
+
+| Target | Arena + serde | Lazy | Path query | Explain | DataSink | SharedBuffer | Notes |
+|---|---|---|---|---|---|---|---|
+| Swift | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | primary target |
+| Rust | ✓ | ✓ | ✓ | ✓ (tooling) | ✓ | ✓ | primary target; `no_std` tiers, Arrow, fuzz, git tools |
+| TypeScript | ✓ | ✓ | – | – | ✓ | ✓ | HTML explorers are generated TS |
+| Go | ✓ | ✓ | – | – | ✓ | ✓ | direct builder; `io.Writer` sinks; `sync/atomic` SharedBuffer strategies |
+| Mojo | ✓ | ✓ | ✓ | – | ✓ | ✓ (+GPU) | |
+| Odin | ✓ | ✓ | – | – | ✓ | ✓ | |
+| Python | ✓ (reflective) | – | – | – | ✓ | ✓ (numpy zero-copy) | plus a native Arrow target |
+
+## Documentation
+
+- `spec/` — the numbered wire-format specification and design plans; start with
+  `spec/README.md`, then `spec/01-motivation-for-arenas.md`.
+- `docs/technical-feature-overview.md` — every feature with an engineering assessment.
+- `examples/` — worked examples: an attested audit log, JWT-shaped tokens, a structured log
+  sink, a package registry, stress graphs, a Swift↔Rust FFI demo.
+- `CONTRIBUTING.md` — repository layout, toolchains, and the generate → test loop.
+
+## Repository layout
+
+```
+dagr/        the Python package: DSL, config, CLI, code generators, importers, runtime, web UI
+spec/        numbered specification documents
+targets/     per-language runtimes, example packages and generated test crates
+tests/       test generators, runners, unit tests, fixture schemas and (generated) fixture corpora
+examples/    worked examples built with `dagr build`
+benchmarks/  micro-benchmarks
+site/        showcase site and spec-document generators
+docs/        prose documentation, blog posts, images
+```
+
+Generated code is not committed. After cloning, run `./regen_all.sh` once to emit every
+generated source, fixture and test suite (see `CONTRIBUTING.md`).
+
+## Status
+
+Dagr is used in production-style projects by its author and is versioned by CalVer
+(`2026.9.0`); the wire format is versioned separately per schema (`wire_format_version`) and
+checked by `dagr check`. Swift and Rust are the most complete targets; see `CHANGELOG.md` for
+what changed and `spec/30-deferred-codegen-gaps.md` for known gaps per target.
+
+## License
+
+Apache License 2.0 — see `LICENSE`.

dagr_cli-2026.9.0/README.md

@@ -0,0 +1,115 @@
+# Dagr
+
+**Dagr** ("Data Graph") is a binary serialization format for **data graphs** — object graphs
+with cycles and shared nodes — and a set of **code generators** that emit a complete,
+self-contained implementation of your schema for Swift, Rust, TypeScript, Go, Mojo, Odin and
+Python.
+
+You describe a graph once, in a small Python DSL:
+
+```python
+from dagr.dsl import DataGraph, Node, Enum, t, required
+from dagr.config import Library, Swift, Rust
+
+address_book = DataGraph("AddressBook", root_type=t.ref("Book"), node_types=[
+    Node("Book", fields=["people" >> t.ref("Person").array]),
+    Node("Person", fields=[
+        "name"    >> t.utf8 >> required,
+        "age"     >> t.u8,
+        "friends" >> t.ref("Person").array,      # cycles and shared nodes are fine
+        "status"  >> t.ref("Status"),
+    ]),
+    Enum("Status", ["single", "married", "widowed"]),
+])
+
+library = Library("AddressBook", schemas=[address_book], targets=[
+    Swift(out="gen/swift", features=["lazy", "path_query", "explain"]),
+    Rust(out="gen/rust", features=["lazy", "path_query"]),
+], wire_format_version=1)
+```
+
+`dagr build` then generates, per language, an **arena**-backed typed API (no reference
+cycles to leak, value-type handles), byte-exact serialization and restore, and optionally
+zero-allocation **lazy accessors**, **path queries** that read one field straight out of a
+buffer, and an **explain** tool that annotates every byte. The generated code has no runtime
+dependency — the runtime is emitted alongside it.
+
+## Why Dagr
+
+- **Graphs, not trees.** Cycles, back-references and shared nodes serialize naturally; the
+  arena model is what makes that safe in every target language.
+- **One schema, seven languages, identical bytes.** Swift, Rust, TypeScript, Go, Mojo, Odin
+  and Python read and write the same buffers; a cross-language test corpus of ~1000 fixture
+  permutations gates every change byte-for-byte.
+- **Four node layouts to choose from.** Regular (vtable, evolvable), packed (compact),
+  frozen (fixed-offset, O(1) reads) and frozen+packed — per node type, per schema
+  (`spec/16-choosing-a-node-layout.md`).
+- **More than graphs.** `DataSink` is an append-only record stream with the same type system
+  (logs, event streams, attestable audit trails); `SharedBuffer` is a fixed-layout overlay for
+  IPC, GPU and no-allocation embedded use, with seqlock, ring and double-buffer strategies.
+- **Tooling around the format.** Schema import from `.proto`, FlatBuffers, JSON Schema and
+  ASN.1; generation receipts and compatibility checks (`dagr check`); a browser schema editor
+  (`dagr ui`); self-contained HTML explorers for any buffer; git diff and three-way merge
+  drivers; an ImHex pattern exporter; a fuzzer; Arrow producers.
+
+## Install
+
+The tool is pure Python 3.9+ with no dependencies.
+
+```bash
+pip install dagr-cli            # or: uv tool install dagr-cli;  from a checkout: pip install -e .
+dagr init --name my_schema      # scaffolds schema.py + pyproject.toml
+dagr build                      # generates every target in Library.targets, writes dagr.lock.json
+dagr check                      # diffs the schema against the committed receipt
+```
+
+Compiling and running the generated code needs the respective toolchain (Swift 6.2, Rust
+1.85+, Node 20+, Go 1.22+, Mojo 1.0 via pixi, Odin). Generating never does.
+
+## Targets
+
+| Target | Arena + serde | Lazy | Path query | Explain | DataSink | SharedBuffer | Notes |
+|---|---|---|---|---|---|---|---|
+| Swift | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | primary target |
+| Rust | ✓ | ✓ | ✓ | ✓ (tooling) | ✓ | ✓ | primary target; `no_std` tiers, Arrow, fuzz, git tools |
+| TypeScript | ✓ | ✓ | – | – | ✓ | ✓ | HTML explorers are generated TS |
+| Go | ✓ | ✓ | – | – | ✓ | ✓ | direct builder; `io.Writer` sinks; `sync/atomic` SharedBuffer strategies |
+| Mojo | ✓ | ✓ | ✓ | – | ✓ | ✓ (+GPU) | |
+| Odin | ✓ | ✓ | – | – | ✓ | ✓ | |
+| Python | ✓ (reflective) | – | – | – | ✓ | ✓ (numpy zero-copy) | plus a native Arrow target |
+
+## Documentation
+
+- `spec/` — the numbered wire-format specification and design plans; start with
+  `spec/README.md`, then `spec/01-motivation-for-arenas.md`.
+- `docs/technical-feature-overview.md` — every feature with an engineering assessment.
+- `examples/` — worked examples: an attested audit log, JWT-shaped tokens, a structured log
+  sink, a package registry, stress graphs, a Swift↔Rust FFI demo.
+- `CONTRIBUTING.md` — repository layout, toolchains, and the generate → test loop.
+
+## Repository layout
+
+```
+dagr/        the Python package: DSL, config, CLI, code generators, importers, runtime, web UI
+spec/        numbered specification documents
+targets/     per-language runtimes, example packages and generated test crates
+tests/       test generators, runners, unit tests, fixture schemas and (generated) fixture corpora
+examples/    worked examples built with `dagr build`
+benchmarks/  micro-benchmarks
+site/        showcase site and spec-document generators
+docs/        prose documentation, blog posts, images
+```
+
+Generated code is not committed. After cloning, run `./regen_all.sh` once to emit every
+generated source, fixture and test suite (see `CONTRIBUTING.md`).
+
+## Status
+
+Dagr is used in production-style projects by its author and is versioned by CalVer
+(`2026.9.0`); the wire format is versioned separately per schema (`wire_format_version`) and
+checked by `dagr check`. Swift and Rust are the most complete targets; see `CHANGELOG.md` for
+what changed and `spec/30-deferred-codegen-gaps.md` for known gaps per target.
+
+## License
+
+Apache License 2.0 — see `LICENSE`.

dagr_cli-2026.9.0/dagr/__init__.py

@@ -0,0 +1,10 @@
+"""Dagr — data-graph binary serialization: schema DSL, code generators, and tooling.
+
+Public schema-authoring surface: ``dagr.dsl`` and ``dagr.config``.  Everything under
+``dagr.codegen`` is the generator implementation; ``dagr.runtime`` is the reflective
+pure-Python runtime that generated Python modules import.  This module deliberately
+imports nothing so that the shipped copy of the package inside a ``dagr build --target
+python`` output stays self-contained.
+"""
+
+__version__ = "2026.9.0"