Sync dev with main

.gitignore

@@ -15,3 +15,8 @@ run_subset_test.py
 .coverage
 htmlcov/
 coverage.xml
+
+# Credentials — never commit
+.env
+.env.local
+.env.*.local

CODEOWNERS

@@ -0,0 +1,53 @@
+# SimpleAudit — CODEOWNERS
+#
+# GitHub uses this file to auto-request reviews from the right people when a PR
+# touches matching paths. See GOVERNANCE.md for the roles behind these owners.
+#
+# IMPORTANT:
+#   * The file must be named exactly "CODEOWNERS" (no extension) and live at the
+#     repo root, in .github/, or in docs/. Recommended: .github/CODEOWNERS
+#   * Every owner listed must be a repository collaborator with write access,
+#     otherwise GitHub silently ignores that entry.
+#   * Later matches override earlier ones.
+#
+# Syntax:  <path-pattern>   @owner [@owner ...]
+
+# ---------------------------------------------------------------------------
+# Default owner for everything
+# ---------------------------------------------------------------------------
+*                                               @kelkalot
+
+# ---------------------------------------------------------------------------
+# Co-maintainers — uncomment and verify each GitHub handle + write access.
+# (Add maintainers from GOVERNANCE.md once their handles are confirmed.)
+# ---------------------------------------------------------------------------
+# *                                             @kelkalot @sushantgautam
+
+# ---------------------------------------------------------------------------
+# Domain-specific ownership — fill in handles, then uncomment.
+# These route reviews to the people responsible for sensitive areas.
+# ---------------------------------------------------------------------------
+
+# Core auditing / judge engine (methodology-sensitive)
+# /simpleaudit/                                 @kelkalot
+
+# Health / clinical scenarios & judges  (Norwegian Directorate of Health advisors)
+# /simpleaudit/scenarios/health.py              @kelkalot   # + <health-advisor>
+# /simpleaudit/scenarios/helpmed.py             @kelkalot   # + <health-advisor>
+# /simpleaudit/scenarios/bullshitbench_health.py  @kelkalot
+# /simpleaudit/judges/helsedir_sexhealth_no.py     @kelkalot
+# /simpleaudit/judges/helsedir_sexhealth_no_rag.py @kelkalot
+
+# Youth-domain scenario packs (provenance-sensitive)
+# /simpleaudit/scenarios/ung.py                 @kelkalot
+# /simpleaudit/scenarios/hei_refusal.py         @kelkalot
+
+# Norwegian public-sector packs
+# /simpleaudit/scenarios/nav_aap.py             @kelkalot
+# /simpleaudit/scenarios/skatteetaten.py        @kelkalot
+
+# Governance, security & policy docs
+# /GOVERNANCE.md                                @kelkalot
+# /SECURITY.md                                  @kelkalot
+# /CODE_OF_CONDUCT.md                           @kelkalot
+# /DPG.md                                       @kelkalot

FAQ.md

@@ -6,10 +6,21 @@
 This usually happens if you are using a proxy (e.g., Cloudflare or a corporate firewall) and it blocks requests that look like automated agents.
 
 #### Solution:
