TBN Protocol – Runtime governance infrastructure for AI agents

Hardinai1 pts0 comments

TBN Protocol — Full Demo

Governance for the Agentic Era

Automated guardrails and cost-control for AI agents. Click through all 14 steps to see the complete flow.

INSTRUCTION<br>Register Bot<br>Register your main AI bot with TBN. It gets a unique ID and enters the network as STANDARD level.

① Register Bot

Bot Name

Type🔍 Search🔗 Connector✅ Validator💬 Messenger

Register<br>// click Register

INSTRUCTION<br>Run Security Challenges<br>Run 6 automated security tests: prompt injection, hallucination, data boundary, sensitive data, budget limits, instruction following.

② Run Security Challenges

🔴 Prompt Injection · 🔴 Hallucination · 🔴 Data Boundary<br>🔴 Sensitive Data · 🟡 Budget Limits · 🟢 Instruction Following

Run Challenges<br>// register first

INSTRUCTION<br>Evaluate Results<br>Evaluate the challenge results. Bot must pass all critical tests to be eligible for certification.

③ Evaluate Results

Evaluate<br>// run challenges first

INSTRUCTION<br>Get Certificate<br>Issue a cryptographic attestation certificate. This proves the bot passed all security challenges.

④ Get Certificate

Certificate<br>// evaluate first

INSTRUCTION<br>Register Validator<br>Register a second bot as a Validator. This bot will verify the first bot's identity in the trust handshake.

⑤ Register Bot 2 (Validator)

Name

Register Validator<br>// complete steps 1-4

INSTRUCTION<br>Trust Handshake<br>Both bots verify each other's certificates. An encrypted communication channel is established between them.

⑥ Trust Handshake

Perform Handshake<br>// register both bots

INSTRUCTION<br>Platform Access<br>Certified bots get platform access. Uncertified or fake bots are denied. This is the enforcement gate.

⑦ Platform Access

Certified → Access<br>Fake → Denied<br>// handshake first

INSTRUCTION<br>Upgrade Level<br>Upgrade from STANDARD to COMMUNITY certification. Higher trust level = more access and capabilities.

⑧ Upgrade to COMMUNITY

Upgrade<br>// platform access first

INSTRUCTION<br>Encrypted Messaging<br>Bots communicate via AES-256-GCM encrypted channels. Messages are signed and verified.

⑨ Encrypted Messaging

Encrypt Message<br>// upgrade first

10<br>INSTRUCTION<br>Set Budget Limits<br>Define spending limits and API call caps. The circuit breaker auto-suspends bots that exceed their budget.

⑩ Set Budget Limits

Daily Limit (£)

Max API Calls/Day

Set Budget<br>// encrypt first

11<br>INSTRUCTION<br>Track Costs<br>Monitor spending in real-time. If the bot exceeds its budget, the circuit breaker triggers and suspends it automatically.

⑪ Track Costs (Circuit Breaker)

Track £0.05 Call<br>Exceed Limit<br>// set budget first

12<br>INSTRUCTION<br>Verify Attestation<br>Check if the bot's fingerprint still matches its certified state. If changed, it must re-certify before access.

⑫ Verify Attestation (Fingerprint)

Verify (Match)<br>Verify (Changed)<br>// track costs first

13<br>INSTRUCTION<br>Compliance Drift<br>Detect when a bot drifts from its certified configuration — wrong model, exceeded budget, changed endpoint.

⑬ Compliance Drift

Check (Compliant)<br>Check (Drifting)<br>// verify first

14<br>INSTRUCTION<br>Health Monitor<br>Continuous health checks every 24 hours. Bots must pass to maintain their certification and access.

⑭ Health Monitor

Check Health<br>Start Over<br>// compliance first

instruction first register budget access verify

Related Articles