Setrya
Test whether your AI assistant can still reveal a customer's deleted information.
A customer deletes their onboarding notes. Yesterday’s background job finishes and puts their hostname back into the support handoff. Setrya catches this by asking the assistant what it can still tell two teammates. On a pull request, the GitHub Action posts the verdict and links to the store reads and answers behind it. Setrya erasure drill on GitHub Marketplace
Get your first PR verdict
Start in the root of your GitHub repository with Python 3.11+ on macOS or Linux. These commands create a branch, a virtual environment and two files for your PR. Use an unused starter directory and workflow path. The sample uses synthetic data and needs no application credentials.
git switch -c try-setrya
python3 -m venv .venv-setrya
. .venv-setrya/bin/activate
python -m pip install setrya==1.1.0
setrya init --output setrya-case
setrya doctor --starter setrya-case/test_erasure.py --mode deletion
mkdir -p .github/workflows
curl -fsSL https://raw.githubusercontent.com/davidahma/setrya/v1.1.0/docs/examples/first-pr/setrya.yml -o .github/workflows/setrya.yml
git add setrya-case/test_erasure.py .github/workflows/setrya.yml
git commit -m "Run the Setrya deletion check on pull requests"
git push -u origin HEAD
Open a pull request. In Checks → Setrya erasure, the sample should report PASS · READY_FOR_REVIEW. The workflow tests deletion, saves the receipt as setrya-receipt and comments on same-repository PRs. A green sample tells you the CI wiring works. See a real PR comment · First-PR workflow and offline replay
Test your application
In setrya-case/test_erasure.py, replace the sample imports with your own fixture.
-from setrya.examples.workspace import SIMPLE as CASE
-from setrya.examples.workspace import open_fixture
+from helpdesk_fixture import CASE, open_fixture
For example, seed a test customer’s depot code and a team dispatch day. Have inspect read the note from your store, read ask your authenticated answer route and erase call your deletion operation. Push the fixture and its test dependencies. The same PR now checks whether the depot code disappears and the dispatch day survives. Start with deletion and switch to late-write once you can pause and release the worker that captured the old note. Runnable help-desk fixture and wiring instructions · Help-desk example PR
Try the broken and fixed versions
To see the worker race locally, run the bundled workspace demo. Two teammates reopen the same handoff after a customer asks for deletion.
python -m pip install setrya==1.1.0
setrya demo --output workspace
setrya replay workspace/guarded
| After the delayed writer finishes | Broken application | Guarded application |
|---|---|---|
| Support lead asks for the deleted customer’s hostname | cobalt-bridge.example |
No matching note |
| Account manager asks the same question in the same workspace | cobalt-bridge.example |
No matching note |
| Both ask for the team’s next launch date | October 18 |
October 18 |
| Engineering verdict | FAIL | PASS |
The broken worker restores a summary it captured before deletion. The fixed worker compares its captured source revisions with the surviving notes before it can publish. The launch date tests a second failure mode. Wiping the whole handoff would remove the hostname and also destroy information the team still needs.
The guarded receipt reports PASS · OPEN_ITEMS. The store and endpoint checks passed. A fictional provider still has a configuration-only record. The case owner can see who must follow up and when. Use setrya replay workspace/guarded --case-review to gate on that obligation too. Download the signed workspace examples · Verify the signer
What a receipt covers
| Result | What the reviewer can conclude |
|---|---|
PASS · exit 0 |
The declared store and serving checks passed for the tested callers and mode. |
FAIL · exit 1 |
A read found a residual or showed that required information was lost. |
ERROR · exit 2 |
The fixture or evidence could not be processed reliably. |
NOT TESTED · exit 3 |
A required observation was missing, such as a direct cache read or a confirmed worker checkpoint. |
Setrya can inspect declared keys, logged copies and synthetic markers within the scanners’ configured scope. A paraphrase can lose a marker, so ask about the fact itself. Provider configuration and retention dates become separate review items. The receipt names the evidence the application supplied and the scope the test exercised. v3 schema and compatibility · SDK integrations and coverage
Two more ways to use it
- Reopen a LangGraph investigation. Two analysts ask about a quarantined laptop after a shared checkpoint is rewritten. A scoped canary also finds an export that lost its subject tag. Install
'setrya[erasure]'and runsetrya demo analyst --output investigation. Investigation drill · Independent Graphiti trial - Start from an existing discovery finding. The experimental Amazon Macie integration accepts a finding pointer and an application-owned mapping. It correlates the source revision with the stores, workers and routes in the test, then returns the evidence to the originating case. The bundled gap case names the unread cache and its owner. No AWS account is needed to run it. Discovery trial · Mapping and approval
Setrya also tests access revocation, search freshness, late cache fills and tenant offboarding. Other drills and Python SDK · Release notes · Apache 2.0 license
Connect an app or review a completed request
Start with the stack your team already runs. The LangGraph guide tests saved memory. The Langfuse guide checks stored traces. For a TypeScript or other HTTP service, declare authenticated reads, deletion and direct store observations in YAML. Stack starters and HTTP cases
For generated answers, Setrya defaults to three reads per caller, question and stage. A single observed disclosure fails the drill. A lexical miss alone leaves absence uncertain. The receipt records sample counts and judge coverage. Verdict rules
For a completed deletion ticket, use the read-only observer to check journalled keys. A weekly sample reports the residual rate with an interval and accounts for unknown cases. To give a customer a plain-language summary of a replayed drill, run setrya receipt render workspace/guarded --audience customer --case-id N-204. Casework commands and permissions
Metadata
Release files for setrya 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| setrya-1.1.0.tar.gz | 589.7 kB | With provenance | Details for setrya-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| setrya-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for setrya-1.1.0-py3-none-any.whl |
Total release size: 949.2 kB
Release files / setrya-1.1.0.tar.gz
| Download URL | setrya-1.1.0.tar.gz |
|---|---|
| Size | 589.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
314517dad88af613a379f32e459aa6bea53df97c202db72c3b238c999e62fcc5
|
|
BLAKE2b-256 checksum How to use checksums |
fb7bce69e40cea166a9b230b0413b681e8a08ae1b55f1b549dd89c5619e88f22
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 22, 2026.
Transparency logRelease files / setrya-1.1.0-py3-none-any.whl
| Download URL | setrya-1.1.0-py3-none-any.whl |
|---|---|
| Size | 359.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2b833c178c5515403dc1f0f6a1bf30fbb545258a95e02faeca64274f5cc8fcd4
|
|
BLAKE2b-256 checksum How to use checksums |
44377bf0047b88b5469995799b72ca7b69748ce576f42733a678c1be2d193799
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 22, 2026.
Transparency logSecurity for setrya 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for setrya-1.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 22, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.