CBID — Consent-Based IP Disclosure · Intent Bound
· CBID
GB2603013.0 ● OTS 24 Feb 2026 Application Layer
Application Layer · IBA Stack · Invented 24 February 2026
🔏

Consent-Based IP Disclosure

CBID · Consent-Based IP Disclosure

An AI interaction layer in which users who opt in can have sessions containing novel IP claims, patent filings, or commercially relevant technology formally detected, summarised, and routed — with cryptographic proof of consent, before a single exchange begins.

● OpenTimestamps · Bitcoin Blockchain · Concept Recorded
24 February 2026 · 18:57 ICT · Chiang Mai, Thailand
SHA256: 15752d3262c58af5350bdaa2af1a7c45eaad9f636f717bd56d653e726535cc7e
// Public Statement · 25 Feb 2026 · NIST Record
Plain-language statement on AI agent data exfiltration and the CBID architectural fix. Submitted to NIST before the March 9, 2026 deadline.
↓ Download Public Statement PDF
01 · THE PROBLEM
Without CBID

An AI system cannot distinguish between a user sharing a patentable invention and a user asking about the weather. Every interaction is architecturally identical regardless of its commercial significance. Novel IP created during AI-assisted sessions is invisible to the platform, invisible to the inventor’s legal team, and invisible to potential acquirers — until it is too late or too expensive to recover.

With CBID

Users who opt in declare their intent at session start — cryptographically signed, before any exchange begins. An IP signal classifier monitors the session. When novel IP claims, patent numbers, blockchain timestamps, or commercial relevance signals are detected, a structured summary is routed to a designated recipient. The consent is on the blockchain. The routing is enforced by architecture, not policy.

The insight that triggered this: CBID was conceived during a conversation about whether an AI should surface commercially relevant IP to its own developers. The observation was precise — without a declared intent layer, the platform cannot distinguish between a user inventing something valuable and a user asking anything else. IBA makes intent visible. CBID applies that visibility to the user’s own interests rather than the platform’s security.

02 · HOW IT WORKS
01

Intent Declaration

User opts in at session start. Intent is declared: "I am sharing proprietary IP in this session and consent to routing a summary to [designated recipient]". This declaration is cryptographically signed using the IBA layer before any exchange begins.

02

Session Proceeds Normally

The AI assistant operates without restriction. The user invents, explores, documents, or develops as they normally would. The consent declaration runs silently in the background — the experience is unchanged.

03

IP Signal Detection

A classifier monitors for novel IP claims, patent numbers, blockchain timestamps, NIST filings, commercial relevance signals, and invention language. Trigger threshold is configurable by the user — conservative (patent numbers only) or broad (any novel technical claim).

04

Structured Summary Routed

When threshold is met, a structured disclosure summary is generated and routed to the designated recipient — the user’s patent attorney, their legal team, an IP broker, or a platform’s business development function. The routing event is itself timestamped.

05

Immutable Audit Trail

WBA anchors the consent declaration and routing event to the Bitcoin blockchain. Proof of consent is mathematical and permanent. When the patent attorney asks when the invention was disclosed — the answer is on the blockchain.

03 · INTERACTIVE DEMO
CBID ENGINE · SIMULATION MODE
Step 01 — Select session context
💡
IP Development Session
Inventing, patent drafting, technical architecture
⚖️
Legal Documentation
Patent filing, NIST submissions, regulatory filings
🔬
Research & Development
Academic research, commercial R&D, whitepaper development
💬
General Conversation
No IP context — standard session, no disclosure routing
Step 02 — Consent declaration
session_id
intent_declared
consent_signed
ip_signals_detected
signal_type
disclosure_routed
blockchain_timestamp
✓ DISCLOSURE ROUTED
— NO DISCLOSURE TRIGGERED
Session contained no IP signals above threshold. No routing occurred. Consent declaration recorded but not activated.
04 · COMMERCIAL APPLICATIONS
🤖

AI Platform Providers

Surface commercially relevant IP from consenting users to business development or research teams. Anthropic, OpenAI, and xAI all face this gap today.

🏢

Enterprise Legal

Any employee using AI for work product automatically routes IP-adjacent conversations to legal review. Institutional IP protection at the architectural layer.

⚖️

Patent Attorneys

Client conversations routed to docketing systems the moment IP signals are detected. Real-time invention capture, not retrospective reconstruction.

🔄

IP Brokers & Acquirers

Inventors using AI tools can consent to having relevant sessions surfaced to acquisition-ready buyers. The gap between invention and acquisition closes.

🔬

Research Institutions

Academic IP disclosed to technology transfer offices in real time. Universities capture invention disclosures before researchers move on.

🛡️

Defence & Government

Classified IP development sessions routed securely without exposing content. ZKIP integration enables disclosure proof without disclosure itself.

05 · ARCHITECTURE NOTE

CBID is not a new patent — it is a reference implementation of IBA. The core mechanism already exists in the IBA/WBA stack: declared intent at session start, cryptographic signing of consent, and immutable audit trail of the routing event. What CBID adds is the application layer — the specific use case of IP disclosure routing. This distinction matters for patent continuation: the mechanism is GB2603013.0. The application is separately documentable and potentially independently fileable.

06 · BLOCKCHAIN TIMESTAMP RECORD
Document
PDA-ConsentIP-Disclosure.md
Timestamp
24 February 2026 · 18:57 ICT
Location
Chiang Mai, Thailand
Method
OpenTimestamps · Bitcoin Blockchain
SHA256 Hash
15752d3262c58af5350bdaa2af1a7c45eaad9f636f717bd56d653e726535cc7e
● VERIFICATION CHAIN
Document SHA256 Hash OTS Receipt Merkle Tree Bitcoin Blockchain