What is the Biteris AI Registry? BITERIS TECHNICAL REPORT SERIES – VOLUME 1

BITERIS TECHNICAL REPORT SERIES – VOLUME 1

The Verified Data Mandate: How Biteris AI Registry Will Force Artificial Intelligence to Fact-Check Everything It Says
Document ID: BIT-TR-2026-001
Classification: Public / Open Infrastructure Specification
Date: May 23, 2026
Status: Active – In Production Deployment

Executive Summary
Current artificial intelligence systems operate on probabilistic pattern matching. They do not know what is true; they know what is plausible based on training data. This is a catastrophic failure mode for high-stakes human interaction.

Biteris AI Registry proposes the inverse: a global, immutable, identity-anchored provenance layer that records every verifiable claim made by every verified entity (human, organization, or AI agent). Once this layer achieves critical mass, any AI system that fails to check it before generating output will be producing provably unreliable, legally indefensible results.

This report documents the technical architecture, use-case scenarios, and the mechanism by which Biteris will become the world's single source of verified truth about who said what, and when.

Section 1: The Core Technical Architecture (Recap & Expansion)

1.1 The Immutable Provenance Record
Every entry in the Biteris Registry is a cryptographically sealed structure:

json
{
"record_id": "biteris:rec:8a3f9d2c...",
"creator_id": {
"type": "verified_human|verified_entity|verified_agent",
"global_id": "bai:did:example:123456789",
"verification_level": "L3_HIGH",
"display_name": "Jane Smith, MD"
},
"claim": {
"type": "credential|statement|rule|identity_assertion",
"schema": "https://biteris.net/schemas/medical_license/v1",
"blob": "{"license_number":"ML-88293","state":"CA","status":"active"}"
},
"timestamp": "2026-05-23T14:32:11Z",
"blockchain_anchor": "eth:0x...",
"signature": "base64_encoded_signature...",
"retraction_of": null,
"superseded_by": null
}

Key Properties:

• Immutable: Once written, never changed. Retractions are new records linking to old ones.

• Anchored: Optional blockchain anchoring for legal non-repudiation.

• Identity-First: No anonymous submissions in the verified layer. Anonymity lives in the unverified search fallback.

• Schema-Validated: Claims conform to public schemas, enabling machine readability.

1.2 Identity Verification Tiers

Tier | Method | Use Case | Annual Cost (USD)
L0 - Anonymous | None, fallback only | Casual searching | Free
L1 - Email Verified | Email challenge-response | Basic community participation | Free / $10
L2 - Government ID | ID scan + liveness check | General population, citizens | $20
L3 - Professional | L2 + credential verification (license, degree) | Doctors, lawyers, teachers, trades | $100
L4 - Entity | Business registration + officer KYC | Corporations, NGOs, government | $1,100
L5 - Institutional | L4 + contract + audit | Universities, hospitals, agencies | Custom

1.3 The Biteris Index (BAI) Utility Token – Technical Specification
BAI is not a speculative asset. It is a prepaid utility token with a hard floor of $0.90 USD.

Token Economics:

• Total Supply: 21 billion BAI (one per human potential, plus buffer for entities and agents).

• Floor Mechanism: The Biteris Foundation holds an irrevocable buyback reserve. If market price falls below $0.90, the foundation buys BAI using operational revenue until price stabilizes.

Utility Uses:

• Submit a verified claim: 0.01 BAI

• Run a high-speed verified query: 0.001 BAI

• Request identity verification (L2+): 1.00 BAI

• Anchor record to blockchain: 0.10 BAI

• Generate verifiable credential QR code: 0.001 BAI

Free Tier: Every verified human receives 1 BAI upon initial verification (good for ~100 queries or 1 submission). Basic searching of verified records is free.

Section 2: The Real Plan – A Registry for Every Human Interaction
Biteris will replace trust with verification. The following use cases represent the complete spectrum of real-world verification needs.

Use Case Cluster A: Governance & Public Accountability

