voyd 0.1.0__tar.gz

voyd-0.1.0/.dockerignore

@@ -0,0 +1,48 @@
+# Without this file, `COPY . .` in the Dockerfile copies the whole working
+# directory into the image. Three of those things must never be in there:
+#
+#   .env    real credentials, baked into a layer that anyone who pulls the
+#           image can read. This is the one that matters.
+#   .venv   248MB of host-built binaries, copied *over* the venv `uv sync`
+#           just created one layer earlier -- so the image was both enormous
+#           and holding an environment linked against the wrong machine.
+#   .git    the full history, including anything ever committed to it.
+#
+# Everything the build actually needs is copied explicitly before this point
+# (pyproject.toml, uv.lock, README.md, voyd/) or is source that `COPY . .` is
+# there to pick up (voydfile.py, examples/, tests/, scanner/).
+
+# Secrets. Every suffixed variant, because the one that leaks is always the
+# one nobody thought to list.
+.env
+.env.*
+
+# Environments and build output -- recreated inside the image.
+.venv/
+dist/
+build/
+*.egg-info/
+
+# History and CI, which the runtime has no use for.
+.git/
+.github/
+.gitignore
+
+# Caches, none of which are portable across machines.
+__pycache__/
+*.py[cod]
+.ruff_cache/
+.pytest_cache/
+.mypy_cache/
+
+# Editor, agent and OS noise.
+.DS_Store
+.claude/
+.idea/
+.vscode/
+*.swp
+
+# Compose files: the image is a build artifact, not the orchestration.
+docker-compose*.yml
+Dockerfile
+.dockerignore

voyd-0.1.0/.github/workflows/policy-plan.yml

@@ -0,0 +1,55 @@
+name: policy-plan
+
+# This repository runs the check it ships. `voydfile.py` at the root is
+# the example policy, and a pull request that edits it gets the same
+# report a user's would -- which is the only way the action stays true:
+# a delivery mechanism nobody exercises rots exactly like a man page.
+#
+# No cluster and no secret here. The structural half needs neither, and
+# it is the half that carries `guard_removed` and `tenant_removed` --
+# the findings a reviewer is least equipped to spot in a diff.
+
+on:
+  pull_request:
+    paths:
+      - voydfile.py
+      - action.yml
+      - voyd/engine/plan.py
+      - voyd/wire/plan.py
+
+permissions:
+  contents: read
+  pull-requests: write
+
+concurrency:
+  group: policy-plan-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  plan:
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          # The action reads the policy in force out of git, so the base
+          # commit has to be in the clone. A shallow one would send it
+          # looking for an object that is not there and report the change
+          # as "the first voydfile", which is the wrong answer in the
+          # admitting direction.
+          fetch-depth: 0
+
+      - uses: ./
+        id: plan
+        with:
+          policy: voydfile.py
+
+      # The artifact is the half a terminal cannot give you: what the
+      # check said, tied to the digest of the exact policy files it said
+      # it about, kept after the runner is gone.
+      - uses: actions/upload-artifact@v4
+        if: always()
+        with:
+          name: voyd-plan-attestation
+          path: ${{ steps.plan.outputs.attestation }}
+          if-no-files-found: error

voyd-0.1.0/.github/workflows/test.yml

