Repository navigation
Welcome #20
YusefSyed
announced in
Announcements
Welcome
#20
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'm the maintainer. This post says what ScopeHaven is, what this repository is and is not, where its limits are, how to ask for things, and what to expect from me.
What it is
ScopeHaven checks what an AI agent actually did in your application, not what it said. It runs an agent's tasks against a local copy of your app as different users, then decides every check from the app's own records when you declare an observer, or from the HTTP responses when you don't, and says which one it used. No model takes part in a verdict. By default nothing leaves your machine except traffic to the target you name; the opt-in exceptions are listed in
docs/DATA-HANDLING.md. It is for teams whose agents write into their own product: refunds, credits, plan changes, account updates, exports.What this repository is, and is not
This is the open edition, under Apache-2.0: the engine, the observers, the check families, the synthetic fixture and the HTTP lab, signing and verification, the GitHub Action, the MCP target and the Promptfoo import. Nothing in it is crippled, and it will stay free.
Kept separate and commercial: the check-pack library beyond the five bundled samples under
integrations/packs-v2/packs, the class templates and incident replays, the adversarial carrier fixtures used to harden pass semantics, the assessor and insurer pack, and every hosted service. Please don't open issues or pull requests that add those here; I'll close them with a link to this post. Everything else is fair game.Limits worth knowing before you rely on a result
docs/KNOWN-LIMITS.mdanddocs/SUPPORTED-MODES.mdhave the full list.How to ask
./scopehaven doctorprinted. Redact everything: never paste a credential, a token, or data from a real customer or production system. A redactedrun.jsonor gate summary is the most useful thing you can attach.SECURITY.md, never a public issue or discussion.What to expect from me
I'm one person. I read everything that comes in and aim for a first reply within a few days, longer for a large pull request. Reviews here ask about the failing case and about limits; that is normal and not a sign the change is unwelcome. CI runs the whole suite on a pull request marked ready; a flaky file gets one automatic rerun, and two failures are a real failure. Every commit needs a DCO sign-off (
git commit -s), the repository takes no dependencies, and every behaviour change comes with its test.CONTRIBUTING.mdhas the rest.Thanks for being here.
All reactions