Source-Verification Standard
Source-Verified by Design
How We Build Trustworthy Compliance Intelligence
Source-verified compliance means every statement in a node traces to the primary legal instrument through a canonical URL and a specific section reference, so any claim can be independently checked against the original text.
Every Bidda node is extracted from a real primary legal source, checked automatically against its source, reviewed by a person, cryptographically signed, and monitored on a rolling sweep for regulatory amendments. You do not have to trust us: paste any citation into the official register and read it yourself. Here is the exact pipeline, and why it matters when a regulator asks where your AI got its answer.
Primary sources only
No inference without a regulatory anchor
SHA-256 signed
Rolling source monitoring
Pipeline
Source Verification
Living Registry
Source Monitoring
Sylva Codex
Scanner
Benchmarks
AI-generated compliance data versus the Bidda source-verified standard
The Problem With AI-Generated Compliance Data
Most AI compliance tools generate plausible-sounding regulatory summaries from training data: a mix of law review articles, blog posts, outdated guidance, and paraphrased summaries, not the actual instruments.
When a general-purpose chatbot tells you "GDPR Article 17 requires deletion within 30 days," it is making a confident claim about a regulation it has never read in primary form. The real provision says "without undue delay." That gap is where regulatory liability lives.
Result: hallucination at the point of compliance decision
The Bidda Standard
Every Bidda compliance node is extracted from the official published text of the regulatory instrument: the actual Act, Regulation, or Standard, not a summary of it. Every claim in the node traces to a specific provision in that text.
We do not paraphrase or infer: if a provision cannot be quoted verbatim from the primary source, it does not appear in the node. Uncertainty is marked explicitly and flagged for human review.
Result: regulatory claims a lawyer can verify against the primary source
Generation Pipeline
The Four-Layer Pipeline
Every node passes all four layers sequentially. A single failure at any layer means the node is deleted and regenerated, never manually patched.
01
📄
Primary Source Identification
Real legal instruments only, with no summaries or commentary
Every node begins with a primary legal instrument: an Act of Parliament, an EU Regulation, an official agency rule. We identify the canonical URL of the official published text: eur-lex.europa.eu, federalregister.gov, legislation.gov.uk. Not a law firm summary, not a news article, not a Wikipedia page.
✓
Canonical government or standards body URL only
✓
HTTP 200 verified: dead links blocked before generation
✓
TLS SPKI fingerprinted on a rolling sweep for tamper detection
✓
Instrument reference extracted (Article, Section, Annex) from source text
Hard rule
If a regulation cannot be found at a primary legal source with a live, verifiable URL, it is not added to the registry.
02
🧬
AI Extraction: Structured and Constrained
AI works from the full text of each regulation, held to a fixed record structure
AI in the loop works from the full text of each regulation and is held to a fixed record structure. It cannot add, invent or paraphrase beyond what the source says. Every threshold, obligation and timeline must trace to a specific clause in the source document.
✓
Every record follows the same structure; incomplete output is rejected
✓
Workflow steps follow the wording of the source
✓
No placeholder text: every step is real regulatory procedure
✓
Every threshold, deadline and penalty traces to a clause in the source
Hard rule
Output that cannot be traced to the source text does not become a record.
03
🔬
Automated Source Checks
Every draft record is checked against its source before a person sees it
Each draft record then follows an internal procedure of automated checks against the primary source. A record that fails is rebuilt from the source, never patched by hand.
✓
The source is reachable at the official publisher
✓
Cited sections can be found in the source text
✓
Thresholds such as fines, deadlines and percentages trace to specific clauses
✓
Links to other records resolve to real records in the registry
✓
Each record carries a SHA-256 fingerprint of its content
Hard rule
A record that fails a check is rebuilt from the source, never patched by hand.
04
👁
Human Review
Every record is reviewed by a person against the official source before it goes live.
Every record is reviewed by a person against the live official source before it reaches the site. A claim that cannot be confirmed in the source is removed and the record rebuilt.
✓
Read against the live official source, not a cached or summarised copy
✓
Wrong section numbers, wrong thresholds or the wrong jurisdiction mean a rebuild
✓
Fingerprinted and re-validated before it goes live
Hard rule
Source-Verification Standard: before accepting any record, we ask whether every claim traces to the primary source and matches it exactly. If uncertain, it does not go live.
For Compliance Officers
What "Source Verified" Actually Means
When we say a node is source-verified, we mean every piece of guidance it contains can be traced directly back to the document it was drawn from (the original regulation, or official framework), not a summary, not a blog post, not a second-hand interpretation.
📄
Primary Sources Only
Every node in the Bidda registry is built from the official, published version of the regulation. NIST publications, EU Official Journal, ICAO annexes, and equivalent authority bodies. We never use third-party commentaries or paraphrased guides as source material.
If you quote a Bidda node in an audit submission, you can point directly to the regulation it came from. The citation is embedded in the node itself.
🔒
Cryptographic Integrity
Each node is assigned a SHA-256 hash, a unique digital fingerprint of that node's content at the moment it was verified. If anyone changes even a single character of the node's data after signing, the fingerprint no longer matches and the system flags it immediately.
You can be confident the compliance guidance you receive is exactly what was reviewed and approved, not a version that has been edited, corrupted, or tampered with in transit.
📅
Dated & Version-Controlled
Regulations change. Nodes carry a version number and a last_updated date. When the underlying regulation is amended, the affected nodes are re-audited and re-signed, and the version number increments. You always know whether you are looking at current law.
Your compliance team is never inadvertently working from an outdated framework, one of the most common causes of audit findings.
🔗
Cross-Framework Mapping
Most organisations operate under multiple overlapping standards: GDPR and NIST CSF, or HIPAA and SOC 2. Each node includes a crosswalks field that maps the regulation to related frameworks. Satisfying one standard often partially satisfies another, and the nodes tell you where.
You can see exactly which controls from Framework A satisfy requirements in Framework B, reducing duplicated compliance effort across your organisation.
The Bottom Line for Compliance Officers
Bidda does not produce advice. It surfaces source-verified regulatory logic in a structured format that compliance teams can act on, cite, and present to auditors. Every node names its issuing authority, links its primary source, and carries a content fingerprint of that source. Where an effective or enactment date could be established from the instrument it is published; where it could not, the field is absent rather than estimated. Every measurement behind this page, including the gaps we are still working through, is published as data at /api/v1/proof-dossier.json.
Continuous Integrity
After Acceptance: The Living Registry
Publishing a record is not the end of the quality process. It is the beginning of a continuous integrity programme.
Current Registry Status
Ledger Cryptographically Signed
Verified Nodes
10,102
Critical Violations
0
Integrity Hash
SHA-256
Data Provenance
Official
SYSTEM NOTE: Autonomous agents can verify node integrity by comparing their local cryptographic payload hash against our publicly signed index. This is designed to detect man-in-the-middle tampering, silent data changes, and injected logic.
🔐
Integrity Hash
Every node gets a SHA-256 content hash at acceptance, and the hash is re-verified on every build, so any change to node content invalidates the hash and blocks deployment.
📡
Rolling Source Watch
Source URLs are re-fetched on a continuous oldest-first sweep, with a TLS public-key hash to detect DNS hijacking and a content SHA-256 hash to detect substantive amendments by the regulator. Detected changes queue for human review. The measured age distribution of fingerprints is published rather than summarised as one interval.
⛓
Git Merkle Chain
Every version of every node is preserved in the git commit history. The DAG structure provides cryptographic chaining, independently verifiable with stock git tooling. No proprietary audit system required.
Weekly Automated Monitoring
Knowing When Regulations Change
Knowing a node is accurate today is only half the picture. Knowing it is still accurate next week is the other half. Bidda runs an automated scan of every primary source URL across all 10,102 nodes every week, before any compliance team would typically notice an amendment themselves.
🔐
TLS Certificate Fingerprint
Each primary source URL is fingerprinted at the TLS layer, the cryptographic key of the server hosting the regulation. If a regulatory body's server key changes unexpectedly, the mismatch is flagged for human review before any change enters the registry.
Catches: DNS hijacking, certificate swaps, MITM redirects on regulatory domains.
📝
Content Hash Comparison
A SHA-256 hash of the published source text is compared against the baseline from last verification. If the text changes, even a single amended clause, the hash no longer matches, and the affected node enters the amendment review queue within 7 days.
Catches: published amendments, revised annexes, superseded standards, regulation repeals.
📋
Git Merkle Audit Trail
Every sweep result is committed to a public git repository. Each commit is a Merkle-anchored snapshot of what every source looked like at a specific point in time, verifiable with standard open-source tooling.
Useful for: regulatory audits, evidence of due diligence, litigation support.
Live Registry Health: Public Endpoint
Compliance teams and agents can query this public endpoint at any time, with no authentication required, to see the current state of the source integrity scan. If sources_with_changes_in_last_7_days is non-zero, re-run staleness checks against your cached node inventory to identify which regulations have been amended.
Request
curl https://bidda.com/api/v1/registry-health.json
Key fields to watch
last_check_completed: when the most recent scan ran
sources_with_changes_in_last_7_days: non-zero = action needed
freshness_days: measured age of the newest fingerprint per source (p50 / p95 / oldest)
integrity_attestation: cryptographic proof string for audit logs
Recommended practice: add this endpoint to your weekly compliance checklist. One call tells you whether any regulation you rely on has been amended since your last review.
View live →
Interactive Visual Tool
Sylva Codex: The Regulation Dependency Graph
One of the most overlooked risks in enterprise compliance is treating regulations as silos: GDPR here, NIST CSF there, DORA somewhere else. In practice, regulations overlap, depend on each other, and share control requirements. The Sylva Codex makes those relationships visible and machine-traversable.
🕸️
What It Is
An interactive network graph rendering every verified Bidda node as a point in a live dependency topology. Each edge represents a real, documented relationship between two regulations: a prerequisite, a crosswalk, or a control overlap confirmed by primary source analysis. Updates automatically as new nodes are accepted.
🔍
What It Shows You
Click any regulation and the graph highlights its full dependency chain in gold: what it depends on, what depends on it, and which peer frameworks address the same control obligations. Example: click the EU AI Act node to see immediately how it draws from GDPR Article 22, and NIST AI RMF.
🗺️
Cross-Framework Overlap Analysis
Most organisations operating under multiple overlapping standards (GDPR and NIST CSF, or HIPAA and SOC 2, or DORA and NIS2) spend significant audit effort duplicating control evidence. The Sylva Codex surfaces shared control obligations so your team can identify which evidence already satisfies multiple requirements simultaneously.
🤖
Agent-Traversable Dependency Graph
For AI compliance systems, the Sylva Codex serves as the structural backbone of the entire registry. Every node's dependencies[] array is a machine-readable edge list that autonomous agents can traverse programmatically, resolving a compliance question without a human directing each step.
10,102
Regulation nodes in graph
39
Sovereign pillars visualised
2,400+
Dependency edges mapped
The Bottom Line
The Sylva Codex answers the question every compliance officer eventually faces: "If this regulation changes, what else in our programme is affected?" It turns a historically manual, expensive analysis into a visual query that takes seconds.
Open Sylva Codex →
Free Developer Tool, Open Source
Bidda Agent Compliance Scanner
A free, open-source GitHub Action that brings Bidda's sovereign compliance intelligence directly into your engineering workflow, scanning every pull request for AI agent regulatory exposure before it reaches production.
🔍
What It Scans
On every pull request, the Action scans changed files for AI agent code patterns with direct regulatory implications: LangChain, CrewAI, AutoGen, Pydantic AI imports; MCP tool and server definitions; biometric identification libraries (EU AI Act Annex III); AI-driven hiring code (NYC Local Law 144); automated credit-decisioning (GDPR Article 22, ECOA); and DORA-relevant ICT third-party dependencies.
💬
What Your Team Gets
A single, idempotent PR comment, updated on each push, never spamming the thread. Each matched pattern links to the specific Bidda node most relevant to that code path, with the BLUF summary, free discovery metadata, and a vault unlock link for the full deterministic compliance workflow.
🔒
Privacy & Data Flow
The scanner runs entirely on your GitHub-hosted runner, with pattern matching done locally so your code, prompts, and diffs never leave your environment. Only the detected pattern ID and a domain filter are used to query Bidda's public discovery API, which requires no authentication.
💡
Advisory, Never Blocking
The action is advisory only by default and never blocks a PR: compliance officers get the right reference at the right moment while engineers keep shipping without friction. Enterprise v0.2 adds Skyfire bearer token support for bulk pre-authorised unlocks.
Add It in 30 Seconds
No config, no API key, and no account required.
View Source →
# .github/workflows/bidda-compliance.yml
name: Bidda Agent Compliance
on:
pull_request:
branches: [main]
permissions:
pull-requests: write
contents: read
jobs:
scan:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: Bidda-Ai/agent-compliance-scanner@v0
10,102
Nodes in registry
12
Code patterns detected
0
PR blocks by default
Illustrative Workflow
How a Real Agent Uses Bidda
A global logistics platform deploys an autonomous shipping agent that needs to verify compliance rules for shipping lithium batteries by air, without calling a human compliance officer. Here is how Bidda handles it end-to-end in four deterministic steps.
QUERY
Agent
Discovery Request
A logistics agent handling an international shipment queries the Sovereign Registry for IATA Dangerous Goods Regulations applicable to lithium battery air transport.
GET /api/v1/nodes/iata-dangerous-goods
RETURN
Bidda
Verified Node Metadata
Bidda returns the verified node BLUF, canonical authority citation, SHA-256 integrity hash, and a 402 challenge to unlock the full deterministic logic graph.
{ "id": "iata-dgr-9a", "hash": "a3f9...c12e", "authority": "IATA", "requires_payment": true }
SETTLE
Agent
L402 Micropayment
The agent autonomously settles a USDC transaction on the Base network. The signed on-chain receipt is presented as the vault bearer token.
Authorization: L402 [base_signed_onchain_receipt]
UNLOCK
Bidda
Full Intelligence Delivered
The complete deterministic logic graph is returned: packing rules, quantity limits, labelling requirements, and documentation checklists, all machine-executable, with reduced hallucination risk.
{ "rules": [...], "documentation": [...], "verified_at": "2026-04", "hash_valid": true }
The Outcome
The agent autonomously resolved a task that typically takes a human compliance analyst a few hours to validate: the correct IATA Section II lithium battery packing regulations, verified against the official 2024 IATA DGR edition, cryptographically signed, and returned directly into the shipment workflow, with reduced hallucination risk, no liability gap, and no human bottleneck.
Current Quality Benchmarks
Snapshot of registry health at last build. Re-published with every deploy.
10,102
Nodes accepted
all 4 layers passed
0
Critical violations
in current registry
39
Sovereign pillars
zero empty
~7
Avg primary citations
per node
0
Placeholder markers
eliminated April 2026
8,000+
Source URLs
rolling fingerprint sweep
What This Means in Practice
Compliance Officers & Legal Teams
→
Every node is traceable to a specific clause in a specific instrument. Paste the citation into eur-lex.europa.eu or federalregister.gov and read it yourself.
→
The version of the source at extraction time is fingerprinted. You can prove what the regulation said on the date your AI agent consulted it.
→
Zero placeholder content in production: every workflow step is a real regulatory procedure, not a gap marker.
AI Agents & Autonomous Systems
→
The deterministic_workflow in each node is a machine-executable procedure, not a natural language summary but a structured sequence of conditional steps.
→
The actionable_schema provides typed fields for agent orchestration: trigger conditions, required inputs, decision thresholds, output format.
→
The dependency graph lets an agent discover the full compliance chain for any obligation, from a single node unlock to a complete regulatory mapping.
Frequently Asked Questions
How does Bidda verify compliance nodes?
+
What does "source-verified" mean for a compliance node?
+
How does Bidda detect when a regulation changes?
+
What is the Sylva Codex and how does it help compliance officers?
+
Can I use Bidda nodes in an audit or legal proceeding?
+
See It For Yourself: Free Sample Node
The free sample node for EU AI Act Article 10 shows every field of the 13-key schema: the full deterministic workflow, all primary citations, the actionable schema, and the dependency graph. No payment required.
View Free Sample Node →
Browse 10,102 Nodes →
Enterprise inquiry: [email protected] · API access: [email protected]