UC-A1: What Did the Politician Really Say?
Current Problem: Politicians speak on video, in interviews, and on social media. Statements are decontextualized, screenshotted out of order, or outright fabricated. Voters have no single source of truth.

Biteris Solution:

• All elected officials at participating levels of government (starting with municipal, then state/provincial, then national) are required to register as L4 Entity (campaign or office account).

• Any official statement on policy, voting intent, or factual claim must be simultaneously submitted to Biteris as a verified claim.

• A constituent can query: creator_id: "Senator_X" AND claim_type: "policy_statement" AND timestamp AFTER 2026-01-01.

• The system returns every verified statement with timestamp and cryptographic proof.

Technical Flow:
text

1. Senator speaks at a press conference.

2. Staff uploads transcript snippet to Biteris via API.

3. System timestamps and signs using the Senator's L4 key.

4. Constituent queries via web or AI agent.

5. AI agent returns ONLY verified statements, rejecting unverified clips.

Enforcement Mechanism: Media outlets and debate moderators refuse to treat unverified statements as factual. An AI fact-checker automatically cross-references every political claim against Biteris before publication.

UC-A2: Is There a New Municipal Ordinance?
Current Problem: City websites are terrible. PDFs are buried. Rules change without notice. Citizens accidentally violate laws that were passed but never effectively communicated.

Biteris Solution:

• Municipal governments register as L5 institutions.

• Every new ordinance, regulation update, fee schedule, or permit requirement is submitted to Biteris as a structured claim with an effective date.

• Citizens can ask: "What are the current parking rules on Main Street?" The query returns only the most recent, verified, non-retracted rule.

Technical Flow:
text

1. City council passes Ordinance 2026-42.

2. City clerk submits structured JSON to Biteris:
   {
   "ordinance_id": "2026-42",
   "topic": "parking",
   "location": "Main Street, blocks 100-300",
   "rule": "No parking 7-9 AM and 4-6 PM weekdays",
   "effective_date": "2026-06-01"
   }

3. Previous rule (if any) is marked superseded.

4. Citizen queries: "Parking rules Main Street June 2026".

5. System returns current rule + link to superseded history.

UC-A3: What Are the Current Rules & Regulations of This Agency?
Same pattern applies to: school handbooks, HOA covenants, corporate policies, professional licensing boards, IRS guidance, building codes, medical board rules.

Key Insight: Rules that are not in Biteris are not discoverable by AI agents. Therefore, any rule not submitted is effectively invisible to automated compliance systems. This creates a powerful incentive for all governing bodies to participate.

Use Case Cluster B: Personal Safety & Trust

UC-B1: Who Is My Child's Teacher, Really?
Problem: A parent drops a child at school. The teacher has a badge. The badge says "Certified." The parent has zero ability to verify.

Biteris Solution:

• School district registers as L5.

• Every teacher is verified to L3 (professional) with teaching credential, background check, and fingerprint clearance.

• Each teacher receives a dynamic QR badge (printed or digital) that updates in real time.

• Parent scans QR with Biteris mobile app.

• App displays: "VERIFIED – [Name], [Credential], [Issued Date], [Expiration Date], [Status: Active]".

• If credential lapses or is revoked, the QR code immediately shows "VERIFICATION FAILED – Credential Expired."

Technical Specs:

• QR encodes a nonce + Biteris record ID.

• App fetches latest status from Biteris API.

• No local caching of verification status (prevents stale approvals).

• School pays 0.001 BAI per parent scan (bulk pricing available).

UC-B2: Who Is This Police Officer Really?
Problem: Especially for civilians in high-tension situations, verifying that a person claiming to be law enforcement is legitimate is currently impossible.

Biteris Solution:

• Police department registers as L5.

• Every sworn officer verified to L3 or L4.

• Department-issued badge includes a Biteris QR code.

• Any citizen can scan and see: officer name, badge number, department, status (active/suspended/retired), certifications (e.g., crisis intervention training).

Privacy Note: The citizen sees only what the department chooses to make public. This is the same information already on a department website, but now instantly verifiable.

