Repository navigation
Releases
Setrya 1.5.0 · Verify branches, vendor stores and destroyed keys
Setrya now checks what survives after an application deletes the original data. Run setrya demo branches to see a pre-erasure SQLite fork and restore keep serving a record the source database has already deleted.
- Review residuals. Summaries count scanner findings separately, identify lost control data, and show paths recovered from surviving Git objects.
- Check branches and backups. Record store ancestry, inspect declared forks and recheck disclosed restore windows.
- Compare vendor behavior. The signed pgvector, LangGraph Store, and Mem0 fixture receipts record the measured surfaces. The Mem0 fixture detects retained text in the local history store.
- Connect agents and tracing. The MCP server offers local replay and review by default. An OTLP importer collects copy observations using the published event schema.
- Verify key destruction. The AWS KMS observer ties an independently pinned ciphertext inventory to key-destruction evidence and records crypto-erasure separately from physical deletion.
Install with python -m pip install setrya==1.5.0. The first-PR workflow is pinned to this release's commit. The linked fixture reports replay offline.
Setrya 1.4.0 · Verify retained Git objects and attribute late writes
A history rewrite can remove every reference to a note while leaving its bytes in the local Git object store. Setrya now checks those objects too, including loose and packed data. A configured remote remains an open follow-up. The scanner records include patterns, and doctor names common file types outside those patterns.
A recorded late write can now identify its agent turn when the evidence confirms the same copy and exact revision. The OpenAI Agents and Claude Agent SDK wrappers supply turn context. Summaries show the number of control answers, distinguish a deletion from a rewrite and link the verdict to its evidence digest.
The first-PR workflow download pins the commit behind this release. The SDK extras install from qualified minor versions, with a weekly job that tests the latest upstream packages independently.
python -m pip install setrya==1.4.0
setrya demo memory-files --output memory-review
setrya receipt summary memory-review/broken --audience reviewer --format mdSetrya 1.3.0 · Agent turns, memory files and Git history
A deleted support note can survive in an assistant’s memory file, a commit, or the inputs already held by a background worker. The new memory-file demo shows all three. The guarded run removes the note, keeps the shared deployment date and records a provider follow-up.
- Scan opted-in working files, local Git history and reflogs, and Turso AgentFS file tables.
- Record which turn handled a copy and the source revisions that fed a derived write. Verify local and collected journals with
setrya journal verify. - Start a LangGraph/Postgres case with checkpoint, memory and scoped SQL reads. Doctor names missing bindings and points to the relevant fixture lines.
- Replay historical v3 receipts alongside v3.1 evidence. The new evidence groups repeated answers and records lexical-only judging where applicable. The Action updates its existing PR comment after an upgrade.
python -m pip install setrya==1.3.0
setrya demo memory-files --output memory-review
setrya replay memory-review/broken
setrya replay memory-review/guardedMemory-file guide · Turn and journal guide · Historical replay and APIs
Setrya 1.2.0 · Journal-aware starters and replayable deletion follow-ups
Setrya 1.2.0 adds replayable evidence for completed deletion requests and overdue follow-ups. The disposable drill asks the application what a caller can recover. The read-only observer follows a completed deletion request and checks its journalled keys against the underlying store.
- Start with a LangGraph/PostgreSQL, OpenAI Agents, Claude Agent or Redis example. Each runs a broken deletion and its fix against the application's own endpoint and store.
- Run a declarative case directly with
setrya run case.yaml. Doctor identifies missing hooks, direct reads and scanner baselines with editable source locations. - Generate an engineer, reviewer or customer summary with external control references. Run
setrya recheckto link due follow-ups to the issuing receipt. - Check observed stores, memory namespaces and trace sinks against your inventory with
setrya coverage-drift. An empty scan still records the namespace that was read. Weekly CI exercises the latest versions of all four SDKs.
Install with python -m pip install setrya==1.2.0. Run setrya demo --output workspace, then setrya receipt summary workspace/guarded --audience reviewer.
Runnable applications · Read-only casework · Contribute a connector
Setrya 1.1.0 · Sampled erasure verdicts and read-only deletion casework
Will the assistant still reveal a deleted fact?
Setrya now records repeated answers for each caller, question and stage. One observed disclosure fails the drill. Question variants and multiple judges can catch paraphrases. The receipt records what was read, where uncertainty remains, and the number of samples. Archived single-read receipts still replay under their original contract.
- Generate a fixture for LangGraph/Postgres, OpenAI Agents, Claude Agent or Redis. A YAML case can call authenticated application endpoints and read the backing test store. A runnable Node example needs no Python in the application.
- Get one updated GitHub PR comment with bounded findings and a replayable artifact. Both workflow jobs pin the Action by SHA and the drill checks its installed package version.
- Render a customer-facing summary of a replayed receipt. For completed deletion tickets, a separate read-only observer reports present, absent or unknown at journalled keys. A weekly random sample reports the uncertainty interval and accounts for unknown cases.
Install with python -m pip install setrya==1.1.0. Run setrya demo --output workspace, then setrya replay workspace/broken and setrya replay workspace/guarded. The broken fixture exits 1. The guarded fixture passes the engineering checks and leaves one provider follow-up open.
First pull request · HTTP and stack starters · Read-only casework · Worker-race demo
Setrya 1.0.3 · First PR verdict on GitHub Marketplace
Get your first pull request verdict
Copy the commands in the workflow guide to add a synthetic deletion test to a PR. The workflow keeps a replayable receipt, including when the application serves a deleted fact. Same-repository PRs also receive a verdict comment.
Switch the generated starter to the Flask and SQLite application fixture to exercise an authenticated answer route and a real deletion operation. The guide explains when to opt into a delayed-worker drill.
The Marketplace description now names the stale-answer failure. On the example PR, compare the sample verdict, the residual after deletion and the result after cache eviction.
Install with python -m pip install setrya==1.0.3. GitHub Marketplace
Setrya 1.0.2 · Get your first PR verdict
Get your first pull request verdict
Copy the commands in the workflow guide to add a synthetic deletion test to a PR. The workflow keeps a replayable receipt, including when the application serves a deleted fact. Same-repository PRs also receive a verdict comment.
Switch the generated starter to the Flask and SQLite application fixture to exercise an authenticated answer route and a real deletion operation. The guide explains when to opt into a delayed-worker drill.
Install with python -m pip install setrya==1.0.2. GitHub Marketplace
Setrya 1.0.1 · Bind receipts to the current run
Setrya 1.0.1 fixes how an erasure run ties a verdict to the worker, store reads and receipt that produced it.
What changed
- A live person drill checks that its receipt matches the evidence written during that invocation. An explicit person or tenant scope is enforced during review and signing.
- Worker checkpoints are bound to the selected subject. Store and cache scanners report incomplete reads when they cannot establish the state of the declared data.
- Doctor and the CLI identify fixture setup failures without forwarding private exception text. The CI example uploads verified receipts, including evidence of an observed failure.
- A PR handoff checks the digest of the completed search recording and keeps a recorded failure if teardown times out.
Try it
python -m pip install setrya==1.0.1
setrya demo --output workspace
setrya replay workspace/guardedTwo teammates reopen the same support handoff. The broken worker brings back the deleted hostname. The fixed worker preserves the launch date for both readers, and the receipt leaves a provider follow-up open. Download workspace-erasure.zip to replay and verify both signed receipts.
Setrya 1.0.0 · Test what your AI assistant remembers after deletion
Test whether your AI assistant can still reveal a customer's deleted information.
Reproduce the release example
python -m pip install setrya==1.0.0
setrya demo --output workspace
setrya replay workspace/guardedTwo teammates reopen the same support handoff. The broken writer restores the deleted customer hostname. The guarded writer leaves it absent while both readers still get the team's launch date. The passing receipt has an open provider follow-up.
Download workspace-erasure.zip for both signed receipts. The signer is the repository’s erasure workflow on main. The independent verifier needs the original evidence directory, an exact signer identity and a trusted Sigstore root.
Changes for adopters
- Start with one private record and one caller using the generated starter and read-only doctor. Add shared rewrites, preserved records and a delayed writer as needed.
- Use built-in marker, regex or entity matching, or supply a model judge. Recorded decisions replay offline.
- Review one v3 format across person, tenant and Macie discovery cases. Historical receipts replay under their original rules.
- Read scoped stores, local agent sessions and self-hosted Langfuse traces. The integrations document which external surfaces remain unverified.
- Run the drill with the reusable GitHub Action and send the verdict and receipt link to the pull request.
Setrya 0.18.0 · Verify a Macie finding across an AI application
Trace one Amazon Macie S3 finding through a disposable AI application. A reviewed mapping identifies the test subject, source revision, approved action, environment, application commit, and AI services. The result goes back to the originating case as a verified JSON attachment.
python -m pip install 'setrya[erasure]'
setrya discovery demo --output catalog-review
setrya discovery replay catalog-review/guardedThe three example runs use a shared LangGraph investigation. An unread second cache leaves a named coverage gap. A delayed worker restores the deleted fact in the broken application. Both callers keep the retained finding in the guarded run, and the provider follow-up stays open.
Download macie-case-review.zip to verify the workflow signatures and replay the original results offline. The import uses a local finding export. Returning the attachment to a ticket or case system stays under your control.