{
  "id": 17022707,
  "title": "Bernstein – open-source governance layer for AI agents",
  "url": "https://urgent.news/2026/10/29/bernstein-open-source-governance-layer-for-ai-agents",
  "topic": "ai",
  "section": "AI",
  "published": "2026-10-29T06:24:56.000Z",
  "source": {
    "name": "Hacker News",
    "slug": "hacker-news",
    "url": "https://bernstein.run/"
  },
  "original_language": "en",
  "account": "Bernstein is an open-source governance layer designed for AI agents. It operates as a deterministic Python scheduler that runs the agents in parallel, without a model in the coordination loop. This ensures that the same plan replays byte-identically each time it is run.\n\nThe system runs on policy as code, meaning that the policy is written by the user, Bernstein enforces it, and produces a verifiable record. To perform an audit, the user can run Bernstein with the \"--audit\" flag, which creates an HMAC-chained event log under the \".sdd/audit/\" directory. Each entry in this log is a JSONL file, representing a UTC day's worth of events. Each entry references the hash of the previous entry, creating a chain of hashes that can be used to verify the integrity of the log.\n\nOne of the key features of Bernstein is that it ensures tampering with the log will break the verification process, as any alteration will result in a mismatch between the computed hash and the stored hash. Importantly, Bernstein ensures that nothing leaves the user's machine during the execution, providing a high level of privacy and security.\n\nFor those who did not run Bernstein, it is still possible to verify the logs. By checking the HMAC leg of the verification process, they can confirm that the log was created using the same key that was used when the log was generated. This key must be provided to the verifier, along with the log files themselves, to ensure a complete and accurate verification.\n\nIn addition to the HMAC verification, Bernstein also produces an ED25519-signed receipt that binds the journal and lineage heads. This receipt can be verified by anyone who has access to the public key, without requiring knowledge of the signing key used to create the receipt. This allows for provenance tracking and ensures that the logs have not been altered or tampered with.",
  "summary": null,
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}