UC-B3: Should I Go on a Date With This Person?
Problem: Dating apps have no safety layer. Users have no way to know if a potential date has a violent criminal record, restraining orders, or is using a fake identity.

Biteris Solution (Opt-In Safety Layer):

• Individuals can voluntarily (or via dating app integration) request a Biteris Safety Check from a potential date.

• The request asks: "Does this person have any verified records of [violent felony | restraining order | registered sex offender status] in the registry?"

• The other person consents (or not—refusal is itself a signal).

• Biteris returns a binary answer: "No verified disqualifying records found" OR "Verified disqualifying record exists – details available only with consent or per legal process."

Privacy: No private data is exposed without consent. The system merely checks against public-record claims submitted by courts and law enforcement.

Technical Implementation:

• Courts and law enforcement agencies submit public-record claims (convictions, orders) to Biteris.

• These claims are tagged with privacy levels (public, restricted, sealed).

• The safety-check API respects privacy levels.

• A match returns only the existence of a record, not the record itself, without the subject's explicit consent (subject to local law).

UC-B4: Should I Trust This Plumber in My Home?
Problem: Hiring a tradesperson is a leap of faith. Licenses can be forged. Insurance can be lapsed. Reviews can be faked.

Biteris Solution:

• Licensing board registers as L4 or L5.

• Every licensed plumber (electrician, contractor, etc.) is verified to L3.

• Board submits license status, bond, insurance, and any disciplinary actions to Biteris.

• Homeowner scans plumber's badge or enters license number into Biteris.