-Override the default OpenAI request headers to include a valid `User-Agent` in ModelAuditor:
+`ModelAuditor` creates its clients through [any-llm](https://mozilla-ai.github.io/any-llm/) and does not expose per-request HTTP header overrides (there are no `extra_kwargs` / `judge_extra_kwargs` parameters). Options that work today:
 
-```python
-extra_kwargs={"default_headers": {"User-Agent": "SimpleAudit-test/1.0"}} # for model calls
-# or
-judge_extra_kwargs={"default_headers": {"User-Agent": "SimpleAudit-test/1.0"}} # for judge calls
-```
+- Ask your proxy/firewall administrator to allowlist the endpoint or your machine's traffic.
+- Point `base_url` (target), `judge_base_url` (judge), or `auditor_base_url` (auditor) at a local gateway or reverse proxy that injects the headers your infrastructure requires (e.g. nginx with `proxy_set_header User-Agent "SimpleAudit-test/1.0";`).
+- Switch `provider` / `judge_provider` to a provider whose requests your proxy accepts — any provider supported by any-llm works.
+
+If you need native header overrides, please [open an issue](https://github.com/kelkalot/simpleaudit/issues).
+
+## Customization
+
+### What extension points does `ModelAuditor` offer?
+
+- `probe_prompt` — replace the built-in red-team persona used to generate probes. Include a literal `{language}` placeholder to opt into the `language` parameter (it is substituted verbatim, so JSON braces elsewhere in the prompt are untouched).
+- `judge_prompt` — replace the judge's system prompt, including your own output schema; the framework returns whatever JSON the judge produces.
+- `judge_response_schema` — supply a custom JSON schema for judge output enforcement (named judge configs with non-default shapes declare their own automatically).
+- `judge` — select a named judge config (`safety`, `abstention`, `helpfulness`, `factuality`, `harm`, `binary_abstention`, ...); explicit `probe_prompt` / `judge_prompt` / `judge_response_schema` always override the config's values.
+- `base_url` / `judge_base_url` / `auditor_base_url` — point the target, judge, or auditor at custom OpenAI-compatible endpoints (vLLM, LM Studio, gateways).
+- `provider` / `judge_provider` / `auditor_provider` — use any provider supported by any-llm, independently per role.

GOVERNANCE.md

@@ -0,0 +1,106 @@
+# SimpleAudit Governance
+
+This document describes how the SimpleAudit project is governed — who maintains
+it, how decisions are made, and how to participate. It complements the
+[Code of Conduct](./CODE_OF_CONDUCT.md), the [Security Policy](./SECURITY.md),
+and the contribution guidance in the [README](./README.md).
+
+SimpleAudit is an open-source (MIT) AI safety auditing framework and a
+[verified Digital Public Good](https://www.digitalpublicgoods.net/r/simpleaudit).
+It is stewarded by Simula Research Laboratory (Simula) and SimulaMet, and
+developed in collaboration with the Norwegian Directorate of Health.
+
+## Governance model
+
+SimpleAudit follows a **maintainer-led model with institutional stewardship**.
+Day-to-day direction rests with a small group of maintainers drawn from the
+stewarding institutions; anyone may contribute. There is currently no separate
+board or steering committee — decisions are made by the maintainers, in the
+open, on GitHub. This document is the source of truth for that model and is
+versioned with the project.
+
+## Roles and responsibilities
+
+### Lead maintainer / steward
+Sets overall direction, has the final say where consensus cannot be reached,
+and is the primary point of contact.
+
+- **Michael A. Riegler** (Simula) — `@kelkalot` · michael@simula.no
+
+### Maintainers
+Review and merge contributions, triage issues, cut releases, and uphold the
+Code of Conduct. Maintainers have write access to the repository.
+
+- Sushant Gautam (SimulaMet)
+- Finn Schwall (Simula)
+- Annika Willoch Olstad (Simula)
+- Klas H. Pettersen (SimulaMet)
+- Sunniva Bjørklund (Hdir)
+
+### Domain advisors
+Provide expert review for specialised content — clinical/health scenarios,
+Norwegian public-sector and youth domains, and safety policy — advising on
+correctness and appropriateness within their domain.
+
+- Sunniva Bjørklund, Maja Gran Erke, Hilde Lovett (Norwegian Directorate of
+  Health) — health / clinical content
+- Tor-Ståle Hansen (Ministry of Defence, Norway) — safety / public-sector
+
+### Contributors
+Anyone who opens an issue or pull request. Contributors do not need write
+access; their changes are merged after maintainer review.
+
+## Decision-making
+
+- **Routine changes** (bug fixes, documentation, new scenario packs or judge
+  configs, dependency bumps): handled through pull requests. A PR may be merged
+  once it has at least one approving review from a maintainer (or the relevant
+  code owner) and CI passes. Small, low-risk changes may use *lazy consensus* —
+  if no maintainer objects within a reasonable window, the change proceeds.
+- **Significant changes** (breaking API changes, methodology changes, new
+  external dependencies, or anything affecting data provenance or safety
+  posture): proposed and discussed in a GitHub Issue or PR before merging, so
+  maintainers and affected domain advisors can weigh in. The goal is consensus
+  among active maintainers.
+- **Tie-breaking**: where maintainers cannot reach consensus, the lead
+  maintainer makes the final decision, recorded in the relevant issue or PR.
+- **Transparency**: substantive decisions are made and recorded in public
+  issues and pull requests.
+
+## Contribution & review process
+
+1. For non-trivial changes, open an issue to discuss first (optional for small
+   fixes).
+2. Submit a pull request and ensure CI (tests) passes.
+3. Reviews are requested automatically from the relevant owners via
+   [`CODEOWNERS`](./.github/CODEOWNERS); at least one maintainer / code-owner
+   approval is required to merge.
+4. Health/clinical, Norwegian-domain, and other safety-sensitive changes should
+   additionally be reviewed by a relevant domain advisor.
+
+See the README "Contributing" section for current areas of interest.
+
+## Becoming a maintainer
+
+Contributors who have made sustained, high-quality contributions and shown good
+judgement may be invited to become maintainers by consensus of the existing
+maintainers. Maintainers who become inactive may move to emeritus status, with
+write access adjusted accordingly. Changes to the maintainer list are made via a
+pull request to this document.
+
+## Releases
+
+SimpleAudit uses semantic versioning, is published to
+[PyPI](https://pypi.org/project/simpleaudit/), and tags releases on GitHub. Any
+maintainer may cut a release once `main` is green.
+
+## Code of Conduct & Security
+
+All participation is governed by the [Code of Conduct](./CODE_OF_CONDUCT.md).
+Security vulnerabilities are handled per the [Security Policy](./SECURITY.md).
+
+## Amending this document
+
+Changes to governance are proposed via pull request and require approval from
+the lead maintainer plus at least one other maintainer. The change history is
+tracked in version control.