@@ -0,0 +1,168 @@
+name: test
+
+# Small on purpose. The suite is the foundation the rewrite stands on, not a
+# census, and it is split by what a test *needs* rather than by how many
+# there are -- a number in a comment is wrong one commit after somebody
+# writes it, which this repository has now been bitten by twice.
+#
+# Most of it needs no database. The per-document check, every decision in
+# the policy package, the wire codec and the custody rungs are pure, which
+# is what lets the same check run inside a proxy in the first place. What
+# needs a real `mongod` says so with `needs_mongo` and gets one, because
+# those claims are about queries and bytes and a mock would only prove the
+# mock was filtered.
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+concurrency:
+  group: test-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Start Atlas Local (mongod + mongot)
+        run: docker compose up -d --wait mongo
+
+      - name: Start the three-node replica set
+        # Fan-out is the one claim Atlas Local cannot test: it is a
+        # single-node set, so every routing assertion against it would pass
+        # by having nowhere else to send a read. This rig also enables
+        # `configureFailPoint`, which is how replication lag gets *caused*
+        # rather than waited for.
+        run: docker compose up -d --wait rs
+
+      - uses: astral-sh/setup-uv@v6
+        with:
+          python-version: "3.11"
+
+      - name: Sync
+        run: uv sync --all-extras
+
+      - name: Lint
+        run: uv run --no-sync ruff check voyd/ tests/ examples/ scanner/
+
+      - name: Types, because the wheel ships py.typed
+        # `voyd/py.typed` tells every downstream checker that these
+        # annotations are load-bearing. That is a promise made in the
+        # artifact, so it is checked here rather than trusted.
+        run: uv run --no-sync mypy
+
+      - name: The core needs no database
+        # If this step ever needs `services:`, the boundary has stopped being
+        # pure -- and a per-document check that cannot run without a database
+        # is one that cannot move to a wire, a browser, or anywhere else.
+        #
+        # Selected by marker rather than by filename, so a new pure file is
+        # covered the moment it is written and a new *impure* one has to
+        # declare itself `needs_mongo` to be skipped here. A list of paths
+        # silently stops covering whatever was added after it.
+        run: |
+          uv run --no-sync pytest -q -m 'not needs_mongo'
+
+      - name: The container is the deployment story, so it is built and run
+        # The deployment path is a claim like any other and gets the same
+        # treatment. It builds, it runs as a non-root uid, it answers
+        # --version, and its HEALTHCHECK command fails when there is
+        # nothing to be healthy about.
+        run: |
+          docker build -t voyd:ci .
+          test "$(docker run --rm --entrypoint id -u voyd:ci)" != "0"
+          docker run --rm voyd:ci --version
+          docker run --rm --entrypoint voyd-wire-health voyd:ci --port 1 \
+            && { echo "health passed with nothing listening"; exit 1; } \
+            || echo "health correctly failed"
+          # And it serves: a sidecar-shaped run, a client on the container's
+          # own loopback, an expired row refused and a delete become a
+          # revocation with every row still on disk.
+          docker run -d --name voyd-ci --network host voyd:ci \
+            --config voydfile.py --listen 27099 --metrics 27100 \
+            --target 127.0.0.1:27018
+          for _ in $(seq 30); do
+            docker exec voyd-ci voyd-wire-health && break || sleep 1
+          done
+          docker exec voyd-ci voyd-wire-health
+          docker rm -f voyd-ci
+
+      - name: The scanner runs on a machine with nothing installed
+        # It is the first thing a stranger runs and the only thing here that
+        # judges code nobody on this side has seen, so the claim that it
+        # needs no install is tested by uninstalling everything: a bare
+        # interpreter, no `uv sync`, no `pip install`, no PYTHONPATH.
+        run: python3 scanner/voyd_scan --strict voyd/ scanner/
+
+      - name: Importing voyd is the policy vocabulary and one driver
+        run: |
+          uv run --no-sync python -c "
+          import sys, voyd
+          assert 'guard' in voyd.__all__ and 'Engine' not in voyd.__all__
+          third = {m.split('.')[0] for m in sys.modules
+                   if not m.startswith(('_', 'voyd'))} - sys.stdlib_module_names
+          unexpected = third - {'pymongo', 'bson', 'gridfs', 'dns',
+                                'pymongocrypt', 'cryptography'}
+          assert not unexpected, f'importing voyd pulled {sorted(unexpected)}'
+          print('clean:', sorted(voyd.__all__))"
+
+      - name: The wheel builds, ships the proxy, and exposes no handle
+        run: |
+          uv build
+          uv venv /tmp/wheelcheck
+          VIRTUAL_ENV=/tmp/wheelcheck uv pip install dist/*.whl
+          /tmp/wheelcheck/bin/python -c "
+          import voyd, voyd.engine
+          from voyd import guard, deadline, revocable
+          # There is one way to use this and it is not an import. An
+          # application-facing handle re-exported from either module would
+          # be a second door onto the guarantee, added silently, and a
+          # wheel built from a dirty tree is where that would show up.
+          for name in ('Engine', 'Model'):
+              assert not hasattr(voyd, name), f'voyd.{name} is in the wheel'
+              assert not hasattr(voyd.engine, name), f'voyd.engine.{name} is in the wheel'
+          # And the product is *in* the wheel. The other half of the same
+          # assertion: a distribution shipping the vocabulary to write a
+          # policy and nothing that can serve one is not the artifact.
+          import voyd.wire, voyd.wire.proxy, voyd.wire.seal, voyd.wire.cascade
+          import voyd.wire.cli, voyd.wire.upstream, voyd.wire.identity
+          assert callable(voyd.wire.cli.main)
+          print('wheel: the policy vocabulary imports, the proxy ships')"
+          test -x /tmp/wheelcheck/bin/voyd-wire
+          /tmp/wheelcheck/bin/voyd-wire --help > /dev/null
+
+      - name: End to end, real driver through a real boundary
+        # Atlas Local is a real mongod and a real mongot, not a mock.
+        #
+        # `-m ""` clears the default deselection. The one `slow` test it
+        # lets in needs a cluster that has registered an embedding model:
+        # Atlas Local *declines* an `auto_embed` declaration rather than
+        # honouring it, and a run that accepted the fallback would assert
+        # the opposite of what it claims.
+        #
+        # So the secret is passed through if the repository has one and
+        # the test skips by name if it does not -- a fork's CI is green
+        # for a reason it can read, rather than red for one it cannot fix.
+        # `-rs` prints every skip, because a claim that quietly stopped
+        # being checked is the failure this suite exists to notice.
+        env:
+          VOYD_TEST_MONGO_URI: mongodb://localhost:27018/?directConnection=true
+          VOYD_ATLAS_URI: ${{ secrets.VOYD_ATLAS_URI }}
+        run: uv run --no-sync pytest -q -rs -m "" tests/
+
+      - name: The examples are the documentation, so they have to run
+        env:
+          VOYD_MONGO_URI: mongodb://localhost:27018/?directConnection=true
+        run: |
+          for f in examples/*.py; do
+            echo "--- $f"
+            uv run --no-sync python "$f" > /dev/null || exit 1
+          done
+
+      - name: Mongo logs on failure
+        if: failure()
+        run: docker compose logs mongo | tail -100

voyd-0.1.0/.gitignore

@@ -0,0 +1,234 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+#
+# ``.env`` alone is not enough: it leaves ``.env.local``, ``.env.production``
+# and every other suffixed variant committable, and the one that leaks is
+# always the one nobody thought to list. So the rule is every ``.env.*``,
+# which is the same fail-closed direction the read path takes, applied to the
+# repository. A tracked template would need an explicit ``!`` exception here.
+.env
+.env.*
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+
+# Local agent/editor state. Per-machine permissions and paths, not project
+# configuration -- committing it shares one person's local allowlist with
+# everybody who clones.
+.claude/
+
+# Written by `voyd-bench` when no --policy is given, so it appears
+# after any suite run that exercises the benchmark. Generated, never edited.
+.voyd_bench_policy.py

voyd-0.1.0/Dockerfile

@@ -0,0 +1,72 @@
+FROM python:3.11-slim
+
+COPY --from=ghcr.io/astral-sh/uv:latest /uv /bin/uv
+
+WORKDIR /app
+
+# Dependency metadata first, so a code change does not invalidate the layer
+# that resolved and installed the environment. README.md is here because
+# pyproject declares it as the package readme and the build reads it.
+COPY pyproject.toml uv.lock* README.md ./
+
+# The package itself, before `uv sync`, because this project is installed
+# rather than merely depended on -- hatchling needs `voyd/` present to build
+# the wheel it then installs.
+COPY voyd/ voyd/
+
+# The boundary needs a MongoDB driver and nothing else. `all` adds the one
+# extra there is -- `crypto`, for the `sealed()` and `--key-vault` path -- so
+# the image can serve a policy that seals a field without being rebuilt.
+RUN uv sync --extra all --frozen --no-dev || uv sync --extra all --no-dev
+
+# The policy file, the proxy and the examples. Last, because they change most
+# often and nothing above depends on them.
+COPY . .
+
+# Not root. The boundary opens one listening socket above 1024, reads a
+# policy file and forwards bytes; nothing it does needs privilege, and a
+# process that holds a database's front door is the last one that should
+# have any. `--chown` because `uv sync` wrote the venv as root.
+RUN useradd --uid 10001 --no-create-home --shell /usr/sbin/nologin voyd \
+    && chown -R 10001:10001 /app
+USER 10001
+
+# Where `uv sync` put the interpreter, so the entry point is the console
+# script rather than `uv run` -- which re-resolves the environment on every
+# container start and needs a writable cache it no longer has.
+ENV PATH="/app/.venv/bin:$PATH"
+
+# The wire boundary, not an HTTP service: what comes out of 27099 is the
+# MongoDB protocol. Mount your own `voydfile.py` over the example one and
+# point `--target` at your cluster.
+#
+# **Run it as a sidecar**, sharing a network namespace with the
+# application -- a Kubernetes pod, or `--network container:<app>`. That is
+# not a workaround, it is the strongest shape available: the application
+# reaches the boundary on `localhost`, nothing else on the network can
+# reach it at all, and there is no route around it to bypass.
+#
+# It is also the only shape that works everywhere. Without `--tls-cert`
+# the listener binds loopback, deliberately -- a plaintext boundary
+# reachable from a network would carry in the clear every document it had
+# just refused to serve. Publishing 27099 with `-p` happens to work on
+# Docker Desktop, whose forwarder runs inside the namespace, and does not
+# on Linux, whose DNAT targets the container's own address. Cross a
+# network with `--tls-cert`, not with a port mapping.
+#
+# 27100 is different and is meant to be published: `/metrics` for a
+# scrape and `/health` for a probe, both cross-pod by nature.
+EXPOSE 27100
+
+# Readiness, not liveness, and the distinction is the point: this asks
+# whether the *upstream* is reachable, because a bound socket answers yes
+# while the deployment behind it is gone. Orchestrators that read this
+# label get it for free; Kubernetes wants it spelled out in the manifest,
+# where the same URL is the readinessProbe.
+HEALTHCHECK --interval=10s --timeout=3s --start-period=5s --retries=3 \
+    CMD ["voyd-wire-health"]
+
+ENTRYPOINT ["voyd-wire"]
+CMD ["--config", "voydfile.py", "--listen", "27099", \
+     "--metrics", "27100", "--metrics-bind", "0.0.0.0", \
+     "--target", "host.docker.internal:27017"]

voyd-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Fabian Valle
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.