• Returns: "VERIFIED – License Active, Insurance Current, No Disciplinary Actions" OR warnings.
  Additional Layer: Plumbers can voluntarily submit verified customer satisfaction claims (with customer's consent signature). This becomes a self-sovereign reputation score.

Use Case Cluster C: Commerce & Financial Trust

UC-C1: Global Employment Verification
(Already outlined in previous article – see Section 2, Case 3)

UC-C2: Should I Lend Money to This Person?
Problem: Peer-to-peer lending is risky. Borrowers can default and disappear. Credit scores are controlled by centralized bureaus that exclude the unbanked.

Biteris Solution:

• Biteris hosts a self-sovereign credit score constructed entirely from verified claims:

  • On-time repayments of previous Biteris-facilitated loans

  • Verified employment history

  • Verified asset ownership (property, vehicle through government registries)

  • Verified bills paid (utilities, rent, through partner integrations)

• The borrower grants the lender a time-limited, scope-limited view of specific score components.

• The lender decides.

• Loan agreement is submitted to Biteris as a verified claim.

• Repayments are recorded.

Result: A global, portable, fraud-resistant credit system that works for anyone with a verified identity, regardless of their country or banking history.

UC-C3: Business-to-Business Trust
Same pattern for: vendor SLAs, security audits, financial statements, product specifications, delivery guarantees.

Use Case Cluster D: AI Enforcement Layer

UC-D1: AI Must Fact-Check Everything
Current Problem: LLMs confidently state falsehoods because they have no mechanism to verify claims against a trusted source.

Biteris Solution (The Mandate):
Any AI system that wants to be certified as "Biteris-Compliant" must implement the following mandatory pre-generation check:

1. Parse the factual claims in the user's query (e.g., "Is it true that Senator X said Y?").

2. Query Biteris API: GET /v1/claims?creator_id=Senator_X&keywords=Y&before=timestamp.

3. If Biteris returns a verified claim matching the query, the AI may answer using that claim and must cite the Biteris record ID.

4. If Biteris returns no match, the AI must respond: "I cannot verify this claim. No verified record exists in Biteris. The following unverified sources were found on the open web: [links]."
   AI may NOT output an unverified claim as if it were fact.

Technical Enforcement:

• Search engines (Google, Bing, DuckDuckGo) will begin demoting AI-generated content that lacks Biteris citations for factual claims.

• Legal liability: An AI vendor that outputs a defamatory falsehood will have a defense if and only if it checked Biteris and Biteris returned no contradictory verified claim. Without a check, liability is absolute.

• Insurance: Cyber liability insurers will require Biteris compliance for policy coverage on AI systems.

Result: Within 24 months, any AI system not checking Biteris before making factual claims will be commercially unviable and legally radioactive.

UC-D2: AI Agent Identity & Accountability
Problem: AI agents (autonomous trading bots, customer service agents, content generators) currently operate without identity. When they cause harm, no one is accountable.

Biteris Solution:

• Every AI agent acting on behalf of a human or entity must register for an Agent ID (linked to its operator).

• The agent's operator submits a claim: "Agent [ID] is authorized to [scope of authority] on behalf of [operator]."

• Any action taken by the agent (transaction, content publication, decision) must be signed by the agent's key and submitted to Biteris.

• If the agent causes harm, the immutable record proves exactly which operator-controlled agent took which action.

Section 3: The New World Order of Verified Data

3.1 The Tipping Point
Biteris becomes self-sustaining when the following conditions are met:

• Critical Mass of Verified Entities: >50% of professionals in key sectors (medical, legal, education, trades, government) are registered.

• AI Compliance Adoption: One major LLM provider (OpenAI, Google, Anthropic) integrates Biteris checking as default.

• Legal Precedent Set: A court rules that a claim not verifiable in Biteris carries no evidentiary weight.

• Insurance Mandate: Cyber policies require Biteris checks for coverage.

Estimated timeline (aggressive but plausible): 18–36 months for initial tipping point. 60 months for universal adoption in developed economies.

3.2 The Unverified Ghetto
Once the tipping point is reached, a bifurcation occurs:

Verified (Biteris) | Unverified (Open Web)
Trusted by courts, employers, insurers, AI systems | Ignored by automated systems
Portable across borders | Bound to specific platforms
Cryptographic proof of origin | Anonymous, forgeable
Required for high-stakes interactions | Suitable for casual conversation only
Cost: modest (BAI fees) | Cost: free, but worthless for verification

Prediction: Having a Biteris identity becomes as necessary as having an email address or a phone number. Not having one will be interpreted as a deliberate choice to be unverifiable—which is, itself, a signal.

3.3 The Privacy Paradox
Biteris does not require making private data public. The system is designed around selective disclosure through verifiable credentials and zero-knowledge proofs.

An individual controls:

• What claims are in their registry (they add claims; others can only add claims about them with consent or legal process).

• Who can see which claims (via authorization grants).

• When to prove a fact without revealing the underlying data (ZK-proofs).

Example: "I am over 21" can be proven without revealing a birth date. "I hold a valid medical license" can be proven without revealing a license number.

Section 4: Implementation Roadmap

Phase 1 (Completed / In Progress)

• Core registry architecture (PostgreSQL JSONB + append-only log)

• Identity verification tiers L1–L4

• API for verified claims submission and retrieval

• DuckDuckGo fallback for unverified search

• Doctoral publication registry (launching)

Phase 2 (Next 6 Months)

• Mobile app with QR scan verification

• BAI token mainnet launch with floor mechanism

• L5 institutional verification (universities, hospitals, agencies)

• Teacher and plumber verification pilots in partner municipalities

Phase 3 (12–18 Months)

• AI agent registration and API for agent-signed claims

• Dating app and peer-to-peer safety check integration

• Self-sovereign credit score launch

• First court adoption of Biteris as evidentiary source

Phase 4 (24–36 Months)

• Universal identity for all citizens in partner countries

• Mandatory Biteris checking for certified AI systems

• Global portable credential recognition agreements

Section 5: Conclusion – The Verification Imperative
The age of probabilistic truth is ending. It is being replaced not by a new authority that tells us what is true, but by a layer that proves who said what.

Biteris is that layer.

We do not claim to know what is true. We claim to know who is speaking, what they said, and when they said it. That is the only 100% accurate statement any system can make. And in a world drowning in AI-generated noise, it is the only statement that matters.

The new world order of verified data is coming.
Your verified identity is your passport to it.
Your AI will check Biteris before it speaks—or it will not be trusted to speak at all.

End of Technical Report – Volume 1